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 ARCH_MIGHT_HAVE_PC_SERIO
27 select HAVE_AOUT if X86_32
28 select HAVE_UNSTABLE_SCHED_CLOCK
29 select ARCH_SUPPORTS_NUMA_BALANCING
30 select ARCH_SUPPORTS_INT128 if X86_64
31 select ARCH_WANTS_PROT_NUMA_PROT_NONE
34 select HAVE_PCSPKR_PLATFORM
35 select HAVE_PERF_EVENTS
36 select HAVE_IOREMAP_PROT
39 select HAVE_MEMBLOCK_NODE_MAP
40 select ARCH_DISCARD_MEMBLOCK
41 select ARCH_WANT_OPTIONAL_GPIOLIB
42 select ARCH_WANT_FRAME_POINTERS
44 select HAVE_DMA_CONTIGUOUS if !SWIOTLB
45 select HAVE_KRETPROBES
46 select GENERIC_EARLY_IOREMAP
48 select HAVE_KPROBES_ON_FTRACE
49 select HAVE_FTRACE_MCOUNT_RECORD
50 select HAVE_FENTRY if X86_64
51 select HAVE_C_RECORDMCOUNT
52 select HAVE_DYNAMIC_FTRACE
53 select HAVE_DYNAMIC_FTRACE_WITH_REGS
54 select HAVE_FUNCTION_TRACER
55 select HAVE_FUNCTION_GRAPH_TRACER
56 select HAVE_FUNCTION_GRAPH_FP_TEST
57 select HAVE_FUNCTION_TRACE_MCOUNT_TEST
58 select HAVE_SYSCALL_TRACEPOINTS
59 select SYSCTL_EXCEPTION_TRACE
62 select HAVE_ARCH_TRACEHOOK
63 select HAVE_GENERIC_DMA_COHERENT if X86_32
64 select HAVE_EFFICIENT_UNALIGNED_ACCESS
65 select USER_STACKTRACE_SUPPORT
66 select HAVE_REGS_AND_STACK_ACCESS_API
67 select HAVE_DMA_API_DEBUG
68 select HAVE_KERNEL_GZIP
69 select HAVE_KERNEL_BZIP2
70 select HAVE_KERNEL_LZMA
72 select HAVE_KERNEL_LZO
73 select HAVE_KERNEL_LZ4
74 select HAVE_HW_BREAKPOINT
75 select HAVE_MIXED_BREAKPOINTS_REGS
77 select HAVE_PERF_EVENTS_NMI
79 select HAVE_PERF_USER_STACK_DUMP
80 select HAVE_DEBUG_KMEMLEAK
82 select HAVE_ALIGNED_STRUCT_PAGE if SLUB
83 select HAVE_CMPXCHG_LOCAL
84 select HAVE_CMPXCHG_DOUBLE
85 select HAVE_ARCH_KMEMCHECK
86 select HAVE_USER_RETURN_NOTIFIER
87 select ARCH_BINFMT_ELF_RANDOMIZE_PIE
88 select HAVE_ARCH_JUMP_LABEL
89 select ARCH_HAS_ATOMIC64_DEC_IF_POSITIVE
91 select GENERIC_FIND_FIRST_BIT
92 select GENERIC_IRQ_PROBE
93 select GENERIC_PENDING_IRQ if SMP
94 select GENERIC_IRQ_SHOW
95 select GENERIC_CLOCKEVENTS_MIN_ADJUST
96 select IRQ_FORCED_THREADING
97 select HAVE_BPF_JIT if X86_64
98 select HAVE_ARCH_TRANSPARENT_HUGEPAGE
100 select ARCH_HAVE_NMI_SAFE_CMPXCHG
102 select DCACHE_WORD_ACCESS
103 select GENERIC_SMP_IDLE_THREAD
104 select ARCH_WANT_IPC_PARSE_VERSION if X86_32
105 select HAVE_ARCH_SECCOMP_FILTER
106 select BUILDTIME_EXTABLE_SORT
107 select GENERIC_CMOS_UPDATE
108 select HAVE_ARCH_SOFT_DIRTY
109 select CLOCKSOURCE_WATCHDOG
110 select GENERIC_CLOCKEVENTS
111 select ARCH_CLOCKSOURCE_DATA
112 select GENERIC_CLOCKEVENTS_BROADCAST if X86_64 || (X86_32 && X86_LOCAL_APIC)
113 select GENERIC_TIME_VSYSCALL
114 select KTIME_SCALAR if X86_32
115 select GENERIC_STRNCPY_FROM_USER
116 select GENERIC_STRNLEN_USER
117 select HAVE_CONTEXT_TRACKING if X86_64
118 select HAVE_IRQ_TIME_ACCOUNTING
120 select MODULES_USE_ELF_REL if X86_32
121 select MODULES_USE_ELF_RELA if X86_64
122 select CLONE_BACKWARDS if X86_32
123 select ARCH_USE_BUILTIN_BSWAP
124 select OLD_SIGSUSPEND3 if X86_32 || IA32_EMULATION
125 select OLD_SIGACTION if X86_32
126 select COMPAT_OLD_SIGACTION if IA32_EMULATION
128 select HAVE_DEBUG_STACKOVERFLOW
129 select HAVE_IRQ_EXIT_ON_IRQ_STACK if X86_64
130 select HAVE_CC_STACKPROTECTOR
131 select GENERIC_CPU_AUTOPROBE
132 select HAVE_ARCH_AUDITSYSCALL
134 config INSTRUCTION_DECODER
136 depends on KPROBES || PERF_EVENTS || UPROBES
140 default "elf32-i386" if X86_32
141 default "elf64-x86-64" if X86_64
143 config ARCH_DEFCONFIG
145 default "arch/x86/configs/i386_defconfig" if X86_32
146 default "arch/x86/configs/x86_64_defconfig" if X86_64
148 config LOCKDEP_SUPPORT
151 config STACKTRACE_SUPPORT
154 config HAVE_LATENCYTOP_SUPPORT
163 config NEED_DMA_MAP_STATE
165 depends on X86_64 || INTEL_IOMMU || DMA_API_DEBUG
167 config NEED_SG_DMA_LENGTH
170 config GENERIC_ISA_DMA
172 depends on ISA_DMA_API
177 select GENERIC_BUG_RELATIVE_POINTERS if X86_64
179 config GENERIC_BUG_RELATIVE_POINTERS
182 config GENERIC_HWEIGHT
185 config ARCH_MAY_HAVE_PC_FDC
187 depends on ISA_DMA_API
189 config RWSEM_XCHGADD_ALGORITHM
192 config GENERIC_CALIBRATE_DELAY
195 config ARCH_HAS_CPU_RELAX
198 config ARCH_HAS_CACHE_LINE_SIZE
201 config HAVE_SETUP_PER_CPU_AREA
204 config NEED_PER_CPU_EMBED_FIRST_CHUNK
207 config NEED_PER_CPU_PAGE_FIRST_CHUNK
210 config ARCH_HIBERNATION_POSSIBLE
213 config ARCH_SUSPEND_POSSIBLE
216 config ARCH_WANT_HUGE_PMD_SHARE
219 config ARCH_WANT_GENERAL_HUGETLB
230 config ARCH_SUPPORTS_OPTIMIZED_INLINING
233 config ARCH_SUPPORTS_DEBUG_PAGEALLOC
236 config HAVE_INTEL_TXT
238 depends on INTEL_IOMMU && ACPI
242 depends on X86_32 && SMP
246 depends on X86_64 && SMP
252 config X86_32_LAZY_GS
254 depends on X86_32 && !CC_STACKPROTECTOR
256 config ARCH_HWEIGHT_CFLAGS
258 default "-fcall-saved-ecx -fcall-saved-edx" if X86_32
259 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
261 config ARCH_SUPPORTS_UPROBES
264 source "init/Kconfig"
265 source "kernel/Kconfig.freezer"
267 menu "Processor type and features"
270 bool "DMA memory allocation support" if EXPERT
273 DMA memory allocation support allows devices with less than 32-bit
274 addressing to allocate within the first 16MB of address space.
275 Disable if no such devices will be used.
280 bool "Symmetric multi-processing support"
282 This enables support for systems with more than one CPU. If you have
283 a system with only one CPU, say N. If you have a system with more
286 If you say N here, the kernel will run on uni- and multiprocessor
287 machines, but will use only one CPU of a multiprocessor machine. If
288 you say Y here, the kernel will run on many, but not all,
289 uniprocessor machines. On a uniprocessor machine, the kernel
290 will run faster if you say N here.
292 Note that if you say Y here and choose architecture "586" or
293 "Pentium" under "Processor family", the kernel will not work on 486
294 architectures. Similarly, multiprocessor kernels for the "PPro"
295 architecture may not work on all Pentium based boards.
297 People using multiprocessor machines who say Y here should also say
298 Y to "Enhanced Real Time Clock Support", below. The "Advanced Power
299 Management" code will be disabled if you say Y here.
301 See also <file:Documentation/x86/i386/IO-APIC.txt>,
302 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
303 <http://www.tldp.org/docs.html#howto>.
305 If you don't know what to do here, say N.
308 bool "Support x2apic"
309 depends on X86_LOCAL_APIC && X86_64 && IRQ_REMAP
311 This enables x2apic support on CPUs that have this feature.
313 This allows 32-bit apic IDs (so it can support very large systems),
314 and accesses the local apic via MSRs not via mmio.
316 If you don't know what to do here, say N.
319 bool "Enable MPS table" if ACPI || SFI
321 depends on X86_LOCAL_APIC
323 For old smp systems that do not have proper acpi support. Newer systems
324 (esp with 64bit cpus) with acpi support, MADT and DSDT will override it
327 bool "Support for big SMP systems with more than 8 CPUs"
328 depends on X86_32 && SMP
330 This option is needed for the systems that have more than 8 CPUs
334 depends on X86_GOLDFISH
337 config X86_EXTENDED_PLATFORM
338 bool "Support for extended (non-PC) x86 platforms"
341 If you disable this option then the kernel will only support
342 standard PC platforms. (which covers the vast majority of
345 If you enable this option then you'll be able to select support
346 for the following (non-PC) 32 bit x86 platforms:
347 Goldfish (Android emulator)
350 SGI 320/540 (Visual Workstation)
351 STA2X11-based (e.g. Northville)
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.
441 bool "Intel MID platform support"
443 depends on X86_EXTENDED_PLATFORM
444 depends on X86_PLATFORM_DEVICES
447 depends on X86_IO_APIC
453 select MFD_INTEL_MSIC
455 Select to build a kernel capable of supporting Intel MID (Mobile
456 Internet Device) platform systems which do not have the PCI legacy
457 interfaces. If you are building for a PC class system say N here.
459 Intel MID platforms are based on an Intel processor and chipset which
460 consume less power than most of the x86 derivatives.
462 config X86_INTEL_LPSS
463 bool "Intel Low Power Subsystem Support"
468 Select to build support for Intel Low Power Subsystem such as
469 found on Intel Lynxpoint PCH. Selecting this option enables
470 things like clock tree (common clock framework) and pincontrol
471 which are needed by the LPSS peripheral drivers.
474 bool "RDC R-321x SoC"
476 depends on X86_EXTENDED_PLATFORM
478 select X86_REBOOTFIXUPS
480 This option is needed for RDC R-321x system-on-chip, also known
482 If you don't have one of these chips, you should say N here.
484 config X86_32_NON_STANDARD
485 bool "Support non-standard 32-bit SMP architectures"
486 depends on X86_32 && SMP
487 depends on X86_EXTENDED_PLATFORM
489 This option compiles in the bigsmp and STA2X11 default
490 subarchitectures. It is intended for a generic binary
491 kernel. If you select them all, kernel will probe it one by
492 one and will fallback to default.
494 # Alphabetically sorted list of Non standard 32 bit platforms
496 config X86_SUPPORTS_MEMORY_FAILURE
498 # MCE code calls memory_failure():
500 # On 32-bit this adds too big of NODES_SHIFT and we run out of page flags:
501 # On 32-bit SPARSEMEM adds too big of SECTIONS_WIDTH:
502 depends on X86_64 || !SPARSEMEM
503 select ARCH_SUPPORTS_MEMORY_FAILURE
506 bool "STA2X11 Companion Chip Support"
507 depends on X86_32_NON_STANDARD && PCI
508 select X86_DEV_DMA_OPS
512 select ARCH_REQUIRE_GPIOLIB
515 This adds support for boards based on the STA2X11 IO-Hub,
516 a.k.a. "ConneXt". The chip is used in place of the standard
517 PC chipset, so all "standard" peripherals are missing. If this
518 option is selected the kernel will still be able to boot on
519 standard PC machines.
522 tristate "Eurobraille/Iris poweroff module"
525 The Iris machines from EuroBraille do not have APM or ACPI support
526 to shut themselves down properly. A special I/O sequence is
527 needed to do so, which is what this module does at
530 This is only for Iris machines from EuroBraille.
534 config SCHED_OMIT_FRAME_POINTER
536 prompt "Single-depth WCHAN output"
539 Calculate simpler /proc/<PID>/wchan values. If this option
540 is disabled then wchan values will recurse back to the
541 caller function. This provides more accurate wchan values,
542 at the expense of slightly more scheduling overhead.
544 If in doubt, say "Y".
546 menuconfig HYPERVISOR_GUEST
547 bool "Linux guest support"
549 Say Y here to enable options for running Linux under various hyper-
550 visors. This option enables basic hypervisor detection and platform
553 If you say N, all options in this submenu will be skipped and
554 disabled, and Linux guest support won't be built in.
559 bool "Enable paravirtualization code"
561 This changes the kernel so it can modify itself when it is run
562 under a hypervisor, potentially improving performance significantly
563 over full virtualization. However, when run without a hypervisor
564 the kernel is theoretically slower and slightly larger.
566 config PARAVIRT_DEBUG
567 bool "paravirt-ops debugging"
568 depends on PARAVIRT && DEBUG_KERNEL
570 Enable to debug paravirt_ops internals. Specifically, BUG if
571 a paravirt_op is missing when it is called.
573 config PARAVIRT_SPINLOCKS
574 bool "Paravirtualization layer for spinlocks"
575 depends on PARAVIRT && SMP
576 select UNINLINE_SPIN_UNLOCK
578 Paravirtualized spinlocks allow a pvops backend to replace the
579 spinlock implementation with something virtualization-friendly
580 (for example, block the virtual CPU rather than spinning).
582 It has a minimal impact on native kernels and gives a nice performance
583 benefit on paravirtualized KVM / Xen kernels.
585 If you are unsure how to answer this question, answer Y.
587 source "arch/x86/xen/Kconfig"
590 bool "KVM Guest support (including kvmclock)"
592 select PARAVIRT_CLOCK
595 This option enables various optimizations for running under the KVM
596 hypervisor. It includes a paravirtualized clock, so that instead
597 of relying on a PIT (or probably other) emulation by the
598 underlying device model, the host provides the guest with
599 timing infrastructure such as time of day, and system time
602 bool "Enable debug information for KVM Guests in debugfs"
603 depends on KVM_GUEST && DEBUG_FS
606 This option enables collection of various statistics for KVM guest.
607 Statistics are displayed in debugfs filesystem. Enabling this option
608 may incur significant overhead.
610 source "arch/x86/lguest/Kconfig"
612 config PARAVIRT_TIME_ACCOUNTING
613 bool "Paravirtual steal time accounting"
617 Select this option to enable fine granularity task steal time
618 accounting. Time spent executing other tasks in parallel with
619 the current vCPU is discounted from the vCPU power. To account for
620 that, there can be a small performance impact.
622 If in doubt, say N here.
624 config PARAVIRT_CLOCK
627 endif #HYPERVISOR_GUEST
635 This option adds a kernel parameter 'memtest', which allows memtest
637 memtest=0, mean disabled; -- default
638 memtest=1, mean do 1 test pattern;
640 memtest=4, mean do 4 test patterns.
641 If you are unsure how to answer this question, answer N.
643 source "arch/x86/Kconfig.cpu"
647 prompt "HPET Timer Support" if X86_32
649 Use the IA-PC HPET (High Precision Event Timer) to manage
650 time in preference to the PIT and RTC, if a HPET is
652 HPET is the next generation timer replacing legacy 8254s.
653 The HPET provides a stable time base on SMP
654 systems, unlike the TSC, but it is more expensive to access,
655 as it is off-chip. You can find the HPET spec at
656 <http://www.intel.com/hardwaredesign/hpetspec_1.pdf>.
658 You can safely choose Y here. However, HPET will only be
659 activated if the platform and the BIOS support this feature.
660 Otherwise the 8254 will be used for timing services.
662 Choose N to continue using the legacy 8254 timer.
664 config HPET_EMULATE_RTC
666 depends on HPET_TIMER && (RTC=y || RTC=m || RTC_DRV_CMOS=m || RTC_DRV_CMOS=y)
669 def_bool y if X86_INTEL_MID
670 prompt "Intel MID APB Timer Support" if X86_INTEL_MID
672 depends on X86_INTEL_MID && SFI
674 APB timer is the replacement for 8254, HPET on X86 MID platforms.
675 The APBT provides a stable time base on SMP
676 systems, unlike the TSC, but it is more expensive to access,
677 as it is off-chip. APB timers are always running regardless of CPU
678 C states, they are used as per CPU clockevent device when possible.
680 # Mark as expert because too many people got it wrong.
681 # The code disables itself when not needed.
684 select DMI_SCAN_MACHINE_NON_EFI_FALLBACK
685 bool "Enable DMI scanning" if EXPERT
687 Enabled scanning of DMI to identify machine quirks. Say Y
688 here unless you have verified that your setup is not
689 affected by entries in the DMI blacklist. Required by PNP
693 bool "Old AMD GART IOMMU support"
695 depends on X86_64 && PCI && AMD_NB
697 Provides a driver for older AMD Athlon64/Opteron/Turion/Sempron
698 GART based hardware IOMMUs.
700 The GART supports full DMA access for devices with 32-bit access
701 limitations, on systems with more than 3 GB. This is usually needed
702 for USB, sound, many IDE/SATA chipsets and some other devices.
704 Newer systems typically have a modern AMD IOMMU, supported via
705 the CONFIG_AMD_IOMMU=y config option.
707 In normal configurations this driver is only active when needed:
708 there's more than 3 GB of memory and the system contains a
709 32-bit limited device.
714 bool "IBM Calgary IOMMU support"
716 depends on X86_64 && PCI
718 Support for hardware IOMMUs in IBM's xSeries x366 and x460
719 systems. Needed to run systems with more than 3GB of memory
720 properly with 32-bit PCI devices that do not support DAC
721 (Double Address Cycle). Calgary also supports bus level
722 isolation, where all DMAs pass through the IOMMU. This
723 prevents them from going anywhere except their intended
724 destination. This catches hard-to-find kernel bugs and
725 mis-behaving drivers and devices that do not use the DMA-API
726 properly to set up their DMA buffers. The IOMMU can be
727 turned off at boot time with the iommu=off parameter.
728 Normally the kernel will make the right choice by itself.
731 config CALGARY_IOMMU_ENABLED_BY_DEFAULT
733 prompt "Should Calgary be enabled by default?"
734 depends on CALGARY_IOMMU
736 Should Calgary be enabled by default? if you choose 'y', Calgary
737 will be used (if it exists). If you choose 'n', Calgary will not be
738 used even if it exists. If you choose 'n' and would like to use
739 Calgary anyway, pass 'iommu=calgary' on the kernel command line.
742 # need this always selected by IOMMU for the VIA workaround
746 Support for software bounce buffers used on x86-64 systems
747 which don't have a hardware IOMMU. Using this PCI devices
748 which can only access 32-bits of memory can be used on systems
749 with more than 3 GB of memory.
754 depends on CALGARY_IOMMU || GART_IOMMU || SWIOTLB || AMD_IOMMU
757 bool "Enable Maximum number of SMP Processors and NUMA Nodes"
758 depends on X86_64 && SMP && DEBUG_KERNEL
759 select CPUMASK_OFFSTACK
761 Enable maximum number of CPUS and NUMA Nodes for this architecture.
765 int "Maximum number of CPUs" if SMP && !MAXSMP
766 range 2 8 if SMP && X86_32 && !X86_BIGSMP
767 range 2 512 if SMP && !MAXSMP && !CPUMASK_OFFSTACK
768 range 2 8192 if SMP && !MAXSMP && CPUMASK_OFFSTACK && X86_64
770 default "8192" if MAXSMP
771 default "32" if SMP && X86_BIGSMP
774 This allows you to specify the maximum number of CPUs which this
775 kernel will support. If CPUMASK_OFFSTACK is enabled, the maximum
776 supported value is 4096, otherwise the maximum value is 512. The
777 minimum value which makes sense is 2.
779 This is purely to save memory - each supported CPU adds
780 approximately eight kilobytes to the kernel image.
783 bool "SMT (Hyperthreading) scheduler support"
786 SMT scheduler support improves the CPU scheduler's decision making
787 when dealing with Intel Pentium 4 chips with HyperThreading at a
788 cost of slightly increased overhead in some places. If unsure say
793 prompt "Multi-core scheduler support"
796 Multi-core scheduler support improves the CPU scheduler's decision
797 making when dealing with multi-core CPU chips at a cost of slightly
798 increased overhead in some places. If unsure say N here.
800 source "kernel/Kconfig.preempt"
803 bool "Local APIC support on uniprocessors"
804 depends on X86_32 && !SMP && !X86_32_NON_STANDARD && !PCI_MSI
806 A local APIC (Advanced Programmable Interrupt Controller) is an
807 integrated interrupt controller in the CPU. If you have a single-CPU
808 system which has a processor with a local APIC, you can say Y here to
809 enable and use it. If you say Y here even though your machine doesn't
810 have a local APIC, then the kernel will still run with no slowdown at
811 all. The local APIC supports CPU-generated self-interrupts (timer,
812 performance counters), and the NMI watchdog which detects hard
816 bool "IO-APIC support on uniprocessors"
817 depends on X86_UP_APIC
819 An IO-APIC (I/O Advanced Programmable Interrupt Controller) is an
820 SMP-capable replacement for PC-style interrupt controllers. Most
821 SMP systems and many recent uniprocessor systems have one.
823 If you have a single-CPU system with an IO-APIC, you can say Y here
824 to use it. If you say Y here even though your machine doesn't have
825 an IO-APIC, then the kernel will still run with no slowdown at all.
827 config X86_LOCAL_APIC
829 depends on X86_64 || SMP || X86_32_NON_STANDARD || X86_UP_APIC || PCI_MSI
833 depends on X86_64 || SMP || X86_32_NON_STANDARD || X86_UP_IOAPIC || PCI_MSI
834 select GENERIC_IRQ_LEGACY_ALLOC_HWIRQ
836 config X86_REROUTE_FOR_BROKEN_BOOT_IRQS
837 bool "Reroute for broken boot IRQs"
838 depends on X86_IO_APIC
840 This option enables a workaround that fixes a source of
841 spurious interrupts. This is recommended when threaded
842 interrupt handling is used on systems where the generation of
843 superfluous "boot interrupts" cannot be disabled.
845 Some chipsets generate a legacy INTx "boot IRQ" when the IRQ
846 entry in the chipset's IO-APIC is masked (as, e.g. the RT
847 kernel does during interrupt handling). On chipsets where this
848 boot IRQ generation cannot be disabled, this workaround keeps
849 the original IRQ line masked so that only the equivalent "boot
850 IRQ" is delivered to the CPUs. The workaround also tells the
851 kernel to set up the IRQ handler on the boot IRQ line. In this
852 way only one interrupt is delivered to the kernel. Otherwise
853 the spurious second interrupt may cause the kernel to bring
854 down (vital) interrupt lines.
856 Only affects "broken" chipsets. Interrupt sharing may be
857 increased on these systems.
860 bool "Machine Check / overheating reporting"
863 Machine Check support allows the processor to notify the
864 kernel if it detects a problem (e.g. overheating, data corruption).
865 The action the kernel takes depends on the severity of the problem,
866 ranging from warning messages to halting the machine.
870 prompt "Intel MCE features"
871 depends on X86_MCE && X86_LOCAL_APIC
873 Additional support for intel specific MCE features such as
878 prompt "AMD MCE features"
879 depends on X86_MCE && X86_LOCAL_APIC
881 Additional support for AMD specific MCE features such as
882 the DRAM Error Threshold.
884 config X86_ANCIENT_MCE
885 bool "Support for old Pentium 5 / WinChip machine checks"
886 depends on X86_32 && X86_MCE
888 Include support for machine check handling on old Pentium 5 or WinChip
889 systems. These typically need to be enabled explicitly on the command
892 config X86_MCE_THRESHOLD
893 depends on X86_MCE_AMD || X86_MCE_INTEL
896 config X86_MCE_INJECT
898 tristate "Machine check injector support"
900 Provide support for injecting machine checks for testing purposes.
901 If you don't know what a machine check is and you don't do kernel
902 QA it is safe to say n.
904 config X86_THERMAL_VECTOR
906 depends on X86_MCE_INTEL
909 bool "Enable VM86 support" if EXPERT
913 This option is required by programs like DOSEMU to run 16-bit legacy
914 code on X86 processors. It also may be needed by software like
915 XFree86 to initialize some video cards via BIOS. Disabling this
916 option saves about 6k.
919 tristate "Toshiba Laptop support"
922 This adds a driver to safely access the System Management Mode of
923 the CPU on Toshiba portables with a genuine Toshiba BIOS. It does
924 not work on models with a Phoenix BIOS. The System Management Mode
925 is used to set the BIOS and power saving options on Toshiba portables.
927 For information on utilities to make use of this driver see the
928 Toshiba Linux utilities web site at:
929 <http://www.buzzard.org.uk/toshiba/>.
931 Say Y if you intend to run this kernel on a Toshiba portable.
935 tristate "Dell laptop support"
938 This adds a driver to safely access the System Management Mode
939 of the CPU on the Dell Inspiron 8000. The System Management Mode
940 is used to read cpu temperature and cooling fan status and to
941 control the fans on the I8K portables.
943 This driver has been tested only on the Inspiron 8000 but it may
944 also work with other Dell laptops. You can force loading on other
945 models by passing the parameter `force=1' to the module. Use at
948 For information on utilities to make use of this driver see the
949 I8K Linux utilities web site at:
950 <http://people.debian.org/~dz/i8k/>
952 Say Y if you intend to run this kernel on a Dell Inspiron 8000.
955 config X86_REBOOTFIXUPS
956 bool "Enable X86 board specific fixups for reboot"
959 This enables chipset and/or board specific fixups to be done
960 in order to get reboot to work correctly. This is only needed on
961 some combinations of hardware and BIOS. The symptom, for which
962 this config is intended, is when reboot ends with a stalled/hung
965 Currently, the only fixup is for the Geode machines using
966 CS5530A and CS5536 chipsets and the RDC R-321x SoC.
968 Say Y if you want to enable the fixup. Currently, it's safe to
969 enable this option even if you don't need it.
973 tristate "CPU microcode loading support"
974 depends on CPU_SUP_AMD || CPU_SUP_INTEL
978 If you say Y here, you will be able to update the microcode on
979 certain Intel and AMD processors. The Intel support is for the
980 IA32 family, e.g. Pentium Pro, Pentium II, Pentium III, Pentium 4,
981 Xeon etc. The AMD support is for families 0x10 and later. You will
982 obviously need the actual microcode binary data itself which is not
983 shipped with the Linux kernel.
985 This option selects the general module only, you need to select
986 at least one vendor specific module as well.
988 To compile this driver as a module, choose M here: the module
989 will be called microcode.
991 config MICROCODE_INTEL
992 bool "Intel microcode loading support"
997 This options enables microcode patch loading support for Intel
1000 For the current Intel microcode data package go to
1001 <https://downloadcenter.intel.com> and search for
1002 'Linux Processor Microcode Data File'.
1004 config MICROCODE_AMD
1005 bool "AMD microcode loading support"
1006 depends on MICROCODE
1009 If you select this option, microcode patch loading support for AMD
1010 processors will be enabled.
1012 config MICROCODE_OLD_INTERFACE
1014 depends on MICROCODE
1016 config MICROCODE_INTEL_EARLY
1019 config MICROCODE_AMD_EARLY
1022 config MICROCODE_EARLY
1023 bool "Early load microcode"
1024 depends on MICROCODE=y && BLK_DEV_INITRD
1025 select MICROCODE_INTEL_EARLY if MICROCODE_INTEL
1026 select MICROCODE_AMD_EARLY if MICROCODE_AMD
1029 This option provides functionality to read additional microcode data
1030 at the beginning of initrd image. The data tells kernel to load
1031 microcode to CPU's as early as possible. No functional change if no
1032 microcode data is glued to the initrd, therefore it's safe to say Y.
1035 tristate "/dev/cpu/*/msr - Model-specific register support"
1037 This device gives privileged processes access to the x86
1038 Model-Specific Registers (MSRs). It is a character device with
1039 major 202 and minors 0 to 31 for /dev/cpu/0/msr to /dev/cpu/31/msr.
1040 MSR accesses are directed to a specific CPU on multi-processor
1044 tristate "/dev/cpu/*/cpuid - CPU information support"
1046 This device gives processes access to the x86 CPUID instruction to
1047 be executed on a specific processor. It is a character device
1048 with major 203 and minors 0 to 31 for /dev/cpu/0/cpuid to
1052 prompt "High Memory Support"
1059 Linux can use up to 64 Gigabytes of physical memory on x86 systems.
1060 However, the address space of 32-bit x86 processors is only 4
1061 Gigabytes large. That means that, if you have a large amount of
1062 physical memory, not all of it can be "permanently mapped" by the
1063 kernel. The physical memory that's not permanently mapped is called
1066 If you are compiling a kernel which will never run on a machine with
1067 more than 1 Gigabyte total physical RAM, answer "off" here (default
1068 choice and suitable for most users). This will result in a "3GB/1GB"
1069 split: 3GB are mapped so that each process sees a 3GB virtual memory
1070 space and the remaining part of the 4GB virtual memory space is used
1071 by the kernel to permanently map as much physical memory as
1074 If the machine has between 1 and 4 Gigabytes physical RAM, then
1077 If more than 4 Gigabytes is used then answer "64GB" here. This
1078 selection turns Intel PAE (Physical Address Extension) mode on.
1079 PAE implements 3-level paging on IA32 processors. PAE is fully
1080 supported by Linux, PAE mode is implemented on all recent Intel
1081 processors (Pentium Pro and better). NOTE: If you say "64GB" here,
1082 then the kernel will not boot on CPUs that don't support PAE!
1084 The actual amount of total physical memory will either be
1085 auto detected or can be forced by using a kernel command line option
1086 such as "mem=256M". (Try "man bootparam" or see the documentation of
1087 your boot loader (lilo or loadlin) about how to pass options to the
1088 kernel at boot time.)
1090 If unsure, say "off".
1095 Select this if you have a 32-bit processor and between 1 and 4
1096 gigabytes of physical RAM.
1103 Select this if you have a 32-bit processor and more than 4
1104 gigabytes of physical RAM.
1109 prompt "Memory split" if EXPERT
1113 Select the desired split between kernel and user memory.
1115 If the address range available to the kernel is less than the
1116 physical memory installed, the remaining memory will be available
1117 as "high memory". Accessing high memory is a little more costly
1118 than low memory, as it needs to be mapped into the kernel first.
1119 Note that increasing the kernel address space limits the range
1120 available to user programs, making the address space there
1121 tighter. Selecting anything other than the default 3G/1G split
1122 will also likely make your kernel incompatible with binary-only
1125 If you are not absolutely sure what you are doing, leave this
1129 bool "3G/1G user/kernel split"
1130 config VMSPLIT_3G_OPT
1132 bool "3G/1G user/kernel split (for full 1G low memory)"
1134 bool "2G/2G user/kernel split"
1135 config VMSPLIT_2G_OPT
1137 bool "2G/2G user/kernel split (for full 2G low memory)"
1139 bool "1G/3G user/kernel split"
1144 default 0xB0000000 if VMSPLIT_3G_OPT
1145 default 0x80000000 if VMSPLIT_2G
1146 default 0x78000000 if VMSPLIT_2G_OPT
1147 default 0x40000000 if VMSPLIT_1G
1153 depends on X86_32 && (HIGHMEM64G || HIGHMEM4G)
1156 bool "PAE (Physical Address Extension) Support"
1157 depends on X86_32 && !HIGHMEM4G
1159 PAE is required for NX support, and furthermore enables
1160 larger swapspace support for non-overcommit purposes. It
1161 has the cost of more pagetable lookup overhead, and also
1162 consumes more pagetable space per process.
1164 config ARCH_PHYS_ADDR_T_64BIT
1166 depends on X86_64 || X86_PAE
1168 config ARCH_DMA_ADDR_T_64BIT
1170 depends on X86_64 || HIGHMEM64G
1172 config DIRECT_GBPAGES
1173 bool "Enable 1GB pages for kernel pagetables" if EXPERT
1177 Allow the kernel linear mapping to use 1GB pages on CPUs that
1178 support it. This can improve the kernel's performance a tiny bit by
1179 reducing TLB pressure. If in doubt, say "Y".
1181 # Common NUMA Features
1183 bool "Numa Memory Allocation and Scheduler Support"
1185 depends on X86_64 || (X86_32 && HIGHMEM64G && X86_BIGSMP)
1186 default y if X86_BIGSMP
1188 Enable NUMA (Non Uniform Memory Access) support.
1190 The kernel will try to allocate memory used by a CPU on the
1191 local memory controller of the CPU and add some more
1192 NUMA awareness to the kernel.
1194 For 64-bit this is recommended if the system is Intel Core i7
1195 (or later), AMD Opteron, or EM64T NUMA.
1197 For 32-bit this is only needed if you boot a 32-bit
1198 kernel on a 64-bit NUMA platform.
1200 Otherwise, you should say N.
1204 prompt "Old style AMD Opteron NUMA detection"
1205 depends on X86_64 && NUMA && PCI
1207 Enable AMD NUMA node topology detection. You should say Y here if
1208 you have a multi processor AMD system. This uses an old method to
1209 read the NUMA configuration directly from the builtin Northbridge
1210 of Opteron. It is recommended to use X86_64_ACPI_NUMA instead,
1211 which also takes priority if both are compiled in.
1213 config X86_64_ACPI_NUMA
1215 prompt "ACPI NUMA detection"
1216 depends on X86_64 && NUMA && ACPI && PCI
1219 Enable ACPI SRAT based node topology detection.
1221 # Some NUMA nodes have memory ranges that span
1222 # other nodes. Even though a pfn is valid and
1223 # between a node's start and end pfns, it may not
1224 # reside on that node. See memmap_init_zone()
1226 config NODES_SPAN_OTHER_NODES
1228 depends on X86_64_ACPI_NUMA
1231 bool "NUMA emulation"
1234 Enable NUMA emulation. A flat machine will be split
1235 into virtual nodes when booted with "numa=fake=N", where N is the
1236 number of nodes. This is only useful for debugging.
1239 int "Maximum NUMA Nodes (as a power of 2)" if !MAXSMP
1241 default "10" if MAXSMP
1242 default "6" if X86_64
1244 depends on NEED_MULTIPLE_NODES
1246 Specify the maximum number of NUMA Nodes available on the target
1247 system. Increases memory reserved to accommodate various tables.
1249 config ARCH_HAVE_MEMORY_PRESENT
1251 depends on X86_32 && DISCONTIGMEM
1253 config NEED_NODE_MEMMAP_SIZE
1255 depends on X86_32 && (DISCONTIGMEM || SPARSEMEM)
1257 config ARCH_FLATMEM_ENABLE
1259 depends on X86_32 && !NUMA
1261 config ARCH_DISCONTIGMEM_ENABLE
1263 depends on NUMA && X86_32
1265 config ARCH_DISCONTIGMEM_DEFAULT
1267 depends on NUMA && X86_32
1269 config ARCH_SPARSEMEM_ENABLE
1271 depends on X86_64 || NUMA || X86_32 || X86_32_NON_STANDARD
1272 select SPARSEMEM_STATIC if X86_32
1273 select SPARSEMEM_VMEMMAP_ENABLE if X86_64
1275 config ARCH_SPARSEMEM_DEFAULT
1279 config ARCH_SELECT_MEMORY_MODEL
1281 depends on ARCH_SPARSEMEM_ENABLE
1283 config ARCH_MEMORY_PROBE
1284 bool "Enable sysfs memory/probe interface"
1285 depends on X86_64 && MEMORY_HOTPLUG
1287 This option enables a sysfs memory/probe interface for testing.
1288 See Documentation/memory-hotplug.txt for more information.
1289 If you are unsure how to answer this question, answer N.
1291 config ARCH_PROC_KCORE_TEXT
1293 depends on X86_64 && PROC_KCORE
1295 config ILLEGAL_POINTER_VALUE
1298 default 0xdead000000000000 if X86_64
1303 bool "Allocate 3rd-level pagetables from highmem"
1306 The VM uses one page table entry for each page of physical memory.
1307 For systems with a lot of RAM, this can be wasteful of precious
1308 low memory. Setting this option will put user-space page table
1309 entries in high memory.
1311 config X86_CHECK_BIOS_CORRUPTION
1312 bool "Check for low memory corruption"
1314 Periodically check for memory corruption in low memory, which
1315 is suspected to be caused by BIOS. Even when enabled in the
1316 configuration, it is disabled at runtime. Enable it by
1317 setting "memory_corruption_check=1" on the kernel command
1318 line. By default it scans the low 64k of memory every 60
1319 seconds; see the memory_corruption_check_size and
1320 memory_corruption_check_period parameters in
1321 Documentation/kernel-parameters.txt to adjust this.
1323 When enabled with the default parameters, this option has
1324 almost no overhead, as it reserves a relatively small amount
1325 of memory and scans it infrequently. It both detects corruption
1326 and prevents it from affecting the running system.
1328 It is, however, intended as a diagnostic tool; if repeatable
1329 BIOS-originated corruption always affects the same memory,
1330 you can use memmap= to prevent the kernel from using that
1333 config X86_BOOTPARAM_MEMORY_CORRUPTION_CHECK
1334 bool "Set the default setting of memory_corruption_check"
1335 depends on X86_CHECK_BIOS_CORRUPTION
1338 Set whether the default state of memory_corruption_check is
1341 config X86_RESERVE_LOW
1342 int "Amount of low memory, in kilobytes, to reserve for the BIOS"
1346 Specify the amount of low memory to reserve for the BIOS.
1348 The first page contains BIOS data structures that the kernel
1349 must not use, so that page must always be reserved.
1351 By default we reserve the first 64K of physical RAM, as a
1352 number of BIOSes are known to corrupt that memory range
1353 during events such as suspend/resume or monitor cable
1354 insertion, so it must not be used by the kernel.
1356 You can set this to 4 if you are absolutely sure that you
1357 trust the BIOS to get all its memory reservations and usages
1358 right. If you know your BIOS have problems beyond the
1359 default 64K area, you can set this to 640 to avoid using the
1360 entire low memory range.
1362 If you have doubts about the BIOS (e.g. suspend/resume does
1363 not work or there's kernel crashes after certain hardware
1364 hotplug events) then you might want to enable
1365 X86_CHECK_BIOS_CORRUPTION=y to allow the kernel to check
1366 typical corruption patterns.
1368 Leave this to the default value of 64 if you are unsure.
1370 config MATH_EMULATION
1372 prompt "Math emulation" if X86_32
1374 Linux can emulate a math coprocessor (used for floating point
1375 operations) if you don't have one. 486DX and Pentium processors have
1376 a math coprocessor built in, 486SX and 386 do not, unless you added
1377 a 487DX or 387, respectively. (The messages during boot time can
1378 give you some hints here ["man dmesg"].) Everyone needs either a
1379 coprocessor or this emulation.
1381 If you don't have a math coprocessor, you need to say Y here; if you
1382 say Y here even though you have a coprocessor, the coprocessor will
1383 be used nevertheless. (This behavior can be changed with the kernel
1384 command line option "no387", which comes handy if your coprocessor
1385 is broken. Try "man bootparam" or see the documentation of your boot
1386 loader (lilo or loadlin) about how to pass options to the kernel at
1387 boot time.) This means that it is a good idea to say Y here if you
1388 intend to use this kernel on different machines.
1390 More information about the internals of the Linux math coprocessor
1391 emulation can be found in <file:arch/x86/math-emu/README>.
1393 If you are not sure, say Y; apart from resulting in a 66 KB bigger
1394 kernel, it won't hurt.
1398 prompt "MTRR (Memory Type Range Register) support" if EXPERT
1400 On Intel P6 family processors (Pentium Pro, Pentium II and later)
1401 the Memory Type Range Registers (MTRRs) may be used to control
1402 processor access to memory ranges. This is most useful if you have
1403 a video (VGA) card on a PCI or AGP bus. Enabling write-combining
1404 allows bus write transfers to be combined into a larger transfer
1405 before bursting over the PCI/AGP bus. This can increase performance
1406 of image write operations 2.5 times or more. Saying Y here creates a
1407 /proc/mtrr file which may be used to manipulate your processor's
1408 MTRRs. Typically the X server should use this.
1410 This code has a reasonably generic interface so that similar
1411 control registers on other processors can be easily supported
1414 The Cyrix 6x86, 6x86MX and M II processors have Address Range
1415 Registers (ARRs) which provide a similar functionality to MTRRs. For
1416 these, the ARRs are used to emulate the MTRRs.
1417 The AMD K6-2 (stepping 8 and above) and K6-3 processors have two
1418 MTRRs. The Centaur C6 (WinChip) has 8 MCRs, allowing
1419 write-combining. All of these processors are supported by this code
1420 and it makes sense to say Y here if you have one of them.
1422 Saying Y here also fixes a problem with buggy SMP BIOSes which only
1423 set the MTRRs for the boot CPU and not for the secondary CPUs. This
1424 can lead to all sorts of problems, so it's good to say Y here.
1426 You can safely say Y even if your machine doesn't have MTRRs, you'll
1427 just add about 9 KB to your kernel.
1429 See <file:Documentation/x86/mtrr.txt> for more information.
1431 config MTRR_SANITIZER
1433 prompt "MTRR cleanup support"
1436 Convert MTRR layout from continuous to discrete, so X drivers can
1437 add writeback entries.
1439 Can be disabled with disable_mtrr_cleanup on the kernel command line.
1440 The largest mtrr entry size for a continuous block can be set with
1445 config MTRR_SANITIZER_ENABLE_DEFAULT
1446 int "MTRR cleanup enable value (0-1)"
1449 depends on MTRR_SANITIZER
1451 Enable mtrr cleanup default value
1453 config MTRR_SANITIZER_SPARE_REG_NR_DEFAULT
1454 int "MTRR cleanup spare reg num (0-7)"
1457 depends on MTRR_SANITIZER
1459 mtrr cleanup spare entries default, it can be changed via
1460 mtrr_spare_reg_nr=N on the kernel command line.
1464 prompt "x86 PAT support" if EXPERT
1467 Use PAT attributes to setup page level cache control.
1469 PATs are the modern equivalents of MTRRs and are much more
1470 flexible than MTRRs.
1472 Say N here if you see bootup problems (boot crash, boot hang,
1473 spontaneous reboots) or a non-working video driver.
1477 config ARCH_USES_PG_UNCACHED
1483 prompt "x86 architectural random number generator" if EXPERT
1485 Enable the x86 architectural RDRAND instruction
1486 (Intel Bull Mountain technology) to generate random numbers.
1487 If supported, this is a high bandwidth, cryptographically
1488 secure hardware random number generator.
1492 prompt "Supervisor Mode Access Prevention" if EXPERT
1494 Supervisor Mode Access Prevention (SMAP) is a security
1495 feature in newer Intel processors. There is a small
1496 performance cost if this enabled and turned on; there is
1497 also a small increase in the kernel size if this is enabled.
1502 bool "EFI runtime service support"
1506 This enables the kernel to use EFI runtime services that are
1507 available (such as the EFI variable services).
1509 This option is only useful on systems that have EFI firmware.
1510 In addition, you should use the latest ELILO loader available
1511 at <http://elilo.sourceforge.net> in order to take advantage
1512 of EFI runtime services. However, even with this option, the
1513 resultant kernel should continue to boot on existing non-EFI
1517 bool "EFI stub support"
1520 This kernel feature allows a bzImage to be loaded directly
1521 by EFI firmware without the use of a bootloader.
1523 See Documentation/efi-stub.txt for more information.
1526 bool "EFI mixed-mode support"
1527 depends on EFI_STUB && X86_64
1529 Enabling this feature allows a 64-bit kernel to be booted
1530 on a 32-bit firmware, provided that your CPU supports 64-bit
1533 Note that it is not possible to boot a mixed-mode enabled
1534 kernel via the EFI boot stub - a bootloader that supports
1535 the EFI handover protocol must be used.
1541 prompt "Enable seccomp to safely compute untrusted bytecode"
1543 This kernel feature is useful for number crunching applications
1544 that may need to compute untrusted bytecode during their
1545 execution. By using pipes or other transports made available to
1546 the process as file descriptors supporting the read/write
1547 syscalls, it's possible to isolate those applications in
1548 their own address space using seccomp. Once seccomp is
1549 enabled via prctl(PR_SET_SECCOMP), it cannot be disabled
1550 and the task is only allowed to execute a few safe syscalls
1551 defined by each seccomp mode.
1553 If unsure, say Y. Only embedded should say N here.
1555 source kernel/Kconfig.hz
1558 bool "kexec system call"
1560 kexec is a system call that implements the ability to shutdown your
1561 current kernel, and to start another kernel. It is like a reboot
1562 but it is independent of the system firmware. And like a reboot
1563 you can start any kernel with it, not just Linux.
1565 The name comes from the similarity to the exec system call.
1567 It is an ongoing process to be certain the hardware in a machine
1568 is properly shutdown, so do not be surprised if this code does not
1569 initially work for you. As of this writing the exact hardware
1570 interface is strongly in flux, so no good recommendation can be
1574 bool "kernel crash dumps"
1575 depends on X86_64 || (X86_32 && HIGHMEM)
1577 Generate crash dump after being started by kexec.
1578 This should be normally only set in special crash dump kernels
1579 which are loaded in the main kernel with kexec-tools into
1580 a specially reserved region and then later executed after
1581 a crash by kdump/kexec. The crash dump kernel must be compiled
1582 to a memory address not used by the main kernel or BIOS using
1583 PHYSICAL_START, or it must be built as a relocatable image
1584 (CONFIG_RELOCATABLE=y).
1585 For more details see Documentation/kdump/kdump.txt
1589 depends on KEXEC && HIBERNATION
1591 Jump between original kernel and kexeced kernel and invoke
1592 code in physical address mode via KEXEC
1594 config PHYSICAL_START
1595 hex "Physical address where the kernel is loaded" if (EXPERT || CRASH_DUMP)
1598 This gives the physical address where the kernel is loaded.
1600 If kernel is a not relocatable (CONFIG_RELOCATABLE=n) then
1601 bzImage will decompress itself to above physical address and
1602 run from there. Otherwise, bzImage will run from the address where
1603 it has been loaded by the boot loader and will ignore above physical
1606 In normal kdump cases one does not have to set/change this option
1607 as now bzImage can be compiled as a completely relocatable image
1608 (CONFIG_RELOCATABLE=y) and be used to load and run from a different
1609 address. This option is mainly useful for the folks who don't want
1610 to use a bzImage for capturing the crash dump and want to use a
1611 vmlinux instead. vmlinux is not relocatable hence a kernel needs
1612 to be specifically compiled to run from a specific memory area
1613 (normally a reserved region) and this option comes handy.
1615 So if you are using bzImage for capturing the crash dump,
1616 leave the value here unchanged to 0x1000000 and set
1617 CONFIG_RELOCATABLE=y. Otherwise if you plan to use vmlinux
1618 for capturing the crash dump change this value to start of
1619 the reserved region. In other words, it can be set based on
1620 the "X" value as specified in the "crashkernel=YM@XM"
1621 command line boot parameter passed to the panic-ed
1622 kernel. Please take a look at Documentation/kdump/kdump.txt
1623 for more details about crash dumps.
1625 Usage of bzImage for capturing the crash dump is recommended as
1626 one does not have to build two kernels. Same kernel can be used
1627 as production kernel and capture kernel. Above option should have
1628 gone away after relocatable bzImage support is introduced. But it
1629 is present because there are users out there who continue to use
1630 vmlinux for dump capture. This option should go away down the
1633 Don't change this unless you know what you are doing.
1636 bool "Build a relocatable kernel"
1639 This builds a kernel image that retains relocation information
1640 so it can be loaded someplace besides the default 1MB.
1641 The relocations tend to make the kernel binary about 10% larger,
1642 but are discarded at runtime.
1644 One use is for the kexec on panic case where the recovery kernel
1645 must live at a different physical address than the primary
1648 Note: If CONFIG_RELOCATABLE=y, then the kernel runs from the address
1649 it has been loaded at and the compile time physical address
1650 (CONFIG_PHYSICAL_START) is used as the minimum location.
1652 config RANDOMIZE_BASE
1653 bool "Randomize the address of the kernel image"
1654 depends on RELOCATABLE
1655 depends on !HIBERNATION
1658 Randomizes the physical and virtual address at which the
1659 kernel image is decompressed, as a security feature that
1660 deters exploit attempts relying on knowledge of the location
1661 of kernel internals.
1663 Entropy is generated using the RDRAND instruction if it is
1664 supported. If RDTSC is supported, it is used as well. If
1665 neither RDRAND nor RDTSC are supported, then randomness is
1666 read from the i8254 timer.
1668 The kernel will be offset by up to RANDOMIZE_BASE_MAX_OFFSET,
1669 and aligned according to PHYSICAL_ALIGN. Since the kernel is
1670 built using 2GiB addressing, and PHYSICAL_ALGIN must be at a
1671 minimum of 2MiB, only 10 bits of entropy is theoretically
1672 possible. At best, due to page table layouts, 64-bit can use
1673 9 bits of entropy and 32-bit uses 8 bits.
1677 config RANDOMIZE_BASE_MAX_OFFSET
1678 hex "Maximum kASLR offset allowed" if EXPERT
1679 depends on RANDOMIZE_BASE
1680 range 0x0 0x20000000 if X86_32
1681 default "0x20000000" if X86_32
1682 range 0x0 0x40000000 if X86_64
1683 default "0x40000000" if X86_64
1685 The lesser of RANDOMIZE_BASE_MAX_OFFSET and available physical
1686 memory is used to determine the maximal offset in bytes that will
1687 be applied to the kernel when kernel Address Space Layout
1688 Randomization (kASLR) is active. This must be a multiple of
1691 On 32-bit this is limited to 512MiB by page table layouts. The
1694 On 64-bit this is limited by how the kernel fixmap page table is
1695 positioned, so this cannot be larger than 1GiB currently. Without
1696 RANDOMIZE_BASE, there is a 512MiB to 1.5GiB split between kernel
1697 and modules. When RANDOMIZE_BASE_MAX_OFFSET is above 512MiB, the
1698 modules area will shrink to compensate, up to the current maximum
1699 1GiB to 1GiB split. The default is 1GiB.
1701 If unsure, leave at the default value.
1703 # Relocation on x86 needs some additional build support
1704 config X86_NEED_RELOCS
1706 depends on RANDOMIZE_BASE || (X86_32 && RELOCATABLE)
1708 config PHYSICAL_ALIGN
1709 hex "Alignment value to which kernel should be aligned"
1711 range 0x2000 0x1000000 if X86_32
1712 range 0x200000 0x1000000 if X86_64
1714 This value puts the alignment restrictions on physical address
1715 where kernel is loaded and run from. Kernel is compiled for an
1716 address which meets above alignment restriction.
1718 If bootloader loads the kernel at a non-aligned address and
1719 CONFIG_RELOCATABLE is set, kernel will move itself to nearest
1720 address aligned to above value and run from there.
1722 If bootloader loads the kernel at a non-aligned address and
1723 CONFIG_RELOCATABLE is not set, kernel will ignore the run time
1724 load address and decompress itself to the address it has been
1725 compiled for and run from there. The address for which kernel is
1726 compiled already meets above alignment restrictions. Hence the
1727 end result is that kernel runs from a physical address meeting
1728 above alignment restrictions.
1730 On 32-bit this value must be a multiple of 0x2000. On 64-bit
1731 this value must be a multiple of 0x200000.
1733 Don't change this unless you know what you are doing.
1736 bool "Support for hot-pluggable CPUs"
1739 Say Y here to allow turning CPUs off and on. CPUs can be
1740 controlled through /sys/devices/system/cpu.
1741 ( Note: power management support will enable this option
1742 automatically on SMP systems. )
1743 Say N if you want to disable CPU hotplug.
1745 config BOOTPARAM_HOTPLUG_CPU0
1746 bool "Set default setting of cpu0_hotpluggable"
1748 depends on HOTPLUG_CPU
1750 Set whether default state of cpu0_hotpluggable is on or off.
1752 Say Y here to enable CPU0 hotplug by default. If this switch
1753 is turned on, there is no need to give cpu0_hotplug kernel
1754 parameter and the CPU0 hotplug feature is enabled by default.
1756 Please note: there are two known CPU0 dependencies if you want
1757 to enable the CPU0 hotplug feature either by this switch or by
1758 cpu0_hotplug kernel parameter.
1760 First, resume from hibernate or suspend always starts from CPU0.
1761 So hibernate and suspend are prevented if CPU0 is offline.
1763 Second dependency is PIC interrupts always go to CPU0. CPU0 can not
1764 offline if any interrupt can not migrate out of CPU0. There may
1765 be other CPU0 dependencies.
1767 Please make sure the dependencies are under your control before
1768 you enable this feature.
1770 Say N if you don't want to enable CPU0 hotplug feature by default.
1771 You still can enable the CPU0 hotplug feature at boot by kernel
1772 parameter cpu0_hotplug.
1774 config DEBUG_HOTPLUG_CPU0
1776 prompt "Debug CPU0 hotplug"
1777 depends on HOTPLUG_CPU
1779 Enabling this option offlines CPU0 (if CPU0 can be offlined) as
1780 soon as possible and boots up userspace with CPU0 offlined. User
1781 can online CPU0 back after boot time.
1783 To debug CPU0 hotplug, you need to enable CPU0 offline/online
1784 feature by either turning on CONFIG_BOOTPARAM_HOTPLUG_CPU0 during
1785 compilation or giving cpu0_hotplug kernel parameter at boot.
1791 prompt "Disable the 32-bit vDSO (needed for glibc 2.3.3)"
1792 depends on X86_32 || IA32_EMULATION
1794 Certain buggy versions of glibc will crash if they are
1795 presented with a 32-bit vDSO that is not mapped at the address
1796 indicated in its segment table.
1798 The bug was introduced by f866314b89d56845f55e6f365e18b31ec978ec3a
1799 and fixed by 3b3ddb4f7db98ec9e912ccdf54d35df4aa30e04a and
1800 49ad572a70b8aeb91e57483a11dd1b77e31c4468. Glibc 2.3.3 is
1801 the only released version with the bug, but OpenSUSE 9
1802 contains a buggy "glibc 2.3.2".
1804 The symptom of the bug is that everything crashes on startup, saying:
1805 dl_main: Assertion `(void *) ph->p_vaddr == _rtld_local._dl_sysinfo_dso' failed!
1807 Saying Y here changes the default value of the vdso32 boot
1808 option from 1 to 0, which turns off the 32-bit vDSO entirely.
1809 This works around the glibc bug but hurts performance.
1811 If unsure, say N: if you are compiling your own kernel, you
1812 are unlikely to be using a buggy version of glibc.
1815 bool "Built-in kernel command line"
1817 Allow for specifying boot arguments to the kernel at
1818 build time. On some systems (e.g. embedded ones), it is
1819 necessary or convenient to provide some or all of the
1820 kernel boot arguments with the kernel itself (that is,
1821 to not rely on the boot loader to provide them.)
1823 To compile command line arguments into the kernel,
1824 set this option to 'Y', then fill in the
1825 the boot arguments in CONFIG_CMDLINE.
1827 Systems with fully functional boot loaders (i.e. non-embedded)
1828 should leave this option set to 'N'.
1831 string "Built-in kernel command string"
1832 depends on CMDLINE_BOOL
1835 Enter arguments here that should be compiled into the kernel
1836 image and used at boot time. If the boot loader provides a
1837 command line at boot time, it is appended to this string to
1838 form the full kernel command line, when the system boots.
1840 However, you can use the CONFIG_CMDLINE_OVERRIDE option to
1841 change this behavior.
1843 In most cases, the command line (whether built-in or provided
1844 by the boot loader) should specify the device for the root
1847 config CMDLINE_OVERRIDE
1848 bool "Built-in command line overrides boot loader arguments"
1849 depends on CMDLINE_BOOL
1851 Set this option to 'Y' to have the kernel ignore the boot loader
1852 command line, and use ONLY the built-in command line.
1854 This is used to work around broken boot loaders. This should
1855 be set to 'N' under normal conditions.
1859 config ARCH_ENABLE_MEMORY_HOTPLUG
1861 depends on X86_64 || (X86_32 && HIGHMEM)
1863 config ARCH_ENABLE_MEMORY_HOTREMOVE
1865 depends on MEMORY_HOTPLUG
1867 config USE_PERCPU_NUMA_NODE_ID
1871 config ARCH_ENABLE_SPLIT_PMD_PTLOCK
1873 depends on X86_64 || X86_PAE
1875 menu "Power management and ACPI options"
1877 config ARCH_HIBERNATION_HEADER
1879 depends on X86_64 && HIBERNATION
1881 source "kernel/power/Kconfig"
1883 source "drivers/acpi/Kconfig"
1885 source "drivers/sfi/Kconfig"
1892 tristate "APM (Advanced Power Management) BIOS support"
1893 depends on X86_32 && PM_SLEEP
1895 APM is a BIOS specification for saving power using several different
1896 techniques. This is mostly useful for battery powered laptops with
1897 APM compliant BIOSes. If you say Y here, the system time will be
1898 reset after a RESUME operation, the /proc/apm device will provide
1899 battery status information, and user-space programs will receive
1900 notification of APM "events" (e.g. battery status change).
1902 If you select "Y" here, you can disable actual use of the APM
1903 BIOS by passing the "apm=off" option to the kernel at boot time.
1905 Note that the APM support is almost completely disabled for
1906 machines with more than one CPU.
1908 In order to use APM, you will need supporting software. For location
1909 and more information, read <file:Documentation/power/apm-acpi.txt>
1910 and the Battery Powered Linux mini-HOWTO, available from
1911 <http://www.tldp.org/docs.html#howto>.
1913 This driver does not spin down disk drives (see the hdparm(8)
1914 manpage ("man 8 hdparm") for that), and it doesn't turn off
1915 VESA-compliant "green" monitors.
1917 This driver does not support the TI 4000M TravelMate and the ACER
1918 486/DX4/75 because they don't have compliant BIOSes. Many "green"
1919 desktop machines also don't have compliant BIOSes, and this driver
1920 may cause those machines to panic during the boot phase.
1922 Generally, if you don't have a battery in your machine, there isn't
1923 much point in using this driver and you should say N. If you get
1924 random kernel OOPSes or reboots that don't seem to be related to
1925 anything, try disabling/enabling this option (or disabling/enabling
1928 Some other things you should try when experiencing seemingly random,
1931 1) make sure that you have enough swap space and that it is
1933 2) pass the "no-hlt" option to the kernel
1934 3) switch on floating point emulation in the kernel and pass
1935 the "no387" option to the kernel
1936 4) pass the "floppy=nodma" option to the kernel
1937 5) pass the "mem=4M" option to the kernel (thereby disabling
1938 all but the first 4 MB of RAM)
1939 6) make sure that the CPU is not over clocked.
1940 7) read the sig11 FAQ at <http://www.bitwizard.nl/sig11/>
1941 8) disable the cache from your BIOS settings
1942 9) install a fan for the video card or exchange video RAM
1943 10) install a better fan for the CPU
1944 11) exchange RAM chips
1945 12) exchange the motherboard.
1947 To compile this driver as a module, choose M here: the
1948 module will be called apm.
1952 config APM_IGNORE_USER_SUSPEND
1953 bool "Ignore USER SUSPEND"
1955 This option will ignore USER SUSPEND requests. On machines with a
1956 compliant APM BIOS, you want to say N. However, on the NEC Versa M
1957 series notebooks, it is necessary to say Y because of a BIOS bug.
1959 config APM_DO_ENABLE
1960 bool "Enable PM at boot time"
1962 Enable APM features at boot time. From page 36 of the APM BIOS
1963 specification: "When disabled, the APM BIOS does not automatically
1964 power manage devices, enter the Standby State, enter the Suspend
1965 State, or take power saving steps in response to CPU Idle calls."
1966 This driver will make CPU Idle calls when Linux is idle (unless this
1967 feature is turned off -- see "Do CPU IDLE calls", below). This
1968 should always save battery power, but more complicated APM features
1969 will be dependent on your BIOS implementation. You may need to turn
1970 this option off if your computer hangs at boot time when using APM
1971 support, or if it beeps continuously instead of suspending. Turn
1972 this off if you have a NEC UltraLite Versa 33/C or a Toshiba
1973 T400CDT. This is off by default since most machines do fine without
1978 bool "Make CPU Idle calls when idle"
1980 Enable calls to APM CPU Idle/CPU Busy inside the kernel's idle loop.
1981 On some machines, this can activate improved power savings, such as
1982 a slowed CPU clock rate, when the machine is idle. These idle calls
1983 are made after the idle loop has run for some length of time (e.g.,
1984 333 mS). On some machines, this will cause a hang at boot time or
1985 whenever the CPU becomes idle. (On machines with more than one CPU,
1986 this option does nothing.)
1988 config APM_DISPLAY_BLANK
1989 bool "Enable console blanking using APM"
1991 Enable console blanking using the APM. Some laptops can use this to
1992 turn off the LCD backlight when the screen blanker of the Linux
1993 virtual console blanks the screen. Note that this is only used by
1994 the virtual console screen blanker, and won't turn off the backlight
1995 when using the X Window system. This also doesn't have anything to
1996 do with your VESA-compliant power-saving monitor. Further, this
1997 option doesn't work for all laptops -- it might not turn off your
1998 backlight at all, or it might print a lot of errors to the console,
1999 especially if you are using gpm.
2001 config APM_ALLOW_INTS
2002 bool "Allow interrupts during APM BIOS calls"
2004 Normally we disable external interrupts while we are making calls to
2005 the APM BIOS as a measure to lessen the effects of a badly behaving
2006 BIOS implementation. The BIOS should reenable interrupts if it
2007 needs to. Unfortunately, some BIOSes do not -- especially those in
2008 many of the newer IBM Thinkpads. If you experience hangs when you
2009 suspend, try setting this to Y. Otherwise, say N.
2013 source "drivers/cpufreq/Kconfig"
2015 source "drivers/cpuidle/Kconfig"
2017 source "drivers/idle/Kconfig"
2022 menu "Bus options (PCI etc.)"
2028 Find out whether you have a PCI motherboard. PCI is the name of a
2029 bus system, i.e. the way the CPU talks to the other stuff inside
2030 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
2031 VESA. If you have PCI, say Y, otherwise N.
2034 prompt "PCI access mode"
2035 depends on X86_32 && PCI
2038 On PCI systems, the BIOS can be used to detect the PCI devices and
2039 determine their configuration. However, some old PCI motherboards
2040 have BIOS bugs and may crash if this is done. Also, some embedded
2041 PCI-based systems don't have any BIOS at all. Linux can also try to
2042 detect the PCI hardware directly without using the BIOS.
2044 With this option, you can specify how Linux should detect the
2045 PCI devices. If you choose "BIOS", the BIOS will be used,
2046 if you choose "Direct", the BIOS won't be used, and if you
2047 choose "MMConfig", then PCI Express MMCONFIG will be used.
2048 If you choose "Any", the kernel will try MMCONFIG, then the
2049 direct access method and falls back to the BIOS if that doesn't
2050 work. If unsure, go with the default, which is "Any".
2055 config PCI_GOMMCONFIG
2072 depends on X86_32 && PCI && (PCI_GOBIOS || PCI_GOANY)
2074 # x86-64 doesn't support PCI BIOS access from long mode so always go direct.
2077 depends on PCI && (X86_64 || (PCI_GODIRECT || PCI_GOANY || PCI_GOOLPC || PCI_GOMMCONFIG))
2081 depends on X86_32 && PCI && (ACPI || SFI) && (PCI_GOMMCONFIG || PCI_GOANY)
2085 depends on PCI && OLPC && (PCI_GOOLPC || PCI_GOANY)
2089 depends on PCI && XEN
2097 bool "Support mmconfig PCI config space access"
2098 depends on X86_64 && PCI && ACPI
2100 config PCI_CNB20LE_QUIRK
2101 bool "Read CNB20LE Host Bridge Windows" if EXPERT
2104 Read the PCI windows out of the CNB20LE host bridge. This allows
2105 PCI hotplug to work on systems with the CNB20LE chipset which do
2108 There's no public spec for this chipset, and this functionality
2109 is known to be incomplete.
2111 You should say N unless you know you need this.
2113 source "drivers/pci/pcie/Kconfig"
2115 source "drivers/pci/Kconfig"
2117 # x86_64 have no ISA slots, but can have ISA-style DMA.
2119 bool "ISA-style DMA support" if (X86_64 && EXPERT)
2122 Enables ISA-style DMA support for devices requiring such controllers.
2130 Find out whether you have ISA slots on your motherboard. ISA is the
2131 name of a bus system, i.e. the way the CPU talks to the other stuff
2132 inside your box. Other bus systems are PCI, EISA, MicroChannel
2133 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
2134 newer boards don't support it. If you have ISA, say Y, otherwise N.
2140 The Extended Industry Standard Architecture (EISA) bus was
2141 developed as an open alternative to the IBM MicroChannel bus.
2143 The EISA bus provided some of the features of the IBM MicroChannel
2144 bus while maintaining backward compatibility with cards made for
2145 the older ISA bus. The EISA bus saw limited use between 1988 and
2146 1995 when it was made obsolete by the PCI bus.
2148 Say Y here if you are building a kernel for an EISA-based machine.
2152 source "drivers/eisa/Kconfig"
2155 tristate "NatSemi SCx200 support"
2157 This provides basic support for National Semiconductor's
2158 (now AMD's) Geode processors. The driver probes for the
2159 PCI-IDs of several on-chip devices, so its a good dependency
2160 for other scx200_* drivers.
2162 If compiled as a module, the driver is named scx200.
2164 config SCx200HR_TIMER
2165 tristate "NatSemi SCx200 27MHz High-Resolution Timer Support"
2169 This driver provides a clocksource built upon the on-chip
2170 27MHz high-resolution timer. Its also a workaround for
2171 NSC Geode SC-1100's buggy TSC, which loses time when the
2172 processor goes idle (as is done by the scheduler). The
2173 other workaround is idle=poll boot option.
2176 bool "One Laptop Per Child support"
2183 Add support for detecting the unique features of the OLPC
2187 bool "OLPC XO-1 Power Management"
2188 depends on OLPC && MFD_CS5535 && PM_SLEEP
2191 Add support for poweroff and suspend of the OLPC XO-1 laptop.
2194 bool "OLPC XO-1 Real Time Clock"
2195 depends on OLPC_XO1_PM && RTC_DRV_CMOS
2197 Add support for the XO-1 real time clock, which can be used as a
2198 programmable wakeup source.
2201 bool "OLPC XO-1 SCI extras"
2202 depends on OLPC && OLPC_XO1_PM
2208 Add support for SCI-based features of the OLPC XO-1 laptop:
2209 - EC-driven system wakeups
2213 - AC adapter status updates
2214 - Battery status updates
2216 config OLPC_XO15_SCI
2217 bool "OLPC XO-1.5 SCI extras"
2218 depends on OLPC && ACPI
2221 Add support for SCI-based features of the OLPC XO-1.5 laptop:
2222 - EC-driven system wakeups
2223 - AC adapter status updates
2224 - Battery status updates
2227 bool "PCEngines ALIX System Support (LED setup)"
2230 This option enables system support for the PCEngines ALIX.
2231 At present this just sets up LEDs for GPIO control on
2232 ALIX2/3/6 boards. However, other system specific setup should
2235 Note: You must still enable the drivers for GPIO and LED support
2236 (GPIO_CS5535 & LEDS_GPIO) to actually use the LEDs
2238 Note: You have to set alix.force=1 for boards with Award BIOS.
2241 bool "Soekris Engineering net5501 System Support (LEDS, GPIO, etc)"
2244 This option enables system support for the Soekris Engineering net5501.
2247 bool "Traverse Technologies GEOS System Support (LEDS, GPIO, etc)"
2251 This option enables system support for the Traverse Technologies GEOS.
2254 bool "Technologic Systems TS-5500 platform support"
2256 select CHECK_SIGNATURE
2260 This option enables system support for the Technologic Systems TS-5500.
2266 depends on CPU_SUP_AMD && PCI
2268 source "drivers/pcmcia/Kconfig"
2270 source "drivers/pci/hotplug/Kconfig"
2273 tristate "RapidIO support"
2277 If enabled this option will include drivers and the core
2278 infrastructure code to support RapidIO interconnect devices.
2280 source "drivers/rapidio/Kconfig"
2283 bool "Mark VGA/VBE/EFI FB as generic system framebuffer"
2285 Firmwares often provide initial graphics framebuffers so the BIOS,
2286 bootloader or kernel can show basic video-output during boot for
2287 user-guidance and debugging. Historically, x86 used the VESA BIOS
2288 Extensions and EFI-framebuffers for this, which are mostly limited
2290 This option, if enabled, marks VGA/VBE/EFI framebuffers as generic
2291 framebuffers so the new generic system-framebuffer drivers can be
2292 used on x86. If the framebuffer is not compatible with the generic
2293 modes, it is adverticed as fallback platform framebuffer so legacy
2294 drivers like efifb, vesafb and uvesafb can pick it up.
2295 If this option is not selected, all system framebuffers are always
2296 marked as fallback platform framebuffers as usual.
2298 Note: Legacy fbdev drivers, including vesafb, efifb, uvesafb, will
2299 not be able to pick up generic system framebuffers if this option
2300 is selected. You are highly encouraged to enable simplefb as
2301 replacement if you select this option. simplefb can correctly deal
2302 with generic system framebuffers. But you should still keep vesafb
2303 and others enabled as fallback if a system framebuffer is
2304 incompatible with simplefb.
2311 menu "Executable file formats / Emulations"
2313 source "fs/Kconfig.binfmt"
2315 config IA32_EMULATION
2316 bool "IA32 Emulation"
2319 select COMPAT_BINFMT_ELF
2322 Include code to run legacy 32-bit programs under a
2323 64-bit kernel. You should likely turn this on, unless you're
2324 100% sure that you don't have any 32-bit programs left.
2327 tristate "IA32 a.out support"
2328 depends on IA32_EMULATION
2330 Support old a.out binaries in the 32bit emulation.
2333 bool "x32 ABI for 64-bit mode"
2334 depends on X86_64 && IA32_EMULATION
2336 Include code to run binaries for the x32 native 32-bit ABI
2337 for 64-bit processors. An x32 process gets access to the
2338 full 64-bit register file and wide data path while leaving
2339 pointers at 32 bits for smaller memory footprint.
2341 You will need a recent binutils (2.22 or later) with
2342 elf32_x86_64 support enabled to compile a kernel with this
2347 depends on IA32_EMULATION || X86_X32
2348 select ARCH_WANT_OLD_COMPAT_IPC
2351 config COMPAT_FOR_U64_ALIGNMENT
2354 config SYSVIPC_COMPAT
2366 config HAVE_ATOMIC_IOMAP
2370 config X86_DEV_DMA_OPS
2372 depends on X86_64 || STA2X11
2374 config X86_DMA_REMAP
2382 To be selected by modules requiring access to the Intel OnChip System
2383 Fabric (IOSF) Sideband MailBox Interface (MBI). For MBI platforms
2386 source "net/Kconfig"
2388 source "drivers/Kconfig"
2390 source "drivers/firmware/Kconfig"
2394 source "arch/x86/Kconfig.debug"
2396 source "security/Kconfig"
2398 source "crypto/Kconfig"
2400 source "arch/x86/kvm/Kconfig"
2402 source "lib/Kconfig"