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 HAVE_VIRT_CPU_ACCOUNTING
29 select ARCH_DISCARD_MEMBLOCK
30 select GENERIC_IRQ_PROBE
31 select GENERIC_PENDING_IRQ if SMP
33 select GENERIC_IRQ_SHOW
34 select ARCH_WANT_OPTIONAL_GPIOLIB
35 select ARCH_HAVE_NMI_SAFE_CMPXCHG
37 select GENERIC_SMP_IDLE_THREAD
39 select ARCH_TASK_STRUCT_ALLOCATOR
40 select ARCH_THREAD_INFO_ALLOCATOR
41 select ARCH_CLOCKSOURCE_DATA
42 select GENERIC_TIME_VSYSCALL
45 The Itanium Processor Family is Intel's 64-bit successor to
46 the 32-bit X86 line. The IA-64 Linux project has a home
47 page at <http://www.linuxia64.org/> and a mailing list at
48 <linux-ia64@vger.kernel.org>.
52 select ATA_NONSTANDARD if ATA
57 depends on !IA64_SGI_SN2
67 config ARCH_DMA_ADDR_T_64BIT
70 config NEED_DMA_MAP_STATE
73 config NEED_SG_DMA_LENGTH
79 config STACKTRACE_SUPPORT
82 config GENERIC_LOCKBREAK
85 config RWSEM_XCHGADD_ALGORITHM
89 config HUGETLB_PAGE_SIZE_VARIABLE
91 depends on HUGETLB_PAGE
94 config GENERIC_CALIBRATE_DELAY
98 config HAVE_SETUP_PER_CPU_AREA
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"
132 Say Y here to get to see options related to running Linux under
133 various hypervisors. This option alone does not add any kernel code.
135 If you say N, all options in this submenu will be skipped and disabled.
140 bool "Enable paravirtualization code"
141 depends on PARAVIRT_GUEST
144 This changes the kernel so it can modify itself when it is run
145 under a hypervisor, potentially improving performance significantly
146 over full virtualization. However, when run without a hypervisor
147 the kernel is theoretically slower and slightly larger.
150 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
345 bool "Symmetric multi-processing support"
346 select USE_GENERIC_SMP_HELPERS
348 This enables support for systems with more than one CPU. If you have
349 a system with only one CPU, say N. If you have a system with more
352 If you say N here, the kernel will run on single and multiprocessor
353 systems, but will use only one CPU of a multiprocessor system. If
354 you say Y here, the kernel will run on many, but not all,
355 single processor systems. On a single processor system, the kernel
356 will run faster if you say N here.
358 See also the SMP-HOWTO available at
359 <http://www.tldp.org/docs.html#howto>.
361 If you don't know what to do here, say N.
364 int "Maximum number of CPUs (2-4096)"
369 You should set this to the number of CPUs in your system, but
370 keep in mind that a kernel compiled for, e.g., 2 CPUs will boot but
371 only use 2 CPUs on a >2 CPU system. Setting this to a value larger
372 than 64 will cause the use of a CPU mask array, causing a small
376 bool "Support for hot-pluggable CPUs (EXPERIMENTAL)"
377 depends on SMP && EXPERIMENTAL
381 Say Y here to experiment with turning CPUs off and on. CPUs
382 can be controlled through /sys/devices/system/cpu/cpu#.
383 Say N if you want to disable CPU hotplug.
385 config ARCH_ENABLE_MEMORY_HOTPLUG
388 config ARCH_ENABLE_MEMORY_HOTREMOVE
392 bool "SMT scheduler support"
395 Improves the CPU scheduler's decision making when dealing with
396 Intel IA64 chips with MultiThreading at a cost of slightly increased
397 overhead in some places. If unsure say N here.
399 config PERMIT_BSP_REMOVE
400 bool "Support removal of Bootstrap Processor"
401 depends on HOTPLUG_CPU
404 Say Y here if your platform SAL will support removal of BSP with HOTPLUG_CPU
407 config FORCE_CPEI_RETARGET
408 bool "Force assumption that CPEI can be re-targeted"
409 depends on PERMIT_BSP_REMOVE
412 Say Y if you need to force the assumption that CPEI can be re-targeted to
413 any cpu in the system. This hint is available via ACPI 3.0 specifications.
414 Tiger4 systems are capable of re-directing CPEI to any CPU other than BSP.
415 This option it useful to enable this feature on older BIOS's as well.
416 You can also enable this by using boot command line option force_cpei=1.
418 source "kernel/Kconfig.preempt"
422 config ARCH_SELECT_MEMORY_MODEL
425 config ARCH_DISCONTIGMEM_ENABLE
428 Say Y to support efficient handling of discontiguous physical memory,
429 for architectures which are either NUMA (Non-Uniform Memory Access)
430 or have huge holes in the physical address space for other reasons.
431 See <file:Documentation/vm/numa> for more.
433 config ARCH_FLATMEM_ENABLE
436 config ARCH_SPARSEMEM_ENABLE
438 depends on ARCH_DISCONTIGMEM_ENABLE
439 select SPARSEMEM_VMEMMAP_ENABLE
441 config ARCH_DISCONTIGMEM_DEFAULT
442 def_bool y if (IA64_SGI_SN2 || IA64_GENERIC || IA64_HP_ZX1 || IA64_HP_ZX1_SWIOTLB)
443 depends on ARCH_DISCONTIGMEM_ENABLE
447 depends on !IA64_HP_SIM && !FLATMEM
448 default y if IA64_SGI_SN2
449 select ACPI_NUMA if ACPI
451 Say Y to compile the kernel to support NUMA (Non-Uniform Memory
452 Access). This option is for configuring high-end multiprocessor
453 server systems. If in doubt, say N.
456 int "Max num nodes shift(3-10)"
459 depends on NEED_MULTIPLE_NODES
461 This option specifies the maximum number of nodes in your SSI system.
462 MAX_NUMNODES will be 2^(This value).
463 If in doubt, use the default.
465 # VIRTUAL_MEM_MAP and FLAT_NODE_MEM_MAP are functionally equivalent.
466 # VIRTUAL_MEM_MAP has been retained for historical reasons.
467 config VIRTUAL_MEM_MAP
468 bool "Virtual mem map"
469 depends on !SPARSEMEM
470 default y if !IA64_HP_SIM
472 Say Y to compile the kernel with support for a virtual mem map.
473 This code also only takes effect if a memory hole of greater than
474 1 Gb is found during boot. You must turn this option on if you
475 require the DISCONTIGMEM option for your machine. If you are
480 default y if VIRTUAL_MEM_MAP
482 config HAVE_ARCH_EARLY_PFN_TO_NID
483 def_bool NUMA && SPARSEMEM
485 config HAVE_ARCH_NODEDATA_EXTENSION
489 config USE_PERCPU_NUMA_NODE_ID
493 config HAVE_MEMORYLESS_NODES
496 config ARCH_PROC_KCORE_TEXT
498 depends on PROC_KCORE
500 config IA64_MCA_RECOVERY
501 tristate "MCA recovery from errors other than TLB."
504 bool "Performance monitor support"
506 Selects whether support for the IA-64 performance monitor hardware
507 is included in the kernel. This makes some kernel data-structures a
508 little bigger and slows down execution a bit, but it is generally
509 a good idea to turn this on. If you're unsure, say Y.
512 tristate "/proc/pal support"
514 If you say Y here, you are able to get PAL (Processor Abstraction
515 Layer) information in /proc/pal. This contains useful information
516 about the processors in your systems, such as cache and TLB sizes
517 and the PAL firmware version in use.
519 To use this option, you have to ensure that the "/proc file system
520 support" (CONFIG_PROC_FS) is enabled, too.
522 config IA64_MC_ERR_INJECT
523 tristate "MC error injection support"
525 Adds support for MC error injection. If enabled, the kernel
526 will provide a sysfs interface for user applications to
527 call MC error injection PAL procedures to inject various errors.
528 This is a useful tool for MCA testing.
530 If you're unsure, do not select this option.
533 def_bool y if (IA64_SGI_SN2 || IA64_GENERIC)
536 bool "ESI (Extensible SAL Interface) support"
538 If you say Y here, support is built into the kernel to
539 make ESI calls. ESI calls are used to support vendor-specific
540 firmware extensions, such as the ability to inject memory-errors
541 for test-purposes. If you're unsure, say N.
543 config IA64_HP_AML_NFW
544 bool "Support ACPI AML calls to native firmware"
546 This driver installs a global ACPI Operation Region handler for
547 region 0xA1. AML methods can use this OpRegion to call arbitrary
548 native firmware functions. The driver installs the OpRegion
549 handler if there is an HPQ5001 device or if the user supplies
550 the "force" module parameter, e.g., with the "aml_nfw.force"
551 kernel command line option.
553 source "drivers/sn/Kconfig"
556 bool "kexec system call (EXPERIMENTAL)"
557 depends on EXPERIMENTAL && !IA64_HP_SIM && (!SMP || HOTPLUG_CPU)
559 kexec is a system call that implements the ability to shutdown your
560 current kernel, and to start another kernel. It is like a reboot
561 but it is independent of the system firmware. And like a reboot
562 you can start any kernel with it, not just Linux.
564 The name comes from the similarity to the exec system call.
566 It is an ongoing process to be certain the hardware in a machine
567 is properly shutdown, so do not be surprised if this code does not
568 initially work for you. It may help to enable device hotplugging
569 support. As of this writing the exact hardware interface is
570 strongly in flux, so no good recommendation can be made.
573 bool "kernel crash dumps"
574 depends on IA64_MCA_RECOVERY && !IA64_HP_SIM && (!SMP || HOTPLUG_CPU)
576 Generate crash dump after being started by kexec.
578 source "drivers/firmware/Kconfig"
580 source "fs/Kconfig.binfmt"
584 menu "Power management and ACPI options"
586 source "kernel/power/Kconfig"
588 source "drivers/acpi/Kconfig"
592 source "arch/ia64/kernel/cpufreq/Kconfig"
600 menu "Bus options (PCI, PCMCIA)"
605 Real IA-64 machines all have PCI/PCI-X/PCI Express busses. Say Y
606 here unless you are using a simulator without PCI support.
614 source "drivers/pci/pcie/Kconfig"
616 source "drivers/pci/Kconfig"
618 source "drivers/pci/hotplug/Kconfig"
620 source "drivers/pcmcia/Kconfig"
628 source "drivers/Kconfig"
630 source "arch/ia64/hp/sim/Kconfig"
633 tristate "Memory special operations driver"
635 select IA64_UNCACHED_ALLOCATOR
637 If you have an ia64 and you want to enable memory special
638 operations support (formerly known as fetchop), say Y here,
643 source "arch/ia64/Kconfig.debug"
645 source "security/Kconfig"
647 source "crypto/Kconfig"
649 source "arch/ia64/kvm/Kconfig"
654 def_bool (IA64_HP_ZX1 || IA64_HP_ZX1_SWIOTLB || IA64_GENERIC || SWIOTLB)