3 bool "64-bit kernel" if ARCH = "x86"
4 default ARCH = "x86_64"
6 Say yes to build a 64-bit kernel - formerly known as x86_64
7 Say no to build a 32-bit kernel - formerly known as i386
19 select HAVE_AOUT if X86_32
20 select HAVE_UNSTABLE_SCHED_CLOCK
23 select HAVE_PCSPKR_PLATFORM
24 select HAVE_PERF_EVENTS
26 select HAVE_IOREMAP_PROT
29 select ARCH_WANT_OPTIONAL_GPIOLIB
30 select ARCH_WANT_FRAME_POINTERS
32 select HAVE_KRETPROBES
34 select HAVE_FTRACE_MCOUNT_RECORD
35 select HAVE_C_RECORDMCOUNT
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
55 select HAVE_KERNEL_LZO
56 select HAVE_HW_BREAKPOINT
57 select HAVE_MIXED_BREAKPOINTS_REGS
59 select HAVE_PERF_EVENTS_NMI
61 select HAVE_ARCH_KMEMCHECK
62 select HAVE_USER_RETURN_NOTIFIER
63 select HAVE_ARCH_JUMP_LABEL
64 select HAVE_TEXT_POKE_SMP
65 select HAVE_GENERIC_HARDIRQS
66 select HAVE_SPARSE_IRQ
68 select GENERIC_FIND_FIRST_BIT
69 select GENERIC_IRQ_PROBE
70 select GENERIC_PENDING_IRQ if SMP
71 select GENERIC_IRQ_SHOW
72 select GENERIC_CLOCKEVENTS_MIN_ADJUST
73 select IRQ_FORCED_THREADING
74 select USE_GENERIC_SMP_HELPERS if SMP
75 select HAVE_BPF_JIT if (X86_64 && NET)
77 select ARCH_HAVE_NMI_SAFE_CMPXCHG
79 config INSTRUCTION_DECODER
80 def_bool (KPROBES || PERF_EVENTS)
84 default "elf32-i386" if X86_32
85 default "elf64-x86-64" if X86_64
89 default "arch/x86/configs/i386_defconfig" if X86_32
90 default "arch/x86/configs/x86_64_defconfig" if X86_64
92 config GENERIC_CMOS_UPDATE
95 config CLOCKSOURCE_WATCHDOG
98 config GENERIC_CLOCKEVENTS
101 config ARCH_CLOCKSOURCE_DATA
105 config GENERIC_CLOCKEVENTS_BROADCAST
107 depends on X86_64 || (X86_32 && X86_LOCAL_APIC)
109 config LOCKDEP_SUPPORT
112 config STACKTRACE_SUPPORT
115 config HAVE_LATENCYTOP_SUPPORT
122 bool "DMA memory allocation support" if EXPERT
125 DMA memory allocation support allows devices with less than 32-bit
126 addressing to allocate within the first 16MB of address space.
127 Disable if no such devices will be used.
134 config NEED_DMA_MAP_STATE
135 def_bool (X86_64 || INTEL_IOMMU || DMA_API_DEBUG)
137 config NEED_SG_DMA_LENGTH
140 config GENERIC_ISA_DMA
149 select GENERIC_BUG_RELATIVE_POINTERS if X86_64
151 config GENERIC_BUG_RELATIVE_POINTERS
154 config GENERIC_HWEIGHT
160 config ARCH_MAY_HAVE_PC_FDC
163 config RWSEM_GENERIC_SPINLOCK
166 config RWSEM_XCHGADD_ALGORITHM
169 config ARCH_HAS_CPU_IDLE_WAIT
172 config GENERIC_CALIBRATE_DELAY
175 config GENERIC_TIME_VSYSCALL
179 config ARCH_HAS_CPU_RELAX
182 config ARCH_HAS_DEFAULT_IDLE
185 config ARCH_HAS_CACHE_LINE_SIZE
188 config HAVE_SETUP_PER_CPU_AREA
191 config NEED_PER_CPU_EMBED_FIRST_CHUNK
194 config NEED_PER_CPU_PAGE_FIRST_CHUNK
197 config HAVE_CPUMASK_OF_CPU_MAP
200 config ARCH_HIBERNATION_POSSIBLE
203 config ARCH_SUSPEND_POSSIBLE
210 config ARCH_POPULATES_NODE_MAP
217 config ARCH_SUPPORTS_OPTIMIZED_INLINING
220 config ARCH_SUPPORTS_DEBUG_PAGEALLOC
223 config HAVE_INTEL_TXT
225 depends on EXPERIMENTAL && INTEL_IOMMU && ACPI
229 depends on X86_32 && SMP
233 depends on X86_64 && SMP
239 config X86_32_LAZY_GS
241 depends on X86_32 && !CC_STACKPROTECTOR
243 config ARCH_HWEIGHT_CFLAGS
245 default "-fcall-saved-ecx -fcall-saved-edx" if X86_32
246 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
251 config ARCH_CPU_PROBE_RELEASE
253 depends on HOTPLUG_CPU
255 source "init/Kconfig"
256 source "kernel/Kconfig.freezer"
258 menu "Processor type and features"
260 source "kernel/time/Kconfig"
263 bool "Symmetric multi-processing support"
265 This enables support for systems with more than one CPU. If you have
266 a system with only one CPU, like most personal computers, say N. If
267 you have a system with more than one CPU, say Y.
269 If you say N here, the kernel will run on single and multiprocessor
270 machines, but will use only one CPU of a multiprocessor machine. If
271 you say Y here, the kernel will run on many, but not all,
272 singleprocessor machines. On a singleprocessor machine, the kernel
273 will run faster if you say N here.
275 Note that if you say Y here and choose architecture "586" or
276 "Pentium" under "Processor family", the kernel will not work on 486
277 architectures. Similarly, multiprocessor kernels for the "PPro"
278 architecture may not work on all Pentium based boards.
280 People using multiprocessor machines who say Y here should also say
281 Y to "Enhanced Real Time Clock Support", below. The "Advanced Power
282 Management" code will be disabled if you say Y here.
284 See also <file:Documentation/x86/i386/IO-APIC.txt>,
285 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
286 <http://www.tldp.org/docs.html#howto>.
288 If you don't know what to do here, say N.
291 bool "Support x2apic"
292 depends on X86_LOCAL_APIC && X86_64 && IRQ_REMAP
294 This enables x2apic support on CPUs that have this feature.
296 This allows 32-bit apic IDs (so it can support very large systems),
297 and accesses the local apic via MSRs not via mmio.
299 If you don't know what to do here, say N.
302 bool "Enable MPS table" if ACPI
304 depends on X86_LOCAL_APIC
306 For old smp systems that do not have proper acpi support. Newer systems
307 (esp with 64bit cpus) with acpi support, MADT and DSDT will override it
310 bool "Support for big SMP systems with more than 8 CPUs"
311 depends on X86_32 && SMP
313 This option is needed for the systems that have more than 8 CPUs
316 config X86_EXTENDED_PLATFORM
317 bool "Support for extended (non-PC) x86 platforms"
320 If you disable this option then the kernel will only support
321 standard PC platforms. (which covers the vast majority of
324 If you enable this option then you'll be able to select support
325 for the following (non-PC) 32 bit x86 platforms:
329 SGI 320/540 (Visual Workstation)
330 Summit/EXA (IBM x440)
331 Unisys ES7000 IA32 series
332 Moorestown MID devices
334 If you have one of these systems, or if you want to build a
335 generic distribution kernel, say Y here - otherwise say N.
339 config X86_EXTENDED_PLATFORM
340 bool "Support for extended (non-PC) x86 platforms"
343 If you disable this option then the kernel will only support
344 standard PC platforms. (which covers the vast majority of
347 If you enable this option then you'll be able to select support
348 for the following (non-PC) 64 bit x86 platforms:
352 If you have one of these systems, or if you want to build a
353 generic distribution kernel, say Y here - otherwise say N.
355 # This is an alphabetically sorted list of 64 bit extended platforms
356 # Please maintain the alphabetic order if and when there are additions
360 select PARAVIRT_GUEST
362 depends on X86_64 && PCI
363 depends on X86_EXTENDED_PLATFORM
365 Support for ScaleMP vSMP systems. Say 'Y' here if this kernel is
366 supposed to run on these EM64T-based machines. Only choose this option
367 if you have one of these machines.
370 bool "SGI Ultraviolet"
372 depends on X86_EXTENDED_PLATFORM
374 depends on X86_X2APIC
376 This option is needed in order to support SGI Ultraviolet systems.
377 If you don't have one of these, you should say N here.
379 # Following is an alphabetically sorted list of 32 bit extended platforms
380 # Please maintain the alphabetic order if and when there are additions
383 bool "CE4100 TV platform"
385 depends on PCI_GODIRECT
387 depends on X86_EXTENDED_PLATFORM
388 select X86_REBOOTFIXUPS
390 select OF_EARLY_FLATTREE
392 Select for the Intel CE media processor (CE4100) SOC.
393 This option compiles in support for the CE4100 SOC for settop
394 boxes and media devices.
397 bool "Intel MID platform support"
399 depends on X86_EXTENDED_PLATFORM
401 Select to build a kernel capable of supporting Intel MID platform
402 systems which do not have the PCI legacy interfaces (Moorestown,
403 Medfield). If you are building for a PC class system say N here.
408 bool "Moorestown MID platform"
411 depends on X86_IO_APIC
416 select X86_PLATFORM_DEVICES
418 Moorestown is Intel's Low Power Intel Architecture (LPIA) based Moblin
419 Internet Device(MID) platform. Moorestown consists of two chips:
420 Lincroft (CPU core, graphics, and memory controller) and Langwell IOH.
421 Unlike standard x86 PCs, Moorestown does not have many legacy devices
422 nor standard legacy replacement devices/features. e.g. Moorestown does
423 not contain i8259, i8254, HPET, legacy BIOS, most of the io ports.
428 bool "RDC R-321x SoC"
430 depends on X86_EXTENDED_PLATFORM
432 select X86_REBOOTFIXUPS
434 This option is needed for RDC R-321x system-on-chip, also known
436 If you don't have one of these chips, you should say N here.
438 config X86_32_NON_STANDARD
439 bool "Support non-standard 32-bit SMP architectures"
440 depends on X86_32 && SMP
441 depends on X86_EXTENDED_PLATFORM
443 This option compiles in the NUMAQ, Summit, bigsmp, ES7000, default
444 subarchitectures. It is intended for a generic binary kernel.
445 if you select them all, kernel will probe it one by one. and will
448 # Alphabetically sorted list of Non standard 32 bit platforms
451 bool "NUMAQ (IBM/Sequent)"
452 depends on X86_32_NON_STANDARD
457 This option is used for getting Linux to run on a NUMAQ (IBM/Sequent)
458 NUMA multiquad box. This changes the way that processors are
459 bootstrapped, and uses Clustered Logical APIC addressing mode instead
460 of Flat Logical. You will need a new lynxer.elf file to flash your
463 config X86_SUPPORTS_MEMORY_FAILURE
465 # MCE code calls memory_failure():
467 # On 32-bit this adds too big of NODES_SHIFT and we run out of page flags:
468 depends on !X86_NUMAQ
469 # On 32-bit SPARSEMEM adds too big of SECTIONS_WIDTH:
470 depends on X86_64 || !SPARSEMEM
471 select ARCH_SUPPORTS_MEMORY_FAILURE
474 bool "SGI 320/540 (Visual Workstation)"
475 depends on X86_32 && PCI && X86_MPPARSE && PCI_GODIRECT
476 depends on X86_32_NON_STANDARD
478 The SGI Visual Workstation series is an IA32-based workstation
479 based on SGI systems chips with some legacy PC hardware attached.
481 Say Y here to create a kernel to run on the SGI 320 or 540.
483 A kernel compiled for the Visual Workstation will run on general
484 PCs as well. See <file:Documentation/sgi-visws.txt> for details.
487 bool "Summit/EXA (IBM x440)"
488 depends on X86_32_NON_STANDARD
490 This option is needed for IBM systems that use the Summit/EXA chipset.
491 In particular, it is needed for the x440.
494 bool "Unisys ES7000 IA32 series"
495 depends on X86_32_NON_STANDARD && X86_BIGSMP
497 Support for Unisys ES7000 systems. Say 'Y' here if this kernel is
498 supposed to run on an IA32-based Unisys ES7000 system.
501 tristate "Eurobraille/Iris poweroff module"
504 The Iris machines from EuroBraille do not have APM or ACPI support
505 to shut themselves down properly. A special I/O sequence is
506 needed to do so, which is what this module does at
509 This is only for Iris machines from EuroBraille.
513 config SCHED_OMIT_FRAME_POINTER
515 prompt "Single-depth WCHAN output"
518 Calculate simpler /proc/<PID>/wchan values. If this option
519 is disabled then wchan values will recurse back to the
520 caller function. This provides more accurate wchan values,
521 at the expense of slightly more scheduling overhead.
523 If in doubt, say "Y".
525 menuconfig PARAVIRT_GUEST
526 bool "Paravirtualized guest support"
528 Say Y here to get to see options related to running Linux under
529 various hypervisors. This option alone does not add any kernel code.
531 If you say N, all options in this submenu will be skipped and disabled.
535 config PARAVIRT_TIME_ACCOUNTING
536 bool "Paravirtual steal time accounting"
540 Select this option to enable fine granularity task steal time
541 accounting. Time spent executing other tasks in parallel with
542 the current vCPU is discounted from the vCPU power. To account for
543 that, there can be a small performance impact.
545 If in doubt, say N here.
547 source "arch/x86/xen/Kconfig"
550 bool "KVM paravirtualized clock"
552 select PARAVIRT_CLOCK
554 Turning on this option will allow you to run a paravirtualized clock
555 when running over the KVM hypervisor. Instead of relying on a PIT
556 (or probably other) emulation by the underlying device model, the host
557 provides the guest with timing infrastructure such as time of day, and
561 bool "KVM Guest support"
564 This option enables various optimizations for running under the KVM
567 source "arch/x86/lguest/Kconfig"
570 bool "Enable paravirtualization code"
572 This changes the kernel so it can modify itself when it is run
573 under a hypervisor, potentially improving performance significantly
574 over full virtualization. However, when run without a hypervisor
575 the kernel is theoretically slower and slightly larger.
577 config PARAVIRT_SPINLOCKS
578 bool "Paravirtualization layer for spinlocks"
579 depends on PARAVIRT && SMP && EXPERIMENTAL
581 Paravirtualized spinlocks allow a pvops backend to replace the
582 spinlock implementation with something virtualization-friendly
583 (for example, block the virtual CPU rather than spinning).
585 Unfortunately the downside is an up to 5% performance hit on
586 native kernels, with various workloads.
588 If you are unsure how to answer this question, answer N.
590 config PARAVIRT_CLOCK
595 config PARAVIRT_DEBUG
596 bool "paravirt-ops debugging"
597 depends on PARAVIRT && DEBUG_KERNEL
599 Enable to debug paravirt_ops internals. Specifically, BUG if
600 a paravirt_op is missing when it is called.
608 This option adds a kernel parameter 'memtest', which allows memtest
610 memtest=0, mean disabled; -- default
611 memtest=1, mean do 1 test pattern;
613 memtest=4, mean do 4 test patterns.
614 If you are unsure how to answer this question, answer N.
616 config X86_SUMMIT_NUMA
618 depends on X86_32 && NUMA && X86_32_NON_STANDARD
620 config X86_CYCLONE_TIMER
622 depends on X86_32_NON_STANDARD
624 source "arch/x86/Kconfig.cpu"
628 prompt "HPET Timer Support" if X86_32
630 Use the IA-PC HPET (High Precision Event Timer) to manage
631 time in preference to the PIT and RTC, if a HPET is
633 HPET is the next generation timer replacing legacy 8254s.
634 The HPET provides a stable time base on SMP
635 systems, unlike the TSC, but it is more expensive to access,
636 as it is off-chip. You can find the HPET spec at
637 <http://www.intel.com/hardwaredesign/hpetspec_1.pdf>.
639 You can safely choose Y here. However, HPET will only be
640 activated if the platform and the BIOS support this feature.
641 Otherwise the 8254 will be used for timing services.
643 Choose N to continue using the legacy 8254 timer.
645 config HPET_EMULATE_RTC
647 depends on HPET_TIMER && (RTC=y || RTC=m || RTC_DRV_CMOS=m || RTC_DRV_CMOS=y)
651 prompt "Langwell APB Timer Support" if X86_MRST
654 APB timer is the replacement for 8254, HPET on X86 MID platforms.
655 The APBT provides a stable time base on SMP
656 systems, unlike the TSC, but it is more expensive to access,
657 as it is off-chip. APB timers are always running regardless of CPU
658 C states, they are used as per CPU clockevent device when possible.
660 # Mark as expert because too many people got it wrong.
661 # The code disables itself when not needed.
664 bool "Enable DMI scanning" if EXPERT
666 Enabled scanning of DMI to identify machine quirks. Say Y
667 here unless you have verified that your setup is not
668 affected by entries in the DMI blacklist. Required by PNP
672 bool "GART IOMMU support" if EXPERT
675 depends on X86_64 && PCI && AMD_NB
677 Support for full DMA access of devices with 32bit memory access only
678 on systems with more than 3GB. This is usually needed for USB,
679 sound, many IDE/SATA chipsets and some other devices.
680 Provides a driver for the AMD Athlon64/Opteron/Turion/Sempron GART
681 based hardware IOMMU and a software bounce buffer based IOMMU used
682 on Intel systems and as fallback.
683 The code is only active when needed (enough memory and limited
684 device) unless CONFIG_IOMMU_DEBUG or iommu=force is specified
688 bool "IBM Calgary IOMMU support"
690 depends on X86_64 && PCI && EXPERIMENTAL
692 Support for hardware IOMMUs in IBM's xSeries x366 and x460
693 systems. Needed to run systems with more than 3GB of memory
694 properly with 32-bit PCI devices that do not support DAC
695 (Double Address Cycle). Calgary also supports bus level
696 isolation, where all DMAs pass through the IOMMU. This
697 prevents them from going anywhere except their intended
698 destination. This catches hard-to-find kernel bugs and
699 mis-behaving drivers and devices that do not use the DMA-API
700 properly to set up their DMA buffers. The IOMMU can be
701 turned off at boot time with the iommu=off parameter.
702 Normally the kernel will make the right choice by itself.
705 config CALGARY_IOMMU_ENABLED_BY_DEFAULT
707 prompt "Should Calgary be enabled by default?"
708 depends on CALGARY_IOMMU
710 Should Calgary be enabled by default? if you choose 'y', Calgary
711 will be used (if it exists). If you choose 'n', Calgary will not be
712 used even if it exists. If you choose 'n' and would like to use
713 Calgary anyway, pass 'iommu=calgary' on the kernel command line.
716 # need this always selected by IOMMU for the VIA workaround
720 Support for software bounce buffers used on x86-64 systems
721 which don't have a hardware IOMMU (e.g. the current generation
722 of Intel's x86-64 CPUs). Using this PCI devices which can only
723 access 32-bits of memory can be used on systems with more than
724 3 GB of memory. If unsure, say Y.
727 def_bool (CALGARY_IOMMU || GART_IOMMU || SWIOTLB || AMD_IOMMU)
730 bool "Enable Maximum number of SMP Processors and NUMA Nodes"
731 depends on X86_64 && SMP && DEBUG_KERNEL && EXPERIMENTAL
732 select CPUMASK_OFFSTACK
734 Enable maximum number of CPUS and NUMA Nodes for this architecture.
738 int "Maximum number of CPUs" if SMP && !MAXSMP
739 range 2 8 if SMP && X86_32 && !X86_BIGSMP
740 range 2 512 if SMP && !MAXSMP
742 default "4096" if MAXSMP
743 default "32" if SMP && (X86_NUMAQ || X86_SUMMIT || X86_BIGSMP || X86_ES7000)
746 This allows you to specify the maximum number of CPUs which this
747 kernel will support. The maximum supported value is 512 and the
748 minimum value which makes sense is 2.
750 This is purely to save memory - each supported CPU adds
751 approximately eight kilobytes to the kernel image.
754 bool "SMT (Hyperthreading) scheduler support"
757 SMT scheduler support improves the CPU scheduler's decision making
758 when dealing with Intel Pentium 4 chips with HyperThreading at a
759 cost of slightly increased overhead in some places. If unsure say
764 prompt "Multi-core scheduler support"
767 Multi-core scheduler support improves the CPU scheduler's decision
768 making when dealing with multi-core CPU chips at a cost of slightly
769 increased overhead in some places. If unsure say N here.
771 config IRQ_TIME_ACCOUNTING
772 bool "Fine granularity task level IRQ time accounting"
775 Select this option to enable fine granularity task irq time
776 accounting. This is done by reading a timestamp on each
777 transitions between softirq and hardirq state, so there can be a
778 small performance impact.
780 If in doubt, say N here.
782 source "kernel/Kconfig.preempt"
785 bool "Local APIC support on uniprocessors"
786 depends on X86_32 && !SMP && !X86_32_NON_STANDARD
788 A local APIC (Advanced Programmable Interrupt Controller) is an
789 integrated interrupt controller in the CPU. If you have a single-CPU
790 system which has a processor with a local APIC, you can say Y here to
791 enable and use it. If you say Y here even though your machine doesn't
792 have a local APIC, then the kernel will still run with no slowdown at
793 all. The local APIC supports CPU-generated self-interrupts (timer,
794 performance counters), and the NMI watchdog which detects hard
798 bool "IO-APIC support on uniprocessors"
799 depends on X86_UP_APIC
801 An IO-APIC (I/O Advanced Programmable Interrupt Controller) is an
802 SMP-capable replacement for PC-style interrupt controllers. Most
803 SMP systems and many recent uniprocessor systems have one.
805 If you have a single-CPU system with an IO-APIC, you can say Y here
806 to use it. If you say Y here even though your machine doesn't have
807 an IO-APIC, then the kernel will still run with no slowdown at all.
809 config X86_LOCAL_APIC
811 depends on X86_64 || SMP || X86_32_NON_STANDARD || X86_UP_APIC
815 depends on X86_64 || SMP || X86_32_NON_STANDARD || X86_UP_IOAPIC
817 config X86_VISWS_APIC
819 depends on X86_32 && X86_VISWS
821 config X86_REROUTE_FOR_BROKEN_BOOT_IRQS
822 bool "Reroute for broken boot IRQs"
823 depends on X86_IO_APIC
825 This option enables a workaround that fixes a source of
826 spurious interrupts. This is recommended when threaded
827 interrupt handling is used on systems where the generation of
828 superfluous "boot interrupts" cannot be disabled.
830 Some chipsets generate a legacy INTx "boot IRQ" when the IRQ
831 entry in the chipset's IO-APIC is masked (as, e.g. the RT
832 kernel does during interrupt handling). On chipsets where this
833 boot IRQ generation cannot be disabled, this workaround keeps
834 the original IRQ line masked so that only the equivalent "boot
835 IRQ" is delivered to the CPUs. The workaround also tells the
836 kernel to set up the IRQ handler on the boot IRQ line. In this
837 way only one interrupt is delivered to the kernel. Otherwise
838 the spurious second interrupt may cause the kernel to bring
839 down (vital) interrupt lines.
841 Only affects "broken" chipsets. Interrupt sharing may be
842 increased on these systems.
845 bool "Machine Check / overheating reporting"
847 Machine Check support allows the processor to notify the
848 kernel if it detects a problem (e.g. overheating, data corruption).
849 The action the kernel takes depends on the severity of the problem,
850 ranging from warning messages to halting the machine.
854 prompt "Intel MCE features"
855 depends on X86_MCE && X86_LOCAL_APIC
857 Additional support for intel specific MCE features such as
862 prompt "AMD MCE features"
863 depends on X86_MCE && X86_LOCAL_APIC
865 Additional support for AMD specific MCE features such as
866 the DRAM Error Threshold.
868 config X86_ANCIENT_MCE
869 bool "Support for old Pentium 5 / WinChip machine checks"
870 depends on X86_32 && X86_MCE
872 Include support for machine check handling on old Pentium 5 or WinChip
873 systems. These typically need to be enabled explicitely on the command
876 config X86_MCE_THRESHOLD
877 depends on X86_MCE_AMD || X86_MCE_INTEL
880 config X86_MCE_INJECT
882 tristate "Machine check injector support"
884 Provide support for injecting machine checks for testing purposes.
885 If you don't know what a machine check is and you don't do kernel
886 QA it is safe to say n.
888 config X86_THERMAL_VECTOR
890 depends on X86_MCE_INTEL
893 bool "Enable VM86 support" if EXPERT
897 This option is required by programs like DOSEMU to run 16-bit legacy
898 code on X86 processors. It also may be needed by software like
899 XFree86 to initialize some video cards via BIOS. Disabling this
900 option saves about 6k.
903 tristate "Toshiba Laptop support"
906 This adds a driver to safely access the System Management Mode of
907 the CPU on Toshiba portables with a genuine Toshiba BIOS. It does
908 not work on models with a Phoenix BIOS. The System Management Mode
909 is used to set the BIOS and power saving options on Toshiba portables.
911 For information on utilities to make use of this driver see the
912 Toshiba Linux utilities web site at:
913 <http://www.buzzard.org.uk/toshiba/>.
915 Say Y if you intend to run this kernel on a Toshiba portable.
919 tristate "Dell laptop support"
922 This adds a driver to safely access the System Management Mode
923 of the CPU on the Dell Inspiron 8000. The System Management Mode
924 is used to read cpu temperature and cooling fan status and to
925 control the fans on the I8K portables.
927 This driver has been tested only on the Inspiron 8000 but it may
928 also work with other Dell laptops. You can force loading on other
929 models by passing the parameter `force=1' to the module. Use at
932 For information on utilities to make use of this driver see the
933 I8K Linux utilities web site at:
934 <http://people.debian.org/~dz/i8k/>
936 Say Y if you intend to run this kernel on a Dell Inspiron 8000.
939 config X86_REBOOTFIXUPS
940 bool "Enable X86 board specific fixups for reboot"
943 This enables chipset and/or board specific fixups to be done
944 in order to get reboot to work correctly. This is only needed on
945 some combinations of hardware and BIOS. The symptom, for which
946 this config is intended, is when reboot ends with a stalled/hung
949 Currently, the only fixup is for the Geode machines using
950 CS5530A and CS5536 chipsets and the RDC R-321x SoC.
952 Say Y if you want to enable the fixup. Currently, it's safe to
953 enable this option even if you don't need it.
957 tristate "/dev/cpu/microcode - microcode support"
960 If you say Y here, you will be able to update the microcode on
961 certain Intel and AMD processors. The Intel support is for the
962 IA32 family, e.g. Pentium Pro, Pentium II, Pentium III,
963 Pentium 4, Xeon etc. The AMD support is for family 0x10 and
964 0x11 processors, e.g. Opteron, Phenom and Turion 64 Ultra.
965 You will obviously need the actual microcode binary data itself
966 which is not shipped with the Linux kernel.
968 This option selects the general module only, you need to select
969 at least one vendor specific module as well.
971 To compile this driver as a module, choose M here: the
972 module will be called microcode.
974 config MICROCODE_INTEL
975 bool "Intel microcode patch loading support"
980 This options enables microcode patch loading support for Intel
983 For latest news and information on obtaining all the required
984 Intel ingredients for this driver, check:
985 <http://www.urbanmyth.org/microcode/>.
988 bool "AMD microcode patch loading support"
992 If you select this option, microcode patch loading support for AMD
993 processors will be enabled.
995 config MICROCODE_OLD_INTERFACE
1000 tristate "/dev/cpu/*/msr - Model-specific register support"
1002 This device gives privileged processes access to the x86
1003 Model-Specific Registers (MSRs). It is a character device with
1004 major 202 and minors 0 to 31 for /dev/cpu/0/msr to /dev/cpu/31/msr.
1005 MSR accesses are directed to a specific CPU on multi-processor
1009 tristate "/dev/cpu/*/cpuid - CPU information support"
1011 This device gives processes access to the x86 CPUID instruction to
1012 be executed on a specific processor. It is a character device
1013 with major 203 and minors 0 to 31 for /dev/cpu/0/cpuid to
1017 prompt "High Memory Support"
1018 default HIGHMEM64G if X86_NUMAQ
1024 depends on !X86_NUMAQ
1026 Linux can use up to 64 Gigabytes of physical memory on x86 systems.
1027 However, the address space of 32-bit x86 processors is only 4
1028 Gigabytes large. That means that, if you have a large amount of
1029 physical memory, not all of it can be "permanently mapped" by the
1030 kernel. The physical memory that's not permanently mapped is called
1033 If you are compiling a kernel which will never run on a machine with
1034 more than 1 Gigabyte total physical RAM, answer "off" here (default
1035 choice and suitable for most users). This will result in a "3GB/1GB"
1036 split: 3GB are mapped so that each process sees a 3GB virtual memory
1037 space and the remaining part of the 4GB virtual memory space is used
1038 by the kernel to permanently map as much physical memory as
1041 If the machine has between 1 and 4 Gigabytes physical RAM, then
1044 If more than 4 Gigabytes is used then answer "64GB" here. This
1045 selection turns Intel PAE (Physical Address Extension) mode on.
1046 PAE implements 3-level paging on IA32 processors. PAE is fully
1047 supported by Linux, PAE mode is implemented on all recent Intel
1048 processors (Pentium Pro and better). NOTE: If you say "64GB" here,
1049 then the kernel will not boot on CPUs that don't support PAE!
1051 The actual amount of total physical memory will either be
1052 auto detected or can be forced by using a kernel command line option
1053 such as "mem=256M". (Try "man bootparam" or see the documentation of
1054 your boot loader (lilo or loadlin) about how to pass options to the
1055 kernel at boot time.)
1057 If unsure, say "off".
1061 depends on !X86_NUMAQ
1063 Select this if you have a 32-bit processor and between 1 and 4
1064 gigabytes of physical RAM.
1068 depends on !M386 && !M486
1071 Select this if you have a 32-bit processor and more than 4
1072 gigabytes of physical RAM.
1077 depends on EXPERIMENTAL
1078 prompt "Memory split" if EXPERT
1082 Select the desired split between kernel and user memory.
1084 If the address range available to the kernel is less than the
1085 physical memory installed, the remaining memory will be available
1086 as "high memory". Accessing high memory is a little more costly
1087 than low memory, as it needs to be mapped into the kernel first.
1088 Note that increasing the kernel address space limits the range
1089 available to user programs, making the address space there
1090 tighter. Selecting anything other than the default 3G/1G split
1091 will also likely make your kernel incompatible with binary-only
1094 If you are not absolutely sure what you are doing, leave this
1098 bool "3G/1G user/kernel split"
1099 config VMSPLIT_3G_OPT
1101 bool "3G/1G user/kernel split (for full 1G low memory)"
1103 bool "2G/2G user/kernel split"
1104 config VMSPLIT_2G_OPT
1106 bool "2G/2G user/kernel split (for full 2G low memory)"
1108 bool "1G/3G user/kernel split"
1113 default 0xB0000000 if VMSPLIT_3G_OPT
1114 default 0x80000000 if VMSPLIT_2G
1115 default 0x78000000 if VMSPLIT_2G_OPT
1116 default 0x40000000 if VMSPLIT_1G
1122 depends on X86_32 && (HIGHMEM64G || HIGHMEM4G)
1125 bool "PAE (Physical Address Extension) Support"
1126 depends on X86_32 && !HIGHMEM4G
1128 PAE is required for NX support, and furthermore enables
1129 larger swapspace support for non-overcommit purposes. It
1130 has the cost of more pagetable lookup overhead, and also
1131 consumes more pagetable space per process.
1133 config ARCH_PHYS_ADDR_T_64BIT
1134 def_bool X86_64 || X86_PAE
1136 config ARCH_DMA_ADDR_T_64BIT
1137 def_bool X86_64 || HIGHMEM64G
1139 config DIRECT_GBPAGES
1140 bool "Enable 1GB pages for kernel pagetables" if EXPERT
1144 Allow the kernel linear mapping to use 1GB pages on CPUs that
1145 support it. This can improve the kernel's performance a tiny bit by
1146 reducing TLB pressure. If in doubt, say "Y".
1148 # Common NUMA Features
1150 bool "Numa Memory Allocation and Scheduler Support"
1152 depends on X86_64 || (X86_32 && HIGHMEM64G && (X86_NUMAQ || X86_BIGSMP || X86_SUMMIT && ACPI) && EXPERIMENTAL)
1153 default y if (X86_NUMAQ || X86_SUMMIT || X86_BIGSMP)
1155 Enable NUMA (Non Uniform Memory Access) support.
1157 The kernel will try to allocate memory used by a CPU on the
1158 local memory controller of the CPU and add some more
1159 NUMA awareness to the kernel.
1161 For 64-bit this is recommended if the system is Intel Core i7
1162 (or later), AMD Opteron, or EM64T NUMA.
1164 For 32-bit this is only needed on (rare) 32-bit-only platforms
1165 that support NUMA topologies, such as NUMAQ / Summit, or if you
1166 boot a 32-bit kernel on a 64-bit NUMA platform.
1168 Otherwise, you should say N.
1170 comment "NUMA (Summit) requires SMP, 64GB highmem support, ACPI"
1171 depends on X86_32 && X86_SUMMIT && (!HIGHMEM64G || !ACPI)
1175 prompt "Old style AMD Opteron NUMA detection"
1176 depends on X86_64 && NUMA && PCI
1178 Enable AMD NUMA node topology detection. You should say Y here if
1179 you have a multi processor AMD system. This uses an old method to
1180 read the NUMA configuration directly from the builtin Northbridge
1181 of Opteron. It is recommended to use X86_64_ACPI_NUMA instead,
1182 which also takes priority if both are compiled in.
1184 config X86_64_ACPI_NUMA
1186 prompt "ACPI NUMA detection"
1187 depends on X86_64 && NUMA && ACPI && PCI
1190 Enable ACPI SRAT based node topology detection.
1192 # Some NUMA nodes have memory ranges that span
1193 # other nodes. Even though a pfn is valid and
1194 # between a node's start and end pfns, it may not
1195 # reside on that node. See memmap_init_zone()
1197 config NODES_SPAN_OTHER_NODES
1199 depends on X86_64_ACPI_NUMA
1202 bool "NUMA emulation"
1205 Enable NUMA emulation. A flat machine will be split
1206 into virtual nodes when booted with "numa=fake=N", where N is the
1207 number of nodes. This is only useful for debugging.
1210 int "Maximum NUMA Nodes (as a power of 2)" if !MAXSMP
1212 default "10" if MAXSMP
1213 default "6" if X86_64
1214 default "4" if X86_NUMAQ
1216 depends on NEED_MULTIPLE_NODES
1218 Specify the maximum number of NUMA Nodes available on the target
1219 system. Increases memory reserved to accommodate various tables.
1221 config HAVE_ARCH_BOOTMEM
1223 depends on X86_32 && NUMA
1225 config HAVE_ARCH_ALLOC_REMAP
1227 depends on X86_32 && NUMA
1229 config ARCH_HAVE_MEMORY_PRESENT
1231 depends on X86_32 && DISCONTIGMEM
1233 config NEED_NODE_MEMMAP_SIZE
1235 depends on X86_32 && (DISCONTIGMEM || SPARSEMEM)
1237 config ARCH_FLATMEM_ENABLE
1239 depends on X86_32 && !NUMA
1241 config ARCH_DISCONTIGMEM_ENABLE
1243 depends on NUMA && X86_32
1245 config ARCH_DISCONTIGMEM_DEFAULT
1247 depends on NUMA && X86_32
1249 config ARCH_SPARSEMEM_ENABLE
1251 depends on X86_64 || NUMA || (EXPERIMENTAL && X86_32) || X86_32_NON_STANDARD
1252 select SPARSEMEM_STATIC if X86_32
1253 select SPARSEMEM_VMEMMAP_ENABLE if X86_64
1255 config ARCH_SPARSEMEM_DEFAULT
1259 config ARCH_SELECT_MEMORY_MODEL
1261 depends on ARCH_SPARSEMEM_ENABLE
1263 config ARCH_MEMORY_PROBE
1265 depends on MEMORY_HOTPLUG
1267 config ARCH_PROC_KCORE_TEXT
1269 depends on X86_64 && PROC_KCORE
1271 config ILLEGAL_POINTER_VALUE
1274 default 0xdead000000000000 if X86_64
1279 bool "Allocate 3rd-level pagetables from highmem"
1282 The VM uses one page table entry for each page of physical memory.
1283 For systems with a lot of RAM, this can be wasteful of precious
1284 low memory. Setting this option will put user-space page table
1285 entries in high memory.
1287 config X86_CHECK_BIOS_CORRUPTION
1288 bool "Check for low memory corruption"
1290 Periodically check for memory corruption in low memory, which
1291 is suspected to be caused by BIOS. Even when enabled in the
1292 configuration, it is disabled at runtime. Enable it by
1293 setting "memory_corruption_check=1" on the kernel command
1294 line. By default it scans the low 64k of memory every 60
1295 seconds; see the memory_corruption_check_size and
1296 memory_corruption_check_period parameters in
1297 Documentation/kernel-parameters.txt to adjust this.
1299 When enabled with the default parameters, this option has
1300 almost no overhead, as it reserves a relatively small amount
1301 of memory and scans it infrequently. It both detects corruption
1302 and prevents it from affecting the running system.
1304 It is, however, intended as a diagnostic tool; if repeatable
1305 BIOS-originated corruption always affects the same memory,
1306 you can use memmap= to prevent the kernel from using that
1309 config X86_BOOTPARAM_MEMORY_CORRUPTION_CHECK
1310 bool "Set the default setting of memory_corruption_check"
1311 depends on X86_CHECK_BIOS_CORRUPTION
1314 Set whether the default state of memory_corruption_check is
1317 config X86_RESERVE_LOW
1318 int "Amount of low memory, in kilobytes, to reserve for the BIOS"
1322 Specify the amount of low memory to reserve for the BIOS.
1324 The first page contains BIOS data structures that the kernel
1325 must not use, so that page must always be reserved.
1327 By default we reserve the first 64K of physical RAM, as a
1328 number of BIOSes are known to corrupt that memory range
1329 during events such as suspend/resume or monitor cable
1330 insertion, so it must not be used by the kernel.
1332 You can set this to 4 if you are absolutely sure that you
1333 trust the BIOS to get all its memory reservations and usages
1334 right. If you know your BIOS have problems beyond the
1335 default 64K area, you can set this to 640 to avoid using the
1336 entire low memory range.
1338 If you have doubts about the BIOS (e.g. suspend/resume does
1339 not work or there's kernel crashes after certain hardware
1340 hotplug events) then you might want to enable
1341 X86_CHECK_BIOS_CORRUPTION=y to allow the kernel to check
1342 typical corruption patterns.
1344 Leave this to the default value of 64 if you are unsure.
1346 config MATH_EMULATION
1348 prompt "Math emulation" if X86_32
1350 Linux can emulate a math coprocessor (used for floating point
1351 operations) if you don't have one. 486DX and Pentium processors have
1352 a math coprocessor built in, 486SX and 386 do not, unless you added
1353 a 487DX or 387, respectively. (The messages during boot time can
1354 give you some hints here ["man dmesg"].) Everyone needs either a
1355 coprocessor or this emulation.
1357 If you don't have a math coprocessor, you need to say Y here; if you
1358 say Y here even though you have a coprocessor, the coprocessor will
1359 be used nevertheless. (This behavior can be changed with the kernel
1360 command line option "no387", which comes handy if your coprocessor
1361 is broken. Try "man bootparam" or see the documentation of your boot
1362 loader (lilo or loadlin) about how to pass options to the kernel at
1363 boot time.) This means that it is a good idea to say Y here if you
1364 intend to use this kernel on different machines.
1366 More information about the internals of the Linux math coprocessor
1367 emulation can be found in <file:arch/x86/math-emu/README>.
1369 If you are not sure, say Y; apart from resulting in a 66 KB bigger
1370 kernel, it won't hurt.
1374 prompt "MTRR (Memory Type Range Register) support" if EXPERT
1376 On Intel P6 family processors (Pentium Pro, Pentium II and later)
1377 the Memory Type Range Registers (MTRRs) may be used to control
1378 processor access to memory ranges. This is most useful if you have
1379 a video (VGA) card on a PCI or AGP bus. Enabling write-combining
1380 allows bus write transfers to be combined into a larger transfer
1381 before bursting over the PCI/AGP bus. This can increase performance
1382 of image write operations 2.5 times or more. Saying Y here creates a
1383 /proc/mtrr file which may be used to manipulate your processor's
1384 MTRRs. Typically the X server should use this.
1386 This code has a reasonably generic interface so that similar
1387 control registers on other processors can be easily supported
1390 The Cyrix 6x86, 6x86MX and M II processors have Address Range
1391 Registers (ARRs) which provide a similar functionality to MTRRs. For
1392 these, the ARRs are used to emulate the MTRRs.
1393 The AMD K6-2 (stepping 8 and above) and K6-3 processors have two
1394 MTRRs. The Centaur C6 (WinChip) has 8 MCRs, allowing
1395 write-combining. All of these processors are supported by this code
1396 and it makes sense to say Y here if you have one of them.
1398 Saying Y here also fixes a problem with buggy SMP BIOSes which only
1399 set the MTRRs for the boot CPU and not for the secondary CPUs. This
1400 can lead to all sorts of problems, so it's good to say Y here.
1402 You can safely say Y even if your machine doesn't have MTRRs, you'll
1403 just add about 9 KB to your kernel.
1405 See <file:Documentation/x86/mtrr.txt> for more information.
1407 config MTRR_SANITIZER
1409 prompt "MTRR cleanup support"
1412 Convert MTRR layout from continuous to discrete, so X drivers can
1413 add writeback entries.
1415 Can be disabled with disable_mtrr_cleanup on the kernel command line.
1416 The largest mtrr entry size for a continuous block can be set with
1421 config MTRR_SANITIZER_ENABLE_DEFAULT
1422 int "MTRR cleanup enable value (0-1)"
1425 depends on MTRR_SANITIZER
1427 Enable mtrr cleanup default value
1429 config MTRR_SANITIZER_SPARE_REG_NR_DEFAULT
1430 int "MTRR cleanup spare reg num (0-7)"
1433 depends on MTRR_SANITIZER
1435 mtrr cleanup spare entries default, it can be changed via
1436 mtrr_spare_reg_nr=N on the kernel command line.
1440 prompt "x86 PAT support" if EXPERT
1443 Use PAT attributes to setup page level cache control.
1445 PATs are the modern equivalents of MTRRs and are much more
1446 flexible than MTRRs.
1448 Say N here if you see bootup problems (boot crash, boot hang,
1449 spontaneous reboots) or a non-working video driver.
1453 config ARCH_USES_PG_UNCACHED
1459 prompt "x86 architectural random number generator" if EXPERT
1461 Enable the x86 architectural RDRAND instruction
1462 (Intel Bull Mountain technology) to generate random numbers.
1463 If supported, this is a high bandwidth, cryptographically
1464 secure hardware random number generator.
1467 bool "EFI runtime service support"
1470 This enables the kernel to use EFI runtime services that are
1471 available (such as the EFI variable services).
1473 This option is only useful on systems that have EFI firmware.
1474 In addition, you should use the latest ELILO loader available
1475 at <http://elilo.sourceforge.net> in order to take advantage
1476 of EFI runtime services. However, even with this option, the
1477 resultant kernel should continue to boot on existing non-EFI
1482 prompt "Enable seccomp to safely compute untrusted bytecode"
1484 This kernel feature is useful for number crunching applications
1485 that may need to compute untrusted bytecode during their
1486 execution. By using pipes or other transports made available to
1487 the process as file descriptors supporting the read/write
1488 syscalls, it's possible to isolate those applications in
1489 their own address space using seccomp. Once seccomp is
1490 enabled via prctl(PR_SET_SECCOMP), it cannot be disabled
1491 and the task is only allowed to execute a few safe syscalls
1492 defined by each seccomp mode.
1494 If unsure, say Y. Only embedded should say N here.
1496 config CC_STACKPROTECTOR
1497 bool "Enable -fstack-protector buffer overflow detection (EXPERIMENTAL)"
1499 This option turns on the -fstack-protector GCC feature. This
1500 feature puts, at the beginning of functions, a canary value on
1501 the stack just before the return address, and validates
1502 the value just before actually returning. Stack based buffer
1503 overflows (that need to overwrite this return address) now also
1504 overwrite the canary, which gets detected and the attack is then
1505 neutralized via a kernel panic.
1507 This feature requires gcc version 4.2 or above, or a distribution
1508 gcc with the feature backported. Older versions are automatically
1509 detected and for those versions, this configuration option is
1510 ignored. (and a warning is printed during bootup)
1512 source kernel/Kconfig.hz
1515 bool "kexec system call"
1517 kexec is a system call that implements the ability to shutdown your
1518 current kernel, and to start another kernel. It is like a reboot
1519 but it is independent of the system firmware. And like a reboot
1520 you can start any kernel with it, not just Linux.
1522 The name comes from the similarity to the exec system call.
1524 It is an ongoing process to be certain the hardware in a machine
1525 is properly shutdown, so do not be surprised if this code does not
1526 initially work for you. It may help to enable device hotplugging
1527 support. As of this writing the exact hardware interface is
1528 strongly in flux, so no good recommendation can be made.
1531 bool "kernel crash dumps"
1532 depends on X86_64 || (X86_32 && HIGHMEM)
1534 Generate crash dump after being started by kexec.
1535 This should be normally only set in special crash dump kernels
1536 which are loaded in the main kernel with kexec-tools into
1537 a specially reserved region and then later executed after
1538 a crash by kdump/kexec. The crash dump kernel must be compiled
1539 to a memory address not used by the main kernel or BIOS using
1540 PHYSICAL_START, or it must be built as a relocatable image
1541 (CONFIG_RELOCATABLE=y).
1542 For more details see Documentation/kdump/kdump.txt
1545 bool "kexec jump (EXPERIMENTAL)"
1546 depends on EXPERIMENTAL
1547 depends on KEXEC && HIBERNATION
1549 Jump between original kernel and kexeced kernel and invoke
1550 code in physical address mode via KEXEC
1552 config PHYSICAL_START
1553 hex "Physical address where the kernel is loaded" if (EXPERT || CRASH_DUMP)
1556 This gives the physical address where the kernel is loaded.
1558 If kernel is a not relocatable (CONFIG_RELOCATABLE=n) then
1559 bzImage will decompress itself to above physical address and
1560 run from there. Otherwise, bzImage will run from the address where
1561 it has been loaded by the boot loader and will ignore above physical
1564 In normal kdump cases one does not have to set/change this option
1565 as now bzImage can be compiled as a completely relocatable image
1566 (CONFIG_RELOCATABLE=y) and be used to load and run from a different
1567 address. This option is mainly useful for the folks who don't want
1568 to use a bzImage for capturing the crash dump and want to use a
1569 vmlinux instead. vmlinux is not relocatable hence a kernel needs
1570 to be specifically compiled to run from a specific memory area
1571 (normally a reserved region) and this option comes handy.
1573 So if you are using bzImage for capturing the crash dump,
1574 leave the value here unchanged to 0x1000000 and set
1575 CONFIG_RELOCATABLE=y. Otherwise if you plan to use vmlinux
1576 for capturing the crash dump change this value to start of
1577 the reserved region. In other words, it can be set based on
1578 the "X" value as specified in the "crashkernel=YM@XM"
1579 command line boot parameter passed to the panic-ed
1580 kernel. Please take a look at Documentation/kdump/kdump.txt
1581 for more details about crash dumps.
1583 Usage of bzImage for capturing the crash dump is recommended as
1584 one does not have to build two kernels. Same kernel can be used
1585 as production kernel and capture kernel. Above option should have
1586 gone away after relocatable bzImage support is introduced. But it
1587 is present because there are users out there who continue to use
1588 vmlinux for dump capture. This option should go away down the
1591 Don't change this unless you know what you are doing.
1594 bool "Build a relocatable kernel"
1597 This builds a kernel image that retains relocation information
1598 so it can be loaded someplace besides the default 1MB.
1599 The relocations tend to make the kernel binary about 10% larger,
1600 but are discarded at runtime.
1602 One use is for the kexec on panic case where the recovery kernel
1603 must live at a different physical address than the primary
1606 Note: If CONFIG_RELOCATABLE=y, then the kernel runs from the address
1607 it has been loaded at and the compile time physical address
1608 (CONFIG_PHYSICAL_START) is ignored.
1610 # Relocation on x86-32 needs some additional build support
1611 config X86_NEED_RELOCS
1613 depends on X86_32 && RELOCATABLE
1615 config PHYSICAL_ALIGN
1616 hex "Alignment value to which kernel should be aligned" if X86_32
1618 range 0x2000 0x1000000
1620 This value puts the alignment restrictions on physical address
1621 where kernel is loaded and run from. Kernel is compiled for an
1622 address which meets above alignment restriction.
1624 If bootloader loads the kernel at a non-aligned address and
1625 CONFIG_RELOCATABLE is set, kernel will move itself to nearest
1626 address aligned to above value and run from there.
1628 If bootloader loads the kernel at a non-aligned address and
1629 CONFIG_RELOCATABLE is not set, kernel will ignore the run time
1630 load address and decompress itself to the address it has been
1631 compiled for and run from there. The address for which kernel is
1632 compiled already meets above alignment restrictions. Hence the
1633 end result is that kernel runs from a physical address meeting
1634 above alignment restrictions.
1636 Don't change this unless you know what you are doing.
1639 bool "Support for hot-pluggable CPUs"
1640 depends on SMP && HOTPLUG
1642 Say Y here to allow turning CPUs off and on. CPUs can be
1643 controlled through /sys/devices/system/cpu.
1644 ( Note: power management support will enable this option
1645 automatically on SMP systems. )
1646 Say N if you want to disable CPU hotplug.
1650 prompt "Compat VDSO support"
1651 depends on X86_32 || IA32_EMULATION
1653 Map the 32-bit VDSO to the predictable old-style address too.
1655 Say N here if you are running a sufficiently recent glibc
1656 version (2.3.3 or later), to remove the high-mapped
1657 VDSO mapping and to exclusively use the randomized VDSO.
1662 bool "Built-in kernel command line"
1664 Allow for specifying boot arguments to the kernel at
1665 build time. On some systems (e.g. embedded ones), it is
1666 necessary or convenient to provide some or all of the
1667 kernel boot arguments with the kernel itself (that is,
1668 to not rely on the boot loader to provide them.)
1670 To compile command line arguments into the kernel,
1671 set this option to 'Y', then fill in the
1672 the boot arguments in CONFIG_CMDLINE.
1674 Systems with fully functional boot loaders (i.e. non-embedded)
1675 should leave this option set to 'N'.
1678 string "Built-in kernel command string"
1679 depends on CMDLINE_BOOL
1682 Enter arguments here that should be compiled into the kernel
1683 image and used at boot time. If the boot loader provides a
1684 command line at boot time, it is appended to this string to
1685 form the full kernel command line, when the system boots.
1687 However, you can use the CONFIG_CMDLINE_OVERRIDE option to
1688 change this behavior.
1690 In most cases, the command line (whether built-in or provided
1691 by the boot loader) should specify the device for the root
1694 config CMDLINE_OVERRIDE
1695 bool "Built-in command line overrides boot loader arguments"
1696 depends on CMDLINE_BOOL
1698 Set this option to 'Y' to have the kernel ignore the boot loader
1699 command line, and use ONLY the built-in command line.
1701 This is used to work around broken boot loaders. This should
1702 be set to 'N' under normal conditions.
1706 config ARCH_ENABLE_MEMORY_HOTPLUG
1708 depends on X86_64 || (X86_32 && HIGHMEM)
1710 config ARCH_ENABLE_MEMORY_HOTREMOVE
1712 depends on MEMORY_HOTPLUG
1714 config USE_PERCPU_NUMA_NODE_ID
1718 menu "Power management and ACPI options"
1720 config ARCH_HIBERNATION_HEADER
1722 depends on X86_64 && HIBERNATION
1724 source "kernel/power/Kconfig"
1726 source "drivers/acpi/Kconfig"
1728 source "drivers/sfi/Kconfig"
1732 depends on APM || APM_MODULE
1735 tristate "APM (Advanced Power Management) BIOS support"
1736 depends on X86_32 && PM_SLEEP
1738 APM is a BIOS specification for saving power using several different
1739 techniques. This is mostly useful for battery powered laptops with
1740 APM compliant BIOSes. If you say Y here, the system time will be
1741 reset after a RESUME operation, the /proc/apm device will provide
1742 battery status information, and user-space programs will receive
1743 notification of APM "events" (e.g. battery status change).
1745 If you select "Y" here, you can disable actual use of the APM
1746 BIOS by passing the "apm=off" option to the kernel at boot time.
1748 Note that the APM support is almost completely disabled for
1749 machines with more than one CPU.
1751 In order to use APM, you will need supporting software. For location
1752 and more information, read <file:Documentation/power/apm-acpi.txt>
1753 and the Battery Powered Linux mini-HOWTO, available from
1754 <http://www.tldp.org/docs.html#howto>.
1756 This driver does not spin down disk drives (see the hdparm(8)
1757 manpage ("man 8 hdparm") for that), and it doesn't turn off
1758 VESA-compliant "green" monitors.
1760 This driver does not support the TI 4000M TravelMate and the ACER
1761 486/DX4/75 because they don't have compliant BIOSes. Many "green"
1762 desktop machines also don't have compliant BIOSes, and this driver
1763 may cause those machines to panic during the boot phase.
1765 Generally, if you don't have a battery in your machine, there isn't
1766 much point in using this driver and you should say N. If you get
1767 random kernel OOPSes or reboots that don't seem to be related to
1768 anything, try disabling/enabling this option (or disabling/enabling
1771 Some other things you should try when experiencing seemingly random,
1774 1) make sure that you have enough swap space and that it is
1776 2) pass the "no-hlt" option to the kernel
1777 3) switch on floating point emulation in the kernel and pass
1778 the "no387" option to the kernel
1779 4) pass the "floppy=nodma" option to the kernel
1780 5) pass the "mem=4M" option to the kernel (thereby disabling
1781 all but the first 4 MB of RAM)
1782 6) make sure that the CPU is not over clocked.
1783 7) read the sig11 FAQ at <http://www.bitwizard.nl/sig11/>
1784 8) disable the cache from your BIOS settings
1785 9) install a fan for the video card or exchange video RAM
1786 10) install a better fan for the CPU
1787 11) exchange RAM chips
1788 12) exchange the motherboard.
1790 To compile this driver as a module, choose M here: the
1791 module will be called apm.
1795 config APM_IGNORE_USER_SUSPEND
1796 bool "Ignore USER SUSPEND"
1798 This option will ignore USER SUSPEND requests. On machines with a
1799 compliant APM BIOS, you want to say N. However, on the NEC Versa M
1800 series notebooks, it is necessary to say Y because of a BIOS bug.
1802 config APM_DO_ENABLE
1803 bool "Enable PM at boot time"
1805 Enable APM features at boot time. From page 36 of the APM BIOS
1806 specification: "When disabled, the APM BIOS does not automatically
1807 power manage devices, enter the Standby State, enter the Suspend
1808 State, or take power saving steps in response to CPU Idle calls."
1809 This driver will make CPU Idle calls when Linux is idle (unless this
1810 feature is turned off -- see "Do CPU IDLE calls", below). This
1811 should always save battery power, but more complicated APM features
1812 will be dependent on your BIOS implementation. You may need to turn
1813 this option off if your computer hangs at boot time when using APM
1814 support, or if it beeps continuously instead of suspending. Turn
1815 this off if you have a NEC UltraLite Versa 33/C or a Toshiba
1816 T400CDT. This is off by default since most machines do fine without
1820 bool "Make CPU Idle calls when idle"
1822 Enable calls to APM CPU Idle/CPU Busy inside the kernel's idle loop.
1823 On some machines, this can activate improved power savings, such as
1824 a slowed CPU clock rate, when the machine is idle. These idle calls
1825 are made after the idle loop has run for some length of time (e.g.,
1826 333 mS). On some machines, this will cause a hang at boot time or
1827 whenever the CPU becomes idle. (On machines with more than one CPU,
1828 this option does nothing.)
1830 config APM_DISPLAY_BLANK
1831 bool "Enable console blanking using APM"
1833 Enable console blanking using the APM. Some laptops can use this to
1834 turn off the LCD backlight when the screen blanker of the Linux
1835 virtual console blanks the screen. Note that this is only used by
1836 the virtual console screen blanker, and won't turn off the backlight
1837 when using the X Window system. This also doesn't have anything to
1838 do with your VESA-compliant power-saving monitor. Further, this
1839 option doesn't work for all laptops -- it might not turn off your
1840 backlight at all, or it might print a lot of errors to the console,
1841 especially if you are using gpm.
1843 config APM_ALLOW_INTS
1844 bool "Allow interrupts during APM BIOS calls"
1846 Normally we disable external interrupts while we are making calls to
1847 the APM BIOS as a measure to lessen the effects of a badly behaving
1848 BIOS implementation. The BIOS should reenable interrupts if it
1849 needs to. Unfortunately, some BIOSes do not -- especially those in
1850 many of the newer IBM Thinkpads. If you experience hangs when you
1851 suspend, try setting this to Y. Otherwise, say N.
1855 source "drivers/cpufreq/Kconfig"
1857 source "drivers/cpuidle/Kconfig"
1859 source "drivers/idle/Kconfig"
1864 menu "Bus options (PCI etc.)"
1869 select ARCH_SUPPORTS_MSI if (X86_LOCAL_APIC && X86_IO_APIC)
1871 Find out whether you have a PCI motherboard. PCI is the name of a
1872 bus system, i.e. the way the CPU talks to the other stuff inside
1873 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
1874 VESA. If you have PCI, say Y, otherwise N.
1877 prompt "PCI access mode"
1878 depends on X86_32 && PCI
1881 On PCI systems, the BIOS can be used to detect the PCI devices and
1882 determine their configuration. However, some old PCI motherboards
1883 have BIOS bugs and may crash if this is done. Also, some embedded
1884 PCI-based systems don't have any BIOS at all. Linux can also try to
1885 detect the PCI hardware directly without using the BIOS.
1887 With this option, you can specify how Linux should detect the
1888 PCI devices. If you choose "BIOS", the BIOS will be used,
1889 if you choose "Direct", the BIOS won't be used, and if you
1890 choose "MMConfig", then PCI Express MMCONFIG will be used.
1891 If you choose "Any", the kernel will try MMCONFIG, then the
1892 direct access method and falls back to the BIOS if that doesn't
1893 work. If unsure, go with the default, which is "Any".
1898 config PCI_GOMMCONFIG
1915 depends on X86_32 && PCI && (PCI_GOBIOS || PCI_GOANY)
1917 # x86-64 doesn't support PCI BIOS access from long mode so always go direct.
1920 depends on PCI && (X86_64 || (PCI_GODIRECT || PCI_GOANY || PCI_GOOLPC || PCI_GOMMCONFIG))
1924 depends on X86_32 && PCI && (ACPI || SFI) && (PCI_GOMMCONFIG || PCI_GOANY)
1928 depends on PCI && OLPC && (PCI_GOOLPC || PCI_GOANY)
1932 depends on PCI && XEN
1940 bool "Support mmconfig PCI config space access"
1941 depends on X86_64 && PCI && ACPI
1943 config PCI_CNB20LE_QUIRK
1944 bool "Read CNB20LE Host Bridge Windows" if EXPERT
1946 depends on PCI && EXPERIMENTAL
1948 Read the PCI windows out of the CNB20LE host bridge. This allows
1949 PCI hotplug to work on systems with the CNB20LE chipset which do
1952 There's no public spec for this chipset, and this functionality
1953 is known to be incomplete.
1955 You should say N unless you know you need this.
1957 source "drivers/pci/pcie/Kconfig"
1959 source "drivers/pci/Kconfig"
1961 # x86_64 have no ISA slots, but can have ISA-style DMA.
1963 bool "ISA-style DMA support" if (X86_64 && EXPERT)
1966 Enables ISA-style DMA support for devices requiring such controllers.
1974 Find out whether you have ISA slots on your motherboard. ISA is the
1975 name of a bus system, i.e. the way the CPU talks to the other stuff
1976 inside your box. Other bus systems are PCI, EISA, MicroChannel
1977 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
1978 newer boards don't support it. If you have ISA, say Y, otherwise N.
1984 The Extended Industry Standard Architecture (EISA) bus was
1985 developed as an open alternative to the IBM MicroChannel bus.
1987 The EISA bus provided some of the features of the IBM MicroChannel
1988 bus while maintaining backward compatibility with cards made for
1989 the older ISA bus. The EISA bus saw limited use between 1988 and
1990 1995 when it was made obsolete by the PCI bus.
1992 Say Y here if you are building a kernel for an EISA-based machine.
1996 source "drivers/eisa/Kconfig"
2001 MicroChannel Architecture is found in some IBM PS/2 machines and
2002 laptops. It is a bus system similar to PCI or ISA. See
2003 <file:Documentation/mca.txt> (and especially the web page given
2004 there) before attempting to build an MCA bus kernel.
2006 source "drivers/mca/Kconfig"
2009 tristate "NatSemi SCx200 support"
2011 This provides basic support for National Semiconductor's
2012 (now AMD's) Geode processors. The driver probes for the
2013 PCI-IDs of several on-chip devices, so its a good dependency
2014 for other scx200_* drivers.
2016 If compiled as a module, the driver is named scx200.
2018 config SCx200HR_TIMER
2019 tristate "NatSemi SCx200 27MHz High-Resolution Timer Support"
2023 This driver provides a clocksource built upon the on-chip
2024 27MHz high-resolution timer. Its also a workaround for
2025 NSC Geode SC-1100's buggy TSC, which loses time when the
2026 processor goes idle (as is done by the scheduler). The
2027 other workaround is idle=poll boot option.
2030 bool "One Laptop Per Child support"
2036 Add support for detecting the unique features of the OLPC
2040 bool "OLPC XO-1 Power Management"
2041 depends on OLPC && MFD_CS5535 && PM_SLEEP
2044 Add support for poweroff and suspend of the OLPC XO-1 laptop.
2047 bool "OLPC XO-1 Real Time Clock"
2048 depends on OLPC_XO1_PM && RTC_DRV_CMOS
2050 Add support for the XO-1 real time clock, which can be used as a
2051 programmable wakeup source.
2054 bool "OLPC XO-1 SCI extras"
2055 depends on OLPC && OLPC_XO1_PM
2060 Add support for SCI-based features of the OLPC XO-1 laptop:
2061 - EC-driven system wakeups
2065 - AC adapter status updates
2066 - Battery status updates
2068 config OLPC_XO15_SCI
2069 bool "OLPC XO-1.5 SCI extras"
2070 depends on OLPC && ACPI
2073 Add support for SCI-based features of the OLPC XO-1.5 laptop:
2074 - EC-driven system wakeups
2075 - AC adapter status updates
2076 - Battery status updates
2079 bool "PCEngines ALIX System Support (LED setup)"
2082 This option enables system support for the PCEngines ALIX.
2083 At present this just sets up LEDs for GPIO control on
2084 ALIX2/3/6 boards. However, other system specific setup should
2087 Note: You must still enable the drivers for GPIO and LED support
2088 (GPIO_CS5535 & LEDS_GPIO) to actually use the LEDs
2090 Note: You have to set alix.force=1 for boards with Award BIOS.
2096 depends on CPU_SUP_AMD && PCI
2098 source "drivers/pcmcia/Kconfig"
2100 source "drivers/pci/hotplug/Kconfig"
2103 bool "RapidIO support"
2107 If you say Y here, the kernel will include drivers and
2108 infrastructure code to support RapidIO interconnect devices.
2110 source "drivers/rapidio/Kconfig"
2115 menu "Executable file formats / Emulations"
2117 source "fs/Kconfig.binfmt"
2119 config IA32_EMULATION
2120 bool "IA32 Emulation"
2122 select COMPAT_BINFMT_ELF
2124 Include code to run 32-bit programs under a 64-bit kernel. You should
2125 likely turn this on, unless you're 100% sure that you don't have any
2126 32-bit programs left.
2129 tristate "IA32 a.out support"
2130 depends on IA32_EMULATION
2132 Support old a.out binaries in the 32bit emulation.
2136 depends on IA32_EMULATION
2138 config COMPAT_FOR_U64_ALIGNMENT
2142 config SYSVIPC_COMPAT
2144 depends on COMPAT && SYSVIPC
2148 depends on COMPAT && KEYS
2154 config HAVE_ATOMIC_IOMAP
2158 config HAVE_TEXT_POKE_SMP
2160 select STOP_MACHINE if SMP
2162 source "net/Kconfig"
2164 source "drivers/Kconfig"
2166 source "drivers/firmware/Kconfig"
2170 source "arch/x86/Kconfig.debug"
2172 source "security/Kconfig"
2174 source "crypto/Kconfig"
2176 source "arch/x86/kvm/Kconfig"
2178 source "lib/Kconfig"