Hello,
On Thu 22-11-12 23:31:36, Zdenek Kabelac wrote:
> For some time - when I reboot via 'sysrq + SUB' I get this BUG: message
> My system is running rawhide (systemd) on ext4 filesystem.
> systemd-195-7.fc18.x86_64
Thanks for report. Looks like my problem. Attached patch should fix it.
Now that we have a notion of (one of the) best CPUs we interrelate
with in terms of memory usage, use that information to improve
can_migrate_task() balancing decisions: allow the migration to
occur even if we locally cache-hot, if we are on another node
and want to migrate towards our best buddy's
The current way of building the p->numa_faults[2][node] faults
statistics has a sampling artifact:
The continuous and immediate nature of propagating new fault
stats to the numa_faults array creates a 'pulsating' dynamic,
that starts at the average value at the beginning of the scan,
increases mon
* Ingo Molnar wrote:
> This release mainly addresses one of the regressions Linus
> (rightfully) complained about: the "4x JVM" SPECjbb run.
>
> [ Note to testers: if possible please still run with
> CONFIG_TRANSPARENT_HUGEPAGES=y enabled, to avoid the
> !THP regression that is still not f
The exynos code claimed wp-gpio with devm_gpio_request() but never did
anything with it. That meant that anyone using a write protect GPIO
would effectively be write protected all the time.
A future change will move the wp-gpio support to the core dw_mmc.c
file. Now the exynos-specific code won'
On some SoCs (like exynos5250) you need to use an external GPIO for
write protect. Add support for wp-gpios to the core dw_mmc driver
since it could be useful across multiple SoCs.
With this change I am able to make use of the write protect for the
external SD slot on exynos5250-snow.
Signed-off
- break out of can_do_numa_run() earlier if we can make no progress
- don't flip between siblings that often
- turn on bidirectional fault balancing
- improve the flow in task_numa_work()
Cc: Peter Zijlstra
Cc: Linus Torvalds
Cc: Andrew Morton
Cc: Andrea Arcangeli
Cc: Rik van Riel
Cc: Mel
Back off slowly from scanning, up to sysctl_sched_numa_scan_period_max
(1.6 seconds). Scan faster again if we were forced to switch to
another node.
This makes sure that workload in equilibrium don't get scanned as often
as workloads that are still converging.
Cc: Peter Zijlstra
Cc: Linus Torval
Interleave tasks that are 'shared' - i.e. whose memory access patterns
indicate that they are intensively sharing memory with other tasks.
If such a task ends up converging then it switches back into the lazy
node-local policy.
Build-Bug-Reported-by: Fengguang Wu
Cc: Peter Zijlstra
Cc: Linus To
From: Peter Zijlstra
Previously, to probe the working set of a task, we'd use
a very simple and crude method: mark all of its address
space PROT_NONE.
That method has various (obvious) disadvantages:
- it samples the working set at dissimilar rates,
giving some tasks a sampling quality adva
From: Peter Zijlstra
Add the NUMA working set scanning/hinting page fault machinery,
with no policy yet.
The numa_migration_target() function is a derivative of
Andrea Arcangeli's code in the AutoNUMA tree - including the
comment above the function.
An additional enhancement is that instead of
Allow architectures to opt-in to the adaptive affinity NUMA balancing code.
Cc: Peter Zijlstra
Cc: Linus Torvalds
Cc: Andrew Morton
Cc: Andrea Arcangeli
Cc: Rik van Riel
Cc: Mel Gorman
Cc: Thomas Gleixner
Cc: Hugh Dickins
Signed-off-by: Ingo Molnar
---
init/Kconfig | 7 +++
1 file ch
From: Peter Zijlstra
Add migrate_misplaced_page() which deals with migrating pages from
faults.
This includes adding a new MIGRATE_FAULT migration mode to
deal with the extra page reference required due to having to look up
the page.
Based-on-work-by: Lee Schermerhorn
Signed-off-by: Peter Zijl
From: Andrea Arcangeli
Introduce FOLL_NUMA to tell follow_page to check
pte/pmd_numa. get_user_pages must use FOLL_NUMA, and it's safe to do
so because it always invokes handle_mm_fault and retries the
follow_page later.
KVM secondary MMU page faults will trigger the NUMA hinting page
faults thr
This patch is based on patches written by multiple people:
Hugh Dickins
Johannes Weiner
Peter Zijlstra
Of the "mm/mpol: Create special PROT_NONE infrastructure" patch
and its variants.
I have reworked the code so significantly that I had to
drop the acks and signoffs.
In order to fa
From: Rik van Riel
Intel has an architectural guarantee that the TLB entry causing
a page fault gets invalidated automatically. This means
we should be able to drop the local TLB invalidation.
Because of the way other areas of the page fault code work,
chances are good that all x86 CPUs do this.
From: Rik van Riel
We need pte_present to return true for _PAGE_PROTNONE pages, to indicate that
the pte is associated with a page.
However, for TLB flushing purposes, we would like to know whether the pte
points to an actually accessible page. This allows us to skip remote TLB
flushes for page
On Thu, Nov 22, 2012 at 09:51:33AM +, Steven Whitehouse wrote:
> Hi,
>
> On Wed, 2012-11-21 at 16:41 -0600, Dave Kleikamp wrote:
> > Signed-off-by: Dave Kleikamp
> > Cc: Steven Whitehouse
> > Cc: cluster-de...@redhat.com
> > ---
> > fs/gfs2/file.c | 21 ++---
> > 1 file chan
From: Rik van Riel
The function ptep_set_access_flags() is only ever used to upgrade
access permissions to a page - i.e. they make it less restrictive.
That means the only negative side effect of not flushing remote
TLBs in this function is that other CPUs may incur spurious page
faults, if they
> diff --git a/include/uapi/linux/pci_regs.h b/include/uapi/linux/pci_regs.h
> index 20ae747..0cf8abb 100644
> --- a/include/uapi/linux/pci_regs.h
> +++ b/include/uapi/linux/pci_regs.h
> @@ -469,6 +469,7 @@
> #define PCI_EXP_LNKSTA_CLS 0x000f /* Current Link Speed */
> #define PCI_EXP_LNKSTA_
On 22.11.2012 10:03, Ilya Zykov wrote:
On 22.11.2012 8:29, Ilya Zykov wrote:
On 22.11.2012 4:47, andrew mcgregor wrote:
On 11/22/2012 at 10:39 AM, in message <50ad4a01.7060...@ilyx.ru>,
Ilya Zykov
wrote:
On 22.11.2012 1:30, Alan Cox wrote:
Function reset_buffer_flags() also invoked durin
On Thu, Nov 22, 2012 at 09:09:57AM +0100, walter harms wrote:
>
>
> Am 19.11.2012 22:34, schrieb Cyril Roelandt:
> > Found using the following semantic patch:
> >
> > @@
> > @@
> > spin_lock_irqsave(...);
> > ... when != spin_unlock_irqrestore(...);
> > * GFP_KERNEL
> >
> >
> > Signed-off-by:
On Wed, Nov 21, 2012 at 11:46 PM, Jeff Chua wrote:
> On Wed, Nov 21, 2012 at 2:09 AM, Jan Kara wrote:
>> I haven't heard about such problem so far. What filesystem are you using?
>
> I've tried ext2/ext3/ext4/reiserfs/btrfs ... all seems to be slower
> than before. Seems to be fs independent.
>
Regression 'tty: fix "IRQ45: nobody cared"'
Regression commit 7b292b4bf9a9d6098440d85616d6ca4c608b8304
Function reset_buffer_flags() also invoked during the ioctl(...,TCFLSH,..).
At the time of request we can have full buffers and throttled driver too.
If we don't unthrottle driver, we can get
Just to be clear, this is not fixed by Dave's patch to NR_FREE_PAGES
accounting.
I can still get 3.7-rc5 + Dave's fix to drop into an endless loop in
kswapd within a couple of minutes on my test box.
As described below, the bug comes from contradicting conditions in
balance_pgdat(), not an accoun
On Thu, Nov 22, 2012 at 08:48:07AM +0800, Jaegeuk Hanse wrote:
> On 11/22/2012 05:34 AM, Johannes Weiner wrote:
> >Hi,
> >
> >On Tue, Nov 20, 2012 at 07:25:00PM +0100, Jan Kara wrote:
> >>On Tue 20-11-12 09:42:42, metin d wrote:
> >>>I have two PostgreSQL databases named data-1 and data-2 that sit
On Thu, Nov 22, 2012 at 09:16:27PM +0800, Jaegeuk Hanse wrote:
> On 11/22/2012 09:09 AM, Johannes Weiner wrote:
> >On Thu, Nov 22, 2012 at 08:48:07AM +0800, Jaegeuk Hanse wrote:
> >>On 11/22/2012 05:34 AM, Johannes Weiner wrote:
> >>>Hi,
> >>>
> >>>On Tue, Nov 20, 2012 at 07:25:00PM +0100, Jan Kara
Hi,
On Tue, Nov 20, 2012 at 07:25:00PM +0100, Jan Kara wrote:
> On Tue 20-11-12 09:42:42, metin d wrote:
> > I have two PostgreSQL databases named data-1 and data-2 that sit on the
> > same machine. Both databases keep 40 GB of data, and the total memory
> > available on the machine is 68GB.
> >
Align IIM registers with the MX27 Reference Manual.
Signed-off-by: Fabio Estevam
---
Changes since v3:
- No changes
Changes since v2:
- No changes. Newly introduced on this series
arch/arm/mach-imx/iim.h | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/arch/arm/ma
On Thu, Nov 22, 2012 at 12:50:32PM +0800, Chen Gang wrote:
> Hello Arnd Bergmann, Greg Kroah-Hartman
>
> in drivers/char/hpet.c:1009
> I suggest to add check for hdp->hd_nirqs whether equal or larger than 32
> (HPET_MAX_TIMERS)
> the type of irqp->interrupt_count is u8 (include/acpi/a
kfree on a NULL pointer is a no-op.
Signed-off-by: Sachin Kamat
---
drivers/tty/vt/consolemap.c |6 ++
1 files changed, 2 insertions(+), 4 deletions(-)
diff --git a/drivers/tty/vt/consolemap.c b/drivers/tty/vt/consolemap.c
index 2aaa0c2..248381b 100644
--- a/drivers/tty/vt/consolemap.c
Do not reserve DMA pools on board file as this can be done via CMA.
The motivation for doing this is to allow to register the VPU driver via a
common
SoC file instead of per board.
Signed-off-by: Fabio Estevam
---
This applies against 20121115 linux-next.
Changes since v3:
- Remove all the DMA
On Thu, Nov 22, 2012 at 5:57 PM, Linus Walleij wrote:
> I have the same (limited by experience) opinion. Working sort of
> near som audio drivers I have understood that power sequencing
> is a big issue not only for things like this backlight example, but
> even more so in the area of audio to avo
On Wed, Nov 21, 2012 at 04:40:56PM -0600, Dave Kleikamp wrote:
> From: Zach Brown
>
> This uses the new kernel aio interface to process loopback IO by
> submitting concurrent direct aio. Previously loop's IO was serialized
> by synchronous processing in a thread.
>
> The aio operations specify
On Wed, Nov 21, 2012 at 7:10 AM, Ingo Molnar wrote:
>
> Because scalability slowdowns are often non-linear.
Only if you hold locks or have other non-cpu-private activity.
Which the vsyscall code really shouldn't have.
That said, it might be worth removing the "prefetchw(&mm->mmap_sem)"
from the
This patch implements the read_iter and write_iter file operations which
allow kernel code to initiate directIO. This allows the loop device to
read and write directly to the server, bypassing the page cache.
Signed-off-by: Dave Kleikamp
Cc: Zach Brown
Cc: Trond Myklebust
Cc: linux-...@vger.ker
Regression 'tty: fix "IRQ45: nobody cared"'
Regression commit 7b292b4bf9a9d6098440d85616d6ca4c608b8304
Function reset_buffer_flags() also invoked during the ioctl(...,TCFLSH,..).
At the time of request we can have full buffers and throttled driver too.
If we don't unthrottle driver, we can get
On Wed, Nov 21, 2012 at 05:47:55PM -0800, Darrick J. Wong wrote:
> On Thu, Nov 22, 2012 at 08:47:13AM +1100, NeilBrown wrote:
> > On Wed, 21 Nov 2012 22:33:33 +0100 Jan Kara wrote:
> >
> > > On Wed 21-11-12 13:13:19, Darrick J. Wong wrote:
> > > > On Wed, Nov 21, 2012 at 03:15:43AM +0100, Jan Kar
On Thu, Nov 22, 2012 at 02:08:43AM -0800, Nitin Gupta wrote:
> On 11/22/2012 12:31 AM, Minchan Kim wrote:
> >Hi Nitin,
> >
> >On Wed, Nov 21, 2012 at 10:06:33AM -0800, Nitin Gupta wrote:
> >>On 11/21/2012 12:37 AM, Minchan Kim wrote:
> >>>Hi alls,
> >>>
> >>>Today, I saw below complain of lockdep.
Commit-ID: 5e4bf1a55da976a5ed60901bb8801f1024ef9774
Gitweb: http://git.kernel.org/tip/5e4bf1a55da976a5ed60901bb8801f1024ef9774
Author: Ingo Molnar
AuthorDate: Tue, 20 Nov 2012 13:02:51 +0100
Committer: Ingo Molnar
CommitDate: Thu, 22 Nov 2012 21:52:06 +0100
x86/mm: Don't flush the TLB
On Thu, Nov 22, 2012 at 12:13:24PM +0100, Jerome Marchand wrote:
> On 11/21/2012 09:37 AM, Minchan Kim wrote:
> > Hi alls,
> >
> > Today, I saw below complain of lockdep.
> > As a matter of fact, I knew it long time ago but forgot that.
> > The reason lockdep complains is that now zram uses GFP_KE
Yinghai Lu writes:
> On Wed, Nov 21, 2012 at 11:50 AM, H. Peter Anvin wrote:
>> The comment is just plain wrong. It assumes you're loading an ELF file,
>> whereas in practice that is rarely true.
>>
>> This does explain why the poor ABI, though. A jump table at the
>> beginning would have been
Hi, list
Does MTD recognize vivi partition and can parse its partition table? It
seems that only RedBoot partion is supported for the physmap device, is
that true? Now I have vivi partions on a memory mapped NOR flash and want
to load a root image from that. What should I do?
--
woody
I can't go
Hi Prabhakar and others,
On Fri, Nov 16, 2012 at 08:15:02PM +0530, Prabhakar Lad wrote:
> From: Manjunath Hadli
>
> This patch set adds media controller based capture driver for
> DM365.
>
> This driver bases its design on Laurent Pinchart's Media Controller Design
> whose patches for Media Con
* fix failure seen on Zaurus corgi:
* sa1100-rtc sa1100-rtc: failed to find rtc clock source
* sa1100-rtc: probe of sa1100-rtc failed with error -2
Signed-off-by: Andrea Adami
---
arch/arm/mach-pxa/pxa25x.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/arch/arm/mach-px
Best,
J.
On Nov 21, 2012, at 4:37 PM, Jan Kara wrote:
> On Wed 21-11-12 13:29:01, Christoph Hellwig wrote:
>> On Wed, Nov 21, 2012 at 11:58:05AM -0500, Jeff Moyer wrote:
I'd like to use this as a vehicle to revisit how dio completions work.
>>>
>>> I don't like the sound of that. ;-)
On Thu, Nov 22, 2012 at 12:51:00PM +0100, Robert Jarzmik wrote:
> Dave Chinner writes:
>
> > We actually have an informal convention for formating filesystem
> > trace events, and that is to use the device number
> >
> >>
> >> > +),
> >> > +
> >> > +TP_printk("page=%p pfn=%lu
Hi Nitin,
Current next-20121115(I don't know why linux-next stay at the version. Is there
any problem on the tree? or Stephen go to holiday?) has a 37b51fdd(staging:
zram: factor-out zram_decompress_page() function) so this patch should be based
on that.
Thanks.
On Thu, Nov 22, 2012 at 02:41:13A
Hi Pavel,
> >>
> >> Now however, that "vsyscall" was effectively replaced by vdso, it
> >> creates a new problem for me and probably for anyone else who uses
> >> some form of checkpoint/restore:
> >
> > Oh, sorry, I can't help here. I can only add Cyrill and Pavel, they
> > seem to enjoy trying
On 22/11/2012 17:47, H. Peter Anvin wrote:
> The other thing that should be considered here is how utterly
> preposterous the notion of doing in-guest crash dumping is in a system
> that contains a hypervisor. The reason for kdump is that on bare metal
> there are no other options, but in a hyp
On Sun, 11 Nov 2012 20:42:48 +0900 Jaegeuk Kim wrote:
> 2012-11-11 (일), 00:55 +0300, Vyacheslav Dubeyko:
> > Hi,
> >
> > On Nov 10, 2012, at 9:33 PM, Martin Steigerwald wrote:
> >
> > [snip]
> > >
> > > merkaba:~> mkfs.f2fs /dev/sdb1
> > > Info: sector size = 512
> > > Info: total sectors = 40
On Tuesday 20 November 2012 03:12 PM, Guennadi Liakhovetski wrote:
Hi Laxman
On Tue, 20 Nov 2012, Laxman Dewangan wrote:
Here you actually need an offset within your register address space, so,
should be
+ max->lru_index[0] = pdata->dvs_def_state;
Yaah, seems some issue if vout_base
Hello Andrew, Russell,
The KDB/NMI core support has been merged into v3.7-rc1, so the only ARM
bits are pending now.
I addressed all the comments ~two month ago, and since then just resending
these patches. I know we're all busy, so no blaming. :) But then let's
pass this via -mm?
Short descript
Just move the macros into header file as we would want to use them for
KGDB FIQ entry code.
The following macros were moved:
- svc_entry
- usr_entry
- kuser_cmpxchg_check
- vector_stub
To make kuser_cmpxchg_check actually work across different files, we
also have to make kuser_cmpxchg64_fixu
The FIQ debugger may be used to debug situations when the kernel stuck
in uninterruptable sections, e.g. the kernel infinitely loops or
deadlocked in an interrupt or with interrupts disabled.
By default KGDB FIQ is disabled in runtime, but can be enabled with
kgdb_fiq.enable=1 kernel command line
If enabled, kernel will able to enter KGDB upon serial line activity on
UART ports.
Note that even with this patch and CONFIG_KGDB_FIQ is enabled, you still
need to pass kgdb_fiq.enable=1 kernel command line option, otherwise UART
will behave in a normal way.
By default UART0 is used, but this ca
Just a couple of calls to manage VIC FIQ routing. We'll use them for
KGDB FIQ support on ARM Versatile machines.
Signed-off-by: Anton Vorontsov
---
arch/arm/common/vic.c | 28
arch/arm/include/asm/hardware/vic.h | 2 ++
2 files changed, 30 insertions(+
On Fri, Nov 23, 2012 at 8:03 AM, Andrea Adami wrote:
> * fix failure seen on Zaurus corgi:
> * sa1100-rtc sa1100-rtc: failed to find rtc clock source
> * sa1100-rtc: probe of sa1100-rtc failed with error -2
>
> Signed-off-by: Andrea Adami
> ---
> arch/arm/mach-pxa/pxa25x.c |1 +
> 1 files ch
Hello Andrew, Russell,
These are small cleanups that I keep resending since Aug. Andrew, can you
please take them for the time being?
The rationale is the same:
During KDB FIQ patches review Russell mentioned that I should not
introduce another FIQ_START. It seems that in v3.6-rc the FIQ_START i
Just move the macros into header file as we would want to use them for
KGDB FIQ entry code.
The following macros were moved:
- svc_entry
- usr_entry
- kuser_cmpxchg_check
- vector_stub
To make kuser_cmpxchg_check actually work across different files, we
also have to make kuser_cmpxchg64_fixu
Hi Johannes,
Yes, problem was as you projected. I tried to make "active" data-2 pages by
manually reading them twice, and finally data-1 are got out of page cache.
We have large files in PostgreSQL and Hadoop that we sequentially scan over;
and try to fit our working set into total memory. So I
If enabled, kernel will able to enter KGDB upon serial line activity on
UART ports.
Note that even with this patch and CONFIG_KGDB_FIQ is enabled, you still
need to pass kgdb_fiq.enable=1 kernel command line option, otherwise UART
will behave in a normal way.
By default UART0 is used, but this ca
The FIQ debugger may be used to debug situations when the kernel stuck
in uninterruptable sections, e.g. the kernel infinitely loops or
deadlocked in an interrupt or with interrupts disabled.
By default KGDB FIQ is disabled in runtime, but can be enabled with
kgdb_fiq.enable=1 kernel command line
Just a couple of calls to manage VIC FIQ routing. We'll use them for
KGDB FIQ support on ARM Versatile machines.
Signed-off-by: Anton Vorontsov
---
arch/arm/common/vic.c | 28
arch/arm/include/asm/hardware/vic.h | 2 ++
2 files changed, 30 insertions(+
mach-rps registers FIQ controller with genirq, which makes no sense:
these FIQs cannot be routed to IRQs, so there is no need to register
it with genirq.
This effectively makes FIQ_START irrelevant.
Signed-off-by: Anton Vorontsov
---
arch/arm/mach-rpc/dma.c | 4 ++--
arch/arm/mac
The driver uses platform-specific mxc_set_irq_fiq() with the VIRQ cookie
passed to it, so it's pretty clear that the driver is absolutely sure
that the FIQ is routed via platform-specific IC, and that the cookie can
be used to mask/unmask FIQs. So, let's switch to the genirq routines,
since we're a
There are no users left, so these can be removed.
Signed-off-by: Anton Vorontsov
---
arch/arm/include/asm/fiq.h | 2 --
arch/arm/kernel/fiq.c | 15 ---
2 files changed, 17 deletions(-)
diff --git a/arch/arm/include/asm/fiq.h b/arch/arm/include/asm/fiq.h
index d493d0b..a293be4
RPC:
FIQ_START is irrelevant nowadays, the arch uses platform-specific
iomd_{,un}mask_fiq() calls.
OMAP1:
The only user of FIQs is MACH_AMS_DELTA, and in particular its
drivers/input/serio/ams_delta_serio.c driver. The driver does not rely on
the FIQ interrupts directly, instead it uses a "
Simply removes ugly #ifdefs from C code.
Signed-off-by: Anton Vorontsov
---
arch/arm/include/asm/mach/irq.h | 5 +
arch/arm/kernel/irq.c | 2 --
arch/arm/plat-mxc/avic.c| 2 --
arch/arm/plat-mxc/tzic.c| 2 --
arch/arm/plat-s3c24xx/irq.c | 2 --
5 files changed,
The return value is never checked, so we can turn show_fiq_list() into
returning void.
Signed-off-by: Anton Vorontsov
---
arch/arm/include/asm/mach/irq.h | 4 ++--
arch/arm/kernel/fiq.c | 4 +---
2 files changed, 3 insertions(+), 5 deletions(-)
diff --git a/arch/arm/include/asm/mach/i
The function only saves initial arch-specific "no FIQ" instruction, by
placing the code into set_fiq_handler() we can:
- Have less code and logic in the platform-specific files;
- Have the code that manages FIQ vector overwriting in one place, i.e.
don't spread the logic around.
p.s. Also, I no
The patch fixes the following sparse warnings:
CHECK arch/arm/kernel/fiq.c
arch/arm/kernel/fiq.c:71:6: warning: symbol 'show_fiq_list' was not declared.
Should it be static?
arch/arm/kernel/fiq.c:129:13: warning: symbol 'init_FIQ' was not declared.
Should it be static?
Signed-off-by: Anton
The driver uses platform-specific mxc_set_irq_fiq() with the VIRQ cookie
passed to it, so it's pretty clear that the driver is absolutely sure
that the FIQ is routed via platform-specific IC, and that the cookie can
be used to mask/unmask FIQs. So, let's switch to the genirq routines,
since we're a
We're about to remove FIQ_START mess, so move the platform-specific
detail inside platform-specific s3c24xx_set_fiq().
Signed-off-by: Anton Vorontsov
Acked-by: Kukjin Kim
---
arch/arm/plat-s3c24xx/irq.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/plat-s3c24xx/ir
Hi Andrew, Jason,
And yet another set that folks seem to be too busy to look into. :)
The rationale for the series is this:
This patchset implements "kiosk" mode for KDB debugger. The mode reduces
kdb features, so that it is no longer possible to leak sensitive data via
the debugger, and not pos
The struct member is never used in the code, so we can remove it.
We will introduce real flags soon by renaming cmd_repeat to cmd_flags.
Signed-off-by: Anton Vorontsov
---
kernel/debug/kdb/kdb_main.c| 1 -
kernel/debug/kdb/kdb_private.h | 1 -
2 files changed, 2 deletions(-)
diff --git a/k
We're about to add more options for command behaviour, so let's expand
the meaning of kdb_repeat_t.
So far we just do various renames, there should be no functional changes.
Signed-off-by: Anton Vorontsov
---
include/linux/kdb.h| 4 ++--
kernel/debug/kdb/kdb_main.c| 6 +++---
ke
The actual values of KDB_REPEAT_* enum values and overall logic stayed
the same, but we now treat the values as flags.
This makes it possible to add other flags and combine them, plus makes
the code a lot simpler and shorter. But functionality-wise, there should
be no changes.
Signed-off-by: Anto
Since we now treat KDB_REPEAT_* as flags, there is no need to
pass KDB_REPEAT_NONE. It's just the default behaviour when no
flags are specified.
Signed-off-by: Anton Vorontsov
---
include/linux/kdb.h | 1 -
kernel/debug/kdb/kdb_bp.c | 6 ++---
kernel/debug/kdb/kdb_main.c | 61 +++
This patch introduces two new flags: KDB_SAFE, denotes a safe command,
and KDB_SAFE_NO_ARGS, denotes a safe command when used without arguments.
The word "safe" here used in the sense that the commands cannot be
used to leak sensitive data from the memory, and cannot be used
to change program flow
By issuing 'echo 1 > /sys/module/kdb/parameters/kiosk' or
booting with kdb.kiosk=1 kernel command line option, one can still have
a somewhat usable debugging facility, but not fearing that the
debugger can be used to easily gain root access or dump sensitive data.
Without the kiosk mode, obtaining
We're about to add more options for commands behaviour, so let's give
a more generic name to the low-level kdb command registration function.
There are just various renames, no functional changes.
Signed-off-by: Anton Vorontsov
---
include/linux/kdb.h | 10 +++---
kernel/debug/kdb/kdb_b
On Wed, 21 Nov 2012, Tony Lindgren wrote:
> * Omar Ramirez Luna [121119 17:08]:
> > This prevents hwmod _enable_clocks...omap2_dflt_clk_enable path
> > from enabling modulemode inside CLKCTRL using its clk->enable_reg
> > field. Instead is left to _omap4_enable_module though soc_ops, as
> > the o
Daniel Kiper writes:
> On Tue, Nov 20, 2012 at 08:40:39AM -0800, ebied...@xmission.com wrote:
>> Daniel Kiper writes:
>>
>> > Some kexec/kdump implementations (e.g. Xen PVOPS) could not use default
>> > functions or require some changes in behavior of kexec/kdump generic code.
>> > To cope with
于 2012年11月23日 02:24, Greg KH 写道:
> On Thu, Nov 22, 2012 at 12:50:32PM +0800, Chen Gang wrote:
>> Hello Arnd Bergmann, Greg Kroah-Hartman
>>
>> in drivers/char/hpet.c:1009
>> I suggest to add check for hdp->hd_nirqs whether equal or larger than 32
>> (HPET_MAX_TIMERS)
>> the type of irq
On Tue, Nov 20, 2012 at 07:57:48AM +0800, Xiao Guangrong wrote:
> The current reexecute_instruction can not well detect the failed instruction
> emulation. It allows guest to retry all the instructions except it accesses
> on error pfn.
>
> For example, these cases can not be detected:
> - for tdp
On Thu, 2012-11-22 at 11:06 +, Alan Cox wrote:
> > --- a/drivers/tty/serial/ifx6x60.c
> > +++ b/drivers/tty/serial/ifx6x60.c
> > @@ -552,7 +552,10 @@ static void ifx_port_shutdown(struct tty_port
> > *port) container_of(port, struct ifx_spi_device, tty_port);
> >
> > mrdy_set_low(ifx_dev)
When shut down SPI port, it's possible that MRDY has been asserted and a SPI
timer was activated waiting for SRDY assert, in the case, it needs to delete
this timer.
Signed-off-by: Chen Jun
Signed-off-by: channing
---
drivers/tty/serial/ifx6x60.c |1 +
1 files changed, 1 insertions(+), 0 d
Implement list_voltage for fixed regulators, otherwise
regulator_is_supported_voltage() returns 0.
Signed-off-by: Axel Lin
---
drivers/regulator/tps80031-regulator.c |6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/drivers/regulator/tps80031-regulator.c
b/drivers/regu
This patch cause boot hang on our SNB EP 2 sockets machine with some
segmentation fault.
revert it recovers booting.
[8.290147] Freeing unused kernel memory: 1264k freed
[8.306140] Freeing unused kernel memory: 1592k freed
[8.342668] init[250]: segfault at 20da510 ip 0
On 11/22/2012 11:26 PM, Fengguang Wu wrote:
Hi Jaegeuk,
Sorry for the delay. I'm traveling these days..
On Wed, Nov 21, 2012 at 05:42:33PM +0800, Jaegeuk Hanse wrote:
On 11/21/2012 05:02 PM, Fengguang Wu wrote:
On Wed, Nov 21, 2012 at 04:34:40PM +0800, Jaegeuk Hanse wrote:
Cc Fengguang Wu.
Ok... that *sort of* makes sense, but also underscores how utterly different
this is from a normal kexec.
Andrew Cooper wrote:
>On 22/11/2012 17:47, H. Peter Anvin wrote:
>> The other thing that should be considered here is how utterly
>> preposterous the notion of doing in-guest crash dumping
I still don't really get why it can't be isolated from dom0, which would make
more sense to me, even for a Xen crash.
Andrew Cooper wrote:
>On 22/11/2012 17:47, H. Peter Anvin wrote:
>> The other thing that should be considered here is how utterly
>> preposterous the notion of doing in-guest c
On Thu, Nov 22, 2012 at 10:11:06AM +0800, Qing Xu wrote:
> - int i, regulator_idx;
> + int i;
> + int regulator_idx = 0;
This sort of fix is rarely good without some analysis as to why this is
a sensible initialisation to do, just unconditionally initialising may
be masking a real iss
On Thu, Nov 22, 2012 at 09:57:22AM +0100, Linus Walleij wrote:
> Is it correct to assume that this library will be useful also for ALSA
> SoC type of devices?
ASoC has facilities for autogenerating the bulk of the sequences which
with modern devices is all that you really need.
signature.asc
De
Bartlomiej Zolnierkiewicz wrote:
>
>
> Hi Kukjin,
>
Hi Bart,
> Could you also apply this patch?
>
Yeah, looks good to me :-)
Will apply, thanks.
Best regards,
Kgene.
--
Kukjin Kim , Senior Engineer,
SW Solution Development Team, Samsung Electronics Co., Ltd.
>
>
> From: Bartlomiej Zolnierk
On 23/11/2012 01:38, H. Peter Anvin wrote:
> I still don't really get why it can't be isolated from dom0, which would make
> more sense to me, even for a Xen crash.
>
The crash region (as specified by crashkernel= on the Xen command line)
is isolated from dom0.
dom0 (using the kexec utility etc)
On Thu, Nov 22, 2012 at 02:05:40PM +, Lee Jones wrote:
> On Thu, 20 Sep 2012, Lee Jones wrote:
> > > > Can we have some closure on this patch please, as it's blocking the
> > > > patch-set? I'm fairly sure the patch is doing the correct thing, as
> > > > seconded by Mark.
> > > I still don't
On 11/21/2012 02:25 AM, Jan Kara wrote:
On Tue 20-11-12 09:42:42, metin d wrote:
I have two PostgreSQL databases named data-1 and data-2 that sit on the
same machine. Both databases keep 40 GB of data, and the total memory
available on the machine is 68GB.
I started data-1 and data-2, and ran s
On 22/11/12 22:56, Sethi Varun-B16395 wrote:
-Original Message-
From: linux-kernel-ow...@vger.kernel.org [mailto:linux-kernel-
ow...@vger.kernel.org] On Behalf Of Alex Williamson
Sent: Tuesday, November 20, 2012 11:50 PM
To: Alexey Kardashevskiy
Cc: Benjamin Herrenschmidt; Paul Mackerr
901 - 1000 of 1096 matches
Mail list logo
