3 bool "64-bit kernel" if ARCH = "x86"
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
18 select X86_DEV_DMA_OPS
19 select ARCH_USE_CMPXCHG_LOCKREF
25 select ACPI_SYSTEM_POWER_STATES_SUPPORT if ACPI
26 select ARCH_MIGHT_HAVE_ACPI_PDC if ACPI
27 select ARCH_HAS_DEBUG_STRICT_USER_COPY_CHECKS
28 select ARCH_HAS_FAST_MULTIPLIER
29 select ARCH_HAS_GCOV_PROFILE_ALL
30 select ARCH_MIGHT_HAVE_PC_PARPORT
31 select ARCH_MIGHT_HAVE_PC_SERIO
32 select HAVE_AOUT if X86_32
33 select HAVE_UNSTABLE_SCHED_CLOCK
34 select ARCH_SUPPORTS_NUMA_BALANCING if X86_64
35 select ARCH_SUPPORTS_INT128 if X86_64
38 select HAVE_PCSPKR_PLATFORM
39 select HAVE_PERF_EVENTS
40 select HAVE_IOREMAP_PROT
43 select HAVE_MEMBLOCK_NODE_MAP
44 select ARCH_DISCARD_MEMBLOCK
45 select ARCH_WANT_OPTIONAL_GPIOLIB
46 select ARCH_WANT_FRAME_POINTERS
48 select HAVE_DMA_CONTIGUOUS
49 select HAVE_KRETPROBES
50 select GENERIC_EARLY_IOREMAP
52 select HAVE_KPROBES_ON_FTRACE
53 select HAVE_FTRACE_MCOUNT_RECORD
54 select HAVE_FENTRY if X86_64
55 select HAVE_C_RECORDMCOUNT
56 select HAVE_DYNAMIC_FTRACE
57 select HAVE_DYNAMIC_FTRACE_WITH_REGS
58 select HAVE_FUNCTION_TRACER
59 select HAVE_FUNCTION_GRAPH_TRACER
60 select HAVE_FUNCTION_GRAPH_FP_TEST
61 select HAVE_SYSCALL_TRACEPOINTS
62 select SYSCTL_EXCEPTION_TRACE
65 select HAVE_ARCH_TRACEHOOK
66 select HAVE_GENERIC_DMA_COHERENT if X86_32
67 select HAVE_EFFICIENT_UNALIGNED_ACCESS
68 select USER_STACKTRACE_SUPPORT
69 select HAVE_REGS_AND_STACK_ACCESS_API
70 select HAVE_DMA_API_DEBUG
71 select HAVE_KERNEL_GZIP
72 select HAVE_KERNEL_BZIP2
73 select HAVE_KERNEL_LZMA
75 select HAVE_KERNEL_LZO
76 select HAVE_KERNEL_LZ4
77 select HAVE_HW_BREAKPOINT
78 select HAVE_MIXED_BREAKPOINTS_REGS
80 select HAVE_PERF_EVENTS_NMI
82 select HAVE_PERF_USER_STACK_DUMP
83 select HAVE_DEBUG_KMEMLEAK
85 select HAVE_ALIGNED_STRUCT_PAGE if SLUB
86 select HAVE_CMPXCHG_LOCAL
87 select HAVE_CMPXCHG_DOUBLE
88 select HAVE_ARCH_KMEMCHECK
89 select HAVE_ARCH_KASAN if X86_64 && SPARSEMEM_VMEMMAP
90 select HAVE_USER_RETURN_NOTIFIER
91 select ARCH_HAS_ELF_RANDOMIZE
92 select HAVE_ARCH_JUMP_LABEL
93 select ARCH_HAS_ATOMIC64_DEC_IF_POSITIVE
95 select GENERIC_FIND_FIRST_BIT
96 select GENERIC_IRQ_PROBE
97 select GENERIC_PENDING_IRQ if SMP
98 select GENERIC_IRQ_SHOW
99 select GENERIC_CLOCKEVENTS_MIN_ADJUST
100 select IRQ_FORCED_THREADING
101 select HAVE_BPF_JIT if X86_64
102 select HAVE_ARCH_TRANSPARENT_HUGEPAGE
103 select HAVE_ARCH_HUGE_VMAP if X86_64 || X86_PAE
104 select ARCH_HAS_SG_CHAIN
106 select ARCH_HAVE_NMI_SAFE_CMPXCHG
108 select DCACHE_WORD_ACCESS
109 select GENERIC_SMP_IDLE_THREAD
110 select ARCH_WANT_IPC_PARSE_VERSION if X86_32
111 select HAVE_ARCH_SECCOMP_FILTER
112 select BUILDTIME_EXTABLE_SORT
113 select GENERIC_CMOS_UPDATE
114 select HAVE_ARCH_SOFT_DIRTY if X86_64
115 select CLOCKSOURCE_WATCHDOG
116 select GENERIC_CLOCKEVENTS
117 select ARCH_CLOCKSOURCE_DATA
118 select CLOCKSOURCE_VALIDATE_LAST_CYCLE
119 select GENERIC_CLOCKEVENTS_BROADCAST if X86_64 || (X86_32 && X86_LOCAL_APIC)
120 select GENERIC_TIME_VSYSCALL
121 select GENERIC_STRNCPY_FROM_USER
122 select GENERIC_STRNLEN_USER
123 select HAVE_CONTEXT_TRACKING if X86_64
124 select HAVE_IRQ_TIME_ACCOUNTING
126 select MODULES_USE_ELF_REL if X86_32
127 select MODULES_USE_ELF_RELA if X86_64
128 select CLONE_BACKWARDS if X86_32
129 select ARCH_USE_BUILTIN_BSWAP
130 select ARCH_USE_QUEUED_SPINLOCKS
131 select ARCH_USE_QUEUED_RWLOCKS
132 select OLD_SIGSUSPEND3 if X86_32 || IA32_EMULATION
133 select OLD_SIGACTION if X86_32
134 select COMPAT_OLD_SIGACTION if IA32_EMULATION
136 select HAVE_DEBUG_STACKOVERFLOW
137 select HAVE_IRQ_EXIT_ON_IRQ_STACK if X86_64
138 select HAVE_CC_STACKPROTECTOR
139 select GENERIC_CPU_AUTOPROBE
140 select HAVE_ARCH_AUDITSYSCALL
141 select ARCH_SUPPORTS_ATOMIC_RMW
142 select HAVE_ACPI_APEI if ACPI
143 select HAVE_ACPI_APEI_NMI if ACPI
144 select ACPI_LEGACY_TABLES_LOOKUP if ACPI
145 select X86_FEATURE_NAMES if PROC_FS
148 config INSTRUCTION_DECODER
150 depends on KPROBES || PERF_EVENTS || UPROBES
152 config PERF_EVENTS_INTEL_UNCORE
154 depends on PERF_EVENTS && CPU_SUP_INTEL && PCI
158 default "elf32-i386" if X86_32
159 default "elf64-x86-64" if X86_64
161 config ARCH_DEFCONFIG
163 default "arch/x86/configs/i386_defconfig" if X86_32
164 default "arch/x86/configs/x86_64_defconfig" if X86_64
166 config LOCKDEP_SUPPORT
169 config STACKTRACE_SUPPORT
172 config HAVE_LATENCYTOP_SUPPORT
181 config NEED_DMA_MAP_STATE
183 depends on X86_64 || INTEL_IOMMU || DMA_API_DEBUG || SWIOTLB
185 config NEED_SG_DMA_LENGTH
188 config GENERIC_ISA_DMA
190 depends on ISA_DMA_API
195 select GENERIC_BUG_RELATIVE_POINTERS if X86_64
197 config GENERIC_BUG_RELATIVE_POINTERS
200 config GENERIC_HWEIGHT
203 config ARCH_MAY_HAVE_PC_FDC
205 depends on ISA_DMA_API
207 config RWSEM_XCHGADD_ALGORITHM
210 config GENERIC_CALIBRATE_DELAY
213 config ARCH_HAS_CPU_RELAX
216 config ARCH_HAS_CACHE_LINE_SIZE
219 config HAVE_SETUP_PER_CPU_AREA
222 config NEED_PER_CPU_EMBED_FIRST_CHUNK
225 config NEED_PER_CPU_PAGE_FIRST_CHUNK
228 config ARCH_HIBERNATION_POSSIBLE
231 config ARCH_SUSPEND_POSSIBLE
234 config ARCH_WANT_HUGE_PMD_SHARE
237 config ARCH_WANT_GENERAL_HUGETLB
246 config ARCH_SUPPORTS_OPTIMIZED_INLINING
249 config ARCH_SUPPORTS_DEBUG_PAGEALLOC
252 config HAVE_INTEL_TXT
254 depends on INTEL_IOMMU && ACPI
258 depends on X86_32 && SMP
262 depends on X86_64 && SMP
268 config X86_32_LAZY_GS
270 depends on X86_32 && !CC_STACKPROTECTOR
272 config ARCH_HWEIGHT_CFLAGS
274 default "-fcall-saved-ecx -fcall-saved-edx" if X86_32
275 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
277 config ARCH_SUPPORTS_UPROBES
280 config FIX_EARLYCON_MEM
283 config PGTABLE_LEVELS
289 source "init/Kconfig"
290 source "kernel/Kconfig.freezer"
292 menu "Processor type and features"
295 bool "DMA memory allocation support" if EXPERT
298 DMA memory allocation support allows devices with less than 32-bit
299 addressing to allocate within the first 16MB of address space.
300 Disable if no such devices will be used.
305 bool "Symmetric multi-processing support"
307 This enables support for systems with more than one CPU. If you have
308 a system with only one CPU, say N. If you have a system with more
311 If you say N here, the kernel will run on uni- and multiprocessor
312 machines, but will use only one CPU of a multiprocessor machine. If
313 you say Y here, the kernel will run on many, but not all,
314 uniprocessor machines. On a uniprocessor machine, the kernel
315 will run faster if you say N here.
317 Note that if you say Y here and choose architecture "586" or
318 "Pentium" under "Processor family", the kernel will not work on 486
319 architectures. Similarly, multiprocessor kernels for the "PPro"
320 architecture may not work on all Pentium based boards.
322 People using multiprocessor machines who say Y here should also say
323 Y to "Enhanced Real Time Clock Support", below. The "Advanced Power
324 Management" code will be disabled if you say Y here.
326 See also <file:Documentation/x86/i386/IO-APIC.txt>,
327 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
328 <http://www.tldp.org/docs.html#howto>.
330 If you don't know what to do here, say N.
332 config X86_FEATURE_NAMES
333 bool "Processor feature human-readable names" if EMBEDDED
336 This option compiles in a table of x86 feature bits and corresponding
337 names. This is required to support /proc/cpuinfo and a few kernel
338 messages. You can disable this to save space, at the expense of
339 making those few kernel messages show numeric feature bits instead.
344 bool "Support x2apic"
345 depends on X86_LOCAL_APIC && X86_64 && (IRQ_REMAP || HYPERVISOR_GUEST)
347 This enables x2apic support on CPUs that have this feature.
349 This allows 32-bit apic IDs (so it can support very large systems),
350 and accesses the local apic via MSRs not via mmio.
352 If you don't know what to do here, say N.
355 bool "Enable MPS table" if ACPI || SFI
357 depends on X86_LOCAL_APIC
359 For old smp systems that do not have proper acpi support. Newer systems
360 (esp with 64bit cpus) with acpi support, MADT and DSDT will override it
363 bool "Support for big SMP systems with more than 8 CPUs"
364 depends on X86_32 && SMP
366 This option is needed for the systems that have more than 8 CPUs
370 depends on X86_GOLDFISH
373 config X86_EXTENDED_PLATFORM
374 bool "Support for extended (non-PC) x86 platforms"
377 If you disable this option then the kernel will only support
378 standard PC platforms. (which covers the vast majority of
381 If you enable this option then you'll be able to select support
382 for the following (non-PC) 32 bit x86 platforms:
383 Goldfish (Android emulator)
386 SGI 320/540 (Visual Workstation)
387 STA2X11-based (e.g. Northville)
388 Moorestown MID devices
390 If you have one of these systems, or if you want to build a
391 generic distribution kernel, say Y here - otherwise say N.
395 config X86_EXTENDED_PLATFORM
396 bool "Support for extended (non-PC) x86 platforms"
399 If you disable this option then the kernel will only support
400 standard PC platforms. (which covers the vast majority of
403 If you enable this option then you'll be able to select support
404 for the following (non-PC) 64 bit x86 platforms:
409 If you have one of these systems, or if you want to build a
410 generic distribution kernel, say Y here - otherwise say N.
412 # This is an alphabetically sorted list of 64 bit extended platforms
413 # Please maintain the alphabetic order if and when there are additions
415 bool "Numascale NumaChip"
417 depends on X86_EXTENDED_PLATFORM
420 depends on X86_X2APIC
421 depends on PCI_MMCONFIG
423 Adds support for Numascale NumaChip large-SMP systems. Needed to
424 enable more than ~168 cores.
425 If you don't have one of these, you should say N here.
429 select HYPERVISOR_GUEST
431 depends on X86_64 && PCI
432 depends on X86_EXTENDED_PLATFORM
435 Support for ScaleMP vSMP systems. Say 'Y' here if this kernel is
436 supposed to run on these EM64T-based machines. Only choose this option
437 if you have one of these machines.
440 bool "SGI Ultraviolet"
442 depends on X86_EXTENDED_PLATFORM
444 depends on X86_X2APIC
447 This option is needed in order to support SGI Ultraviolet systems.
448 If you don't have one of these, you should say N here.
450 # Following is an alphabetically sorted list of 32 bit extended platforms
451 # Please maintain the alphabetic order if and when there are additions
454 bool "Goldfish (Virtual Platform)"
455 depends on X86_EXTENDED_PLATFORM
457 Enable support for the Goldfish virtual platform used primarily
458 for Android development. Unless you are building for the Android
459 Goldfish emulator say N here.
462 bool "CE4100 TV platform"
464 depends on PCI_GODIRECT
465 depends on X86_IO_APIC
467 depends on X86_EXTENDED_PLATFORM
468 select X86_REBOOTFIXUPS
470 select OF_EARLY_FLATTREE
472 Select for the Intel CE media processor (CE4100) SOC.
473 This option compiles in support for the CE4100 SOC for settop
474 boxes and media devices.
477 bool "Intel MID platform support"
479 depends on X86_EXTENDED_PLATFORM
480 depends on X86_PLATFORM_DEVICES
483 depends on X86_IO_APIC
489 select MFD_INTEL_MSIC
491 Select to build a kernel capable of supporting Intel MID (Mobile
492 Internet Device) platform systems which do not have the PCI legacy
493 interfaces. If you are building for a PC class system say N here.
495 Intel MID platforms are based on an Intel processor and chipset which
496 consume less power than most of the x86 derivatives.
498 config X86_INTEL_QUARK
499 bool "Intel Quark platform support"
501 depends on X86_EXTENDED_PLATFORM
502 depends on X86_PLATFORM_DEVICES
506 depends on X86_IO_APIC
511 Select to include support for Quark X1000 SoC.
512 Say Y here if you have a Quark based system such as the Arduino
513 compatible Intel Galileo.
515 config X86_INTEL_LPSS
516 bool "Intel Low Power Subsystem Support"
521 Select to build support for Intel Low Power Subsystem such as
522 found on Intel Lynxpoint PCH. Selecting this option enables
523 things like clock tree (common clock framework) and pincontrol
524 which are needed by the LPSS peripheral drivers.
526 config X86_AMD_PLATFORM_DEVICE
527 bool "AMD ACPI2Platform devices support"
532 Select to interpret AMD specific ACPI device to platform device
533 such as I2C, UART, GPIO found on AMD Carrizo and later chipsets.
534 I2C and UART depend on COMMON_CLK to set clock. GPIO driver is
535 implemented under PINCTRL subsystem.
538 tristate "Intel SoC IOSF Sideband support for SoC platforms"
541 This option enables sideband register access support for Intel SoC
542 platforms. On these platforms the IOSF sideband is used in lieu of
543 MSR's for some register accesses, mostly but not limited to thermal
544 and power. Drivers may query the availability of this device to
545 determine if they need the sideband in order to work on these
546 platforms. The sideband is available on the following SoC products.
547 This list is not meant to be exclusive.
552 You should say Y if you are running a kernel on one of these SoC's.
554 config IOSF_MBI_DEBUG
555 bool "Enable IOSF sideband access through debugfs"
556 depends on IOSF_MBI && DEBUG_FS
558 Select this option to expose the IOSF sideband access registers (MCR,
559 MDR, MCRX) through debugfs to write and read register information from
560 different units on the SoC. This is most useful for obtaining device
561 state information for debug and analysis. As this is a general access
562 mechanism, users of this option would have specific knowledge of the
563 device they want to access.
565 If you don't require the option or are in doubt, say N.
568 bool "RDC R-321x SoC"
570 depends on X86_EXTENDED_PLATFORM
572 select X86_REBOOTFIXUPS
574 This option is needed for RDC R-321x system-on-chip, also known
576 If you don't have one of these chips, you should say N here.
578 config X86_32_NON_STANDARD
579 bool "Support non-standard 32-bit SMP architectures"
580 depends on X86_32 && SMP
581 depends on X86_EXTENDED_PLATFORM
583 This option compiles in the bigsmp and STA2X11 default
584 subarchitectures. It is intended for a generic binary
585 kernel. If you select them all, kernel will probe it one by
586 one and will fallback to default.
588 # Alphabetically sorted list of Non standard 32 bit platforms
590 config X86_SUPPORTS_MEMORY_FAILURE
592 # MCE code calls memory_failure():
594 # On 32-bit this adds too big of NODES_SHIFT and we run out of page flags:
595 # On 32-bit SPARSEMEM adds too big of SECTIONS_WIDTH:
596 depends on X86_64 || !SPARSEMEM
597 select ARCH_SUPPORTS_MEMORY_FAILURE
600 bool "STA2X11 Companion Chip Support"
601 depends on X86_32_NON_STANDARD && PCI
602 select X86_DEV_DMA_OPS
606 select ARCH_REQUIRE_GPIOLIB
609 This adds support for boards based on the STA2X11 IO-Hub,
610 a.k.a. "ConneXt". The chip is used in place of the standard
611 PC chipset, so all "standard" peripherals are missing. If this
612 option is selected the kernel will still be able to boot on
613 standard PC machines.
616 tristate "Eurobraille/Iris poweroff module"
619 The Iris machines from EuroBraille do not have APM or ACPI support
620 to shut themselves down properly. A special I/O sequence is
621 needed to do so, which is what this module does at
624 This is only for Iris machines from EuroBraille.
628 config SCHED_OMIT_FRAME_POINTER
630 prompt "Single-depth WCHAN output"
633 Calculate simpler /proc/<PID>/wchan values. If this option
634 is disabled then wchan values will recurse back to the
635 caller function. This provides more accurate wchan values,
636 at the expense of slightly more scheduling overhead.
638 If in doubt, say "Y".
640 menuconfig HYPERVISOR_GUEST
641 bool "Linux guest support"
643 Say Y here to enable options for running Linux under various hyper-
644 visors. This option enables basic hypervisor detection and platform
647 If you say N, all options in this submenu will be skipped and
648 disabled, and Linux guest support won't be built in.
653 bool "Enable paravirtualization code"
655 This changes the kernel so it can modify itself when it is run
656 under a hypervisor, potentially improving performance significantly
657 over full virtualization. However, when run without a hypervisor
658 the kernel is theoretically slower and slightly larger.
660 config PARAVIRT_DEBUG
661 bool "paravirt-ops debugging"
662 depends on PARAVIRT && DEBUG_KERNEL
664 Enable to debug paravirt_ops internals. Specifically, BUG if
665 a paravirt_op is missing when it is called.
667 config PARAVIRT_SPINLOCKS
668 bool "Paravirtualization layer for spinlocks"
669 depends on PARAVIRT && SMP
670 select UNINLINE_SPIN_UNLOCK if !QUEUED_SPINLOCKS
672 Paravirtualized spinlocks allow a pvops backend to replace the
673 spinlock implementation with something virtualization-friendly
674 (for example, block the virtual CPU rather than spinning).
676 It has a minimal impact on native kernels and gives a nice performance
677 benefit on paravirtualized KVM / Xen kernels.
679 If you are unsure how to answer this question, answer Y.
681 source "arch/x86/xen/Kconfig"
684 bool "KVM Guest support (including kvmclock)"
686 select PARAVIRT_CLOCK
689 This option enables various optimizations for running under the KVM
690 hypervisor. It includes a paravirtualized clock, so that instead
691 of relying on a PIT (or probably other) emulation by the
692 underlying device model, the host provides the guest with
693 timing infrastructure such as time of day, and system time
696 bool "Enable debug information for KVM Guests in debugfs"
697 depends on KVM_GUEST && DEBUG_FS
700 This option enables collection of various statistics for KVM guest.
701 Statistics are displayed in debugfs filesystem. Enabling this option
702 may incur significant overhead.
704 source "arch/x86/lguest/Kconfig"
706 config PARAVIRT_TIME_ACCOUNTING
707 bool "Paravirtual steal time accounting"
711 Select this option to enable fine granularity task steal time
712 accounting. Time spent executing other tasks in parallel with
713 the current vCPU is discounted from the vCPU power. To account for
714 that, there can be a small performance impact.
716 If in doubt, say N here.
718 config PARAVIRT_CLOCK
721 endif #HYPERVISOR_GUEST
726 source "arch/x86/Kconfig.cpu"
730 prompt "HPET Timer Support" if X86_32
732 Use the IA-PC HPET (High Precision Event Timer) to manage
733 time in preference to the PIT and RTC, if a HPET is
735 HPET is the next generation timer replacing legacy 8254s.
736 The HPET provides a stable time base on SMP
737 systems, unlike the TSC, but it is more expensive to access,
738 as it is off-chip. You can find the HPET spec at
739 <http://www.intel.com/hardwaredesign/hpetspec_1.pdf>.
741 You can safely choose Y here. However, HPET will only be
742 activated if the platform and the BIOS support this feature.
743 Otherwise the 8254 will be used for timing services.
745 Choose N to continue using the legacy 8254 timer.
747 config HPET_EMULATE_RTC
749 depends on HPET_TIMER && (RTC=y || RTC=m || RTC_DRV_CMOS=m || RTC_DRV_CMOS=y)
752 def_bool y if X86_INTEL_MID
753 prompt "Intel MID APB Timer Support" if X86_INTEL_MID
755 depends on X86_INTEL_MID && SFI
757 APB timer is the replacement for 8254, HPET on X86 MID platforms.
758 The APBT provides a stable time base on SMP
759 systems, unlike the TSC, but it is more expensive to access,
760 as it is off-chip. APB timers are always running regardless of CPU
761 C states, they are used as per CPU clockevent device when possible.
763 # Mark as expert because too many people got it wrong.
764 # The code disables itself when not needed.
767 select DMI_SCAN_MACHINE_NON_EFI_FALLBACK
768 bool "Enable DMI scanning" if EXPERT
770 Enabled scanning of DMI to identify machine quirks. Say Y
771 here unless you have verified that your setup is not
772 affected by entries in the DMI blacklist. Required by PNP
776 bool "Old AMD GART IOMMU support"
778 depends on X86_64 && PCI && AMD_NB
780 Provides a driver for older AMD Athlon64/Opteron/Turion/Sempron
781 GART based hardware IOMMUs.
783 The GART supports full DMA access for devices with 32-bit access
784 limitations, on systems with more than 3 GB. This is usually needed
785 for USB, sound, many IDE/SATA chipsets and some other devices.
787 Newer systems typically have a modern AMD IOMMU, supported via
788 the CONFIG_AMD_IOMMU=y config option.
790 In normal configurations this driver is only active when needed:
791 there's more than 3 GB of memory and the system contains a
792 32-bit limited device.
797 bool "IBM Calgary IOMMU support"
799 depends on X86_64 && PCI
801 Support for hardware IOMMUs in IBM's xSeries x366 and x460
802 systems. Needed to run systems with more than 3GB of memory
803 properly with 32-bit PCI devices that do not support DAC
804 (Double Address Cycle). Calgary also supports bus level
805 isolation, where all DMAs pass through the IOMMU. This
806 prevents them from going anywhere except their intended
807 destination. This catches hard-to-find kernel bugs and
808 mis-behaving drivers and devices that do not use the DMA-API
809 properly to set up their DMA buffers. The IOMMU can be
810 turned off at boot time with the iommu=off parameter.
811 Normally the kernel will make the right choice by itself.
814 config CALGARY_IOMMU_ENABLED_BY_DEFAULT
816 prompt "Should Calgary be enabled by default?"
817 depends on CALGARY_IOMMU
819 Should Calgary be enabled by default? if you choose 'y', Calgary
820 will be used (if it exists). If you choose 'n', Calgary will not be
821 used even if it exists. If you choose 'n' and would like to use
822 Calgary anyway, pass 'iommu=calgary' on the kernel command line.
825 # need this always selected by IOMMU for the VIA workaround
829 Support for software bounce buffers used on x86-64 systems
830 which don't have a hardware IOMMU. Using this PCI devices
831 which can only access 32-bits of memory can be used on systems
832 with more than 3 GB of memory.
837 depends on CALGARY_IOMMU || GART_IOMMU || SWIOTLB || AMD_IOMMU
840 bool "Enable Maximum number of SMP Processors and NUMA Nodes"
841 depends on X86_64 && SMP && DEBUG_KERNEL
842 select CPUMASK_OFFSTACK
844 Enable maximum number of CPUS and NUMA Nodes for this architecture.
848 int "Maximum number of CPUs" if SMP && !MAXSMP
849 range 2 8 if SMP && X86_32 && !X86_BIGSMP
850 range 2 512 if SMP && !MAXSMP && !CPUMASK_OFFSTACK
851 range 2 8192 if SMP && !MAXSMP && CPUMASK_OFFSTACK && X86_64
853 default "8192" if MAXSMP
854 default "32" if SMP && X86_BIGSMP
855 default "8" if SMP && X86_32
858 This allows you to specify the maximum number of CPUs which this
859 kernel will support. If CPUMASK_OFFSTACK is enabled, the maximum
860 supported value is 8192, otherwise the maximum value is 512. The
861 minimum value which makes sense is 2.
863 This is purely to save memory - each supported CPU adds
864 approximately eight kilobytes to the kernel image.
867 bool "SMT (Hyperthreading) scheduler support"
870 SMT scheduler support improves the CPU scheduler's decision making
871 when dealing with Intel Pentium 4 chips with HyperThreading at a
872 cost of slightly increased overhead in some places. If unsure say
877 prompt "Multi-core scheduler support"
880 Multi-core scheduler support improves the CPU scheduler's decision
881 making when dealing with multi-core CPU chips at a cost of slightly
882 increased overhead in some places. If unsure say N here.
884 source "kernel/Kconfig.preempt"
888 depends on !SMP && X86_LOCAL_APIC
891 bool "Local APIC support on uniprocessors" if !PCI_MSI
893 depends on X86_32 && !SMP && !X86_32_NON_STANDARD
895 A local APIC (Advanced Programmable Interrupt Controller) is an
896 integrated interrupt controller in the CPU. If you have a single-CPU
897 system which has a processor with a local APIC, you can say Y here to
898 enable and use it. If you say Y here even though your machine doesn't
899 have a local APIC, then the kernel will still run with no slowdown at
900 all. The local APIC supports CPU-generated self-interrupts (timer,
901 performance counters), and the NMI watchdog which detects hard
905 bool "IO-APIC support on uniprocessors"
906 depends on X86_UP_APIC
908 An IO-APIC (I/O Advanced Programmable Interrupt Controller) is an
909 SMP-capable replacement for PC-style interrupt controllers. Most
910 SMP systems and many recent uniprocessor systems have one.
912 If you have a single-CPU system with an IO-APIC, you can say Y here
913 to use it. If you say Y here even though your machine doesn't have
914 an IO-APIC, then the kernel will still run with no slowdown at all.
916 config X86_LOCAL_APIC
918 depends on X86_64 || SMP || X86_32_NON_STANDARD || X86_UP_APIC || PCI_MSI
919 select IRQ_DOMAIN_HIERARCHY
920 select PCI_MSI_IRQ_DOMAIN if PCI_MSI
924 depends on X86_LOCAL_APIC || X86_UP_IOAPIC
926 config X86_REROUTE_FOR_BROKEN_BOOT_IRQS
927 bool "Reroute for broken boot IRQs"
928 depends on X86_IO_APIC
930 This option enables a workaround that fixes a source of
931 spurious interrupts. This is recommended when threaded
932 interrupt handling is used on systems where the generation of
933 superfluous "boot interrupts" cannot be disabled.
935 Some chipsets generate a legacy INTx "boot IRQ" when the IRQ
936 entry in the chipset's IO-APIC is masked (as, e.g. the RT
937 kernel does during interrupt handling). On chipsets where this
938 boot IRQ generation cannot be disabled, this workaround keeps
939 the original IRQ line masked so that only the equivalent "boot
940 IRQ" is delivered to the CPUs. The workaround also tells the
941 kernel to set up the IRQ handler on the boot IRQ line. In this
942 way only one interrupt is delivered to the kernel. Otherwise
943 the spurious second interrupt may cause the kernel to bring
944 down (vital) interrupt lines.
946 Only affects "broken" chipsets. Interrupt sharing may be
947 increased on these systems.
950 bool "Machine Check / overheating reporting"
953 Machine Check support allows the processor to notify the
954 kernel if it detects a problem (e.g. overheating, data corruption).
955 The action the kernel takes depends on the severity of the problem,
956 ranging from warning messages to halting the machine.
960 prompt "Intel MCE features"
961 depends on X86_MCE && X86_LOCAL_APIC
963 Additional support for intel specific MCE features such as
968 prompt "AMD MCE features"
969 depends on X86_MCE && X86_LOCAL_APIC
971 Additional support for AMD specific MCE features such as
972 the DRAM Error Threshold.
974 config X86_ANCIENT_MCE
975 bool "Support for old Pentium 5 / WinChip machine checks"
976 depends on X86_32 && X86_MCE
978 Include support for machine check handling on old Pentium 5 or WinChip
979 systems. These typically need to be enabled explicitly on the command
982 config X86_MCE_THRESHOLD
983 depends on X86_MCE_AMD || X86_MCE_INTEL
986 config X86_MCE_INJECT
988 tristate "Machine check injector support"
990 Provide support for injecting machine checks for testing purposes.
991 If you don't know what a machine check is and you don't do kernel
992 QA it is safe to say n.
994 config X86_THERMAL_VECTOR
996 depends on X86_MCE_INTEL
999 bool "Enable VM86 support" if EXPERT
1003 This option is required by programs like DOSEMU to run
1004 16-bit real mode legacy code on x86 processors. It also may
1005 be needed by software like XFree86 to initialize some video
1006 cards via BIOS. Disabling this option saves about 6K.
1009 bool "Enable support for 16-bit segments" if EXPERT
1012 This option is required by programs like Wine to run 16-bit
1013 protected mode legacy code on x86 processors. Disabling
1014 this option saves about 300 bytes on i386, or around 6K text
1015 plus 16K runtime memory on x86-64,
1019 depends on X86_16BIT && X86_32
1023 depends on X86_16BIT && X86_64
1025 config X86_VSYSCALL_EMULATION
1026 bool "Enable vsyscall emulation" if EXPERT
1030 This enables emulation of the legacy vsyscall page. Disabling
1031 it is roughly equivalent to booting with vsyscall=none, except
1032 that it will also disable the helpful warning if a program
1033 tries to use a vsyscall. With this option set to N, offending
1034 programs will just segfault, citing addresses of the form
1037 This option is required by many programs built before 2013, and
1038 care should be used even with newer programs if set to N.
1040 Disabling this option saves about 7K of kernel size and
1041 possibly 4K of additional runtime pagetable memory.
1044 tristate "Toshiba Laptop support"
1047 This adds a driver to safely access the System Management Mode of
1048 the CPU on Toshiba portables with a genuine Toshiba BIOS. It does
1049 not work on models with a Phoenix BIOS. The System Management Mode
1050 is used to set the BIOS and power saving options on Toshiba portables.
1052 For information on utilities to make use of this driver see the
1053 Toshiba Linux utilities web site at:
1054 <http://www.buzzard.org.uk/toshiba/>.
1056 Say Y if you intend to run this kernel on a Toshiba portable.
1060 tristate "Dell laptop support"
1063 This adds a driver to safely access the System Management Mode
1064 of the CPU on the Dell Inspiron 8000. The System Management Mode
1065 is used to read cpu temperature and cooling fan status and to
1066 control the fans on the I8K portables.
1068 This driver has been tested only on the Inspiron 8000 but it may
1069 also work with other Dell laptops. You can force loading on other
1070 models by passing the parameter `force=1' to the module. Use at
1073 For information on utilities to make use of this driver see the
1074 I8K Linux utilities web site at:
1075 <http://people.debian.org/~dz/i8k/>
1077 Say Y if you intend to run this kernel on a Dell Inspiron 8000.
1080 config X86_REBOOTFIXUPS
1081 bool "Enable X86 board specific fixups for reboot"
1084 This enables chipset and/or board specific fixups to be done
1085 in order to get reboot to work correctly. This is only needed on
1086 some combinations of hardware and BIOS. The symptom, for which
1087 this config is intended, is when reboot ends with a stalled/hung
1090 Currently, the only fixup is for the Geode machines using
1091 CS5530A and CS5536 chipsets and the RDC R-321x SoC.
1093 Say Y if you want to enable the fixup. Currently, it's safe to
1094 enable this option even if you don't need it.
1098 tristate "CPU microcode loading support"
1099 depends on CPU_SUP_AMD || CPU_SUP_INTEL
1103 If you say Y here, you will be able to update the microcode on
1104 certain Intel and AMD processors. The Intel support is for the
1105 IA32 family, e.g. Pentium Pro, Pentium II, Pentium III, Pentium 4,
1106 Xeon etc. The AMD support is for families 0x10 and later. You will
1107 obviously need the actual microcode binary data itself which is not
1108 shipped with the Linux kernel.
1110 This option selects the general module only, you need to select
1111 at least one vendor specific module as well.
1113 To compile this driver as a module, choose M here: the module
1114 will be called microcode.
1116 config MICROCODE_INTEL
1117 bool "Intel microcode loading support"
1118 depends on MICROCODE
1122 This options enables microcode patch loading support for Intel
1125 For the current Intel microcode data package go to
1126 <https://downloadcenter.intel.com> and search for
1127 'Linux Processor Microcode Data File'.
1129 config MICROCODE_AMD
1130 bool "AMD microcode loading support"
1131 depends on MICROCODE
1134 If you select this option, microcode patch loading support for AMD
1135 processors will be enabled.
1137 config MICROCODE_OLD_INTERFACE
1139 depends on MICROCODE
1141 config MICROCODE_INTEL_EARLY
1144 config MICROCODE_AMD_EARLY
1147 config MICROCODE_EARLY
1148 bool "Early load microcode"
1149 depends on MICROCODE=y && BLK_DEV_INITRD
1150 select MICROCODE_INTEL_EARLY if MICROCODE_INTEL
1151 select MICROCODE_AMD_EARLY if MICROCODE_AMD
1154 This option provides functionality to read additional microcode data
1155 at the beginning of initrd image. The data tells kernel to load
1156 microcode to CPU's as early as possible. No functional change if no
1157 microcode data is glued to the initrd, therefore it's safe to say Y.
1160 tristate "/dev/cpu/*/msr - Model-specific register support"
1162 This device gives privileged processes access to the x86
1163 Model-Specific Registers (MSRs). It is a character device with
1164 major 202 and minors 0 to 31 for /dev/cpu/0/msr to /dev/cpu/31/msr.
1165 MSR accesses are directed to a specific CPU on multi-processor
1169 tristate "/dev/cpu/*/cpuid - CPU information support"
1171 This device gives processes access to the x86 CPUID instruction to
1172 be executed on a specific processor. It is a character device
1173 with major 203 and minors 0 to 31 for /dev/cpu/0/cpuid to
1177 prompt "High Memory Support"
1184 Linux can use up to 64 Gigabytes of physical memory on x86 systems.
1185 However, the address space of 32-bit x86 processors is only 4
1186 Gigabytes large. That means that, if you have a large amount of
1187 physical memory, not all of it can be "permanently mapped" by the
1188 kernel. The physical memory that's not permanently mapped is called
1191 If you are compiling a kernel which will never run on a machine with
1192 more than 1 Gigabyte total physical RAM, answer "off" here (default
1193 choice and suitable for most users). This will result in a "3GB/1GB"
1194 split: 3GB are mapped so that each process sees a 3GB virtual memory
1195 space and the remaining part of the 4GB virtual memory space is used
1196 by the kernel to permanently map as much physical memory as
1199 If the machine has between 1 and 4 Gigabytes physical RAM, then
1202 If more than 4 Gigabytes is used then answer "64GB" here. This
1203 selection turns Intel PAE (Physical Address Extension) mode on.
1204 PAE implements 3-level paging on IA32 processors. PAE is fully
1205 supported by Linux, PAE mode is implemented on all recent Intel
1206 processors (Pentium Pro and better). NOTE: If you say "64GB" here,
1207 then the kernel will not boot on CPUs that don't support PAE!
1209 The actual amount of total physical memory will either be
1210 auto detected or can be forced by using a kernel command line option
1211 such as "mem=256M". (Try "man bootparam" or see the documentation of
1212 your boot loader (lilo or loadlin) about how to pass options to the
1213 kernel at boot time.)
1215 If unsure, say "off".
1220 Select this if you have a 32-bit processor and between 1 and 4
1221 gigabytes of physical RAM.
1228 Select this if you have a 32-bit processor and more than 4
1229 gigabytes of physical RAM.
1234 prompt "Memory split" if EXPERT
1238 Select the desired split between kernel and user memory.
1240 If the address range available to the kernel is less than the
1241 physical memory installed, the remaining memory will be available
1242 as "high memory". Accessing high memory is a little more costly
1243 than low memory, as it needs to be mapped into the kernel first.
1244 Note that increasing the kernel address space limits the range
1245 available to user programs, making the address space there
1246 tighter. Selecting anything other than the default 3G/1G split
1247 will also likely make your kernel incompatible with binary-only
1250 If you are not absolutely sure what you are doing, leave this
1254 bool "3G/1G user/kernel split"
1255 config VMSPLIT_3G_OPT
1257 bool "3G/1G user/kernel split (for full 1G low memory)"
1259 bool "2G/2G user/kernel split"
1260 config VMSPLIT_2G_OPT
1262 bool "2G/2G user/kernel split (for full 2G low memory)"
1264 bool "1G/3G user/kernel split"
1269 default 0xB0000000 if VMSPLIT_3G_OPT
1270 default 0x80000000 if VMSPLIT_2G
1271 default 0x78000000 if VMSPLIT_2G_OPT
1272 default 0x40000000 if VMSPLIT_1G
1278 depends on X86_32 && (HIGHMEM64G || HIGHMEM4G)
1281 bool "PAE (Physical Address Extension) Support"
1282 depends on X86_32 && !HIGHMEM4G
1284 PAE is required for NX support, and furthermore enables
1285 larger swapspace support for non-overcommit purposes. It
1286 has the cost of more pagetable lookup overhead, and also
1287 consumes more pagetable space per process.
1289 config ARCH_PHYS_ADDR_T_64BIT
1291 depends on X86_64 || X86_PAE
1293 config ARCH_DMA_ADDR_T_64BIT
1295 depends on X86_64 || HIGHMEM64G
1297 config X86_DIRECT_GBPAGES
1299 depends on X86_64 && !DEBUG_PAGEALLOC && !KMEMCHECK
1301 Certain kernel features effectively disable kernel
1302 linear 1 GB mappings (even if the CPU otherwise
1303 supports them), so don't confuse the user by printing
1304 that we have them enabled.
1306 # Common NUMA Features
1308 bool "Numa Memory Allocation and Scheduler Support"
1310 depends on X86_64 || (X86_32 && HIGHMEM64G && X86_BIGSMP)
1311 default y if X86_BIGSMP
1313 Enable NUMA (Non Uniform Memory Access) support.
1315 The kernel will try to allocate memory used by a CPU on the
1316 local memory controller of the CPU and add some more
1317 NUMA awareness to the kernel.
1319 For 64-bit this is recommended if the system is Intel Core i7
1320 (or later), AMD Opteron, or EM64T NUMA.
1322 For 32-bit this is only needed if you boot a 32-bit
1323 kernel on a 64-bit NUMA platform.
1325 Otherwise, you should say N.
1329 prompt "Old style AMD Opteron NUMA detection"
1330 depends on X86_64 && NUMA && PCI
1332 Enable AMD NUMA node topology detection. You should say Y here if
1333 you have a multi processor AMD system. This uses an old method to
1334 read the NUMA configuration directly from the builtin Northbridge
1335 of Opteron. It is recommended to use X86_64_ACPI_NUMA instead,
1336 which also takes priority if both are compiled in.
1338 config X86_64_ACPI_NUMA
1340 prompt "ACPI NUMA detection"
1341 depends on X86_64 && NUMA && ACPI && PCI
1344 Enable ACPI SRAT based node topology detection.
1346 # Some NUMA nodes have memory ranges that span
1347 # other nodes. Even though a pfn is valid and
1348 # between a node's start and end pfns, it may not
1349 # reside on that node. See memmap_init_zone()
1351 config NODES_SPAN_OTHER_NODES
1353 depends on X86_64_ACPI_NUMA
1356 bool "NUMA emulation"
1359 Enable NUMA emulation. A flat machine will be split
1360 into virtual nodes when booted with "numa=fake=N", where N is the
1361 number of nodes. This is only useful for debugging.
1364 int "Maximum NUMA Nodes (as a power of 2)" if !MAXSMP
1366 default "10" if MAXSMP
1367 default "6" if X86_64
1369 depends on NEED_MULTIPLE_NODES
1371 Specify the maximum number of NUMA Nodes available on the target
1372 system. Increases memory reserved to accommodate various tables.
1374 config ARCH_HAVE_MEMORY_PRESENT
1376 depends on X86_32 && DISCONTIGMEM
1378 config NEED_NODE_MEMMAP_SIZE
1380 depends on X86_32 && (DISCONTIGMEM || SPARSEMEM)
1382 config ARCH_FLATMEM_ENABLE
1384 depends on X86_32 && !NUMA
1386 config ARCH_DISCONTIGMEM_ENABLE
1388 depends on NUMA && X86_32
1390 config ARCH_DISCONTIGMEM_DEFAULT
1392 depends on NUMA && X86_32
1394 config ARCH_SPARSEMEM_ENABLE
1396 depends on X86_64 || NUMA || X86_32 || X86_32_NON_STANDARD
1397 select SPARSEMEM_STATIC if X86_32
1398 select SPARSEMEM_VMEMMAP_ENABLE if X86_64
1400 config ARCH_SPARSEMEM_DEFAULT
1404 config ARCH_SELECT_MEMORY_MODEL
1406 depends on ARCH_SPARSEMEM_ENABLE
1408 config ARCH_MEMORY_PROBE
1409 bool "Enable sysfs memory/probe interface"
1410 depends on X86_64 && MEMORY_HOTPLUG
1412 This option enables a sysfs memory/probe interface for testing.
1413 See Documentation/memory-hotplug.txt for more information.
1414 If you are unsure how to answer this question, answer N.
1416 config ARCH_PROC_KCORE_TEXT
1418 depends on X86_64 && PROC_KCORE
1420 config ILLEGAL_POINTER_VALUE
1423 default 0xdead000000000000 if X86_64
1427 config X86_PMEM_LEGACY
1428 bool "Support non-standard NVDIMMs and ADR protected memory"
1430 Treat memory marked using the non-standard e820 type of 12 as used
1431 by the Intel Sandy Bridge-EP reference BIOS as protected memory.
1432 The kernel will offer these regions to the 'pmem' driver so
1433 they can be used for persistent storage.
1438 bool "Allocate 3rd-level pagetables from highmem"
1441 The VM uses one page table entry for each page of physical memory.
1442 For systems with a lot of RAM, this can be wasteful of precious
1443 low memory. Setting this option will put user-space page table
1444 entries in high memory.
1446 config X86_CHECK_BIOS_CORRUPTION
1447 bool "Check for low memory corruption"
1449 Periodically check for memory corruption in low memory, which
1450 is suspected to be caused by BIOS. Even when enabled in the
1451 configuration, it is disabled at runtime. Enable it by
1452 setting "memory_corruption_check=1" on the kernel command
1453 line. By default it scans the low 64k of memory every 60
1454 seconds; see the memory_corruption_check_size and
1455 memory_corruption_check_period parameters in
1456 Documentation/kernel-parameters.txt to adjust this.
1458 When enabled with the default parameters, this option has
1459 almost no overhead, as it reserves a relatively small amount
1460 of memory and scans it infrequently. It both detects corruption
1461 and prevents it from affecting the running system.
1463 It is, however, intended as a diagnostic tool; if repeatable
1464 BIOS-originated corruption always affects the same memory,
1465 you can use memmap= to prevent the kernel from using that
1468 config X86_BOOTPARAM_MEMORY_CORRUPTION_CHECK
1469 bool "Set the default setting of memory_corruption_check"
1470 depends on X86_CHECK_BIOS_CORRUPTION
1473 Set whether the default state of memory_corruption_check is
1476 config X86_RESERVE_LOW
1477 int "Amount of low memory, in kilobytes, to reserve for the BIOS"
1481 Specify the amount of low memory to reserve for the BIOS.
1483 The first page contains BIOS data structures that the kernel
1484 must not use, so that page must always be reserved.
1486 By default we reserve the first 64K of physical RAM, as a
1487 number of BIOSes are known to corrupt that memory range
1488 during events such as suspend/resume or monitor cable
1489 insertion, so it must not be used by the kernel.
1491 You can set this to 4 if you are absolutely sure that you
1492 trust the BIOS to get all its memory reservations and usages
1493 right. If you know your BIOS have problems beyond the
1494 default 64K area, you can set this to 640 to avoid using the
1495 entire low memory range.
1497 If you have doubts about the BIOS (e.g. suspend/resume does
1498 not work or there's kernel crashes after certain hardware
1499 hotplug events) then you might want to enable
1500 X86_CHECK_BIOS_CORRUPTION=y to allow the kernel to check
1501 typical corruption patterns.
1503 Leave this to the default value of 64 if you are unsure.
1505 config MATH_EMULATION
1507 prompt "Math emulation" if X86_32
1509 Linux can emulate a math coprocessor (used for floating point
1510 operations) if you don't have one. 486DX and Pentium processors have
1511 a math coprocessor built in, 486SX and 386 do not, unless you added
1512 a 487DX or 387, respectively. (The messages during boot time can
1513 give you some hints here ["man dmesg"].) Everyone needs either a
1514 coprocessor or this emulation.
1516 If you don't have a math coprocessor, you need to say Y here; if you
1517 say Y here even though you have a coprocessor, the coprocessor will
1518 be used nevertheless. (This behavior can be changed with the kernel
1519 command line option "no387", which comes handy if your coprocessor
1520 is broken. Try "man bootparam" or see the documentation of your boot
1521 loader (lilo or loadlin) about how to pass options to the kernel at
1522 boot time.) This means that it is a good idea to say Y here if you
1523 intend to use this kernel on different machines.
1525 More information about the internals of the Linux math coprocessor
1526 emulation can be found in <file:arch/x86/math-emu/README>.
1528 If you are not sure, say Y; apart from resulting in a 66 KB bigger
1529 kernel, it won't hurt.
1533 prompt "MTRR (Memory Type Range Register) support" if EXPERT
1535 On Intel P6 family processors (Pentium Pro, Pentium II and later)
1536 the Memory Type Range Registers (MTRRs) may be used to control
1537 processor access to memory ranges. This is most useful if you have
1538 a video (VGA) card on a PCI or AGP bus. Enabling write-combining
1539 allows bus write transfers to be combined into a larger transfer
1540 before bursting over the PCI/AGP bus. This can increase performance
1541 of image write operations 2.5 times or more. Saying Y here creates a
1542 /proc/mtrr file which may be used to manipulate your processor's
1543 MTRRs. Typically the X server should use this.
1545 This code has a reasonably generic interface so that similar
1546 control registers on other processors can be easily supported
1549 The Cyrix 6x86, 6x86MX and M II processors have Address Range
1550 Registers (ARRs) which provide a similar functionality to MTRRs. For
1551 these, the ARRs are used to emulate the MTRRs.
1552 The AMD K6-2 (stepping 8 and above) and K6-3 processors have two
1553 MTRRs. The Centaur C6 (WinChip) has 8 MCRs, allowing
1554 write-combining. All of these processors are supported by this code
1555 and it makes sense to say Y here if you have one of them.
1557 Saying Y here also fixes a problem with buggy SMP BIOSes which only
1558 set the MTRRs for the boot CPU and not for the secondary CPUs. This
1559 can lead to all sorts of problems, so it's good to say Y here.
1561 You can safely say Y even if your machine doesn't have MTRRs, you'll
1562 just add about 9 KB to your kernel.
1564 See <file:Documentation/x86/mtrr.txt> for more information.
1566 config MTRR_SANITIZER
1568 prompt "MTRR cleanup support"
1571 Convert MTRR layout from continuous to discrete, so X drivers can
1572 add writeback entries.
1574 Can be disabled with disable_mtrr_cleanup on the kernel command line.
1575 The largest mtrr entry size for a continuous block can be set with
1580 config MTRR_SANITIZER_ENABLE_DEFAULT
1581 int "MTRR cleanup enable value (0-1)"
1584 depends on MTRR_SANITIZER
1586 Enable mtrr cleanup default value
1588 config MTRR_SANITIZER_SPARE_REG_NR_DEFAULT
1589 int "MTRR cleanup spare reg num (0-7)"
1592 depends on MTRR_SANITIZER
1594 mtrr cleanup spare entries default, it can be changed via
1595 mtrr_spare_reg_nr=N on the kernel command line.
1599 prompt "x86 PAT support" if EXPERT
1602 Use PAT attributes to setup page level cache control.
1604 PATs are the modern equivalents of MTRRs and are much more
1605 flexible than MTRRs.
1607 Say N here if you see bootup problems (boot crash, boot hang,
1608 spontaneous reboots) or a non-working video driver.
1612 config ARCH_USES_PG_UNCACHED
1618 prompt "x86 architectural random number generator" if EXPERT
1620 Enable the x86 architectural RDRAND instruction
1621 (Intel Bull Mountain technology) to generate random numbers.
1622 If supported, this is a high bandwidth, cryptographically
1623 secure hardware random number generator.
1627 prompt "Supervisor Mode Access Prevention" if EXPERT
1629 Supervisor Mode Access Prevention (SMAP) is a security
1630 feature in newer Intel processors. There is a small
1631 performance cost if this enabled and turned on; there is
1632 also a small increase in the kernel size if this is enabled.
1636 config X86_INTEL_MPX
1637 prompt "Intel MPX (Memory Protection Extensions)"
1639 depends on CPU_SUP_INTEL
1641 MPX provides hardware features that can be used in
1642 conjunction with compiler-instrumented code to check
1643 memory references. It is designed to detect buffer
1644 overflow or underflow bugs.
1646 This option enables running applications which are
1647 instrumented or otherwise use MPX. It does not use MPX
1648 itself inside the kernel or to protect the kernel
1649 against bad memory references.
1651 Enabling this option will make the kernel larger:
1652 ~8k of kernel text and 36 bytes of data on a 64-bit
1653 defconfig. It adds a long to the 'mm_struct' which
1654 will increase the kernel memory overhead of each
1655 process and adds some branches to paths used during
1656 exec() and munmap().
1658 For details, see Documentation/x86/intel_mpx.txt
1663 bool "EFI runtime service support"
1666 select EFI_RUNTIME_WRAPPERS
1668 This enables the kernel to use EFI runtime services that are
1669 available (such as the EFI variable services).
1671 This option is only useful on systems that have EFI firmware.
1672 In addition, you should use the latest ELILO loader available
1673 at <http://elilo.sourceforge.net> in order to take advantage
1674 of EFI runtime services. However, even with this option, the
1675 resultant kernel should continue to boot on existing non-EFI
1679 bool "EFI stub support"
1680 depends on EFI && !X86_USE_3DNOW
1683 This kernel feature allows a bzImage to be loaded directly
1684 by EFI firmware without the use of a bootloader.
1686 See Documentation/efi-stub.txt for more information.
1689 bool "EFI mixed-mode support"
1690 depends on EFI_STUB && X86_64
1692 Enabling this feature allows a 64-bit kernel to be booted
1693 on a 32-bit firmware, provided that your CPU supports 64-bit
1696 Note that it is not possible to boot a mixed-mode enabled
1697 kernel via the EFI boot stub - a bootloader that supports
1698 the EFI handover protocol must be used.
1704 prompt "Enable seccomp to safely compute untrusted bytecode"
1706 This kernel feature is useful for number crunching applications
1707 that may need to compute untrusted bytecode during their
1708 execution. By using pipes or other transports made available to
1709 the process as file descriptors supporting the read/write
1710 syscalls, it's possible to isolate those applications in
1711 their own address space using seccomp. Once seccomp is
1712 enabled via prctl(PR_SET_SECCOMP), it cannot be disabled
1713 and the task is only allowed to execute a few safe syscalls
1714 defined by each seccomp mode.
1716 If unsure, say Y. Only embedded should say N here.
1718 source kernel/Kconfig.hz
1721 bool "kexec system call"
1723 kexec is a system call that implements the ability to shutdown your
1724 current kernel, and to start another kernel. It is like a reboot
1725 but it is independent of the system firmware. And like a reboot
1726 you can start any kernel with it, not just Linux.
1728 The name comes from the similarity to the exec system call.
1730 It is an ongoing process to be certain the hardware in a machine
1731 is properly shutdown, so do not be surprised if this code does not
1732 initially work for you. As of this writing the exact hardware
1733 interface is strongly in flux, so no good recommendation can be
1737 bool "kexec file based system call"
1742 depends on CRYPTO_SHA256=y
1744 This is new version of kexec system call. This system call is
1745 file based and takes file descriptors as system call argument
1746 for kernel and initramfs as opposed to list of segments as
1747 accepted by previous system call.
1749 config KEXEC_VERIFY_SIG
1750 bool "Verify kernel signature during kexec_file_load() syscall"
1751 depends on KEXEC_FILE
1753 This option makes kernel signature verification mandatory for
1754 the kexec_file_load() syscall.
1756 In addition to that option, you need to enable signature
1757 verification for the corresponding kernel image type being
1758 loaded in order for this to work.
1760 config KEXEC_BZIMAGE_VERIFY_SIG
1761 bool "Enable bzImage signature verification support"
1762 depends on KEXEC_VERIFY_SIG
1763 depends on SIGNED_PE_FILE_VERIFICATION
1764 select SYSTEM_TRUSTED_KEYRING
1766 Enable bzImage signature verification support.
1769 bool "kernel crash dumps"
1770 depends on X86_64 || (X86_32 && HIGHMEM)
1772 Generate crash dump after being started by kexec.
1773 This should be normally only set in special crash dump kernels
1774 which are loaded in the main kernel with kexec-tools into
1775 a specially reserved region and then later executed after
1776 a crash by kdump/kexec. The crash dump kernel must be compiled
1777 to a memory address not used by the main kernel or BIOS using
1778 PHYSICAL_START, or it must be built as a relocatable image
1779 (CONFIG_RELOCATABLE=y).
1780 For more details see Documentation/kdump/kdump.txt
1784 depends on KEXEC && HIBERNATION
1786 Jump between original kernel and kexeced kernel and invoke
1787 code in physical address mode via KEXEC
1789 config PHYSICAL_START
1790 hex "Physical address where the kernel is loaded" if (EXPERT || CRASH_DUMP)
1793 This gives the physical address where the kernel is loaded.
1795 If kernel is a not relocatable (CONFIG_RELOCATABLE=n) then
1796 bzImage will decompress itself to above physical address and
1797 run from there. Otherwise, bzImage will run from the address where
1798 it has been loaded by the boot loader and will ignore above physical
1801 In normal kdump cases one does not have to set/change this option
1802 as now bzImage can be compiled as a completely relocatable image
1803 (CONFIG_RELOCATABLE=y) and be used to load and run from a different
1804 address. This option is mainly useful for the folks who don't want
1805 to use a bzImage for capturing the crash dump and want to use a
1806 vmlinux instead. vmlinux is not relocatable hence a kernel needs
1807 to be specifically compiled to run from a specific memory area
1808 (normally a reserved region) and this option comes handy.
1810 So if you are using bzImage for capturing the crash dump,
1811 leave the value here unchanged to 0x1000000 and set
1812 CONFIG_RELOCATABLE=y. Otherwise if you plan to use vmlinux
1813 for capturing the crash dump change this value to start of
1814 the reserved region. In other words, it can be set based on
1815 the "X" value as specified in the "crashkernel=YM@XM"
1816 command line boot parameter passed to the panic-ed
1817 kernel. Please take a look at Documentation/kdump/kdump.txt
1818 for more details about crash dumps.
1820 Usage of bzImage for capturing the crash dump is recommended as
1821 one does not have to build two kernels. Same kernel can be used
1822 as production kernel and capture kernel. Above option should have
1823 gone away after relocatable bzImage support is introduced. But it
1824 is present because there are users out there who continue to use
1825 vmlinux for dump capture. This option should go away down the
1828 Don't change this unless you know what you are doing.
1831 bool "Build a relocatable kernel"
1834 This builds a kernel image that retains relocation information
1835 so it can be loaded someplace besides the default 1MB.
1836 The relocations tend to make the kernel binary about 10% larger,
1837 but are discarded at runtime.
1839 One use is for the kexec on panic case where the recovery kernel
1840 must live at a different physical address than the primary
1843 Note: If CONFIG_RELOCATABLE=y, then the kernel runs from the address
1844 it has been loaded at and the compile time physical address
1845 (CONFIG_PHYSICAL_START) is used as the minimum location.
1847 config RANDOMIZE_BASE
1848 bool "Randomize the address of the kernel image"
1849 depends on RELOCATABLE
1852 Randomizes the physical and virtual address at which the
1853 kernel image is decompressed, as a security feature that
1854 deters exploit attempts relying on knowledge of the location
1855 of kernel internals.
1857 Entropy is generated using the RDRAND instruction if it is
1858 supported. If RDTSC is supported, it is used as well. If
1859 neither RDRAND nor RDTSC are supported, then randomness is
1860 read from the i8254 timer.
1862 The kernel will be offset by up to RANDOMIZE_BASE_MAX_OFFSET,
1863 and aligned according to PHYSICAL_ALIGN. Since the kernel is
1864 built using 2GiB addressing, and PHYSICAL_ALGIN must be at a
1865 minimum of 2MiB, only 10 bits of entropy is theoretically
1866 possible. At best, due to page table layouts, 64-bit can use
1867 9 bits of entropy and 32-bit uses 8 bits.
1871 config RANDOMIZE_BASE_MAX_OFFSET
1872 hex "Maximum kASLR offset allowed" if EXPERT
1873 depends on RANDOMIZE_BASE
1874 range 0x0 0x20000000 if X86_32
1875 default "0x20000000" if X86_32
1876 range 0x0 0x40000000 if X86_64
1877 default "0x40000000" if X86_64
1879 The lesser of RANDOMIZE_BASE_MAX_OFFSET and available physical
1880 memory is used to determine the maximal offset in bytes that will
1881 be applied to the kernel when kernel Address Space Layout
1882 Randomization (kASLR) is active. This must be a multiple of
1885 On 32-bit this is limited to 512MiB by page table layouts. The
1888 On 64-bit this is limited by how the kernel fixmap page table is
1889 positioned, so this cannot be larger than 1GiB currently. Without
1890 RANDOMIZE_BASE, there is a 512MiB to 1.5GiB split between kernel
1891 and modules. When RANDOMIZE_BASE_MAX_OFFSET is above 512MiB, the
1892 modules area will shrink to compensate, up to the current maximum
1893 1GiB to 1GiB split. The default is 1GiB.
1895 If unsure, leave at the default value.
1897 # Relocation on x86 needs some additional build support
1898 config X86_NEED_RELOCS
1900 depends on RANDOMIZE_BASE || (X86_32 && RELOCATABLE)
1902 config PHYSICAL_ALIGN
1903 hex "Alignment value to which kernel should be aligned"
1905 range 0x2000 0x1000000 if X86_32
1906 range 0x200000 0x1000000 if X86_64
1908 This value puts the alignment restrictions on physical address
1909 where kernel is loaded and run from. Kernel is compiled for an
1910 address which meets above alignment restriction.
1912 If bootloader loads the kernel at a non-aligned address and
1913 CONFIG_RELOCATABLE is set, kernel will move itself to nearest
1914 address aligned to above value and run from there.
1916 If bootloader loads the kernel at a non-aligned address and
1917 CONFIG_RELOCATABLE is not set, kernel will ignore the run time
1918 load address and decompress itself to the address it has been
1919 compiled for and run from there. The address for which kernel is
1920 compiled already meets above alignment restrictions. Hence the
1921 end result is that kernel runs from a physical address meeting
1922 above alignment restrictions.
1924 On 32-bit this value must be a multiple of 0x2000. On 64-bit
1925 this value must be a multiple of 0x200000.
1927 Don't change this unless you know what you are doing.
1930 bool "Support for hot-pluggable CPUs"
1933 Say Y here to allow turning CPUs off and on. CPUs can be
1934 controlled through /sys/devices/system/cpu.
1935 ( Note: power management support will enable this option
1936 automatically on SMP systems. )
1937 Say N if you want to disable CPU hotplug.
1939 config BOOTPARAM_HOTPLUG_CPU0
1940 bool "Set default setting of cpu0_hotpluggable"
1942 depends on HOTPLUG_CPU
1944 Set whether default state of cpu0_hotpluggable is on or off.
1946 Say Y here to enable CPU0 hotplug by default. If this switch
1947 is turned on, there is no need to give cpu0_hotplug kernel
1948 parameter and the CPU0 hotplug feature is enabled by default.
1950 Please note: there are two known CPU0 dependencies if you want
1951 to enable the CPU0 hotplug feature either by this switch or by
1952 cpu0_hotplug kernel parameter.
1954 First, resume from hibernate or suspend always starts from CPU0.
1955 So hibernate and suspend are prevented if CPU0 is offline.
1957 Second dependency is PIC interrupts always go to CPU0. CPU0 can not
1958 offline if any interrupt can not migrate out of CPU0. There may
1959 be other CPU0 dependencies.
1961 Please make sure the dependencies are under your control before
1962 you enable this feature.
1964 Say N if you don't want to enable CPU0 hotplug feature by default.
1965 You still can enable the CPU0 hotplug feature at boot by kernel
1966 parameter cpu0_hotplug.
1968 config DEBUG_HOTPLUG_CPU0
1970 prompt "Debug CPU0 hotplug"
1971 depends on HOTPLUG_CPU
1973 Enabling this option offlines CPU0 (if CPU0 can be offlined) as
1974 soon as possible and boots up userspace with CPU0 offlined. User
1975 can online CPU0 back after boot time.
1977 To debug CPU0 hotplug, you need to enable CPU0 offline/online
1978 feature by either turning on CONFIG_BOOTPARAM_HOTPLUG_CPU0 during
1979 compilation or giving cpu0_hotplug kernel parameter at boot.
1985 prompt "Disable the 32-bit vDSO (needed for glibc 2.3.3)"
1986 depends on X86_32 || IA32_EMULATION
1988 Certain buggy versions of glibc will crash if they are
1989 presented with a 32-bit vDSO that is not mapped at the address
1990 indicated in its segment table.
1992 The bug was introduced by f866314b89d56845f55e6f365e18b31ec978ec3a
1993 and fixed by 3b3ddb4f7db98ec9e912ccdf54d35df4aa30e04a and
1994 49ad572a70b8aeb91e57483a11dd1b77e31c4468. Glibc 2.3.3 is
1995 the only released version with the bug, but OpenSUSE 9
1996 contains a buggy "glibc 2.3.2".
1998 The symptom of the bug is that everything crashes on startup, saying:
1999 dl_main: Assertion `(void *) ph->p_vaddr == _rtld_local._dl_sysinfo_dso' failed!
2001 Saying Y here changes the default value of the vdso32 boot
2002 option from 1 to 0, which turns off the 32-bit vDSO entirely.
2003 This works around the glibc bug but hurts performance.
2005 If unsure, say N: if you are compiling your own kernel, you
2006 are unlikely to be using a buggy version of glibc.
2009 bool "Built-in kernel command line"
2011 Allow for specifying boot arguments to the kernel at
2012 build time. On some systems (e.g. embedded ones), it is
2013 necessary or convenient to provide some or all of the
2014 kernel boot arguments with the kernel itself (that is,
2015 to not rely on the boot loader to provide them.)
2017 To compile command line arguments into the kernel,
2018 set this option to 'Y', then fill in the
2019 the boot arguments in CONFIG_CMDLINE.
2021 Systems with fully functional boot loaders (i.e. non-embedded)
2022 should leave this option set to 'N'.
2025 string "Built-in kernel command string"
2026 depends on CMDLINE_BOOL
2029 Enter arguments here that should be compiled into the kernel
2030 image and used at boot time. If the boot loader provides a
2031 command line at boot time, it is appended to this string to
2032 form the full kernel command line, when the system boots.
2034 However, you can use the CONFIG_CMDLINE_OVERRIDE option to
2035 change this behavior.
2037 In most cases, the command line (whether built-in or provided
2038 by the boot loader) should specify the device for the root
2041 config CMDLINE_OVERRIDE
2042 bool "Built-in command line overrides boot loader arguments"
2043 depends on CMDLINE_BOOL
2045 Set this option to 'Y' to have the kernel ignore the boot loader
2046 command line, and use ONLY the built-in command line.
2048 This is used to work around broken boot loaders. This should
2049 be set to 'N' under normal conditions.
2051 source "kernel/livepatch/Kconfig"
2055 config ARCH_ENABLE_MEMORY_HOTPLUG
2057 depends on X86_64 || (X86_32 && HIGHMEM)
2059 config ARCH_ENABLE_MEMORY_HOTREMOVE
2061 depends on MEMORY_HOTPLUG
2063 config USE_PERCPU_NUMA_NODE_ID
2067 config ARCH_ENABLE_SPLIT_PMD_PTLOCK
2069 depends on X86_64 || X86_PAE
2071 config ARCH_ENABLE_HUGEPAGE_MIGRATION
2073 depends on X86_64 && HUGETLB_PAGE && MIGRATION
2075 menu "Power management and ACPI options"
2077 config ARCH_HIBERNATION_HEADER
2079 depends on X86_64 && HIBERNATION
2081 source "kernel/power/Kconfig"
2083 source "drivers/acpi/Kconfig"
2085 source "drivers/sfi/Kconfig"
2092 tristate "APM (Advanced Power Management) BIOS support"
2093 depends on X86_32 && PM_SLEEP
2095 APM is a BIOS specification for saving power using several different
2096 techniques. This is mostly useful for battery powered laptops with
2097 APM compliant BIOSes. If you say Y here, the system time will be
2098 reset after a RESUME operation, the /proc/apm device will provide
2099 battery status information, and user-space programs will receive
2100 notification of APM "events" (e.g. battery status change).
2102 If you select "Y" here, you can disable actual use of the APM
2103 BIOS by passing the "apm=off" option to the kernel at boot time.
2105 Note that the APM support is almost completely disabled for
2106 machines with more than one CPU.
2108 In order to use APM, you will need supporting software. For location
2109 and more information, read <file:Documentation/power/apm-acpi.txt>
2110 and the Battery Powered Linux mini-HOWTO, available from
2111 <http://www.tldp.org/docs.html#howto>.
2113 This driver does not spin down disk drives (see the hdparm(8)
2114 manpage ("man 8 hdparm") for that), and it doesn't turn off
2115 VESA-compliant "green" monitors.
2117 This driver does not support the TI 4000M TravelMate and the ACER
2118 486/DX4/75 because they don't have compliant BIOSes. Many "green"
2119 desktop machines also don't have compliant BIOSes, and this driver
2120 may cause those machines to panic during the boot phase.
2122 Generally, if you don't have a battery in your machine, there isn't
2123 much point in using this driver and you should say N. If you get
2124 random kernel OOPSes or reboots that don't seem to be related to
2125 anything, try disabling/enabling this option (or disabling/enabling
2128 Some other things you should try when experiencing seemingly random,
2131 1) make sure that you have enough swap space and that it is
2133 2) pass the "no-hlt" option to the kernel
2134 3) switch on floating point emulation in the kernel and pass
2135 the "no387" option to the kernel
2136 4) pass the "floppy=nodma" option to the kernel
2137 5) pass the "mem=4M" option to the kernel (thereby disabling
2138 all but the first 4 MB of RAM)
2139 6) make sure that the CPU is not over clocked.
2140 7) read the sig11 FAQ at <http://www.bitwizard.nl/sig11/>
2141 8) disable the cache from your BIOS settings
2142 9) install a fan for the video card or exchange video RAM
2143 10) install a better fan for the CPU
2144 11) exchange RAM chips
2145 12) exchange the motherboard.
2147 To compile this driver as a module, choose M here: the
2148 module will be called apm.
2152 config APM_IGNORE_USER_SUSPEND
2153 bool "Ignore USER SUSPEND"
2155 This option will ignore USER SUSPEND requests. On machines with a
2156 compliant APM BIOS, you want to say N. However, on the NEC Versa M
2157 series notebooks, it is necessary to say Y because of a BIOS bug.
2159 config APM_DO_ENABLE
2160 bool "Enable PM at boot time"
2162 Enable APM features at boot time. From page 36 of the APM BIOS
2163 specification: "When disabled, the APM BIOS does not automatically
2164 power manage devices, enter the Standby State, enter the Suspend
2165 State, or take power saving steps in response to CPU Idle calls."
2166 This driver will make CPU Idle calls when Linux is idle (unless this
2167 feature is turned off -- see "Do CPU IDLE calls", below). This
2168 should always save battery power, but more complicated APM features
2169 will be dependent on your BIOS implementation. You may need to turn
2170 this option off if your computer hangs at boot time when using APM
2171 support, or if it beeps continuously instead of suspending. Turn
2172 this off if you have a NEC UltraLite Versa 33/C or a Toshiba
2173 T400CDT. This is off by default since most machines do fine without
2178 bool "Make CPU Idle calls when idle"
2180 Enable calls to APM CPU Idle/CPU Busy inside the kernel's idle loop.
2181 On some machines, this can activate improved power savings, such as
2182 a slowed CPU clock rate, when the machine is idle. These idle calls
2183 are made after the idle loop has run for some length of time (e.g.,
2184 333 mS). On some machines, this will cause a hang at boot time or
2185 whenever the CPU becomes idle. (On machines with more than one CPU,
2186 this option does nothing.)
2188 config APM_DISPLAY_BLANK
2189 bool "Enable console blanking using APM"
2191 Enable console blanking using the APM. Some laptops can use this to
2192 turn off the LCD backlight when the screen blanker of the Linux
2193 virtual console blanks the screen. Note that this is only used by
2194 the virtual console screen blanker, and won't turn off the backlight
2195 when using the X Window system. This also doesn't have anything to
2196 do with your VESA-compliant power-saving monitor. Further, this
2197 option doesn't work for all laptops -- it might not turn off your
2198 backlight at all, or it might print a lot of errors to the console,
2199 especially if you are using gpm.
2201 config APM_ALLOW_INTS
2202 bool "Allow interrupts during APM BIOS calls"
2204 Normally we disable external interrupts while we are making calls to
2205 the APM BIOS as a measure to lessen the effects of a badly behaving
2206 BIOS implementation. The BIOS should reenable interrupts if it
2207 needs to. Unfortunately, some BIOSes do not -- especially those in
2208 many of the newer IBM Thinkpads. If you experience hangs when you
2209 suspend, try setting this to Y. Otherwise, say N.
2213 source "drivers/cpufreq/Kconfig"
2215 source "drivers/cpuidle/Kconfig"
2217 source "drivers/idle/Kconfig"
2222 menu "Bus options (PCI etc.)"
2228 Find out whether you have a PCI motherboard. PCI is the name of a
2229 bus system, i.e. the way the CPU talks to the other stuff inside
2230 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
2231 VESA. If you have PCI, say Y, otherwise N.
2234 prompt "PCI access mode"
2235 depends on X86_32 && PCI
2238 On PCI systems, the BIOS can be used to detect the PCI devices and
2239 determine their configuration. However, some old PCI motherboards
2240 have BIOS bugs and may crash if this is done. Also, some embedded
2241 PCI-based systems don't have any BIOS at all. Linux can also try to
2242 detect the PCI hardware directly without using the BIOS.
2244 With this option, you can specify how Linux should detect the
2245 PCI devices. If you choose "BIOS", the BIOS will be used,
2246 if you choose "Direct", the BIOS won't be used, and if you
2247 choose "MMConfig", then PCI Express MMCONFIG will be used.
2248 If you choose "Any", the kernel will try MMCONFIG, then the
2249 direct access method and falls back to the BIOS if that doesn't
2250 work. If unsure, go with the default, which is "Any".
2255 config PCI_GOMMCONFIG
2272 depends on X86_32 && PCI && (PCI_GOBIOS || PCI_GOANY)
2274 # x86-64 doesn't support PCI BIOS access from long mode so always go direct.
2277 depends on PCI && (X86_64 || (PCI_GODIRECT || PCI_GOANY || PCI_GOOLPC || PCI_GOMMCONFIG))
2281 depends on X86_32 && PCI && (ACPI || SFI) && (PCI_GOMMCONFIG || PCI_GOANY)
2285 depends on PCI && OLPC && (PCI_GOOLPC || PCI_GOANY)
2289 depends on PCI && XEN
2297 bool "Support mmconfig PCI config space access"
2298 depends on X86_64 && PCI && ACPI
2300 config PCI_CNB20LE_QUIRK
2301 bool "Read CNB20LE Host Bridge Windows" if EXPERT
2304 Read the PCI windows out of the CNB20LE host bridge. This allows
2305 PCI hotplug to work on systems with the CNB20LE chipset which do
2308 There's no public spec for this chipset, and this functionality
2309 is known to be incomplete.
2311 You should say N unless you know you need this.
2313 source "drivers/pci/pcie/Kconfig"
2315 source "drivers/pci/Kconfig"
2317 # x86_64 have no ISA slots, but can have ISA-style DMA.
2319 bool "ISA-style DMA support" if (X86_64 && EXPERT)
2322 Enables ISA-style DMA support for devices requiring such controllers.
2330 Find out whether you have ISA slots on your motherboard. ISA is the
2331 name of a bus system, i.e. the way the CPU talks to the other stuff
2332 inside your box. Other bus systems are PCI, EISA, MicroChannel
2333 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
2334 newer boards don't support it. If you have ISA, say Y, otherwise N.
2340 The Extended Industry Standard Architecture (EISA) bus was
2341 developed as an open alternative to the IBM MicroChannel bus.
2343 The EISA bus provided some of the features of the IBM MicroChannel
2344 bus while maintaining backward compatibility with cards made for
2345 the older ISA bus. The EISA bus saw limited use between 1988 and
2346 1995 when it was made obsolete by the PCI bus.
2348 Say Y here if you are building a kernel for an EISA-based machine.
2352 source "drivers/eisa/Kconfig"
2355 tristate "NatSemi SCx200 support"
2357 This provides basic support for National Semiconductor's
2358 (now AMD's) Geode processors. The driver probes for the
2359 PCI-IDs of several on-chip devices, so its a good dependency
2360 for other scx200_* drivers.
2362 If compiled as a module, the driver is named scx200.
2364 config SCx200HR_TIMER
2365 tristate "NatSemi SCx200 27MHz High-Resolution Timer Support"
2369 This driver provides a clocksource built upon the on-chip
2370 27MHz high-resolution timer. Its also a workaround for
2371 NSC Geode SC-1100's buggy TSC, which loses time when the
2372 processor goes idle (as is done by the scheduler). The
2373 other workaround is idle=poll boot option.
2376 bool "One Laptop Per Child support"
2383 Add support for detecting the unique features of the OLPC
2387 bool "OLPC XO-1 Power Management"
2388 depends on OLPC && MFD_CS5535 && PM_SLEEP
2391 Add support for poweroff and suspend of the OLPC XO-1 laptop.
2394 bool "OLPC XO-1 Real Time Clock"
2395 depends on OLPC_XO1_PM && RTC_DRV_CMOS
2397 Add support for the XO-1 real time clock, which can be used as a
2398 programmable wakeup source.
2401 bool "OLPC XO-1 SCI extras"
2402 depends on OLPC && OLPC_XO1_PM
2408 Add support for SCI-based features of the OLPC XO-1 laptop:
2409 - EC-driven system wakeups
2413 - AC adapter status updates
2414 - Battery status updates
2416 config OLPC_XO15_SCI
2417 bool "OLPC XO-1.5 SCI extras"
2418 depends on OLPC && ACPI
2421 Add support for SCI-based features of the OLPC XO-1.5 laptop:
2422 - EC-driven system wakeups
2423 - AC adapter status updates
2424 - Battery status updates
2427 bool "PCEngines ALIX System Support (LED setup)"
2430 This option enables system support for the PCEngines ALIX.
2431 At present this just sets up LEDs for GPIO control on
2432 ALIX2/3/6 boards. However, other system specific setup should
2435 Note: You must still enable the drivers for GPIO and LED support
2436 (GPIO_CS5535 & LEDS_GPIO) to actually use the LEDs
2438 Note: You have to set alix.force=1 for boards with Award BIOS.
2441 bool "Soekris Engineering net5501 System Support (LEDS, GPIO, etc)"
2444 This option enables system support for the Soekris Engineering net5501.
2447 bool "Traverse Technologies GEOS System Support (LEDS, GPIO, etc)"
2451 This option enables system support for the Traverse Technologies GEOS.
2454 bool "Technologic Systems TS-5500 platform support"
2456 select CHECK_SIGNATURE
2460 This option enables system support for the Technologic Systems TS-5500.
2466 depends on CPU_SUP_AMD && PCI
2468 source "drivers/pcmcia/Kconfig"
2470 source "drivers/pci/hotplug/Kconfig"
2473 tristate "RapidIO support"
2477 If enabled this option will include drivers and the core
2478 infrastructure code to support RapidIO interconnect devices.
2480 source "drivers/rapidio/Kconfig"
2483 bool "Mark VGA/VBE/EFI FB as generic system framebuffer"
2485 Firmwares often provide initial graphics framebuffers so the BIOS,
2486 bootloader or kernel can show basic video-output during boot for
2487 user-guidance and debugging. Historically, x86 used the VESA BIOS
2488 Extensions and EFI-framebuffers for this, which are mostly limited
2490 This option, if enabled, marks VGA/VBE/EFI framebuffers as generic
2491 framebuffers so the new generic system-framebuffer drivers can be
2492 used on x86. If the framebuffer is not compatible with the generic
2493 modes, it is adverticed as fallback platform framebuffer so legacy
2494 drivers like efifb, vesafb and uvesafb can pick it up.
2495 If this option is not selected, all system framebuffers are always
2496 marked as fallback platform framebuffers as usual.
2498 Note: Legacy fbdev drivers, including vesafb, efifb, uvesafb, will
2499 not be able to pick up generic system framebuffers if this option
2500 is selected. You are highly encouraged to enable simplefb as
2501 replacement if you select this option. simplefb can correctly deal
2502 with generic system framebuffers. But you should still keep vesafb
2503 and others enabled as fallback if a system framebuffer is
2504 incompatible with simplefb.
2511 menu "Executable file formats / Emulations"
2513 source "fs/Kconfig.binfmt"
2515 config IA32_EMULATION
2516 bool "IA32 Emulation"
2519 select COMPAT_BINFMT_ELF
2522 Include code to run legacy 32-bit programs under a
2523 64-bit kernel. You should likely turn this on, unless you're
2524 100% sure that you don't have any 32-bit programs left.
2527 tristate "IA32 a.out support"
2528 depends on IA32_EMULATION
2530 Support old a.out binaries in the 32bit emulation.
2533 bool "x32 ABI for 64-bit mode"
2534 depends on X86_64 && IA32_EMULATION
2536 Include code to run binaries for the x32 native 32-bit ABI
2537 for 64-bit processors. An x32 process gets access to the
2538 full 64-bit register file and wide data path while leaving
2539 pointers at 32 bits for smaller memory footprint.
2541 You will need a recent binutils (2.22 or later) with
2542 elf32_x86_64 support enabled to compile a kernel with this
2547 depends on IA32_EMULATION || X86_X32
2548 select ARCH_WANT_OLD_COMPAT_IPC
2551 config COMPAT_FOR_U64_ALIGNMENT
2554 config SYSVIPC_COMPAT
2566 config HAVE_ATOMIC_IOMAP
2570 config X86_DEV_DMA_OPS
2572 depends on X86_64 || STA2X11
2574 config X86_DMA_REMAP
2582 source "net/Kconfig"
2584 source "drivers/Kconfig"
2586 source "drivers/firmware/Kconfig"
2590 source "arch/x86/Kconfig.debug"
2592 source "security/Kconfig"
2594 source "crypto/Kconfig"
2596 source "arch/x86/kvm/Kconfig"
2598 source "lib/Kconfig"