Mike Kravetz 96cd5b0856 [PATCH] ppc64: POWER 4 fails to boot with NUMA ... If CONFIG_NUMA is set, some POWER 4 systems will fail to boot. This is because of special processing needed to handle invalid node IDs (0xffff) on POWER 4. My previous patch to handle memory 'holes' within nodes forgot to add this special case for POWER 4 in one place. In reality, I'm not sure that configuring the kernel for NUMA on POWER 4 makes much sense. Are there POWER 4 based systems with NUMA characteristics that are presented by the firmware? But, distros want one kernel for all systems so NUMA is on by default in their kernels. The patch handles those cases. Signed-off-by: Mike Kravetz <kravetz@us.ibm.com> Signed-off-by: Paul Mackerras <paulus@samba.org> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>		2005-08-01 21:38:01 -07:00
..
alpha
arm
arm26
cris
frv
h8300
i386	[PATCH] transmeta: CONFIG_PROC_FS=n build fix	2005-08-01 21:38:00 -07:00
ia64	[PATCH] remove sys_set_zone_reclaim()	2005-08-01 10:03:56 -07:00
m32r	[PATCH] m32r: Fix local-timer event handling	2005-08-01 21:37:59 -07:00
m68k
m68knommu
mips
parisc
ppc	[PATCH] ppc32: add bamboo defconfig	2005-08-01 19:14:01 -07:00
ppc64	[PATCH] ppc64: POWER 4 fails to boot with NUMA	2005-08-01 21:38:01 -07:00
s390	[PATCH] s390: ioprio & inotify system calls.	2005-08-01 21:37:59 -07:00
sh
sh64
sparc
sparc64
um
v850
x86_64
xtensa