3 bool "64-bit kernel" if ARCH = "x86"
6 Say yes to build a 64-bit kernel - formerly known as x86_64
7 Say no to build a 32-bit kernel - formerly known as i386
18 select X86_DEV_DMA_OPS
19 select ARCH_USE_CMPXCHG_LOCKREF
24 select ARCH_HAS_DEBUG_STRICT_USER_COPY_CHECKS
25 select ARCH_MIGHT_HAVE_PC_PARPORT
26 select HAVE_AOUT if X86_32
27 select HAVE_UNSTABLE_SCHED_CLOCK
28 select ARCH_SUPPORTS_NUMA_BALANCING
29 select ARCH_WANTS_PROT_NUMA_PROT_NONE
32 select HAVE_PCSPKR_PLATFORM
33 select HAVE_PERF_EVENTS
34 select HAVE_IOREMAP_PROT
37 select HAVE_MEMBLOCK_NODE_MAP
38 select ARCH_DISCARD_MEMBLOCK
39 select ARCH_WANT_OPTIONAL_GPIOLIB
40 select ARCH_WANT_FRAME_POINTERS
42 select HAVE_DMA_CONTIGUOUS if !SWIOTLB
43 select HAVE_KRETPROBES
45 select HAVE_KPROBES_ON_FTRACE
46 select HAVE_FTRACE_MCOUNT_RECORD
47 select HAVE_FENTRY if X86_64
48 select HAVE_C_RECORDMCOUNT
49 select HAVE_DYNAMIC_FTRACE
50 select HAVE_DYNAMIC_FTRACE_WITH_REGS
51 select HAVE_FUNCTION_TRACER
52 select HAVE_FUNCTION_GRAPH_TRACER
53 select HAVE_FUNCTION_GRAPH_FP_TEST
54 select HAVE_FUNCTION_TRACE_MCOUNT_TEST
55 select HAVE_SYSCALL_TRACEPOINTS
56 select SYSCTL_EXCEPTION_TRACE
59 select HAVE_ARCH_TRACEHOOK
60 select HAVE_GENERIC_DMA_COHERENT if X86_32
61 select HAVE_EFFICIENT_UNALIGNED_ACCESS
62 select USER_STACKTRACE_SUPPORT
63 select HAVE_REGS_AND_STACK_ACCESS_API
64 select HAVE_DMA_API_DEBUG
65 select HAVE_KERNEL_GZIP
66 select HAVE_KERNEL_BZIP2
67 select HAVE_KERNEL_LZMA
69 select HAVE_KERNEL_LZO
70 select HAVE_KERNEL_LZ4
71 select HAVE_HW_BREAKPOINT
72 select HAVE_MIXED_BREAKPOINTS_REGS
74 select HAVE_PERF_EVENTS_NMI
76 select HAVE_PERF_USER_STACK_DUMP
77 select HAVE_DEBUG_KMEMLEAK
79 select HAVE_ALIGNED_STRUCT_PAGE if SLUB
80 select HAVE_CMPXCHG_LOCAL
81 select HAVE_CMPXCHG_DOUBLE
82 select HAVE_ARCH_KMEMCHECK
83 select HAVE_USER_RETURN_NOTIFIER
84 select ARCH_BINFMT_ELF_RANDOMIZE_PIE
85 select HAVE_ARCH_JUMP_LABEL
86 select ARCH_HAS_ATOMIC64_DEC_IF_POSITIVE
88 select GENERIC_FIND_FIRST_BIT
89 select GENERIC_IRQ_PROBE
90 select GENERIC_PENDING_IRQ if SMP
91 select GENERIC_IRQ_SHOW
92 select GENERIC_CLOCKEVENTS_MIN_ADJUST
93 select IRQ_FORCED_THREADING
94 select HAVE_BPF_JIT if X86_64
95 select HAVE_ARCH_TRANSPARENT_HUGEPAGE
97 select ARCH_HAVE_NMI_SAFE_CMPXCHG
99 select DCACHE_WORD_ACCESS
100 select GENERIC_SMP_IDLE_THREAD
101 select ARCH_WANT_IPC_PARSE_VERSION if X86_32
102 select HAVE_ARCH_SECCOMP_FILTER
103 select BUILDTIME_EXTABLE_SORT
104 select GENERIC_CMOS_UPDATE
105 select HAVE_ARCH_SOFT_DIRTY
106 select CLOCKSOURCE_WATCHDOG
107 select GENERIC_CLOCKEVENTS
108 select ARCH_CLOCKSOURCE_DATA if X86_64
109 select GENERIC_CLOCKEVENTS_BROADCAST if X86_64 || (X86_32 && X86_LOCAL_APIC)
110 select GENERIC_TIME_VSYSCALL if X86_64
111 select KTIME_SCALAR if X86_32
112 select GENERIC_STRNCPY_FROM_USER
113 select GENERIC_STRNLEN_USER
114 select HAVE_CONTEXT_TRACKING if X86_64
115 select HAVE_IRQ_TIME_ACCOUNTING
117 select MODULES_USE_ELF_REL if X86_32
118 select MODULES_USE_ELF_RELA if X86_64
119 select CLONE_BACKWARDS if X86_32
120 select ARCH_USE_BUILTIN_BSWAP
121 select OLD_SIGSUSPEND3 if X86_32 || IA32_EMULATION
122 select OLD_SIGACTION if X86_32
123 select COMPAT_OLD_SIGACTION if IA32_EMULATION
125 select HAVE_DEBUG_STACKOVERFLOW
126 select HAVE_IRQ_EXIT_ON_IRQ_STACK if X86_64
128 config INSTRUCTION_DECODER
130 depends on KPROBES || PERF_EVENTS || UPROBES
134 default "elf32-i386" if X86_32
135 default "elf64-x86-64" if X86_64
137 config ARCH_DEFCONFIG
139 default "arch/x86/configs/i386_defconfig" if X86_32
140 default "arch/x86/configs/x86_64_defconfig" if X86_64
142 config LOCKDEP_SUPPORT
145 config STACKTRACE_SUPPORT
148 config HAVE_LATENCYTOP_SUPPORT
157 config NEED_DMA_MAP_STATE
159 depends on X86_64 || INTEL_IOMMU || DMA_API_DEBUG
161 config NEED_SG_DMA_LENGTH
164 config GENERIC_ISA_DMA
166 depends on ISA_DMA_API
171 select GENERIC_BUG_RELATIVE_POINTERS if X86_64
173 config GENERIC_BUG_RELATIVE_POINTERS
176 config GENERIC_HWEIGHT
179 config ARCH_MAY_HAVE_PC_FDC
181 depends on ISA_DMA_API
183 config RWSEM_XCHGADD_ALGORITHM
186 config GENERIC_CALIBRATE_DELAY
189 config ARCH_HAS_CPU_RELAX
192 config ARCH_HAS_CACHE_LINE_SIZE
195 config ARCH_HAS_CPU_AUTOPROBE
198 config HAVE_SETUP_PER_CPU_AREA
201 config NEED_PER_CPU_EMBED_FIRST_CHUNK
204 config NEED_PER_CPU_PAGE_FIRST_CHUNK
207 config ARCH_HIBERNATION_POSSIBLE
210 config ARCH_SUSPEND_POSSIBLE
213 config ARCH_WANT_HUGE_PMD_SHARE
216 config ARCH_WANT_GENERAL_HUGETLB
227 config ARCH_SUPPORTS_OPTIMIZED_INLINING
230 config ARCH_SUPPORTS_DEBUG_PAGEALLOC
233 config HAVE_INTEL_TXT
235 depends on INTEL_IOMMU && ACPI
239 depends on X86_32 && SMP
243 depends on X86_64 && SMP
249 config X86_32_LAZY_GS
251 depends on X86_32 && !CC_STACKPROTECTOR
253 config ARCH_HWEIGHT_CFLAGS
255 default "-fcall-saved-ecx -fcall-saved-edx" if X86_32
256 default "-fcall-saved-rdi -fcall-saved-rsi -fcall-saved-rdx -fcall-saved-rcx -fcall-saved-r8 -fcall-saved-r9 -fcall-saved-r10 -fcall-saved-r11" if X86_64
258 config ARCH_SUPPORTS_UPROBES
261 source "init/Kconfig"
262 source "kernel/Kconfig.freezer"
264 menu "Processor type and features"
267 bool "DMA memory allocation support" if EXPERT
270 DMA memory allocation support allows devices with less than 32-bit
271 addressing to allocate within the first 16MB of address space.
272 Disable if no such devices will be used.
277 bool "Symmetric multi-processing support"
279 This enables support for systems with more than one CPU. If you have
280 a system with only one CPU, like most personal computers, say N. If
281 you have a system with more than one CPU, say Y.
283 If you say N here, the kernel will run on single and multiprocessor
284 machines, but will use only one CPU of a multiprocessor machine. If
285 you say Y here, the kernel will run on many, but not all,
286 singleprocessor machines. On a singleprocessor machine, the kernel
287 will run faster if you say N here.
289 Note that if you say Y here and choose architecture "586" or
290 "Pentium" under "Processor family", the kernel will not work on 486
291 architectures. Similarly, multiprocessor kernels for the "PPro"
292 architecture may not work on all Pentium based boards.
294 People using multiprocessor machines who say Y here should also say
295 Y to "Enhanced Real Time Clock Support", below. The "Advanced Power
296 Management" code will be disabled if you say Y here.
298 See also <file:Documentation/x86/i386/IO-APIC.txt>,
299 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
300 <http://www.tldp.org/docs.html#howto>.
302 If you don't know what to do here, say N.
305 bool "Support x2apic"
306 depends on X86_LOCAL_APIC && X86_64 && IRQ_REMAP
308 This enables x2apic support on CPUs that have this feature.
310 This allows 32-bit apic IDs (so it can support very large systems),
311 and accesses the local apic via MSRs not via mmio.
313 If you don't know what to do here, say N.
316 bool "Enable MPS table" if ACPI || SFI
318 depends on X86_LOCAL_APIC
320 For old smp systems that do not have proper acpi support. Newer systems
321 (esp with 64bit cpus) with acpi support, MADT and DSDT will override it
324 bool "Support for big SMP systems with more than 8 CPUs"
325 depends on X86_32 && SMP
327 This option is needed for the systems that have more than 8 CPUs
331 depends on X86_GOLDFISH
334 config X86_EXTENDED_PLATFORM
335 bool "Support for extended (non-PC) x86 platforms"
338 If you disable this option then the kernel will only support
339 standard PC platforms. (which covers the vast majority of
342 If you enable this option then you'll be able to select support
343 for the following (non-PC) 32 bit x86 platforms:
344 Goldfish (Android emulator)
348 SGI 320/540 (Visual Workstation)
349 STA2X11-based (e.g. Northville)
350 Summit/EXA (IBM x440)
351 Unisys ES7000 IA32 series
352 Moorestown MID devices
354 If you have one of these systems, or if you want to build a
355 generic distribution kernel, say Y here - otherwise say N.
359 config X86_EXTENDED_PLATFORM
360 bool "Support for extended (non-PC) x86 platforms"
363 If you disable this option then the kernel will only support
364 standard PC platforms. (which covers the vast majority of
367 If you enable this option then you'll be able to select support
368 for the following (non-PC) 64 bit x86 platforms:
373 If you have one of these systems, or if you want to build a
374 generic distribution kernel, say Y here - otherwise say N.
376 # This is an alphabetically sorted list of 64 bit extended platforms
377 # Please maintain the alphabetic order if and when there are additions
379 bool "Numascale NumaChip"
381 depends on X86_EXTENDED_PLATFORM
384 depends on X86_X2APIC
385 depends on PCI_MMCONFIG
387 Adds support for Numascale NumaChip large-SMP systems. Needed to
388 enable more than ~168 cores.
389 If you don't have one of these, you should say N here.
393 select HYPERVISOR_GUEST
395 depends on X86_64 && PCI
396 depends on X86_EXTENDED_PLATFORM
399 Support for ScaleMP vSMP systems. Say 'Y' here if this kernel is
400 supposed to run on these EM64T-based machines. Only choose this option
401 if you have one of these machines.
404 bool "SGI Ultraviolet"
406 depends on X86_EXTENDED_PLATFORM
408 depends on X86_X2APIC
410 This option is needed in order to support SGI Ultraviolet systems.
411 If you don't have one of these, you should say N here.
413 # Following is an alphabetically sorted list of 32 bit extended platforms
414 # Please maintain the alphabetic order if and when there are additions
417 bool "Goldfish (Virtual Platform)"
419 depends on X86_EXTENDED_PLATFORM
421 Enable support for the Goldfish virtual platform used primarily
422 for Android development. Unless you are building for the Android
423 Goldfish emulator say N here.
426 bool "CE4100 TV platform"
428 depends on PCI_GODIRECT
430 depends on X86_EXTENDED_PLATFORM
431 select X86_REBOOTFIXUPS
433 select OF_EARLY_FLATTREE
436 Select for the Intel CE media processor (CE4100) SOC.
437 This option compiles in support for the CE4100 SOC for settop
438 boxes and media devices.
440 config X86_WANT_INTEL_MID
441 bool "Intel MID platform support"
443 depends on X86_EXTENDED_PLATFORM
445 Select to build a kernel capable of supporting Intel MID platform
446 systems which do not have the PCI legacy interfaces (Moorestown,
447 Medfield). If you are building for a PC class system say N here.
449 if X86_WANT_INTEL_MID
455 bool "Medfield MID platform"
458 depends on X86_IO_APIC
466 select X86_PLATFORM_DEVICES
467 select MFD_INTEL_MSIC
469 Medfield is Intel's Low Power Intel Architecture (LPIA) based Moblin
470 Internet Device(MID) platform.
471 Unlike standard x86 PCs, Medfield does not have many legacy devices
472 nor standard legacy replacement devices/features. e.g. Medfield does
473 not contain i8259, i8254, HPET, legacy BIOS, most of the io ports.
477 config X86_INTEL_LPSS
478 bool "Intel Low Power Subsystem Support"
483 Select to build support for Intel Low Power Subsystem such as
484 found on Intel Lynxpoint PCH. Selecting this option enables
485 things like clock tree (common clock framework) and pincontrol
486 which are needed by the LPSS peripheral drivers.
489 bool "RDC R-321x SoC"
491 depends on X86_EXTENDED_PLATFORM
493 select X86_REBOOTFIXUPS
495 This option is needed for RDC R-321x system-on-chip, also known
497 If you don't have one of these chips, you should say N here.
499 config X86_32_NON_STANDARD
500 bool "Support non-standard 32-bit SMP architectures"
501 depends on X86_32 && SMP
502 depends on X86_EXTENDED_PLATFORM
504 This option compiles in the NUMAQ, Summit, bigsmp, ES7000,
505 STA2X11, default subarchitectures. It is intended for a generic
506 binary kernel. If you select them all, kernel will probe it
507 one by one and will fallback to default.
509 # Alphabetically sorted list of Non standard 32 bit platforms
512 bool "NUMAQ (IBM/Sequent)"
513 depends on X86_32_NON_STANDARD
518 This option is used for getting Linux to run on a NUMAQ (IBM/Sequent)
519 NUMA multiquad box. This changes the way that processors are
520 bootstrapped, and uses Clustered Logical APIC addressing mode instead
521 of Flat Logical. You will need a new lynxer.elf file to flash your
522 firmware with - send email to <Martin.Bligh@us.ibm.com>.
524 config X86_SUPPORTS_MEMORY_FAILURE
526 # MCE code calls memory_failure():
528 # On 32-bit this adds too big of NODES_SHIFT and we run out of page flags:
529 depends on !X86_NUMAQ
530 # On 32-bit SPARSEMEM adds too big of SECTIONS_WIDTH:
531 depends on X86_64 || !SPARSEMEM
532 select ARCH_SUPPORTS_MEMORY_FAILURE
535 bool "SGI 320/540 (Visual Workstation)"
536 depends on X86_32 && PCI && X86_MPPARSE && PCI_GODIRECT
537 depends on X86_32_NON_STANDARD
539 The SGI Visual Workstation series is an IA32-based workstation
540 based on SGI systems chips with some legacy PC hardware attached.
542 Say Y here to create a kernel to run on the SGI 320 or 540.
544 A kernel compiled for the Visual Workstation will run on general
545 PCs as well. See <file:Documentation/sgi-visws.txt> for details.
548 bool "STA2X11 Companion Chip Support"
549 depends on X86_32_NON_STANDARD && PCI
550 select X86_DEV_DMA_OPS
554 select ARCH_REQUIRE_GPIOLIB
557 This adds support for boards based on the STA2X11 IO-Hub,
558 a.k.a. "ConneXt". The chip is used in place of the standard
559 PC chipset, so all "standard" peripherals are missing. If this
560 option is selected the kernel will still be able to boot on
561 standard PC machines.
564 bool "Summit/EXA (IBM x440)"
565 depends on X86_32_NON_STANDARD
567 This option is needed for IBM systems that use the Summit/EXA chipset.
568 In particular, it is needed for the x440.
571 bool "Unisys ES7000 IA32 series"
572 depends on X86_32_NON_STANDARD && X86_BIGSMP
574 Support for Unisys ES7000 systems. Say 'Y' here if this kernel is
575 supposed to run on an IA32-based Unisys ES7000 system.
578 tristate "Eurobraille/Iris poweroff module"
581 The Iris machines from EuroBraille do not have APM or ACPI support
582 to shut themselves down properly. A special I/O sequence is
583 needed to do so, which is what this module does at
586 This is only for Iris machines from EuroBraille.
590 config SCHED_OMIT_FRAME_POINTER
592 prompt "Single-depth WCHAN output"
595 Calculate simpler /proc/<PID>/wchan values. If this option
596 is disabled then wchan values will recurse back to the
597 caller function. This provides more accurate wchan values,
598 at the expense of slightly more scheduling overhead.
600 If in doubt, say "Y".
602 menuconfig HYPERVISOR_GUEST
603 bool "Linux guest support"
605 Say Y here to enable options for running Linux under various hyper-
606 visors. This option enables basic hypervisor detection and platform
609 If you say N, all options in this submenu will be skipped and
610 disabled, and Linux guest support won't be built in.
615 bool "Enable paravirtualization code"
617 This changes the kernel so it can modify itself when it is run
618 under a hypervisor, potentially improving performance significantly
619 over full virtualization. However, when run without a hypervisor
620 the kernel is theoretically slower and slightly larger.
622 config PARAVIRT_DEBUG
623 bool "paravirt-ops debugging"
624 depends on PARAVIRT && DEBUG_KERNEL
626 Enable to debug paravirt_ops internals. Specifically, BUG if
627 a paravirt_op is missing when it is called.
629 config PARAVIRT_SPINLOCKS
630 bool "Paravirtualization layer for spinlocks"
631 depends on PARAVIRT && SMP
632 select UNINLINE_SPIN_UNLOCK
634 Paravirtualized spinlocks allow a pvops backend to replace the
635 spinlock implementation with something virtualization-friendly
636 (for example, block the virtual CPU rather than spinning).
638 It has a minimal impact on native kernels and gives a nice performance
639 benefit on paravirtualized KVM / Xen kernels.
641 If you are unsure how to answer this question, answer Y.
643 source "arch/x86/xen/Kconfig"
646 bool "KVM Guest support (including kvmclock)"
648 select PARAVIRT_CLOCK
651 This option enables various optimizations for running under the KVM
652 hypervisor. It includes a paravirtualized clock, so that instead
653 of relying on a PIT (or probably other) emulation by the
654 underlying device model, the host provides the guest with
655 timing infrastructure such as time of day, and system time
658 bool "Enable debug information for KVM Guests in debugfs"
659 depends on KVM_GUEST && DEBUG_FS
662 This option enables collection of various statistics for KVM guest.
663 Statistics are displayed in debugfs filesystem. Enabling this option
664 may incur significant overhead.
666 source "arch/x86/lguest/Kconfig"
668 config PARAVIRT_TIME_ACCOUNTING
669 bool "Paravirtual steal time accounting"
673 Select this option to enable fine granularity task steal time
674 accounting. Time spent executing other tasks in parallel with
675 the current vCPU is discounted from the vCPU power. To account for
676 that, there can be a small performance impact.
678 If in doubt, say N here.
680 config PARAVIRT_CLOCK
683 endif #HYPERVISOR_GUEST
691 This option adds a kernel parameter 'memtest', which allows memtest
693 memtest=0, mean disabled; -- default
694 memtest=1, mean do 1 test pattern;
696 memtest=4, mean do 4 test patterns.
697 If you are unsure how to answer this question, answer N.
699 config X86_SUMMIT_NUMA
701 depends on X86_32 && NUMA && X86_32_NON_STANDARD
703 config X86_CYCLONE_TIMER
705 depends on X86_SUMMIT
707 source "arch/x86/Kconfig.cpu"
711 prompt "HPET Timer Support" if X86_32
713 Use the IA-PC HPET (High Precision Event Timer) to manage
714 time in preference to the PIT and RTC, if a HPET is
716 HPET is the next generation timer replacing legacy 8254s.
717 The HPET provides a stable time base on SMP
718 systems, unlike the TSC, but it is more expensive to access,
719 as it is off-chip. You can find the HPET spec at
720 <http://www.intel.com/hardwaredesign/hpetspec_1.pdf>.
722 You can safely choose Y here. However, HPET will only be
723 activated if the platform and the BIOS support this feature.
724 Otherwise the 8254 will be used for timing services.
726 Choose N to continue using the legacy 8254 timer.
728 config HPET_EMULATE_RTC
730 depends on HPET_TIMER && (RTC=y || RTC=m || RTC_DRV_CMOS=m || RTC_DRV_CMOS=y)
733 def_bool y if X86_INTEL_MID
734 prompt "Intel MID APB Timer Support" if X86_INTEL_MID
736 depends on X86_INTEL_MID && SFI
738 APB timer is the replacement for 8254, HPET on X86 MID platforms.
739 The APBT provides a stable time base on SMP
740 systems, unlike the TSC, but it is more expensive to access,
741 as it is off-chip. APB timers are always running regardless of CPU
742 C states, they are used as per CPU clockevent device when possible.
744 # Mark as expert because too many people got it wrong.
745 # The code disables itself when not needed.
748 bool "Enable DMI scanning" if EXPERT
750 Enabled scanning of DMI to identify machine quirks. Say Y
751 here unless you have verified that your setup is not
752 affected by entries in the DMI blacklist. Required by PNP
756 bool "Old AMD GART IOMMU support"
758 depends on X86_64 && PCI && AMD_NB
760 Provides a driver for older AMD Athlon64/Opteron/Turion/Sempron
761 GART based hardware IOMMUs.
763 The GART supports full DMA access for devices with 32-bit access
764 limitations, on systems with more than 3 GB. This is usually needed
765 for USB, sound, many IDE/SATA chipsets and some other devices.
767 Newer systems typically have a modern AMD IOMMU, supported via
768 the CONFIG_AMD_IOMMU=y config option.
770 In normal configurations this driver is only active when needed:
771 there's more than 3 GB of memory and the system contains a
772 32-bit limited device.
777 bool "IBM Calgary IOMMU support"
779 depends on X86_64 && PCI
781 Support for hardware IOMMUs in IBM's xSeries x366 and x460
782 systems. Needed to run systems with more than 3GB of memory
783 properly with 32-bit PCI devices that do not support DAC
784 (Double Address Cycle). Calgary also supports bus level
785 isolation, where all DMAs pass through the IOMMU. This
786 prevents them from going anywhere except their intended
787 destination. This catches hard-to-find kernel bugs and
788 mis-behaving drivers and devices that do not use the DMA-API
789 properly to set up their DMA buffers. The IOMMU can be
790 turned off at boot time with the iommu=off parameter.
791 Normally the kernel will make the right choice by itself.
794 config CALGARY_IOMMU_ENABLED_BY_DEFAULT
796 prompt "Should Calgary be enabled by default?"
797 depends on CALGARY_IOMMU
799 Should Calgary be enabled by default? if you choose 'y', Calgary
800 will be used (if it exists). If you choose 'n', Calgary will not be
801 used even if it exists. If you choose 'n' and would like to use
802 Calgary anyway, pass 'iommu=calgary' on the kernel command line.
805 # need this always selected by IOMMU for the VIA workaround
809 Support for software bounce buffers used on x86-64 systems
810 which don't have a hardware IOMMU. Using this PCI devices
811 which can only access 32-bits of memory can be used on systems
812 with more than 3 GB of memory.
817 depends on CALGARY_IOMMU || GART_IOMMU || SWIOTLB || AMD_IOMMU
820 bool "Enable Maximum number of SMP Processors and NUMA Nodes"
821 depends on X86_64 && SMP && DEBUG_KERNEL
822 select CPUMASK_OFFSTACK
824 Enable maximum number of CPUS and NUMA Nodes for this architecture.
828 int "Maximum number of CPUs" if SMP && !MAXSMP
829 range 2 8 if SMP && X86_32 && !X86_BIGSMP
830 range 2 512 if SMP && !MAXSMP && !CPUMASK_OFFSTACK
831 range 2 8192 if SMP && !MAXSMP && CPUMASK_OFFSTACK && X86_64
833 default "8192" if MAXSMP
834 default "32" if SMP && (X86_NUMAQ || X86_SUMMIT || X86_BIGSMP || X86_ES7000)
837 This allows you to specify the maximum number of CPUs which this
838 kernel will support. If CPUMASK_OFFSTACK is enabled, the maximum
839 supported value is 4096, otherwise the maximum value is 512. The
840 minimum value which makes sense is 2.
842 This is purely to save memory - each supported CPU adds
843 approximately eight kilobytes to the kernel image.
846 bool "SMT (Hyperthreading) scheduler support"
849 SMT scheduler support improves the CPU scheduler's decision making
850 when dealing with Intel Pentium 4 chips with HyperThreading at a
851 cost of slightly increased overhead in some places. If unsure say
856 prompt "Multi-core scheduler support"
859 Multi-core scheduler support improves the CPU scheduler's decision
860 making when dealing with multi-core CPU chips at a cost of slightly
861 increased overhead in some places. If unsure say N here.
863 source "kernel/Kconfig.preempt"
866 bool "Local APIC support on uniprocessors"
867 depends on X86_32 && !SMP && !X86_32_NON_STANDARD && !PCI_MSI
869 A local APIC (Advanced Programmable Interrupt Controller) is an
870 integrated interrupt controller in the CPU. If you have a single-CPU
871 system which has a processor with a local APIC, you can say Y here to
872 enable and use it. If you say Y here even though your machine doesn't
873 have a local APIC, then the kernel will still run with no slowdown at
874 all. The local APIC supports CPU-generated self-interrupts (timer,
875 performance counters), and the NMI watchdog which detects hard
879 bool "IO-APIC support on uniprocessors"
880 depends on X86_UP_APIC
882 An IO-APIC (I/O Advanced Programmable Interrupt Controller) is an
883 SMP-capable replacement for PC-style interrupt controllers. Most
884 SMP systems and many recent uniprocessor systems have one.
886 If you have a single-CPU system with an IO-APIC, you can say Y here
887 to use it. If you say Y here even though your machine doesn't have
888 an IO-APIC, then the kernel will still run with no slowdown at all.
890 config X86_LOCAL_APIC
892 depends on X86_64 || SMP || X86_32_NON_STANDARD || X86_UP_APIC || PCI_MSI
896 depends on X86_64 || SMP || X86_32_NON_STANDARD || X86_UP_IOAPIC || PCI_MSI
898 config X86_VISWS_APIC
900 depends on X86_32 && X86_VISWS
902 config X86_REROUTE_FOR_BROKEN_BOOT_IRQS
903 bool "Reroute for broken boot IRQs"
904 depends on X86_IO_APIC
906 This option enables a workaround that fixes a source of
907 spurious interrupts. This is recommended when threaded
908 interrupt handling is used on systems where the generation of
909 superfluous "boot interrupts" cannot be disabled.
911 Some chipsets generate a legacy INTx "boot IRQ" when the IRQ
912 entry in the chipset's IO-APIC is masked (as, e.g. the RT
913 kernel does during interrupt handling). On chipsets where this
914 boot IRQ generation cannot be disabled, this workaround keeps
915 the original IRQ line masked so that only the equivalent "boot
916 IRQ" is delivered to the CPUs. The workaround also tells the
917 kernel to set up the IRQ handler on the boot IRQ line. In this
918 way only one interrupt is delivered to the kernel. Otherwise
919 the spurious second interrupt may cause the kernel to bring
920 down (vital) interrupt lines.
922 Only affects "broken" chipsets. Interrupt sharing may be
923 increased on these systems.
926 bool "Machine Check / overheating reporting"
929 Machine Check support allows the processor to notify the
930 kernel if it detects a problem (e.g. overheating, data corruption).
931 The action the kernel takes depends on the severity of the problem,
932 ranging from warning messages to halting the machine.
936 prompt "Intel MCE features"
937 depends on X86_MCE && X86_LOCAL_APIC
939 Additional support for intel specific MCE features such as
944 prompt "AMD MCE features"
945 depends on X86_MCE && X86_LOCAL_APIC
947 Additional support for AMD specific MCE features such as
948 the DRAM Error Threshold.
950 config X86_ANCIENT_MCE
951 bool "Support for old Pentium 5 / WinChip machine checks"
952 depends on X86_32 && X86_MCE
954 Include support for machine check handling on old Pentium 5 or WinChip
955 systems. These typically need to be enabled explicitely on the command
958 config X86_MCE_THRESHOLD
959 depends on X86_MCE_AMD || X86_MCE_INTEL
962 config X86_MCE_INJECT
964 tristate "Machine check injector support"
966 Provide support for injecting machine checks for testing purposes.
967 If you don't know what a machine check is and you don't do kernel
968 QA it is safe to say n.
970 config X86_THERMAL_VECTOR
972 depends on X86_MCE_INTEL
975 bool "Enable VM86 support" if EXPERT
979 This option is required by programs like DOSEMU to run 16-bit legacy
980 code on X86 processors. It also may be needed by software like
981 XFree86 to initialize some video cards via BIOS. Disabling this
982 option saves about 6k.
985 tristate "Toshiba Laptop support"
988 This adds a driver to safely access the System Management Mode of
989 the CPU on Toshiba portables with a genuine Toshiba BIOS. It does
990 not work on models with a Phoenix BIOS. The System Management Mode
991 is used to set the BIOS and power saving options on Toshiba portables.
993 For information on utilities to make use of this driver see the
994 Toshiba Linux utilities web site at:
995 <http://www.buzzard.org.uk/toshiba/>.
997 Say Y if you intend to run this kernel on a Toshiba portable.
1001 tristate "Dell laptop support"
1004 This adds a driver to safely access the System Management Mode
1005 of the CPU on the Dell Inspiron 8000. The System Management Mode
1006 is used to read cpu temperature and cooling fan status and to
1007 control the fans on the I8K portables.
1009 This driver has been tested only on the Inspiron 8000 but it may
1010 also work with other Dell laptops. You can force loading on other
1011 models by passing the parameter `force=1' to the module. Use at
1014 For information on utilities to make use of this driver see the
1015 I8K Linux utilities web site at:
1016 <http://people.debian.org/~dz/i8k/>
1018 Say Y if you intend to run this kernel on a Dell Inspiron 8000.
1021 config X86_REBOOTFIXUPS
1022 bool "Enable X86 board specific fixups for reboot"
1025 This enables chipset and/or board specific fixups to be done
1026 in order to get reboot to work correctly. This is only needed on
1027 some combinations of hardware and BIOS. The symptom, for which
1028 this config is intended, is when reboot ends with a stalled/hung
1031 Currently, the only fixup is for the Geode machines using
1032 CS5530A and CS5536 chipsets and the RDC R-321x SoC.
1034 Say Y if you want to enable the fixup. Currently, it's safe to
1035 enable this option even if you don't need it.
1039 tristate "CPU microcode loading support"
1040 depends on CPU_SUP_AMD || CPU_SUP_INTEL
1044 If you say Y here, you will be able to update the microcode on
1045 certain Intel and AMD processors. The Intel support is for the
1046 IA32 family, e.g. Pentium Pro, Pentium II, Pentium III, Pentium 4,
1047 Xeon etc. The AMD support is for families 0x10 and later. You will
1048 obviously need the actual microcode binary data itself which is not
1049 shipped with the Linux kernel.
1051 This option selects the general module only, you need to select
1052 at least one vendor specific module as well.
1054 To compile this driver as a module, choose M here: the module
1055 will be called microcode.
1057 config MICROCODE_INTEL
1058 bool "Intel microcode loading support"
1059 depends on MICROCODE
1063 This options enables microcode patch loading support for Intel
1066 For latest news and information on obtaining all the required
1067 Intel ingredients for this driver, check:
1068 <http://www.urbanmyth.org/microcode/>.
1070 config MICROCODE_AMD
1071 bool "AMD microcode loading support"
1072 depends on MICROCODE
1075 If you select this option, microcode patch loading support for AMD
1076 processors will be enabled.
1078 config MICROCODE_OLD_INTERFACE
1080 depends on MICROCODE
1082 config MICROCODE_INTEL_LIB
1084 depends on MICROCODE_INTEL
1086 config MICROCODE_INTEL_EARLY
1089 config MICROCODE_AMD_EARLY
1092 config MICROCODE_EARLY
1093 bool "Early load microcode"
1094 depends on MICROCODE=y && BLK_DEV_INITRD
1095 select MICROCODE_INTEL_EARLY if MICROCODE_INTEL
1096 select MICROCODE_AMD_EARLY if MICROCODE_AMD
1099 This option provides functionality to read additional microcode data
1100 at the beginning of initrd image. The data tells kernel to load
1101 microcode to CPU's as early as possible. No functional change if no
1102 microcode data is glued to the initrd, therefore it's safe to say Y.
1105 tristate "/dev/cpu/*/msr - Model-specific register support"
1107 This device gives privileged processes access to the x86
1108 Model-Specific Registers (MSRs). It is a character device with
1109 major 202 and minors 0 to 31 for /dev/cpu/0/msr to /dev/cpu/31/msr.
1110 MSR accesses are directed to a specific CPU on multi-processor
1114 tristate "/dev/cpu/*/cpuid - CPU information support"
1116 This device gives processes access to the x86 CPUID instruction to
1117 be executed on a specific processor. It is a character device
1118 with major 203 and minors 0 to 31 for /dev/cpu/0/cpuid to
1122 prompt "High Memory Support"
1123 default HIGHMEM64G if X86_NUMAQ
1129 depends on !X86_NUMAQ
1131 Linux can use up to 64 Gigabytes of physical memory on x86 systems.
1132 However, the address space of 32-bit x86 processors is only 4
1133 Gigabytes large. That means that, if you have a large amount of
1134 physical memory, not all of it can be "permanently mapped" by the
1135 kernel. The physical memory that's not permanently mapped is called
1138 If you are compiling a kernel which will never run on a machine with
1139 more than 1 Gigabyte total physical RAM, answer "off" here (default
1140 choice and suitable for most users). This will result in a "3GB/1GB"
1141 split: 3GB are mapped so that each process sees a 3GB virtual memory
1142 space and the remaining part of the 4GB virtual memory space is used
1143 by the kernel to permanently map as much physical memory as
1146 If the machine has between 1 and 4 Gigabytes physical RAM, then
1149 If more than 4 Gigabytes is used then answer "64GB" here. This
1150 selection turns Intel PAE (Physical Address Extension) mode on.
1151 PAE implements 3-level paging on IA32 processors. PAE is fully
1152 supported by Linux, PAE mode is implemented on all recent Intel
1153 processors (Pentium Pro and better). NOTE: If you say "64GB" here,
1154 then the kernel will not boot on CPUs that don't support PAE!
1156 The actual amount of total physical memory will either be
1157 auto detected or can be forced by using a kernel command line option
1158 such as "mem=256M". (Try "man bootparam" or see the documentation of
1159 your boot loader (lilo or loadlin) about how to pass options to the
1160 kernel at boot time.)
1162 If unsure, say "off".
1166 depends on !X86_NUMAQ
1168 Select this if you have a 32-bit processor and between 1 and 4
1169 gigabytes of physical RAM.
1176 Select this if you have a 32-bit processor and more than 4
1177 gigabytes of physical RAM.
1182 prompt "Memory split" if EXPERT
1186 Select the desired split between kernel and user memory.
1188 If the address range available to the kernel is less than the
1189 physical memory installed, the remaining memory will be available
1190 as "high memory". Accessing high memory is a little more costly
1191 than low memory, as it needs to be mapped into the kernel first.
1192 Note that increasing the kernel address space limits the range
1193 available to user programs, making the address space there
1194 tighter. Selecting anything other than the default 3G/1G split
1195 will also likely make your kernel incompatible with binary-only
1198 If you are not absolutely sure what you are doing, leave this
1202 bool "3G/1G user/kernel split"
1203 config VMSPLIT_3G_OPT
1205 bool "3G/1G user/kernel split (for full 1G low memory)"
1207 bool "2G/2G user/kernel split"
1208 config VMSPLIT_2G_OPT
1210 bool "2G/2G user/kernel split (for full 2G low memory)"
1212 bool "1G/3G user/kernel split"
1217 default 0xB0000000 if VMSPLIT_3G_OPT
1218 default 0x80000000 if VMSPLIT_2G
1219 default 0x78000000 if VMSPLIT_2G_OPT
1220 default 0x40000000 if VMSPLIT_1G
1226 depends on X86_32 && (HIGHMEM64G || HIGHMEM4G)
1229 bool "PAE (Physical Address Extension) Support"
1230 depends on X86_32 && !HIGHMEM4G
1232 PAE is required for NX support, and furthermore enables
1233 larger swapspace support for non-overcommit purposes. It
1234 has the cost of more pagetable lookup overhead, and also
1235 consumes more pagetable space per process.
1237 config ARCH_PHYS_ADDR_T_64BIT
1239 depends on X86_64 || X86_PAE
1241 config ARCH_DMA_ADDR_T_64BIT
1243 depends on X86_64 || HIGHMEM64G
1245 config DIRECT_GBPAGES
1246 bool "Enable 1GB pages for kernel pagetables" if EXPERT
1250 Allow the kernel linear mapping to use 1GB pages on CPUs that
1251 support it. This can improve the kernel's performance a tiny bit by
1252 reducing TLB pressure. If in doubt, say "Y".
1254 # Common NUMA Features
1256 bool "Numa Memory Allocation and Scheduler Support"
1258 depends on X86_64 || (X86_32 && HIGHMEM64G && (X86_NUMAQ || X86_BIGSMP || X86_SUMMIT && ACPI))
1259 default y if (X86_NUMAQ || X86_SUMMIT || X86_BIGSMP)
1261 Enable NUMA (Non Uniform Memory Access) support.
1263 The kernel will try to allocate memory used by a CPU on the
1264 local memory controller of the CPU and add some more
1265 NUMA awareness to the kernel.
1267 For 64-bit this is recommended if the system is Intel Core i7
1268 (or later), AMD Opteron, or EM64T NUMA.
1270 For 32-bit this is only needed on (rare) 32-bit-only platforms
1271 that support NUMA topologies, such as NUMAQ / Summit, or if you
1272 boot a 32-bit kernel on a 64-bit NUMA platform.
1274 Otherwise, you should say N.
1276 comment "NUMA (Summit) requires SMP, 64GB highmem support, ACPI"
1277 depends on X86_32 && X86_SUMMIT && (!HIGHMEM64G || !ACPI)
1281 prompt "Old style AMD Opteron NUMA detection"
1282 depends on X86_64 && NUMA && PCI
1284 Enable AMD NUMA node topology detection. You should say Y here if
1285 you have a multi processor AMD system. This uses an old method to
1286 read the NUMA configuration directly from the builtin Northbridge
1287 of Opteron. It is recommended to use X86_64_ACPI_NUMA instead,
1288 which also takes priority if both are compiled in.
1290 config X86_64_ACPI_NUMA
1292 prompt "ACPI NUMA detection"
1293 depends on X86_64 && NUMA && ACPI && PCI
1296 Enable ACPI SRAT based node topology detection.
1298 # Some NUMA nodes have memory ranges that span
1299 # other nodes. Even though a pfn is valid and
1300 # between a node's start and end pfns, it may not
1301 # reside on that node. See memmap_init_zone()
1303 config NODES_SPAN_OTHER_NODES
1305 depends on X86_64_ACPI_NUMA
1308 bool "NUMA emulation"
1311 Enable NUMA emulation. A flat machine will be split
1312 into virtual nodes when booted with "numa=fake=N", where N is the
1313 number of nodes. This is only useful for debugging.
1316 int "Maximum NUMA Nodes (as a power of 2)" if !MAXSMP
1318 default "10" if MAXSMP
1319 default "6" if X86_64
1320 default "4" if X86_NUMAQ
1322 depends on NEED_MULTIPLE_NODES
1324 Specify the maximum number of NUMA Nodes available on the target
1325 system. Increases memory reserved to accommodate various tables.
1327 config ARCH_HAVE_MEMORY_PRESENT
1329 depends on X86_32 && DISCONTIGMEM
1331 config NEED_NODE_MEMMAP_SIZE
1333 depends on X86_32 && (DISCONTIGMEM || SPARSEMEM)
1335 config ARCH_FLATMEM_ENABLE
1337 depends on X86_32 && !NUMA
1339 config ARCH_DISCONTIGMEM_ENABLE
1341 depends on NUMA && X86_32
1343 config ARCH_DISCONTIGMEM_DEFAULT
1345 depends on NUMA && X86_32
1347 config ARCH_SPARSEMEM_ENABLE
1349 depends on X86_64 || NUMA || X86_32 || X86_32_NON_STANDARD
1350 select SPARSEMEM_STATIC if X86_32
1351 select SPARSEMEM_VMEMMAP_ENABLE if X86_64
1353 config ARCH_SPARSEMEM_DEFAULT
1357 config ARCH_SELECT_MEMORY_MODEL
1359 depends on ARCH_SPARSEMEM_ENABLE
1361 config ARCH_MEMORY_PROBE
1362 bool "Enable sysfs memory/probe interface"
1363 depends on X86_64 && MEMORY_HOTPLUG
1365 This option enables a sysfs memory/probe interface for testing.
1366 See Documentation/memory-hotplug.txt for more information.
1367 If you are unsure how to answer this question, answer N.
1369 config ARCH_PROC_KCORE_TEXT
1371 depends on X86_64 && PROC_KCORE
1373 config ILLEGAL_POINTER_VALUE
1376 default 0xdead000000000000 if X86_64
1381 bool "Allocate 3rd-level pagetables from highmem"
1384 The VM uses one page table entry for each page of physical memory.
1385 For systems with a lot of RAM, this can be wasteful of precious
1386 low memory. Setting this option will put user-space page table
1387 entries in high memory.
1389 config X86_CHECK_BIOS_CORRUPTION
1390 bool "Check for low memory corruption"
1392 Periodically check for memory corruption in low memory, which
1393 is suspected to be caused by BIOS. Even when enabled in the
1394 configuration, it is disabled at runtime. Enable it by
1395 setting "memory_corruption_check=1" on the kernel command
1396 line. By default it scans the low 64k of memory every 60
1397 seconds; see the memory_corruption_check_size and
1398 memory_corruption_check_period parameters in
1399 Documentation/kernel-parameters.txt to adjust this.
1401 When enabled with the default parameters, this option has
1402 almost no overhead, as it reserves a relatively small amount
1403 of memory and scans it infrequently. It both detects corruption
1404 and prevents it from affecting the running system.
1406 It is, however, intended as a diagnostic tool; if repeatable
1407 BIOS-originated corruption always affects the same memory,
1408 you can use memmap= to prevent the kernel from using that
1411 config X86_BOOTPARAM_MEMORY_CORRUPTION_CHECK
1412 bool "Set the default setting of memory_corruption_check"
1413 depends on X86_CHECK_BIOS_CORRUPTION
1416 Set whether the default state of memory_corruption_check is
1419 config X86_RESERVE_LOW
1420 int "Amount of low memory, in kilobytes, to reserve for the BIOS"
1424 Specify the amount of low memory to reserve for the BIOS.
1426 The first page contains BIOS data structures that the kernel
1427 must not use, so that page must always be reserved.
1429 By default we reserve the first 64K of physical RAM, as a
1430 number of BIOSes are known to corrupt that memory range
1431 during events such as suspend/resume or monitor cable
1432 insertion, so it must not be used by the kernel.
1434 You can set this to 4 if you are absolutely sure that you
1435 trust the BIOS to get all its memory reservations and usages
1436 right. If you know your BIOS have problems beyond the
1437 default 64K area, you can set this to 640 to avoid using the
1438 entire low memory range.
1440 If you have doubts about the BIOS (e.g. suspend/resume does
1441 not work or there's kernel crashes after certain hardware
1442 hotplug events) then you might want to enable
1443 X86_CHECK_BIOS_CORRUPTION=y to allow the kernel to check
1444 typical corruption patterns.
1446 Leave this to the default value of 64 if you are unsure.
1448 config MATH_EMULATION
1450 prompt "Math emulation" if X86_32
1452 Linux can emulate a math coprocessor (used for floating point
1453 operations) if you don't have one. 486DX and Pentium processors have
1454 a math coprocessor built in, 486SX and 386 do not, unless you added
1455 a 487DX or 387, respectively. (The messages during boot time can
1456 give you some hints here ["man dmesg"].) Everyone needs either a
1457 coprocessor or this emulation.
1459 If you don't have a math coprocessor, you need to say Y here; if you
1460 say Y here even though you have a coprocessor, the coprocessor will
1461 be used nevertheless. (This behavior can be changed with the kernel
1462 command line option "no387", which comes handy if your coprocessor
1463 is broken. Try "man bootparam" or see the documentation of your boot
1464 loader (lilo or loadlin) about how to pass options to the kernel at
1465 boot time.) This means that it is a good idea to say Y here if you
1466 intend to use this kernel on different machines.
1468 More information about the internals of the Linux math coprocessor
1469 emulation can be found in <file:arch/x86/math-emu/README>.
1471 If you are not sure, say Y; apart from resulting in a 66 KB bigger
1472 kernel, it won't hurt.
1476 prompt "MTRR (Memory Type Range Register) support" if EXPERT
1478 On Intel P6 family processors (Pentium Pro, Pentium II and later)
1479 the Memory Type Range Registers (MTRRs) may be used to control
1480 processor access to memory ranges. This is most useful if you have
1481 a video (VGA) card on a PCI or AGP bus. Enabling write-combining
1482 allows bus write transfers to be combined into a larger transfer
1483 before bursting over the PCI/AGP bus. This can increase performance
1484 of image write operations 2.5 times or more. Saying Y here creates a
1485 /proc/mtrr file which may be used to manipulate your processor's
1486 MTRRs. Typically the X server should use this.
1488 This code has a reasonably generic interface so that similar
1489 control registers on other processors can be easily supported
1492 The Cyrix 6x86, 6x86MX and M II processors have Address Range
1493 Registers (ARRs) which provide a similar functionality to MTRRs. For
1494 these, the ARRs are used to emulate the MTRRs.
1495 The AMD K6-2 (stepping 8 and above) and K6-3 processors have two
1496 MTRRs. The Centaur C6 (WinChip) has 8 MCRs, allowing
1497 write-combining. All of these processors are supported by this code
1498 and it makes sense to say Y here if you have one of them.
1500 Saying Y here also fixes a problem with buggy SMP BIOSes which only
1501 set the MTRRs for the boot CPU and not for the secondary CPUs. This
1502 can lead to all sorts of problems, so it's good to say Y here.
1504 You can safely say Y even if your machine doesn't have MTRRs, you'll
1505 just add about 9 KB to your kernel.
1507 See <file:Documentation/x86/mtrr.txt> for more information.
1509 config MTRR_SANITIZER
1511 prompt "MTRR cleanup support"
1514 Convert MTRR layout from continuous to discrete, so X drivers can
1515 add writeback entries.
1517 Can be disabled with disable_mtrr_cleanup on the kernel command line.
1518 The largest mtrr entry size for a continuous block can be set with
1523 config MTRR_SANITIZER_ENABLE_DEFAULT
1524 int "MTRR cleanup enable value (0-1)"
1527 depends on MTRR_SANITIZER
1529 Enable mtrr cleanup default value
1531 config MTRR_SANITIZER_SPARE_REG_NR_DEFAULT
1532 int "MTRR cleanup spare reg num (0-7)"
1535 depends on MTRR_SANITIZER
1537 mtrr cleanup spare entries default, it can be changed via
1538 mtrr_spare_reg_nr=N on the kernel command line.
1542 prompt "x86 PAT support" if EXPERT
1545 Use PAT attributes to setup page level cache control.
1547 PATs are the modern equivalents of MTRRs and are much more
1548 flexible than MTRRs.
1550 Say N here if you see bootup problems (boot crash, boot hang,
1551 spontaneous reboots) or a non-working video driver.
1555 config ARCH_USES_PG_UNCACHED
1561 prompt "x86 architectural random number generator" if EXPERT
1563 Enable the x86 architectural RDRAND instruction
1564 (Intel Bull Mountain technology) to generate random numbers.
1565 If supported, this is a high bandwidth, cryptographically
1566 secure hardware random number generator.
1570 prompt "Supervisor Mode Access Prevention" if EXPERT
1572 Supervisor Mode Access Prevention (SMAP) is a security
1573 feature in newer Intel processors. There is a small
1574 performance cost if this enabled and turned on; there is
1575 also a small increase in the kernel size if this is enabled.
1580 bool "EFI runtime service support"
1584 This enables the kernel to use EFI runtime services that are
1585 available (such as the EFI variable services).
1587 This option is only useful on systems that have EFI firmware.
1588 In addition, you should use the latest ELILO loader available
1589 at <http://elilo.sourceforge.net> in order to take advantage
1590 of EFI runtime services. However, even with this option, the
1591 resultant kernel should continue to boot on existing non-EFI
1595 bool "EFI stub support"
1598 This kernel feature allows a bzImage to be loaded directly
1599 by EFI firmware without the use of a bootloader.
1601 See Documentation/efi-stub.txt for more information.
1605 prompt "Enable seccomp to safely compute untrusted bytecode"
1607 This kernel feature is useful for number crunching applications
1608 that may need to compute untrusted bytecode during their
1609 execution. By using pipes or other transports made available to
1610 the process as file descriptors supporting the read/write
1611 syscalls, it's possible to isolate those applications in
1612 their own address space using seccomp. Once seccomp is
1613 enabled via prctl(PR_SET_SECCOMP), it cannot be disabled
1614 and the task is only allowed to execute a few safe syscalls
1615 defined by each seccomp mode.
1617 If unsure, say Y. Only embedded should say N here.
1619 config CC_STACKPROTECTOR
1620 bool "Enable -fstack-protector buffer overflow detection"
1622 This option turns on the -fstack-protector GCC feature. This
1623 feature puts, at the beginning of functions, a canary value on
1624 the stack just before the return address, and validates
1625 the value just before actually returning. Stack based buffer
1626 overflows (that need to overwrite this return address) now also
1627 overwrite the canary, which gets detected and the attack is then
1628 neutralized via a kernel panic.
1630 This feature requires gcc version 4.2 or above, or a distribution
1631 gcc with the feature backported. Older versions are automatically
1632 detected and for those versions, this configuration option is
1633 ignored. (and a warning is printed during bootup)
1635 source kernel/Kconfig.hz
1638 bool "kexec system call"
1640 kexec is a system call that implements the ability to shutdown your
1641 current kernel, and to start another kernel. It is like a reboot
1642 but it is independent of the system firmware. And like a reboot
1643 you can start any kernel with it, not just Linux.
1645 The name comes from the similarity to the exec system call.
1647 It is an ongoing process to be certain the hardware in a machine
1648 is properly shutdown, so do not be surprised if this code does not
1649 initially work for you. As of this writing the exact hardware
1650 interface is strongly in flux, so no good recommendation can be
1654 bool "kernel crash dumps"
1655 depends on X86_64 || (X86_32 && HIGHMEM)
1657 Generate crash dump after being started by kexec.
1658 This should be normally only set in special crash dump kernels
1659 which are loaded in the main kernel with kexec-tools into
1660 a specially reserved region and then later executed after
1661 a crash by kdump/kexec. The crash dump kernel must be compiled
1662 to a memory address not used by the main kernel or BIOS using
1663 PHYSICAL_START, or it must be built as a relocatable image
1664 (CONFIG_RELOCATABLE=y).
1665 For more details see Documentation/kdump/kdump.txt
1669 depends on KEXEC && HIBERNATION
1671 Jump between original kernel and kexeced kernel and invoke
1672 code in physical address mode via KEXEC
1674 config PHYSICAL_START
1675 hex "Physical address where the kernel is loaded" if (EXPERT || CRASH_DUMP)
1678 This gives the physical address where the kernel is loaded.
1680 If kernel is a not relocatable (CONFIG_RELOCATABLE=n) then
1681 bzImage will decompress itself to above physical address and
1682 run from there. Otherwise, bzImage will run from the address where
1683 it has been loaded by the boot loader and will ignore above physical
1686 In normal kdump cases one does not have to set/change this option
1687 as now bzImage can be compiled as a completely relocatable image
1688 (CONFIG_RELOCATABLE=y) and be used to load and run from a different
1689 address. This option is mainly useful for the folks who don't want
1690 to use a bzImage for capturing the crash dump and want to use a
1691 vmlinux instead. vmlinux is not relocatable hence a kernel needs
1692 to be specifically compiled to run from a specific memory area
1693 (normally a reserved region) and this option comes handy.
1695 So if you are using bzImage for capturing the crash dump,
1696 leave the value here unchanged to 0x1000000 and set
1697 CONFIG_RELOCATABLE=y. Otherwise if you plan to use vmlinux
1698 for capturing the crash dump change this value to start of
1699 the reserved region. In other words, it can be set based on
1700 the "X" value as specified in the "crashkernel=YM@XM"
1701 command line boot parameter passed to the panic-ed
1702 kernel. Please take a look at Documentation/kdump/kdump.txt
1703 for more details about crash dumps.
1705 Usage of bzImage for capturing the crash dump is recommended as
1706 one does not have to build two kernels. Same kernel can be used
1707 as production kernel and capture kernel. Above option should have
1708 gone away after relocatable bzImage support is introduced. But it
1709 is present because there are users out there who continue to use
1710 vmlinux for dump capture. This option should go away down the
1713 Don't change this unless you know what you are doing.
1716 bool "Build a relocatable kernel"
1719 This builds a kernel image that retains relocation information
1720 so it can be loaded someplace besides the default 1MB.
1721 The relocations tend to make the kernel binary about 10% larger,
1722 but are discarded at runtime.
1724 One use is for the kexec on panic case where the recovery kernel
1725 must live at a different physical address than the primary
1728 Note: If CONFIG_RELOCATABLE=y, then the kernel runs from the address
1729 it has been loaded at and the compile time physical address
1730 (CONFIG_PHYSICAL_START) is ignored.
1732 # Relocation on x86-32 needs some additional build support
1733 config X86_NEED_RELOCS
1735 depends on X86_32 && RELOCATABLE
1737 config PHYSICAL_ALIGN
1738 hex "Alignment value to which kernel should be aligned"
1740 range 0x2000 0x1000000 if X86_32
1741 range 0x200000 0x1000000 if X86_64
1743 This value puts the alignment restrictions on physical address
1744 where kernel is loaded and run from. Kernel is compiled for an
1745 address which meets above alignment restriction.
1747 If bootloader loads the kernel at a non-aligned address and
1748 CONFIG_RELOCATABLE is set, kernel will move itself to nearest
1749 address aligned to above value and run from there.
1751 If bootloader loads the kernel at a non-aligned address and
1752 CONFIG_RELOCATABLE is not set, kernel will ignore the run time
1753 load address and decompress itself to the address it has been
1754 compiled for and run from there. The address for which kernel is
1755 compiled already meets above alignment restrictions. Hence the
1756 end result is that kernel runs from a physical address meeting
1757 above alignment restrictions.
1759 On 32-bit this value must be a multiple of 0x2000. On 64-bit
1760 this value must be a multiple of 0x200000.
1762 Don't change this unless you know what you are doing.
1765 bool "Support for hot-pluggable CPUs"
1768 Say Y here to allow turning CPUs off and on. CPUs can be
1769 controlled through /sys/devices/system/cpu.
1770 ( Note: power management support will enable this option
1771 automatically on SMP systems. )
1772 Say N if you want to disable CPU hotplug.
1774 config BOOTPARAM_HOTPLUG_CPU0
1775 bool "Set default setting of cpu0_hotpluggable"
1777 depends on HOTPLUG_CPU
1779 Set whether default state of cpu0_hotpluggable is on or off.
1781 Say Y here to enable CPU0 hotplug by default. If this switch
1782 is turned on, there is no need to give cpu0_hotplug kernel
1783 parameter and the CPU0 hotplug feature is enabled by default.
1785 Please note: there are two known CPU0 dependencies if you want
1786 to enable the CPU0 hotplug feature either by this switch or by
1787 cpu0_hotplug kernel parameter.
1789 First, resume from hibernate or suspend always starts from CPU0.
1790 So hibernate and suspend are prevented if CPU0 is offline.
1792 Second dependency is PIC interrupts always go to CPU0. CPU0 can not
1793 offline if any interrupt can not migrate out of CPU0. There may
1794 be other CPU0 dependencies.
1796 Please make sure the dependencies are under your control before
1797 you enable this feature.
1799 Say N if you don't want to enable CPU0 hotplug feature by default.
1800 You still can enable the CPU0 hotplug feature at boot by kernel
1801 parameter cpu0_hotplug.
1803 config DEBUG_HOTPLUG_CPU0
1805 prompt "Debug CPU0 hotplug"
1806 depends on HOTPLUG_CPU
1808 Enabling this option offlines CPU0 (if CPU0 can be offlined) as
1809 soon as possible and boots up userspace with CPU0 offlined. User
1810 can online CPU0 back after boot time.
1812 To debug CPU0 hotplug, you need to enable CPU0 offline/online
1813 feature by either turning on CONFIG_BOOTPARAM_HOTPLUG_CPU0 during
1814 compilation or giving cpu0_hotplug kernel parameter at boot.
1820 prompt "Compat VDSO support"
1821 depends on X86_32 || IA32_EMULATION
1823 Map the 32-bit VDSO to the predictable old-style address too.
1825 Say N here if you are running a sufficiently recent glibc
1826 version (2.3.3 or later), to remove the high-mapped
1827 VDSO mapping and to exclusively use the randomized VDSO.
1832 bool "Built-in kernel command line"
1834 Allow for specifying boot arguments to the kernel at
1835 build time. On some systems (e.g. embedded ones), it is
1836 necessary or convenient to provide some or all of the
1837 kernel boot arguments with the kernel itself (that is,
1838 to not rely on the boot loader to provide them.)
1840 To compile command line arguments into the kernel,
1841 set this option to 'Y', then fill in the
1842 the boot arguments in CONFIG_CMDLINE.
1844 Systems with fully functional boot loaders (i.e. non-embedded)
1845 should leave this option set to 'N'.
1848 string "Built-in kernel command string"
1849 depends on CMDLINE_BOOL
1852 Enter arguments here that should be compiled into the kernel
1853 image and used at boot time. If the boot loader provides a
1854 command line at boot time, it is appended to this string to
1855 form the full kernel command line, when the system boots.
1857 However, you can use the CONFIG_CMDLINE_OVERRIDE option to
1858 change this behavior.
1860 In most cases, the command line (whether built-in or provided
1861 by the boot loader) should specify the device for the root
1864 config CMDLINE_OVERRIDE
1865 bool "Built-in command line overrides boot loader arguments"
1866 depends on CMDLINE_BOOL
1868 Set this option to 'Y' to have the kernel ignore the boot loader
1869 command line, and use ONLY the built-in command line.
1871 This is used to work around broken boot loaders. This should
1872 be set to 'N' under normal conditions.
1876 config ARCH_ENABLE_MEMORY_HOTPLUG
1878 depends on X86_64 || (X86_32 && HIGHMEM)
1880 config ARCH_ENABLE_MEMORY_HOTREMOVE
1882 depends on MEMORY_HOTPLUG
1884 config USE_PERCPU_NUMA_NODE_ID
1888 config ARCH_ENABLE_SPLIT_PMD_PTLOCK
1890 depends on X86_64 || X86_PAE
1892 menu "Power management and ACPI options"
1894 config ARCH_HIBERNATION_HEADER
1896 depends on X86_64 && HIBERNATION
1898 source "kernel/power/Kconfig"
1900 source "drivers/acpi/Kconfig"
1902 source "drivers/sfi/Kconfig"
1909 tristate "APM (Advanced Power Management) BIOS support"
1910 depends on X86_32 && PM_SLEEP
1912 APM is a BIOS specification for saving power using several different
1913 techniques. This is mostly useful for battery powered laptops with
1914 APM compliant BIOSes. If you say Y here, the system time will be
1915 reset after a RESUME operation, the /proc/apm device will provide
1916 battery status information, and user-space programs will receive
1917 notification of APM "events" (e.g. battery status change).
1919 If you select "Y" here, you can disable actual use of the APM
1920 BIOS by passing the "apm=off" option to the kernel at boot time.
1922 Note that the APM support is almost completely disabled for
1923 machines with more than one CPU.
1925 In order to use APM, you will need supporting software. For location
1926 and more information, read <file:Documentation/power/apm-acpi.txt>
1927 and the Battery Powered Linux mini-HOWTO, available from
1928 <http://www.tldp.org/docs.html#howto>.
1930 This driver does not spin down disk drives (see the hdparm(8)
1931 manpage ("man 8 hdparm") for that), and it doesn't turn off
1932 VESA-compliant "green" monitors.
1934 This driver does not support the TI 4000M TravelMate and the ACER
1935 486/DX4/75 because they don't have compliant BIOSes. Many "green"
1936 desktop machines also don't have compliant BIOSes, and this driver
1937 may cause those machines to panic during the boot phase.
1939 Generally, if you don't have a battery in your machine, there isn't
1940 much point in using this driver and you should say N. If you get
1941 random kernel OOPSes or reboots that don't seem to be related to
1942 anything, try disabling/enabling this option (or disabling/enabling
1945 Some other things you should try when experiencing seemingly random,
1948 1) make sure that you have enough swap space and that it is
1950 2) pass the "no-hlt" option to the kernel
1951 3) switch on floating point emulation in the kernel and pass
1952 the "no387" option to the kernel
1953 4) pass the "floppy=nodma" option to the kernel
1954 5) pass the "mem=4M" option to the kernel (thereby disabling
1955 all but the first 4 MB of RAM)
1956 6) make sure that the CPU is not over clocked.
1957 7) read the sig11 FAQ at <http://www.bitwizard.nl/sig11/>
1958 8) disable the cache from your BIOS settings
1959 9) install a fan for the video card or exchange video RAM
1960 10) install a better fan for the CPU
1961 11) exchange RAM chips
1962 12) exchange the motherboard.
1964 To compile this driver as a module, choose M here: the
1965 module will be called apm.
1969 config APM_IGNORE_USER_SUSPEND
1970 bool "Ignore USER SUSPEND"
1972 This option will ignore USER SUSPEND requests. On machines with a
1973 compliant APM BIOS, you want to say N. However, on the NEC Versa M
1974 series notebooks, it is necessary to say Y because of a BIOS bug.
1976 config APM_DO_ENABLE
1977 bool "Enable PM at boot time"
1979 Enable APM features at boot time. From page 36 of the APM BIOS
1980 specification: "When disabled, the APM BIOS does not automatically
1981 power manage devices, enter the Standby State, enter the Suspend
1982 State, or take power saving steps in response to CPU Idle calls."
1983 This driver will make CPU Idle calls when Linux is idle (unless this
1984 feature is turned off -- see "Do CPU IDLE calls", below). This
1985 should always save battery power, but more complicated APM features
1986 will be dependent on your BIOS implementation. You may need to turn
1987 this option off if your computer hangs at boot time when using APM
1988 support, or if it beeps continuously instead of suspending. Turn
1989 this off if you have a NEC UltraLite Versa 33/C or a Toshiba
1990 T400CDT. This is off by default since most machines do fine without
1995 bool "Make CPU Idle calls when idle"
1997 Enable calls to APM CPU Idle/CPU Busy inside the kernel's idle loop.
1998 On some machines, this can activate improved power savings, such as
1999 a slowed CPU clock rate, when the machine is idle. These idle calls
2000 are made after the idle loop has run for some length of time (e.g.,
2001 333 mS). On some machines, this will cause a hang at boot time or
2002 whenever the CPU becomes idle. (On machines with more than one CPU,
2003 this option does nothing.)
2005 config APM_DISPLAY_BLANK
2006 bool "Enable console blanking using APM"
2008 Enable console blanking using the APM. Some laptops can use this to
2009 turn off the LCD backlight when the screen blanker of the Linux
2010 virtual console blanks the screen. Note that this is only used by
2011 the virtual console screen blanker, and won't turn off the backlight
2012 when using the X Window system. This also doesn't have anything to
2013 do with your VESA-compliant power-saving monitor. Further, this
2014 option doesn't work for all laptops -- it might not turn off your
2015 backlight at all, or it might print a lot of errors to the console,
2016 especially if you are using gpm.
2018 config APM_ALLOW_INTS
2019 bool "Allow interrupts during APM BIOS calls"
2021 Normally we disable external interrupts while we are making calls to
2022 the APM BIOS as a measure to lessen the effects of a badly behaving
2023 BIOS implementation. The BIOS should reenable interrupts if it
2024 needs to. Unfortunately, some BIOSes do not -- especially those in
2025 many of the newer IBM Thinkpads. If you experience hangs when you
2026 suspend, try setting this to Y. Otherwise, say N.
2030 source "drivers/cpufreq/Kconfig"
2032 source "drivers/cpuidle/Kconfig"
2034 source "drivers/idle/Kconfig"
2039 menu "Bus options (PCI etc.)"
2045 Find out whether you have a PCI motherboard. PCI is the name of a
2046 bus system, i.e. the way the CPU talks to the other stuff inside
2047 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
2048 VESA. If you have PCI, say Y, otherwise N.
2051 prompt "PCI access mode"
2052 depends on X86_32 && PCI
2055 On PCI systems, the BIOS can be used to detect the PCI devices and
2056 determine their configuration. However, some old PCI motherboards
2057 have BIOS bugs and may crash if this is done. Also, some embedded
2058 PCI-based systems don't have any BIOS at all. Linux can also try to
2059 detect the PCI hardware directly without using the BIOS.
2061 With this option, you can specify how Linux should detect the
2062 PCI devices. If you choose "BIOS", the BIOS will be used,
2063 if you choose "Direct", the BIOS won't be used, and if you
2064 choose "MMConfig", then PCI Express MMCONFIG will be used.
2065 If you choose "Any", the kernel will try MMCONFIG, then the
2066 direct access method and falls back to the BIOS if that doesn't
2067 work. If unsure, go with the default, which is "Any".
2072 config PCI_GOMMCONFIG
2089 depends on X86_32 && PCI && (PCI_GOBIOS || PCI_GOANY)
2091 # x86-64 doesn't support PCI BIOS access from long mode so always go direct.
2094 depends on PCI && (X86_64 || (PCI_GODIRECT || PCI_GOANY || PCI_GOOLPC || PCI_GOMMCONFIG))
2098 depends on X86_32 && PCI && (ACPI || SFI) && (PCI_GOMMCONFIG || PCI_GOANY)
2102 depends on PCI && OLPC && (PCI_GOOLPC || PCI_GOANY)
2106 depends on PCI && XEN
2114 bool "Support mmconfig PCI config space access"
2115 depends on X86_64 && PCI && ACPI
2117 config PCI_CNB20LE_QUIRK
2118 bool "Read CNB20LE Host Bridge Windows" if EXPERT
2121 Read the PCI windows out of the CNB20LE host bridge. This allows
2122 PCI hotplug to work on systems with the CNB20LE chipset which do
2125 There's no public spec for this chipset, and this functionality
2126 is known to be incomplete.
2128 You should say N unless you know you need this.
2130 source "drivers/pci/pcie/Kconfig"
2132 source "drivers/pci/Kconfig"
2134 # x86_64 have no ISA slots, but can have ISA-style DMA.
2136 bool "ISA-style DMA support" if (X86_64 && EXPERT)
2139 Enables ISA-style DMA support for devices requiring such controllers.
2147 Find out whether you have ISA slots on your motherboard. ISA is the
2148 name of a bus system, i.e. the way the CPU talks to the other stuff
2149 inside your box. Other bus systems are PCI, EISA, MicroChannel
2150 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
2151 newer boards don't support it. If you have ISA, say Y, otherwise N.
2157 The Extended Industry Standard Architecture (EISA) bus was
2158 developed as an open alternative to the IBM MicroChannel bus.
2160 The EISA bus provided some of the features of the IBM MicroChannel
2161 bus while maintaining backward compatibility with cards made for
2162 the older ISA bus. The EISA bus saw limited use between 1988 and
2163 1995 when it was made obsolete by the PCI bus.
2165 Say Y here if you are building a kernel for an EISA-based machine.
2169 source "drivers/eisa/Kconfig"
2172 tristate "NatSemi SCx200 support"
2174 This provides basic support for National Semiconductor's
2175 (now AMD's) Geode processors. The driver probes for the
2176 PCI-IDs of several on-chip devices, so its a good dependency
2177 for other scx200_* drivers.
2179 If compiled as a module, the driver is named scx200.
2181 config SCx200HR_TIMER
2182 tristate "NatSemi SCx200 27MHz High-Resolution Timer Support"
2186 This driver provides a clocksource built upon the on-chip
2187 27MHz high-resolution timer. Its also a workaround for
2188 NSC Geode SC-1100's buggy TSC, which loses time when the
2189 processor goes idle (as is done by the scheduler). The
2190 other workaround is idle=poll boot option.
2193 bool "One Laptop Per Child support"
2200 Add support for detecting the unique features of the OLPC
2204 bool "OLPC XO-1 Power Management"
2205 depends on OLPC && MFD_CS5535 && PM_SLEEP
2208 Add support for poweroff and suspend of the OLPC XO-1 laptop.
2211 bool "OLPC XO-1 Real Time Clock"
2212 depends on OLPC_XO1_PM && RTC_DRV_CMOS
2214 Add support for the XO-1 real time clock, which can be used as a
2215 programmable wakeup source.
2218 bool "OLPC XO-1 SCI extras"
2219 depends on OLPC && OLPC_XO1_PM
2225 Add support for SCI-based features of the OLPC XO-1 laptop:
2226 - EC-driven system wakeups
2230 - AC adapter status updates
2231 - Battery status updates
2233 config OLPC_XO15_SCI
2234 bool "OLPC XO-1.5 SCI extras"
2235 depends on OLPC && ACPI
2238 Add support for SCI-based features of the OLPC XO-1.5 laptop:
2239 - EC-driven system wakeups
2240 - AC adapter status updates
2241 - Battery status updates
2244 bool "PCEngines ALIX System Support (LED setup)"
2247 This option enables system support for the PCEngines ALIX.
2248 At present this just sets up LEDs for GPIO control on
2249 ALIX2/3/6 boards. However, other system specific setup should
2252 Note: You must still enable the drivers for GPIO and LED support
2253 (GPIO_CS5535 & LEDS_GPIO) to actually use the LEDs
2255 Note: You have to set alix.force=1 for boards with Award BIOS.
2258 bool "Soekris Engineering net5501 System Support (LEDS, GPIO, etc)"
2261 This option enables system support for the Soekris Engineering net5501.
2264 bool "Traverse Technologies GEOS System Support (LEDS, GPIO, etc)"
2268 This option enables system support for the Traverse Technologies GEOS.
2271 bool "Technologic Systems TS-5500 platform support"
2273 select CHECK_SIGNATURE
2277 This option enables system support for the Technologic Systems TS-5500.
2283 depends on CPU_SUP_AMD && PCI
2285 source "drivers/pcmcia/Kconfig"
2287 source "drivers/pci/hotplug/Kconfig"
2290 tristate "RapidIO support"
2294 If enabled this option will include drivers and the core
2295 infrastructure code to support RapidIO interconnect devices.
2297 source "drivers/rapidio/Kconfig"
2300 bool "Mark VGA/VBE/EFI FB as generic system framebuffer"
2302 Firmwares often provide initial graphics framebuffers so the BIOS,
2303 bootloader or kernel can show basic video-output during boot for
2304 user-guidance and debugging. Historically, x86 used the VESA BIOS
2305 Extensions and EFI-framebuffers for this, which are mostly limited
2307 This option, if enabled, marks VGA/VBE/EFI framebuffers as generic
2308 framebuffers so the new generic system-framebuffer drivers can be
2309 used on x86. If the framebuffer is not compatible with the generic
2310 modes, it is adverticed as fallback platform framebuffer so legacy
2311 drivers like efifb, vesafb and uvesafb can pick it up.
2312 If this option is not selected, all system framebuffers are always
2313 marked as fallback platform framebuffers as usual.
2315 Note: Legacy fbdev drivers, including vesafb, efifb, uvesafb, will
2316 not be able to pick up generic system framebuffers if this option
2317 is selected. You are highly encouraged to enable simplefb as
2318 replacement if you select this option. simplefb can correctly deal
2319 with generic system framebuffers. But you should still keep vesafb
2320 and others enabled as fallback if a system framebuffer is
2321 incompatible with simplefb.
2328 menu "Executable file formats / Emulations"
2330 source "fs/Kconfig.binfmt"
2332 config IA32_EMULATION
2333 bool "IA32 Emulation"
2336 select COMPAT_BINFMT_ELF
2339 Include code to run legacy 32-bit programs under a
2340 64-bit kernel. You should likely turn this on, unless you're
2341 100% sure that you don't have any 32-bit programs left.
2344 tristate "IA32 a.out support"
2345 depends on IA32_EMULATION
2347 Support old a.out binaries in the 32bit emulation.
2350 bool "x32 ABI for 64-bit mode"
2351 depends on X86_64 && IA32_EMULATION
2353 Include code to run binaries for the x32 native 32-bit ABI
2354 for 64-bit processors. An x32 process gets access to the
2355 full 64-bit register file and wide data path while leaving
2356 pointers at 32 bits for smaller memory footprint.
2358 You will need a recent binutils (2.22 or later) with
2359 elf32_x86_64 support enabled to compile a kernel with this
2364 depends on IA32_EMULATION || X86_X32
2365 select ARCH_WANT_OLD_COMPAT_IPC
2368 config COMPAT_FOR_U64_ALIGNMENT
2371 config SYSVIPC_COMPAT
2383 config HAVE_ATOMIC_IOMAP
2387 config X86_DEV_DMA_OPS
2389 depends on X86_64 || STA2X11
2391 config X86_DMA_REMAP
2395 source "net/Kconfig"
2397 source "drivers/Kconfig"
2399 source "drivers/firmware/Kconfig"
2403 source "arch/x86/Kconfig.debug"
2405 source "security/Kconfig"
2407 source "crypto/Kconfig"
2409 source "arch/x86/kvm/Kconfig"
2411 source "lib/Kconfig"
projects / linux-drm-fsl-dcu.git / blob