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_CONFIGURES_CPU_MITIGATIONS
65 select ARCH_CORRECT_STACKTRACE_ON_KRETPROBE
66 select ARCH_ENABLE_HUGEPAGE_MIGRATION if X86_64 && HUGETLB_PAGE && MIGRATION
67 select ARCH_ENABLE_MEMORY_HOTPLUG if X86_64
68 select ARCH_ENABLE_MEMORY_HOTREMOVE if MEMORY_HOTPLUG
69 select ARCH_ENABLE_SPLIT_PMD_PTLOCK if (PGTABLE_LEVELS > 2) && (X86_64 || X86_PAE)
70 select ARCH_ENABLE_THP_MIGRATION if X86_64 && TRANSPARENT_HUGEPAGE
71 select ARCH_HAS_ACPI_TABLE_UPGRADE if ACPI
72 select ARCH_HAS_CACHE_LINE_SIZE
73 select ARCH_HAS_CPU_FINALIZE_INIT
74 select ARCH_HAS_CURRENT_STACK_POINTER
75 select ARCH_HAS_DEBUG_VIRTUAL
76 select ARCH_HAS_DEBUG_VM_PGTABLE if !X86_PAE
77 select ARCH_HAS_DEVMEM_IS_ALLOWED
78 select ARCH_HAS_EARLY_DEBUG if KGDB
79 select ARCH_HAS_ELF_RANDOMIZE
80 select ARCH_HAS_FAST_MULTIPLIER
81 select ARCH_HAS_FORTIFY_SOURCE
82 select ARCH_HAS_GCOV_PROFILE_ALL
83 select ARCH_HAS_KCOV if X86_64
84 select ARCH_HAS_MEM_ENCRYPT
85 select ARCH_HAS_MEMBARRIER_SYNC_CORE
86 select ARCH_HAS_NON_OVERLAPPING_ADDRESS_SPACE
87 select ARCH_HAS_PMEM_API if X86_64
88 select ARCH_HAS_PTE_DEVMAP if X86_64
89 select ARCH_HAS_PTE_SPECIAL
90 select ARCH_HAS_NONLEAF_PMD_YOUNG if PGTABLE_LEVELS > 2
91 select ARCH_HAS_UACCESS_FLUSHCACHE if X86_64
92 select ARCH_HAS_COPY_MC if X86_64
93 select ARCH_HAS_SET_MEMORY
94 select ARCH_HAS_SET_DIRECT_MAP
95 select ARCH_HAS_STRICT_KERNEL_RWX
96 select ARCH_HAS_STRICT_MODULE_RWX
97 select ARCH_HAS_SYNC_CORE_BEFORE_USERMODE
98 select ARCH_HAS_SYSCALL_WRAPPER
99 select ARCH_HAS_UBSAN_SANITIZE_ALL
100 select ARCH_HAS_DEBUG_WX
101 select ARCH_HAS_ZONE_DMA_SET if EXPERT
102 select ARCH_HAVE_NMI_SAFE_CMPXCHG
103 select ARCH_MIGHT_HAVE_ACPI_PDC if ACPI
104 select ARCH_MIGHT_HAVE_PC_PARPORT
105 select ARCH_MIGHT_HAVE_PC_SERIO
106 select ARCH_STACKWALK
107 select ARCH_SUPPORTS_ACPI
108 select ARCH_SUPPORTS_ATOMIC_RMW
109 select ARCH_SUPPORTS_DEBUG_PAGEALLOC
110 select ARCH_SUPPORTS_PAGE_TABLE_CHECK if X86_64
111 select ARCH_SUPPORTS_NUMA_BALANCING if X86_64
112 select ARCH_SUPPORTS_KMAP_LOCAL_FORCE_MAP if NR_CPUS <= 4096
113 select ARCH_SUPPORTS_CFI_CLANG if X86_64
114 select ARCH_USES_CFI_TRAPS if X86_64 && CFI_CLANG
115 select ARCH_SUPPORTS_LTO_CLANG
116 select ARCH_SUPPORTS_LTO_CLANG_THIN
117 select ARCH_USE_BUILTIN_BSWAP
118 select ARCH_USE_MEMTEST
119 select ARCH_USE_QUEUED_RWLOCKS
120 select ARCH_USE_QUEUED_SPINLOCKS
121 select ARCH_USE_SYM_ANNOTATIONS
122 select ARCH_WANT_BATCHED_UNMAP_TLB_FLUSH
123 select ARCH_WANT_DEFAULT_BPF_JIT if X86_64
124 select ARCH_WANTS_DYNAMIC_TASK_STRUCT
125 select ARCH_WANTS_NO_INSTR
126 select ARCH_WANT_GENERAL_HUGETLB
127 select ARCH_WANT_HUGE_PMD_SHARE
128 select ARCH_WANT_HUGETLB_PAGE_OPTIMIZE_VMEMMAP if X86_64
129 select ARCH_WANT_LD_ORPHAN_WARN
130 select ARCH_WANTS_THP_SWAP if X86_64
131 select ARCH_HAS_PARANOID_L1D_FLUSH
132 select BUILDTIME_TABLE_SORT
134 select CLOCKSOURCE_VALIDATE_LAST_CYCLE
135 select CLOCKSOURCE_WATCHDOG
136 # Word-size accesses may read uninitialized data past the trailing \0
137 # in strings and cause false KMSAN reports.
138 select DCACHE_WORD_ACCESS if !KMSAN
139 select DYNAMIC_SIGFRAME
140 select EDAC_ATOMIC_SCRUB
142 select GENERIC_CLOCKEVENTS_BROADCAST if X86_64 || (X86_32 && X86_LOCAL_APIC)
143 select GENERIC_CLOCKEVENTS_MIN_ADJUST
144 select GENERIC_CMOS_UPDATE
145 select GENERIC_CPU_AUTOPROBE
146 select GENERIC_CPU_VULNERABILITIES
147 select GENERIC_EARLY_IOREMAP
150 select GENERIC_IRQ_EFFECTIVE_AFF_MASK if SMP
151 select GENERIC_IRQ_MATRIX_ALLOCATOR if X86_LOCAL_APIC
152 select GENERIC_IRQ_MIGRATION if SMP
153 select GENERIC_IRQ_PROBE
154 select GENERIC_IRQ_RESERVATION_MODE
155 select GENERIC_IRQ_SHOW
156 select GENERIC_PENDING_IRQ if SMP
157 select GENERIC_PTDUMP
158 select GENERIC_SMP_IDLE_THREAD
159 select GENERIC_TIME_VSYSCALL
160 select GENERIC_GETTIMEOFDAY
161 select GENERIC_VDSO_TIME_NS
162 select GUP_GET_PTE_LOW_HIGH if X86_PAE
163 select HARDIRQS_SW_RESEND
164 select HARDLOCKUP_CHECK_TIMESTAMP if X86_64
165 select HAVE_ACPI_APEI if ACPI
166 select HAVE_ACPI_APEI_NMI if ACPI
167 select HAVE_ALIGNED_STRUCT_PAGE if SLUB
168 select HAVE_ARCH_AUDITSYSCALL
169 select HAVE_ARCH_HUGE_VMAP if X86_64 || X86_PAE
170 select HAVE_ARCH_HUGE_VMALLOC if X86_64
171 select HAVE_ARCH_JUMP_LABEL
172 select HAVE_ARCH_JUMP_LABEL_RELATIVE
173 select HAVE_ARCH_KASAN if X86_64
174 select HAVE_ARCH_KASAN_VMALLOC if X86_64
175 select HAVE_ARCH_KFENCE
176 select HAVE_ARCH_KMSAN if X86_64
177 select HAVE_ARCH_KGDB
178 select HAVE_ARCH_MMAP_RND_BITS if MMU
179 select HAVE_ARCH_MMAP_RND_COMPAT_BITS if MMU && COMPAT
180 select HAVE_ARCH_COMPAT_MMAP_BASES if MMU && COMPAT
181 select HAVE_ARCH_PREL32_RELOCATIONS
182 select HAVE_ARCH_SECCOMP_FILTER
183 select HAVE_ARCH_THREAD_STRUCT_WHITELIST
184 select HAVE_ARCH_STACKLEAK
185 select HAVE_ARCH_TRACEHOOK
186 select HAVE_ARCH_TRANSPARENT_HUGEPAGE
187 select HAVE_ARCH_TRANSPARENT_HUGEPAGE_PUD if X86_64
188 select HAVE_ARCH_USERFAULTFD_WP if X86_64 && USERFAULTFD
189 select HAVE_ARCH_USERFAULTFD_MINOR if X86_64 && USERFAULTFD
190 select HAVE_ARCH_VMAP_STACK if X86_64
191 select HAVE_ARCH_RANDOMIZE_KSTACK_OFFSET
192 select HAVE_ARCH_WITHIN_STACK_FRAMES
193 select HAVE_ASM_MODVERSIONS
194 select HAVE_CMPXCHG_DOUBLE
195 select HAVE_CMPXCHG_LOCAL
196 select HAVE_CONTEXT_TRACKING_USER if X86_64
197 select HAVE_CONTEXT_TRACKING_USER_OFFSTACK if HAVE_CONTEXT_TRACKING_USER
198 select HAVE_C_RECORDMCOUNT
199 select HAVE_OBJTOOL_MCOUNT if HAVE_OBJTOOL
200 select HAVE_BUILDTIME_MCOUNT_SORT
201 select HAVE_DEBUG_KMEMLEAK
202 select HAVE_DMA_CONTIGUOUS
203 select HAVE_DYNAMIC_FTRACE
204 select HAVE_DYNAMIC_FTRACE_WITH_REGS
205 select HAVE_DYNAMIC_FTRACE_WITH_ARGS if X86_64
206 select HAVE_DYNAMIC_FTRACE_WITH_DIRECT_CALLS
207 select HAVE_SAMPLE_FTRACE_DIRECT if X86_64
208 select HAVE_SAMPLE_FTRACE_DIRECT_MULTI if X86_64
210 select HAVE_EFFICIENT_UNALIGNED_ACCESS
212 select HAVE_EXIT_THREAD
214 select HAVE_FENTRY if X86_64 || DYNAMIC_FTRACE
215 select HAVE_FTRACE_MCOUNT_RECORD
216 select HAVE_FUNCTION_GRAPH_TRACER if X86_32 || (X86_64 && DYNAMIC_FTRACE)
217 select HAVE_FUNCTION_TRACER
218 select HAVE_GCC_PLUGINS
219 select HAVE_HW_BREAKPOINT
220 select HAVE_IOREMAP_PROT
221 select HAVE_IRQ_EXIT_ON_IRQ_STACK if X86_64
222 select HAVE_IRQ_TIME_ACCOUNTING
223 select HAVE_JUMP_LABEL_HACK if HAVE_OBJTOOL
224 select HAVE_KERNEL_BZIP2
225 select HAVE_KERNEL_GZIP
226 select HAVE_KERNEL_LZ4
227 select HAVE_KERNEL_LZMA
228 select HAVE_KERNEL_LZO
229 select HAVE_KERNEL_XZ
230 select HAVE_KERNEL_ZSTD
232 select HAVE_KPROBES_ON_FTRACE
233 select HAVE_FUNCTION_ERROR_INJECTION
234 select HAVE_KRETPROBES
237 select HAVE_LIVEPATCH if X86_64
238 select HAVE_MIXED_BREAKPOINTS_REGS
239 select HAVE_MOD_ARCH_SPECIFIC
242 select HAVE_NOINSTR_HACK if HAVE_OBJTOOL
244 select HAVE_NOINSTR_VALIDATION if HAVE_OBJTOOL
245 select HAVE_OBJTOOL if X86_64
246 select HAVE_OPTPROBES
247 select HAVE_PCSPKR_PLATFORM
248 select HAVE_PERF_EVENTS
249 select HAVE_PERF_EVENTS_NMI
250 select HAVE_HARDLOCKUP_DETECTOR_PERF if PERF_EVENTS && HAVE_PERF_EVENTS_NMI
252 select HAVE_PERF_REGS
253 select HAVE_PERF_USER_STACK_DUMP
254 select MMU_GATHER_RCU_TABLE_FREE if PARAVIRT
255 select MMU_GATHER_MERGE_VMAS
256 select HAVE_POSIX_CPU_TIMERS_TASK_WORK
257 select HAVE_REGS_AND_STACK_ACCESS_API
258 select HAVE_RELIABLE_STACKTRACE if UNWINDER_ORC || STACK_VALIDATION
259 select HAVE_FUNCTION_ARG_ACCESS_API
260 select HAVE_SETUP_PER_CPU_AREA
261 select HAVE_SOFTIRQ_ON_OWN_STACK
262 select HAVE_STACKPROTECTOR if CC_HAS_SANE_STACKPROTECTOR
263 select HAVE_STACK_VALIDATION if HAVE_OBJTOOL
264 select HAVE_STATIC_CALL
265 select HAVE_STATIC_CALL_INLINE if HAVE_OBJTOOL
266 select HAVE_PREEMPT_DYNAMIC_CALL
268 select HAVE_RUST if X86_64
269 select HAVE_SYSCALL_TRACEPOINTS
270 select HAVE_UACCESS_VALIDATION if HAVE_OBJTOOL
271 select HAVE_UNSTABLE_SCHED_CLOCK
272 select HAVE_USER_RETURN_NOTIFIER
273 select HAVE_GENERIC_VDSO
274 select HOTPLUG_SMT if SMP
275 select IRQ_FORCED_THREADING
276 select LOCK_MM_AND_FIND_VMA
277 select NEED_PER_CPU_EMBED_FIRST_CHUNK
278 select NEED_PER_CPU_PAGE_FIRST_CHUNK
279 select NEED_SG_DMA_LENGTH
280 select PCI_DOMAINS if PCI
281 select PCI_LOCKLESS_CONFIG if PCI
284 select RTC_MC146818_LIB
287 select SYSCTL_EXCEPTION_TRACE
288 select THREAD_INFO_IN_TASK
289 select TRACE_IRQFLAGS_SUPPORT
290 select TRACE_IRQFLAGS_NMI_SUPPORT
291 select USER_STACKTRACE_SUPPORT
292 select HAVE_ARCH_KCSAN if X86_64
293 select X86_FEATURE_NAMES if PROC_FS
294 select PROC_PID_ARCH_STATUS if PROC_FS
295 select HAVE_ARCH_NODE_DEV_GROUP if X86_SGX
296 imply IMA_SECURE_AND_OR_TRUSTED_BOOT if EFI
297 select HAVE_DYNAMIC_FTRACE_NO_PATCHABLE
299 config INSTRUCTION_DECODER
301 depends on KPROBES || PERF_EVENTS || UPROBES
305 default "elf32-i386" if X86_32
306 default "elf64-x86-64" if X86_64
308 config LOCKDEP_SUPPORT
311 config STACKTRACE_SUPPORT
317 config ARCH_MMAP_RND_BITS_MIN
321 config ARCH_MMAP_RND_BITS_MAX
325 config ARCH_MMAP_RND_COMPAT_BITS_MIN
328 config ARCH_MMAP_RND_COMPAT_BITS_MAX
334 config GENERIC_ISA_DMA
336 depends on ISA_DMA_API
340 default y if KMSAN || KASAN
345 select GENERIC_BUG_RELATIVE_POINTERS if X86_64
347 config GENERIC_BUG_RELATIVE_POINTERS
350 config ARCH_MAY_HAVE_PC_FDC
352 depends on ISA_DMA_API
354 config GENERIC_CALIBRATE_DELAY
357 config ARCH_HAS_CPU_RELAX
360 config ARCH_HIBERNATION_POSSIBLE
365 default 1024 if X86_64
368 config ARCH_SUSPEND_POSSIBLE
374 config KASAN_SHADOW_OFFSET
377 default 0xdffffc0000000000
379 config HAVE_INTEL_TXT
381 depends on INTEL_IOMMU && ACPI
385 depends on X86_32 && SMP
389 depends on X86_64 && SMP
391 config ARCH_SUPPORTS_UPROBES
394 config FIX_EARLYCON_MEM
397 config DYNAMIC_PHYSICAL_MASK
400 config PGTABLE_LEVELS
402 default 5 if X86_5LEVEL
407 config CC_HAS_SANE_STACKPROTECTOR
409 default $(success,$(srctree)/scripts/gcc-x86_64-has-stack-protector.sh $(CC) $(CLANG_FLAGS)) if 64BIT
410 default $(success,$(srctree)/scripts/gcc-x86_32-has-stack-protector.sh $(CC) $(CLANG_FLAGS))
412 We have to make sure stack protector is unconditionally disabled if
413 the compiler produces broken code or if it does not let us control
414 the segment on 32-bit kernels.
416 menu "Processor type and features"
419 bool "Symmetric multi-processing support"
421 This enables support for systems with more than one CPU. If you have
422 a system with only one CPU, say N. If you have a system with more
425 If you say N here, the kernel will run on uni- and multiprocessor
426 machines, but will use only one CPU of a multiprocessor machine. If
427 you say Y here, the kernel will run on many, but not all,
428 uniprocessor machines. On a uniprocessor machine, the kernel
429 will run faster if you say N here.
431 Note that if you say Y here and choose architecture "586" or
432 "Pentium" under "Processor family", the kernel will not work on 486
433 architectures. Similarly, multiprocessor kernels for the "PPro"
434 architecture may not work on all Pentium based boards.
436 People using multiprocessor machines who say Y here should also say
437 Y to "Enhanced Real Time Clock Support", below. The "Advanced Power
438 Management" code will be disabled if you say Y here.
440 See also <file:Documentation/x86/i386/IO-APIC.rst>,
441 <file:Documentation/admin-guide/lockup-watchdogs.rst> and the SMP-HOWTO available at
442 <http://www.tldp.org/docs.html#howto>.
444 If you don't know what to do here, say N.
446 config X86_FEATURE_NAMES
447 bool "Processor feature human-readable names" if EMBEDDED
450 This option compiles in a table of x86 feature bits and corresponding
451 names. This is required to support /proc/cpuinfo and a few kernel
452 messages. You can disable this to save space, at the expense of
453 making those few kernel messages show numeric feature bits instead.
458 bool "Support x2apic"
459 depends on X86_LOCAL_APIC && X86_64 && (IRQ_REMAP || HYPERVISOR_GUEST)
461 This enables x2apic support on CPUs that have this feature.
463 This allows 32-bit apic IDs (so it can support very large systems),
464 and accesses the local apic via MSRs not via mmio.
466 Some Intel systems circa 2022 and later are locked into x2APIC mode
467 and can not fall back to the legacy APIC modes if SGX or TDX are
468 enabled in the BIOS. They will boot with very reduced functionality
469 without enabling this option.
471 If you don't know what to do here, say N.
474 bool "Enable MPS table" if ACPI
476 depends on X86_LOCAL_APIC
478 For old smp systems that do not have proper acpi support. Newer systems
479 (esp with 64bit cpus) with acpi support, MADT and DSDT will override it
483 depends on X86_GOLDFISH
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 config INTEL_TDX_GUEST
886 bool "Intel TDX (Trust Domain Extensions) - Guest Support"
887 depends on X86_64 && CPU_SUP_INTEL
888 depends on X86_X2APIC
889 select ARCH_HAS_CC_PLATFORM
890 select X86_MEM_ENCRYPT
893 Support running as a guest under Intel TDX. Without this support,
894 the guest kernel can not boot or run under TDX.
895 TDX includes memory encryption and integrity capabilities
896 which protect the confidentiality and integrity of guest
897 memory contents and CPU state. TDX guests are protected from
898 some attacks from the VMM.
900 endif # HYPERVISOR_GUEST
902 source "arch/x86/Kconfig.cpu"
906 prompt "HPET Timer Support" if X86_32
908 Use the IA-PC HPET (High Precision Event Timer) to manage
909 time in preference to the PIT and RTC, if a HPET is
911 HPET is the next generation timer replacing legacy 8254s.
912 The HPET provides a stable time base on SMP
913 systems, unlike the TSC, but it is more expensive to access,
914 as it is off-chip. The interface used is documented
915 in the HPET spec, revision 1.
917 You can safely choose Y here. However, HPET will only be
918 activated if the platform and the BIOS support this feature.
919 Otherwise the 8254 will be used for timing services.
921 Choose N to continue using the legacy 8254 timer.
923 config HPET_EMULATE_RTC
925 depends on HPET_TIMER && (RTC_DRV_CMOS=m || RTC_DRV_CMOS=y)
927 # Mark as expert because too many people got it wrong.
928 # The code disables itself when not needed.
931 select DMI_SCAN_MACHINE_NON_EFI_FALLBACK
932 bool "Enable DMI scanning" if EXPERT
934 Enabled scanning of DMI to identify machine quirks. Say Y
935 here unless you have verified that your setup is not
936 affected by entries in the DMI blacklist. Required by PNP
940 bool "Old AMD GART IOMMU support"
944 depends on X86_64 && PCI && AMD_NB
946 Provides a driver for older AMD Athlon64/Opteron/Turion/Sempron
947 GART based hardware IOMMUs.
949 The GART supports full DMA access for devices with 32-bit access
950 limitations, on systems with more than 3 GB. This is usually needed
951 for USB, sound, many IDE/SATA chipsets and some other devices.
953 Newer systems typically have a modern AMD IOMMU, supported via
954 the CONFIG_AMD_IOMMU=y config option.
956 In normal configurations this driver is only active when needed:
957 there's more than 3 GB of memory and the system contains a
958 32-bit limited device.
962 config BOOT_VESA_SUPPORT
965 If true, at least one selected framebuffer driver can take advantage
966 of VESA video modes set at an early boot stage via the vga= parameter.
969 bool "Enable Maximum number of SMP Processors and NUMA Nodes"
970 depends on X86_64 && SMP && DEBUG_KERNEL
971 select CPUMASK_OFFSTACK
973 Enable maximum number of CPUS and NUMA Nodes for this architecture.
977 # The maximum number of CPUs supported:
979 # The main config value is NR_CPUS, which defaults to NR_CPUS_DEFAULT,
980 # and which can be configured interactively in the
981 # [NR_CPUS_RANGE_BEGIN ... NR_CPUS_RANGE_END] range.
983 # The ranges are different on 32-bit and 64-bit kernels, depending on
984 # hardware capabilities and scalability features of the kernel.
986 # ( If MAXSMP is enabled we just use the highest possible value and disable
987 # interactive configuration. )
990 config NR_CPUS_RANGE_BEGIN
992 default NR_CPUS_RANGE_END if MAXSMP
996 config NR_CPUS_RANGE_END
999 default 64 if SMP && X86_BIGSMP
1000 default 8 if SMP && !X86_BIGSMP
1003 config NR_CPUS_RANGE_END
1006 default 8192 if SMP && CPUMASK_OFFSTACK
1007 default 512 if SMP && !CPUMASK_OFFSTACK
1010 config NR_CPUS_DEFAULT
1013 default 32 if X86_BIGSMP
1017 config NR_CPUS_DEFAULT
1020 default 8192 if MAXSMP
1025 int "Maximum number of CPUs" if SMP && !MAXSMP
1026 range NR_CPUS_RANGE_BEGIN NR_CPUS_RANGE_END
1027 default NR_CPUS_DEFAULT
1029 This allows you to specify the maximum number of CPUs which this
1030 kernel will support. If CPUMASK_OFFSTACK is enabled, the maximum
1031 supported value is 8192, otherwise the maximum value is 512. The
1032 minimum value which makes sense is 2.
1034 This is purely to save memory: each supported CPU adds about 8KB
1035 to the kernel image.
1037 config SCHED_CLUSTER
1038 bool "Cluster scheduler support"
1042 Cluster scheduler support improves the CPU scheduler's decision
1043 making when dealing with machines that have clusters of CPUs.
1044 Cluster usually means a couple of CPUs which are placed closely
1045 by sharing mid-level caches, last-level cache tags or internal
1053 prompt "Multi-core scheduler support"
1056 Multi-core scheduler support improves the CPU scheduler's decision
1057 making when dealing with multi-core CPU chips at a cost of slightly
1058 increased overhead in some places. If unsure say N here.
1060 config SCHED_MC_PRIO
1061 bool "CPU core priorities scheduler support"
1062 depends on SCHED_MC && CPU_SUP_INTEL
1063 select X86_INTEL_PSTATE
1067 Intel Turbo Boost Max Technology 3.0 enabled CPUs have a
1068 core ordering determined at manufacturing time, which allows
1069 certain cores to reach higher turbo frequencies (when running
1070 single threaded workloads) than others.
1072 Enabling this kernel feature teaches the scheduler about
1073 the TBM3 (aka ITMT) priority order of the CPU cores and adjusts the
1074 scheduler's CPU selection logic accordingly, so that higher
1075 overall system performance can be achieved.
1077 This feature will have no effect on CPUs without this feature.
1079 If unsure say Y here.
1083 depends on !SMP && X86_LOCAL_APIC
1086 bool "Local APIC support on uniprocessors" if !PCI_MSI
1088 depends on X86_32 && !SMP && !X86_32_NON_STANDARD
1090 A local APIC (Advanced Programmable Interrupt Controller) is an
1091 integrated interrupt controller in the CPU. If you have a single-CPU
1092 system which has a processor with a local APIC, you can say Y here to
1093 enable and use it. If you say Y here even though your machine doesn't
1094 have a local APIC, then the kernel will still run with no slowdown at
1095 all. The local APIC supports CPU-generated self-interrupts (timer,
1096 performance counters), and the NMI watchdog which detects hard
1099 config X86_UP_IOAPIC
1100 bool "IO-APIC support on uniprocessors"
1101 depends on X86_UP_APIC
1103 An IO-APIC (I/O Advanced Programmable Interrupt Controller) is an
1104 SMP-capable replacement for PC-style interrupt controllers. Most
1105 SMP systems and many recent uniprocessor systems have one.
1107 If you have a single-CPU system with an IO-APIC, you can say Y here
1108 to use it. If you say Y here even though your machine doesn't have
1109 an IO-APIC, then the kernel will still run with no slowdown at all.
1111 config X86_LOCAL_APIC
1113 depends on X86_64 || SMP || X86_32_NON_STANDARD || X86_UP_APIC || PCI_MSI
1114 select IRQ_DOMAIN_HIERARCHY
1115 select PCI_MSI_IRQ_DOMAIN if PCI_MSI
1119 depends on X86_LOCAL_APIC || X86_UP_IOAPIC
1121 config X86_REROUTE_FOR_BROKEN_BOOT_IRQS
1122 bool "Reroute for broken boot IRQs"
1123 depends on X86_IO_APIC
1125 This option enables a workaround that fixes a source of
1126 spurious interrupts. This is recommended when threaded
1127 interrupt handling is used on systems where the generation of
1128 superfluous "boot interrupts" cannot be disabled.
1130 Some chipsets generate a legacy INTx "boot IRQ" when the IRQ
1131 entry in the chipset's IO-APIC is masked (as, e.g. the RT
1132 kernel does during interrupt handling). On chipsets where this
1133 boot IRQ generation cannot be disabled, this workaround keeps
1134 the original IRQ line masked so that only the equivalent "boot
1135 IRQ" is delivered to the CPUs. The workaround also tells the
1136 kernel to set up the IRQ handler on the boot IRQ line. In this
1137 way only one interrupt is delivered to the kernel. Otherwise
1138 the spurious second interrupt may cause the kernel to bring
1139 down (vital) interrupt lines.
1141 Only affects "broken" chipsets. Interrupt sharing may be
1142 increased on these systems.
1145 bool "Machine Check / overheating reporting"
1146 select GENERIC_ALLOCATOR
1149 Machine Check support allows the processor to notify the
1150 kernel if it detects a problem (e.g. overheating, data corruption).
1151 The action the kernel takes depends on the severity of the problem,
1152 ranging from warning messages to halting the machine.
1154 config X86_MCELOG_LEGACY
1155 bool "Support for deprecated /dev/mcelog character device"
1158 Enable support for /dev/mcelog which is needed by the old mcelog
1159 userspace logging daemon. Consider switching to the new generation
1162 config X86_MCE_INTEL
1164 prompt "Intel MCE features"
1165 depends on X86_MCE && X86_LOCAL_APIC
1167 Additional support for intel specific MCE features such as
1168 the thermal monitor.
1172 prompt "AMD MCE features"
1173 depends on X86_MCE && X86_LOCAL_APIC && AMD_NB
1175 Additional support for AMD specific MCE features such as
1176 the DRAM Error Threshold.
1178 config X86_ANCIENT_MCE
1179 bool "Support for old Pentium 5 / WinChip machine checks"
1180 depends on X86_32 && X86_MCE
1182 Include support for machine check handling on old Pentium 5 or WinChip
1183 systems. These typically need to be enabled explicitly on the command
1186 config X86_MCE_THRESHOLD
1187 depends on X86_MCE_AMD || X86_MCE_INTEL
1190 config X86_MCE_INJECT
1191 depends on X86_MCE && X86_LOCAL_APIC && DEBUG_FS
1192 tristate "Machine check injector support"
1194 Provide support for injecting machine checks for testing purposes.
1195 If you don't know what a machine check is and you don't do kernel
1196 QA it is safe to say n.
1198 source "arch/x86/events/Kconfig"
1200 config X86_LEGACY_VM86
1201 bool "Legacy VM86 support"
1204 This option allows user programs to put the CPU into V8086
1205 mode, which is an 80286-era approximation of 16-bit real mode.
1207 Some very old versions of X and/or vbetool require this option
1208 for user mode setting. Similarly, DOSEMU will use it if
1209 available to accelerate real mode DOS programs. However, any
1210 recent version of DOSEMU, X, or vbetool should be fully
1211 functional even without kernel VM86 support, as they will all
1212 fall back to software emulation. Nevertheless, if you are using
1213 a 16-bit DOS program where 16-bit performance matters, vm86
1214 mode might be faster than emulation and you might want to
1217 Note that any app that works on a 64-bit kernel is unlikely to
1218 need this option, as 64-bit kernels don't, and can't, support
1219 V8086 mode. This option is also unrelated to 16-bit protected
1220 mode and is not needed to run most 16-bit programs under Wine.
1222 Enabling this option increases the complexity of the kernel
1223 and slows down exception handling a tiny bit.
1225 If unsure, say N here.
1229 default X86_LEGACY_VM86
1232 bool "Enable support for 16-bit segments" if EXPERT
1234 depends on MODIFY_LDT_SYSCALL
1236 This option is required by programs like Wine to run 16-bit
1237 protected mode legacy code on x86 processors. Disabling
1238 this option saves about 300 bytes on i386, or around 6K text
1239 plus 16K runtime memory on x86-64,
1243 depends on X86_16BIT && X86_32
1247 depends on X86_16BIT && X86_64
1249 config X86_VSYSCALL_EMULATION
1250 bool "Enable vsyscall emulation" if EXPERT
1254 This enables emulation of the legacy vsyscall page. Disabling
1255 it is roughly equivalent to booting with vsyscall=none, except
1256 that it will also disable the helpful warning if a program
1257 tries to use a vsyscall. With this option set to N, offending
1258 programs will just segfault, citing addresses of the form
1261 This option is required by many programs built before 2013, and
1262 care should be used even with newer programs if set to N.
1264 Disabling this option saves about 7K of kernel size and
1265 possibly 4K of additional runtime pagetable memory.
1267 config X86_IOPL_IOPERM
1268 bool "IOPERM and IOPL Emulation"
1271 This enables the ioperm() and iopl() syscalls which are necessary
1272 for legacy applications.
1274 Legacy IOPL support is an overbroad mechanism which allows user
1275 space aside of accessing all 65536 I/O ports also to disable
1276 interrupts. To gain this access the caller needs CAP_SYS_RAWIO
1277 capabilities and permission from potentially active security
1280 The emulation restricts the functionality of the syscall to
1281 only allowing the full range I/O port access, but prevents the
1282 ability to disable interrupts from user space which would be
1283 granted if the hardware IOPL mechanism would be used.
1286 tristate "Toshiba Laptop support"
1289 This adds a driver to safely access the System Management Mode of
1290 the CPU on Toshiba portables with a genuine Toshiba BIOS. It does
1291 not work on models with a Phoenix BIOS. The System Management Mode
1292 is used to set the BIOS and power saving options on Toshiba portables.
1294 For information on utilities to make use of this driver see the
1295 Toshiba Linux utilities web site at:
1296 <http://www.buzzard.org.uk/toshiba/>.
1298 Say Y if you intend to run this kernel on a Toshiba portable.
1301 config X86_REBOOTFIXUPS
1302 bool "Enable X86 board specific fixups for reboot"
1305 This enables chipset and/or board specific fixups to be done
1306 in order to get reboot to work correctly. This is only needed on
1307 some combinations of hardware and BIOS. The symptom, for which
1308 this config is intended, is when reboot ends with a stalled/hung
1311 Currently, the only fixup is for the Geode machines using
1312 CS5530A and CS5536 chipsets and the RDC R-321x SoC.
1314 Say Y if you want to enable the fixup. Currently, it's safe to
1315 enable this option even if you don't need it.
1319 bool "CPU microcode loading support"
1321 depends on CPU_SUP_AMD || CPU_SUP_INTEL
1323 If you say Y here, you will be able to update the microcode on
1324 Intel and AMD processors. The Intel support is for the IA32 family,
1325 e.g. Pentium Pro, Pentium II, Pentium III, Pentium 4, Xeon etc. The
1326 AMD support is for families 0x10 and later. You will obviously need
1327 the actual microcode binary data itself which is not shipped with
1330 The preferred method to load microcode from a detached initrd is described
1331 in Documentation/x86/microcode.rst. For that you need to enable
1332 CONFIG_BLK_DEV_INITRD in order for the loader to be able to scan the
1333 initrd for microcode blobs.
1335 In addition, you can build the microcode into the kernel. For that you
1336 need to add the vendor-supplied microcode to the CONFIG_EXTRA_FIRMWARE
1339 config MICROCODE_INTEL
1340 bool "Intel microcode loading support"
1341 depends on CPU_SUP_INTEL && MICROCODE
1344 This options enables microcode patch loading support for Intel
1347 For the current Intel microcode data package go to
1348 <https://downloadcenter.intel.com> and search for
1349 'Linux Processor Microcode Data File'.
1351 config MICROCODE_AMD
1352 bool "AMD microcode loading support"
1353 depends on CPU_SUP_AMD && MICROCODE
1355 If you select this option, microcode patch loading support for AMD
1356 processors will be enabled.
1358 config MICROCODE_LATE_LOADING
1359 bool "Late microcode loading (DANGEROUS)"
1361 depends on MICROCODE
1363 Loading microcode late, when the system is up and executing instructions
1364 is a tricky business and should be avoided if possible. Just the sequence
1365 of synchronizing all cores and SMT threads is one fragile dance which does
1366 not guarantee that cores might not softlock after the loading. Therefore,
1367 use this at your own risk. Late loading taints the kernel too.
1370 tristate "/dev/cpu/*/msr - Model-specific register support"
1372 This device gives privileged processes access to the x86
1373 Model-Specific Registers (MSRs). It is a character device with
1374 major 202 and minors 0 to 31 for /dev/cpu/0/msr to /dev/cpu/31/msr.
1375 MSR accesses are directed to a specific CPU on multi-processor
1379 tristate "/dev/cpu/*/cpuid - CPU information support"
1381 This device gives processes access to the x86 CPUID instruction to
1382 be executed on a specific processor. It is a character device
1383 with major 203 and minors 0 to 31 for /dev/cpu/0/cpuid to
1387 prompt "High Memory Support"
1394 Linux can use up to 64 Gigabytes of physical memory on x86 systems.
1395 However, the address space of 32-bit x86 processors is only 4
1396 Gigabytes large. That means that, if you have a large amount of
1397 physical memory, not all of it can be "permanently mapped" by the
1398 kernel. The physical memory that's not permanently mapped is called
1401 If you are compiling a kernel which will never run on a machine with
1402 more than 1 Gigabyte total physical RAM, answer "off" here (default
1403 choice and suitable for most users). This will result in a "3GB/1GB"
1404 split: 3GB are mapped so that each process sees a 3GB virtual memory
1405 space and the remaining part of the 4GB virtual memory space is used
1406 by the kernel to permanently map as much physical memory as
1409 If the machine has between 1 and 4 Gigabytes physical RAM, then
1412 If more than 4 Gigabytes is used then answer "64GB" here. This
1413 selection turns Intel PAE (Physical Address Extension) mode on.
1414 PAE implements 3-level paging on IA32 processors. PAE is fully
1415 supported by Linux, PAE mode is implemented on all recent Intel
1416 processors (Pentium Pro and better). NOTE: If you say "64GB" here,
1417 then the kernel will not boot on CPUs that don't support PAE!
1419 The actual amount of total physical memory will either be
1420 auto detected or can be forced by using a kernel command line option
1421 such as "mem=256M". (Try "man bootparam" or see the documentation of
1422 your boot loader (lilo or loadlin) about how to pass options to the
1423 kernel at boot time.)
1425 If unsure, say "off".
1430 Select this if you have a 32-bit processor and between 1 and 4
1431 gigabytes of physical RAM.
1435 depends on !M486SX && !M486 && !M586 && !M586TSC && !M586MMX && !MGEODE_LX && !MGEODEGX1 && !MCYRIXIII && !MELAN && !MWINCHIPC6 && !MWINCHIP3D && !MK6
1438 Select this if you have a 32-bit processor and more than 4
1439 gigabytes of physical RAM.
1444 prompt "Memory split" if EXPERT
1448 Select the desired split between kernel and user memory.
1450 If the address range available to the kernel is less than the
1451 physical memory installed, the remaining memory will be available
1452 as "high memory". Accessing high memory is a little more costly
1453 than low memory, as it needs to be mapped into the kernel first.
1454 Note that increasing the kernel address space limits the range
1455 available to user programs, making the address space there
1456 tighter. Selecting anything other than the default 3G/1G split
1457 will also likely make your kernel incompatible with binary-only
1460 If you are not absolutely sure what you are doing, leave this
1464 bool "3G/1G user/kernel split"
1465 config VMSPLIT_3G_OPT
1467 bool "3G/1G user/kernel split (for full 1G low memory)"
1469 bool "2G/2G user/kernel split"
1470 config VMSPLIT_2G_OPT
1472 bool "2G/2G user/kernel split (for full 2G low memory)"
1474 bool "1G/3G user/kernel split"
1479 default 0xB0000000 if VMSPLIT_3G_OPT
1480 default 0x80000000 if VMSPLIT_2G
1481 default 0x78000000 if VMSPLIT_2G_OPT
1482 default 0x40000000 if VMSPLIT_1G
1488 depends on X86_32 && (HIGHMEM64G || HIGHMEM4G)
1491 bool "PAE (Physical Address Extension) Support"
1492 depends on X86_32 && !HIGHMEM4G
1493 select PHYS_ADDR_T_64BIT
1496 PAE is required for NX support, and furthermore enables
1497 larger swapspace support for non-overcommit purposes. It
1498 has the cost of more pagetable lookup overhead, and also
1499 consumes more pagetable space per process.
1502 bool "Enable 5-level page tables support"
1504 select DYNAMIC_MEMORY_LAYOUT
1505 select SPARSEMEM_VMEMMAP
1508 5-level paging enables access to larger address space:
1509 upto 128 PiB of virtual address space and 4 PiB of
1510 physical address space.
1512 It will be supported by future Intel CPUs.
1514 A kernel with the option enabled can be booted on machines that
1515 support 4- or 5-level paging.
1517 See Documentation/x86/x86_64/5level-paging.rst for more
1522 config X86_DIRECT_GBPAGES
1526 Certain kernel features effectively disable kernel
1527 linear 1 GB mappings (even if the CPU otherwise
1528 supports them), so don't confuse the user by printing
1529 that we have them enabled.
1531 config X86_CPA_STATISTICS
1532 bool "Enable statistic for Change Page Attribute"
1535 Expose statistics about the Change Page Attribute mechanism, which
1536 helps to determine the effectiveness of preserving large and huge
1537 page mappings when mapping protections are changed.
1539 config X86_MEM_ENCRYPT
1540 select ARCH_HAS_FORCE_DMA_UNENCRYPTED
1541 select DYNAMIC_PHYSICAL_MASK
1544 config AMD_MEM_ENCRYPT
1545 bool "AMD Secure Memory Encryption (SME) support"
1546 depends on X86_64 && CPU_SUP_AMD
1547 select DMA_COHERENT_POOL
1548 select ARCH_USE_MEMREMAP_PROT
1549 select INSTRUCTION_DECODER
1550 select ARCH_HAS_CC_PLATFORM
1551 select X86_MEM_ENCRYPT
1553 Say yes to enable support for the encryption of system memory.
1554 This requires an AMD processor that supports Secure Memory
1557 # Common NUMA Features
1559 bool "NUMA Memory Allocation and Scheduler Support"
1561 depends on X86_64 || (X86_32 && HIGHMEM64G && X86_BIGSMP)
1562 default y if X86_BIGSMP
1563 select USE_PERCPU_NUMA_NODE_ID
1565 Enable NUMA (Non-Uniform Memory Access) support.
1567 The kernel will try to allocate memory used by a CPU on the
1568 local memory controller of the CPU and add some more
1569 NUMA awareness to the kernel.
1571 For 64-bit this is recommended if the system is Intel Core i7
1572 (or later), AMD Opteron, or EM64T NUMA.
1574 For 32-bit this is only needed if you boot a 32-bit
1575 kernel on a 64-bit NUMA platform.
1577 Otherwise, you should say N.
1581 prompt "Old style AMD Opteron NUMA detection"
1582 depends on X86_64 && NUMA && PCI
1584 Enable AMD NUMA node topology detection. You should say Y here if
1585 you have a multi processor AMD system. This uses an old method to
1586 read the NUMA configuration directly from the builtin Northbridge
1587 of Opteron. It is recommended to use X86_64_ACPI_NUMA instead,
1588 which also takes priority if both are compiled in.
1590 config X86_64_ACPI_NUMA
1592 prompt "ACPI NUMA detection"
1593 depends on X86_64 && NUMA && ACPI && PCI
1596 Enable ACPI SRAT based node topology detection.
1599 bool "NUMA emulation"
1602 Enable NUMA emulation. A flat machine will be split
1603 into virtual nodes when booted with "numa=fake=N", where N is the
1604 number of nodes. This is only useful for debugging.
1607 int "Maximum NUMA Nodes (as a power of 2)" if !MAXSMP
1609 default "10" if MAXSMP
1610 default "6" if X86_64
1614 Specify the maximum number of NUMA Nodes available on the target
1615 system. Increases memory reserved to accommodate various tables.
1617 config ARCH_FLATMEM_ENABLE
1619 depends on X86_32 && !NUMA
1621 config ARCH_SPARSEMEM_ENABLE
1623 depends on X86_64 || NUMA || X86_32 || X86_32_NON_STANDARD
1624 select SPARSEMEM_STATIC if X86_32
1625 select SPARSEMEM_VMEMMAP_ENABLE if X86_64
1627 config ARCH_SPARSEMEM_DEFAULT
1628 def_bool X86_64 || (NUMA && X86_32)
1630 config ARCH_SELECT_MEMORY_MODEL
1632 depends on ARCH_SPARSEMEM_ENABLE && ARCH_FLATMEM_ENABLE
1634 config ARCH_MEMORY_PROBE
1635 bool "Enable sysfs memory/probe interface"
1636 depends on MEMORY_HOTPLUG
1638 This option enables a sysfs memory/probe interface for testing.
1639 See Documentation/admin-guide/mm/memory-hotplug.rst for more information.
1640 If you are unsure how to answer this question, answer N.
1642 config ARCH_PROC_KCORE_TEXT
1644 depends on X86_64 && PROC_KCORE
1646 config ILLEGAL_POINTER_VALUE
1649 default 0xdead000000000000 if X86_64
1651 config X86_PMEM_LEGACY_DEVICE
1654 config X86_PMEM_LEGACY
1655 tristate "Support non-standard NVDIMMs and ADR protected memory"
1656 depends on PHYS_ADDR_T_64BIT
1658 select X86_PMEM_LEGACY_DEVICE
1659 select NUMA_KEEP_MEMINFO if NUMA
1662 Treat memory marked using the non-standard e820 type of 12 as used
1663 by the Intel Sandy Bridge-EP reference BIOS as protected memory.
1664 The kernel will offer these regions to the 'pmem' driver so
1665 they can be used for persistent storage.
1670 bool "Allocate 3rd-level pagetables from highmem"
1673 The VM uses one page table entry for each page of physical memory.
1674 For systems with a lot of RAM, this can be wasteful of precious
1675 low memory. Setting this option will put user-space page table
1676 entries in high memory.
1678 config X86_CHECK_BIOS_CORRUPTION
1679 bool "Check for low memory corruption"
1681 Periodically check for memory corruption in low memory, which
1682 is suspected to be caused by BIOS. Even when enabled in the
1683 configuration, it is disabled at runtime. Enable it by
1684 setting "memory_corruption_check=1" on the kernel command
1685 line. By default it scans the low 64k of memory every 60
1686 seconds; see the memory_corruption_check_size and
1687 memory_corruption_check_period parameters in
1688 Documentation/admin-guide/kernel-parameters.rst to adjust this.
1690 When enabled with the default parameters, this option has
1691 almost no overhead, as it reserves a relatively small amount
1692 of memory and scans it infrequently. It both detects corruption
1693 and prevents it from affecting the running system.
1695 It is, however, intended as a diagnostic tool; if repeatable
1696 BIOS-originated corruption always affects the same memory,
1697 you can use memmap= to prevent the kernel from using that
1700 config X86_BOOTPARAM_MEMORY_CORRUPTION_CHECK
1701 bool "Set the default setting of memory_corruption_check"
1702 depends on X86_CHECK_BIOS_CORRUPTION
1705 Set whether the default state of memory_corruption_check is
1708 config MATH_EMULATION
1710 depends on MODIFY_LDT_SYSCALL
1711 prompt "Math emulation" if X86_32 && (M486SX || MELAN)
1713 Linux can emulate a math coprocessor (used for floating point
1714 operations) if you don't have one. 486DX and Pentium processors have
1715 a math coprocessor built in, 486SX and 386 do not, unless you added
1716 a 487DX or 387, respectively. (The messages during boot time can
1717 give you some hints here ["man dmesg"].) Everyone needs either a
1718 coprocessor or this emulation.
1720 If you don't have a math coprocessor, you need to say Y here; if you
1721 say Y here even though you have a coprocessor, the coprocessor will
1722 be used nevertheless. (This behavior can be changed with the kernel
1723 command line option "no387", which comes handy if your coprocessor
1724 is broken. Try "man bootparam" or see the documentation of your boot
1725 loader (lilo or loadlin) about how to pass options to the kernel at
1726 boot time.) This means that it is a good idea to say Y here if you
1727 intend to use this kernel on different machines.
1729 More information about the internals of the Linux math coprocessor
1730 emulation can be found in <file:arch/x86/math-emu/README>.
1732 If you are not sure, say Y; apart from resulting in a 66 KB bigger
1733 kernel, it won't hurt.
1737 prompt "MTRR (Memory Type Range Register) support" if EXPERT
1739 On Intel P6 family processors (Pentium Pro, Pentium II and later)
1740 the Memory Type Range Registers (MTRRs) may be used to control
1741 processor access to memory ranges. This is most useful if you have
1742 a video (VGA) card on a PCI or AGP bus. Enabling write-combining
1743 allows bus write transfers to be combined into a larger transfer
1744 before bursting over the PCI/AGP bus. This can increase performance
1745 of image write operations 2.5 times or more. Saying Y here creates a
1746 /proc/mtrr file which may be used to manipulate your processor's
1747 MTRRs. Typically the X server should use this.
1749 This code has a reasonably generic interface so that similar
1750 control registers on other processors can be easily supported
1753 The Cyrix 6x86, 6x86MX and M II processors have Address Range
1754 Registers (ARRs) which provide a similar functionality to MTRRs. For
1755 these, the ARRs are used to emulate the MTRRs.
1756 The AMD K6-2 (stepping 8 and above) and K6-3 processors have two
1757 MTRRs. The Centaur C6 (WinChip) has 8 MCRs, allowing
1758 write-combining. All of these processors are supported by this code
1759 and it makes sense to say Y here if you have one of them.
1761 Saying Y here also fixes a problem with buggy SMP BIOSes which only
1762 set the MTRRs for the boot CPU and not for the secondary CPUs. This
1763 can lead to all sorts of problems, so it's good to say Y here.
1765 You can safely say Y even if your machine doesn't have MTRRs, you'll
1766 just add about 9 KB to your kernel.
1768 See <file:Documentation/x86/mtrr.rst> for more information.
1770 config MTRR_SANITIZER
1772 prompt "MTRR cleanup support"
1775 Convert MTRR layout from continuous to discrete, so X drivers can
1776 add writeback entries.
1778 Can be disabled with disable_mtrr_cleanup on the kernel command line.
1779 The largest mtrr entry size for a continuous block can be set with
1784 config MTRR_SANITIZER_ENABLE_DEFAULT
1785 int "MTRR cleanup enable value (0-1)"
1788 depends on MTRR_SANITIZER
1790 Enable mtrr cleanup default value
1792 config MTRR_SANITIZER_SPARE_REG_NR_DEFAULT
1793 int "MTRR cleanup spare reg num (0-7)"
1796 depends on MTRR_SANITIZER
1798 mtrr cleanup spare entries default, it can be changed via
1799 mtrr_spare_reg_nr=N on the kernel command line.
1803 prompt "x86 PAT support" if EXPERT
1806 Use PAT attributes to setup page level cache control.
1808 PATs are the modern equivalents of MTRRs and are much more
1809 flexible than MTRRs.
1811 Say N here if you see bootup problems (boot crash, boot hang,
1812 spontaneous reboots) or a non-working video driver.
1816 config ARCH_USES_PG_UNCACHED
1822 prompt "User Mode Instruction Prevention" if EXPERT
1824 User Mode Instruction Prevention (UMIP) is a security feature in
1825 some x86 processors. If enabled, a general protection fault is
1826 issued if the SGDT, SLDT, SIDT, SMSW or STR instructions are
1827 executed in user mode. These instructions unnecessarily expose
1828 information about the hardware state.
1830 The vast majority of applications do not use these instructions.
1831 For the very few that do, software emulation is provided in
1832 specific cases in protected and virtual-8086 modes. Emulated
1836 # GCC >= 9 and binutils >= 2.29
1837 # Retpoline check to work around https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93654
1839 # https://github.com/llvm/llvm-project/commit/e0b89df2e0f0130881bf6c39bf31d7f6aac00e0f
1840 # https://github.com/llvm/llvm-project/commit/dfcf69770bc522b9e411c66454934a37c1f35332
1841 def_bool ((CC_IS_GCC && $(cc-option, -fcf-protection=branch -mindirect-branch-register)) || \
1842 (CC_IS_CLANG && CLANG_VERSION >= 140000)) && \
1845 config X86_KERNEL_IBT
1846 prompt "Indirect Branch Tracking"
1848 depends on X86_64 && CC_HAS_IBT && HAVE_OBJTOOL
1849 # https://github.com/llvm/llvm-project/commit/9d7001eba9c4cb311e03cd8cdc231f9e579f2d0f
1850 depends on !LD_IS_LLD || LLD_VERSION >= 140000
1853 Build the kernel with support for Indirect Branch Tracking, a
1854 hardware support course-grain forward-edge Control Flow Integrity
1855 protection. It enforces that all indirect calls must land on
1856 an ENDBR instruction, as such, the compiler will instrument the
1857 code with them to make this happen.
1859 In addition to building the kernel with IBT, seal all functions that
1860 are not indirect call targets, avoiding them ever becoming one.
1862 This requires LTO like objtool runs and will slow down the build. It
1863 does significantly reduce the number of ENDBR instructions in the
1866 config X86_INTEL_MEMORY_PROTECTION_KEYS
1867 prompt "Memory Protection Keys"
1869 # Note: only available in 64-bit mode
1870 depends on X86_64 && (CPU_SUP_INTEL || CPU_SUP_AMD)
1871 select ARCH_USES_HIGH_VMA_FLAGS
1872 select ARCH_HAS_PKEYS
1874 Memory Protection Keys provides a mechanism for enforcing
1875 page-based protections, but without requiring modification of the
1876 page tables when an application changes protection domains.
1878 For details, see Documentation/core-api/protection-keys.rst
1883 prompt "TSX enable mode"
1884 depends on CPU_SUP_INTEL
1885 default X86_INTEL_TSX_MODE_OFF
1887 Intel's TSX (Transactional Synchronization Extensions) feature
1888 allows to optimize locking protocols through lock elision which
1889 can lead to a noticeable performance boost.
1891 On the other hand it has been shown that TSX can be exploited
1892 to form side channel attacks (e.g. TAA) and chances are there
1893 will be more of those attacks discovered in the future.
1895 Therefore TSX is not enabled by default (aka tsx=off). An admin
1896 might override this decision by tsx=on the command line parameter.
1897 Even with TSX enabled, the kernel will attempt to enable the best
1898 possible TAA mitigation setting depending on the microcode available
1899 for the particular machine.
1901 This option allows to set the default tsx mode between tsx=on, =off
1902 and =auto. See Documentation/admin-guide/kernel-parameters.txt for more
1905 Say off if not sure, auto if TSX is in use but it should be used on safe
1906 platforms or on if TSX is in use and the security aspect of tsx is not
1909 config X86_INTEL_TSX_MODE_OFF
1912 TSX is disabled if possible - equals to tsx=off command line parameter.
1914 config X86_INTEL_TSX_MODE_ON
1917 TSX is always enabled on TSX capable HW - equals the tsx=on command
1920 config X86_INTEL_TSX_MODE_AUTO
1923 TSX is enabled on TSX capable HW that is believed to be safe against
1924 side channel attacks- equals the tsx=auto command line parameter.
1928 bool "Software Guard eXtensions (SGX)"
1929 depends on X86_64 && CPU_SUP_INTEL && X86_X2APIC
1931 depends on CRYPTO_SHA256=y
1934 select NUMA_KEEP_MEMINFO if NUMA
1937 Intel(R) Software Guard eXtensions (SGX) is a set of CPU instructions
1938 that can be used by applications to set aside private regions of code
1939 and data, referred to as enclaves. An enclave's private memory can
1940 only be accessed by code running within the enclave. Accesses from
1941 outside the enclave, including other enclaves, are disallowed by
1947 bool "EFI runtime service support"
1950 select EFI_RUNTIME_WRAPPERS
1951 select ARCH_USE_MEMREMAP_PROT
1953 This enables the kernel to use EFI runtime services that are
1954 available (such as the EFI variable services).
1956 This option is only useful on systems that have EFI firmware.
1957 In addition, you should use the latest ELILO loader available
1958 at <http://elilo.sourceforge.net> in order to take advantage
1959 of EFI runtime services. However, even with this option, the
1960 resultant kernel should continue to boot on existing non-EFI
1964 bool "EFI stub support"
1968 This kernel feature allows a bzImage to be loaded directly
1969 by EFI firmware without the use of a bootloader.
1971 See Documentation/admin-guide/efi-stub.rst for more information.
1973 config EFI_HANDOVER_PROTOCOL
1974 bool "EFI handover protocol (DEPRECATED)"
1978 Select this in order to include support for the deprecated EFI
1979 handover protocol, which defines alternative entry points into the
1980 EFI stub. This is a practice that has no basis in the UEFI
1981 specification, and requires a priori knowledge on the part of the
1982 bootloader about Linux/x86 specific ways of passing the command line
1983 and initrd, and where in memory those assets may be loaded.
1985 If in doubt, say Y. Even though the corresponding support is not
1986 present in upstream GRUB or other bootloaders, most distros build
1987 GRUB with numerous downstream patches applied, and may rely on the
1988 handover protocol as as result.
1991 bool "EFI mixed-mode support"
1992 depends on EFI_STUB && X86_64
1994 Enabling this feature allows a 64-bit kernel to be booted
1995 on a 32-bit firmware, provided that your CPU supports 64-bit
1998 Note that it is not possible to boot a mixed-mode enabled
1999 kernel via the EFI boot stub - a bootloader that supports
2000 the EFI handover protocol must be used.
2004 source "kernel/Kconfig.hz"
2007 bool "kexec system call"
2010 kexec is a system call that implements the ability to shutdown your
2011 current kernel, and to start another kernel. It is like a reboot
2012 but it is independent of the system firmware. And like a reboot
2013 you can start any kernel with it, not just Linux.
2015 The name comes from the similarity to the exec system call.
2017 It is an ongoing process to be certain the hardware in a machine
2018 is properly shutdown, so do not be surprised if this code does not
2019 initially work for you. As of this writing the exact hardware
2020 interface is strongly in flux, so no good recommendation can be
2024 bool "kexec file based system call"
2026 select HAVE_IMA_KEXEC if IMA
2029 depends on CRYPTO_SHA256=y
2031 This is new version of kexec system call. This system call is
2032 file based and takes file descriptors as system call argument
2033 for kernel and initramfs as opposed to list of segments as
2034 accepted by previous system call.
2036 config ARCH_HAS_KEXEC_PURGATORY
2040 bool "Verify kernel signature during kexec_file_load() syscall"
2041 depends on KEXEC_FILE
2044 This option makes the kexec_file_load() syscall check for a valid
2045 signature of the kernel image. The image can still be loaded without
2046 a valid signature unless you also enable KEXEC_SIG_FORCE, though if
2047 there's a signature that we can check, then it must be valid.
2049 In addition to this option, you need to enable signature
2050 verification for the corresponding kernel image type being
2051 loaded in order for this to work.
2053 config KEXEC_SIG_FORCE
2054 bool "Require a valid signature in kexec_file_load() syscall"
2055 depends on KEXEC_SIG
2057 This option makes kernel signature verification mandatory for
2058 the kexec_file_load() syscall.
2060 config KEXEC_BZIMAGE_VERIFY_SIG
2061 bool "Enable bzImage signature verification support"
2062 depends on KEXEC_SIG
2063 depends on SIGNED_PE_FILE_VERIFICATION
2064 select SYSTEM_TRUSTED_KEYRING
2066 Enable bzImage signature verification support.
2069 bool "kernel crash dumps"
2070 depends on X86_64 || (X86_32 && HIGHMEM)
2072 Generate crash dump after being started by kexec.
2073 This should be normally only set in special crash dump kernels
2074 which are loaded in the main kernel with kexec-tools into
2075 a specially reserved region and then later executed after
2076 a crash by kdump/kexec. The crash dump kernel must be compiled
2077 to a memory address not used by the main kernel or BIOS using
2078 PHYSICAL_START, or it must be built as a relocatable image
2079 (CONFIG_RELOCATABLE=y).
2080 For more details see Documentation/admin-guide/kdump/kdump.rst
2084 depends on KEXEC && HIBERNATION
2086 Jump between original kernel and kexeced kernel and invoke
2087 code in physical address mode via KEXEC
2089 config PHYSICAL_START
2090 hex "Physical address where the kernel is loaded" if (EXPERT || CRASH_DUMP)
2093 This gives the physical address where the kernel is loaded.
2095 If kernel is a not relocatable (CONFIG_RELOCATABLE=n) then
2096 bzImage will decompress itself to above physical address and
2097 run from there. Otherwise, bzImage will run from the address where
2098 it has been loaded by the boot loader and will ignore above physical
2101 In normal kdump cases one does not have to set/change this option
2102 as now bzImage can be compiled as a completely relocatable image
2103 (CONFIG_RELOCATABLE=y) and be used to load and run from a different
2104 address. This option is mainly useful for the folks who don't want
2105 to use a bzImage for capturing the crash dump and want to use a
2106 vmlinux instead. vmlinux is not relocatable hence a kernel needs
2107 to be specifically compiled to run from a specific memory area
2108 (normally a reserved region) and this option comes handy.
2110 So if you are using bzImage for capturing the crash dump,
2111 leave the value here unchanged to 0x1000000 and set
2112 CONFIG_RELOCATABLE=y. Otherwise if you plan to use vmlinux
2113 for capturing the crash dump change this value to start of
2114 the reserved region. In other words, it can be set based on
2115 the "X" value as specified in the "crashkernel=YM@XM"
2116 command line boot parameter passed to the panic-ed
2117 kernel. Please take a look at Documentation/admin-guide/kdump/kdump.rst
2118 for more details about crash dumps.
2120 Usage of bzImage for capturing the crash dump is recommended as
2121 one does not have to build two kernels. Same kernel can be used
2122 as production kernel and capture kernel. Above option should have
2123 gone away after relocatable bzImage support is introduced. But it
2124 is present because there are users out there who continue to use
2125 vmlinux for dump capture. This option should go away down the
2128 Don't change this unless you know what you are doing.
2131 bool "Build a relocatable kernel"
2134 This builds a kernel image that retains relocation information
2135 so it can be loaded someplace besides the default 1MB.
2136 The relocations tend to make the kernel binary about 10% larger,
2137 but are discarded at runtime.
2139 One use is for the kexec on panic case where the recovery kernel
2140 must live at a different physical address than the primary
2143 Note: If CONFIG_RELOCATABLE=y, then the kernel runs from the address
2144 it has been loaded at and the compile time physical address
2145 (CONFIG_PHYSICAL_START) is used as the minimum location.
2147 config RANDOMIZE_BASE
2148 bool "Randomize the address of the kernel image (KASLR)"
2149 depends on RELOCATABLE
2152 In support of Kernel Address Space Layout Randomization (KASLR),
2153 this randomizes the physical address at which the kernel image
2154 is decompressed and the virtual address where the kernel
2155 image is mapped, as a security feature that deters exploit
2156 attempts relying on knowledge of the location of kernel
2159 On 64-bit, the kernel physical and virtual addresses are
2160 randomized separately. The physical address will be anywhere
2161 between 16MB and the top of physical memory (up to 64TB). The
2162 virtual address will be randomized from 16MB up to 1GB (9 bits
2163 of entropy). Note that this also reduces the memory space
2164 available to kernel modules from 1.5GB to 1GB.
2166 On 32-bit, the kernel physical and virtual addresses are
2167 randomized together. They will be randomized from 16MB up to
2168 512MB (8 bits of entropy).
2170 Entropy is generated using the RDRAND instruction if it is
2171 supported. If RDTSC is supported, its value is mixed into
2172 the entropy pool as well. If neither RDRAND nor RDTSC are
2173 supported, then entropy is read from the i8254 timer. The
2174 usable entropy is limited by the kernel being built using
2175 2GB addressing, and that PHYSICAL_ALIGN must be at a
2176 minimum of 2MB. As a result, only 10 bits of entropy are
2177 theoretically possible, but the implementations are further
2178 limited due to memory layouts.
2182 # Relocation on x86 needs some additional build support
2183 config X86_NEED_RELOCS
2185 depends on RANDOMIZE_BASE || (X86_32 && RELOCATABLE)
2187 config PHYSICAL_ALIGN
2188 hex "Alignment value to which kernel should be aligned"
2190 range 0x2000 0x1000000 if X86_32
2191 range 0x200000 0x1000000 if X86_64
2193 This value puts the alignment restrictions on physical address
2194 where kernel is loaded and run from. Kernel is compiled for an
2195 address which meets above alignment restriction.
2197 If bootloader loads the kernel at a non-aligned address and
2198 CONFIG_RELOCATABLE is set, kernel will move itself to nearest
2199 address aligned to above value and run from there.
2201 If bootloader loads the kernel at a non-aligned address and
2202 CONFIG_RELOCATABLE is not set, kernel will ignore the run time
2203 load address and decompress itself to the address it has been
2204 compiled for and run from there. The address for which kernel is
2205 compiled already meets above alignment restrictions. Hence the
2206 end result is that kernel runs from a physical address meeting
2207 above alignment restrictions.
2209 On 32-bit this value must be a multiple of 0x2000. On 64-bit
2210 this value must be a multiple of 0x200000.
2212 Don't change this unless you know what you are doing.
2214 config DYNAMIC_MEMORY_LAYOUT
2217 This option makes base addresses of vmalloc and vmemmap as well as
2218 __PAGE_OFFSET movable during boot.
2220 config RANDOMIZE_MEMORY
2221 bool "Randomize the kernel memory sections"
2223 depends on RANDOMIZE_BASE
2224 select DYNAMIC_MEMORY_LAYOUT
2225 default RANDOMIZE_BASE
2227 Randomizes the base virtual address of kernel memory sections
2228 (physical memory mapping, vmalloc & vmemmap). This security feature
2229 makes exploits relying on predictable memory locations less reliable.
2231 The order of allocations remains unchanged. Entropy is generated in
2232 the same way as RANDOMIZE_BASE. Current implementation in the optimal
2233 configuration have in average 30,000 different possible virtual
2234 addresses for each memory section.
2238 config RANDOMIZE_MEMORY_PHYSICAL_PADDING
2239 hex "Physical memory mapping padding" if EXPERT
2240 depends on RANDOMIZE_MEMORY
2241 default "0xa" if MEMORY_HOTPLUG
2243 range 0x1 0x40 if MEMORY_HOTPLUG
2246 Define the padding in terabytes added to the existing physical
2247 memory size during kernel memory randomization. It is useful
2248 for memory hotplug support but reduces the entropy available for
2249 address randomization.
2251 If unsure, leave at the default value.
2257 config BOOTPARAM_HOTPLUG_CPU0
2258 bool "Set default setting of cpu0_hotpluggable"
2259 depends on HOTPLUG_CPU
2261 Set whether default state of cpu0_hotpluggable is on or off.
2263 Say Y here to enable CPU0 hotplug by default. If this switch
2264 is turned on, there is no need to give cpu0_hotplug kernel
2265 parameter and the CPU0 hotplug feature is enabled by default.
2267 Please note: there are two known CPU0 dependencies if you want
2268 to enable the CPU0 hotplug feature either by this switch or by
2269 cpu0_hotplug kernel parameter.
2271 First, resume from hibernate or suspend always starts from CPU0.
2272 So hibernate and suspend are prevented if CPU0 is offline.
2274 Second dependency is PIC interrupts always go to CPU0. CPU0 can not
2275 offline if any interrupt can not migrate out of CPU0. There may
2276 be other CPU0 dependencies.
2278 Please make sure the dependencies are under your control before
2279 you enable this feature.
2281 Say N if you don't want to enable CPU0 hotplug feature by default.
2282 You still can enable the CPU0 hotplug feature at boot by kernel
2283 parameter cpu0_hotplug.
2285 config DEBUG_HOTPLUG_CPU0
2287 prompt "Debug CPU0 hotplug"
2288 depends on HOTPLUG_CPU
2290 Enabling this option offlines CPU0 (if CPU0 can be offlined) as
2291 soon as possible and boots up userspace with CPU0 offlined. User
2292 can online CPU0 back after boot time.
2294 To debug CPU0 hotplug, you need to enable CPU0 offline/online
2295 feature by either turning on CONFIG_BOOTPARAM_HOTPLUG_CPU0 during
2296 compilation or giving cpu0_hotplug kernel parameter at boot.
2302 prompt "Disable the 32-bit vDSO (needed for glibc 2.3.3)"
2303 depends on COMPAT_32
2305 Certain buggy versions of glibc will crash if they are
2306 presented with a 32-bit vDSO that is not mapped at the address
2307 indicated in its segment table.
2309 The bug was introduced by f866314b89d56845f55e6f365e18b31ec978ec3a
2310 and fixed by 3b3ddb4f7db98ec9e912ccdf54d35df4aa30e04a and
2311 49ad572a70b8aeb91e57483a11dd1b77e31c4468. Glibc 2.3.3 is
2312 the only released version with the bug, but OpenSUSE 9
2313 contains a buggy "glibc 2.3.2".
2315 The symptom of the bug is that everything crashes on startup, saying:
2316 dl_main: Assertion `(void *) ph->p_vaddr == _rtld_local._dl_sysinfo_dso' failed!
2318 Saying Y here changes the default value of the vdso32 boot
2319 option from 1 to 0, which turns off the 32-bit vDSO entirely.
2320 This works around the glibc bug but hurts performance.
2322 If unsure, say N: if you are compiling your own kernel, you
2323 are unlikely to be using a buggy version of glibc.
2326 prompt "vsyscall table for legacy applications"
2328 default LEGACY_VSYSCALL_XONLY
2330 Legacy user code that does not know how to find the vDSO expects
2331 to be able to issue three syscalls by calling fixed addresses in
2332 kernel space. Since this location is not randomized with ASLR,
2333 it can be used to assist security vulnerability exploitation.
2335 This setting can be changed at boot time via the kernel command
2336 line parameter vsyscall=[emulate|xonly|none]. Emulate mode
2337 is deprecated and can only be enabled using the kernel command
2340 On a system with recent enough glibc (2.14 or newer) and no
2341 static binaries, you can say None without a performance penalty
2342 to improve security.
2344 If unsure, select "Emulate execution only".
2346 config LEGACY_VSYSCALL_XONLY
2347 bool "Emulate execution only"
2349 The kernel traps and emulates calls into the fixed vsyscall
2350 address mapping and does not allow reads. This
2351 configuration is recommended when userspace might use the
2352 legacy vsyscall area but support for legacy binary
2353 instrumentation of legacy code is not needed. It mitigates
2354 certain uses of the vsyscall area as an ASLR-bypassing
2357 config LEGACY_VSYSCALL_NONE
2360 There will be no vsyscall mapping at all. This will
2361 eliminate any risk of ASLR bypass due to the vsyscall
2362 fixed address mapping. Attempts to use the vsyscalls
2363 will be reported to dmesg, so that either old or
2364 malicious userspace programs can be identified.
2369 bool "Built-in kernel command line"
2371 Allow for specifying boot arguments to the kernel at
2372 build time. On some systems (e.g. embedded ones), it is
2373 necessary or convenient to provide some or all of the
2374 kernel boot arguments with the kernel itself (that is,
2375 to not rely on the boot loader to provide them.)
2377 To compile command line arguments into the kernel,
2378 set this option to 'Y', then fill in the
2379 boot arguments in CONFIG_CMDLINE.
2381 Systems with fully functional boot loaders (i.e. non-embedded)
2382 should leave this option set to 'N'.
2385 string "Built-in kernel command string"
2386 depends on CMDLINE_BOOL
2389 Enter arguments here that should be compiled into the kernel
2390 image and used at boot time. If the boot loader provides a
2391 command line at boot time, it is appended to this string to
2392 form the full kernel command line, when the system boots.
2394 However, you can use the CONFIG_CMDLINE_OVERRIDE option to
2395 change this behavior.
2397 In most cases, the command line (whether built-in or provided
2398 by the boot loader) should specify the device for the root
2401 config CMDLINE_OVERRIDE
2402 bool "Built-in command line overrides boot loader arguments"
2403 depends on CMDLINE_BOOL && CMDLINE != ""
2405 Set this option to 'Y' to have the kernel ignore the boot loader
2406 command line, and use ONLY the built-in command line.
2408 This is used to work around broken boot loaders. This should
2409 be set to 'N' under normal conditions.
2411 config MODIFY_LDT_SYSCALL
2412 bool "Enable the LDT (local descriptor table)" if EXPERT
2415 Linux can allow user programs to install a per-process x86
2416 Local Descriptor Table (LDT) using the modify_ldt(2) system
2417 call. This is required to run 16-bit or segmented code such as
2418 DOSEMU or some Wine programs. It is also used by some very old
2419 threading libraries.
2421 Enabling this feature adds a small amount of overhead to
2422 context switches and increases the low-level kernel attack
2423 surface. Disabling it removes the modify_ldt(2) system call.
2425 Saying 'N' here may make sense for embedded or server kernels.
2427 config STRICT_SIGALTSTACK_SIZE
2428 bool "Enforce strict size checking for sigaltstack"
2429 depends on DYNAMIC_SIGFRAME
2431 For historical reasons MINSIGSTKSZ is a constant which became
2432 already too small with AVX512 support. Add a mechanism to
2433 enforce strict checking of the sigaltstack size against the
2434 real size of the FPU frame. This option enables the check
2435 by default. It can also be controlled via the kernel command
2436 line option 'strict_sas_size' independent of this config
2437 switch. Enabling it might break existing applications which
2438 allocate a too small sigaltstack but 'work' because they
2439 never get a signal delivered.
2441 Say 'N' unless you want to really enforce this check.
2443 source "kernel/livepatch/Kconfig"
2448 def_bool $(cc-option,-mharden-sls=all)
2450 config CC_HAS_RETURN_THUNK
2451 def_bool $(cc-option,-mfunction-return=thunk-extern)
2453 menuconfig CPU_MITIGATIONS
2454 bool "Mitigations for CPU vulnerabilities"
2457 Say Y here to enable options which enable mitigations for hardware
2458 vulnerabilities (usually related to speculative execution).
2460 If you say N, all mitigations will be disabled. You really
2461 should know what you are doing to say so.
2465 config PAGE_TABLE_ISOLATION
2466 bool "Remove the kernel mapping in user mode"
2468 depends on (X86_64 || X86_PAE)
2470 This feature reduces the number of hardware side channels by
2471 ensuring that the majority of kernel addresses are not mapped
2474 See Documentation/x86/pti.rst for more details.
2477 bool "Avoid speculative indirect branches in kernel"
2478 select OBJTOOL if HAVE_OBJTOOL
2481 Compile kernel with the retpoline compiler options to guard against
2482 kernel-to-user data leaks by avoiding speculative indirect
2483 branches. Requires a compiler with -mindirect-branch=thunk-extern
2484 support for full protection. The kernel may run slower.
2487 bool "Enable return-thunks"
2488 depends on RETPOLINE && CC_HAS_RETURN_THUNK
2489 select OBJTOOL if HAVE_OBJTOOL
2492 Compile the kernel with the return-thunks compiler option to guard
2493 against kernel-to-user data leaks by avoiding return speculation.
2494 Requires a compiler with -mfunction-return=thunk-extern
2495 support for full protection. The kernel may run slower.
2497 config CPU_UNRET_ENTRY
2498 bool "Enable UNRET on kernel entry"
2499 depends on CPU_SUP_AMD && RETHUNK && X86_64
2502 Compile the kernel with support for the retbleed=unret mitigation.
2504 config CPU_IBPB_ENTRY
2505 bool "Enable IBPB on kernel entry"
2506 depends on CPU_SUP_AMD && X86_64
2509 Compile the kernel with support for the retbleed=ibpb mitigation.
2511 config CPU_IBRS_ENTRY
2512 bool "Enable IBRS on kernel entry"
2513 depends on CPU_SUP_INTEL && X86_64
2516 Compile the kernel with support for the spectre_v2=ibrs mitigation.
2517 This mitigates both spectre_v2 and retbleed at great cost to
2521 bool "Mitigate speculative RAS overflow on AMD"
2522 depends on CPU_SUP_AMD && X86_64 && RETHUNK
2525 Enable the SRSO mitigation needed on AMD Zen1-4 machines.
2528 bool "Mitigate Straight-Line-Speculation"
2529 depends on CC_HAS_SLS && X86_64
2530 select OBJTOOL if HAVE_OBJTOOL
2533 Compile the kernel with straight-line-speculation options to guard
2534 against straight line speculation. The kernel image might be slightly
2537 config GDS_FORCE_MITIGATION
2538 bool "Force GDS Mitigation"
2539 depends on CPU_SUP_INTEL
2542 Gather Data Sampling (GDS) is a hardware vulnerability which allows
2543 unprivileged speculative access to data which was previously stored in
2546 This option is equivalent to setting gather_data_sampling=force on the
2547 command line. The microcode mitigation is used if present, otherwise
2548 AVX is disabled as a mitigation. On affected systems that are missing
2549 the microcode any userspace code that unconditionally uses AVX will
2550 break with this option set.
2552 Setting this option on systems not vulnerable to GDS has no effect.
2556 config MITIGATION_RFDS
2557 bool "RFDS Mitigation"
2558 depends on CPU_SUP_INTEL
2561 Enable mitigation for Register File Data Sampling (RFDS) by default.
2562 RFDS is a hardware vulnerability which affects Intel Atom CPUs. It
2563 allows unprivileged speculative access to stale data previously
2564 stored in floating point, vector and integer registers.
2565 See also <file:Documentation/admin-guide/hw-vuln/reg-file-data-sampling.rst>
2567 config MITIGATION_SPECTRE_BHI
2568 bool "Mitigate Spectre-BHB (Branch History Injection)"
2569 depends on CPU_SUP_INTEL
2572 Enable BHI mitigations. BHI attacks are a form of Spectre V2 attacks
2573 where the branch history buffer is poisoned to speculatively steer
2575 See <file:Documentation/admin-guide/hw-vuln/spectre.rst>
2579 config ARCH_HAS_ADD_PAGES
2581 depends on ARCH_ENABLE_MEMORY_HOTPLUG
2583 config ARCH_MHP_MEMMAP_ON_MEMORY_ENABLE
2586 menu "Power management and ACPI options"
2588 config ARCH_HIBERNATION_HEADER
2590 depends on HIBERNATION
2592 source "kernel/power/Kconfig"
2594 source "drivers/acpi/Kconfig"
2601 tristate "APM (Advanced Power Management) BIOS support"
2602 depends on X86_32 && PM_SLEEP
2604 APM is a BIOS specification for saving power using several different
2605 techniques. This is mostly useful for battery powered laptops with
2606 APM compliant BIOSes. If you say Y here, the system time will be
2607 reset after a RESUME operation, the /proc/apm device will provide
2608 battery status information, and user-space programs will receive
2609 notification of APM "events" (e.g. battery status change).
2611 If you select "Y" here, you can disable actual use of the APM
2612 BIOS by passing the "apm=off" option to the kernel at boot time.
2614 Note that the APM support is almost completely disabled for
2615 machines with more than one CPU.
2617 In order to use APM, you will need supporting software. For location
2618 and more information, read <file:Documentation/power/apm-acpi.rst>
2619 and the Battery Powered Linux mini-HOWTO, available from
2620 <http://www.tldp.org/docs.html#howto>.
2622 This driver does not spin down disk drives (see the hdparm(8)
2623 manpage ("man 8 hdparm") for that), and it doesn't turn off
2624 VESA-compliant "green" monitors.
2626 This driver does not support the TI 4000M TravelMate and the ACER
2627 486/DX4/75 because they don't have compliant BIOSes. Many "green"
2628 desktop machines also don't have compliant BIOSes, and this driver
2629 may cause those machines to panic during the boot phase.
2631 Generally, if you don't have a battery in your machine, there isn't
2632 much point in using this driver and you should say N. If you get
2633 random kernel OOPSes or reboots that don't seem to be related to
2634 anything, try disabling/enabling this option (or disabling/enabling
2637 Some other things you should try when experiencing seemingly random,
2640 1) make sure that you have enough swap space and that it is
2642 2) pass the "idle=poll" option to the kernel
2643 3) switch on floating point emulation in the kernel and pass
2644 the "no387" option to the kernel
2645 4) pass the "floppy=nodma" option to the kernel
2646 5) pass the "mem=4M" option to the kernel (thereby disabling
2647 all but the first 4 MB of RAM)
2648 6) make sure that the CPU is not over clocked.
2649 7) read the sig11 FAQ at <http://www.bitwizard.nl/sig11/>
2650 8) disable the cache from your BIOS settings
2651 9) install a fan for the video card or exchange video RAM
2652 10) install a better fan for the CPU
2653 11) exchange RAM chips
2654 12) exchange the motherboard.
2656 To compile this driver as a module, choose M here: the
2657 module will be called apm.
2661 config APM_IGNORE_USER_SUSPEND
2662 bool "Ignore USER SUSPEND"
2664 This option will ignore USER SUSPEND requests. On machines with a
2665 compliant APM BIOS, you want to say N. However, on the NEC Versa M
2666 series notebooks, it is necessary to say Y because of a BIOS bug.
2668 config APM_DO_ENABLE
2669 bool "Enable PM at boot time"
2671 Enable APM features at boot time. From page 36 of the APM BIOS
2672 specification: "When disabled, the APM BIOS does not automatically
2673 power manage devices, enter the Standby State, enter the Suspend
2674 State, or take power saving steps in response to CPU Idle calls."
2675 This driver will make CPU Idle calls when Linux is idle (unless this
2676 feature is turned off -- see "Do CPU IDLE calls", below). This
2677 should always save battery power, but more complicated APM features
2678 will be dependent on your BIOS implementation. You may need to turn
2679 this option off if your computer hangs at boot time when using APM
2680 support, or if it beeps continuously instead of suspending. Turn
2681 this off if you have a NEC UltraLite Versa 33/C or a Toshiba
2682 T400CDT. This is off by default since most machines do fine without
2687 bool "Make CPU Idle calls when idle"
2689 Enable calls to APM CPU Idle/CPU Busy inside the kernel's idle loop.
2690 On some machines, this can activate improved power savings, such as
2691 a slowed CPU clock rate, when the machine is idle. These idle calls
2692 are made after the idle loop has run for some length of time (e.g.,
2693 333 mS). On some machines, this will cause a hang at boot time or
2694 whenever the CPU becomes idle. (On machines with more than one CPU,
2695 this option does nothing.)
2697 config APM_DISPLAY_BLANK
2698 bool "Enable console blanking using APM"
2700 Enable console blanking using the APM. Some laptops can use this to
2701 turn off the LCD backlight when the screen blanker of the Linux
2702 virtual console blanks the screen. Note that this is only used by
2703 the virtual console screen blanker, and won't turn off the backlight
2704 when using the X Window system. This also doesn't have anything to
2705 do with your VESA-compliant power-saving monitor. Further, this
2706 option doesn't work for all laptops -- it might not turn off your
2707 backlight at all, or it might print a lot of errors to the console,
2708 especially if you are using gpm.
2710 config APM_ALLOW_INTS
2711 bool "Allow interrupts during APM BIOS calls"
2713 Normally we disable external interrupts while we are making calls to
2714 the APM BIOS as a measure to lessen the effects of a badly behaving
2715 BIOS implementation. The BIOS should reenable interrupts if it
2716 needs to. Unfortunately, some BIOSes do not -- especially those in
2717 many of the newer IBM Thinkpads. If you experience hangs when you
2718 suspend, try setting this to Y. Otherwise, say N.
2722 source "drivers/cpufreq/Kconfig"
2724 source "drivers/cpuidle/Kconfig"
2726 source "drivers/idle/Kconfig"
2730 menu "Bus options (PCI etc.)"
2733 prompt "PCI access mode"
2734 depends on X86_32 && PCI
2737 On PCI systems, the BIOS can be used to detect the PCI devices and
2738 determine their configuration. However, some old PCI motherboards
2739 have BIOS bugs and may crash if this is done. Also, some embedded
2740 PCI-based systems don't have any BIOS at all. Linux can also try to
2741 detect the PCI hardware directly without using the BIOS.
2743 With this option, you can specify how Linux should detect the
2744 PCI devices. If you choose "BIOS", the BIOS will be used,
2745 if you choose "Direct", the BIOS won't be used, and if you
2746 choose "MMConfig", then PCI Express MMCONFIG will be used.
2747 If you choose "Any", the kernel will try MMCONFIG, then the
2748 direct access method and falls back to the BIOS if that doesn't
2749 work. If unsure, go with the default, which is "Any".
2754 config PCI_GOMMCONFIG
2771 depends on X86_32 && PCI && (PCI_GOBIOS || PCI_GOANY)
2773 # x86-64 doesn't support PCI BIOS access from long mode so always go direct.
2776 depends on PCI && (X86_64 || (PCI_GODIRECT || PCI_GOANY || PCI_GOOLPC || PCI_GOMMCONFIG))
2779 bool "Support mmconfig PCI config space access" if X86_64
2781 depends on PCI && (ACPI || JAILHOUSE_GUEST)
2782 depends on X86_64 || (PCI_GOANY || PCI_GOMMCONFIG)
2786 depends on PCI && OLPC && (PCI_GOOLPC || PCI_GOANY)
2790 depends on PCI && XEN
2792 config MMCONF_FAM10H
2794 depends on X86_64 && PCI_MMCONFIG && ACPI
2796 config PCI_CNB20LE_QUIRK
2797 bool "Read CNB20LE Host Bridge Windows" if EXPERT
2800 Read the PCI windows out of the CNB20LE host bridge. This allows
2801 PCI hotplug to work on systems with the CNB20LE chipset which do
2804 There's no public spec for this chipset, and this functionality
2805 is known to be incomplete.
2807 You should say N unless you know you need this.
2810 bool "ISA bus support on modern systems" if EXPERT
2812 Expose ISA bus device drivers and options available for selection and
2813 configuration. Enable this option if your target machine has an ISA
2814 bus. ISA is an older system, displaced by PCI and newer bus
2815 architectures -- if your target machine is modern, it probably does
2816 not have an ISA bus.
2820 # x86_64 have no ISA slots, but can have ISA-style DMA.
2822 bool "ISA-style DMA support" if (X86_64 && EXPERT)
2825 Enables ISA-style DMA support for devices requiring such controllers.
2833 Find out whether you have ISA slots on your motherboard. ISA is the
2834 name of a bus system, i.e. the way the CPU talks to the other stuff
2835 inside your box. Other bus systems are PCI, EISA, MicroChannel
2836 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
2837 newer boards don't support it. If you have ISA, say Y, otherwise N.
2840 tristate "NatSemi SCx200 support"
2842 This provides basic support for National Semiconductor's
2843 (now AMD's) Geode processors. The driver probes for the
2844 PCI-IDs of several on-chip devices, so its a good dependency
2845 for other scx200_* drivers.
2847 If compiled as a module, the driver is named scx200.
2849 config SCx200HR_TIMER
2850 tristate "NatSemi SCx200 27MHz High-Resolution Timer Support"
2854 This driver provides a clocksource built upon the on-chip
2855 27MHz high-resolution timer. Its also a workaround for
2856 NSC Geode SC-1100's buggy TSC, which loses time when the
2857 processor goes idle (as is done by the scheduler). The
2858 other workaround is idle=poll boot option.
2861 bool "One Laptop Per Child support"
2869 Add support for detecting the unique features of the OLPC
2873 bool "OLPC XO-1 Power Management"
2874 depends on OLPC && MFD_CS5535=y && PM_SLEEP
2876 Add support for poweroff and suspend of the OLPC XO-1 laptop.
2879 bool "OLPC XO-1 Real Time Clock"
2880 depends on OLPC_XO1_PM && RTC_DRV_CMOS
2882 Add support for the XO-1 real time clock, which can be used as a
2883 programmable wakeup source.
2886 bool "OLPC XO-1 SCI extras"
2887 depends on OLPC && OLPC_XO1_PM && GPIO_CS5535=y
2891 Add support for SCI-based features of the OLPC XO-1 laptop:
2892 - EC-driven system wakeups
2896 - AC adapter status updates
2897 - Battery status updates
2899 config OLPC_XO15_SCI
2900 bool "OLPC XO-1.5 SCI extras"
2901 depends on OLPC && ACPI
2904 Add support for SCI-based features of the OLPC XO-1.5 laptop:
2905 - EC-driven system wakeups
2906 - AC adapter status updates
2907 - Battery status updates
2910 bool "PCEngines ALIX System Support (LED setup)"
2913 This option enables system support for the PCEngines ALIX.
2914 At present this just sets up LEDs for GPIO control on
2915 ALIX2/3/6 boards. However, other system specific setup should
2918 Note: You must still enable the drivers for GPIO and LED support
2919 (GPIO_CS5535 & LEDS_GPIO) to actually use the LEDs
2921 Note: You have to set alix.force=1 for boards with Award BIOS.
2924 bool "Soekris Engineering net5501 System Support (LEDS, GPIO, etc)"
2927 This option enables system support for the Soekris Engineering net5501.
2930 bool "Traverse Technologies GEOS System Support (LEDS, GPIO, etc)"
2934 This option enables system support for the Traverse Technologies GEOS.
2937 bool "Technologic Systems TS-5500 platform support"
2939 select CHECK_SIGNATURE
2943 This option enables system support for the Technologic Systems TS-5500.
2949 depends on CPU_SUP_AMD && PCI
2953 menu "Binary Emulations"
2955 config IA32_EMULATION
2956 bool "IA32 Emulation"
2958 select ARCH_WANT_OLD_COMPAT_IPC
2960 select COMPAT_OLD_SIGACTION
2962 Include code to run legacy 32-bit programs under a
2963 64-bit kernel. You should likely turn this on, unless you're
2964 100% sure that you don't have any 32-bit programs left.
2967 bool "x32 ABI for 64-bit mode"
2969 # llvm-objcopy does not convert x86_64 .note.gnu.property or
2970 # compressed debug sections to x86_x32 properly:
2971 # https://github.com/ClangBuiltLinux/linux/issues/514
2972 # https://github.com/ClangBuiltLinux/linux/issues/1141
2973 depends on $(success,$(OBJCOPY) --version | head -n1 | grep -qv llvm)
2975 Include code to run binaries for the x32 native 32-bit ABI
2976 for 64-bit processors. An x32 process gets access to the
2977 full 64-bit register file and wide data path while leaving
2978 pointers at 32 bits for smaller memory footprint.
2982 depends on IA32_EMULATION || X86_32
2984 select OLD_SIGSUSPEND3
2988 depends on IA32_EMULATION || X86_X32_ABI
2990 config COMPAT_FOR_U64_ALIGNMENT
2996 config HAVE_ATOMIC_IOMAP
3000 source "arch/x86/kvm/Kconfig"
3002 source "arch/x86/Kconfig.assembler"