3 source "kernel/Kconfig.freezer"
5 menu "Processor type and features"
9 select PCI if (!IA64_HP_SIM)
10 select ACPI if (!IA64_HP_SIM)
11 select PM if (!IA64_HP_SIM)
12 select ARCH_SUPPORTS_MSI
13 select HAVE_UNSTABLE_SCHED_CLOCK
17 select HAVE_KRETPROBES
18 select HAVE_FTRACE_MCOUNT_RECORD
19 select HAVE_DYNAMIC_FTRACE if (!ITANIUM)
20 select HAVE_FUNCTION_TRACER
23 select HAVE_ARCH_TRACEHOOK
24 select HAVE_DMA_API_DEBUG
25 select HAVE_GENERIC_HARDIRQS
26 select GENERIC_IRQ_PROBE
27 select GENERIC_PENDING_IRQ if SMP
29 select GENERIC_IRQ_SHOW
30 select ARCH_WANT_OPTIONAL_GPIOLIB
31 select ARCH_HAVE_NMI_SAFE_CMPXCHG
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
56 config ARCH_DMA_ADDR_T_64BIT
59 config NEED_DMA_MAP_STATE
62 config NEED_SG_DMA_LENGTH
68 config STACKTRACE_SUPPORT
71 config GENERIC_LOCKBREAK
74 config RWSEM_XCHGADD_ALGORITHM
78 config HUGETLB_PAGE_SIZE_VARIABLE
80 depends on HUGETLB_PAGE
83 config GENERIC_CALIBRATE_DELAY
87 config GENERIC_TIME_VSYSCALL
91 config HAVE_SETUP_PER_CPU_AREA
109 config ARCH_CLOCKSOURCE_DATA
112 config SCHED_OMIT_FRAME_POINTER
116 config IA64_UNCACHED_ALLOCATOR
118 select GENERIC_ALLOCATOR
120 config ARCH_USES_PG_UNCACHED
122 depends on IA64_UNCACHED_ALLOCATOR
128 menuconfig PARAVIRT_GUEST
129 bool "Paravirtualized guest support"
131 Say Y here to get to see options related to running Linux under
132 various hypervisors. This option alone does not add any kernel code.
134 If you say N, all options in this submenu will be skipped and disabled.
139 bool "Enable paravirtualization code"
140 depends on PARAVIRT_GUEST
145 This changes the kernel so it can modify itself when it is run
146 under a hypervisor, potentially improving performance significantly
147 over full virtualization. However, when run without a hypervisor
148 the kernel is theoretically slower and slightly larger.
151 source "arch/ia64/xen/Kconfig"
167 This selects the system type of your hardware. A "generic" kernel
168 will run on any supported IA-64 system. However, if you configure
169 a kernel for your specific system, it will be faster and smaller.
171 generic For any supported IA-64 system
172 DIG-compliant For DIG ("Developer's Interface Guide") compliant systems
173 DIG+Intel+IOMMU For DIG systems with Intel IOMMU
174 HP-zx1/sx1000 For HP systems
175 HP-zx1/sx1000+swiotlb For HP systems with (broken) DMA-constrained devices.
176 SGI-SN2 For SGI Altix systems
177 SGI-UV For SGI UV systems
178 Ski-simulator For the HP simulator <http://www.hpl.hp.com/research/linux/ski/>
179 Xen-domU For xen domU system
181 If you don't know what to do, choose "generic".
188 bool "DIG+Intel+IOMMU"
195 Build a kernel that runs on HP zx1 and sx1000 systems. This adds
196 support for the HP I/O MMU.
198 config IA64_HP_ZX1_SWIOTLB
199 bool "HP-zx1/sx1000 with software I/O TLB"
202 Build a kernel that runs on HP zx1 and sx1000 systems even when they
203 have broken PCI devices which cannot DMA to full 32 bits. Apart
204 from support for the HP I/O MMU, this includes support for the software
205 I/O TLB, which allows supporting the broken devices at the expense of
206 wasting some kernel memory (about 2MB by default).
213 Selecting this option will optimize the kernel for use on sn2 based
214 systems, but the resulting kernel binary will not run on other
215 types of ia64 systems. If you have an SGI Altix system, it's safe
216 to select this option. If in doubt, select ia64 generic support
225 Selecting this option will optimize the kernel for use on UV based
226 systems, but the resulting kernel binary will not run on other
227 types of ia64 systems. If you have an SGI UV system, it's safe
228 to select this option. If in doubt, select ia64 generic support
235 config IA64_XEN_GUEST
240 Build a kernel that runs on Xen guest domain. At this moment only
241 16KB page size in supported.
246 prompt "Processor type"
252 Select your IA-64 processor type. The default is Itanium.
253 This choice is safe for all IA-64 systems, but may not perform
254 optimally on systems with, say, Itanium 2 or newer processors.
259 Select this to configure for an Itanium 2 (McKinley) processor.
264 prompt "Kernel page size"
265 default IA64_PAGE_SIZE_16KB
267 config IA64_PAGE_SIZE_4KB
270 This lets you select the page size of the kernel. For best IA-64
271 performance, a page size of 8KB or 16KB is recommended. For best
272 IA-32 compatibility, a page size of 4KB should be selected (the vast
273 majority of IA-32 binaries work perfectly fine with a larger page
274 size). For Itanium 2 or newer systems, a page size of 64KB can also
277 4KB For best IA-32 compatibility
278 8KB For best IA-64 performance
279 16KB For best IA-64 performance
280 64KB Requires Itanium 2 or newer processor.
282 If you don't know what to do, choose 16KB.
284 config IA64_PAGE_SIZE_8KB
287 config IA64_PAGE_SIZE_16KB
290 config IA64_PAGE_SIZE_64KB
297 prompt "Page Table Levels"
304 depends on !IA64_PAGE_SIZE_64KB
315 source kernel/Kconfig.hz
323 # align cache-sensitive data to 128 bytes
324 config IA64_L1_CACHE_SHIFT
326 default "7" if MCKINLEY
327 default "6" if ITANIUM
330 bool "Cyclone (EXA) Time Source support"
332 Say Y here to enable support for IBM EXA Cyclone time source.
333 If you're unsure, answer N.
337 depends on !IA64_HP_SIM
340 config FORCE_MAX_ZONEORDER
341 int "MAX_ORDER (11 - 17)" if !HUGETLB_PAGE
342 range 11 17 if !HUGETLB_PAGE
343 default "17" if HUGETLB_PAGE
346 config VIRT_CPU_ACCOUNTING
347 bool "Deterministic task and CPU time accounting"
350 Select this option to enable more accurate task and CPU time
351 accounting. This is done by reading a CPU counter on each
352 kernel entry and exit and on transitions within the kernel
353 between system, softirq and hardirq state, so there is a
354 small performance impact.
355 If in doubt, say N here.
358 bool "Symmetric multi-processing support"
359 select USE_GENERIC_SMP_HELPERS
361 This enables support for systems with more than one CPU. If you have
362 a system with only one CPU, say N. If you have a system with more
365 If you say N here, the kernel will run on single and multiprocessor
366 systems, but will use only one CPU of a multiprocessor system. If
367 you say Y here, the kernel will run on many, but not all,
368 single processor systems. On a single processor system, the kernel
369 will run faster if you say N here.
371 See also the SMP-HOWTO available at
372 <http://www.tldp.org/docs.html#howto>.
374 If you don't know what to do here, say N.
377 int "Maximum number of CPUs (2-4096)"
382 You should set this to the number of CPUs in your system, but
383 keep in mind that a kernel compiled for, e.g., 2 CPUs will boot but
384 only use 2 CPUs on a >2 CPU system. Setting this to a value larger
385 than 64 will cause the use of a CPU mask array, causing a small
389 bool "Support for hot-pluggable CPUs (EXPERIMENTAL)"
390 depends on SMP && EXPERIMENTAL
394 Say Y here to experiment with turning CPUs off and on. CPUs
395 can be controlled through /sys/devices/system/cpu/cpu#.
396 Say N if you want to disable CPU hotplug.
398 config ARCH_ENABLE_MEMORY_HOTPLUG
401 config ARCH_ENABLE_MEMORY_HOTREMOVE
405 bool "SMT scheduler support"
408 Improves the CPU scheduler's decision making when dealing with
409 Intel IA64 chips with MultiThreading at a cost of slightly increased
410 overhead in some places. If unsure say N here.
412 config PERMIT_BSP_REMOVE
413 bool "Support removal of Bootstrap Processor"
414 depends on HOTPLUG_CPU
417 Say Y here if your platform SAL will support removal of BSP with HOTPLUG_CPU
420 config FORCE_CPEI_RETARGET
421 bool "Force assumption that CPEI can be re-targeted"
422 depends on PERMIT_BSP_REMOVE
425 Say Y if you need to force the assumption that CPEI can be re-targeted to
426 any cpu in the system. This hint is available via ACPI 3.0 specifications.
427 Tiger4 systems are capable of re-directing CPEI to any CPU other than BSP.
428 This option it useful to enable this feature on older BIOS's as well.
429 You can also enable this by using boot command line option force_cpei=1.
431 source "kernel/Kconfig.preempt"
435 config ARCH_SELECT_MEMORY_MODEL
438 config ARCH_DISCONTIGMEM_ENABLE
441 Say Y to support efficient handling of discontiguous physical memory,
442 for architectures which are either NUMA (Non-Uniform Memory Access)
443 or have huge holes in the physical address space for other reasons.
444 See <file:Documentation/vm/numa> for more.
446 config ARCH_FLATMEM_ENABLE
449 config ARCH_SPARSEMEM_ENABLE
451 depends on ARCH_DISCONTIGMEM_ENABLE
452 select SPARSEMEM_VMEMMAP_ENABLE
454 config ARCH_DISCONTIGMEM_DEFAULT
455 def_bool y if (IA64_SGI_SN2 || IA64_GENERIC || IA64_HP_ZX1 || IA64_HP_ZX1_SWIOTLB)
456 depends on ARCH_DISCONTIGMEM_ENABLE
460 depends on !IA64_HP_SIM && !FLATMEM
461 default y if IA64_SGI_SN2
462 select ACPI_NUMA if ACPI
464 Say Y to compile the kernel to support NUMA (Non-Uniform Memory
465 Access). This option is for configuring high-end multiprocessor
466 server systems. If in doubt, say N.
469 int "Max num nodes shift(3-10)"
472 depends on NEED_MULTIPLE_NODES
474 This option specifies the maximum number of nodes in your SSI system.
475 MAX_NUMNODES will be 2^(This value).
476 If in doubt, use the default.
478 config ARCH_POPULATES_NODE_MAP
481 # VIRTUAL_MEM_MAP and FLAT_NODE_MEM_MAP are functionally equivalent.
482 # VIRTUAL_MEM_MAP has been retained for historical reasons.
483 config VIRTUAL_MEM_MAP
484 bool "Virtual mem map"
485 depends on !SPARSEMEM
486 default y if !IA64_HP_SIM
488 Say Y to compile the kernel with support for a virtual mem map.
489 This code also only takes effect if a memory hole of greater than
490 1 Gb is found during boot. You must turn this option on if you
491 require the DISCONTIGMEM option for your machine. If you are
496 default y if VIRTUAL_MEM_MAP
498 config HAVE_ARCH_EARLY_PFN_TO_NID
499 def_bool NUMA && SPARSEMEM
501 config HAVE_ARCH_NODEDATA_EXTENSION
505 config USE_PERCPU_NUMA_NODE_ID
509 config HAVE_MEMORYLESS_NODES
512 config ARCH_PROC_KCORE_TEXT
514 depends on PROC_KCORE
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"
644 source "drivers/Kconfig"
646 source "arch/ia64/hp/sim/Kconfig"
649 tristate "Memory special operations driver"
651 select IA64_UNCACHED_ALLOCATOR
653 If you have an ia64 and you want to enable memory special
654 operations support (formerly known as fetchop), say Y here,
659 source "arch/ia64/Kconfig.debug"
661 source "security/Kconfig"
663 source "crypto/Kconfig"
665 source "arch/ia64/kvm/Kconfig"
670 def_bool (IA64_HP_ZX1 || IA64_HP_ZX1_SWIOTLB || IA64_GENERIC || SWIOTLB)