2 mainmenu "Linux Kernel Configuration for x86"
6 bool "64-bit kernel" if ARCH = "x86"
7 default ARCH = "x86_64"
9 Say yes to build a 64-bit kernel - formerly known as x86_64
10 Say no to build a 32-bit kernel - formerly known as i386
21 select HAVE_AOUT if X86_32
24 select HAVE_UNSTABLE_SCHED_CLOCK
27 select HAVE_PERF_EVENTS if (!M386 && !M486)
28 select HAVE_IOREMAP_PROT
30 select ARCH_WANT_OPTIONAL_GPIOLIB
31 select ARCH_WANT_FRAME_POINTERS
33 select HAVE_KRETPROBES
35 select HAVE_FTRACE_MCOUNT_RECORD
36 select HAVE_DYNAMIC_FTRACE
37 select HAVE_FUNCTION_TRACER
38 select HAVE_FUNCTION_GRAPH_TRACER
39 select HAVE_FUNCTION_GRAPH_FP_TEST
40 select HAVE_FUNCTION_TRACE_MCOUNT_TEST
41 select HAVE_FTRACE_NMI_ENTER if DYNAMIC_FTRACE
42 select HAVE_SYSCALL_TRACEPOINTS
45 select HAVE_ARCH_TRACEHOOK
46 select HAVE_GENERIC_DMA_COHERENT if X86_32
47 select HAVE_EFFICIENT_UNALIGNED_ACCESS
48 select USER_STACKTRACE_SUPPORT
49 select HAVE_REGS_AND_STACK_ACCESS_API
50 select HAVE_DMA_API_DEBUG
51 select HAVE_KERNEL_GZIP
52 select HAVE_KERNEL_BZIP2
53 select HAVE_KERNEL_LZMA
54 select HAVE_KERNEL_LZO
55 select HAVE_HW_BREAKPOINT
56 select HAVE_MIXED_BREAKPOINTS_REGS
58 select HAVE_PERF_EVENTS_NMI
60 select HAVE_ARCH_KMEMCHECK
61 select HAVE_USER_RETURN_NOTIFIER
63 config INSTRUCTION_DECODER
64 def_bool (KPROBES || PERF_EVENTS)
68 default "elf32-i386" if X86_32
69 default "elf64-x86-64" if X86_64
73 default "arch/x86/configs/i386_defconfig" if X86_32
74 default "arch/x86/configs/x86_64_defconfig" if X86_64
76 config GENERIC_CMOS_UPDATE
79 config CLOCKSOURCE_WATCHDOG
82 config GENERIC_CLOCKEVENTS
85 config GENERIC_CLOCKEVENTS_BROADCAST
87 depends on X86_64 || (X86_32 && X86_LOCAL_APIC)
89 config LOCKDEP_SUPPORT
92 config STACKTRACE_SUPPORT
95 config HAVE_LATENCYTOP_SUPPORT
107 config NEED_DMA_MAP_STATE
108 def_bool (X86_64 || DMAR || DMA_API_DEBUG)
110 config NEED_SG_DMA_LENGTH
113 config GENERIC_ISA_DMA
122 select GENERIC_BUG_RELATIVE_POINTERS if X86_64
124 config GENERIC_BUG_RELATIVE_POINTERS
127 config GENERIC_HWEIGHT
133 config ARCH_MAY_HAVE_PC_FDC
136 config RWSEM_GENERIC_SPINLOCK
139 config RWSEM_XCHGADD_ALGORITHM
142 config ARCH_HAS_CPU_IDLE_WAIT
145 config GENERIC_CALIBRATE_DELAY
148 config GENERIC_TIME_VSYSCALL
152 config ARCH_HAS_CPU_RELAX
155 config ARCH_HAS_DEFAULT_IDLE
158 config ARCH_HAS_CACHE_LINE_SIZE
161 config HAVE_SETUP_PER_CPU_AREA
164 config NEED_PER_CPU_EMBED_FIRST_CHUNK
167 config NEED_PER_CPU_PAGE_FIRST_CHUNK
170 config HAVE_CPUMASK_OF_CPU_MAP
173 config ARCH_HIBERNATION_POSSIBLE
176 config ARCH_SUSPEND_POSSIBLE
183 config ARCH_POPULATES_NODE_MAP
190 config ARCH_SUPPORTS_OPTIMIZED_INLINING
193 config ARCH_SUPPORTS_DEBUG_PAGEALLOC
196 config HAVE_EARLY_RES
199 config HAVE_INTEL_TXT
201 depends on EXPERIMENTAL && DMAR && ACPI
203 # Use the generic interrupt handling code in kernel/irq/:
204 config GENERIC_HARDIRQS
207 config GENERIC_HARDIRQS_NO__DO_IRQ
210 config GENERIC_IRQ_PROBE
213 config GENERIC_PENDING_IRQ
215 depends on GENERIC_HARDIRQS && SMP
217 config USE_GENERIC_SMP_HELPERS
223 depends on X86_32 && SMP
227 depends on X86_64 && SMP
233 config X86_TRAMPOLINE
235 depends on SMP || (64BIT && ACPI_SLEEP)
237 config X86_32_LAZY_GS
239 depends on X86_32 && !CC_STACKPROTECTOR
241 config ARCH_HWEIGHT_CFLAGS
243 default "-fcall-saved-ecx -fcall-saved-edx" if X86_32
244 default "-fcall-saved-rdi -fcall-saved-rsi -fcall-saved-rdx -fcall-saved-rcx -fcall-saved-r8 -fcall-saved-r9 -fcall-saved-r10 -fcall-saved-r11" if X86_64
249 config ARCH_CPU_PROBE_RELEASE
251 depends on HOTPLUG_CPU
253 source "init/Kconfig"
254 source "kernel/Kconfig.freezer"
256 menu "Processor type and features"
258 source "kernel/time/Kconfig"
261 bool "Symmetric multi-processing support"
263 This enables support for systems with more than one CPU. If you have
264 a system with only one CPU, like most personal computers, say N. If
265 you have a system with more than one CPU, say Y.
267 If you say N here, the kernel will run on single and multiprocessor
268 machines, but will use only one CPU of a multiprocessor machine. If
269 you say Y here, the kernel will run on many, but not all,
270 singleprocessor machines. On a singleprocessor machine, the kernel
271 will run faster if you say N here.
273 Note that if you say Y here and choose architecture "586" or
274 "Pentium" under "Processor family", the kernel will not work on 486
275 architectures. Similarly, multiprocessor kernels for the "PPro"
276 architecture may not work on all Pentium based boards.
278 People using multiprocessor machines who say Y here should also say
279 Y to "Enhanced Real Time Clock Support", below. The "Advanced Power
280 Management" code will be disabled if you say Y here.
282 See also <file:Documentation/i386/IO-APIC.txt>,
283 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
284 <http://www.tldp.org/docs.html#howto>.
286 If you don't know what to do here, say N.
289 bool "Support x2apic"
290 depends on X86_LOCAL_APIC && X86_64 && INTR_REMAP
292 This enables x2apic support on CPUs that have this feature.
294 This allows 32-bit apic IDs (so it can support very large systems),
295 and accesses the local apic via MSRs not via mmio.
297 If you don't know what to do here, say N.
300 bool "Support sparse irq numbering"
301 depends on PCI_MSI || HT_IRQ
303 This enables support for sparse irqs. This is useful for distro
304 kernels that want to define a high CONFIG_NR_CPUS value but still
305 want to have low kernel memory footprint on smaller machines.
307 ( Sparse IRQs can also be beneficial on NUMA boxes, as they spread
308 out the irq_desc[] array in a more NUMA-friendly way. )
310 If you don't know what to do here, say N.
314 depends on SPARSE_IRQ && NUMA
317 bool "Enable MPS table" if ACPI
319 depends on X86_LOCAL_APIC
321 For old smp systems that do not have proper acpi support. Newer systems
322 (esp with 64bit cpus) with acpi support, MADT and DSDT will override it
325 bool "Support for big SMP systems with more than 8 CPUs"
326 depends on X86_32 && SMP
328 This option is needed for the systems that have more than 8 CPUs
331 config X86_EXTENDED_PLATFORM
332 bool "Support for extended (non-PC) x86 platforms"
335 If you disable this option then the kernel will only support
336 standard PC platforms. (which covers the vast majority of
339 If you enable this option then you'll be able to select support
340 for the following (non-PC) 32 bit x86 platforms:
344 SGI 320/540 (Visual Workstation)
345 Summit/EXA (IBM x440)
346 Unisys ES7000 IA32 series
347 Moorestown MID devices
349 If you have one of these systems, or if you want to build a
350 generic distribution kernel, say Y here - otherwise say N.
354 config X86_EXTENDED_PLATFORM
355 bool "Support for extended (non-PC) x86 platforms"
358 If you disable this option then the kernel will only support
359 standard PC platforms. (which covers the vast majority of
362 If you enable this option then you'll be able to select support
363 for the following (non-PC) 64 bit x86 platforms:
367 If you have one of these systems, or if you want to build a
368 generic distribution kernel, say Y here - otherwise say N.
370 # This is an alphabetically sorted list of 64 bit extended platforms
371 # Please maintain the alphabetic order if and when there are additions
376 depends on X86_64 && PCI
377 depends on X86_EXTENDED_PLATFORM
379 Support for ScaleMP vSMP systems. Say 'Y' here if this kernel is
380 supposed to run on these EM64T-based machines. Only choose this option
381 if you have one of these machines.
384 bool "SGI Ultraviolet"
386 depends on X86_EXTENDED_PLATFORM
388 depends on X86_X2APIC
390 This option is needed in order to support SGI Ultraviolet systems.
391 If you don't have one of these, you should say N here.
393 # Following is an alphabetically sorted list of 32 bit extended platforms
394 # Please maintain the alphabetic order if and when there are additions
399 depends on X86_EXTENDED_PLATFORM
401 Select this for an AMD Elan processor.
403 Do not use this option for K6/Athlon/Opteron processors!
405 If unsure, choose "PC-compatible" instead.
408 bool "Moorestown MID platform"
412 depends on X86_EXTENDED_PLATFORM
413 depends on X86_IO_APIC
416 Moorestown is Intel's Low Power Intel Architecture (LPIA) based Moblin
417 Internet Device(MID) platform. Moorestown consists of two chips:
418 Lincroft (CPU core, graphics, and memory controller) and Langwell IOH.
419 Unlike standard x86 PCs, Moorestown does not have many legacy devices
420 nor standard legacy replacement devices/features. e.g. Moorestown does
421 not contain i8259, i8254, HPET, legacy BIOS, most of the io ports.
424 bool "RDC R-321x SoC"
426 depends on X86_EXTENDED_PLATFORM
428 select X86_REBOOTFIXUPS
430 This option is needed for RDC R-321x system-on-chip, also known
432 If you don't have one of these chips, you should say N here.
434 config X86_32_NON_STANDARD
435 bool "Support non-standard 32-bit SMP architectures"
436 depends on X86_32 && SMP
437 depends on X86_EXTENDED_PLATFORM
439 This option compiles in the NUMAQ, Summit, bigsmp, ES7000, default
440 subarchitectures. It is intended for a generic binary kernel.
441 if you select them all, kernel will probe it one by one. and will
444 # Alphabetically sorted list of Non standard 32 bit platforms
447 bool "NUMAQ (IBM/Sequent)"
448 depends on X86_32_NON_STANDARD
453 This option is used for getting Linux to run on a NUMAQ (IBM/Sequent)
454 NUMA multiquad box. This changes the way that processors are
455 bootstrapped, and uses Clustered Logical APIC addressing mode instead
456 of Flat Logical. You will need a new lynxer.elf file to flash your
457 firmware with - send email to <Martin.Bligh@us.ibm.com>.
459 config X86_SUPPORTS_MEMORY_FAILURE
461 # MCE code calls memory_failure():
463 # On 32-bit this adds too big of NODES_SHIFT and we run out of page flags:
464 depends on !X86_NUMAQ
465 # On 32-bit SPARSEMEM adds too big of SECTIONS_WIDTH:
466 depends on X86_64 || !SPARSEMEM
467 select ARCH_SUPPORTS_MEMORY_FAILURE
470 bool "SGI 320/540 (Visual Workstation)"
471 depends on X86_32 && PCI && X86_MPPARSE && PCI_GODIRECT
472 depends on X86_32_NON_STANDARD
474 The SGI Visual Workstation series is an IA32-based workstation
475 based on SGI systems chips with some legacy PC hardware attached.
477 Say Y here to create a kernel to run on the SGI 320 or 540.
479 A kernel compiled for the Visual Workstation will run on general
480 PCs as well. See <file:Documentation/sgi-visws.txt> for details.
483 bool "Summit/EXA (IBM x440)"
484 depends on X86_32_NON_STANDARD
486 This option is needed for IBM systems that use the Summit/EXA chipset.
487 In particular, it is needed for the x440.
490 bool "Unisys ES7000 IA32 series"
491 depends on X86_32_NON_STANDARD && X86_BIGSMP
493 Support for Unisys ES7000 systems. Say 'Y' here if this kernel is
494 supposed to run on an IA32-based Unisys ES7000 system.
496 config SCHED_OMIT_FRAME_POINTER
498 prompt "Single-depth WCHAN output"
501 Calculate simpler /proc/<PID>/wchan values. If this option
502 is disabled then wchan values will recurse back to the
503 caller function. This provides more accurate wchan values,
504 at the expense of slightly more scheduling overhead.
506 If in doubt, say "Y".
508 menuconfig PARAVIRT_GUEST
509 bool "Paravirtualized guest support"
511 Say Y here to get to see options related to running Linux under
512 various hypervisors. This option alone does not add any kernel code.
514 If you say N, all options in this submenu will be skipped and disabled.
518 source "arch/x86/xen/Kconfig"
521 bool "VMI Guest support (DEPRECATED)"
525 VMI provides a paravirtualized interface to the VMware ESX server
526 (it could be used by other hypervisors in theory too, but is not
527 at the moment), by linking the kernel to a GPL-ed ROM module
528 provided by the hypervisor.
530 As of September 2009, VMware has started a phased retirement
531 of this feature from VMware's products. Please see
532 feature-removal-schedule.txt for details. If you are
533 planning to enable this option, please note that you cannot
534 live migrate a VMI enabled VM to a future VMware product,
535 which doesn't support VMI. So if you expect your kernel to
536 seamlessly migrate to newer VMware products, keep this
540 bool "KVM paravirtualized clock"
542 select PARAVIRT_CLOCK
544 Turning on this option will allow you to run a paravirtualized clock
545 when running over the KVM hypervisor. Instead of relying on a PIT
546 (or probably other) emulation by the underlying device model, the host
547 provides the guest with timing infrastructure such as time of day, and
551 bool "KVM Guest support"
554 This option enables various optimizations for running under the KVM
557 source "arch/x86/lguest/Kconfig"
560 bool "Enable paravirtualization code"
562 This changes the kernel so it can modify itself when it is run
563 under a hypervisor, potentially improving performance significantly
564 over full virtualization. However, when run without a hypervisor
565 the kernel is theoretically slower and slightly larger.
567 config PARAVIRT_SPINLOCKS
568 bool "Paravirtualization layer for spinlocks"
569 depends on PARAVIRT && SMP && EXPERIMENTAL
571 Paravirtualized spinlocks allow a pvops backend to replace the
572 spinlock implementation with something virtualization-friendly
573 (for example, block the virtual CPU rather than spinning).
575 Unfortunately the downside is an up to 5% performance hit on
576 native kernels, with various workloads.
578 If you are unsure how to answer this question, answer N.
580 config PARAVIRT_CLOCK
585 config PARAVIRT_DEBUG
586 bool "paravirt-ops debugging"
587 depends on PARAVIRT && DEBUG_KERNEL
589 Enable to debug paravirt_ops internals. Specifically, BUG if
590 a paravirt_op is missing when it is called.
594 bool "Disable Bootmem code"
596 Use early_res directly instead of bootmem before slab is ready.
597 - allocator (buddy) [generic]
598 - early allocator (bootmem) [generic]
599 - very early allocator (reserve_early*()) [x86]
600 - very very early allocator (early brk model) [x86]
601 So reduce one layer between early allocator to final allocator
607 This option adds a kernel parameter 'memtest', which allows memtest
609 memtest=0, mean disabled; -- default
610 memtest=1, mean do 1 test pattern;
612 memtest=4, mean do 4 test patterns.
613 If you are unsure how to answer this question, answer N.
615 config X86_SUMMIT_NUMA
617 depends on X86_32 && NUMA && X86_32_NON_STANDARD
619 config X86_CYCLONE_TIMER
621 depends on X86_32_NON_STANDARD
623 source "arch/x86/Kconfig.cpu"
627 prompt "HPET Timer Support" if X86_32
629 Use the IA-PC HPET (High Precision Event Timer) to manage
630 time in preference to the PIT and RTC, if a HPET is
632 HPET is the next generation timer replacing legacy 8254s.
633 The HPET provides a stable time base on SMP
634 systems, unlike the TSC, but it is more expensive to access,
635 as it is off-chip. You can find the HPET spec at
636 <http://www.intel.com/hardwaredesign/hpetspec_1.pdf>.
638 You can safely choose Y here. However, HPET will only be
639 activated if the platform and the BIOS support this feature.
640 Otherwise the 8254 will be used for timing services.
642 Choose N to continue using the legacy 8254 timer.
644 config HPET_EMULATE_RTC
646 depends on HPET_TIMER && (RTC=y || RTC=m || RTC_DRV_CMOS=m || RTC_DRV_CMOS=y)
650 prompt "Langwell APB Timer Support" if X86_MRST
652 APB timer is the replacement for 8254, HPET on X86 MID platforms.
653 The APBT provides a stable time base on SMP
654 systems, unlike the TSC, but it is more expensive to access,
655 as it is off-chip. APB timers are always running regardless of CPU
656 C states, they are used as per CPU clockevent device when possible.
658 # Mark as embedded because too many people got it wrong.
659 # The code disables itself when not needed.
662 bool "Enable DMI scanning" if EMBEDDED
664 Enabled scanning of DMI to identify machine quirks. Say Y
665 here unless you have verified that your setup is not
666 affected by entries in the DMI blacklist. Required by PNP
670 bool "GART IOMMU support" if EMBEDDED
673 depends on X86_64 && PCI && K8_NB
675 Support for full DMA access of devices with 32bit memory access only
676 on systems with more than 3GB. This is usually needed for USB,
677 sound, many IDE/SATA chipsets and some other devices.
678 Provides a driver for the AMD Athlon64/Opteron/Turion/Sempron GART
679 based hardware IOMMU and a software bounce buffer based IOMMU used
680 on Intel systems and as fallback.
681 The code is only active when needed (enough memory and limited
682 device) unless CONFIG_IOMMU_DEBUG or iommu=force is specified
686 bool "IBM Calgary IOMMU support"
688 depends on X86_64 && PCI && EXPERIMENTAL
690 Support for hardware IOMMUs in IBM's xSeries x366 and x460
691 systems. Needed to run systems with more than 3GB of memory
692 properly with 32-bit PCI devices that do not support DAC
693 (Double Address Cycle). Calgary also supports bus level
694 isolation, where all DMAs pass through the IOMMU. This
695 prevents them from going anywhere except their intended
696 destination. This catches hard-to-find kernel bugs and
697 mis-behaving drivers and devices that do not use the DMA-API
698 properly to set up their DMA buffers. The IOMMU can be
699 turned off at boot time with the iommu=off parameter.
700 Normally the kernel will make the right choice by itself.
703 config CALGARY_IOMMU_ENABLED_BY_DEFAULT
705 prompt "Should Calgary be enabled by default?"
706 depends on CALGARY_IOMMU
708 Should Calgary be enabled by default? if you choose 'y', Calgary
709 will be used (if it exists). If you choose 'n', Calgary will not be
710 used even if it exists. If you choose 'n' and would like to use
711 Calgary anyway, pass 'iommu=calgary' on the kernel command line.
715 bool "AMD IOMMU support"
718 depends on X86_64 && PCI && ACPI
720 With this option you can enable support for AMD IOMMU hardware in
721 your system. An IOMMU is a hardware component which provides
722 remapping of DMA memory accesses from devices. With an AMD IOMMU you
723 can isolate the the DMA memory of different devices and protect the
724 system from misbehaving device drivers or hardware.
726 You can find out if your system has an AMD IOMMU if you look into
727 your BIOS for an option to enable it or if you have an IVRS ACPI
730 config AMD_IOMMU_STATS
731 bool "Export AMD IOMMU statistics to debugfs"
735 This option enables code in the AMD IOMMU driver to collect various
736 statistics about whats happening in the driver and exports that
737 information to userspace via debugfs.
740 # need this always selected by IOMMU for the VIA workaround
744 Support for software bounce buffers used on x86-64 systems
745 which don't have a hardware IOMMU (e.g. the current generation
746 of Intel's x86-64 CPUs). Using this PCI devices which can only
747 access 32-bits of memory can be used on systems with more than
748 3 GB of memory. If unsure, say Y.
751 def_bool (CALGARY_IOMMU || GART_IOMMU || SWIOTLB || AMD_IOMMU)
754 def_bool (AMD_IOMMU || DMAR)
757 bool "Enable Maximum number of SMP Processors and NUMA Nodes"
758 depends on X86_64 && SMP && DEBUG_KERNEL && EXPERIMENTAL
759 select CPUMASK_OFFSTACK
761 Enable maximum number of CPUS and NUMA Nodes for this architecture.
765 int "Maximum number of CPUs" if SMP && !MAXSMP
766 range 2 8 if SMP && X86_32 && !X86_BIGSMP
767 range 2 512 if SMP && !MAXSMP
769 default "4096" if MAXSMP
770 default "32" if SMP && (X86_NUMAQ || X86_SUMMIT || X86_BIGSMP || X86_ES7000)
773 This allows you to specify the maximum number of CPUs which this
774 kernel will support. The maximum supported value is 512 and the
775 minimum value which makes sense is 2.
777 This is purely to save memory - each supported CPU adds
778 approximately eight kilobytes to the kernel image.
781 bool "SMT (Hyperthreading) scheduler support"
784 SMT scheduler support improves the CPU scheduler's decision making
785 when dealing with Intel Pentium 4 chips with HyperThreading at a
786 cost of slightly increased overhead in some places. If unsure say
791 prompt "Multi-core scheduler support"
794 Multi-core scheduler support improves the CPU scheduler's decision
795 making when dealing with multi-core CPU chips at a cost of slightly
796 increased overhead in some places. If unsure say N here.
798 config IRQ_TIME_ACCOUNTING
799 bool "Fine granularity task level IRQ time accounting"
802 Select this option to enable fine granularity task irq time
803 accounting. This is done by reading a timestamp on each
804 transitions between softirq and hardirq state, so there can be a
805 small performance impact.
807 If in doubt, say N here.
809 source "kernel/Kconfig.preempt"
812 bool "Local APIC support on uniprocessors"
813 depends on X86_32 && !SMP && !X86_32_NON_STANDARD
815 A local APIC (Advanced Programmable Interrupt Controller) is an
816 integrated interrupt controller in the CPU. If you have a single-CPU
817 system which has a processor with a local APIC, you can say Y here to
818 enable and use it. If you say Y here even though your machine doesn't
819 have a local APIC, then the kernel will still run with no slowdown at
820 all. The local APIC supports CPU-generated self-interrupts (timer,
821 performance counters), and the NMI watchdog which detects hard
825 bool "IO-APIC support on uniprocessors"
826 depends on X86_UP_APIC
828 An IO-APIC (I/O Advanced Programmable Interrupt Controller) is an
829 SMP-capable replacement for PC-style interrupt controllers. Most
830 SMP systems and many recent uniprocessor systems have one.
832 If you have a single-CPU system with an IO-APIC, you can say Y here
833 to use it. If you say Y here even though your machine doesn't have
834 an IO-APIC, then the kernel will still run with no slowdown at all.
836 config X86_LOCAL_APIC
838 depends on X86_64 || SMP || X86_32_NON_STANDARD || X86_UP_APIC
842 depends on X86_64 || SMP || X86_32_NON_STANDARD || X86_UP_APIC
844 config X86_VISWS_APIC
846 depends on X86_32 && X86_VISWS
848 config X86_REROUTE_FOR_BROKEN_BOOT_IRQS
849 bool "Reroute for broken boot IRQs"
850 depends on X86_IO_APIC
852 This option enables a workaround that fixes a source of
853 spurious interrupts. This is recommended when threaded
854 interrupt handling is used on systems where the generation of
855 superfluous "boot interrupts" cannot be disabled.
857 Some chipsets generate a legacy INTx "boot IRQ" when the IRQ
858 entry in the chipset's IO-APIC is masked (as, e.g. the RT
859 kernel does during interrupt handling). On chipsets where this
860 boot IRQ generation cannot be disabled, this workaround keeps
861 the original IRQ line masked so that only the equivalent "boot
862 IRQ" is delivered to the CPUs. The workaround also tells the
863 kernel to set up the IRQ handler on the boot IRQ line. In this
864 way only one interrupt is delivered to the kernel. Otherwise
865 the spurious second interrupt may cause the kernel to bring
866 down (vital) interrupt lines.
868 Only affects "broken" chipsets. Interrupt sharing may be
869 increased on these systems.
872 bool "Machine Check / overheating reporting"
874 Machine Check support allows the processor to notify the
875 kernel if it detects a problem (e.g. overheating, data corruption).
876 The action the kernel takes depends on the severity of the problem,
877 ranging from warning messages to halting the machine.
881 prompt "Intel MCE features"
882 depends on X86_MCE && X86_LOCAL_APIC
884 Additional support for intel specific MCE features such as
889 prompt "AMD MCE features"
890 depends on X86_MCE && X86_LOCAL_APIC
892 Additional support for AMD specific MCE features such as
893 the DRAM Error Threshold.
895 config X86_ANCIENT_MCE
896 bool "Support for old Pentium 5 / WinChip machine checks"
897 depends on X86_32 && X86_MCE
899 Include support for machine check handling on old Pentium 5 or WinChip
900 systems. These typically need to be enabled explicitely on the command
903 config X86_MCE_THRESHOLD
904 depends on X86_MCE_AMD || X86_MCE_INTEL
907 config X86_MCE_INJECT
909 tristate "Machine check injector support"
911 Provide support for injecting machine checks for testing purposes.
912 If you don't know what a machine check is and you don't do kernel
913 QA it is safe to say n.
915 config X86_THERMAL_VECTOR
917 depends on X86_MCE_INTEL
920 bool "Enable VM86 support" if EMBEDDED
924 This option is required by programs like DOSEMU to run 16-bit legacy
925 code on X86 processors. It also may be needed by software like
926 XFree86 to initialize some video cards via BIOS. Disabling this
927 option saves about 6k.
930 tristate "Toshiba Laptop support"
933 This adds a driver to safely access the System Management Mode of
934 the CPU on Toshiba portables with a genuine Toshiba BIOS. It does
935 not work on models with a Phoenix BIOS. The System Management Mode
936 is used to set the BIOS and power saving options on Toshiba portables.
938 For information on utilities to make use of this driver see the
939 Toshiba Linux utilities web site at:
940 <http://www.buzzard.org.uk/toshiba/>.
942 Say Y if you intend to run this kernel on a Toshiba portable.
946 tristate "Dell laptop support"
948 This adds a driver to safely access the System Management Mode
949 of the CPU on the Dell Inspiron 8000. The System Management Mode
950 is used to read cpu temperature and cooling fan status and to
951 control the fans on the I8K portables.
953 This driver has been tested only on the Inspiron 8000 but it may
954 also work with other Dell laptops. You can force loading on other
955 models by passing the parameter `force=1' to the module. Use at
958 For information on utilities to make use of this driver see the
959 I8K Linux utilities web site at:
960 <http://people.debian.org/~dz/i8k/>
962 Say Y if you intend to run this kernel on a Dell Inspiron 8000.
965 config X86_REBOOTFIXUPS
966 bool "Enable X86 board specific fixups for reboot"
969 This enables chipset and/or board specific fixups to be done
970 in order to get reboot to work correctly. This is only needed on
971 some combinations of hardware and BIOS. The symptom, for which
972 this config is intended, is when reboot ends with a stalled/hung
975 Currently, the only fixup is for the Geode machines using
976 CS5530A and CS5536 chipsets and the RDC R-321x SoC.
978 Say Y if you want to enable the fixup. Currently, it's safe to
979 enable this option even if you don't need it.
983 tristate "/dev/cpu/microcode - microcode support"
986 If you say Y here, you will be able to update the microcode on
987 certain Intel and AMD processors. The Intel support is for the
988 IA32 family, e.g. Pentium Pro, Pentium II, Pentium III,
989 Pentium 4, Xeon etc. The AMD support is for family 0x10 and
990 0x11 processors, e.g. Opteron, Phenom and Turion 64 Ultra.
991 You will obviously need the actual microcode binary data itself
992 which is not shipped with the Linux kernel.
994 This option selects the general module only, you need to select
995 at least one vendor specific module as well.
997 To compile this driver as a module, choose M here: the
998 module will be called microcode.
1000 config MICROCODE_INTEL
1001 bool "Intel microcode patch loading support"
1002 depends on MICROCODE
1006 This options enables microcode patch loading support for Intel
1009 For latest news and information on obtaining all the required
1010 Intel ingredients for this driver, check:
1011 <http://www.urbanmyth.org/microcode/>.
1013 config MICROCODE_AMD
1014 bool "AMD microcode patch loading support"
1015 depends on MICROCODE
1018 If you select this option, microcode patch loading support for AMD
1019 processors will be enabled.
1021 config MICROCODE_OLD_INTERFACE
1023 depends on MICROCODE
1026 tristate "/dev/cpu/*/msr - Model-specific register support"
1028 This device gives privileged processes access to the x86
1029 Model-Specific Registers (MSRs). It is a character device with
1030 major 202 and minors 0 to 31 for /dev/cpu/0/msr to /dev/cpu/31/msr.
1031 MSR accesses are directed to a specific CPU on multi-processor
1035 tristate "/dev/cpu/*/cpuid - CPU information support"
1037 This device gives processes access to the x86 CPUID instruction to
1038 be executed on a specific processor. It is a character device
1039 with major 203 and minors 0 to 31 for /dev/cpu/0/cpuid to
1043 prompt "High Memory Support"
1044 default HIGHMEM64G if X86_NUMAQ
1050 depends on !X86_NUMAQ
1052 Linux can use up to 64 Gigabytes of physical memory on x86 systems.
1053 However, the address space of 32-bit x86 processors is only 4
1054 Gigabytes large. That means that, if you have a large amount of
1055 physical memory, not all of it can be "permanently mapped" by the
1056 kernel. The physical memory that's not permanently mapped is called
1059 If you are compiling a kernel which will never run on a machine with
1060 more than 1 Gigabyte total physical RAM, answer "off" here (default
1061 choice and suitable for most users). This will result in a "3GB/1GB"
1062 split: 3GB are mapped so that each process sees a 3GB virtual memory
1063 space and the remaining part of the 4GB virtual memory space is used
1064 by the kernel to permanently map as much physical memory as
1067 If the machine has between 1 and 4 Gigabytes physical RAM, then
1070 If more than 4 Gigabytes is used then answer "64GB" here. This
1071 selection turns Intel PAE (Physical Address Extension) mode on.
1072 PAE implements 3-level paging on IA32 processors. PAE is fully
1073 supported by Linux, PAE mode is implemented on all recent Intel
1074 processors (Pentium Pro and better). NOTE: If you say "64GB" here,
1075 then the kernel will not boot on CPUs that don't support PAE!
1077 The actual amount of total physical memory will either be
1078 auto detected or can be forced by using a kernel command line option
1079 such as "mem=256M". (Try "man bootparam" or see the documentation of
1080 your boot loader (lilo or loadlin) about how to pass options to the
1081 kernel at boot time.)
1083 If unsure, say "off".
1087 depends on !X86_NUMAQ
1089 Select this if you have a 32-bit processor and between 1 and 4
1090 gigabytes of physical RAM.
1094 depends on !M386 && !M486
1097 Select this if you have a 32-bit processor and more than 4
1098 gigabytes of physical RAM.
1103 depends on EXPERIMENTAL
1104 prompt "Memory split" if EMBEDDED
1108 Select the desired split between kernel and user memory.
1110 If the address range available to the kernel is less than the
1111 physical memory installed, the remaining memory will be available
1112 as "high memory". Accessing high memory is a little more costly
1113 than low memory, as it needs to be mapped into the kernel first.
1114 Note that increasing the kernel address space limits the range
1115 available to user programs, making the address space there
1116 tighter. Selecting anything other than the default 3G/1G split
1117 will also likely make your kernel incompatible with binary-only
1120 If you are not absolutely sure what you are doing, leave this
1124 bool "3G/1G user/kernel split"
1125 config VMSPLIT_3G_OPT
1127 bool "3G/1G user/kernel split (for full 1G low memory)"
1129 bool "2G/2G user/kernel split"
1130 config VMSPLIT_2G_OPT
1132 bool "2G/2G user/kernel split (for full 2G low memory)"
1134 bool "1G/3G user/kernel split"
1139 default 0xB0000000 if VMSPLIT_3G_OPT
1140 default 0x80000000 if VMSPLIT_2G
1141 default 0x78000000 if VMSPLIT_2G_OPT
1142 default 0x40000000 if VMSPLIT_1G
1148 depends on X86_32 && (HIGHMEM64G || HIGHMEM4G)
1151 bool "PAE (Physical Address Extension) Support"
1152 depends on X86_32 && !HIGHMEM4G
1154 PAE is required for NX support, and furthermore enables
1155 larger swapspace support for non-overcommit purposes. It
1156 has the cost of more pagetable lookup overhead, and also
1157 consumes more pagetable space per process.
1159 config ARCH_PHYS_ADDR_T_64BIT
1160 def_bool X86_64 || X86_PAE
1162 config DIRECT_GBPAGES
1163 bool "Enable 1GB pages for kernel pagetables" if EMBEDDED
1167 Allow the kernel linear mapping to use 1GB pages on CPUs that
1168 support it. This can improve the kernel's performance a tiny bit by
1169 reducing TLB pressure. If in doubt, say "Y".
1171 # Common NUMA Features
1173 bool "Numa Memory Allocation and Scheduler Support"
1175 depends on X86_64 || (X86_32 && HIGHMEM64G && (X86_NUMAQ || X86_BIGSMP || X86_SUMMIT && ACPI) && EXPERIMENTAL)
1176 default y if (X86_NUMAQ || X86_SUMMIT || X86_BIGSMP)
1178 Enable NUMA (Non Uniform Memory Access) support.
1180 The kernel will try to allocate memory used by a CPU on the
1181 local memory controller of the CPU and add some more
1182 NUMA awareness to the kernel.
1184 For 64-bit this is recommended if the system is Intel Core i7
1185 (or later), AMD Opteron, or EM64T NUMA.
1187 For 32-bit this is only needed on (rare) 32-bit-only platforms
1188 that support NUMA topologies, such as NUMAQ / Summit, or if you
1189 boot a 32-bit kernel on a 64-bit NUMA platform.
1191 Otherwise, you should say N.
1193 comment "NUMA (Summit) requires SMP, 64GB highmem support, ACPI"
1194 depends on X86_32 && X86_SUMMIT && (!HIGHMEM64G || !ACPI)
1198 prompt "Old style AMD Opteron NUMA detection"
1199 depends on X86_64 && NUMA && PCI
1201 Enable K8 NUMA node topology detection. You should say Y here if
1202 you have a multi processor AMD K8 system. This uses an old
1203 method to read the NUMA configuration directly from the builtin
1204 Northbridge of Opteron. It is recommended to use X86_64_ACPI_NUMA
1205 instead, which also takes priority if both are compiled in.
1207 config X86_64_ACPI_NUMA
1209 prompt "ACPI NUMA detection"
1210 depends on X86_64 && NUMA && ACPI && PCI
1213 Enable ACPI SRAT based node topology detection.
1215 # Some NUMA nodes have memory ranges that span
1216 # other nodes. Even though a pfn is valid and
1217 # between a node's start and end pfns, it may not
1218 # reside on that node. See memmap_init_zone()
1220 config NODES_SPAN_OTHER_NODES
1222 depends on X86_64_ACPI_NUMA
1225 bool "NUMA emulation"
1226 depends on X86_64 && NUMA
1228 Enable NUMA emulation. A flat machine will be split
1229 into virtual nodes when booted with "numa=fake=N", where N is the
1230 number of nodes. This is only useful for debugging.
1233 int "Maximum NUMA Nodes (as a power of 2)" if !MAXSMP
1235 default "10" if MAXSMP
1236 default "6" if X86_64
1237 default "4" if X86_NUMAQ
1239 depends on NEED_MULTIPLE_NODES
1241 Specify the maximum number of NUMA Nodes available on the target
1242 system. Increases memory reserved to accommodate various tables.
1244 config HAVE_ARCH_BOOTMEM
1246 depends on X86_32 && NUMA
1248 config ARCH_HAVE_MEMORY_PRESENT
1250 depends on X86_32 && DISCONTIGMEM
1252 config NEED_NODE_MEMMAP_SIZE
1254 depends on X86_32 && (DISCONTIGMEM || SPARSEMEM)
1256 config HAVE_ARCH_ALLOC_REMAP
1258 depends on X86_32 && NUMA
1260 config ARCH_FLATMEM_ENABLE
1262 depends on X86_32 && ARCH_SELECT_MEMORY_MODEL && !NUMA
1264 config ARCH_DISCONTIGMEM_ENABLE
1266 depends on NUMA && X86_32
1268 config ARCH_DISCONTIGMEM_DEFAULT
1270 depends on NUMA && X86_32
1272 config ARCH_PROC_KCORE_TEXT
1274 depends on X86_64 && PROC_KCORE
1276 config ARCH_SPARSEMEM_DEFAULT
1280 config ARCH_SPARSEMEM_ENABLE
1282 depends on X86_64 || NUMA || (EXPERIMENTAL && X86_32) || X86_32_NON_STANDARD
1283 select SPARSEMEM_STATIC if X86_32
1284 select SPARSEMEM_VMEMMAP_ENABLE if X86_64
1286 config ARCH_SELECT_MEMORY_MODEL
1288 depends on ARCH_SPARSEMEM_ENABLE
1290 config ARCH_MEMORY_PROBE
1292 depends on MEMORY_HOTPLUG
1294 config ILLEGAL_POINTER_VALUE
1297 default 0xdead000000000000 if X86_64
1302 bool "Allocate 3rd-level pagetables from highmem"
1305 The VM uses one page table entry for each page of physical memory.
1306 For systems with a lot of RAM, this can be wasteful of precious
1307 low memory. Setting this option will put user-space page table
1308 entries in high memory.
1310 config X86_CHECK_BIOS_CORRUPTION
1311 bool "Check for low memory corruption"
1313 Periodically check for memory corruption in low memory, which
1314 is suspected to be caused by BIOS. Even when enabled in the
1315 configuration, it is disabled at runtime. Enable it by
1316 setting "memory_corruption_check=1" on the kernel command
1317 line. By default it scans the low 64k of memory every 60
1318 seconds; see the memory_corruption_check_size and
1319 memory_corruption_check_period parameters in
1320 Documentation/kernel-parameters.txt to adjust this.
1322 When enabled with the default parameters, this option has
1323 almost no overhead, as it reserves a relatively small amount
1324 of memory and scans it infrequently. It both detects corruption
1325 and prevents it from affecting the running system.
1327 It is, however, intended as a diagnostic tool; if repeatable
1328 BIOS-originated corruption always affects the same memory,
1329 you can use memmap= to prevent the kernel from using that
1332 config X86_BOOTPARAM_MEMORY_CORRUPTION_CHECK
1333 bool "Set the default setting of memory_corruption_check"
1334 depends on X86_CHECK_BIOS_CORRUPTION
1337 Set whether the default state of memory_corruption_check is
1340 config X86_RESERVE_LOW_64K
1341 bool "Reserve low 64K of RAM on AMI/Phoenix BIOSen"
1344 Reserve the first 64K of physical RAM on BIOSes that are known
1345 to potentially corrupt that memory range. A numbers of BIOSes are
1346 known to utilize this area during suspend/resume, so it must not
1347 be used by the kernel.
1349 Set this to N if you are absolutely sure that you trust the BIOS
1350 to get all its memory reservations and usages right.
1352 If you have doubts about the BIOS (e.g. suspend/resume does not
1353 work or there's kernel crashes after certain hardware hotplug
1354 events) and it's not AMI or Phoenix, then you might want to enable
1355 X86_CHECK_BIOS_CORRUPTION=y to allow the kernel to check typical
1356 corruption patterns.
1360 config MATH_EMULATION
1362 prompt "Math emulation" if X86_32
1364 Linux can emulate a math coprocessor (used for floating point
1365 operations) if you don't have one. 486DX and Pentium processors have
1366 a math coprocessor built in, 486SX and 386 do not, unless you added
1367 a 487DX or 387, respectively. (The messages during boot time can
1368 give you some hints here ["man dmesg"].) Everyone needs either a
1369 coprocessor or this emulation.
1371 If you don't have a math coprocessor, you need to say Y here; if you
1372 say Y here even though you have a coprocessor, the coprocessor will
1373 be used nevertheless. (This behavior can be changed with the kernel
1374 command line option "no387", which comes handy if your coprocessor
1375 is broken. Try "man bootparam" or see the documentation of your boot
1376 loader (lilo or loadlin) about how to pass options to the kernel at
1377 boot time.) This means that it is a good idea to say Y here if you
1378 intend to use this kernel on different machines.
1380 More information about the internals of the Linux math coprocessor
1381 emulation can be found in <file:arch/x86/math-emu/README>.
1383 If you are not sure, say Y; apart from resulting in a 66 KB bigger
1384 kernel, it won't hurt.
1388 prompt "MTRR (Memory Type Range Register) support" if EMBEDDED
1390 On Intel P6 family processors (Pentium Pro, Pentium II and later)
1391 the Memory Type Range Registers (MTRRs) may be used to control
1392 processor access to memory ranges. This is most useful if you have
1393 a video (VGA) card on a PCI or AGP bus. Enabling write-combining
1394 allows bus write transfers to be combined into a larger transfer
1395 before bursting over the PCI/AGP bus. This can increase performance
1396 of image write operations 2.5 times or more. Saying Y here creates a
1397 /proc/mtrr file which may be used to manipulate your processor's
1398 MTRRs. Typically the X server should use this.
1400 This code has a reasonably generic interface so that similar
1401 control registers on other processors can be easily supported
1404 The Cyrix 6x86, 6x86MX and M II processors have Address Range
1405 Registers (ARRs) which provide a similar functionality to MTRRs. For
1406 these, the ARRs are used to emulate the MTRRs.
1407 The AMD K6-2 (stepping 8 and above) and K6-3 processors have two
1408 MTRRs. The Centaur C6 (WinChip) has 8 MCRs, allowing
1409 write-combining. All of these processors are supported by this code
1410 and it makes sense to say Y here if you have one of them.
1412 Saying Y here also fixes a problem with buggy SMP BIOSes which only
1413 set the MTRRs for the boot CPU and not for the secondary CPUs. This
1414 can lead to all sorts of problems, so it's good to say Y here.
1416 You can safely say Y even if your machine doesn't have MTRRs, you'll
1417 just add about 9 KB to your kernel.
1419 See <file:Documentation/x86/mtrr.txt> for more information.
1421 config MTRR_SANITIZER
1423 prompt "MTRR cleanup support"
1426 Convert MTRR layout from continuous to discrete, so X drivers can
1427 add writeback entries.
1429 Can be disabled with disable_mtrr_cleanup on the kernel command line.
1430 The largest mtrr entry size for a continuous block can be set with
1435 config MTRR_SANITIZER_ENABLE_DEFAULT
1436 int "MTRR cleanup enable value (0-1)"
1439 depends on MTRR_SANITIZER
1441 Enable mtrr cleanup default value
1443 config MTRR_SANITIZER_SPARE_REG_NR_DEFAULT
1444 int "MTRR cleanup spare reg num (0-7)"
1447 depends on MTRR_SANITIZER
1449 mtrr cleanup spare entries default, it can be changed via
1450 mtrr_spare_reg_nr=N on the kernel command line.
1454 prompt "x86 PAT support" if EMBEDDED
1457 Use PAT attributes to setup page level cache control.
1459 PATs are the modern equivalents of MTRRs and are much more
1460 flexible than MTRRs.
1462 Say N here if you see bootup problems (boot crash, boot hang,
1463 spontaneous reboots) or a non-working video driver.
1467 config ARCH_USES_PG_UNCACHED
1472 bool "EFI runtime service support"
1475 This enables the kernel to use EFI runtime services that are
1476 available (such as the EFI variable services).
1478 This option is only useful on systems that have EFI firmware.
1479 In addition, you should use the latest ELILO loader available
1480 at <http://elilo.sourceforge.net> in order to take advantage
1481 of EFI runtime services. However, even with this option, the
1482 resultant kernel should continue to boot on existing non-EFI
1487 prompt "Enable seccomp to safely compute untrusted bytecode"
1489 This kernel feature is useful for number crunching applications
1490 that may need to compute untrusted bytecode during their
1491 execution. By using pipes or other transports made available to
1492 the process as file descriptors supporting the read/write
1493 syscalls, it's possible to isolate those applications in
1494 their own address space using seccomp. Once seccomp is
1495 enabled via prctl(PR_SET_SECCOMP), it cannot be disabled
1496 and the task is only allowed to execute a few safe syscalls
1497 defined by each seccomp mode.
1499 If unsure, say Y. Only embedded should say N here.
1501 config CC_STACKPROTECTOR
1502 bool "Enable -fstack-protector buffer overflow detection (EXPERIMENTAL)"
1504 This option turns on the -fstack-protector GCC feature. This
1505 feature puts, at the beginning of functions, a canary value on
1506 the stack just before the return address, and validates
1507 the value just before actually returning. Stack based buffer
1508 overflows (that need to overwrite this return address) now also
1509 overwrite the canary, which gets detected and the attack is then
1510 neutralized via a kernel panic.
1512 This feature requires gcc version 4.2 or above, or a distribution
1513 gcc with the feature backported. Older versions are automatically
1514 detected and for those versions, this configuration option is
1515 ignored. (and a warning is printed during bootup)
1517 source kernel/Kconfig.hz
1520 bool "kexec system call"
1522 kexec is a system call that implements the ability to shutdown your
1523 current kernel, and to start another kernel. It is like a reboot
1524 but it is independent of the system firmware. And like a reboot
1525 you can start any kernel with it, not just Linux.
1527 The name comes from the similarity to the exec system call.
1529 It is an ongoing process to be certain the hardware in a machine
1530 is properly shutdown, so do not be surprised if this code does not
1531 initially work for you. It may help to enable device hotplugging
1532 support. As of this writing the exact hardware interface is
1533 strongly in flux, so no good recommendation can be made.
1536 bool "kernel crash dumps"
1537 depends on X86_64 || (X86_32 && HIGHMEM)
1539 Generate crash dump after being started by kexec.
1540 This should be normally only set in special crash dump kernels
1541 which are loaded in the main kernel with kexec-tools into
1542 a specially reserved region and then later executed after
1543 a crash by kdump/kexec. The crash dump kernel must be compiled
1544 to a memory address not used by the main kernel or BIOS using
1545 PHYSICAL_START, or it must be built as a relocatable image
1546 (CONFIG_RELOCATABLE=y).
1547 For more details see Documentation/kdump/kdump.txt
1550 bool "kexec jump (EXPERIMENTAL)"
1551 depends on EXPERIMENTAL
1552 depends on KEXEC && HIBERNATION
1554 Jump between original kernel and kexeced kernel and invoke
1555 code in physical address mode via KEXEC
1557 config PHYSICAL_START
1558 hex "Physical address where the kernel is loaded" if (EMBEDDED || CRASH_DUMP)
1561 This gives the physical address where the kernel is loaded.
1563 If kernel is a not relocatable (CONFIG_RELOCATABLE=n) then
1564 bzImage will decompress itself to above physical address and
1565 run from there. Otherwise, bzImage will run from the address where
1566 it has been loaded by the boot loader and will ignore above physical
1569 In normal kdump cases one does not have to set/change this option
1570 as now bzImage can be compiled as a completely relocatable image
1571 (CONFIG_RELOCATABLE=y) and be used to load and run from a different
1572 address. This option is mainly useful for the folks who don't want
1573 to use a bzImage for capturing the crash dump and want to use a
1574 vmlinux instead. vmlinux is not relocatable hence a kernel needs
1575 to be specifically compiled to run from a specific memory area
1576 (normally a reserved region) and this option comes handy.
1578 So if you are using bzImage for capturing the crash dump,
1579 leave the value here unchanged to 0x1000000 and set
1580 CONFIG_RELOCATABLE=y. Otherwise if you plan to use vmlinux
1581 for capturing the crash dump change this value to start of
1582 the reserved region. In other words, it can be set based on
1583 the "X" value as specified in the "crashkernel=YM@XM"
1584 command line boot parameter passed to the panic-ed
1585 kernel. Please take a look at Documentation/kdump/kdump.txt
1586 for more details about crash dumps.
1588 Usage of bzImage for capturing the crash dump is recommended as
1589 one does not have to build two kernels. Same kernel can be used
1590 as production kernel and capture kernel. Above option should have
1591 gone away after relocatable bzImage support is introduced. But it
1592 is present because there are users out there who continue to use
1593 vmlinux for dump capture. This option should go away down the
1596 Don't change this unless you know what you are doing.
1599 bool "Build a relocatable kernel"
1602 This builds a kernel image that retains relocation information
1603 so it can be loaded someplace besides the default 1MB.
1604 The relocations tend to make the kernel binary about 10% larger,
1605 but are discarded at runtime.
1607 One use is for the kexec on panic case where the recovery kernel
1608 must live at a different physical address than the primary
1611 Note: If CONFIG_RELOCATABLE=y, then the kernel runs from the address
1612 it has been loaded at and the compile time physical address
1613 (CONFIG_PHYSICAL_START) is ignored.
1615 # Relocation on x86-32 needs some additional build support
1616 config X86_NEED_RELOCS
1618 depends on X86_32 && RELOCATABLE
1620 config PHYSICAL_ALIGN
1621 hex "Alignment value to which kernel should be aligned" if X86_32
1623 range 0x2000 0x1000000
1625 This value puts the alignment restrictions on physical address
1626 where kernel is loaded and run from. Kernel is compiled for an
1627 address which meets above alignment restriction.
1629 If bootloader loads the kernel at a non-aligned address and
1630 CONFIG_RELOCATABLE is set, kernel will move itself to nearest
1631 address aligned to above value and run from there.
1633 If bootloader loads the kernel at a non-aligned address and
1634 CONFIG_RELOCATABLE is not set, kernel will ignore the run time
1635 load address and decompress itself to the address it has been
1636 compiled for and run from there. The address for which kernel is
1637 compiled already meets above alignment restrictions. Hence the
1638 end result is that kernel runs from a physical address meeting
1639 above alignment restrictions.
1641 Don't change this unless you know what you are doing.
1644 bool "Support for hot-pluggable CPUs"
1645 depends on SMP && HOTPLUG
1647 Say Y here to allow turning CPUs off and on. CPUs can be
1648 controlled through /sys/devices/system/cpu.
1649 ( Note: power management support will enable this option
1650 automatically on SMP systems. )
1651 Say N if you want to disable CPU hotplug.
1655 prompt "Compat VDSO support"
1656 depends on X86_32 || IA32_EMULATION
1658 Map the 32-bit VDSO to the predictable old-style address too.
1660 Say N here if you are running a sufficiently recent glibc
1661 version (2.3.3 or later), to remove the high-mapped
1662 VDSO mapping and to exclusively use the randomized VDSO.
1667 bool "Built-in kernel command line"
1669 Allow for specifying boot arguments to the kernel at
1670 build time. On some systems (e.g. embedded ones), it is
1671 necessary or convenient to provide some or all of the
1672 kernel boot arguments with the kernel itself (that is,
1673 to not rely on the boot loader to provide them.)
1675 To compile command line arguments into the kernel,
1676 set this option to 'Y', then fill in the
1677 the boot arguments in CONFIG_CMDLINE.
1679 Systems with fully functional boot loaders (i.e. non-embedded)
1680 should leave this option set to 'N'.
1683 string "Built-in kernel command string"
1684 depends on CMDLINE_BOOL
1687 Enter arguments here that should be compiled into the kernel
1688 image and used at boot time. If the boot loader provides a
1689 command line at boot time, it is appended to this string to
1690 form the full kernel command line, when the system boots.
1692 However, you can use the CONFIG_CMDLINE_OVERRIDE option to
1693 change this behavior.
1695 In most cases, the command line (whether built-in or provided
1696 by the boot loader) should specify the device for the root
1699 config CMDLINE_OVERRIDE
1700 bool "Built-in command line overrides boot loader arguments"
1701 depends on CMDLINE_BOOL
1703 Set this option to 'Y' to have the kernel ignore the boot loader
1704 command line, and use ONLY the built-in command line.
1706 This is used to work around broken boot loaders. This should
1707 be set to 'N' under normal conditions.
1711 config ARCH_ENABLE_MEMORY_HOTPLUG
1713 depends on X86_64 || (X86_32 && HIGHMEM)
1715 config ARCH_ENABLE_MEMORY_HOTREMOVE
1717 depends on MEMORY_HOTPLUG
1719 config HAVE_ARCH_EARLY_PFN_TO_NID
1723 config USE_PERCPU_NUMA_NODE_ID
1727 menu "Power management and ACPI options"
1729 config ARCH_HIBERNATION_HEADER
1731 depends on X86_64 && HIBERNATION
1733 source "kernel/power/Kconfig"
1735 source "drivers/acpi/Kconfig"
1737 source "drivers/sfi/Kconfig"
1741 depends on APM || APM_MODULE
1744 tristate "APM (Advanced Power Management) BIOS support"
1745 depends on X86_32 && PM_SLEEP
1747 APM is a BIOS specification for saving power using several different
1748 techniques. This is mostly useful for battery powered laptops with
1749 APM compliant BIOSes. If you say Y here, the system time will be
1750 reset after a RESUME operation, the /proc/apm device will provide
1751 battery status information, and user-space programs will receive
1752 notification of APM "events" (e.g. battery status change).
1754 If you select "Y" here, you can disable actual use of the APM
1755 BIOS by passing the "apm=off" option to the kernel at boot time.
1757 Note that the APM support is almost completely disabled for
1758 machines with more than one CPU.
1760 In order to use APM, you will need supporting software. For location
1761 and more information, read <file:Documentation/power/pm.txt> and the
1762 Battery Powered Linux mini-HOWTO, available from
1763 <http://www.tldp.org/docs.html#howto>.
1765 This driver does not spin down disk drives (see the hdparm(8)
1766 manpage ("man 8 hdparm") for that), and it doesn't turn off
1767 VESA-compliant "green" monitors.
1769 This driver does not support the TI 4000M TravelMate and the ACER
1770 486/DX4/75 because they don't have compliant BIOSes. Many "green"
1771 desktop machines also don't have compliant BIOSes, and this driver
1772 may cause those machines to panic during the boot phase.
1774 Generally, if you don't have a battery in your machine, there isn't
1775 much point in using this driver and you should say N. If you get
1776 random kernel OOPSes or reboots that don't seem to be related to
1777 anything, try disabling/enabling this option (or disabling/enabling
1780 Some other things you should try when experiencing seemingly random,
1783 1) make sure that you have enough swap space and that it is
1785 2) pass the "no-hlt" option to the kernel
1786 3) switch on floating point emulation in the kernel and pass
1787 the "no387" option to the kernel
1788 4) pass the "floppy=nodma" option to the kernel
1789 5) pass the "mem=4M" option to the kernel (thereby disabling
1790 all but the first 4 MB of RAM)
1791 6) make sure that the CPU is not over clocked.
1792 7) read the sig11 FAQ at <http://www.bitwizard.nl/sig11/>
1793 8) disable the cache from your BIOS settings
1794 9) install a fan for the video card or exchange video RAM
1795 10) install a better fan for the CPU
1796 11) exchange RAM chips
1797 12) exchange the motherboard.
1799 To compile this driver as a module, choose M here: the
1800 module will be called apm.
1804 config APM_IGNORE_USER_SUSPEND
1805 bool "Ignore USER SUSPEND"
1807 This option will ignore USER SUSPEND requests. On machines with a
1808 compliant APM BIOS, you want to say N. However, on the NEC Versa M
1809 series notebooks, it is necessary to say Y because of a BIOS bug.
1811 config APM_DO_ENABLE
1812 bool "Enable PM at boot time"
1814 Enable APM features at boot time. From page 36 of the APM BIOS
1815 specification: "When disabled, the APM BIOS does not automatically
1816 power manage devices, enter the Standby State, enter the Suspend
1817 State, or take power saving steps in response to CPU Idle calls."
1818 This driver will make CPU Idle calls when Linux is idle (unless this
1819 feature is turned off -- see "Do CPU IDLE calls", below). This
1820 should always save battery power, but more complicated APM features
1821 will be dependent on your BIOS implementation. You may need to turn
1822 this option off if your computer hangs at boot time when using APM
1823 support, or if it beeps continuously instead of suspending. Turn
1824 this off if you have a NEC UltraLite Versa 33/C or a Toshiba
1825 T400CDT. This is off by default since most machines do fine without
1829 bool "Make CPU Idle calls when idle"
1831 Enable calls to APM CPU Idle/CPU Busy inside the kernel's idle loop.
1832 On some machines, this can activate improved power savings, such as
1833 a slowed CPU clock rate, when the machine is idle. These idle calls
1834 are made after the idle loop has run for some length of time (e.g.,
1835 333 mS). On some machines, this will cause a hang at boot time or
1836 whenever the CPU becomes idle. (On machines with more than one CPU,
1837 this option does nothing.)
1839 config APM_DISPLAY_BLANK
1840 bool "Enable console blanking using APM"
1842 Enable console blanking using the APM. Some laptops can use this to
1843 turn off the LCD backlight when the screen blanker of the Linux
1844 virtual console blanks the screen. Note that this is only used by
1845 the virtual console screen blanker, and won't turn off the backlight
1846 when using the X Window system. This also doesn't have anything to
1847 do with your VESA-compliant power-saving monitor. Further, this
1848 option doesn't work for all laptops -- it might not turn off your
1849 backlight at all, or it might print a lot of errors to the console,
1850 especially if you are using gpm.
1852 config APM_ALLOW_INTS
1853 bool "Allow interrupts during APM BIOS calls"
1855 Normally we disable external interrupts while we are making calls to
1856 the APM BIOS as a measure to lessen the effects of a badly behaving
1857 BIOS implementation. The BIOS should reenable interrupts if it
1858 needs to. Unfortunately, some BIOSes do not -- especially those in
1859 many of the newer IBM Thinkpads. If you experience hangs when you
1860 suspend, try setting this to Y. Otherwise, say N.
1864 source "arch/x86/kernel/cpu/cpufreq/Kconfig"
1866 source "drivers/cpuidle/Kconfig"
1868 source "drivers/idle/Kconfig"
1873 menu "Bus options (PCI etc.)"
1878 select ARCH_SUPPORTS_MSI if (X86_LOCAL_APIC && X86_IO_APIC)
1880 Find out whether you have a PCI motherboard. PCI is the name of a
1881 bus system, i.e. the way the CPU talks to the other stuff inside
1882 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
1883 VESA. If you have PCI, say Y, otherwise N.
1886 prompt "PCI access mode"
1887 depends on X86_32 && PCI
1890 On PCI systems, the BIOS can be used to detect the PCI devices and
1891 determine their configuration. However, some old PCI motherboards
1892 have BIOS bugs and may crash if this is done. Also, some embedded
1893 PCI-based systems don't have any BIOS at all. Linux can also try to
1894 detect the PCI hardware directly without using the BIOS.
1896 With this option, you can specify how Linux should detect the
1897 PCI devices. If you choose "BIOS", the BIOS will be used,
1898 if you choose "Direct", the BIOS won't be used, and if you
1899 choose "MMConfig", then PCI Express MMCONFIG will be used.
1900 If you choose "Any", the kernel will try MMCONFIG, then the
1901 direct access method and falls back to the BIOS if that doesn't
1902 work. If unsure, go with the default, which is "Any".
1907 config PCI_GOMMCONFIG
1924 depends on X86_32 && PCI && (PCI_GOBIOS || PCI_GOANY)
1926 # x86-64 doesn't support PCI BIOS access from long mode so always go direct.
1929 depends on PCI && (X86_64 || (PCI_GODIRECT || PCI_GOANY || PCI_GOOLPC))
1933 depends on X86_32 && PCI && (ACPI || SFI) && (PCI_GOMMCONFIG || PCI_GOANY)
1937 depends on PCI && OLPC && (PCI_GOOLPC || PCI_GOANY)
1944 bool "Support mmconfig PCI config space access"
1945 depends on X86_64 && PCI && ACPI
1947 config PCI_CNB20LE_QUIRK
1948 bool "Read CNB20LE Host Bridge Windows"
1951 Read the PCI windows out of the CNB20LE host bridge. This allows
1952 PCI hotplug to work on systems with the CNB20LE chipset which do
1956 bool "Support for DMA Remapping Devices (EXPERIMENTAL)"
1957 depends on PCI_MSI && ACPI && EXPERIMENTAL
1959 DMA remapping (DMAR) devices support enables independent address
1960 translations for Direct Memory Access (DMA) from devices.
1961 These DMA remapping devices are reported via ACPI tables
1962 and include PCI device scope covered by these DMA
1965 config DMAR_DEFAULT_ON
1967 prompt "Enable DMA Remapping Devices by default"
1970 Selecting this option will enable a DMAR device at boot time if
1971 one is found. If this option is not selected, DMAR support can
1972 be enabled by passing intel_iommu=on to the kernel. It is
1973 recommended you say N here while the DMAR code remains
1976 config DMAR_BROKEN_GFX_WA
1977 bool "Workaround broken graphics drivers (going away soon)"
1978 depends on DMAR && BROKEN
1980 Current Graphics drivers tend to use physical address
1981 for DMA and avoid using DMA APIs. Setting this config
1982 option permits the IOMMU driver to set a unity map for
1983 all the OS-visible memory. Hence the driver can continue
1984 to use physical addresses for DMA, at least until this
1985 option is removed in the 2.6.32 kernel.
1987 config DMAR_FLOPPY_WA
1991 Floppy disk drivers are known to bypass DMA API calls
1992 thereby failing to work when IOMMU is enabled. This
1993 workaround will setup a 1:1 mapping for the first
1994 16MiB to make floppy (an ISA device) work.
1997 bool "Support for Interrupt Remapping (EXPERIMENTAL)"
1998 depends on X86_64 && X86_IO_APIC && PCI_MSI && ACPI && EXPERIMENTAL
2000 Supports Interrupt remapping for IO-APIC and MSI devices.
2001 To use x2apic mode in the CPU's which support x2APIC enhancements or
2002 to support platforms with CPU's having > 8 bit APIC ID, say Y.
2004 source "drivers/pci/pcie/Kconfig"
2006 source "drivers/pci/Kconfig"
2008 # x86_64 have no ISA slots, but do have ISA-style DMA.
2017 Find out whether you have ISA slots on your motherboard. ISA is the
2018 name of a bus system, i.e. the way the CPU talks to the other stuff
2019 inside your box. Other bus systems are PCI, EISA, MicroChannel
2020 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
2021 newer boards don't support it. If you have ISA, say Y, otherwise N.
2027 The Extended Industry Standard Architecture (EISA) bus was
2028 developed as an open alternative to the IBM MicroChannel bus.
2030 The EISA bus provided some of the features of the IBM MicroChannel
2031 bus while maintaining backward compatibility with cards made for
2032 the older ISA bus. The EISA bus saw limited use between 1988 and
2033 1995 when it was made obsolete by the PCI bus.
2035 Say Y here if you are building a kernel for an EISA-based machine.
2039 source "drivers/eisa/Kconfig"
2044 MicroChannel Architecture is found in some IBM PS/2 machines and
2045 laptops. It is a bus system similar to PCI or ISA. See
2046 <file:Documentation/mca.txt> (and especially the web page given
2047 there) before attempting to build an MCA bus kernel.
2049 source "drivers/mca/Kconfig"
2052 tristate "NatSemi SCx200 support"
2054 This provides basic support for National Semiconductor's
2055 (now AMD's) Geode processors. The driver probes for the
2056 PCI-IDs of several on-chip devices, so its a good dependency
2057 for other scx200_* drivers.
2059 If compiled as a module, the driver is named scx200.
2061 config SCx200HR_TIMER
2062 tristate "NatSemi SCx200 27MHz High-Resolution Timer Support"
2066 This driver provides a clocksource built upon the on-chip
2067 27MHz high-resolution timer. Its also a workaround for
2068 NSC Geode SC-1100's buggy TSC, which loses time when the
2069 processor goes idle (as is done by the scheduler). The
2070 other workaround is idle=poll boot option.
2073 bool "One Laptop Per Child support"
2076 Add support for detecting the unique features of the OLPC
2079 config OLPC_OPENFIRMWARE
2080 bool "Support for OLPC's Open Firmware"
2081 depends on !X86_64 && !X86_PAE
2084 This option adds support for the implementation of Open Firmware
2085 that is used on the OLPC XO-1 Children's Machine.
2086 If unsure, say N here.
2092 depends on CPU_SUP_AMD && PCI
2094 source "drivers/pcmcia/Kconfig"
2096 source "drivers/pci/hotplug/Kconfig"
2101 menu "Executable file formats / Emulations"
2103 source "fs/Kconfig.binfmt"
2105 config IA32_EMULATION
2106 bool "IA32 Emulation"
2108 select COMPAT_BINFMT_ELF
2110 Include code to run 32-bit programs under a 64-bit kernel. You should
2111 likely turn this on, unless you're 100% sure that you don't have any
2112 32-bit programs left.
2115 tristate "IA32 a.out support"
2116 depends on IA32_EMULATION
2118 Support old a.out binaries in the 32bit emulation.
2122 depends on IA32_EMULATION
2124 config COMPAT_FOR_U64_ALIGNMENT
2128 config SYSVIPC_COMPAT
2130 depends on COMPAT && SYSVIPC
2135 config HAVE_ATOMIC_IOMAP
2139 source "net/Kconfig"
2141 source "drivers/Kconfig"
2143 source "drivers/firmware/Kconfig"
2147 source "arch/x86/Kconfig.debug"
2149 source "security/Kconfig"
2151 source "crypto/Kconfig"
2153 source "arch/x86/kvm/Kconfig"
2155 source "lib/Kconfig"