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
118 config ARCH_USES_PG_UNCACHED
120 depends on IA64_UNCACHED_ALLOCATOR
126 menuconfig PARAVIRT_GUEST
127 bool "Paravirtualized guest support"
129 Say Y here to get to see options related to running Linux under
130 various hypervisors. This option alone does not add any kernel code.
132 If you say N, all options in this submenu will be skipped and disabled.
137 bool "Enable paravirtualization code"
138 depends on PARAVIRT_GUEST
143 This changes the kernel so it can modify itself when it is run
144 under a hypervisor, potentially improving performance significantly
145 over full virtualization. However, when run without a hypervisor
146 the kernel is theoretically slower and slightly larger.
149 source "arch/ia64/xen/Kconfig"
165 This selects the system type of your hardware. A "generic" kernel
166 will run on any supported IA-64 system. However, if you configure
167 a kernel for your specific system, it will be faster and smaller.
169 generic For any supported IA-64 system
170 DIG-compliant For DIG ("Developer's Interface Guide") compliant systems
171 DIG+Intel+IOMMU For DIG systems with Intel IOMMU
172 HP-zx1/sx1000 For HP systems
173 HP-zx1/sx1000+swiotlb For HP systems with (broken) DMA-constrained devices.
174 SGI-SN2 For SGI Altix systems
175 SGI-UV For SGI UV systems
176 Ski-simulator For the HP simulator <http://www.hpl.hp.com/research/linux/ski/>
177 Xen-domU For xen domU system
179 If you don't know what to do, choose "generic".
186 bool "DIG+Intel+IOMMU"
193 Build a kernel that runs on HP zx1 and sx1000 systems. This adds
194 support for the HP I/O MMU.
196 config IA64_HP_ZX1_SWIOTLB
197 bool "HP-zx1/sx1000 with software I/O TLB"
200 Build a kernel that runs on HP zx1 and sx1000 systems even when they
201 have broken PCI devices which cannot DMA to full 32 bits. Apart
202 from support for the HP I/O MMU, this includes support for the software
203 I/O TLB, which allows supporting the broken devices at the expense of
204 wasting some kernel memory (about 2MB by default).
211 Selecting this option will optimize the kernel for use on sn2 based
212 systems, but the resulting kernel binary will not run on other
213 types of ia64 systems. If you have an SGI Altix system, it's safe
214 to select this option. If in doubt, select ia64 generic support
223 Selecting this option will optimize the kernel for use on UV based
224 systems, but the resulting kernel binary will not run on other
225 types of ia64 systems. If you have an SGI UV system, it's safe
226 to select this option. If in doubt, select ia64 generic support
233 config IA64_XEN_GUEST
238 Build a kernel that runs on Xen guest domain. At this moment only
239 16KB page size in supported.
244 prompt "Processor type"
250 Select your IA-64 processor type. The default is Itanium.
251 This choice is safe for all IA-64 systems, but may not perform
252 optimally on systems with, say, Itanium 2 or newer processors.
257 Select this to configure for an Itanium 2 (McKinley) processor.
262 prompt "Kernel page size"
263 default IA64_PAGE_SIZE_16KB
265 config IA64_PAGE_SIZE_4KB
268 This lets you select the page size of the kernel. For best IA-64
269 performance, a page size of 8KB or 16KB is recommended. For best
270 IA-32 compatibility, a page size of 4KB should be selected (the vast
271 majority of IA-32 binaries work perfectly fine with a larger page
272 size). For Itanium 2 or newer systems, a page size of 64KB can also
275 4KB For best IA-32 compatibility
276 8KB For best IA-64 performance
277 16KB For best IA-64 performance
278 64KB Requires Itanium 2 or newer processor.
280 If you don't know what to do, choose 16KB.
282 config IA64_PAGE_SIZE_8KB
285 config IA64_PAGE_SIZE_16KB
288 config IA64_PAGE_SIZE_64KB
295 prompt "Page Table Levels"
302 depends on !IA64_PAGE_SIZE_64KB
313 source kernel/Kconfig.hz
321 # align cache-sensitive data to 128 bytes
322 config IA64_L1_CACHE_SHIFT
324 default "7" if MCKINLEY
325 default "6" if ITANIUM
328 bool "Cyclone (EXA) Time Source support"
330 Say Y here to enable support for IBM EXA Cyclone time source.
331 If you're unsure, answer N.
335 depends on !IA64_HP_SIM
338 config FORCE_MAX_ZONEORDER
339 int "MAX_ORDER (11 - 17)" if !HUGETLB_PAGE
340 range 11 17 if !HUGETLB_PAGE
341 default "17" if HUGETLB_PAGE
344 config VIRT_CPU_ACCOUNTING
345 bool "Deterministic task and CPU time accounting"
348 Select this option to enable more accurate task and CPU time
349 accounting. This is done by reading a CPU counter on each
350 kernel entry and exit and on transitions within the kernel
351 between system, softirq and hardirq state, so there is a
352 small performance impact.
353 If in doubt, say N here.
356 bool "Symmetric multi-processing support"
357 select USE_GENERIC_SMP_HELPERS
359 This enables support for systems with more than one CPU. If you have
360 a system with only one CPU, say N. If you have a system with more
363 If you say N here, the kernel will run on single and multiprocessor
364 systems, but will use only one CPU of a multiprocessor system. If
365 you say Y here, the kernel will run on many, but not all,
366 single processor systems. On a single processor system, the kernel
367 will run faster if you say N here.
369 See also the SMP-HOWTO available at
370 <http://www.tldp.org/docs.html#howto>.
372 If you don't know what to do here, say N.
375 int "Maximum number of CPUs (2-4096)"
380 You should set this to the number of CPUs in your system, but
381 keep in mind that a kernel compiled for, e.g., 2 CPUs will boot but
382 only use 2 CPUs on a >2 CPU system. Setting this to a value larger
383 than 64 will cause the use of a CPU mask array, causing a small
387 bool "Support for hot-pluggable CPUs (EXPERIMENTAL)"
388 depends on SMP && EXPERIMENTAL
392 Say Y here to experiment with turning CPUs off and on. CPUs
393 can be controlled through /sys/devices/system/cpu/cpu#.
394 Say N if you want to disable CPU hotplug.
396 config ARCH_ENABLE_MEMORY_HOTPLUG
399 config ARCH_ENABLE_MEMORY_HOTREMOVE
403 bool "SMT scheduler support"
406 Improves the CPU scheduler's decision making when dealing with
407 Intel IA64 chips with MultiThreading at a cost of slightly increased
408 overhead in some places. If unsure say N here.
410 config PERMIT_BSP_REMOVE
411 bool "Support removal of Bootstrap Processor"
412 depends on HOTPLUG_CPU
415 Say Y here if your platform SAL will support removal of BSP with HOTPLUG_CPU
418 config FORCE_CPEI_RETARGET
419 bool "Force assumption that CPEI can be re-targetted"
420 depends on PERMIT_BSP_REMOVE
423 Say Y if you need to force the assumption that CPEI can be re-targetted to
424 any cpu in the system. This hint is available via ACPI 3.0 specifications.
425 Tiger4 systems are capable of re-directing CPEI to any CPU other than BSP.
426 This option it useful to enable this feature on older BIOS's as well.
427 You can also enable this by using boot command line option force_cpei=1.
429 source "kernel/Kconfig.preempt"
433 config ARCH_SELECT_MEMORY_MODEL
436 config ARCH_DISCONTIGMEM_ENABLE
439 Say Y to support efficient handling of discontiguous physical memory,
440 for architectures which are either NUMA (Non-Uniform Memory Access)
441 or have huge holes in the physical address space for other reasons.
442 See <file:Documentation/vm/numa> for more.
444 config ARCH_FLATMEM_ENABLE
447 config ARCH_SPARSEMEM_ENABLE
449 depends on ARCH_DISCONTIGMEM_ENABLE
450 select SPARSEMEM_VMEMMAP_ENABLE
452 config ARCH_DISCONTIGMEM_DEFAULT
453 def_bool y if (IA64_SGI_SN2 || IA64_GENERIC || IA64_HP_ZX1 || IA64_HP_ZX1_SWIOTLB)
454 depends on ARCH_DISCONTIGMEM_ENABLE
458 depends on !IA64_HP_SIM && !FLATMEM
459 default y if IA64_SGI_SN2
460 select ACPI_NUMA if ACPI
462 Say Y to compile the kernel to support NUMA (Non-Uniform Memory
463 Access). This option is for configuring high-end multiprocessor
464 server systems. If in doubt, say N.
467 int "Max num nodes shift(3-10)"
470 depends on NEED_MULTIPLE_NODES
472 This option specifies the maximum number of nodes in your SSI system.
473 MAX_NUMNODES will be 2^(This value).
474 If in doubt, use the default.
476 config ARCH_POPULATES_NODE_MAP
479 # VIRTUAL_MEM_MAP and FLAT_NODE_MEM_MAP are functionally equivalent.
480 # VIRTUAL_MEM_MAP has been retained for historical reasons.
481 config VIRTUAL_MEM_MAP
482 bool "Virtual mem map"
483 depends on !SPARSEMEM
484 default y if !IA64_HP_SIM
486 Say Y to compile the kernel with support for a virtual mem map.
487 This code also only takes effect if a memory hole of greater than
488 1 Gb is found during boot. You must turn this option on if you
489 require the DISCONTIGMEM option for your machine. If you are
494 default y if VIRTUAL_MEM_MAP
496 config HAVE_ARCH_EARLY_PFN_TO_NID
497 def_bool NUMA && SPARSEMEM
499 config HAVE_ARCH_NODEDATA_EXTENSION
504 bool "Support for Linux/x86 binaries"
506 IA-64 processors can execute IA-32 (X86) instructions. By
507 saying Y here, the kernel will include IA-32 system call
508 emulation support which makes it possible to transparently
509 run IA-32 Linux binaries on an IA-64 Linux system.
514 depends on IA32_SUPPORT
517 config COMPAT_FOR_U64_ALIGNMENT
520 config IA64_MCA_RECOVERY
521 tristate "MCA recovery from errors other than TLB."
524 bool "Performance monitor support"
526 Selects whether support for the IA-64 performance monitor hardware
527 is included in the kernel. This makes some kernel data-structures a
528 little bigger and slows down execution a bit, but it is generally
529 a good idea to turn this on. If you're unsure, say Y.
532 tristate "/proc/pal support"
534 If you say Y here, you are able to get PAL (Processor Abstraction
535 Layer) information in /proc/pal. This contains useful information
536 about the processors in your systems, such as cache and TLB sizes
537 and the PAL firmware version in use.
539 To use this option, you have to ensure that the "/proc file system
540 support" (CONFIG_PROC_FS) is enabled, too.
542 config IA64_MC_ERR_INJECT
543 tristate "MC error injection support"
545 Adds support for MC error injection. If enabled, the kernel
546 will provide a sysfs interface for user applications to
547 call MC error injection PAL procedures to inject various errors.
548 This is a useful tool for MCA testing.
550 If you're unsure, do not select this option.
553 def_bool y if (IA64_SGI_SN2 || IA64_GENERIC)
556 bool "ESI (Extensible SAL Interface) support"
558 If you say Y here, support is built into the kernel to
559 make ESI calls. ESI calls are used to support vendor-specific
560 firmware extensions, such as the ability to inject memory-errors
561 for test-purposes. If you're unsure, say N.
563 config IA64_HP_AML_NFW
564 bool "Support ACPI AML calls to native firmware"
566 This driver installs a global ACPI Operation Region handler for
567 region 0xA1. AML methods can use this OpRegion to call arbitrary
568 native firmware functions. The driver installs the OpRegion
569 handler if there is an HPQ5001 device or if the user supplies
570 the "force" module parameter, e.g., with the "aml_nfw.force"
571 kernel command line option.
573 source "drivers/sn/Kconfig"
576 bool "kexec system call (EXPERIMENTAL)"
577 depends on EXPERIMENTAL && !IA64_HP_SIM && (!SMP || HOTPLUG_CPU)
579 kexec is a system call that implements the ability to shutdown your
580 current kernel, and to start another kernel. It is like a reboot
581 but it is independent of the system firmware. And like a reboot
582 you can start any kernel with it, not just Linux.
584 The name comes from the similarity to the exec system call.
586 It is an ongoing process to be certain the hardware in a machine
587 is properly shutdown, so do not be surprised if this code does not
588 initially work for you. It may help to enable device hotplugging
589 support. As of this writing the exact hardware interface is
590 strongly in flux, so no good recommendation can be made.
593 bool "kernel crash dumps"
594 depends on IA64_MCA_RECOVERY && !IA64_HP_SIM && (!SMP || HOTPLUG_CPU)
596 Generate crash dump after being started by kexec.
598 source "drivers/firmware/Kconfig"
600 source "fs/Kconfig.binfmt"
604 menu "Power management and ACPI options"
606 source "kernel/power/Kconfig"
608 source "drivers/acpi/Kconfig"
612 source "arch/ia64/kernel/cpufreq/Kconfig"
620 menu "Bus options (PCI, PCMCIA)"
625 Real IA-64 machines all have PCI/PCI-X/PCI Express busses. Say Y
626 here unless you are using a simulator without PCI support.
634 source "drivers/pci/pcie/Kconfig"
636 source "drivers/pci/Kconfig"
638 source "drivers/pci/hotplug/Kconfig"
640 source "drivers/pcmcia/Kconfig"
643 bool "Support for DMA Remapping Devices (EXPERIMENTAL)"
644 depends on IA64_GENERIC && ACPI && EXPERIMENTAL
646 DMA remapping (DMAR) devices support enables independent address
647 translations for Direct Memory Access (DMA) from devices.
648 These DMA remapping devices are reported via ACPI tables
649 and include PCI device scope covered by these DMA
652 config DMAR_DEFAULT_ON
654 prompt "Enable DMA Remapping Devices by default"
657 Selecting this option will enable a DMAR device at boot time if
658 one is found. If this option is not selected, DMAR support can
659 be enabled by passing intel_iommu=on to the kernel. It is
660 recommended you say N here while the DMAR code remains
669 source "drivers/Kconfig"
671 source "arch/ia64/hp/sim/Kconfig"
674 tristate "Memory special operations driver"
676 select IA64_UNCACHED_ALLOCATOR
678 If you have an ia64 and you want to enable memory special
679 operations support (formerly known as fetchop), say Y here,
684 source "arch/ia64/Kconfig.debug"
686 source "security/Kconfig"
688 source "crypto/Kconfig"
690 source "arch/ia64/kvm/Kconfig"
695 # Use the generic interrupt handling code in kernel/irq/:
697 config GENERIC_HARDIRQS
701 config GENERIC_IRQ_PROBE
705 config GENERIC_PENDING_IRQ
707 depends on GENERIC_HARDIRQS && SMP
715 def_bool (IA64_HP_ZX1 || IA64_HP_ZX1_SWIOTLB || IA64_GENERIC || SWIOTLB)