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_SETUP_PER_CPU_AREA
107 config SCHED_OMIT_FRAME_POINTER
111 config IA64_UNCACHED_ALLOCATOR
113 select GENERIC_ALLOCATOR
119 menuconfig PARAVIRT_GUEST
120 bool "Paravirtualized guest support"
122 Say Y here to get to see options related to running Linux under
123 various hypervisors. This option alone does not add any kernel code.
125 If you say N, all options in this submenu will be skipped and disabled.
130 bool "Enable paravirtualization code"
131 depends on PARAVIRT_GUEST
136 This changes the kernel so it can modify itself when it is run
137 under a hypervisor, potentially improving performance significantly
138 over full virtualization. However, when run without a hypervisor
139 the kernel is theoretically slower and slightly larger.
142 source "arch/ia64/xen/Kconfig"
158 This selects the system type of your hardware. A "generic" kernel
159 will run on any supported IA-64 system. However, if you configure
160 a kernel for your specific system, it will be faster and smaller.
162 generic For any supported IA-64 system
163 DIG-compliant For DIG ("Developer's Interface Guide") compliant systems
164 DIG+Intel+IOMMU For DIG systems with Intel IOMMU
165 HP-zx1/sx1000 For HP systems
166 HP-zx1/sx1000+swiotlb For HP systems with (broken) DMA-constrained devices.
167 SGI-SN2 For SGI Altix systems
168 SGI-UV For SGI UV systems
169 Ski-simulator For the HP simulator <http://www.hpl.hp.com/research/linux/ski/>
170 Xen-domU For xen domU system
172 If you don't know what to do, choose "generic".
179 bool "DIG+Intel+IOMMU"
186 Build a kernel that runs on HP zx1 and sx1000 systems. This adds
187 support for the HP I/O MMU.
189 config IA64_HP_ZX1_SWIOTLB
190 bool "HP-zx1/sx1000 with software I/O TLB"
193 Build a kernel that runs on HP zx1 and sx1000 systems even when they
194 have broken PCI devices which cannot DMA to full 32 bits. Apart
195 from support for the HP I/O MMU, this includes support for the software
196 I/O TLB, which allows supporting the broken devices at the expense of
197 wasting some kernel memory (about 2MB by default).
204 Selecting this option will optimize the kernel for use on sn2 based
205 systems, but the resulting kernel binary will not run on other
206 types of ia64 systems. If you have an SGI Altix system, it's safe
207 to select this option. If in doubt, select ia64 generic support
216 Selecting this option will optimize the kernel for use on UV based
217 systems, but the resulting kernel binary will not run on other
218 types of ia64 systems. If you have an SGI UV system, it's safe
219 to select this option. If in doubt, select ia64 generic support
226 config IA64_XEN_GUEST
231 Build a kernel that runs on Xen guest domain. At this moment only
232 16KB page size in supported.
237 prompt "Processor type"
243 Select your IA-64 processor type. The default is Itanium.
244 This choice is safe for all IA-64 systems, but may not perform
245 optimally on systems with, say, Itanium 2 or newer processors.
250 Select this to configure for an Itanium 2 (McKinley) processor.
255 prompt "Kernel page size"
256 default IA64_PAGE_SIZE_16KB
258 config IA64_PAGE_SIZE_4KB
261 This lets you select the page size of the kernel. For best IA-64
262 performance, a page size of 8KB or 16KB is recommended. For best
263 IA-32 compatibility, a page size of 4KB should be selected (the vast
264 majority of IA-32 binaries work perfectly fine with a larger page
265 size). For Itanium 2 or newer systems, a page size of 64KB can also
268 4KB For best IA-32 compatibility
269 8KB For best IA-64 performance
270 16KB For best IA-64 performance
271 64KB Requires Itanium 2 or newer processor.
273 If you don't know what to do, choose 16KB.
275 config IA64_PAGE_SIZE_8KB
278 config IA64_PAGE_SIZE_16KB
281 config IA64_PAGE_SIZE_64KB
288 prompt "Page Table Levels"
295 depends on !IA64_PAGE_SIZE_64KB
306 source kernel/Kconfig.hz
314 # align cache-sensitive data to 128 bytes
315 config IA64_L1_CACHE_SHIFT
317 default "7" if MCKINLEY
318 default "6" if ITANIUM
321 bool "Cyclone (EXA) Time Source support"
323 Say Y here to enable support for IBM EXA Cyclone time source.
324 If you're unsure, answer N.
328 depends on !IA64_HP_SIM
331 config FORCE_MAX_ZONEORDER
332 int "MAX_ORDER (11 - 17)" if !HUGETLB_PAGE
333 range 11 17 if !HUGETLB_PAGE
334 default "17" if HUGETLB_PAGE
337 config VIRT_CPU_ACCOUNTING
338 bool "Deterministic task and CPU time accounting"
341 Select this option to enable more accurate task and CPU time
342 accounting. This is done by reading a CPU counter on each
343 kernel entry and exit and on transitions within the kernel
344 between system, softirq and hardirq state, so there is a
345 small performance impact.
346 If in doubt, say N here.
349 bool "Symmetric multi-processing support"
350 select USE_GENERIC_SMP_HELPERS
352 This enables support for systems with more than one CPU. If you have
353 a system with only one CPU, say N. If you have a system with more
356 If you say N here, the kernel will run on single and multiprocessor
357 systems, but will use only one CPU of a multiprocessor system. If
358 you say Y here, the kernel will run on many, but not all,
359 single processor systems. On a single processor system, the kernel
360 will run faster if you say N here.
362 See also the SMP-HOWTO available at
363 <http://www.tldp.org/docs.html#howto>.
365 If you don't know what to do here, say N.
368 int "Maximum number of CPUs (2-4096)"
373 You should set this to the number of CPUs in your system, but
374 keep in mind that a kernel compiled for, e.g., 2 CPUs will boot but
375 only use 2 CPUs on a >2 CPU system. Setting this to a value larger
376 than 64 will cause the use of a CPU mask array, causing a small
380 bool "Support for hot-pluggable CPUs (EXPERIMENTAL)"
381 depends on SMP && EXPERIMENTAL
385 Say Y here to experiment with turning CPUs off and on. CPUs
386 can be controlled through /sys/devices/system/cpu/cpu#.
387 Say N if you want to disable CPU hotplug.
389 config ARCH_ENABLE_MEMORY_HOTPLUG
392 config ARCH_ENABLE_MEMORY_HOTREMOVE
396 bool "SMT scheduler support"
399 Improves the CPU scheduler's decision making when dealing with
400 Intel IA64 chips with MultiThreading at a cost of slightly increased
401 overhead in some places. If unsure say N here.
403 config PERMIT_BSP_REMOVE
404 bool "Support removal of Bootstrap Processor"
405 depends on HOTPLUG_CPU
408 Say Y here if your platform SAL will support removal of BSP with HOTPLUG_CPU
411 config FORCE_CPEI_RETARGET
412 bool "Force assumption that CPEI can be re-targetted"
413 depends on PERMIT_BSP_REMOVE
416 Say Y if you need to force the assumption that CPEI can be re-targetted to
417 any cpu in the system. This hint is available via ACPI 3.0 specifications.
418 Tiger4 systems are capable of re-directing CPEI to any CPU other than BSP.
419 This option it useful to enable this feature on older BIOS's as well.
420 You can also enable this by using boot command line option force_cpei=1.
422 source "kernel/Kconfig.preempt"
426 config ARCH_SELECT_MEMORY_MODEL
429 config ARCH_DISCONTIGMEM_ENABLE
432 Say Y to support efficient handling of discontiguous physical memory,
433 for architectures which are either NUMA (Non-Uniform Memory Access)
434 or have huge holes in the physical address space for other reasons.
435 See <file:Documentation/vm/numa> for more.
437 config ARCH_FLATMEM_ENABLE
440 config ARCH_SPARSEMEM_ENABLE
442 depends on ARCH_DISCONTIGMEM_ENABLE
443 select SPARSEMEM_VMEMMAP_ENABLE
445 config ARCH_DISCONTIGMEM_DEFAULT
446 def_bool y if (IA64_SGI_SN2 || IA64_GENERIC || IA64_HP_ZX1 || IA64_HP_ZX1_SWIOTLB)
447 depends on ARCH_DISCONTIGMEM_ENABLE
451 depends on !IA64_HP_SIM && !FLATMEM
452 default y if IA64_SGI_SN2
453 select ACPI_NUMA if ACPI
455 Say Y to compile the kernel to support NUMA (Non-Uniform Memory
456 Access). This option is for configuring high-end multiprocessor
457 server systems. If in doubt, say N.
460 int "Max num nodes shift(3-10)"
463 depends on NEED_MULTIPLE_NODES
465 This option specifies the maximum number of nodes in your SSI system.
466 MAX_NUMNODES will be 2^(This value).
467 If in doubt, use the default.
469 config ARCH_POPULATES_NODE_MAP
472 # VIRTUAL_MEM_MAP and FLAT_NODE_MEM_MAP are functionally equivalent.
473 # VIRTUAL_MEM_MAP has been retained for historical reasons.
474 config VIRTUAL_MEM_MAP
475 bool "Virtual mem map"
476 depends on !SPARSEMEM
477 default y if !IA64_HP_SIM
479 Say Y to compile the kernel with support for a virtual mem map.
480 This code also only takes effect if a memory hole of greater than
481 1 Gb is found during boot. You must turn this option on if you
482 require the DISCONTIGMEM option for your machine. If you are
487 default y if VIRTUAL_MEM_MAP
489 config HAVE_ARCH_EARLY_PFN_TO_NID
490 def_bool NUMA && SPARSEMEM
492 config HAVE_ARCH_NODEDATA_EXTENSION
497 bool "Support for Linux/x86 binaries"
499 IA-64 processors can execute IA-32 (X86) instructions. By
500 saying Y here, the kernel will include IA-32 system call
501 emulation support which makes it possible to transparently
502 run IA-32 Linux binaries on an IA-64 Linux system.
507 depends on IA32_SUPPORT
510 config COMPAT_FOR_U64_ALIGNMENT
513 config IA64_MCA_RECOVERY
514 tristate "MCA recovery from errors other than TLB."
517 bool "Performance monitor support"
519 Selects whether support for the IA-64 performance monitor hardware
520 is included in the kernel. This makes some kernel data-structures a
521 little bigger and slows down execution a bit, but it is generally
522 a good idea to turn this on. If you're unsure, say Y.
525 tristate "/proc/pal support"
527 If you say Y here, you are able to get PAL (Processor Abstraction
528 Layer) information in /proc/pal. This contains useful information
529 about the processors in your systems, such as cache and TLB sizes
530 and the PAL firmware version in use.
532 To use this option, you have to ensure that the "/proc file system
533 support" (CONFIG_PROC_FS) is enabled, too.
535 config IA64_MC_ERR_INJECT
536 tristate "MC error injection support"
538 Adds support for MC error injection. If enabled, the kernel
539 will provide a sysfs interface for user applications to
540 call MC error injection PAL procedures to inject various errors.
541 This is a useful tool for MCA testing.
543 If you're unsure, do not select this option.
546 def_bool y if (IA64_SGI_SN2 || IA64_GENERIC)
549 bool "ESI (Extensible SAL Interface) support"
551 If you say Y here, support is built into the kernel to
552 make ESI calls. ESI calls are used to support vendor-specific
553 firmware extensions, such as the ability to inject memory-errors
554 for test-purposes. If you're unsure, say N.
556 config IA64_HP_AML_NFW
557 bool "Support ACPI AML calls to native firmware"
559 This driver installs a global ACPI Operation Region handler for
560 region 0xA1. AML methods can use this OpRegion to call arbitrary
561 native firmware functions. The driver installs the OpRegion
562 handler if there is an HPQ5001 device or if the user supplies
563 the "force" module parameter, e.g., with the "aml_nfw.force"
564 kernel command line option.
566 source "drivers/sn/Kconfig"
569 bool "kexec system call (EXPERIMENTAL)"
570 depends on EXPERIMENTAL && !IA64_HP_SIM && (!SMP || HOTPLUG_CPU)
572 kexec is a system call that implements the ability to shutdown your
573 current kernel, and to start another kernel. It is like a reboot
574 but it is independent of the system firmware. And like a reboot
575 you can start any kernel with it, not just Linux.
577 The name comes from the similarity to the exec system call.
579 It is an ongoing process to be certain the hardware in a machine
580 is properly shutdown, so do not be surprised if this code does not
581 initially work for you. It may help to enable device hotplugging
582 support. As of this writing the exact hardware interface is
583 strongly in flux, so no good recommendation can be made.
586 bool "kernel crash dumps"
587 depends on IA64_MCA_RECOVERY && !IA64_HP_SIM && (!SMP || HOTPLUG_CPU)
589 Generate crash dump after being started by kexec.
591 source "drivers/firmware/Kconfig"
593 source "fs/Kconfig.binfmt"
597 menu "Power management and ACPI options"
599 source "kernel/power/Kconfig"
601 source "drivers/acpi/Kconfig"
605 source "arch/ia64/kernel/cpufreq/Kconfig"
613 menu "Bus options (PCI, PCMCIA)"
618 Real IA-64 machines all have PCI/PCI-X/PCI Express busses. Say Y
619 here unless you are using a simulator without PCI support.
627 source "drivers/pci/pcie/Kconfig"
629 source "drivers/pci/Kconfig"
631 source "drivers/pci/hotplug/Kconfig"
633 source "drivers/pcmcia/Kconfig"
636 bool "Support for DMA Remapping Devices (EXPERIMENTAL)"
637 depends on IA64_GENERIC && ACPI && EXPERIMENTAL
639 DMA remapping (DMAR) devices support enables independent address
640 translations for Direct Memory Access (DMA) from devices.
641 These DMA remapping devices are reported via ACPI tables
642 and include PCI device scope covered by these DMA
645 config DMAR_DEFAULT_ON
647 prompt "Enable DMA Remapping Devices by default"
650 Selecting this option will enable a DMAR device at boot time if
651 one is found. If this option is not selected, DMAR support can
652 be enabled by passing intel_iommu=on to the kernel. It is
653 recommended you say N here while the DMAR code remains
662 source "drivers/Kconfig"
664 source "arch/ia64/hp/sim/Kconfig"
667 tristate "Memory special operations driver"
669 select IA64_UNCACHED_ALLOCATOR
671 If you have an ia64 and you want to enable memory special
672 operations support (formerly known as fetchop), say Y here,
677 source "arch/ia64/Kconfig.debug"
679 source "security/Kconfig"
681 source "crypto/Kconfig"
683 source "arch/ia64/kvm/Kconfig"
688 # Use the generic interrupt handling code in kernel/irq/:
690 config GENERIC_HARDIRQS
694 config GENERIC_IRQ_PROBE
698 config GENERIC_PENDING_IRQ
700 depends on GENERIC_HARDIRQS && SMP
708 def_bool (IA64_HP_ZX1 || IA64_HP_ZX1_SWIOTLB || IA64_GENERIC || SWIOTLB)