Commit abf917cd91cb ("cputime: Generic on-demand virtual cputime
accounting") inadvertantly changed the default CPU_ACCOUNTING config
for PPC64. Repair that.
Signed-off-by: Stephen Rothwell
---
init/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/init/Kconfig b/init/
#x27;t know if that was deliberate, but it was suprising. I noticed
> when this patch entered next-20130207.
I suspect that this is caused by the changes to init/Kconfig:
diff --git a/init/Kconfig b/init/Kconfig
index be8b7f5..a05f843 100644
--- a/init/Kconfig
+++ b/init/Kconfig
@@ -326,6 +326,9
before/after this patch)
@@ -119,8 +120,8 @@
#
# CPU/Task time and stats accounting
#
-# CONFIG_TICK_CPU_ACCOUNTING is not set
-CONFIG_VIRT_CPU_ACCOUNTING=y
+CONFIG_TICK_CPU_ACCOUNTING=y
+# CONFIG_VIRT_CPU_ACCOUNTING_NATIVE is not set
# CONFIG_BSD_PROCESS_ACCT is not set
CONFIG_TASKSTATS=y
CO
On Thu, 2013-01-31 at 20:04 -0600, Jason Wessel wrote:
> > diff --git a/arch/powerpc/kernel/kgdb.c b/arch/powerpc/kernel/kgdb.c
> > index 8747447..5ca82cd 100644
> > --- a/arch/powerpc/kernel/kgdb.c
> > +++ b/arch/powerpc/kernel/kgdb.c
> > @@ -154,12 +154,12 @@ static int kgdb_handle_breakpoint(st
On Fri, 2013-02-08 at 01:09 +0200, Aaro Koskinen wrote:
>
> I get this BUG when enabling DEBUG_PAGEALLOC with 3.8-rc6+
> (6bacaa9ddacb71c691d32c678d37bc59ffc71fac) on G5 PPC.
>
> It seems to be fairly reproducible - I saw it 3 times, soon after
> booting
> while running a compilation job on ext3
From: Ian Munsie
This patch adds support for enabling and context switching the Target
Address Register in Power8. The TAR is a new special purpose register
that can be used for computed branches with the bctar[l] (branch
conditional to TAR) instruction in the same manner as the count and link
re
On 02/07/2013 02:07:00 AM, Zhao Chenhui wrote:
The Freescale implementation of the MPIC only allows a single CPU
destination for non-IPI interrupts. Test the flag MPIC_SINGLE_DEST_CPU
to check if the Destination registers should be set.
This prevents more than one bit is set at secondary process
On 02/07/2013 06:19:25 AM, Thomas Waldecker wrote:
Hi Scott,
I measured the power consumption of the whole system on the tqmp2020
( http://tq-group.com/tqmp2020 )
with a QorIQ P2020.
Kernel:
root@generic-powerpc-e500v2:/sys/power# uname -a
Linux generic-powerpc-e500v2 3.7.0-rc8-4-g6e9341
2013/2/7 Li Zhong :
> On Thu, 2013-02-07 at 01:29 +0100, Frederic Weisbecker wrote:
>> In x86-64, schedule_user() and do_notify_resume() can be called before
>> syscall_trace_leave(). As a result we may be entering
>> syscall_trace_leave() in user mode (from a context tracking POV). To
>> fix this
Hi Scott,
I measured the power consumption of the whole system on the tqmp2020 (
http://tq-group.com/tqmp2020 )
with a QorIQ P2020.
Kernel:
root@generic-powerpc-e500v2:/sys/power# uname -a
Linux generic-powerpc-e500v2 3.7.0-rc8-4-g6e93414 #4 SMP Tue Dec 11
08:53:23 CET 2012 ppc GNU/Linux
ro
On Thu, 2013-02-07 at 01:29 +0100, Frederic Weisbecker wrote:
> 2013/2/1 Li Zhong :
> > This is the syscall slow path hooks for context tracking subsystem,
> > corresponding to
> > [PATCH] x86: Syscall hooks for userspace RCU extended QS
> > commit bf5a3c13b939813d28ce26c01425054c740d6731
> >
> >
The Freescale implementation of the MPIC only allows a single CPU
destination for non-IPI interrupts. Test the flag MPIC_SINGLE_DEST_CPU
to check if the Destination registers should be set.
This prevents more than one bit is set at secondary processors
initilizing time if the flag MPIC_SINGLE_DEST
12 matches
Mail list logo