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 source "kernel/Kconfig.freezer"
12 menu "Processor type and features"
16 select PCI if (!IA64_HP_SIM)
17 select ACPI if (!IA64_HP_SIM)
18 select PM if (!IA64_HP_SIM)
19 select ARCH_SUPPORTS_MSI
20 select HAVE_UNSTABLE_SCHED_CLOCK
24 select HAVE_KRETPROBES
25 select HAVE_FTRACE_MCOUNT_RECORD
26 select HAVE_DYNAMIC_FTRACE if (!ITANIUM)
27 select HAVE_FUNCTION_TRACER
30 select HAVE_ARCH_TRACEHOOK
31 select HAVE_DMA_API_DEBUG
34 The Itanium Processor Family is Intel's 64-bit successor to
35 the 32-bit X86 line. The IA-64 Linux project has a home
36 page at <http://www.linuxia64.org/> and a mailing list at
37 <linux-ia64@vger.kernel.org>.
41 select ATA_NONSTANDARD if ATA
46 depends on !IA64_SGI_SN2
62 config GENERIC_LOCKBREAK
65 config RWSEM_XCHGADD_ALGORITHM
69 config HUGETLB_PAGE_SIZE_VARIABLE
71 depends on HUGETLB_PAGE
74 config GENERIC_FIND_NEXT_BIT
78 config GENERIC_CALIBRATE_DELAY
86 config GENERIC_TIME_VSYSCALL
90 config HAVE_SETUP_PER_CPU_AREA
105 config SCHED_OMIT_FRAME_POINTER
109 config IA64_UNCACHED_ALLOCATOR
111 select GENERIC_ALLOCATOR
113 config ARCH_USES_PG_UNCACHED
115 depends on IA64_UNCACHED_ALLOCATOR
121 menuconfig PARAVIRT_GUEST
122 bool "Paravirtualized guest support"
124 Say Y here to get to see options related to running Linux under
125 various hypervisors. This option alone does not add any kernel code.
127 If you say N, all options in this submenu will be skipped and disabled.
132 bool "Enable paravirtualization code"
133 depends on PARAVIRT_GUEST
138 This changes the kernel so it can modify itself when it is run
139 under a hypervisor, potentially improving performance significantly
140 over full virtualization. However, when run without a hypervisor
141 the kernel is theoretically slower and slightly larger.
144 source "arch/ia64/xen/Kconfig"
160 This selects the system type of your hardware. A "generic" kernel
161 will run on any supported IA-64 system. However, if you configure
162 a kernel for your specific system, it will be faster and smaller.
164 generic For any supported IA-64 system
165 DIG-compliant For DIG ("Developer's Interface Guide") compliant systems
166 DIG+Intel+IOMMU For DIG systems with Intel IOMMU
167 HP-zx1/sx1000 For HP systems
168 HP-zx1/sx1000+swiotlb For HP systems with (broken) DMA-constrained devices.
169 SGI-SN2 For SGI Altix systems
170 SGI-UV For SGI UV systems
171 Ski-simulator For the HP simulator <http://www.hpl.hp.com/research/linux/ski/>
172 Xen-domU For xen domU system
174 If you don't know what to do, choose "generic".
181 bool "DIG+Intel+IOMMU"
188 Build a kernel that runs on HP zx1 and sx1000 systems. This adds
189 support for the HP I/O MMU.
191 config IA64_HP_ZX1_SWIOTLB
192 bool "HP-zx1/sx1000 with software I/O TLB"
195 Build a kernel that runs on HP zx1 and sx1000 systems even when they
196 have broken PCI devices which cannot DMA to full 32 bits. Apart
197 from support for the HP I/O MMU, this includes support for the software
198 I/O TLB, which allows supporting the broken devices at the expense of
199 wasting some kernel memory (about 2MB by default).
206 Selecting this option will optimize the kernel for use on sn2 based
207 systems, but the resulting kernel binary will not run on other
208 types of ia64 systems. If you have an SGI Altix system, it's safe
209 to select this option. If in doubt, select ia64 generic support
218 Selecting this option will optimize the kernel for use on UV based
219 systems, but the resulting kernel binary will not run on other
220 types of ia64 systems. If you have an SGI UV system, it's safe
221 to select this option. If in doubt, select ia64 generic support
228 config IA64_XEN_GUEST
233 Build a kernel that runs on Xen guest domain. At this moment only
234 16KB page size in supported.
239 prompt "Processor type"
245 Select your IA-64 processor type. The default is Itanium.
246 This choice is safe for all IA-64 systems, but may not perform
247 optimally on systems with, say, Itanium 2 or newer processors.
252 Select this to configure for an Itanium 2 (McKinley) processor.
257 prompt "Kernel page size"
258 default IA64_PAGE_SIZE_16KB
260 config IA64_PAGE_SIZE_4KB
263 This lets you select the page size of the kernel. For best IA-64
264 performance, a page size of 8KB or 16KB is recommended. For best
265 IA-32 compatibility, a page size of 4KB should be selected (the vast
266 majority of IA-32 binaries work perfectly fine with a larger page
267 size). For Itanium 2 or newer systems, a page size of 64KB can also
270 4KB For best IA-32 compatibility
271 8KB For best IA-64 performance
272 16KB For best IA-64 performance
273 64KB Requires Itanium 2 or newer processor.
275 If you don't know what to do, choose 16KB.
277 config IA64_PAGE_SIZE_8KB
280 config IA64_PAGE_SIZE_16KB
283 config IA64_PAGE_SIZE_64KB
290 prompt "Page Table Levels"
297 depends on !IA64_PAGE_SIZE_64KB
308 source kernel/Kconfig.hz
316 # align cache-sensitive data to 128 bytes
317 config IA64_L1_CACHE_SHIFT
319 default "7" if MCKINLEY
320 default "6" if ITANIUM
323 bool "Cyclone (EXA) Time Source support"
325 Say Y here to enable support for IBM EXA Cyclone time source.
326 If you're unsure, answer N.
330 depends on !IA64_HP_SIM
333 config FORCE_MAX_ZONEORDER
334 int "MAX_ORDER (11 - 17)" if !HUGETLB_PAGE
335 range 11 17 if !HUGETLB_PAGE
336 default "17" if HUGETLB_PAGE
339 config VIRT_CPU_ACCOUNTING
340 bool "Deterministic task and CPU time accounting"
343 Select this option to enable more accurate task and CPU time
344 accounting. This is done by reading a CPU counter on each
345 kernel entry and exit and on transitions within the kernel
346 between system, softirq and hardirq state, so there is a
347 small performance impact.
348 If in doubt, say N here.
351 bool "Symmetric multi-processing support"
352 select USE_GENERIC_SMP_HELPERS
354 This enables support for systems with more than one CPU. If you have
355 a system with only one CPU, say N. If you have a system with more
358 If you say N here, the kernel will run on single and multiprocessor
359 systems, but will use only one CPU of a multiprocessor system. If
360 you say Y here, the kernel will run on many, but not all,
361 single processor systems. On a single processor system, the kernel
362 will run faster if you say N here.
364 See also the SMP-HOWTO available at
365 <http://www.tldp.org/docs.html#howto>.
367 If you don't know what to do here, say N.
370 int "Maximum number of CPUs (2-4096)"
375 You should set this to the number of CPUs in your system, but
376 keep in mind that a kernel compiled for, e.g., 2 CPUs will boot but
377 only use 2 CPUs on a >2 CPU system. Setting this to a value larger
378 than 64 will cause the use of a CPU mask array, causing a small
382 bool "Support for hot-pluggable CPUs (EXPERIMENTAL)"
383 depends on SMP && EXPERIMENTAL
387 Say Y here to experiment with turning CPUs off and on. CPUs
388 can be controlled through /sys/devices/system/cpu/cpu#.
389 Say N if you want to disable CPU hotplug.
391 config ARCH_ENABLE_MEMORY_HOTPLUG
394 config ARCH_ENABLE_MEMORY_HOTREMOVE
398 bool "SMT scheduler support"
401 Improves the CPU scheduler's decision making when dealing with
402 Intel IA64 chips with MultiThreading at a cost of slightly increased
403 overhead in some places. If unsure say N here.
405 config PERMIT_BSP_REMOVE
406 bool "Support removal of Bootstrap Processor"
407 depends on HOTPLUG_CPU
410 Say Y here if your platform SAL will support removal of BSP with HOTPLUG_CPU
413 config FORCE_CPEI_RETARGET
414 bool "Force assumption that CPEI can be re-targetted"
415 depends on PERMIT_BSP_REMOVE
418 Say Y if you need to force the assumption that CPEI can be re-targetted to
419 any cpu in the system. This hint is available via ACPI 3.0 specifications.
420 Tiger4 systems are capable of re-directing CPEI to any CPU other than BSP.
421 This option it useful to enable this feature on older BIOS's as well.
422 You can also enable this by using boot command line option force_cpei=1.
424 source "kernel/Kconfig.preempt"
428 config ARCH_SELECT_MEMORY_MODEL
431 config ARCH_DISCONTIGMEM_ENABLE
434 Say Y to support efficient handling of discontiguous physical memory,
435 for architectures which are either NUMA (Non-Uniform Memory Access)
436 or have huge holes in the physical address space for other reasons.
437 See <file:Documentation/vm/numa> for more.
439 config ARCH_FLATMEM_ENABLE
442 config ARCH_SPARSEMEM_ENABLE
444 depends on ARCH_DISCONTIGMEM_ENABLE
445 select SPARSEMEM_VMEMMAP_ENABLE
447 config ARCH_DISCONTIGMEM_DEFAULT
448 def_bool y if (IA64_SGI_SN2 || IA64_GENERIC || IA64_HP_ZX1 || IA64_HP_ZX1_SWIOTLB)
449 depends on ARCH_DISCONTIGMEM_ENABLE
453 depends on !IA64_HP_SIM && !FLATMEM
454 default y if IA64_SGI_SN2
455 select ACPI_NUMA if ACPI
457 Say Y to compile the kernel to support NUMA (Non-Uniform Memory
458 Access). This option is for configuring high-end multiprocessor
459 server systems. If in doubt, say N.
462 int "Max num nodes shift(3-10)"
465 depends on NEED_MULTIPLE_NODES
467 This option specifies the maximum number of nodes in your SSI system.
468 MAX_NUMNODES will be 2^(This value).
469 If in doubt, use the default.
471 config ARCH_POPULATES_NODE_MAP
474 # VIRTUAL_MEM_MAP and FLAT_NODE_MEM_MAP are functionally equivalent.
475 # VIRTUAL_MEM_MAP has been retained for historical reasons.
476 config VIRTUAL_MEM_MAP
477 bool "Virtual mem map"
478 depends on !SPARSEMEM
479 default y if !IA64_HP_SIM
481 Say Y to compile the kernel with support for a virtual mem map.
482 This code also only takes effect if a memory hole of greater than
483 1 Gb is found during boot. You must turn this option on if you
484 require the DISCONTIGMEM option for your machine. If you are
489 default y if VIRTUAL_MEM_MAP
491 config HAVE_ARCH_EARLY_PFN_TO_NID
492 def_bool NUMA && SPARSEMEM
494 config HAVE_ARCH_NODEDATA_EXTENSION
498 config ARCH_PROC_KCORE_TEXT
500 depends on PROC_KCORE
503 bool "Support for Linux/x86 binaries"
505 IA-64 processors can execute IA-32 (X86) instructions. By
506 saying Y here, the kernel will include IA-32 system call
507 emulation support which makes it possible to transparently
508 run IA-32 Linux binaries on an IA-64 Linux system.
513 depends on IA32_SUPPORT
516 config COMPAT_FOR_U64_ALIGNMENT
519 config IA64_MCA_RECOVERY
520 tristate "MCA recovery from errors other than TLB."
523 bool "Performance monitor support"
525 Selects whether support for the IA-64 performance monitor hardware
526 is included in the kernel. This makes some kernel data-structures a
527 little bigger and slows down execution a bit, but it is generally
528 a good idea to turn this on. If you're unsure, say Y.
531 tristate "/proc/pal support"
533 If you say Y here, you are able to get PAL (Processor Abstraction
534 Layer) information in /proc/pal. This contains useful information
535 about the processors in your systems, such as cache and TLB sizes
536 and the PAL firmware version in use.
538 To use this option, you have to ensure that the "/proc file system
539 support" (CONFIG_PROC_FS) is enabled, too.
541 config IA64_MC_ERR_INJECT
542 tristate "MC error injection support"
544 Adds support for MC error injection. If enabled, the kernel
545 will provide a sysfs interface for user applications to
546 call MC error injection PAL procedures to inject various errors.
547 This is a useful tool for MCA testing.
549 If you're unsure, do not select this option.
552 def_bool y if (IA64_SGI_SN2 || IA64_GENERIC)
555 bool "ESI (Extensible SAL Interface) support"
557 If you say Y here, support is built into the kernel to
558 make ESI calls. ESI calls are used to support vendor-specific
559 firmware extensions, such as the ability to inject memory-errors
560 for test-purposes. If you're unsure, say N.
562 config IA64_HP_AML_NFW
563 bool "Support ACPI AML calls to native firmware"
565 This driver installs a global ACPI Operation Region handler for
566 region 0xA1. AML methods can use this OpRegion to call arbitrary
567 native firmware functions. The driver installs the OpRegion
568 handler if there is an HPQ5001 device or if the user supplies
569 the "force" module parameter, e.g., with the "aml_nfw.force"
570 kernel command line option.
572 source "drivers/sn/Kconfig"
575 bool "kexec system call (EXPERIMENTAL)"
576 depends on EXPERIMENTAL && !IA64_HP_SIM && (!SMP || HOTPLUG_CPU)
578 kexec is a system call that implements the ability to shutdown your
579 current kernel, and to start another kernel. It is like a reboot
580 but it is independent of the system firmware. And like a reboot
581 you can start any kernel with it, not just Linux.
583 The name comes from the similarity to the exec system call.
585 It is an ongoing process to be certain the hardware in a machine
586 is properly shutdown, so do not be surprised if this code does not
587 initially work for you. It may help to enable device hotplugging
588 support. As of this writing the exact hardware interface is
589 strongly in flux, so no good recommendation can be made.
592 bool "kernel crash dumps"
593 depends on IA64_MCA_RECOVERY && !IA64_HP_SIM && (!SMP || HOTPLUG_CPU)
595 Generate crash dump after being started by kexec.
597 source "drivers/firmware/Kconfig"
599 source "fs/Kconfig.binfmt"
603 menu "Power management and ACPI options"
605 source "kernel/power/Kconfig"
607 source "drivers/acpi/Kconfig"
611 source "arch/ia64/kernel/cpufreq/Kconfig"
619 menu "Bus options (PCI, PCMCIA)"
624 Real IA-64 machines all have PCI/PCI-X/PCI Express busses. Say Y
625 here unless you are using a simulator without PCI support.
633 source "drivers/pci/pcie/Kconfig"
635 source "drivers/pci/Kconfig"
637 source "drivers/pci/hotplug/Kconfig"
639 source "drivers/pcmcia/Kconfig"
642 bool "Support for DMA Remapping Devices (EXPERIMENTAL)"
643 depends on IA64_GENERIC && ACPI && EXPERIMENTAL
645 DMA remapping (DMAR) devices support enables independent address
646 translations for Direct Memory Access (DMA) from devices.
647 These DMA remapping devices are reported via ACPI tables
648 and include PCI device scope covered by these DMA
651 config DMAR_DEFAULT_ON
653 prompt "Enable DMA Remapping Devices by default"
656 Selecting this option will enable a DMAR device at boot time if
657 one is found. If this option is not selected, DMAR support can
658 be enabled by passing intel_iommu=on to the kernel. It is
659 recommended you say N here while the DMAR code remains
668 source "drivers/Kconfig"
670 source "arch/ia64/hp/sim/Kconfig"
673 tristate "Memory special operations driver"
675 select IA64_UNCACHED_ALLOCATOR
677 If you have an ia64 and you want to enable memory special
678 operations support (formerly known as fetchop), say Y here,
683 source "arch/ia64/Kconfig.debug"
685 source "security/Kconfig"
687 source "crypto/Kconfig"
689 source "arch/ia64/kvm/Kconfig"
694 # Use the generic interrupt handling code in kernel/irq/:
696 config GENERIC_HARDIRQS
700 config GENERIC_IRQ_PROBE
704 config GENERIC_PENDING_IRQ
706 depends on GENERIC_HARDIRQS && SMP
714 def_bool (IA64_HP_ZX1 || IA64_HP_ZX1_SWIOTLB || IA64_GENERIC || SWIOTLB)