Re: 3.5+: yaboot, Invalid memory access

2012-09-03 Thread Michael Ellerman
On Mon, 2012-09-03 at 23:18 -0700, Christian Kujau wrote: > On Mon, 30 Jul 2012 at 22:46, Christian Kujau wrote: > > when trying to upgrade from 3.5 (final) to today's git checkout from > > Linus' tree, yaboot cannot boot and the following is printed: > > > > [...] > > returning from prom_ini

Re: 3.5+: yaboot, Invalid memory access

2012-09-03 Thread Christian Kujau
On Mon, 30 Jul 2012 at 22:46, Christian Kujau wrote: > when trying to upgrade from 3.5 (final) to today's git checkout from > Linus' tree, yaboot cannot boot and the following is printed: > > [...] > returning from prom_init > Invalid memory access at %SRR0: 00c62fd4 %SRR1: 3030 Final

Re: [RFC v8 PATCH 13/20] memory-hotplug: check page type in get_page_bootmem

2012-09-03 Thread Wen Congyang
Hi, isimatu-san At 09/01/2012 05:30 AM, Andrew Morton Wrote: > On Tue, 28 Aug 2012 18:00:20 +0800 > we...@cn.fujitsu.com wrote: > >> From: Yasuaki Ishimatsu >> >> There is a possibility that get_page_bootmem() is called to the same page >> many >> times. So when get_page_bootmem is called to th

[PATCH 4/4] powerpc: Restore correct DSCR in context switch

2012-09-03 Thread Anton Blanchard
During a context switch we always restore the per thread DSCR value. If we aren't doing explicit DSCR management (ie thread.dscr_inherit == 0) and the default DSCR changed while the process has been sleeping we end up with the wrong value. Check thread.dscr_inherit and select the default DSCR or

[PATCH 3/4] powerpc: Fix DSCR inheritance in copy_thread()

2012-09-03 Thread Anton Blanchard
If the default DSCR is non zero we set thread.dscr_inherit in copy_thread() meaning the new thread and all its children will ignore future updates to the default DSCR. This is not intended and is a change in behaviour that a number of our users have hit. We just need to inherit thread.dscr and th

[PATCH 2/4] powerpc: Keep thread.dscr and thread.dscr_inherit in sync

2012-09-03 Thread Anton Blanchard
When we update the DSCR either via emulation of mtspr(DSCR) or via a change to dscr_default in sysfs we don't update thread.dscr. We will eventually update it at context switch time but there is a period where thread.dscr is incorrect. If we fork at this point we will copy the old value of thread

[PATCH 1/4] powerpc: Update DSCR on all CPUs when writing sysfs dscr_default

2012-09-03 Thread Anton Blanchard
Writing to dscr_default in sysfs doesn't actually change the DSCR - we rely on a context switch on each CPU to do the work. There is no guarantee we will get a context switch in a reasonable amount of time so fire off an IPI to force an immediate change. This issue was found with the following te

[PATCH 2/2] powerpc/pci: Use PCIe IP block revision register instead of compatible

2012-09-03 Thread Roy Zang
Freescale PCIe IP block revision bigger than rev2.2 will also need redefine the sequence of inbound windows. So change to use IP block revision instead of compatible for the judgment. Signed-off-by: Roy Zang --- arch/powerpc/sysdev/fsl_pci.c | 14 -- 1 files changed, 8 insertions(

[PATCH 1/2] powerpc/pci: Add IP revision register define for Freescale PCIe controller

2012-09-03 Thread Roy Zang
Signed-off-by: Roy Zang --- arch/powerpc/sysdev/fsl_pci.h |5 - 1 files changed, 4 insertions(+), 1 deletions(-) diff --git a/arch/powerpc/sysdev/fsl_pci.h b/arch/powerpc/sysdev/fsl_pci.h index baa0fd1..7192932 100644 --- a/arch/powerpc/sysdev/fsl_pci.h +++ b/arch/powerpc/sysdev/fsl_pci.

Re: [RFC v8 PATCH 08/20] memory-hotplug: remove /sys/firmware/memmap/X sysfs

2012-09-03 Thread Wen Congyang
At 09/01/2012 05:06 AM, Andrew Morton Wrote: > On Tue, 28 Aug 2012 18:00:15 +0800 > we...@cn.fujitsu.com wrote: > >> From: Yasuaki Ishimatsu >> >> When (hot)adding memory into system, /sys/firmware/memmap/X/{end, start, >> type} >> sysfs files are created. But there is no code to remove these fi