linux-stable/arch/ppc64
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
..
boot [PATCH] remove duplicate printf in arch/ppc64/boot/main.c 2005-06-28 21:01:46 +10:00
configs [PATCH] ppc64: update defconfigs 2005-07-27 16:25:57 -07:00
kernel [PATCH] ppc64: Fix CONFIG_ALTIVEC not set 2005-08-01 19:14:00 -07:00
lib [PATCH] ppc64 iSeries: allow build with no PCI 2005-06-21 18:46:31 -07:00
mm [PATCH] ppc64: POWER 4 fails to boot with NUMA 2005-08-01 21:38:01 -07:00
oprofile Linux-2.6.12-rc2 2005-04-16 15:20:36 -07:00
xmon [PATCH] ppc32: Kill embedded system.map, use kallsyms 2005-06-21 18:46:26 -07:00
defconfig [PATCH] ppc64: update defconfigs 2005-07-27 16:25:57 -07:00
Kconfig [PATCH] ppc/ppc64: use Kconfig.hz 2005-07-27 16:25:55 -07:00
Kconfig.debug [PATCH] ppc64: add missing Kconfig help text 2005-05-05 16:36:32 -07:00
Makefile [PATCH] ppc64: add BPA platform type 2005-06-23 09:43:37 +10:00