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 depends on SMP && PREEMPT
67 config RWSEM_XCHGADD_ALGORITHM
71 config HUGETLB_PAGE_SIZE_VARIABLE
73 depends on HUGETLB_PAGE
76 config GENERIC_FIND_NEXT_BIT
80 config GENERIC_CALIBRATE_DELAY
88 config GENERIC_TIME_VSYSCALL
92 config HAVE_LEGACY_PER_CPU_AREA
95 config HAVE_SETUP_PER_CPU_AREA
110 config SCHED_OMIT_FRAME_POINTER
114 config IA64_UNCACHED_ALLOCATOR
116 select GENERIC_ALLOCATOR
122 menuconfig PARAVIRT_GUEST
123 bool "Paravirtualized guest support"
125 Say Y here to get to see options related to running Linux under
126 various hypervisors. This option alone does not add any kernel code.
128 If you say N, all options in this submenu will be skipped and disabled.
133 bool "Enable paravirtualization code"
134 depends on PARAVIRT_GUEST
139 This changes the kernel so it can modify itself when it is run
140 under a hypervisor, potentially improving performance significantly
141 over full virtualization. However, when run without a hypervisor
142 the kernel is theoretically slower and slightly larger.
145 source "arch/ia64/xen/Kconfig"
161 This selects the system type of your hardware. A "generic" kernel
162 will run on any supported IA-64 system. However, if you configure
163 a kernel for your specific system, it will be faster and smaller.
165 generic For any supported IA-64 system
166 DIG-compliant For DIG ("Developer's Interface Guide") compliant systems
167 DIG+Intel+IOMMU For DIG systems with Intel IOMMU
168 HP-zx1/sx1000 For HP systems
169 HP-zx1/sx1000+swiotlb For HP systems with (broken) DMA-constrained devices.
170 SGI-SN2 For SGI Altix systems
171 SGI-UV For SGI UV systems
172 Ski-simulator For the HP simulator <http://www.hpl.hp.com/research/linux/ski/>
173 Xen-domU For xen domU system
175 If you don't know what to do, choose "generic".
182 bool "DIG+Intel+IOMMU"
189 Build a kernel that runs on HP zx1 and sx1000 systems. This adds
190 support for the HP I/O MMU.
192 config IA64_HP_ZX1_SWIOTLB
193 bool "HP-zx1/sx1000 with software I/O TLB"
196 Build a kernel that runs on HP zx1 and sx1000 systems even when they
197 have broken PCI devices which cannot DMA to full 32 bits. Apart
198 from support for the HP I/O MMU, this includes support for the software
199 I/O TLB, which allows supporting the broken devices at the expense of
200 wasting some kernel memory (about 2MB by default).
207 Selecting this option will optimize the kernel for use on sn2 based
208 systems, but the resulting kernel binary will not run on other
209 types of ia64 systems. If you have an SGI Altix system, it's safe
210 to select this option. If in doubt, select ia64 generic support
219 Selecting this option will optimize the kernel for use on UV based
220 systems, but the resulting kernel binary will not run on other
221 types of ia64 systems. If you have an SGI UV system, it's safe
222 to select this option. If in doubt, select ia64 generic support
229 config IA64_XEN_GUEST
234 Build a kernel that runs on Xen guest domain. At this moment only
235 16KB page size in supported.
240 prompt "Processor type"
246 Select your IA-64 processor type. The default is Itanium.
247 This choice is safe for all IA-64 systems, but may not perform
248 optimally on systems with, say, Itanium 2 or newer processors.
253 Select this to configure for an Itanium 2 (McKinley) processor.
258 prompt "Kernel page size"
259 default IA64_PAGE_SIZE_16KB
261 config IA64_PAGE_SIZE_4KB
264 This lets you select the page size of the kernel. For best IA-64
265 performance, a page size of 8KB or 16KB is recommended. For best
266 IA-32 compatibility, a page size of 4KB should be selected (the vast
267 majority of IA-32 binaries work perfectly fine with a larger page
268 size). For Itanium 2 or newer systems, a page size of 64KB can also
271 4KB For best IA-32 compatibility
272 8KB For best IA-64 performance
273 16KB For best IA-64 performance
274 64KB Requires Itanium 2 or newer processor.
276 If you don't know what to do, choose 16KB.
278 config IA64_PAGE_SIZE_8KB
281 config IA64_PAGE_SIZE_16KB
284 config IA64_PAGE_SIZE_64KB
291 prompt "Page Table Levels"
298 depends on !IA64_PAGE_SIZE_64KB
309 source kernel/Kconfig.hz
317 # align cache-sensitive data to 128 bytes
318 config IA64_L1_CACHE_SHIFT
320 default "7" if MCKINLEY
321 default "6" if ITANIUM
324 bool "Cyclone (EXA) Time Source support"
326 Say Y here to enable support for IBM EXA Cyclone time source.
327 If you're unsure, answer N.
331 depends on !IA64_HP_SIM
334 config FORCE_MAX_ZONEORDER
335 int "MAX_ORDER (11 - 17)" if !HUGETLB_PAGE
336 range 11 17 if !HUGETLB_PAGE
337 default "17" if HUGETLB_PAGE
340 config VIRT_CPU_ACCOUNTING
341 bool "Deterministic task and CPU time accounting"
344 Select this option to enable more accurate task and CPU time
345 accounting. This is done by reading a CPU counter on each
346 kernel entry and exit and on transitions within the kernel
347 between system, softirq and hardirq state, so there is a
348 small performance impact.
349 If in doubt, say N here.
352 bool "Symmetric multi-processing support"
353 select USE_GENERIC_SMP_HELPERS
355 This enables support for systems with more than one CPU. If you have
356 a system with only one CPU, say N. If you have a system with more
359 If you say N here, the kernel will run on single and multiprocessor
360 systems, but will use only one CPU of a multiprocessor system. If
361 you say Y here, the kernel will run on many, but not all,
362 single processor systems. On a single processor system, the kernel
363 will run faster if you say N here.
365 See also the SMP-HOWTO available at
366 <http://www.tldp.org/docs.html#howto>.
368 If you don't know what to do here, say N.
371 int "Maximum number of CPUs (2-4096)"
376 You should set this to the number of CPUs in your system, but
377 keep in mind that a kernel compiled for, e.g., 2 CPUs will boot but
378 only use 2 CPUs on a >2 CPU system. Setting this to a value larger
379 than 64 will cause the use of a CPU mask array, causing a small
383 bool "Support for hot-pluggable CPUs (EXPERIMENTAL)"
384 depends on SMP && EXPERIMENTAL
388 Say Y here to experiment with turning CPUs off and on. CPUs
389 can be controlled through /sys/devices/system/cpu/cpu#.
390 Say N if you want to disable CPU hotplug.
392 config ARCH_ENABLE_MEMORY_HOTPLUG
395 config ARCH_ENABLE_MEMORY_HOTREMOVE
399 bool "SMT scheduler support"
402 Improves the CPU scheduler's decision making when dealing with
403 Intel IA64 chips with MultiThreading at a cost of slightly increased
404 overhead in some places. If unsure say N here.
406 config PERMIT_BSP_REMOVE
407 bool "Support removal of Bootstrap Processor"
408 depends on HOTPLUG_CPU
411 Say Y here if your platform SAL will support removal of BSP with HOTPLUG_CPU
414 config FORCE_CPEI_RETARGET
415 bool "Force assumption that CPEI can be re-targetted"
416 depends on PERMIT_BSP_REMOVE
419 Say Y if you need to force the assumption that CPEI can be re-targetted to
420 any cpu in the system. This hint is available via ACPI 3.0 specifications.
421 Tiger4 systems are capable of re-directing CPEI to any CPU other than BSP.
422 This option it useful to enable this feature on older BIOS's as well.
423 You can also enable this by using boot command line option force_cpei=1.
425 source "kernel/Kconfig.preempt"
429 config ARCH_SELECT_MEMORY_MODEL
432 config ARCH_DISCONTIGMEM_ENABLE
435 Say Y to support efficient handling of discontiguous physical memory,
436 for architectures which are either NUMA (Non-Uniform Memory Access)
437 or have huge holes in the physical address space for other reasons.
438 See <file:Documentation/vm/numa> for more.
440 config ARCH_FLATMEM_ENABLE
443 config ARCH_SPARSEMEM_ENABLE
445 depends on ARCH_DISCONTIGMEM_ENABLE
446 select SPARSEMEM_VMEMMAP_ENABLE
448 config ARCH_DISCONTIGMEM_DEFAULT
449 def_bool y if (IA64_SGI_SN2 || IA64_GENERIC || IA64_HP_ZX1 || IA64_HP_ZX1_SWIOTLB)
450 depends on ARCH_DISCONTIGMEM_ENABLE
454 depends on !IA64_HP_SIM && !FLATMEM
455 default y if IA64_SGI_SN2
456 select ACPI_NUMA if ACPI
458 Say Y to compile the kernel to support NUMA (Non-Uniform Memory
459 Access). This option is for configuring high-end multiprocessor
460 server systems. If in doubt, say N.
463 int "Max num nodes shift(3-10)"
466 depends on NEED_MULTIPLE_NODES
468 This option specifies the maximum number of nodes in your SSI system.
469 MAX_NUMNODES will be 2^(This value).
470 If in doubt, use the default.
472 config ARCH_POPULATES_NODE_MAP
475 # VIRTUAL_MEM_MAP and FLAT_NODE_MEM_MAP are functionally equivalent.
476 # VIRTUAL_MEM_MAP has been retained for historical reasons.
477 config VIRTUAL_MEM_MAP
478 bool "Virtual mem map"
479 depends on !SPARSEMEM
480 default y if !IA64_HP_SIM
482 Say Y to compile the kernel with support for a virtual mem map.
483 This code also only takes effect if a memory hole of greater than
484 1 Gb is found during boot. You must turn this option on if you
485 require the DISCONTIGMEM option for your machine. If you are
490 default y if VIRTUAL_MEM_MAP
492 config HAVE_ARCH_EARLY_PFN_TO_NID
493 def_bool NUMA && SPARSEMEM
495 config HAVE_ARCH_NODEDATA_EXTENSION
500 bool "Support for Linux/x86 binaries"
502 IA-64 processors can execute IA-32 (X86) instructions. By
503 saying Y here, the kernel will include IA-32 system call
504 emulation support which makes it possible to transparently
505 run IA-32 Linux binaries on an IA-64 Linux system.
510 depends on IA32_SUPPORT
513 config COMPAT_FOR_U64_ALIGNMENT
516 config IA64_MCA_RECOVERY
517 tristate "MCA recovery from errors other than TLB."
520 bool "Performance monitor support"
522 Selects whether support for the IA-64 performance monitor hardware
523 is included in the kernel. This makes some kernel data-structures a
524 little bigger and slows down execution a bit, but it is generally
525 a good idea to turn this on. If you're unsure, say Y.
528 tristate "/proc/pal support"
530 If you say Y here, you are able to get PAL (Processor Abstraction
531 Layer) information in /proc/pal. This contains useful information
532 about the processors in your systems, such as cache and TLB sizes
533 and the PAL firmware version in use.
535 To use this option, you have to ensure that the "/proc file system
536 support" (CONFIG_PROC_FS) is enabled, too.
538 config IA64_MC_ERR_INJECT
539 tristate "MC error injection support"
541 Adds support for MC error injection. If enabled, the kernel
542 will provide a sysfs interface for user applications to
543 call MC error injection PAL procedures to inject various errors.
544 This is a useful tool for MCA testing.
546 If you're unsure, do not select this option.
549 def_bool y if (IA64_SGI_SN2 || IA64_GENERIC)
552 bool "ESI (Extensible SAL Interface) support"
554 If you say Y here, support is built into the kernel to
555 make ESI calls. ESI calls are used to support vendor-specific
556 firmware extensions, such as the ability to inject memory-errors
557 for test-purposes. If you're unsure, say N.
559 config IA64_HP_AML_NFW
560 bool "Support ACPI AML calls to native firmware"
562 This driver installs a global ACPI Operation Region handler for
563 region 0xA1. AML methods can use this OpRegion to call arbitrary
564 native firmware functions. The driver installs the OpRegion
565 handler if there is an HPQ5001 device or if the user supplies
566 the "force" module parameter, e.g., with the "aml_nfw.force"
567 kernel command line option.
569 source "drivers/sn/Kconfig"
572 bool "kexec system call (EXPERIMENTAL)"
573 depends on EXPERIMENTAL && !IA64_HP_SIM && (!SMP || HOTPLUG_CPU)
575 kexec is a system call that implements the ability to shutdown your
576 current kernel, and to start another kernel. It is like a reboot
577 but it is independent of the system firmware. And like a reboot
578 you can start any kernel with it, not just Linux.
580 The name comes from the similarity to the exec system call.
582 It is an ongoing process to be certain the hardware in a machine
583 is properly shutdown, so do not be surprised if this code does not
584 initially work for you. It may help to enable device hotplugging
585 support. As of this writing the exact hardware interface is
586 strongly in flux, so no good recommendation can be made.
589 bool "kernel crash dumps"
590 depends on IA64_MCA_RECOVERY && !IA64_HP_SIM && (!SMP || HOTPLUG_CPU)
592 Generate crash dump after being started by kexec.
594 source "drivers/firmware/Kconfig"
596 source "fs/Kconfig.binfmt"
600 menu "Power management and ACPI options"
602 source "kernel/power/Kconfig"
604 source "drivers/acpi/Kconfig"
608 source "arch/ia64/kernel/cpufreq/Kconfig"
616 menu "Bus options (PCI, PCMCIA)"
621 Real IA-64 machines all have PCI/PCI-X/PCI Express busses. Say Y
622 here unless you are using a simulator without PCI support.
630 source "drivers/pci/pcie/Kconfig"
632 source "drivers/pci/Kconfig"
634 source "drivers/pci/hotplug/Kconfig"
636 source "drivers/pcmcia/Kconfig"
639 bool "Support for DMA Remapping Devices (EXPERIMENTAL)"
640 depends on IA64_GENERIC && ACPI && EXPERIMENTAL
642 DMA remapping (DMAR) devices support enables independent address
643 translations for Direct Memory Access (DMA) from devices.
644 These DMA remapping devices are reported via ACPI tables
645 and include PCI device scope covered by these DMA
648 config DMAR_DEFAULT_ON
650 prompt "Enable DMA Remapping Devices by default"
653 Selecting this option will enable a DMAR device at boot time if
654 one is found. If this option is not selected, DMAR support can
655 be enabled by passing intel_iommu=on to the kernel. It is
656 recommended you say N here while the DMAR code remains
665 source "drivers/Kconfig"
667 source "arch/ia64/hp/sim/Kconfig"
670 tristate "Memory special operations driver"
672 select IA64_UNCACHED_ALLOCATOR
674 If you have an ia64 and you want to enable memory special
675 operations support (formerly known as fetchop), say Y here,
680 source "arch/ia64/Kconfig.debug"
682 source "security/Kconfig"
684 source "crypto/Kconfig"
686 source "arch/ia64/kvm/Kconfig"
691 # Use the generic interrupt handling code in kernel/irq/:
693 config GENERIC_HARDIRQS
697 config GENERIC_IRQ_PROBE
701 config GENERIC_PENDING_IRQ
703 depends on GENERIC_HARDIRQS && SMP
711 def_bool (IA64_HP_ZX1 || IA64_HP_ZX1_SWIOTLB || IA64_GENERIC || SWIOTLB)