2 # For a description of the syntax of this configuration file,
3 # see Documentation/kbuild/kconfig-language.txt.
6 mainmenu "IA-64 Linux Kernel Configuration"
10 menu "Processor type and features"
16 The Itanium Processor Family is Intel's 64-bit successor to
17 the 32-bit X86 line. The IA-64 Linux project has a home
18 page at <http://www.linuxia64.org/> and a mailing list at
19 <linux-ia64@vger.kernel.org>.
33 config RWSEM_XCHGADD_ALGORITHM
37 config GENERIC_CALIBRATE_DELAY
41 config TIME_INTERPOLATION
53 config SCHED_NO_NO_OMIT_FRAME_POINTER
57 config IA64_UNCACHED_ALLOCATOR
59 select GENERIC_ALLOCATOR
75 This selects the system type of your hardware. A "generic" kernel
76 will run on any supported IA-64 system. However, if you configure
77 a kernel for your specific system, it will be faster and smaller.
79 generic For any supported IA-64 system
80 DIG-compliant For DIG ("Developer's Interface Guide") compliant systems
81 HP-zx1/sx1000 For HP systems
82 HP-zx1/sx1000+swiotlb For HP systems with (broken) DMA-constrained devices.
83 SGI-SN2 For SGI Altix systems
84 Ski-simulator For the HP simulator <http://www.hpl.hp.com/research/linux/ski/>
86 If you don't know what to do, choose "generic".
94 Build a kernel that runs on HP zx1 and sx1000 systems. This adds
95 support for the HP I/O MMU.
97 config IA64_HP_ZX1_SWIOTLB
98 bool "HP-zx1/sx1000 with software I/O TLB"
100 Build a kernel that runs on HP zx1 and sx1000 systems even when they
101 have broken PCI devices which cannot DMA to full 32 bits. Apart
102 from support for the HP I/O MMU, this includes support for the software
103 I/O TLB, which allows supporting the broken devices at the expense of
104 wasting some kernel memory (about 2MB by default).
109 Selecting this option will optimize the kernel for use on sn2 based
110 systems, but the resulting kernel binary will not run on other
111 types of ia64 systems. If you have an SGI Altix system, it's safe
112 to select this option. If in doubt, select ia64 generic support
121 prompt "Processor type"
127 Select your IA-64 processor type. The default is Itanium.
128 This choice is safe for all IA-64 systems, but may not perform
129 optimally on systems with, say, Itanium 2 or newer processors.
134 Select this to configure for an Itanium 2 (McKinley) processor.
139 prompt "Kernel page size"
140 default IA64_PAGE_SIZE_16KB
142 config IA64_PAGE_SIZE_4KB
145 This lets you select the page size of the kernel. For best IA-64
146 performance, a page size of 8KB or 16KB is recommended. For best
147 IA-32 compatibility, a page size of 4KB should be selected (the vast
148 majority of IA-32 binaries work perfectly fine with a larger page
149 size). For Itanium 2 or newer systems, a page size of 64KB can also
152 4KB For best IA-32 compatibility
153 8KB For best IA-64 performance
154 16KB For best IA-64 performance
155 64KB Requires Itanium 2 or newer processor.
157 If you don't know what to do, choose 16KB.
159 config IA64_PAGE_SIZE_8KB
162 config IA64_PAGE_SIZE_16KB
165 config IA64_PAGE_SIZE_64KB
172 prompt "Page Table Levels"
179 depends on !IA64_PAGE_SIZE_64KB
184 source kernel/Kconfig.hz
191 # align cache-sensitive data to 128 bytes
192 config IA64_L1_CACHE_SHIFT
194 default "7" if MCKINLEY
195 default "6" if ITANIUM
197 # align cache-sensitive data to 64 bytes
199 bool "Cyclone (EXA) Time Source support"
201 Say Y here to enable support for IBM EXA Cyclone time source.
202 If you're unsure, answer N.
206 depends on !IA64_HP_SIM
209 config IA64_SGI_SN_XP
210 tristate "Support communication between SGI SSIs"
211 depends on IA64_GENERIC || IA64_SGI_SN2
212 select IA64_UNCACHED_ALLOCATOR
214 An SGI machine can be divided into multiple Single System
215 Images which act independently of each other and have
216 hardware based memory protection from the others. Enabling
217 this feature will allow for direct communication between SSIs
218 based on a network adapter and DMA messaging.
220 config FORCE_MAX_ZONEORDER
221 int "MAX_ORDER (11 - 17)" if !HUGETLB_PAGE
222 range 11 17 if !HUGETLB_PAGE
223 default "17" if HUGETLB_PAGE
227 bool "Symmetric multi-processing support"
229 This enables support for systems with more than one CPU. If you have
230 a system with only one CPU, say N. If you have a system with more
233 If you say N here, the kernel will run on single and multiprocessor
234 systems, but will use only one CPU of a multiprocessor system. If
235 you say Y here, the kernel will run on many, but not all,
236 single processor systems. On a single processor system, the kernel
237 will run faster if you say N here.
239 See also the <file:Documentation/smp.txt> and the SMP-HOWTO
240 available at <http://www.tldp.org/docs.html#howto>.
242 If you don't know what to do here, say N.
245 int "Maximum number of CPUs (2-1024)"
250 You should set this to the number of CPUs in your system, but
251 keep in mind that a kernel compiled for, e.g., 2 CPUs will boot but
252 only use 2 CPUs on a >2 CPU system. Setting this to a value larger
253 than 64 will cause the use of a CPU mask array, causing a small
257 bool "Support for hot-pluggable CPUs (EXPERIMENTAL)"
258 depends on SMP && EXPERIMENTAL
262 Say Y here to experiment with turning CPUs off and on. CPUs
263 can be controlled through /sys/devices/system/cpu/cpu#.
264 Say N if you want to disable CPU hotplug.
267 bool "SMT scheduler support"
271 Improves the CPU scheduler's decision making when dealing with
272 Intel IA64 chips with MultiThreading at a cost of slightly increased
273 overhead in some places. If unsure say N here.
275 config PERMIT_BSP_REMOVE
276 bool "Support removal of Bootstrap Processor"
277 depends on HOTPLUG_CPU
280 Say Y here if your platform SAL will support removal of BSP with HOTPLUG_CPU
283 config FORCE_CPEI_RETARGET
284 bool "Force assumption that CPEI can be re-targetted"
285 depends on PERMIT_BSP_REMOVE
288 Say Y if you need to force the assumption that CPEI can be re-targetted to
289 any cpu in the system. This hint is available via ACPI 3.0 specifications.
290 Tiger4 systems are capable of re-directing CPEI to any CPU other than BSP.
291 This option it useful to enable this feature on older BIOS's as well.
292 You can also enable this by using boot command line option force_cpei=1.
295 bool "Preemptible Kernel"
297 This option reduces the latency of the kernel when reacting to
298 real-time or interactive events by allowing a low priority process to
299 be preempted even if it is in kernel mode executing a system call.
300 This allows applications to run more reliably even when the system is
303 Say Y here if you are building a kernel for a desktop, embedded
304 or real-time system. Say N if you are unsure.
308 config ARCH_SELECT_MEMORY_MODEL
311 config ARCH_DISCONTIGMEM_ENABLE
314 Say Y to support efficient handling of discontiguous physical memory,
315 for architectures which are either NUMA (Non-Uniform Memory Access)
316 or have huge holes in the physical address space for other reasons.
317 See <file:Documentation/vm/numa> for more.
319 config ARCH_FLATMEM_ENABLE
322 config ARCH_SPARSEMEM_ENABLE
324 depends on ARCH_DISCONTIGMEM_ENABLE
326 config ARCH_DISCONTIGMEM_DEFAULT
327 def_bool y if (IA64_SGI_SN2 || IA64_GENERIC || IA64_HP_ZX1 || IA64_HP_ZX1_SWIOTLB)
328 depends on ARCH_DISCONTIGMEM_ENABLE
332 depends on !IA64_HP_SIM && !FLATMEM
333 default y if IA64_SGI_SN2
335 Say Y to compile the kernel to support NUMA (Non-Uniform Memory
336 Access). This option is for configuring high-end multiprocessor
337 server systems. If in doubt, say N.
339 # VIRTUAL_MEM_MAP and FLAT_NODE_MEM_MAP are functionally equivalent.
340 # VIRTUAL_MEM_MAP has been retained for historical reasons.
341 config VIRTUAL_MEM_MAP
342 bool "Virtual mem map"
343 depends on !SPARSEMEM
344 default y if !IA64_HP_SIM
346 Say Y to compile the kernel with support for a virtual mem map.
347 This code also only takes effect if a memory hole of greater than
348 1 Gb is found during boot. You must turn this option on if you
349 require the DISCONTIGMEM option for your machine. If you are
354 default y if VIRTUAL_MEM_MAP
356 config HAVE_ARCH_EARLY_PFN_TO_NID
358 depends on NEED_MULTIPLE_NODES
361 bool "Support for Linux/x86 binaries"
363 IA-64 processors can execute IA-32 (X86) instructions. By
364 saying Y here, the kernel will include IA-32 system call
365 emulation support which makes it possible to transparently
366 run IA-32 Linux binaries on an IA-64 Linux system.
371 depends on IA32_SUPPORT
374 config IA64_MCA_RECOVERY
375 tristate "MCA recovery from errors other than TLB."
378 bool "Performance monitor support"
380 Selects whether support for the IA-64 performance monitor hardware
381 is included in the kernel. This makes some kernel data-structures a
382 little bigger and slows down execution a bit, but it is generally
383 a good idea to turn this on. If you're unsure, say Y.
386 tristate "/proc/pal support"
388 If you say Y here, you are able to get PAL (Processor Abstraction
389 Layer) information in /proc/pal. This contains useful information
390 about the processors in your systems, such as cache and TLB sizes
391 and the PAL firmware version in use.
393 To use this option, you have to ensure that the "/proc file system
394 support" (CONFIG_PROC_FS) is enabled, too.
396 source "drivers/firmware/Kconfig"
398 source "fs/Kconfig.binfmt"
402 menu "Power management and ACPI"
404 source "kernel/power/Kconfig"
406 source "drivers/acpi/Kconfig"
410 source "arch/ia64/kernel/cpufreq/Kconfig"
418 menu "Bus options (PCI, PCMCIA)"
423 Real IA-64 machines all have PCI/PCI-X/PCI Express busses. Say Y
424 here unless you are using a simulator without PCI support.
430 source "drivers/pci/Kconfig"
432 source "drivers/pci/hotplug/Kconfig"
434 source "drivers/pcmcia/Kconfig"
442 source "drivers/Kconfig"
449 # Use the generic interrupt handling code in kernel/irq/:
451 config GENERIC_HARDIRQS
455 config GENERIC_IRQ_PROBE
459 config GENERIC_PENDING_IRQ
461 depends on GENERIC_HARDIRQS && SMP
464 source "arch/ia64/hp/sim/Kconfig"
466 menu "Instrumentation Support"
467 depends on EXPERIMENTAL
469 source "arch/ia64/oprofile/Kconfig"
472 bool "Kprobes (EXPERIMENTAL)"
474 Kprobes allows you to trap at almost any kernel address and
475 execute a callback function. register_kprobe() establishes
476 a probepoint and specifies the callback. Kprobes is useful
477 for kernel debugging, non-intrusive instrumentation and testing.
478 If in doubt, say "N".
481 source "arch/ia64/Kconfig.debug"
483 source "security/Kconfig"
485 source "crypto/Kconfig"