linux/arch/ppc64/mm
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
..
fault.c
hash_low.S [PATCH] ppc64: kill bitfields in ppc64 hash code 2005-07-13 11:25:25 -07:00
hash_native.c [PATCH] ppc64: kill bitfields in ppc64 hash code 2005-07-13 11:25:25 -07:00
hash_utils.c [PATCH] ppc64: kill bitfields in ppc64 hash code 2005-07-13 11:25:25 -07:00
hugetlbpage.c [PATCH] ppc64: kill bitfields in ppc64 hash code 2005-07-13 11:25:25 -07:00
imalloc.c
init.c [PATCH] ppc64: kill bitfields in ppc64 hash code 2005-07-13 11:25:25 -07:00
Makefile
mmap.c
numa.c [PATCH] ppc64: POWER 4 fails to boot with NUMA 2005-08-01 21:38:01 -07:00
slb_low.S
slb.c
stab.c [PATCH] ppc64: dynamically allocate segment tables 2005-07-27 16:25:58 -07:00
tlb.c