There is nothing inherent in HIGHMEM64G required for CONFIG_NUMA to work. It
just limits potential testing coverage so remove the limitation.
Signed-off-by: Mel Gorman <[EMAIL PROTECTED]>
---
arch/x86/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff -rup -X /usr/src/patchset-0.6/bin//dontdiff
linux-2.6.24-rc8-fix-numa-boot/arch/x86/Kconfig
linux-2.6.24-rc8-005_non64GB/arch/x86/Kconfig
--- linux-2.6.24-rc8-fix-numa-boot/arch/x86/Kconfig 2008-01-16
04:22:48.000000000 +0000
+++ linux-2.6.24-rc8-005_non64GB/arch/x86/Kconfig 2008-01-17
18:22:26.000000000 +0000
@@ -817,7 +817,7 @@ config X86_PAE
config NUMA
bool "Numa Memory Allocation and Scheduler Support (EXPERIMENTAL)"
depends on SMP
- depends on X86_64 || (X86_32 && HIGHMEM64G && (X86_NUMAQ || (X86_SUMMIT
|| X86_GENERICARCH) && ACPI) && EXPERIMENTAL)
+ depends on X86_64 || (X86_32 && (X86_NUMAQ || (X86_SUMMIT ||
X86_GENERICARCH) && ACPI) && EXPERIMENTAL)
default n if X86_PC
default y if (X86_NUMAQ || X86_SUMMIT)
help
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
