1 # SPDX-License-Identifier: GPL-2.0
4 bool "64-bit kernel" if "$(ARCH)" = "x86"
5 default "$(ARCH)" != "i386"
7 Say yes to build a 64-bit kernel - formerly known as x86_64
8 Say no to build a 32-bit kernel - formerly known as i386
13 # Options that are inherently 32-bit kernel only:
14 select ARCH_WANT_IPC_PARSE_VERSION
16 select CLONE_BACKWARDS
17 select GENERIC_VDSO_32
18 select HAVE_DEBUG_STACKOVERFLOW
20 select MODULES_USE_ELF_REL
22 select ARCH_SPLIT_ARG64
27 # Options that are inherently 64-bit kernel only:
28 select ARCH_HAS_GIGANTIC_PAGE
29 select ARCH_SUPPORTS_INT128 if CC_HAS_INT128
30 select ARCH_USE_CMPXCHG_LOCKREF
31 select HAVE_ARCH_SOFT_DIRTY
32 select MODULES_USE_ELF_RELA
33 select NEED_DMA_MAP_STATE
35 select ARCH_HAS_ELFCORE_COMPAT
38 config FORCE_DYNAMIC_FTRACE
41 depends on FUNCTION_TRACER
44 We keep the static function tracing (!DYNAMIC_FTRACE) around
45 in order to test the non static function tracing in the
46 generic code, as other architectures still use it. But we
47 only need to keep it around for x86_64. No need to keep it
48 for x86_32. For x86_32, force DYNAMIC_FTRACE.
52 # ( Note that options that are marked 'if X86_64' could in principle be
53 # ported to 32-bit as well. )
58 # Note: keep this list sorted alphabetically
60 select ACPI_LEGACY_TABLES_LOOKUP if ACPI
61 select ACPI_SYSTEM_POWER_STATES_SUPPORT if ACPI
62 select ARCH_32BIT_OFF_T if X86_32
63 select ARCH_CLOCKSOURCE_INIT
64 select ARCH_CORRECT_STACKTRACE_ON_KRETPROBE
65 select ARCH_ENABLE_HUGEPAGE_MIGRATION if X86_64 && HUGETLB_PAGE && MIGRATION
66 select ARCH_ENABLE_MEMORY_HOTPLUG if X86_64
67 select ARCH_ENABLE_MEMORY_HOTREMOVE if MEMORY_HOTPLUG
68 select ARCH_ENABLE_SPLIT_PMD_PTLOCK if (PGTABLE_LEVELS > 2) && (X86_64 || X86_PAE)
69 select ARCH_ENABLE_THP_MIGRATION if X86_64 && TRANSPARENT_HUGEPAGE
70 select ARCH_HAS_ACPI_TABLE_UPGRADE if ACPI
71 select ARCH_HAS_CACHE_LINE_SIZE
72 select ARCH_HAS_CURRENT_STACK_POINTER
73 select ARCH_HAS_DEBUG_VIRTUAL
74 select ARCH_HAS_DEBUG_VM_PGTABLE if !X86_PAE
75 select ARCH_HAS_DEVMEM_IS_ALLOWED
76 select ARCH_HAS_EARLY_DEBUG if KGDB
77 select ARCH_HAS_ELF_RANDOMIZE
78 select ARCH_HAS_FAST_MULTIPLIER
79 select ARCH_HAS_FILTER_PGPROT
80 select ARCH_HAS_FORTIFY_SOURCE
81 select ARCH_HAS_GCOV_PROFILE_ALL
82 select ARCH_HAS_KCOV if X86_64
83 select ARCH_HAS_MEM_ENCRYPT
84 select ARCH_HAS_MEMBARRIER_SYNC_CORE
85 select ARCH_HAS_NON_OVERLAPPING_ADDRESS_SPACE
86 select ARCH_HAS_PMEM_API if X86_64
87 select ARCH_HAS_PTE_DEVMAP if X86_64
88 select ARCH_HAS_PTE_SPECIAL
89 select ARCH_HAS_UACCESS_FLUSHCACHE if X86_64
90 select ARCH_HAS_COPY_MC if X86_64
91 select ARCH_HAS_SET_MEMORY
92 select ARCH_HAS_SET_DIRECT_MAP
93 select ARCH_HAS_STRICT_KERNEL_RWX
94 select ARCH_HAS_STRICT_MODULE_RWX
95 select ARCH_HAS_SYNC_CORE_BEFORE_USERMODE
96 select ARCH_HAS_SYSCALL_WRAPPER
97 select ARCH_HAS_UBSAN_SANITIZE_ALL
98 select ARCH_HAS_DEBUG_WX
99 select ARCH_HAS_ZONE_DMA_SET if EXPERT
100 select ARCH_HAVE_NMI_SAFE_CMPXCHG
101 select ARCH_MIGHT_HAVE_ACPI_PDC if ACPI
102 select ARCH_MIGHT_HAVE_PC_PARPORT
103 select ARCH_MIGHT_HAVE_PC_SERIO
104 select ARCH_STACKWALK
105 select ARCH_SUPPORTS_ACPI
106 select ARCH_SUPPORTS_ATOMIC_RMW
107 select ARCH_SUPPORTS_DEBUG_PAGEALLOC
108 select ARCH_SUPPORTS_PAGE_TABLE_CHECK if X86_64
109 select ARCH_SUPPORTS_NUMA_BALANCING if X86_64
110 select ARCH_SUPPORTS_KMAP_LOCAL_FORCE_MAP if NR_CPUS <= 4096
111 select ARCH_SUPPORTS_LTO_CLANG
112 select ARCH_SUPPORTS_LTO_CLANG_THIN
113 select ARCH_USE_BUILTIN_BSWAP
114 select ARCH_USE_MEMTEST
115 select ARCH_USE_QUEUED_RWLOCKS
116 select ARCH_USE_QUEUED_SPINLOCKS
117 select ARCH_USE_SYM_ANNOTATIONS
118 select ARCH_WANT_BATCHED_UNMAP_TLB_FLUSH
119 select ARCH_WANT_DEFAULT_BPF_JIT if X86_64
120 select ARCH_WANTS_DYNAMIC_TASK_STRUCT
121 select ARCH_WANTS_NO_INSTR
122 select ARCH_WANT_HUGE_PMD_SHARE
123 select ARCH_WANT_LD_ORPHAN_WARN
124 select ARCH_WANTS_RT_DELAYED_SIGNALS
125 select ARCH_WANTS_THP_SWAP if X86_64
126 select ARCH_HAS_PARANOID_L1D_FLUSH
127 select BUILDTIME_TABLE_SORT
129 select CLOCKSOURCE_VALIDATE_LAST_CYCLE
130 select CLOCKSOURCE_WATCHDOG
131 select DCACHE_WORD_ACCESS
132 select DYNAMIC_SIGFRAME
133 select EDAC_ATOMIC_SCRUB
135 select GENERIC_CLOCKEVENTS_BROADCAST if X86_64 || (X86_32 && X86_LOCAL_APIC)
136 select GENERIC_CLOCKEVENTS_MIN_ADJUST
137 select GENERIC_CMOS_UPDATE
138 select GENERIC_CPU_AUTOPROBE
139 select GENERIC_CPU_VULNERABILITIES
140 select GENERIC_EARLY_IOREMAP
143 select GENERIC_IRQ_EFFECTIVE_AFF_MASK if SMP
144 select GENERIC_IRQ_MATRIX_ALLOCATOR if X86_LOCAL_APIC
145 select GENERIC_IRQ_MIGRATION if SMP
146 select GENERIC_IRQ_PROBE
147 select GENERIC_IRQ_RESERVATION_MODE
148 select GENERIC_IRQ_SHOW
149 select GENERIC_PENDING_IRQ if SMP
150 select GENERIC_PTDUMP
151 select GENERIC_SMP_IDLE_THREAD
152 select GENERIC_TIME_VSYSCALL
153 select GENERIC_GETTIMEOFDAY
154 select GENERIC_VDSO_TIME_NS
155 select GUP_GET_PTE_LOW_HIGH if X86_PAE
156 select HARDIRQS_SW_RESEND
157 select HARDLOCKUP_CHECK_TIMESTAMP if X86_64
158 select HAVE_ACPI_APEI if ACPI
159 select HAVE_ACPI_APEI_NMI if ACPI
160 select HAVE_ALIGNED_STRUCT_PAGE if SLUB
161 select HAVE_ARCH_AUDITSYSCALL
162 select HAVE_ARCH_HUGE_VMAP if X86_64 || X86_PAE
163 select HAVE_ARCH_JUMP_LABEL
164 select HAVE_ARCH_JUMP_LABEL_RELATIVE
165 select HAVE_ARCH_KASAN if X86_64
166 select HAVE_ARCH_KASAN_VMALLOC if X86_64
167 select HAVE_ARCH_KFENCE
168 select HAVE_ARCH_KGDB
169 select HAVE_ARCH_MMAP_RND_BITS if MMU
170 select HAVE_ARCH_MMAP_RND_COMPAT_BITS if MMU && COMPAT
171 select HAVE_ARCH_COMPAT_MMAP_BASES if MMU && COMPAT
172 select HAVE_ARCH_PREL32_RELOCATIONS
173 select HAVE_ARCH_SECCOMP_FILTER
174 select HAVE_ARCH_THREAD_STRUCT_WHITELIST
175 select HAVE_ARCH_STACKLEAK
176 select HAVE_ARCH_TRACEHOOK
177 select HAVE_ARCH_TRANSPARENT_HUGEPAGE
178 select HAVE_ARCH_TRANSPARENT_HUGEPAGE_PUD if X86_64
179 select HAVE_ARCH_USERFAULTFD_WP if X86_64 && USERFAULTFD
180 select HAVE_ARCH_USERFAULTFD_MINOR if X86_64 && USERFAULTFD
181 select HAVE_ARCH_VMAP_STACK if X86_64
182 select HAVE_ARCH_RANDOMIZE_KSTACK_OFFSET
183 select HAVE_ARCH_WITHIN_STACK_FRAMES
184 select HAVE_ASM_MODVERSIONS
185 select HAVE_CMPXCHG_DOUBLE
186 select HAVE_CMPXCHG_LOCAL
187 select HAVE_CONTEXT_TRACKING if X86_64
188 select HAVE_CONTEXT_TRACKING_OFFSTACK if HAVE_CONTEXT_TRACKING
189 select HAVE_C_RECORDMCOUNT
190 select HAVE_OBJTOOL_MCOUNT if STACK_VALIDATION
191 select HAVE_BUILDTIME_MCOUNT_SORT
192 select HAVE_DEBUG_KMEMLEAK
193 select HAVE_DMA_CONTIGUOUS
194 select HAVE_DYNAMIC_FTRACE
195 select HAVE_DYNAMIC_FTRACE_WITH_REGS
196 select HAVE_DYNAMIC_FTRACE_WITH_ARGS if X86_64
197 select HAVE_DYNAMIC_FTRACE_WITH_DIRECT_CALLS
198 select HAVE_SAMPLE_FTRACE_DIRECT if X86_64
199 select HAVE_SAMPLE_FTRACE_DIRECT_MULTI if X86_64
201 select HAVE_EFFICIENT_UNALIGNED_ACCESS
203 select HAVE_EXIT_THREAD
205 select HAVE_FENTRY if X86_64 || DYNAMIC_FTRACE
206 select HAVE_FTRACE_MCOUNT_RECORD
207 select HAVE_FUNCTION_GRAPH_TRACER if X86_32 || (X86_64 && DYNAMIC_FTRACE)
208 select HAVE_FUNCTION_TRACER
209 select HAVE_GCC_PLUGINS
210 select HAVE_HW_BREAKPOINT
211 select HAVE_IOREMAP_PROT
212 select HAVE_IRQ_EXIT_ON_IRQ_STACK if X86_64
213 select HAVE_IRQ_TIME_ACCOUNTING
214 select HAVE_KERNEL_BZIP2
215 select HAVE_KERNEL_GZIP
216 select HAVE_KERNEL_LZ4
217 select HAVE_KERNEL_LZMA
218 select HAVE_KERNEL_LZO
219 select HAVE_KERNEL_XZ
220 select HAVE_KERNEL_ZSTD
222 select HAVE_KPROBES_ON_FTRACE
223 select HAVE_FUNCTION_ERROR_INJECTION
224 select HAVE_KRETPROBES
226 select HAVE_LIVEPATCH if X86_64
227 select HAVE_MIXED_BREAKPOINTS_REGS
228 select HAVE_MOD_ARCH_SPECIFIC
232 select HAVE_OPTPROBES
233 select HAVE_PCSPKR_PLATFORM
234 select HAVE_PERF_EVENTS
235 select HAVE_PERF_EVENTS_NMI
236 select HAVE_HARDLOCKUP_DETECTOR_PERF if PERF_EVENTS && HAVE_PERF_EVENTS_NMI
238 select HAVE_PERF_REGS
239 select HAVE_PERF_USER_STACK_DUMP
240 select MMU_GATHER_RCU_TABLE_FREE if PARAVIRT
241 select HAVE_POSIX_CPU_TIMERS_TASK_WORK
242 select HAVE_REGS_AND_STACK_ACCESS_API
243 select HAVE_RELIABLE_STACKTRACE if X86_64 && (UNWINDER_FRAME_POINTER || UNWINDER_ORC) && STACK_VALIDATION
244 select HAVE_FUNCTION_ARG_ACCESS_API
245 select HAVE_SETUP_PER_CPU_AREA
246 select HAVE_SOFTIRQ_ON_OWN_STACK
247 select HAVE_STACKPROTECTOR if CC_HAS_SANE_STACKPROTECTOR
248 select HAVE_STACK_VALIDATION if X86_64
249 select HAVE_STATIC_CALL
250 select HAVE_STATIC_CALL_INLINE if HAVE_STACK_VALIDATION
251 select HAVE_PREEMPT_DYNAMIC
253 select HAVE_SYSCALL_TRACEPOINTS
254 select HAVE_UNSTABLE_SCHED_CLOCK
255 select HAVE_USER_RETURN_NOTIFIER
256 select HAVE_GENERIC_VDSO
257 select HOTPLUG_SMT if SMP
258 select IRQ_FORCED_THREADING
259 select NEED_PER_CPU_EMBED_FIRST_CHUNK
260 select NEED_PER_CPU_PAGE_FIRST_CHUNK
261 select NEED_SG_DMA_LENGTH
262 select PCI_DOMAINS if PCI
263 select PCI_LOCKLESS_CONFIG if PCI
266 select RTC_MC146818_LIB
269 select STACK_VALIDATION if HAVE_STACK_VALIDATION && (HAVE_STATIC_CALL_INLINE || RETPOLINE)
270 select SYSCTL_EXCEPTION_TRACE
271 select THREAD_INFO_IN_TASK
272 select TRACE_IRQFLAGS_SUPPORT
273 select USER_STACKTRACE_SUPPORT
275 select HAVE_ARCH_KCSAN if X86_64
276 select X86_FEATURE_NAMES if PROC_FS
277 select PROC_PID_ARCH_STATUS if PROC_FS
278 select HAVE_ARCH_NODE_DEV_GROUP if X86_SGX
279 imply IMA_SECURE_AND_OR_TRUSTED_BOOT if EFI
281 config INSTRUCTION_DECODER
283 depends on KPROBES || PERF_EVENTS || UPROBES
287 default "elf32-i386" if X86_32
288 default "elf64-x86-64" if X86_64
290 config LOCKDEP_SUPPORT
293 config STACKTRACE_SUPPORT
299 config ARCH_MMAP_RND_BITS_MIN
303 config ARCH_MMAP_RND_BITS_MAX
307 config ARCH_MMAP_RND_COMPAT_BITS_MIN
310 config ARCH_MMAP_RND_COMPAT_BITS_MAX
316 config GENERIC_ISA_DMA
318 depends on ISA_DMA_API
323 select GENERIC_BUG_RELATIVE_POINTERS if X86_64
325 config GENERIC_BUG_RELATIVE_POINTERS
328 config ARCH_MAY_HAVE_PC_FDC
330 depends on ISA_DMA_API
332 config GENERIC_CALIBRATE_DELAY
335 config ARCH_HAS_CPU_RELAX
338 config ARCH_HAS_FILTER_PGPROT
341 config ARCH_HIBERNATION_POSSIBLE
346 default 1024 if X86_64
349 config ARCH_SUSPEND_POSSIBLE
352 config ARCH_WANT_GENERAL_HUGETLB
358 config KASAN_SHADOW_OFFSET
361 default 0xdffffc0000000000
363 config HAVE_INTEL_TXT
365 depends on INTEL_IOMMU && ACPI
369 depends on X86_32 && SMP
373 depends on X86_64 && SMP
375 config ARCH_SUPPORTS_UPROBES
378 config FIX_EARLYCON_MEM
381 config DYNAMIC_PHYSICAL_MASK
384 config PGTABLE_LEVELS
386 default 5 if X86_5LEVEL
391 config CC_HAS_SANE_STACKPROTECTOR
393 default $(success,$(srctree)/scripts/gcc-x86_64-has-stack-protector.sh $(CC)) if 64BIT
394 default $(success,$(srctree)/scripts/gcc-x86_32-has-stack-protector.sh $(CC))
396 We have to make sure stack protector is unconditionally disabled if
397 the compiler produces broken code or if it does not let us control
398 the segment on 32-bit kernels.
400 menu "Processor type and features"
403 bool "Symmetric multi-processing support"
405 This enables support for systems with more than one CPU. If you have
406 a system with only one CPU, say N. If you have a system with more
409 If you say N here, the kernel will run on uni- and multiprocessor
410 machines, but will use only one CPU of a multiprocessor machine. If
411 you say Y here, the kernel will run on many, but not all,
412 uniprocessor machines. On a uniprocessor machine, the kernel
413 will run faster if you say N here.
415 Note that if you say Y here and choose architecture "586" or
416 "Pentium" under "Processor family", the kernel will not work on 486
417 architectures. Similarly, multiprocessor kernels for the "PPro"
418 architecture may not work on all Pentium based boards.
420 People using multiprocessor machines who say Y here should also say
421 Y to "Enhanced Real Time Clock Support", below. The "Advanced Power
422 Management" code will be disabled if you say Y here.
424 See also <file:Documentation/x86/i386/IO-APIC.rst>,
425 <file:Documentation/admin-guide/lockup-watchdogs.rst> and the SMP-HOWTO available at
426 <http://www.tldp.org/docs.html#howto>.
428 If you don't know what to do here, say N.
430 config X86_FEATURE_NAMES
431 bool "Processor feature human-readable names" if EMBEDDED
434 This option compiles in a table of x86 feature bits and corresponding
435 names. This is required to support /proc/cpuinfo and a few kernel
436 messages. You can disable this to save space, at the expense of
437 making those few kernel messages show numeric feature bits instead.
442 bool "Support x2apic"
443 depends on X86_LOCAL_APIC && X86_64 && (IRQ_REMAP || HYPERVISOR_GUEST)
445 This enables x2apic support on CPUs that have this feature.
447 This allows 32-bit apic IDs (so it can support very large systems),
448 and accesses the local apic via MSRs not via mmio.
450 If you don't know what to do here, say N.
453 bool "Enable MPS table" if ACPI
455 depends on X86_LOCAL_APIC
457 For old smp systems that do not have proper acpi support. Newer systems
458 (esp with 64bit cpus) with acpi support, MADT and DSDT will override it
462 depends on X86_GOLDFISH
465 bool "Avoid speculative indirect branches in kernel"
468 Compile kernel with the retpoline compiler options to guard against
469 kernel-to-user data leaks by avoiding speculative indirect
470 branches. Requires a compiler with -mindirect-branch=thunk-extern
471 support for full protection. The kernel may run slower.
474 def_bool $(cc-option,-mharden-sls=all)
477 bool "Mitigate Straight-Line-Speculation"
478 depends on CC_HAS_SLS && X86_64
481 Compile the kernel with straight-line-speculation options to guard
482 against straight line speculation. The kernel image might be slightly
485 config X86_CPU_RESCTRL
486 bool "x86 CPU resource control support"
487 depends on X86 && (CPU_SUP_INTEL || CPU_SUP_AMD)
489 select PROC_CPU_RESCTRL if PROC_FS
491 Enable x86 CPU resource control support.
493 Provide support for the allocation and monitoring of system resources
496 Intel calls this Intel Resource Director Technology
497 (Intel(R) RDT). More information about RDT can be found in the
498 Intel x86 Architecture Software Developer Manual.
500 AMD calls this AMD Platform Quality of Service (AMD QoS).
501 More information about AMD QoS can be found in the AMD64 Technology
502 Platform Quality of Service Extensions manual.
508 bool "Support for big SMP systems with more than 8 CPUs"
511 This option is needed for the systems that have more than 8 CPUs.
513 config X86_EXTENDED_PLATFORM
514 bool "Support for extended (non-PC) x86 platforms"
517 If you disable this option then the kernel will only support
518 standard PC platforms. (which covers the vast majority of
521 If you enable this option then you'll be able to select support
522 for the following (non-PC) 32 bit x86 platforms:
523 Goldfish (Android emulator)
526 SGI 320/540 (Visual Workstation)
527 STA2X11-based (e.g. Northville)
528 Moorestown MID devices
530 If you have one of these systems, or if you want to build a
531 generic distribution kernel, say Y here - otherwise say N.
535 config X86_EXTENDED_PLATFORM
536 bool "Support for extended (non-PC) x86 platforms"
539 If you disable this option then the kernel will only support
540 standard PC platforms. (which covers the vast majority of
543 If you enable this option then you'll be able to select support
544 for the following (non-PC) 64 bit x86 platforms:
549 If you have one of these systems, or if you want to build a
550 generic distribution kernel, say Y here - otherwise say N.
552 # This is an alphabetically sorted list of 64 bit extended platforms
553 # Please maintain the alphabetic order if and when there are additions
555 bool "Numascale NumaChip"
557 depends on X86_EXTENDED_PLATFORM
560 depends on X86_X2APIC
561 depends on PCI_MMCONFIG
563 Adds support for Numascale NumaChip large-SMP systems. Needed to
564 enable more than ~168 cores.
565 If you don't have one of these, you should say N here.
569 select HYPERVISOR_GUEST
571 depends on X86_64 && PCI
572 depends on X86_EXTENDED_PLATFORM
575 Support for ScaleMP vSMP systems. Say 'Y' here if this kernel is
576 supposed to run on these EM64T-based machines. Only choose this option
577 if you have one of these machines.
580 bool "SGI Ultraviolet"
582 depends on X86_EXTENDED_PLATFORM
585 depends on KEXEC_CORE
586 depends on X86_X2APIC
589 This option is needed in order to support SGI Ultraviolet systems.
590 If you don't have one of these, you should say N here.
592 # Following is an alphabetically sorted list of 32 bit extended platforms
593 # Please maintain the alphabetic order if and when there are additions
596 bool "Goldfish (Virtual Platform)"
597 depends on X86_EXTENDED_PLATFORM
599 Enable support for the Goldfish virtual platform used primarily
600 for Android development. Unless you are building for the Android
601 Goldfish emulator say N here.
604 bool "CE4100 TV platform"
606 depends on PCI_GODIRECT
607 depends on X86_IO_APIC
609 depends on X86_EXTENDED_PLATFORM
610 select X86_REBOOTFIXUPS
612 select OF_EARLY_FLATTREE
614 Select for the Intel CE media processor (CE4100) SOC.
615 This option compiles in support for the CE4100 SOC for settop
616 boxes and media devices.
619 bool "Intel MID platform support"
620 depends on X86_EXTENDED_PLATFORM
621 depends on X86_PLATFORM_DEVICES
623 depends on X86_64 || (PCI_GOANY && X86_32)
624 depends on X86_IO_APIC
629 Select to build a kernel capable of supporting Intel MID (Mobile
630 Internet Device) platform systems which do not have the PCI legacy
631 interfaces. If you are building for a PC class system say N here.
633 Intel MID platforms are based on an Intel processor and chipset which
634 consume less power than most of the x86 derivatives.
636 config X86_INTEL_QUARK
637 bool "Intel Quark platform support"
639 depends on X86_EXTENDED_PLATFORM
640 depends on X86_PLATFORM_DEVICES
644 depends on X86_IO_APIC
649 Select to include support for Quark X1000 SoC.
650 Say Y here if you have a Quark based system such as the Arduino
651 compatible Intel Galileo.
653 config X86_INTEL_LPSS
654 bool "Intel Low Power Subsystem Support"
655 depends on X86 && ACPI && PCI
660 Select to build support for Intel Low Power Subsystem such as
661 found on Intel Lynxpoint PCH. Selecting this option enables
662 things like clock tree (common clock framework) and pincontrol
663 which are needed by the LPSS peripheral drivers.
665 config X86_AMD_PLATFORM_DEVICE
666 bool "AMD ACPI2Platform devices support"
671 Select to interpret AMD specific ACPI device to platform device
672 such as I2C, UART, GPIO found on AMD Carrizo and later chipsets.
673 I2C and UART depend on COMMON_CLK to set clock. GPIO driver is
674 implemented under PINCTRL subsystem.
677 tristate "Intel SoC IOSF Sideband support for SoC platforms"
680 This option enables sideband register access support for Intel SoC
681 platforms. On these platforms the IOSF sideband is used in lieu of
682 MSR's for some register accesses, mostly but not limited to thermal
683 and power. Drivers may query the availability of this device to
684 determine if they need the sideband in order to work on these
685 platforms. The sideband is available on the following SoC products.
686 This list is not meant to be exclusive.
691 You should say Y if you are running a kernel on one of these SoC's.
693 config IOSF_MBI_DEBUG
694 bool "Enable IOSF sideband access through debugfs"
695 depends on IOSF_MBI && DEBUG_FS
697 Select this option to expose the IOSF sideband access registers (MCR,
698 MDR, MCRX) through debugfs to write and read register information from
699 different units on the SoC. This is most useful for obtaining device
700 state information for debug and analysis. As this is a general access
701 mechanism, users of this option would have specific knowledge of the
702 device they want to access.
704 If you don't require the option or are in doubt, say N.
707 bool "RDC R-321x SoC"
709 depends on X86_EXTENDED_PLATFORM
711 select X86_REBOOTFIXUPS
713 This option is needed for RDC R-321x system-on-chip, also known
715 If you don't have one of these chips, you should say N here.
717 config X86_32_NON_STANDARD
718 bool "Support non-standard 32-bit SMP architectures"
719 depends on X86_32 && SMP
720 depends on X86_EXTENDED_PLATFORM
722 This option compiles in the bigsmp and STA2X11 default
723 subarchitectures. It is intended for a generic binary
724 kernel. If you select them all, kernel will probe it one by
725 one and will fallback to default.
727 # Alphabetically sorted list of Non standard 32 bit platforms
729 config X86_SUPPORTS_MEMORY_FAILURE
731 # MCE code calls memory_failure():
733 # On 32-bit this adds too big of NODES_SHIFT and we run out of page flags:
734 # On 32-bit SPARSEMEM adds too big of SECTIONS_WIDTH:
735 depends on X86_64 || !SPARSEMEM
736 select ARCH_SUPPORTS_MEMORY_FAILURE
739 bool "STA2X11 Companion Chip Support"
740 depends on X86_32_NON_STANDARD && PCI
745 This adds support for boards based on the STA2X11 IO-Hub,
746 a.k.a. "ConneXt". The chip is used in place of the standard
747 PC chipset, so all "standard" peripherals are missing. If this
748 option is selected the kernel will still be able to boot on
749 standard PC machines.
752 tristate "Eurobraille/Iris poweroff module"
755 The Iris machines from EuroBraille do not have APM or ACPI support
756 to shut themselves down properly. A special I/O sequence is
757 needed to do so, which is what this module does at
760 This is only for Iris machines from EuroBraille.
764 config SCHED_OMIT_FRAME_POINTER
766 prompt "Single-depth WCHAN output"
769 Calculate simpler /proc/<PID>/wchan values. If this option
770 is disabled then wchan values will recurse back to the
771 caller function. This provides more accurate wchan values,
772 at the expense of slightly more scheduling overhead.
774 If in doubt, say "Y".
776 menuconfig HYPERVISOR_GUEST
777 bool "Linux guest support"
779 Say Y here to enable options for running Linux under various hyper-
780 visors. This option enables basic hypervisor detection and platform
783 If you say N, all options in this submenu will be skipped and
784 disabled, and Linux guest support won't be built in.
789 bool "Enable paravirtualization code"
790 depends on HAVE_STATIC_CALL
792 This changes the kernel so it can modify itself when it is run
793 under a hypervisor, potentially improving performance significantly
794 over full virtualization. However, when run without a hypervisor
795 the kernel is theoretically slower and slightly larger.
800 config PARAVIRT_DEBUG
801 bool "paravirt-ops debugging"
802 depends on PARAVIRT && DEBUG_KERNEL
804 Enable to debug paravirt_ops internals. Specifically, BUG if
805 a paravirt_op is missing when it is called.
807 config PARAVIRT_SPINLOCKS
808 bool "Paravirtualization layer for spinlocks"
809 depends on PARAVIRT && SMP
811 Paravirtualized spinlocks allow a pvops backend to replace the
812 spinlock implementation with something virtualization-friendly
813 (for example, block the virtual CPU rather than spinning).
815 It has a minimal impact on native kernels and gives a nice performance
816 benefit on paravirtualized KVM / Xen kernels.
818 If you are unsure how to answer this question, answer Y.
820 config X86_HV_CALLBACK_VECTOR
823 source "arch/x86/xen/Kconfig"
826 bool "KVM Guest support (including kvmclock)"
828 select PARAVIRT_CLOCK
829 select ARCH_CPUIDLE_HALTPOLL
830 select X86_HV_CALLBACK_VECTOR
833 This option enables various optimizations for running under the KVM
834 hypervisor. It includes a paravirtualized clock, so that instead
835 of relying on a PIT (or probably other) emulation by the
836 underlying device model, the host provides the guest with
837 timing infrastructure such as time of day, and system time
839 config ARCH_CPUIDLE_HALTPOLL
841 prompt "Disable host haltpoll when loading haltpoll driver"
843 If virtualized under KVM, disable host haltpoll.
846 bool "Support for running PVH guests"
848 This option enables the PVH entry point for guest virtual machines
849 as specified in the x86/HVM direct boot ABI.
851 config PARAVIRT_TIME_ACCOUNTING
852 bool "Paravirtual steal time accounting"
855 Select this option to enable fine granularity task steal time
856 accounting. Time spent executing other tasks in parallel with
857 the current vCPU is discounted from the vCPU power. To account for
858 that, there can be a small performance impact.
860 If in doubt, say N here.
862 config PARAVIRT_CLOCK
865 config JAILHOUSE_GUEST
866 bool "Jailhouse non-root cell support"
867 depends on X86_64 && PCI
870 This option allows to run Linux as guest in a Jailhouse non-root
871 cell. You can leave this option disabled if you only want to start
872 Jailhouse and run Linux afterwards in the root cell.
875 bool "ACRN Guest support"
877 select X86_HV_CALLBACK_VECTOR
879 This option allows to run Linux as guest in the ACRN hypervisor. ACRN is
880 a flexible, lightweight reference open-source hypervisor, built with
881 real-time and safety-criticality in mind. It is built for embedded
882 IOT with small footprint and real-time features. More details can be
883 found in https://projectacrn.org/.
885 endif #HYPERVISOR_GUEST
887 source "arch/x86/Kconfig.cpu"
891 prompt "HPET Timer Support" if X86_32
893 Use the IA-PC HPET (High Precision Event Timer) to manage
894 time in preference to the PIT and RTC, if a HPET is
896 HPET is the next generation timer replacing legacy 8254s.
897 The HPET provides a stable time base on SMP
898 systems, unlike the TSC, but it is more expensive to access,
899 as it is off-chip. The interface used is documented
900 in the HPET spec, revision 1.
902 You can safely choose Y here. However, HPET will only be
903 activated if the platform and the BIOS support this feature.
904 Otherwise the 8254 will be used for timing services.
906 Choose N to continue using the legacy 8254 timer.
908 config HPET_EMULATE_RTC
910 depends on HPET_TIMER && (RTC_DRV_CMOS=m || RTC_DRV_CMOS=y)
912 # Mark as expert because too many people got it wrong.
913 # The code disables itself when not needed.
916 select DMI_SCAN_MACHINE_NON_EFI_FALLBACK
917 bool "Enable DMI scanning" if EXPERT
919 Enabled scanning of DMI to identify machine quirks. Say Y
920 here unless you have verified that your setup is not
921 affected by entries in the DMI blacklist. Required by PNP
925 bool "Old AMD GART IOMMU support"
929 depends on X86_64 && PCI && AMD_NB
931 Provides a driver for older AMD Athlon64/Opteron/Turion/Sempron
932 GART based hardware IOMMUs.
934 The GART supports full DMA access for devices with 32-bit access
935 limitations, on systems with more than 3 GB. This is usually needed
936 for USB, sound, many IDE/SATA chipsets and some other devices.
938 Newer systems typically have a modern AMD IOMMU, supported via
939 the CONFIG_AMD_IOMMU=y config option.
941 In normal configurations this driver is only active when needed:
942 there's more than 3 GB of memory and the system contains a
943 32-bit limited device.
948 bool "Enable Maximum number of SMP Processors and NUMA Nodes"
949 depends on X86_64 && SMP && DEBUG_KERNEL
950 select CPUMASK_OFFSTACK
952 Enable maximum number of CPUS and NUMA Nodes for this architecture.
956 # The maximum number of CPUs supported:
958 # The main config value is NR_CPUS, which defaults to NR_CPUS_DEFAULT,
959 # and which can be configured interactively in the
960 # [NR_CPUS_RANGE_BEGIN ... NR_CPUS_RANGE_END] range.
962 # The ranges are different on 32-bit and 64-bit kernels, depending on
963 # hardware capabilities and scalability features of the kernel.
965 # ( If MAXSMP is enabled we just use the highest possible value and disable
966 # interactive configuration. )
969 config NR_CPUS_RANGE_BEGIN
971 default NR_CPUS_RANGE_END if MAXSMP
975 config NR_CPUS_RANGE_END
978 default 64 if SMP && X86_BIGSMP
979 default 8 if SMP && !X86_BIGSMP
982 config NR_CPUS_RANGE_END
985 default 8192 if SMP && CPUMASK_OFFSTACK
986 default 512 if SMP && !CPUMASK_OFFSTACK
989 config NR_CPUS_DEFAULT
992 default 32 if X86_BIGSMP
996 config NR_CPUS_DEFAULT
999 default 8192 if MAXSMP
1004 int "Maximum number of CPUs" if SMP && !MAXSMP
1005 range NR_CPUS_RANGE_BEGIN NR_CPUS_RANGE_END
1006 default NR_CPUS_DEFAULT
1008 This allows you to specify the maximum number of CPUs which this
1009 kernel will support. If CPUMASK_OFFSTACK is enabled, the maximum
1010 supported value is 8192, otherwise the maximum value is 512. The
1011 minimum value which makes sense is 2.
1013 This is purely to save memory: each supported CPU adds about 8KB
1014 to the kernel image.
1016 config SCHED_CLUSTER
1017 bool "Cluster scheduler support"
1021 Cluster scheduler support improves the CPU scheduler's decision
1022 making when dealing with machines that have clusters of CPUs.
1023 Cluster usually means a couple of CPUs which are placed closely
1024 by sharing mid-level caches, last-level cache tags or internal
1032 prompt "Multi-core scheduler support"
1035 Multi-core scheduler support improves the CPU scheduler's decision
1036 making when dealing with multi-core CPU chips at a cost of slightly
1037 increased overhead in some places. If unsure say N here.
1039 config SCHED_MC_PRIO
1040 bool "CPU core priorities scheduler support"
1041 depends on SCHED_MC && CPU_SUP_INTEL
1042 select X86_INTEL_PSTATE
1046 Intel Turbo Boost Max Technology 3.0 enabled CPUs have a
1047 core ordering determined at manufacturing time, which allows
1048 certain cores to reach higher turbo frequencies (when running
1049 single threaded workloads) than others.
1051 Enabling this kernel feature teaches the scheduler about
1052 the TBM3 (aka ITMT) priority order of the CPU cores and adjusts the
1053 scheduler's CPU selection logic accordingly, so that higher
1054 overall system performance can be achieved.
1056 This feature will have no effect on CPUs without this feature.
1058 If unsure say Y here.
1062 depends on !SMP && X86_LOCAL_APIC
1065 bool "Local APIC support on uniprocessors" if !PCI_MSI
1067 depends on X86_32 && !SMP && !X86_32_NON_STANDARD
1069 A local APIC (Advanced Programmable Interrupt Controller) is an
1070 integrated interrupt controller in the CPU. If you have a single-CPU
1071 system which has a processor with a local APIC, you can say Y here to
1072 enable and use it. If you say Y here even though your machine doesn't
1073 have a local APIC, then the kernel will still run with no slowdown at
1074 all. The local APIC supports CPU-generated self-interrupts (timer,
1075 performance counters), and the NMI watchdog which detects hard
1078 config X86_UP_IOAPIC
1079 bool "IO-APIC support on uniprocessors"
1080 depends on X86_UP_APIC
1082 An IO-APIC (I/O Advanced Programmable Interrupt Controller) is an
1083 SMP-capable replacement for PC-style interrupt controllers. Most
1084 SMP systems and many recent uniprocessor systems have one.
1086 If you have a single-CPU system with an IO-APIC, you can say Y here
1087 to use it. If you say Y here even though your machine doesn't have
1088 an IO-APIC, then the kernel will still run with no slowdown at all.
1090 config X86_LOCAL_APIC
1092 depends on X86_64 || SMP || X86_32_NON_STANDARD || X86_UP_APIC || PCI_MSI
1093 select IRQ_DOMAIN_HIERARCHY
1094 select PCI_MSI_IRQ_DOMAIN if PCI_MSI
1098 depends on X86_LOCAL_APIC || X86_UP_IOAPIC
1100 config X86_REROUTE_FOR_BROKEN_BOOT_IRQS
1101 bool "Reroute for broken boot IRQs"
1102 depends on X86_IO_APIC
1104 This option enables a workaround that fixes a source of
1105 spurious interrupts. This is recommended when threaded
1106 interrupt handling is used on systems where the generation of
1107 superfluous "boot interrupts" cannot be disabled.
1109 Some chipsets generate a legacy INTx "boot IRQ" when the IRQ
1110 entry in the chipset's IO-APIC is masked (as, e.g. the RT
1111 kernel does during interrupt handling). On chipsets where this
1112 boot IRQ generation cannot be disabled, this workaround keeps
1113 the original IRQ line masked so that only the equivalent "boot
1114 IRQ" is delivered to the CPUs. The workaround also tells the
1115 kernel to set up the IRQ handler on the boot IRQ line. In this
1116 way only one interrupt is delivered to the kernel. Otherwise
1117 the spurious second interrupt may cause the kernel to bring
1118 down (vital) interrupt lines.
1120 Only affects "broken" chipsets. Interrupt sharing may be
1121 increased on these systems.
1124 bool "Machine Check / overheating reporting"
1125 select GENERIC_ALLOCATOR
1128 Machine Check support allows the processor to notify the
1129 kernel if it detects a problem (e.g. overheating, data corruption).
1130 The action the kernel takes depends on the severity of the problem,
1131 ranging from warning messages to halting the machine.
1133 config X86_MCELOG_LEGACY
1134 bool "Support for deprecated /dev/mcelog character device"
1137 Enable support for /dev/mcelog which is needed by the old mcelog
1138 userspace logging daemon. Consider switching to the new generation
1141 config X86_MCE_INTEL
1143 prompt "Intel MCE features"
1144 depends on X86_MCE && X86_LOCAL_APIC
1146 Additional support for intel specific MCE features such as
1147 the thermal monitor.
1151 prompt "AMD MCE features"
1152 depends on X86_MCE && X86_LOCAL_APIC && AMD_NB
1154 Additional support for AMD specific MCE features such as
1155 the DRAM Error Threshold.
1157 config X86_ANCIENT_MCE
1158 bool "Support for old Pentium 5 / WinChip machine checks"
1159 depends on X86_32 && X86_MCE
1161 Include support for machine check handling on old Pentium 5 or WinChip
1162 systems. These typically need to be enabled explicitly on the command
1165 config X86_MCE_THRESHOLD
1166 depends on X86_MCE_AMD || X86_MCE_INTEL
1169 config X86_MCE_INJECT
1170 depends on X86_MCE && X86_LOCAL_APIC && DEBUG_FS
1171 tristate "Machine check injector support"
1173 Provide support for injecting machine checks for testing purposes.
1174 If you don't know what a machine check is and you don't do kernel
1175 QA it is safe to say n.
1177 source "arch/x86/events/Kconfig"
1179 config X86_LEGACY_VM86
1180 bool "Legacy VM86 support"
1183 This option allows user programs to put the CPU into V8086
1184 mode, which is an 80286-era approximation of 16-bit real mode.
1186 Some very old versions of X and/or vbetool require this option
1187 for user mode setting. Similarly, DOSEMU will use it if
1188 available to accelerate real mode DOS programs. However, any
1189 recent version of DOSEMU, X, or vbetool should be fully
1190 functional even without kernel VM86 support, as they will all
1191 fall back to software emulation. Nevertheless, if you are using
1192 a 16-bit DOS program where 16-bit performance matters, vm86
1193 mode might be faster than emulation and you might want to
1196 Note that any app that works on a 64-bit kernel is unlikely to
1197 need this option, as 64-bit kernels don't, and can't, support
1198 V8086 mode. This option is also unrelated to 16-bit protected
1199 mode and is not needed to run most 16-bit programs under Wine.
1201 Enabling this option increases the complexity of the kernel
1202 and slows down exception handling a tiny bit.
1204 If unsure, say N here.
1208 default X86_LEGACY_VM86
1211 bool "Enable support for 16-bit segments" if EXPERT
1213 depends on MODIFY_LDT_SYSCALL
1215 This option is required by programs like Wine to run 16-bit
1216 protected mode legacy code on x86 processors. Disabling
1217 this option saves about 300 bytes on i386, or around 6K text
1218 plus 16K runtime memory on x86-64,
1222 depends on X86_16BIT && X86_32
1226 depends on X86_16BIT && X86_64
1228 config X86_VSYSCALL_EMULATION
1229 bool "Enable vsyscall emulation" if EXPERT
1233 This enables emulation of the legacy vsyscall page. Disabling
1234 it is roughly equivalent to booting with vsyscall=none, except
1235 that it will also disable the helpful warning if a program
1236 tries to use a vsyscall. With this option set to N, offending
1237 programs will just segfault, citing addresses of the form
1240 This option is required by many programs built before 2013, and
1241 care should be used even with newer programs if set to N.
1243 Disabling this option saves about 7K of kernel size and
1244 possibly 4K of additional runtime pagetable memory.
1246 config X86_IOPL_IOPERM
1247 bool "IOPERM and IOPL Emulation"
1250 This enables the ioperm() and iopl() syscalls which are necessary
1251 for legacy applications.
1253 Legacy IOPL support is an overbroad mechanism which allows user
1254 space aside of accessing all 65536 I/O ports also to disable
1255 interrupts. To gain this access the caller needs CAP_SYS_RAWIO
1256 capabilities and permission from potentially active security
1259 The emulation restricts the functionality of the syscall to
1260 only allowing the full range I/O port access, but prevents the
1261 ability to disable interrupts from user space which would be
1262 granted if the hardware IOPL mechanism would be used.
1265 tristate "Toshiba Laptop support"
1268 This adds a driver to safely access the System Management Mode of
1269 the CPU on Toshiba portables with a genuine Toshiba BIOS. It does
1270 not work on models with a Phoenix BIOS. The System Management Mode
1271 is used to set the BIOS and power saving options on Toshiba portables.
1273 For information on utilities to make use of this driver see the
1274 Toshiba Linux utilities web site at:
1275 <http://www.buzzard.org.uk/toshiba/>.
1277 Say Y if you intend to run this kernel on a Toshiba portable.
1280 config X86_REBOOTFIXUPS
1281 bool "Enable X86 board specific fixups for reboot"
1284 This enables chipset and/or board specific fixups to be done
1285 in order to get reboot to work correctly. This is only needed on
1286 some combinations of hardware and BIOS. The symptom, for which
1287 this config is intended, is when reboot ends with a stalled/hung
1290 Currently, the only fixup is for the Geode machines using
1291 CS5530A and CS5536 chipsets and the RDC R-321x SoC.
1293 Say Y if you want to enable the fixup. Currently, it's safe to
1294 enable this option even if you don't need it.
1298 bool "CPU microcode loading support"
1300 depends on CPU_SUP_AMD || CPU_SUP_INTEL
1302 If you say Y here, you will be able to update the microcode on
1303 Intel and AMD processors. The Intel support is for the IA32 family,
1304 e.g. Pentium Pro, Pentium II, Pentium III, Pentium 4, Xeon etc. The
1305 AMD support is for families 0x10 and later. You will obviously need
1306 the actual microcode binary data itself which is not shipped with
1309 The preferred method to load microcode from a detached initrd is described
1310 in Documentation/x86/microcode.rst. For that you need to enable
1311 CONFIG_BLK_DEV_INITRD in order for the loader to be able to scan the
1312 initrd for microcode blobs.
1314 In addition, you can build the microcode into the kernel. For that you
1315 need to add the vendor-supplied microcode to the CONFIG_EXTRA_FIRMWARE
1318 config MICROCODE_INTEL
1319 bool "Intel microcode loading support"
1320 depends on MICROCODE
1323 This options enables microcode patch loading support for Intel
1326 For the current Intel microcode data package go to
1327 <https://downloadcenter.intel.com> and search for
1328 'Linux Processor Microcode Data File'.
1330 config MICROCODE_AMD
1331 bool "AMD microcode loading support"
1332 depends on MICROCODE
1334 If you select this option, microcode patch loading support for AMD
1335 processors will be enabled.
1337 config MICROCODE_OLD_INTERFACE
1338 bool "Ancient loading interface (DEPRECATED)"
1340 depends on MICROCODE
1342 DO NOT USE THIS! This is the ancient /dev/cpu/microcode interface
1343 which was used by userspace tools like iucode_tool and microcode.ctl.
1344 It is inadequate because it runs too late to be able to properly
1345 load microcode on a machine and it needs special tools. Instead, you
1346 should've switched to the early loading method with the initrd or
1347 builtin microcode by now: Documentation/x86/microcode.rst
1350 tristate "/dev/cpu/*/msr - Model-specific register support"
1352 This device gives privileged processes access to the x86
1353 Model-Specific Registers (MSRs). It is a character device with
1354 major 202 and minors 0 to 31 for /dev/cpu/0/msr to /dev/cpu/31/msr.
1355 MSR accesses are directed to a specific CPU on multi-processor
1359 tristate "/dev/cpu/*/cpuid - CPU information support"
1361 This device gives processes access to the x86 CPUID instruction to
1362 be executed on a specific processor. It is a character device
1363 with major 203 and minors 0 to 31 for /dev/cpu/0/cpuid to
1367 prompt "High Memory Support"
1374 Linux can use up to 64 Gigabytes of physical memory on x86 systems.
1375 However, the address space of 32-bit x86 processors is only 4
1376 Gigabytes large. That means that, if you have a large amount of
1377 physical memory, not all of it can be "permanently mapped" by the
1378 kernel. The physical memory that's not permanently mapped is called
1381 If you are compiling a kernel which will never run on a machine with
1382 more than 1 Gigabyte total physical RAM, answer "off" here (default
1383 choice and suitable for most users). This will result in a "3GB/1GB"
1384 split: 3GB are mapped so that each process sees a 3GB virtual memory
1385 space and the remaining part of the 4GB virtual memory space is used
1386 by the kernel to permanently map as much physical memory as
1389 If the machine has between 1 and 4 Gigabytes physical RAM, then
1392 If more than 4 Gigabytes is used then answer "64GB" here. This
1393 selection turns Intel PAE (Physical Address Extension) mode on.
1394 PAE implements 3-level paging on IA32 processors. PAE is fully
1395 supported by Linux, PAE mode is implemented on all recent Intel
1396 processors (Pentium Pro and better). NOTE: If you say "64GB" here,
1397 then the kernel will not boot on CPUs that don't support PAE!
1399 The actual amount of total physical memory will either be
1400 auto detected or can be forced by using a kernel command line option
1401 such as "mem=256M". (Try "man bootparam" or see the documentation of
1402 your boot loader (lilo or loadlin) about how to pass options to the
1403 kernel at boot time.)
1405 If unsure, say "off".
1410 Select this if you have a 32-bit processor and between 1 and 4
1411 gigabytes of physical RAM.
1415 depends on !M486SX && !M486 && !M586 && !M586TSC && !M586MMX && !MGEODE_LX && !MGEODEGX1 && !MCYRIXIII && !MELAN && !MWINCHIPC6 && !MWINCHIP3D && !MK6
1418 Select this if you have a 32-bit processor and more than 4
1419 gigabytes of physical RAM.
1424 prompt "Memory split" if EXPERT
1428 Select the desired split between kernel and user memory.
1430 If the address range available to the kernel is less than the
1431 physical memory installed, the remaining memory will be available
1432 as "high memory". Accessing high memory is a little more costly
1433 than low memory, as it needs to be mapped into the kernel first.
1434 Note that increasing the kernel address space limits the range
1435 available to user programs, making the address space there
1436 tighter. Selecting anything other than the default 3G/1G split
1437 will also likely make your kernel incompatible with binary-only
1440 If you are not absolutely sure what you are doing, leave this
1444 bool "3G/1G user/kernel split"
1445 config VMSPLIT_3G_OPT
1447 bool "3G/1G user/kernel split (for full 1G low memory)"
1449 bool "2G/2G user/kernel split"
1450 config VMSPLIT_2G_OPT
1452 bool "2G/2G user/kernel split (for full 2G low memory)"
1454 bool "1G/3G user/kernel split"
1459 default 0xB0000000 if VMSPLIT_3G_OPT
1460 default 0x80000000 if VMSPLIT_2G
1461 default 0x78000000 if VMSPLIT_2G_OPT
1462 default 0x40000000 if VMSPLIT_1G
1468 depends on X86_32 && (HIGHMEM64G || HIGHMEM4G)
1471 bool "PAE (Physical Address Extension) Support"
1472 depends on X86_32 && !HIGHMEM4G
1473 select PHYS_ADDR_T_64BIT
1476 PAE is required for NX support, and furthermore enables
1477 larger swapspace support for non-overcommit purposes. It
1478 has the cost of more pagetable lookup overhead, and also
1479 consumes more pagetable space per process.
1482 bool "Enable 5-level page tables support"
1484 select DYNAMIC_MEMORY_LAYOUT
1485 select SPARSEMEM_VMEMMAP
1488 5-level paging enables access to larger address space:
1489 upto 128 PiB of virtual address space and 4 PiB of
1490 physical address space.
1492 It will be supported by future Intel CPUs.
1494 A kernel with the option enabled can be booted on machines that
1495 support 4- or 5-level paging.
1497 See Documentation/x86/x86_64/5level-paging.rst for more
1502 config X86_DIRECT_GBPAGES
1506 Certain kernel features effectively disable kernel
1507 linear 1 GB mappings (even if the CPU otherwise
1508 supports them), so don't confuse the user by printing
1509 that we have them enabled.
1511 config X86_CPA_STATISTICS
1512 bool "Enable statistic for Change Page Attribute"
1515 Expose statistics about the Change Page Attribute mechanism, which
1516 helps to determine the effectiveness of preserving large and huge
1517 page mappings when mapping protections are changed.
1519 config X86_MEM_ENCRYPT
1520 select ARCH_HAS_FORCE_DMA_UNENCRYPTED
1521 select DYNAMIC_PHYSICAL_MASK
1522 select ARCH_HAS_RESTRICTED_VIRTIO_MEMORY_ACCESS
1525 config AMD_MEM_ENCRYPT
1526 bool "AMD Secure Memory Encryption (SME) support"
1527 depends on X86_64 && CPU_SUP_AMD
1528 select DMA_COHERENT_POOL
1529 select ARCH_USE_MEMREMAP_PROT
1530 select INSTRUCTION_DECODER
1531 select ARCH_HAS_CC_PLATFORM
1532 select X86_MEM_ENCRYPT
1534 Say yes to enable support for the encryption of system memory.
1535 This requires an AMD processor that supports Secure Memory
1538 config AMD_MEM_ENCRYPT_ACTIVE_BY_DEFAULT
1539 bool "Activate AMD Secure Memory Encryption (SME) by default"
1540 depends on AMD_MEM_ENCRYPT
1542 Say yes to have system memory encrypted by default if running on
1543 an AMD processor that supports Secure Memory Encryption (SME).
1545 If set to Y, then the encryption of system memory can be
1546 deactivated with the mem_encrypt=off command line option.
1548 If set to N, then the encryption of system memory can be
1549 activated with the mem_encrypt=on command line option.
1551 # Common NUMA Features
1553 bool "NUMA Memory Allocation and Scheduler Support"
1555 depends on X86_64 || (X86_32 && HIGHMEM64G && X86_BIGSMP)
1556 default y if X86_BIGSMP
1557 select USE_PERCPU_NUMA_NODE_ID
1559 Enable NUMA (Non-Uniform Memory Access) support.
1561 The kernel will try to allocate memory used by a CPU on the
1562 local memory controller of the CPU and add some more
1563 NUMA awareness to the kernel.
1565 For 64-bit this is recommended if the system is Intel Core i7
1566 (or later), AMD Opteron, or EM64T NUMA.
1568 For 32-bit this is only needed if you boot a 32-bit
1569 kernel on a 64-bit NUMA platform.
1571 Otherwise, you should say N.
1575 prompt "Old style AMD Opteron NUMA detection"
1576 depends on X86_64 && NUMA && PCI
1578 Enable AMD NUMA node topology detection. You should say Y here if
1579 you have a multi processor AMD system. This uses an old method to
1580 read the NUMA configuration directly from the builtin Northbridge
1581 of Opteron. It is recommended to use X86_64_ACPI_NUMA instead,
1582 which also takes priority if both are compiled in.
1584 config X86_64_ACPI_NUMA
1586 prompt "ACPI NUMA detection"
1587 depends on X86_64 && NUMA && ACPI && PCI
1590 Enable ACPI SRAT based node topology detection.
1593 bool "NUMA emulation"
1596 Enable NUMA emulation. A flat machine will be split
1597 into virtual nodes when booted with "numa=fake=N", where N is the
1598 number of nodes. This is only useful for debugging.
1601 int "Maximum NUMA Nodes (as a power of 2)" if !MAXSMP
1603 default "10" if MAXSMP
1604 default "6" if X86_64
1608 Specify the maximum number of NUMA Nodes available on the target
1609 system. Increases memory reserved to accommodate various tables.
1611 config ARCH_FLATMEM_ENABLE
1613 depends on X86_32 && !NUMA
1615 config ARCH_SPARSEMEM_ENABLE
1617 depends on X86_64 || NUMA || X86_32 || X86_32_NON_STANDARD
1618 select SPARSEMEM_STATIC if X86_32
1619 select SPARSEMEM_VMEMMAP_ENABLE if X86_64
1621 config ARCH_SPARSEMEM_DEFAULT
1622 def_bool X86_64 || (NUMA && X86_32)
1624 config ARCH_SELECT_MEMORY_MODEL
1626 depends on ARCH_SPARSEMEM_ENABLE && ARCH_FLATMEM_ENABLE
1628 config ARCH_MEMORY_PROBE
1629 bool "Enable sysfs memory/probe interface"
1630 depends on MEMORY_HOTPLUG
1632 This option enables a sysfs memory/probe interface for testing.
1633 See Documentation/admin-guide/mm/memory-hotplug.rst for more information.
1634 If you are unsure how to answer this question, answer N.
1636 config ARCH_PROC_KCORE_TEXT
1638 depends on X86_64 && PROC_KCORE
1640 config ILLEGAL_POINTER_VALUE
1643 default 0xdead000000000000 if X86_64
1645 config X86_PMEM_LEGACY_DEVICE
1648 config X86_PMEM_LEGACY
1649 tristate "Support non-standard NVDIMMs and ADR protected memory"
1650 depends on PHYS_ADDR_T_64BIT
1652 select X86_PMEM_LEGACY_DEVICE
1653 select NUMA_KEEP_MEMINFO if NUMA
1656 Treat memory marked using the non-standard e820 type of 12 as used
1657 by the Intel Sandy Bridge-EP reference BIOS as protected memory.
1658 The kernel will offer these regions to the 'pmem' driver so
1659 they can be used for persistent storage.
1664 bool "Allocate 3rd-level pagetables from highmem"
1667 The VM uses one page table entry for each page of physical memory.
1668 For systems with a lot of RAM, this can be wasteful of precious
1669 low memory. Setting this option will put user-space page table
1670 entries in high memory.
1672 config X86_CHECK_BIOS_CORRUPTION
1673 bool "Check for low memory corruption"
1675 Periodically check for memory corruption in low memory, which
1676 is suspected to be caused by BIOS. Even when enabled in the
1677 configuration, it is disabled at runtime. Enable it by
1678 setting "memory_corruption_check=1" on the kernel command
1679 line. By default it scans the low 64k of memory every 60
1680 seconds; see the memory_corruption_check_size and
1681 memory_corruption_check_period parameters in
1682 Documentation/admin-guide/kernel-parameters.rst to adjust this.
1684 When enabled with the default parameters, this option has
1685 almost no overhead, as it reserves a relatively small amount
1686 of memory and scans it infrequently. It both detects corruption
1687 and prevents it from affecting the running system.
1689 It is, however, intended as a diagnostic tool; if repeatable
1690 BIOS-originated corruption always affects the same memory,
1691 you can use memmap= to prevent the kernel from using that
1694 config X86_BOOTPARAM_MEMORY_CORRUPTION_CHECK
1695 bool "Set the default setting of memory_corruption_check"
1696 depends on X86_CHECK_BIOS_CORRUPTION
1699 Set whether the default state of memory_corruption_check is
1702 config MATH_EMULATION
1704 depends on MODIFY_LDT_SYSCALL
1705 prompt "Math emulation" if X86_32 && (M486SX || MELAN)
1707 Linux can emulate a math coprocessor (used for floating point
1708 operations) if you don't have one. 486DX and Pentium processors have
1709 a math coprocessor built in, 486SX and 386 do not, unless you added
1710 a 487DX or 387, respectively. (The messages during boot time can
1711 give you some hints here ["man dmesg"].) Everyone needs either a
1712 coprocessor or this emulation.
1714 If you don't have a math coprocessor, you need to say Y here; if you
1715 say Y here even though you have a coprocessor, the coprocessor will
1716 be used nevertheless. (This behavior can be changed with the kernel
1717 command line option "no387", which comes handy if your coprocessor
1718 is broken. Try "man bootparam" or see the documentation of your boot
1719 loader (lilo or loadlin) about how to pass options to the kernel at
1720 boot time.) This means that it is a good idea to say Y here if you
1721 intend to use this kernel on different machines.
1723 More information about the internals of the Linux math coprocessor
1724 emulation can be found in <file:arch/x86/math-emu/README>.
1726 If you are not sure, say Y; apart from resulting in a 66 KB bigger
1727 kernel, it won't hurt.
1731 prompt "MTRR (Memory Type Range Register) support" if EXPERT
1733 On Intel P6 family processors (Pentium Pro, Pentium II and later)
1734 the Memory Type Range Registers (MTRRs) may be used to control
1735 processor access to memory ranges. This is most useful if you have
1736 a video (VGA) card on a PCI or AGP bus. Enabling write-combining
1737 allows bus write transfers to be combined into a larger transfer
1738 before bursting over the PCI/AGP bus. This can increase performance
1739 of image write operations 2.5 times or more. Saying Y here creates a
1740 /proc/mtrr file which may be used to manipulate your processor's
1741 MTRRs. Typically the X server should use this.
1743 This code has a reasonably generic interface so that similar
1744 control registers on other processors can be easily supported
1747 The Cyrix 6x86, 6x86MX and M II processors have Address Range
1748 Registers (ARRs) which provide a similar functionality to MTRRs. For
1749 these, the ARRs are used to emulate the MTRRs.
1750 The AMD K6-2 (stepping 8 and above) and K6-3 processors have two
1751 MTRRs. The Centaur C6 (WinChip) has 8 MCRs, allowing
1752 write-combining. All of these processors are supported by this code
1753 and it makes sense to say Y here if you have one of them.
1755 Saying Y here also fixes a problem with buggy SMP BIOSes which only
1756 set the MTRRs for the boot CPU and not for the secondary CPUs. This
1757 can lead to all sorts of problems, so it's good to say Y here.
1759 You can safely say Y even if your machine doesn't have MTRRs, you'll
1760 just add about 9 KB to your kernel.
1762 See <file:Documentation/x86/mtrr.rst> for more information.
1764 config MTRR_SANITIZER
1766 prompt "MTRR cleanup support"
1769 Convert MTRR layout from continuous to discrete, so X drivers can
1770 add writeback entries.
1772 Can be disabled with disable_mtrr_cleanup on the kernel command line.
1773 The largest mtrr entry size for a continuous block can be set with
1778 config MTRR_SANITIZER_ENABLE_DEFAULT
1779 int "MTRR cleanup enable value (0-1)"
1782 depends on MTRR_SANITIZER
1784 Enable mtrr cleanup default value
1786 config MTRR_SANITIZER_SPARE_REG_NR_DEFAULT
1787 int "MTRR cleanup spare reg num (0-7)"
1790 depends on MTRR_SANITIZER
1792 mtrr cleanup spare entries default, it can be changed via
1793 mtrr_spare_reg_nr=N on the kernel command line.
1797 prompt "x86 PAT support" if EXPERT
1800 Use PAT attributes to setup page level cache control.
1802 PATs are the modern equivalents of MTRRs and are much more
1803 flexible than MTRRs.
1805 Say N here if you see bootup problems (boot crash, boot hang,
1806 spontaneous reboots) or a non-working video driver.
1810 config ARCH_USES_PG_UNCACHED
1816 prompt "x86 architectural random number generator" if EXPERT
1818 Enable the x86 architectural RDRAND instruction
1819 (Intel Bull Mountain technology) to generate random numbers.
1820 If supported, this is a high bandwidth, cryptographically
1821 secure hardware random number generator.
1825 prompt "Supervisor Mode Access Prevention" if EXPERT
1827 Supervisor Mode Access Prevention (SMAP) is a security
1828 feature in newer Intel processors. There is a small
1829 performance cost if this enabled and turned on; there is
1830 also a small increase in the kernel size if this is enabled.
1836 prompt "User Mode Instruction Prevention" if EXPERT
1838 User Mode Instruction Prevention (UMIP) is a security feature in
1839 some x86 processors. If enabled, a general protection fault is
1840 issued if the SGDT, SLDT, SIDT, SMSW or STR instructions are
1841 executed in user mode. These instructions unnecessarily expose
1842 information about the hardware state.
1844 The vast majority of applications do not use these instructions.
1845 For the very few that do, software emulation is provided in
1846 specific cases in protected and virtual-8086 modes. Emulated
1849 config X86_INTEL_MEMORY_PROTECTION_KEYS
1850 prompt "Memory Protection Keys"
1852 # Note: only available in 64-bit mode
1853 depends on X86_64 && (CPU_SUP_INTEL || CPU_SUP_AMD)
1854 select ARCH_USES_HIGH_VMA_FLAGS
1855 select ARCH_HAS_PKEYS
1857 Memory Protection Keys provides a mechanism for enforcing
1858 page-based protections, but without requiring modification of the
1859 page tables when an application changes protection domains.
1861 For details, see Documentation/core-api/protection-keys.rst
1866 prompt "TSX enable mode"
1867 depends on CPU_SUP_INTEL
1868 default X86_INTEL_TSX_MODE_OFF
1870 Intel's TSX (Transactional Synchronization Extensions) feature
1871 allows to optimize locking protocols through lock elision which
1872 can lead to a noticeable performance boost.
1874 On the other hand it has been shown that TSX can be exploited
1875 to form side channel attacks (e.g. TAA) and chances are there
1876 will be more of those attacks discovered in the future.
1878 Therefore TSX is not enabled by default (aka tsx=off). An admin
1879 might override this decision by tsx=on the command line parameter.
1880 Even with TSX enabled, the kernel will attempt to enable the best
1881 possible TAA mitigation setting depending on the microcode available
1882 for the particular machine.
1884 This option allows to set the default tsx mode between tsx=on, =off
1885 and =auto. See Documentation/admin-guide/kernel-parameters.txt for more
1888 Say off if not sure, auto if TSX is in use but it should be used on safe
1889 platforms or on if TSX is in use and the security aspect of tsx is not
1892 config X86_INTEL_TSX_MODE_OFF
1895 TSX is disabled if possible - equals to tsx=off command line parameter.
1897 config X86_INTEL_TSX_MODE_ON
1900 TSX is always enabled on TSX capable HW - equals the tsx=on command
1903 config X86_INTEL_TSX_MODE_AUTO
1906 TSX is enabled on TSX capable HW that is believed to be safe against
1907 side channel attacks- equals the tsx=auto command line parameter.
1911 bool "Software Guard eXtensions (SGX)"
1912 depends on X86_64 && CPU_SUP_INTEL
1914 depends on CRYPTO_SHA256=y
1917 select NUMA_KEEP_MEMINFO if NUMA
1920 Intel(R) Software Guard eXtensions (SGX) is a set of CPU instructions
1921 that can be used by applications to set aside private regions of code
1922 and data, referred to as enclaves. An enclave's private memory can
1923 only be accessed by code running within the enclave. Accesses from
1924 outside the enclave, including other enclaves, are disallowed by
1930 bool "EFI runtime service support"
1933 select EFI_RUNTIME_WRAPPERS
1934 select ARCH_USE_MEMREMAP_PROT
1936 This enables the kernel to use EFI runtime services that are
1937 available (such as the EFI variable services).
1939 This option is only useful on systems that have EFI firmware.
1940 In addition, you should use the latest ELILO loader available
1941 at <http://elilo.sourceforge.net> in order to take advantage
1942 of EFI runtime services. However, even with this option, the
1943 resultant kernel should continue to boot on existing non-EFI
1947 bool "EFI stub support"
1949 depends on $(cc-option,-mabi=ms) || X86_32
1952 This kernel feature allows a bzImage to be loaded directly
1953 by EFI firmware without the use of a bootloader.
1955 See Documentation/admin-guide/efi-stub.rst for more information.
1958 bool "EFI mixed-mode support"
1959 depends on EFI_STUB && X86_64
1961 Enabling this feature allows a 64-bit kernel to be booted
1962 on a 32-bit firmware, provided that your CPU supports 64-bit
1965 Note that it is not possible to boot a mixed-mode enabled
1966 kernel via the EFI boot stub - a bootloader that supports
1967 the EFI handover protocol must be used.
1971 source "kernel/Kconfig.hz"
1974 bool "kexec system call"
1977 kexec is a system call that implements the ability to shutdown your
1978 current kernel, and to start another kernel. It is like a reboot
1979 but it is independent of the system firmware. And like a reboot
1980 you can start any kernel with it, not just Linux.
1982 The name comes from the similarity to the exec system call.
1984 It is an ongoing process to be certain the hardware in a machine
1985 is properly shutdown, so do not be surprised if this code does not
1986 initially work for you. As of this writing the exact hardware
1987 interface is strongly in flux, so no good recommendation can be
1991 bool "kexec file based system call"
1996 depends on CRYPTO_SHA256=y
1998 This is new version of kexec system call. This system call is
1999 file based and takes file descriptors as system call argument
2000 for kernel and initramfs as opposed to list of segments as
2001 accepted by previous system call.
2003 config ARCH_HAS_KEXEC_PURGATORY
2007 bool "Verify kernel signature during kexec_file_load() syscall"
2008 depends on KEXEC_FILE
2011 This option makes the kexec_file_load() syscall check for a valid
2012 signature of the kernel image. The image can still be loaded without
2013 a valid signature unless you also enable KEXEC_SIG_FORCE, though if
2014 there's a signature that we can check, then it must be valid.
2016 In addition to this option, you need to enable signature
2017 verification for the corresponding kernel image type being
2018 loaded in order for this to work.
2020 config KEXEC_SIG_FORCE
2021 bool "Require a valid signature in kexec_file_load() syscall"
2022 depends on KEXEC_SIG
2024 This option makes kernel signature verification mandatory for
2025 the kexec_file_load() syscall.
2027 config KEXEC_BZIMAGE_VERIFY_SIG
2028 bool "Enable bzImage signature verification support"
2029 depends on KEXEC_SIG
2030 depends on SIGNED_PE_FILE_VERIFICATION
2031 select SYSTEM_TRUSTED_KEYRING
2033 Enable bzImage signature verification support.
2036 bool "kernel crash dumps"
2037 depends on X86_64 || (X86_32 && HIGHMEM)
2039 Generate crash dump after being started by kexec.
2040 This should be normally only set in special crash dump kernels
2041 which are loaded in the main kernel with kexec-tools into
2042 a specially reserved region and then later executed after
2043 a crash by kdump/kexec. The crash dump kernel must be compiled
2044 to a memory address not used by the main kernel or BIOS using
2045 PHYSICAL_START, or it must be built as a relocatable image
2046 (CONFIG_RELOCATABLE=y).
2047 For more details see Documentation/admin-guide/kdump/kdump.rst
2051 depends on KEXEC && HIBERNATION
2053 Jump between original kernel and kexeced kernel and invoke
2054 code in physical address mode via KEXEC
2056 config PHYSICAL_START
2057 hex "Physical address where the kernel is loaded" if (EXPERT || CRASH_DUMP)
2060 This gives the physical address where the kernel is loaded.
2062 If kernel is a not relocatable (CONFIG_RELOCATABLE=n) then
2063 bzImage will decompress itself to above physical address and
2064 run from there. Otherwise, bzImage will run from the address where
2065 it has been loaded by the boot loader and will ignore above physical
2068 In normal kdump cases one does not have to set/change this option
2069 as now bzImage can be compiled as a completely relocatable image
2070 (CONFIG_RELOCATABLE=y) and be used to load and run from a different
2071 address. This option is mainly useful for the folks who don't want
2072 to use a bzImage for capturing the crash dump and want to use a
2073 vmlinux instead. vmlinux is not relocatable hence a kernel needs
2074 to be specifically compiled to run from a specific memory area
2075 (normally a reserved region) and this option comes handy.
2077 So if you are using bzImage for capturing the crash dump,
2078 leave the value here unchanged to 0x1000000 and set
2079 CONFIG_RELOCATABLE=y. Otherwise if you plan to use vmlinux
2080 for capturing the crash dump change this value to start of
2081 the reserved region. In other words, it can be set based on
2082 the "X" value as specified in the "crashkernel=YM@XM"
2083 command line boot parameter passed to the panic-ed
2084 kernel. Please take a look at Documentation/admin-guide/kdump/kdump.rst
2085 for more details about crash dumps.
2087 Usage of bzImage for capturing the crash dump is recommended as
2088 one does not have to build two kernels. Same kernel can be used
2089 as production kernel and capture kernel. Above option should have
2090 gone away after relocatable bzImage support is introduced. But it
2091 is present because there are users out there who continue to use
2092 vmlinux for dump capture. This option should go away down the
2095 Don't change this unless you know what you are doing.
2098 bool "Build a relocatable kernel"
2101 This builds a kernel image that retains relocation information
2102 so it can be loaded someplace besides the default 1MB.
2103 The relocations tend to make the kernel binary about 10% larger,
2104 but are discarded at runtime.
2106 One use is for the kexec on panic case where the recovery kernel
2107 must live at a different physical address than the primary
2110 Note: If CONFIG_RELOCATABLE=y, then the kernel runs from the address
2111 it has been loaded at and the compile time physical address
2112 (CONFIG_PHYSICAL_START) is used as the minimum location.
2114 config RANDOMIZE_BASE
2115 bool "Randomize the address of the kernel image (KASLR)"
2116 depends on RELOCATABLE
2119 In support of Kernel Address Space Layout Randomization (KASLR),
2120 this randomizes the physical address at which the kernel image
2121 is decompressed and the virtual address where the kernel
2122 image is mapped, as a security feature that deters exploit
2123 attempts relying on knowledge of the location of kernel
2126 On 64-bit, the kernel physical and virtual addresses are
2127 randomized separately. The physical address will be anywhere
2128 between 16MB and the top of physical memory (up to 64TB). The
2129 virtual address will be randomized from 16MB up to 1GB (9 bits
2130 of entropy). Note that this also reduces the memory space
2131 available to kernel modules from 1.5GB to 1GB.
2133 On 32-bit, the kernel physical and virtual addresses are
2134 randomized together. They will be randomized from 16MB up to
2135 512MB (8 bits of entropy).
2137 Entropy is generated using the RDRAND instruction if it is
2138 supported. If RDTSC is supported, its value is mixed into
2139 the entropy pool as well. If neither RDRAND nor RDTSC are
2140 supported, then entropy is read from the i8254 timer. The
2141 usable entropy is limited by the kernel being built using
2142 2GB addressing, and that PHYSICAL_ALIGN must be at a
2143 minimum of 2MB. As a result, only 10 bits of entropy are
2144 theoretically possible, but the implementations are further
2145 limited due to memory layouts.
2149 # Relocation on x86 needs some additional build support
2150 config X86_NEED_RELOCS
2152 depends on RANDOMIZE_BASE || (X86_32 && RELOCATABLE)
2154 config PHYSICAL_ALIGN
2155 hex "Alignment value to which kernel should be aligned"
2157 range 0x2000 0x1000000 if X86_32
2158 range 0x200000 0x1000000 if X86_64
2160 This value puts the alignment restrictions on physical address
2161 where kernel is loaded and run from. Kernel is compiled for an
2162 address which meets above alignment restriction.
2164 If bootloader loads the kernel at a non-aligned address and
2165 CONFIG_RELOCATABLE is set, kernel will move itself to nearest
2166 address aligned to above value and run from there.
2168 If bootloader loads the kernel at a non-aligned address and
2169 CONFIG_RELOCATABLE is not set, kernel will ignore the run time
2170 load address and decompress itself to the address it has been
2171 compiled for and run from there. The address for which kernel is
2172 compiled already meets above alignment restrictions. Hence the
2173 end result is that kernel runs from a physical address meeting
2174 above alignment restrictions.
2176 On 32-bit this value must be a multiple of 0x2000. On 64-bit
2177 this value must be a multiple of 0x200000.
2179 Don't change this unless you know what you are doing.
2181 config DYNAMIC_MEMORY_LAYOUT
2184 This option makes base addresses of vmalloc and vmemmap as well as
2185 __PAGE_OFFSET movable during boot.
2187 config RANDOMIZE_MEMORY
2188 bool "Randomize the kernel memory sections"
2190 depends on RANDOMIZE_BASE
2191 select DYNAMIC_MEMORY_LAYOUT
2192 default RANDOMIZE_BASE
2194 Randomizes the base virtual address of kernel memory sections
2195 (physical memory mapping, vmalloc & vmemmap). This security feature
2196 makes exploits relying on predictable memory locations less reliable.
2198 The order of allocations remains unchanged. Entropy is generated in
2199 the same way as RANDOMIZE_BASE. Current implementation in the optimal
2200 configuration have in average 30,000 different possible virtual
2201 addresses for each memory section.
2205 config RANDOMIZE_MEMORY_PHYSICAL_PADDING
2206 hex "Physical memory mapping padding" if EXPERT
2207 depends on RANDOMIZE_MEMORY
2208 default "0xa" if MEMORY_HOTPLUG
2210 range 0x1 0x40 if MEMORY_HOTPLUG
2213 Define the padding in terabytes added to the existing physical
2214 memory size during kernel memory randomization. It is useful
2215 for memory hotplug support but reduces the entropy available for
2216 address randomization.
2218 If unsure, leave at the default value.
2224 config BOOTPARAM_HOTPLUG_CPU0
2225 bool "Set default setting of cpu0_hotpluggable"
2226 depends on HOTPLUG_CPU
2228 Set whether default state of cpu0_hotpluggable is on or off.
2230 Say Y here to enable CPU0 hotplug by default. If this switch
2231 is turned on, there is no need to give cpu0_hotplug kernel
2232 parameter and the CPU0 hotplug feature is enabled by default.
2234 Please note: there are two known CPU0 dependencies if you want
2235 to enable the CPU0 hotplug feature either by this switch or by
2236 cpu0_hotplug kernel parameter.
2238 First, resume from hibernate or suspend always starts from CPU0.
2239 So hibernate and suspend are prevented if CPU0 is offline.
2241 Second dependency is PIC interrupts always go to CPU0. CPU0 can not
2242 offline if any interrupt can not migrate out of CPU0. There may
2243 be other CPU0 dependencies.
2245 Please make sure the dependencies are under your control before
2246 you enable this feature.
2248 Say N if you don't want to enable CPU0 hotplug feature by default.
2249 You still can enable the CPU0 hotplug feature at boot by kernel
2250 parameter cpu0_hotplug.
2252 config DEBUG_HOTPLUG_CPU0
2254 prompt "Debug CPU0 hotplug"
2255 depends on HOTPLUG_CPU
2257 Enabling this option offlines CPU0 (if CPU0 can be offlined) as
2258 soon as possible and boots up userspace with CPU0 offlined. User
2259 can online CPU0 back after boot time.
2261 To debug CPU0 hotplug, you need to enable CPU0 offline/online
2262 feature by either turning on CONFIG_BOOTPARAM_HOTPLUG_CPU0 during
2263 compilation or giving cpu0_hotplug kernel parameter at boot.
2269 prompt "Disable the 32-bit vDSO (needed for glibc 2.3.3)"
2270 depends on COMPAT_32
2272 Certain buggy versions of glibc will crash if they are
2273 presented with a 32-bit vDSO that is not mapped at the address
2274 indicated in its segment table.
2276 The bug was introduced by f866314b89d56845f55e6f365e18b31ec978ec3a
2277 and fixed by 3b3ddb4f7db98ec9e912ccdf54d35df4aa30e04a and
2278 49ad572a70b8aeb91e57483a11dd1b77e31c4468. Glibc 2.3.3 is
2279 the only released version with the bug, but OpenSUSE 9
2280 contains a buggy "glibc 2.3.2".
2282 The symptom of the bug is that everything crashes on startup, saying:
2283 dl_main: Assertion `(void *) ph->p_vaddr == _rtld_local._dl_sysinfo_dso' failed!
2285 Saying Y here changes the default value of the vdso32 boot
2286 option from 1 to 0, which turns off the 32-bit vDSO entirely.
2287 This works around the glibc bug but hurts performance.
2289 If unsure, say N: if you are compiling your own kernel, you
2290 are unlikely to be using a buggy version of glibc.
2293 prompt "vsyscall table for legacy applications"
2295 default LEGACY_VSYSCALL_XONLY
2297 Legacy user code that does not know how to find the vDSO expects
2298 to be able to issue three syscalls by calling fixed addresses in
2299 kernel space. Since this location is not randomized with ASLR,
2300 it can be used to assist security vulnerability exploitation.
2302 This setting can be changed at boot time via the kernel command
2303 line parameter vsyscall=[emulate|xonly|none].
2305 On a system with recent enough glibc (2.14 or newer) and no
2306 static binaries, you can say None without a performance penalty
2307 to improve security.
2309 If unsure, select "Emulate execution only".
2311 config LEGACY_VSYSCALL_EMULATE
2312 bool "Full emulation"
2314 The kernel traps and emulates calls into the fixed vsyscall
2315 address mapping. This makes the mapping non-executable, but
2316 it still contains readable known contents, which could be
2317 used in certain rare security vulnerability exploits. This
2318 configuration is recommended when using legacy userspace
2319 that still uses vsyscalls along with legacy binary
2320 instrumentation tools that require code to be readable.
2322 An example of this type of legacy userspace is running
2323 Pin on an old binary that still uses vsyscalls.
2325 config LEGACY_VSYSCALL_XONLY
2326 bool "Emulate execution only"
2328 The kernel traps and emulates calls into the fixed vsyscall
2329 address mapping and does not allow reads. This
2330 configuration is recommended when userspace might use the
2331 legacy vsyscall area but support for legacy binary
2332 instrumentation of legacy code is not needed. It mitigates
2333 certain uses of the vsyscall area as an ASLR-bypassing
2336 config LEGACY_VSYSCALL_NONE
2339 There will be no vsyscall mapping at all. This will
2340 eliminate any risk of ASLR bypass due to the vsyscall
2341 fixed address mapping. Attempts to use the vsyscalls
2342 will be reported to dmesg, so that either old or
2343 malicious userspace programs can be identified.
2348 bool "Built-in kernel command line"
2350 Allow for specifying boot arguments to the kernel at
2351 build time. On some systems (e.g. embedded ones), it is
2352 necessary or convenient to provide some or all of the
2353 kernel boot arguments with the kernel itself (that is,
2354 to not rely on the boot loader to provide them.)
2356 To compile command line arguments into the kernel,
2357 set this option to 'Y', then fill in the
2358 boot arguments in CONFIG_CMDLINE.
2360 Systems with fully functional boot loaders (i.e. non-embedded)
2361 should leave this option set to 'N'.
2364 string "Built-in kernel command string"
2365 depends on CMDLINE_BOOL
2368 Enter arguments here that should be compiled into the kernel
2369 image and used at boot time. If the boot loader provides a
2370 command line at boot time, it is appended to this string to
2371 form the full kernel command line, when the system boots.
2373 However, you can use the CONFIG_CMDLINE_OVERRIDE option to
2374 change this behavior.
2376 In most cases, the command line (whether built-in or provided
2377 by the boot loader) should specify the device for the root
2380 config CMDLINE_OVERRIDE
2381 bool "Built-in command line overrides boot loader arguments"
2382 depends on CMDLINE_BOOL && CMDLINE != ""
2384 Set this option to 'Y' to have the kernel ignore the boot loader
2385 command line, and use ONLY the built-in command line.
2387 This is used to work around broken boot loaders. This should
2388 be set to 'N' under normal conditions.
2390 config MODIFY_LDT_SYSCALL
2391 bool "Enable the LDT (local descriptor table)" if EXPERT
2394 Linux can allow user programs to install a per-process x86
2395 Local Descriptor Table (LDT) using the modify_ldt(2) system
2396 call. This is required to run 16-bit or segmented code such as
2397 DOSEMU or some Wine programs. It is also used by some very old
2398 threading libraries.
2400 Enabling this feature adds a small amount of overhead to
2401 context switches and increases the low-level kernel attack
2402 surface. Disabling it removes the modify_ldt(2) system call.
2404 Saying 'N' here may make sense for embedded or server kernels.
2406 config STRICT_SIGALTSTACK_SIZE
2407 bool "Enforce strict size checking for sigaltstack"
2408 depends on DYNAMIC_SIGFRAME
2410 For historical reasons MINSIGSTKSZ is a constant which became
2411 already too small with AVX512 support. Add a mechanism to
2412 enforce strict checking of the sigaltstack size against the
2413 real size of the FPU frame. This option enables the check
2414 by default. It can also be controlled via the kernel command
2415 line option 'strict_sas_size' independent of this config
2416 switch. Enabling it might break existing applications which
2417 allocate a too small sigaltstack but 'work' because they
2418 never get a signal delivered.
2420 Say 'N' unless you want to really enforce this check.
2422 source "kernel/livepatch/Kconfig"
2426 config ARCH_HAS_ADD_PAGES
2428 depends on ARCH_ENABLE_MEMORY_HOTPLUG
2430 config ARCH_MHP_MEMMAP_ON_MEMORY_ENABLE
2433 menu "Power management and ACPI options"
2435 config ARCH_HIBERNATION_HEADER
2437 depends on HIBERNATION
2439 source "kernel/power/Kconfig"
2441 source "drivers/acpi/Kconfig"
2448 tristate "APM (Advanced Power Management) BIOS support"
2449 depends on X86_32 && PM_SLEEP
2451 APM is a BIOS specification for saving power using several different
2452 techniques. This is mostly useful for battery powered laptops with
2453 APM compliant BIOSes. If you say Y here, the system time will be
2454 reset after a RESUME operation, the /proc/apm device will provide
2455 battery status information, and user-space programs will receive
2456 notification of APM "events" (e.g. battery status change).
2458 If you select "Y" here, you can disable actual use of the APM
2459 BIOS by passing the "apm=off" option to the kernel at boot time.
2461 Note that the APM support is almost completely disabled for
2462 machines with more than one CPU.
2464 In order to use APM, you will need supporting software. For location
2465 and more information, read <file:Documentation/power/apm-acpi.rst>
2466 and the Battery Powered Linux mini-HOWTO, available from
2467 <http://www.tldp.org/docs.html#howto>.
2469 This driver does not spin down disk drives (see the hdparm(8)
2470 manpage ("man 8 hdparm") for that), and it doesn't turn off
2471 VESA-compliant "green" monitors.
2473 This driver does not support the TI 4000M TravelMate and the ACER
2474 486/DX4/75 because they don't have compliant BIOSes. Many "green"
2475 desktop machines also don't have compliant BIOSes, and this driver
2476 may cause those machines to panic during the boot phase.
2478 Generally, if you don't have a battery in your machine, there isn't
2479 much point in using this driver and you should say N. If you get
2480 random kernel OOPSes or reboots that don't seem to be related to
2481 anything, try disabling/enabling this option (or disabling/enabling
2484 Some other things you should try when experiencing seemingly random,
2487 1) make sure that you have enough swap space and that it is
2489 2) pass the "no-hlt" option to the kernel
2490 3) switch on floating point emulation in the kernel and pass
2491 the "no387" option to the kernel
2492 4) pass the "floppy=nodma" option to the kernel
2493 5) pass the "mem=4M" option to the kernel (thereby disabling
2494 all but the first 4 MB of RAM)
2495 6) make sure that the CPU is not over clocked.
2496 7) read the sig11 FAQ at <http://www.bitwizard.nl/sig11/>
2497 8) disable the cache from your BIOS settings
2498 9) install a fan for the video card or exchange video RAM
2499 10) install a better fan for the CPU
2500 11) exchange RAM chips
2501 12) exchange the motherboard.
2503 To compile this driver as a module, choose M here: the
2504 module will be called apm.
2508 config APM_IGNORE_USER_SUSPEND
2509 bool "Ignore USER SUSPEND"
2511 This option will ignore USER SUSPEND requests. On machines with a
2512 compliant APM BIOS, you want to say N. However, on the NEC Versa M
2513 series notebooks, it is necessary to say Y because of a BIOS bug.
2515 config APM_DO_ENABLE
2516 bool "Enable PM at boot time"
2518 Enable APM features at boot time. From page 36 of the APM BIOS
2519 specification: "When disabled, the APM BIOS does not automatically
2520 power manage devices, enter the Standby State, enter the Suspend
2521 State, or take power saving steps in response to CPU Idle calls."
2522 This driver will make CPU Idle calls when Linux is idle (unless this
2523 feature is turned off -- see "Do CPU IDLE calls", below). This
2524 should always save battery power, but more complicated APM features
2525 will be dependent on your BIOS implementation. You may need to turn
2526 this option off if your computer hangs at boot time when using APM
2527 support, or if it beeps continuously instead of suspending. Turn
2528 this off if you have a NEC UltraLite Versa 33/C or a Toshiba
2529 T400CDT. This is off by default since most machines do fine without
2534 bool "Make CPU Idle calls when idle"
2536 Enable calls to APM CPU Idle/CPU Busy inside the kernel's idle loop.
2537 On some machines, this can activate improved power savings, such as
2538 a slowed CPU clock rate, when the machine is idle. These idle calls
2539 are made after the idle loop has run for some length of time (e.g.,
2540 333 mS). On some machines, this will cause a hang at boot time or
2541 whenever the CPU becomes idle. (On machines with more than one CPU,
2542 this option does nothing.)
2544 config APM_DISPLAY_BLANK
2545 bool "Enable console blanking using APM"
2547 Enable console blanking using the APM. Some laptops can use this to
2548 turn off the LCD backlight when the screen blanker of the Linux
2549 virtual console blanks the screen. Note that this is only used by
2550 the virtual console screen blanker, and won't turn off the backlight
2551 when using the X Window system. This also doesn't have anything to
2552 do with your VESA-compliant power-saving monitor. Further, this
2553 option doesn't work for all laptops -- it might not turn off your
2554 backlight at all, or it might print a lot of errors to the console,
2555 especially if you are using gpm.
2557 config APM_ALLOW_INTS
2558 bool "Allow interrupts during APM BIOS calls"
2560 Normally we disable external interrupts while we are making calls to
2561 the APM BIOS as a measure to lessen the effects of a badly behaving
2562 BIOS implementation. The BIOS should reenable interrupts if it
2563 needs to. Unfortunately, some BIOSes do not -- especially those in
2564 many of the newer IBM Thinkpads. If you experience hangs when you
2565 suspend, try setting this to Y. Otherwise, say N.
2569 source "drivers/cpufreq/Kconfig"
2571 source "drivers/cpuidle/Kconfig"
2573 source "drivers/idle/Kconfig"
2578 menu "Bus options (PCI etc.)"
2581 prompt "PCI access mode"
2582 depends on X86_32 && PCI
2585 On PCI systems, the BIOS can be used to detect the PCI devices and
2586 determine their configuration. However, some old PCI motherboards
2587 have BIOS bugs and may crash if this is done. Also, some embedded
2588 PCI-based systems don't have any BIOS at all. Linux can also try to
2589 detect the PCI hardware directly without using the BIOS.
2591 With this option, you can specify how Linux should detect the
2592 PCI devices. If you choose "BIOS", the BIOS will be used,
2593 if you choose "Direct", the BIOS won't be used, and if you
2594 choose "MMConfig", then PCI Express MMCONFIG will be used.
2595 If you choose "Any", the kernel will try MMCONFIG, then the
2596 direct access method and falls back to the BIOS if that doesn't
2597 work. If unsure, go with the default, which is "Any".
2602 config PCI_GOMMCONFIG
2619 depends on X86_32 && PCI && (PCI_GOBIOS || PCI_GOANY)
2621 # x86-64 doesn't support PCI BIOS access from long mode so always go direct.
2624 depends on PCI && (X86_64 || (PCI_GODIRECT || PCI_GOANY || PCI_GOOLPC || PCI_GOMMCONFIG))
2627 bool "Support mmconfig PCI config space access" if X86_64
2629 depends on PCI && (ACPI || JAILHOUSE_GUEST)
2630 depends on X86_64 || (PCI_GOANY || PCI_GOMMCONFIG)
2634 depends on PCI && OLPC && (PCI_GOOLPC || PCI_GOANY)
2638 depends on PCI && XEN
2640 config MMCONF_FAM10H
2642 depends on X86_64 && PCI_MMCONFIG && ACPI
2644 config PCI_CNB20LE_QUIRK
2645 bool "Read CNB20LE Host Bridge Windows" if EXPERT
2648 Read the PCI windows out of the CNB20LE host bridge. This allows
2649 PCI hotplug to work on systems with the CNB20LE chipset which do
2652 There's no public spec for this chipset, and this functionality
2653 is known to be incomplete.
2655 You should say N unless you know you need this.
2658 bool "ISA bus support on modern systems" if EXPERT
2660 Expose ISA bus device drivers and options available for selection and
2661 configuration. Enable this option if your target machine has an ISA
2662 bus. ISA is an older system, displaced by PCI and newer bus
2663 architectures -- if your target machine is modern, it probably does
2664 not have an ISA bus.
2668 # x86_64 have no ISA slots, but can have ISA-style DMA.
2670 bool "ISA-style DMA support" if (X86_64 && EXPERT)
2673 Enables ISA-style DMA support for devices requiring such controllers.
2681 Find out whether you have ISA slots on your motherboard. ISA is the
2682 name of a bus system, i.e. the way the CPU talks to the other stuff
2683 inside your box. Other bus systems are PCI, EISA, MicroChannel
2684 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
2685 newer boards don't support it. If you have ISA, say Y, otherwise N.
2688 tristate "NatSemi SCx200 support"
2690 This provides basic support for National Semiconductor's
2691 (now AMD's) Geode processors. The driver probes for the
2692 PCI-IDs of several on-chip devices, so its a good dependency
2693 for other scx200_* drivers.
2695 If compiled as a module, the driver is named scx200.
2697 config SCx200HR_TIMER
2698 tristate "NatSemi SCx200 27MHz High-Resolution Timer Support"
2702 This driver provides a clocksource built upon the on-chip
2703 27MHz high-resolution timer. Its also a workaround for
2704 NSC Geode SC-1100's buggy TSC, which loses time when the
2705 processor goes idle (as is done by the scheduler). The
2706 other workaround is idle=poll boot option.
2709 bool "One Laptop Per Child support"
2717 Add support for detecting the unique features of the OLPC
2721 bool "OLPC XO-1 Power Management"
2722 depends on OLPC && MFD_CS5535=y && PM_SLEEP
2724 Add support for poweroff and suspend of the OLPC XO-1 laptop.
2727 bool "OLPC XO-1 Real Time Clock"
2728 depends on OLPC_XO1_PM && RTC_DRV_CMOS
2730 Add support for the XO-1 real time clock, which can be used as a
2731 programmable wakeup source.
2734 bool "OLPC XO-1 SCI extras"
2735 depends on OLPC && OLPC_XO1_PM && GPIO_CS5535=y
2739 Add support for SCI-based features of the OLPC XO-1 laptop:
2740 - EC-driven system wakeups
2744 - AC adapter status updates
2745 - Battery status updates
2747 config OLPC_XO15_SCI
2748 bool "OLPC XO-1.5 SCI extras"
2749 depends on OLPC && ACPI
2752 Add support for SCI-based features of the OLPC XO-1.5 laptop:
2753 - EC-driven system wakeups
2754 - AC adapter status updates
2755 - Battery status updates
2758 bool "PCEngines ALIX System Support (LED setup)"
2761 This option enables system support for the PCEngines ALIX.
2762 At present this just sets up LEDs for GPIO control on
2763 ALIX2/3/6 boards. However, other system specific setup should
2766 Note: You must still enable the drivers for GPIO and LED support
2767 (GPIO_CS5535 & LEDS_GPIO) to actually use the LEDs
2769 Note: You have to set alix.force=1 for boards with Award BIOS.
2772 bool "Soekris Engineering net5501 System Support (LEDS, GPIO, etc)"
2775 This option enables system support for the Soekris Engineering net5501.
2778 bool "Traverse Technologies GEOS System Support (LEDS, GPIO, etc)"
2782 This option enables system support for the Traverse Technologies GEOS.
2785 bool "Technologic Systems TS-5500 platform support"
2787 select CHECK_SIGNATURE
2791 This option enables system support for the Technologic Systems TS-5500.
2797 depends on CPU_SUP_AMD && PCI
2802 menu "Binary Emulations"
2804 config IA32_EMULATION
2805 bool "IA32 Emulation"
2807 select ARCH_WANT_OLD_COMPAT_IPC
2809 select COMPAT_OLD_SIGACTION
2811 Include code to run legacy 32-bit programs under a
2812 64-bit kernel. You should likely turn this on, unless you're
2813 100% sure that you don't have any 32-bit programs left.
2816 tristate "IA32 a.out support"
2817 depends on IA32_EMULATION
2820 Support old a.out binaries in the 32bit emulation.
2823 bool "x32 ABI for 64-bit mode"
2826 Include code to run binaries for the x32 native 32-bit ABI
2827 for 64-bit processors. An x32 process gets access to the
2828 full 64-bit register file and wide data path while leaving
2829 pointers at 32 bits for smaller memory footprint.
2831 You will need a recent binutils (2.22 or later) with
2832 elf32_x86_64 support enabled to compile a kernel with this
2837 depends on IA32_EMULATION || X86_32
2839 select OLD_SIGSUSPEND3
2843 depends on IA32_EMULATION || X86_X32
2846 config COMPAT_FOR_U64_ALIGNMENT
2849 config SYSVIPC_COMPAT
2857 config HAVE_ATOMIC_IOMAP
2861 source "arch/x86/kvm/Kconfig"
2863 source "arch/x86/Kconfig.assembler"