Pull release into acpica branch

1 files changed, 93 insertions, 40 deletions

diff --git a/arch/ia64/Kconfig b/arch/ia64/Kconfig
index 945c15a0722b..b76ce1fe2e7f 100644
--- a/arch/ia64/Kconfig
+++ b/arch/ia64/Kconfig
@@ -26,6 +26,10 @@ config MMU
         bool
         default y
 
+config SWIOTLB
+       bool
+       default y
+
 config RWSEM_XCHGADD_ALGORITHM
         bool
         default y
@@ -54,6 +58,10 @@ config IA64_UNCACHED_ALLOCATOR
         bool
         select GENERIC_ALLOCATOR
 
+config ZONE_DMA_IS_DMA32
+        bool
+        default y
+
 choice
         prompt "System type"
         default IA64_GENERIC
@@ -63,8 +71,6 @@ config IA64_GENERIC
         select ACPI
         select NUMA
         select ACPI_NUMA
-        select VIRTUAL_MEM_MAP
-        select DISCONTIGMEM
         help
           This selects the system type of your hardware.  A "generic" kernel
           will run on any supported IA-64 system.  However, if you configure
@@ -162,6 +168,19 @@ config IA64_PAGE_SIZE_64KB
 
 endchoice
 
+choice
+        prompt "Page Table Levels"
+        default PGTABLE_3
+
+config PGTABLE_3
+        bool "3 Levels"
+
+config PGTABLE_4
+        depends on !IA64_PAGE_SIZE_64KB
+        bool "4 Levels"
+
+endchoice
+
 source kernel/Kconfig.hz
 
 config IA64_BRL_EMU
@@ -176,40 +195,6 @@ config IA64_L1_CACHE_SHIFT
         default "6" if ITANIUM
 
 # align cache-sensitive data to 64 bytes
-config NUMA
-        bool "NUMA support"
-        depends on !IA64_HP_SIM
-        default y if IA64_SGI_SN2
-        select ACPI_NUMA
-        help
-          Say Y to compile the kernel to support NUMA (Non-Uniform Memory
-          Access).  This option is for configuring high-end multiprocessor
-          server systems.  If in doubt, say N.
-
-config VIRTUAL_MEM_MAP
-        bool "Virtual mem map"
-        default y if !IA64_HP_SIM
-        help
-          Say Y to compile the kernel with support for a virtual mem map.
-          This code also only takes effect if a memory hole of greater than
-          1 Gb is found during boot.  You must turn this option on if you
-          require the DISCONTIGMEM option for your machine. If you are
-          unsure, say Y.
-
-config HOLES_IN_ZONE
-        bool
-        default y if VIRTUAL_MEM_MAP
-
-config ARCH_DISCONTIGMEM_ENABLE
-        bool "Discontiguous memory support"
-        depends on (IA64_DIG || IA64_SGI_SN2 || IA64_GENERIC || IA64_HP_ZX1 || IA64_HP_ZX1_SWIOTLB) && NUMA && VIRTUAL_MEM_MAP
-        default y if (IA64_SGI_SN2 || IA64_GENERIC) && NUMA
-        help
-          Say Y to support efficient handling of discontiguous physical memory,
-          for architectures which are either NUMA (Non-Uniform Memory Access)
-          or have huge holes in the physical address space for other reasons.
-          See <file:Documentation/vm/numa> for more.
-
 config IA64_CYCLONE
         bool "Cyclone (EXA) Time Source support"
         help
@@ -223,6 +208,7 @@ config IOSAPIC
 
 config IA64_SGI_SN_XP
         tristate "Support communication between SGI SSIs"
+        depends on IA64_GENERIC || IA64_SGI_SN2
         select IA64_UNCACHED_ALLOCATOR
         help
           An SGI machine can be divided into multiple Single System
@@ -232,8 +218,10 @@ config IA64_SGI_SN_XP
           based on a network adapter and DMA messaging.
 
 config FORCE_MAX_ZONEORDER
-        int
-        default "18"
+        int "MAX_ORDER (11 - 17)"  if !HUGETLB_PAGE
+        range 11 17  if !HUGETLB_PAGE
+        default "17" if HUGETLB_PAGE
+        default "11"
 
 config SMP
         bool "Symmetric multi-processing support"
@@ -254,8 +242,8 @@ config SMP
           If you don't know what to do here, say N.
 
 config NR_CPUS
-        int "Maximum number of CPUs (2-512)"
-        range 2 512
+        int "Maximum number of CPUs (2-1024)"
+        range 2 1024
         depends on SMP
         default "64"
         help
@@ -298,6 +286,58 @@ config PREEMPT
 
 source "mm/Kconfig"
 
+config ARCH_SELECT_MEMORY_MODEL
+        def_bool y
+
+config ARCH_DISCONTIGMEM_ENABLE
+        def_bool y
+        help
+          Say Y to support efficient handling of discontiguous physical memory,
+          for architectures which are either NUMA (Non-Uniform Memory Access)
+          or have huge holes in the physical address space for other reasons.
+          See <file:Documentation/vm/numa> for more.
+
+config ARCH_FLATMEM_ENABLE
+        def_bool y
+
+config ARCH_SPARSEMEM_ENABLE
+        def_bool y
+        depends on ARCH_DISCONTIGMEM_ENABLE
+
+config ARCH_DISCONTIGMEM_DEFAULT
+        def_bool y if (IA64_SGI_SN2 || IA64_GENERIC || IA64_HP_ZX1 || IA64_HP_ZX1_SWIOTLB)
+        depends on ARCH_DISCONTIGMEM_ENABLE
+
+config NUMA
+        bool "NUMA support"
+        depends on !IA64_HP_SIM && !FLATMEM
+        default y if IA64_SGI_SN2
+        help
+          Say Y to compile the kernel to support NUMA (Non-Uniform Memory
+          Access).  This option is for configuring high-end multiprocessor
+          server systems.  If in doubt, say N.
+
+# VIRTUAL_MEM_MAP and FLAT_NODE_MEM_MAP are functionally equivalent.
+# VIRTUAL_MEM_MAP has been retained for historical reasons.
+config VIRTUAL_MEM_MAP
+        bool "Virtual mem map"
+        depends on !SPARSEMEM
+        default y if !IA64_HP_SIM
+        help
+          Say Y to compile the kernel with support for a virtual mem map.
+          This code also only takes effect if a memory hole of greater than
+          1 Gb is found during boot.  You must turn this option on if you
+          require the DISCONTIGMEM option for your machine. If you are
+          unsure, say Y.
+
+config HOLES_IN_ZONE
+        bool
+        default y if VIRTUAL_MEM_MAP
+
+config HAVE_ARCH_EARLY_PFN_TO_NID
+        def_bool y
+        depends on NEED_MULTIPLE_NODES
+
 config IA32_SUPPORT
         bool "Support for Linux/x86 binaries"
         help
@@ -404,8 +444,21 @@ config GENERIC_PENDING_IRQ
 
 source "arch/ia64/hp/sim/Kconfig"
 
+menu "Instrumentation Support"
+        depends on EXPERIMENTAL
+
 source "arch/ia64/oprofile/Kconfig"
 
+config KPROBES
+        bool "Kprobes (EXPERIMENTAL)"
+        help
+          Kprobes allows you to trap at almost any kernel address and
+          execute a callback function.  register_kprobe() establishes
+          a probepoint and specifies the callback.  Kprobes is useful
+          for kernel debugging, non-intrusive instrumentation and testing.
+          If in doubt, say "N".
+endmenu
+
 source "arch/ia64/Kconfig.debug"
 
 source "security/Kconfig"