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
27 select HAVE_MEMBLOCK_NODE_MAP
28 select ARCH_DISCARD_MEMBLOCK
29 select GENERIC_IRQ_PROBE
30 select GENERIC_PENDING_IRQ if SMP
32 select GENERIC_IRQ_SHOW
33 select ARCH_WANT_OPTIONAL_GPIOLIB
34 select ARCH_HAVE_NMI_SAFE_CMPXCHG
36 select ARCH_CLOCKSOURCE_DATA
37 select GENERIC_TIME_VSYSCALL
40 The Itanium Processor Family is Intel's 64-bit successor to
41 the 32-bit X86 line. The IA-64 Linux project has a home
42 page at <http://www.linuxia64.org/> and a mailing list at
43 <linux-ia64@vger.kernel.org>.
47 select ATA_NONSTANDARD if ATA
52 depends on !IA64_SGI_SN2
62 config ARCH_DMA_ADDR_T_64BIT
65 config NEED_DMA_MAP_STATE
68 config NEED_SG_DMA_LENGTH
74 config STACKTRACE_SUPPORT
77 config GENERIC_LOCKBREAK
80 config RWSEM_XCHGADD_ALGORITHM
84 config HUGETLB_PAGE_SIZE_VARIABLE
86 depends on HUGETLB_PAGE
89 config GENERIC_CALIBRATE_DELAY
93 config HAVE_SETUP_PER_CPU_AREA
107 config SCHED_OMIT_FRAME_POINTER
111 config IA64_UNCACHED_ALLOCATOR
113 select GENERIC_ALLOCATOR
115 config ARCH_USES_PG_UNCACHED
117 depends on IA64_UNCACHED_ALLOCATOR
123 menuconfig PARAVIRT_GUEST
124 bool "Paravirtualized guest support"
126 Say Y here to get to see options related to running Linux under
127 various hypervisors. This option alone does not add any kernel code.
129 If you say N, all options in this submenu will be skipped and disabled.
134 bool "Enable paravirtualization code"
135 depends on PARAVIRT_GUEST
140 This changes the kernel so it can modify itself when it is run
141 under a hypervisor, potentially improving performance significantly
142 over full virtualization. However, when run without a hypervisor
143 the kernel is theoretically slower and slightly larger.
146 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-targeted"
416 depends on PERMIT_BSP_REMOVE
419 Say Y if you need to force the assumption that CPEI can be re-targeted 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 # 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
496 config USE_PERCPU_NUMA_NODE_ID
500 config HAVE_MEMORYLESS_NODES
503 config ARCH_PROC_KCORE_TEXT
505 depends on PROC_KCORE
507 config IA64_MCA_RECOVERY
508 tristate "MCA recovery from errors other than TLB."
511 bool "Performance monitor support"
513 Selects whether support for the IA-64 performance monitor hardware
514 is included in the kernel. This makes some kernel data-structures a
515 little bigger and slows down execution a bit, but it is generally
516 a good idea to turn this on. If you're unsure, say Y.
519 tristate "/proc/pal support"
521 If you say Y here, you are able to get PAL (Processor Abstraction
522 Layer) information in /proc/pal. This contains useful information
523 about the processors in your systems, such as cache and TLB sizes
524 and the PAL firmware version in use.
526 To use this option, you have to ensure that the "/proc file system
527 support" (CONFIG_PROC_FS) is enabled, too.
529 config IA64_MC_ERR_INJECT
530 tristate "MC error injection support"
532 Adds support for MC error injection. If enabled, the kernel
533 will provide a sysfs interface for user applications to
534 call MC error injection PAL procedures to inject various errors.
535 This is a useful tool for MCA testing.
537 If you're unsure, do not select this option.
540 def_bool y if (IA64_SGI_SN2 || IA64_GENERIC)
543 bool "ESI (Extensible SAL Interface) support"
545 If you say Y here, support is built into the kernel to
546 make ESI calls. ESI calls are used to support vendor-specific
547 firmware extensions, such as the ability to inject memory-errors
548 for test-purposes. If you're unsure, say N.
550 config IA64_HP_AML_NFW
551 bool "Support ACPI AML calls to native firmware"
553 This driver installs a global ACPI Operation Region handler for
554 region 0xA1. AML methods can use this OpRegion to call arbitrary
555 native firmware functions. The driver installs the OpRegion
556 handler if there is an HPQ5001 device or if the user supplies
557 the "force" module parameter, e.g., with the "aml_nfw.force"
558 kernel command line option.
560 source "drivers/sn/Kconfig"
563 bool "kexec system call (EXPERIMENTAL)"
564 depends on EXPERIMENTAL && !IA64_HP_SIM && (!SMP || HOTPLUG_CPU)
566 kexec is a system call that implements the ability to shutdown your
567 current kernel, and to start another kernel. It is like a reboot
568 but it is independent of the system firmware. And like a reboot
569 you can start any kernel with it, not just Linux.
571 The name comes from the similarity to the exec system call.
573 It is an ongoing process to be certain the hardware in a machine
574 is properly shutdown, so do not be surprised if this code does not
575 initially work for you. It may help to enable device hotplugging
576 support. As of this writing the exact hardware interface is
577 strongly in flux, so no good recommendation can be made.
580 bool "kernel crash dumps"
581 depends on IA64_MCA_RECOVERY && !IA64_HP_SIM && (!SMP || HOTPLUG_CPU)
583 Generate crash dump after being started by kexec.
585 source "drivers/firmware/Kconfig"
587 source "fs/Kconfig.binfmt"
591 menu "Power management and ACPI options"
593 source "kernel/power/Kconfig"
595 source "drivers/acpi/Kconfig"
599 source "arch/ia64/kernel/cpufreq/Kconfig"
607 menu "Bus options (PCI, PCMCIA)"
612 Real IA-64 machines all have PCI/PCI-X/PCI Express busses. Say Y
613 here unless you are using a simulator without PCI support.
621 source "drivers/pci/pcie/Kconfig"
623 source "drivers/pci/Kconfig"
625 source "drivers/pci/hotplug/Kconfig"
627 source "drivers/pcmcia/Kconfig"
635 source "drivers/Kconfig"
637 source "arch/ia64/hp/sim/Kconfig"
640 tristate "Memory special operations driver"
642 select IA64_UNCACHED_ALLOCATOR
644 If you have an ia64 and you want to enable memory special
645 operations support (formerly known as fetchop), say Y here,
650 source "arch/ia64/Kconfig.debug"
652 source "security/Kconfig"
654 source "crypto/Kconfig"
656 source "arch/ia64/kvm/Kconfig"
661 def_bool (IA64_HP_ZX1 || IA64_HP_ZX1_SWIOTLB || IA64_GENERIC || SWIOTLB)