| blob | 3e0f80a764a78b7a50a27d387bae023728805b57 |
1 # x86 configuration
2 mainmenu "Linux Kernel Configuration for x86"
4 # Select 32 or 64 bit
5 config 64BIT
6 bool "64-bit kernel" if ARCH = "x86"
7 default ARCH = "x86_64"
8 ---help---
9 Say yes to build a 64-bit kernel - formerly known as x86_64
10 Say no to build a 32-bit kernel - formerly known as i386
12 config X86_32
13 def_bool !64BIT
15 config X86_64
16 def_bool 64BIT
18 ### Arch settings
19 config X86
20 def_bool y
21 select HAVE_AOUT if X86_32
22 select HAVE_READQ
23 select HAVE_WRITEQ
24 select HAVE_UNSTABLE_SCHED_CLOCK
25 select HAVE_IDE
26 select HAVE_OPROFILE
27 select HAVE_IOREMAP_PROT
28 select HAVE_KPROBES
29 select ARCH_WANT_OPTIONAL_GPIOLIB
30 select ARCH_WANT_FRAME_POINTERS
31 select HAVE_KRETPROBES
32 select HAVE_FTRACE_MCOUNT_RECORD
33 select HAVE_DYNAMIC_FTRACE
34 select HAVE_FUNCTION_TRACER
35 select HAVE_FUNCTION_GRAPH_TRACER
36 select HAVE_FUNCTION_TRACE_MCOUNT_TEST
37 select HAVE_FTRACE_NMI_ENTER if DYNAMIC_FTRACE
38 select HAVE_FTRACE_SYSCALLS
39 select HAVE_KVM
40 select HAVE_ARCH_KGDB
41 select HAVE_ARCH_TRACEHOOK
42 select HAVE_GENERIC_DMA_COHERENT if X86_32
43 select HAVE_EFFICIENT_UNALIGNED_ACCESS
44 select USER_STACKTRACE_SUPPORT
45 select HAVE_DMA_API_DEBUG
46 select HAVE_KERNEL_GZIP
47 select HAVE_KERNEL_BZIP2
48 select HAVE_KERNEL_LZMA
50 config OUTPUT_FORMAT
51 string
52 default "elf32-i386" if X86_32
53 default "elf64-x86-64" if X86_64
55 config ARCH_DEFCONFIG
56 string
57 default "arch/x86/configs/i386_defconfig" if X86_32
58 default "arch/x86/configs/x86_64_defconfig" if X86_64
60 config GENERIC_TIME
61 def_bool y
63 config GENERIC_CMOS_UPDATE
64 def_bool y
66 config CLOCKSOURCE_WATCHDOG
67 def_bool y
69 config GENERIC_CLOCKEVENTS
70 def_bool y
72 config GENERIC_CLOCKEVENTS_BROADCAST
73 def_bool y
74 depends on X86_64 || (X86_32 && X86_LOCAL_APIC)
76 config LOCKDEP_SUPPORT
77 def_bool y
79 config STACKTRACE_SUPPORT
80 def_bool y
82 config HAVE_LATENCYTOP_SUPPORT
83 def_bool y
85 config FAST_CMPXCHG_LOCAL
86 bool
87 default y
89 config MMU
90 def_bool y
92 config ZONE_DMA
93 def_bool y
95 config SBUS
96 bool
98 config GENERIC_ISA_DMA
99 def_bool y
101 config GENERIC_IOMAP
102 def_bool y
104 config GENERIC_BUG
105 def_bool y
106 depends on BUG
107 select GENERIC_BUG_RELATIVE_POINTERS if X86_64
109 config GENERIC_BUG_RELATIVE_POINTERS
110 bool
112 config GENERIC_HWEIGHT
113 def_bool y
115 config GENERIC_GPIO
116 bool
118 config ARCH_MAY_HAVE_PC_FDC
119 def_bool y
121 config RWSEM_GENERIC_SPINLOCK
122 def_bool !X86_XADD
124 config RWSEM_XCHGADD_ALGORITHM
125 def_bool X86_XADD
127 config ARCH_HAS_CPU_IDLE_WAIT
128 def_bool y
130 config GENERIC_CALIBRATE_DELAY
131 def_bool y
133 config GENERIC_TIME_VSYSCALL
134 bool
135 default X86_64
137 config ARCH_HAS_CPU_RELAX
138 def_bool y
140 config ARCH_HAS_DEFAULT_IDLE
141 def_bool y
143 config ARCH_HAS_CACHE_LINE_SIZE
144 def_bool y
146 config HAVE_SETUP_PER_CPU_AREA
147 def_bool y
149 config HAVE_DYNAMIC_PER_CPU_AREA
150 def_bool y
152 config HAVE_CPUMASK_OF_CPU_MAP
153 def_bool X86_64_SMP
155 config ARCH_HIBERNATION_POSSIBLE
156 def_bool y
158 config ARCH_SUSPEND_POSSIBLE
159 def_bool y
161 config ZONE_DMA32
162 bool
163 default X86_64
165 config ARCH_POPULATES_NODE_MAP
166 def_bool y
168 config AUDIT_ARCH
169 bool
170 default X86_64
172 config ARCH_SUPPORTS_OPTIMIZED_INLINING
173 def_bool y
175 config ARCH_SUPPORTS_DEBUG_PAGEALLOC
176 def_bool y
178 # Use the generic interrupt handling code in kernel/irq/:
179 config GENERIC_HARDIRQS
180 bool
181 default y
183 config GENERIC_HARDIRQS_NO__DO_IRQ
184 def_bool y
186 config GENERIC_IRQ_PROBE
187 bool
188 default y
190 config GENERIC_PENDING_IRQ
191 bool
192 depends on GENERIC_HARDIRQS && SMP
193 default y
195 config USE_GENERIC_SMP_HELPERS
196 def_bool y
197 depends on SMP
199 config X86_32_SMP
200 def_bool y
201 depends on X86_32 && SMP
203 config X86_64_SMP
204 def_bool y
205 depends on X86_64 && SMP
207 config X86_HT
208 bool
209 depends on SMP
210 default y
212 config X86_TRAMPOLINE
213 bool
214 depends on SMP || (64BIT && ACPI_SLEEP)
215 default y
217 config X86_32_LAZY_GS
218 def_bool y
219 depends on X86_32 && !CC_STACKPROTECTOR
221 config KTIME_SCALAR
222 def_bool X86_32
223 source "init/Kconfig"
224 source "kernel/Kconfig.freezer"
226 menu "Processor type and features"
228 source "kernel/time/Kconfig"
230 config SMP
231 bool "Symmetric multi-processing support"
232 ---help---
233 This enables support for systems with more than one CPU. If you have
234 a system with only one CPU, like most personal computers, say N. If
235 you have a system with more than one CPU, say Y.
237 If you say N here, the kernel will run on single and multiprocessor
238 machines, but will use only one CPU of a multiprocessor machine. If
239 you say Y here, the kernel will run on many, but not all,
240 singleprocessor machines. On a singleprocessor machine, the kernel
241 will run faster if you say N here.
243 Note that if you say Y here and choose architecture "586" or
244 "Pentium" under "Processor family", the kernel will not work on 486
245 architectures. Similarly, multiprocessor kernels for the "PPro"
246 architecture may not work on all Pentium based boards.
248 People using multiprocessor machines who say Y here should also say
249 Y to "Enhanced Real Time Clock Support", below. The "Advanced Power
250 Management" code will be disabled if you say Y here.
252 See also <file:Documentation/i386/IO-APIC.txt>,
253 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
254 <http://www.tldp.org/docs.html#howto>.
256 If you don't know what to do here, say N.
258 config X86_X2APIC
259 bool "Support x2apic"
260 depends on X86_LOCAL_APIC && X86_64 && INTR_REMAP
261 ---help---
262 This enables x2apic support on CPUs that have this feature.
264 This allows 32-bit apic IDs (so it can support very large systems),
265 and accesses the local apic via MSRs not via mmio.
267 If you don't know what to do here, say N.
269 config SPARSE_IRQ
270 bool "Support sparse irq numbering"
271 depends on PCI_MSI || HT_IRQ
272 ---help---
273 This enables support for sparse irqs. This is useful for distro
274 kernels that want to define a high CONFIG_NR_CPUS value but still
275 want to have low kernel memory footprint on smaller machines.
277 ( Sparse IRQs can also be beneficial on NUMA boxes, as they spread
278 out the irq_desc[] array in a more NUMA-friendly way. )
280 If you don't know what to do here, say N.
282 config NUMA_MIGRATE_IRQ_DESC
283 bool "Move irq desc when changing irq smp_affinity"
284 depends on SPARSE_IRQ && NUMA
285 default n
286 ---help---
287 This enables moving irq_desc to cpu/node that irq will use handled.
289 If you don't know what to do here, say N.
291 config X86_MPPARSE
292 bool "Enable MPS table" if ACPI
293 default y
294 depends on X86_LOCAL_APIC
295 ---help---
296 For old smp systems that do not have proper acpi support. Newer systems
297 (esp with 64bit cpus) with acpi support, MADT and DSDT will override it
299 config X86_BIGSMP
300 bool "Support for big SMP systems with more than 8 CPUs"
301 depends on X86_32 && SMP
302 ---help---
303 This option is needed for the systems that have more than 8 CPUs
305 if X86_32
306 config X86_EXTENDED_PLATFORM
307 bool "Support for extended (non-PC) x86 platforms"
308 default y
309 ---help---
310 If you disable this option then the kernel will only support
311 standard PC platforms. (which covers the vast majority of
312 systems out there.)
314 If you enable this option then you'll be able to select support
315 for the following (non-PC) 32 bit x86 platforms:
316 AMD Elan
317 NUMAQ (IBM/Sequent)
318 RDC R-321x SoC
319 SGI 320/540 (Visual Workstation)
320 Summit/EXA (IBM x440)
321 Unisys ES7000 IA32 series
323 If you have one of these systems, or if you want to build a
324 generic distribution kernel, say Y here - otherwise say N.
325 endif
327 if X86_64
328 config X86_EXTENDED_PLATFORM
329 bool "Support for extended (non-PC) x86 platforms"
330 default y
331 ---help---
332 If you disable this option then the kernel will only support
333 standard PC platforms. (which covers the vast majority of
334 systems out there.)
336 If you enable this option then you'll be able to select support
337 for the following (non-PC) 64 bit x86 platforms:
338 ScaleMP vSMP
339 SGI Ultraviolet
341 If you have one of these systems, or if you want to build a
342 generic distribution kernel, say Y here - otherwise say N.
343 endif
344 # This is an alphabetically sorted list of 64 bit extended platforms
345 # Please maintain the alphabetic order if and when there are additions
347 config X86_VSMP
348 bool "ScaleMP vSMP"
349 select PARAVIRT
350 depends on X86_64 && PCI
351 depends on X86_EXTENDED_PLATFORM
352 ---help---
353 Support for ScaleMP vSMP systems. Say 'Y' here if this kernel is
354 supposed to run on these EM64T-based machines. Only choose this option
355 if you have one of these machines.
357 config X86_UV
358 bool "SGI Ultraviolet"
359 depends on X86_64
360 depends on X86_EXTENDED_PLATFORM
361 select X86_X2APIC
362 ---help---
363 This option is needed in order to support SGI Ultraviolet systems.
364 If you don't have one of these, you should say N here.
366 # Following is an alphabetically sorted list of 32 bit extended platforms
367 # Please maintain the alphabetic order if and when there are additions
369 config X86_ELAN
370 bool "AMD Elan"
371 depends on X86_32
372 depends on X86_EXTENDED_PLATFORM
373 ---help---
374 Select this for an AMD Elan processor.
376 Do not use this option for K6/Athlon/Opteron processors!
378 If unsure, choose "PC-compatible" instead.
380 config X86_RDC321X
381 bool "RDC R-321x SoC"
382 depends on X86_32
383 depends on X86_EXTENDED_PLATFORM
384 select M486
385 select X86_REBOOTFIXUPS
386 ---help---
387 This option is needed for RDC R-321x system-on-chip, also known
388 as R-8610-(G).
389 If you don't have one of these chips, you should say N here.
391 config X86_32_NON_STANDARD
392 bool "Support non-standard 32-bit SMP architectures"
393 depends on X86_32 && SMP
394 depends on X86_EXTENDED_PLATFORM
395 ---help---
396 This option compiles in the NUMAQ, Summit, bigsmp, ES7000, default
397 subarchitectures. It is intended for a generic binary kernel.
398 if you select them all, kernel will probe it one by one. and will
399 fallback to default.
401 # Alphabetically sorted list of Non standard 32 bit platforms
403 config X86_NUMAQ
404 bool "NUMAQ (IBM/Sequent)"
405 depends on X86_32_NON_STANDARD
406 select NUMA
407 select X86_MPPARSE
408 ---help---
409 This option is used for getting Linux to run on a NUMAQ (IBM/Sequent)
410 NUMA multiquad box. This changes the way that processors are
411 bootstrapped, and uses Clustered Logical APIC addressing mode instead
412 of Flat Logical. You will need a new lynxer.elf file to flash your
413 firmware with - send email to <Martin.Bligh@us.ibm.com>.
415 config X86_VISWS
416 bool "SGI 320/540 (Visual Workstation)"
417 depends on X86_32 && PCI && X86_MPPARSE && PCI_GODIRECT
418 depends on X86_32_NON_STANDARD
419 ---help---
420 The SGI Visual Workstation series is an IA32-based workstation
421 based on SGI systems chips with some legacy PC hardware attached.
423 Say Y here to create a kernel to run on the SGI 320 or 540.
425 A kernel compiled for the Visual Workstation will run on general
426 PCs as well. See <file:Documentation/sgi-visws.txt> for details.
428 config X86_SUMMIT
429 bool "Summit/EXA (IBM x440)"
430 depends on X86_32_NON_STANDARD
431 ---help---
432 This option is needed for IBM systems that use the Summit/EXA chipset.
433 In particular, it is needed for the x440.
435 config X86_ES7000
436 bool "Unisys ES7000 IA32 series"
437 depends on X86_32_NON_STANDARD && X86_BIGSMP
438 ---help---
439 Support for Unisys ES7000 systems. Say 'Y' here if this kernel is
440 supposed to run on an IA32-based Unisys ES7000 system.
442 config SCHED_OMIT_FRAME_POINTER
443 def_bool y
444 prompt "Single-depth WCHAN output"
445 depends on X86
446 ---help---
447 Calculate simpler /proc/<PID>/wchan values. If this option
448 is disabled then wchan values will recurse back to the
449 caller function. This provides more accurate wchan values,
450 at the expense of slightly more scheduling overhead.
452 If in doubt, say "Y".
454 menuconfig PARAVIRT_GUEST
455 bool "Paravirtualized guest support"
456 ---help---
457 Say Y here to get to see options related to running Linux under
458 various hypervisors. This option alone does not add any kernel code.
460 If you say N, all options in this submenu will be skipped and disabled.
462 if PARAVIRT_GUEST
464 source "arch/x86/xen/Kconfig"
466 config VMI
467 bool "VMI Guest support"
468 select PARAVIRT
469 depends on X86_32
470 ---help---
471 VMI provides a paravirtualized interface to the VMware ESX server
472 (it could be used by other hypervisors in theory too, but is not
473 at the moment), by linking the kernel to a GPL-ed ROM module
474 provided by the hypervisor.
476 config KVM_CLOCK
477 bool "KVM paravirtualized clock"
478 select PARAVIRT
479 select PARAVIRT_CLOCK
480 ---help---
481 Turning on this option will allow you to run a paravirtualized clock
482 when running over the KVM hypervisor. Instead of relying on a PIT
483 (or probably other) emulation by the underlying device model, the host
484 provides the guest with timing infrastructure such as time of day, and
485 system time
487 config KVM_GUEST
488 bool "KVM Guest support"
489 select PARAVIRT
490 ---help---
491 This option enables various optimizations for running under the KVM
492 hypervisor.
494 source "arch/x86/lguest/Kconfig"
496 config PARAVIRT
497 bool "Enable paravirtualization code"
498 ---help---
499 This changes the kernel so it can modify itself when it is run
500 under a hypervisor, potentially improving performance significantly
501 over full virtualization. However, when run without a hypervisor
502 the kernel is theoretically slower and slightly larger.
504 config PARAVIRT_CLOCK
505 bool
506 default n
508 endif
510 config PARAVIRT_DEBUG
511 bool "paravirt-ops debugging"
512 depends on PARAVIRT && DEBUG_KERNEL
513 ---help---
514 Enable to debug paravirt_ops internals. Specifically, BUG if
515 a paravirt_op is missing when it is called.
517 config MEMTEST
518 bool "Memtest"
519 ---help---
520 This option adds a kernel parameter 'memtest', which allows memtest
521 to be set.
522 memtest=0, mean disabled; -- default
523 memtest=1, mean do 1 test pattern;
524 ...
525 memtest=4, mean do 4 test patterns.
526 If you are unsure how to answer this question, answer N.
528 config X86_SUMMIT_NUMA
529 def_bool y
530 depends on X86_32 && NUMA && X86_32_NON_STANDARD
532 config X86_CYCLONE_TIMER
533 def_bool y
534 depends on X86_32_NON_STANDARD
536 source "arch/x86/Kconfig.cpu"
538 config HPET_TIMER
539 def_bool X86_64
540 prompt "HPET Timer Support" if X86_32
541 ---help---
542 Use the IA-PC HPET (High Precision Event Timer) to manage
543 time in preference to the PIT and RTC, if a HPET is
544 present.
545 HPET is the next generation timer replacing legacy 8254s.
546 The HPET provides a stable time base on SMP
547 systems, unlike the TSC, but it is more expensive to access,
548 as it is off-chip. You can find the HPET spec at
549 <http://www.intel.com/hardwaredesign/hpetspec_1.pdf>.
551 You can safely choose Y here. However, HPET will only be
552 activated if the platform and the BIOS support this feature.
553 Otherwise the 8254 will be used for timing services.
555 Choose N to continue using the legacy 8254 timer.
557 config HPET_EMULATE_RTC
558 def_bool y
559 depends on HPET_TIMER && (RTC=y || RTC=m || RTC_DRV_CMOS=m || RTC_DRV_CMOS=y)
561 # Mark as embedded because too many people got it wrong.
562 # The code disables itself when not needed.
563 config DMI
564 default y
565 bool "Enable DMI scanning" if EMBEDDED
566 ---help---
567 Enabled scanning of DMI to identify machine quirks. Say Y
568 here unless you have verified that your setup is not
569 affected by entries in the DMI blacklist. Required by PNP
570 BIOS code.
572 config GART_IOMMU
573 bool "GART IOMMU support" if EMBEDDED
574 default y
575 select SWIOTLB
576 select AGP
577 depends on X86_64 && PCI
578 ---help---
579 Support for full DMA access of devices with 32bit memory access only
580 on systems with more than 3GB. This is usually needed for USB,
581 sound, many IDE/SATA chipsets and some other devices.
582 Provides a driver for the AMD Athlon64/Opteron/Turion/Sempron GART
583 based hardware IOMMU and a software bounce buffer based IOMMU used
584 on Intel systems and as fallback.
585 The code is only active when needed (enough memory and limited
586 device) unless CONFIG_IOMMU_DEBUG or iommu=force is specified
587 too.
589 config CALGARY_IOMMU
590 bool "IBM Calgary IOMMU support"
591 select SWIOTLB
592 depends on X86_64 && PCI && EXPERIMENTAL
593 ---help---
594 Support for hardware IOMMUs in IBM's xSeries x366 and x460
595 systems. Needed to run systems with more than 3GB of memory
596 properly with 32-bit PCI devices that do not support DAC
597 (Double Address Cycle). Calgary also supports bus level
598 isolation, where all DMAs pass through the IOMMU. This
599 prevents them from going anywhere except their intended
600 destination. This catches hard-to-find kernel bugs and
601 mis-behaving drivers and devices that do not use the DMA-API
602 properly to set up their DMA buffers. The IOMMU can be
603 turned off at boot time with the iommu=off parameter.
604 Normally the kernel will make the right choice by itself.
605 If unsure, say Y.
607 config CALGARY_IOMMU_ENABLED_BY_DEFAULT
608 def_bool y
609 prompt "Should Calgary be enabled by default?"
610 depends on CALGARY_IOMMU
611 ---help---
612 Should Calgary be enabled by default? if you choose 'y', Calgary
613 will be used (if it exists). If you choose 'n', Calgary will not be
614 used even if it exists. If you choose 'n' and would like to use
615 Calgary anyway, pass 'iommu=calgary' on the kernel command line.
616 If unsure, say Y.
618 config AMD_IOMMU
619 bool "AMD IOMMU support"
620 select SWIOTLB
621 select PCI_MSI
622 depends on X86_64 && PCI && ACPI
623 ---help---
624 With this option you can enable support for AMD IOMMU hardware in
625 your system. An IOMMU is a hardware component which provides
626 remapping of DMA memory accesses from devices. With an AMD IOMMU you
627 can isolate the the DMA memory of different devices and protect the
628 system from misbehaving device drivers or hardware.
630 You can find out if your system has an AMD IOMMU if you look into
631 your BIOS for an option to enable it or if you have an IVRS ACPI
632 table.
634 config AMD_IOMMU_STATS
635 bool "Export AMD IOMMU statistics to debugfs"
636 depends on AMD_IOMMU
637 select DEBUG_FS
638 ---help---
639 This option enables code in the AMD IOMMU driver to collect various
640 statistics about whats happening in the driver and exports that
641 information to userspace via debugfs.
642 If unsure, say N.
644 # need this always selected by IOMMU for the VIA workaround
645 config SWIOTLB
646 def_bool y if X86_64
647 ---help---
648 Support for software bounce buffers used on x86-64 systems
649 which don't have a hardware IOMMU (e.g. the current generation
650 of Intel's x86-64 CPUs). Using this PCI devices which can only
651 access 32-bits of memory can be used on systems with more than
652 3 GB of memory. If unsure, say Y.
654 config IOMMU_HELPER
655 def_bool (CALGARY_IOMMU || GART_IOMMU || SWIOTLB || AMD_IOMMU)
657 config IOMMU_API
658 def_bool (AMD_IOMMU || DMAR)
660 config MAXSMP
661 bool "Configure Maximum number of SMP Processors and NUMA Nodes"
662 depends on X86_64 && SMP && DEBUG_KERNEL && EXPERIMENTAL
663 select CPUMASK_OFFSTACK
664 default n
665 ---help---
666 Configure maximum number of CPUS and NUMA Nodes for this architecture.
667 If unsure, say N.
669 config NR_CPUS
670 int "Maximum number of CPUs" if SMP && !MAXSMP
671 range 2 512 if SMP && !MAXSMP
672 default "1" if !SMP
673 default "4096" if MAXSMP
674 default "32" if SMP && (X86_NUMAQ || X86_SUMMIT || X86_BIGSMP || X86_ES7000)
675 default "8" if SMP
676 ---help---
677 This allows you to specify the maximum number of CPUs which this
678 kernel will support. The maximum supported value is 512 and the
679 minimum value which makes sense is 2.
681 This is purely to save memory - each supported CPU adds
682 approximately eight kilobytes to the kernel image.
684 config SCHED_SMT
685 bool "SMT (Hyperthreading) scheduler support"
686 depends on X86_HT
687 ---help---
688 SMT scheduler support improves the CPU scheduler's decision making
689 when dealing with Intel Pentium 4 chips with HyperThreading at a
690 cost of slightly increased overhead in some places. If unsure say
691 N here.
693 config SCHED_MC
694 def_bool y
695 prompt "Multi-core scheduler support"
696 depends on X86_HT
697 ---help---
698 Multi-core scheduler support improves the CPU scheduler's decision
699 making when dealing with multi-core CPU chips at a cost of slightly
700 increased overhead in some places. If unsure say N here.
702 source "kernel/Kconfig.preempt"
704 config X86_UP_APIC
705 bool "Local APIC support on uniprocessors"
706 depends on X86_32 && !SMP && !X86_32_NON_STANDARD
707 ---help---
708 A local APIC (Advanced Programmable Interrupt Controller) is an
709 integrated interrupt controller in the CPU. If you have a single-CPU
710 system which has a processor with a local APIC, you can say Y here to
711 enable and use it. If you say Y here even though your machine doesn't
712 have a local APIC, then the kernel will still run with no slowdown at
713 all. The local APIC supports CPU-generated self-interrupts (timer,
714 performance counters), and the NMI watchdog which detects hard
715 lockups.
717 config X86_UP_IOAPIC
718 bool "IO-APIC support on uniprocessors"
719 depends on X86_UP_APIC
720 ---help---
721 An IO-APIC (I/O Advanced Programmable Interrupt Controller) is an
722 SMP-capable replacement for PC-style interrupt controllers. Most
723 SMP systems and many recent uniprocessor systems have one.
725 If you have a single-CPU system with an IO-APIC, you can say Y here
726 to use it. If you say Y here even though your machine doesn't have
727 an IO-APIC, then the kernel will still run with no slowdown at all.
729 config X86_LOCAL_APIC
730 def_bool y
731 depends on X86_64 || SMP || X86_32_NON_STANDARD || X86_UP_APIC
733 config X86_IO_APIC
734 def_bool y
735 depends on X86_64 || SMP || X86_32_NON_STANDARD || X86_UP_APIC
737 config X86_VISWS_APIC
738 def_bool y
739 depends on X86_32 && X86_VISWS
741 config X86_REROUTE_FOR_BROKEN_BOOT_IRQS
742 bool "Reroute for broken boot IRQs"
743 default n
744 depends on X86_IO_APIC
745 ---help---
746 This option enables a workaround that fixes a source of
747 spurious interrupts. This is recommended when threaded
748 interrupt handling is used on systems where the generation of
749 superfluous "boot interrupts" cannot be disabled.
751 Some chipsets generate a legacy INTx "boot IRQ" when the IRQ
752 entry in the chipset's IO-APIC is masked (as, e.g. the RT
753 kernel does during interrupt handling). On chipsets where this
754 boot IRQ generation cannot be disabled, this workaround keeps
755 the original IRQ line masked so that only the equivalent "boot
756 IRQ" is delivered to the CPUs. The workaround also tells the
757 kernel to set up the IRQ handler on the boot IRQ line. In this
758 way only one interrupt is delivered to the kernel. Otherwise
759 the spurious second interrupt may cause the kernel to bring
760 down (vital) interrupt lines.
762 Only affects "broken" chipsets. Interrupt sharing may be
763 increased on these systems.
765 config X86_MCE
766 bool "Machine Check Exception"
767 ---help---
768 Machine Check Exception support allows the processor to notify the
769 kernel if it detects a problem (e.g. overheating, component failure).
770 The action the kernel takes depends on the severity of the problem,
771 ranging from a warning message on the console, to halting the machine.
772 Your processor must be a Pentium or newer to support this - check the
773 flags in /proc/cpuinfo for mce. Note that some older Pentium systems
774 have a design flaw which leads to false MCE events - hence MCE is
775 disabled on all P5 processors, unless explicitly enabled with "mce"
776 as a boot argument. Similarly, if MCE is built in and creates a
777 problem on some new non-standard machine, you can boot with "nomce"
778 to disable it. MCE support simply ignores non-MCE processors like
779 the 386 and 486, so nearly everyone can say Y here.
781 config X86_MCE_INTEL
782 def_bool y
783 prompt "Intel MCE features"
784 depends on X86_64 && X86_MCE && X86_LOCAL_APIC
785 ---help---
786 Additional support for intel specific MCE features such as
787 the thermal monitor.
789 config X86_MCE_AMD
790 def_bool y
791 prompt "AMD MCE features"
792 depends on X86_64 && X86_MCE && X86_LOCAL_APIC
793 ---help---
794 Additional support for AMD specific MCE features such as
795 the DRAM Error Threshold.
797 config X86_MCE_THRESHOLD
798 depends on X86_MCE_AMD || X86_MCE_INTEL
799 bool
800 default y
802 config X86_MCE_NONFATAL
803 tristate "Check for non-fatal errors on AMD Athlon/Duron / Intel Pentium 4"
804 depends on X86_32 && X86_MCE
805 ---help---
806 Enabling this feature starts a timer that triggers every 5 seconds which
807 will look at the machine check registers to see if anything happened.
808 Non-fatal problems automatically get corrected (but still logged).
809 Disable this if you don't want to see these messages.
810 Seeing the messages this option prints out may be indicative of dying
811 or out-of-spec (ie, overclocked) hardware.
812 This option only does something on certain CPUs.
813 (AMD Athlon/Duron and Intel Pentium 4)
815 config X86_MCE_P4THERMAL
816 bool "check for P4 thermal throttling interrupt."
817 depends on X86_32 && X86_MCE && (X86_UP_APIC || SMP)
818 ---help---
819 Enabling this feature will cause a message to be printed when the P4
820 enters thermal throttling.
822 config VM86
823 bool "Enable VM86 support" if EMBEDDED
824 default y
825 depends on X86_32
826 ---help---
827 This option is required by programs like DOSEMU to run 16-bit legacy
828 code on X86 processors. It also may be needed by software like
829 XFree86 to initialize some video cards via BIOS. Disabling this
830 option saves about 6k.
832 config TOSHIBA
833 tristate "Toshiba Laptop support"
834 depends on X86_32
835 ---help---
836 This adds a driver to safely access the System Management Mode of
837 the CPU on Toshiba portables with a genuine Toshiba BIOS. It does
838 not work on models with a Phoenix BIOS. The System Management Mode
839 is used to set the BIOS and power saving options on Toshiba portables.
841 For information on utilities to make use of this driver see the
842 Toshiba Linux utilities web site at:
843 <http://www.buzzard.org.uk/toshiba/>.
845 Say Y if you intend to run this kernel on a Toshiba portable.
846 Say N otherwise.
848 config I8K
849 tristate "Dell laptop support"
850 ---help---
851 This adds a driver to safely access the System Management Mode
852 of the CPU on the Dell Inspiron 8000. The System Management Mode
853 is used to read cpu temperature and cooling fan status and to
854 control the fans on the I8K portables.
856 This driver has been tested only on the Inspiron 8000 but it may
857 also work with other Dell laptops. You can force loading on other
858 models by passing the parameter `force=1' to the module. Use at
859 your own risk.
861 For information on utilities to make use of this driver see the
862 I8K Linux utilities web site at:
863 <http://people.debian.org/~dz/i8k/>
865 Say Y if you intend to run this kernel on a Dell Inspiron 8000.
866 Say N otherwise.
868 config X86_REBOOTFIXUPS
869 bool "Enable X86 board specific fixups for reboot"
870 depends on X86_32
871 ---help---
872 This enables chipset and/or board specific fixups to be done
873 in order to get reboot to work correctly. This is only needed on
874 some combinations of hardware and BIOS. The symptom, for which
875 this config is intended, is when reboot ends with a stalled/hung
876 system.
878 Currently, the only fixup is for the Geode machines using
879 CS5530A and CS5536 chipsets and the RDC R-321x SoC.
881 Say Y if you want to enable the fixup. Currently, it's safe to
882 enable this option even if you don't need it.
883 Say N otherwise.
885 config MICROCODE
886 tristate "/dev/cpu/microcode - microcode support"
887 select FW_LOADER
888 ---help---
889 If you say Y here, you will be able to update the microcode on
890 certain Intel and AMD processors. The Intel support is for the
891 IA32 family, e.g. Pentium Pro, Pentium II, Pentium III,
892 Pentium 4, Xeon etc. The AMD support is for family 0x10 and
893 0x11 processors, e.g. Opteron, Phenom and Turion 64 Ultra.
894 You will obviously need the actual microcode binary data itself
895 which is not shipped with the Linux kernel.
897 This option selects the general module only, you need to select
898 at least one vendor specific module as well.
900 To compile this driver as a module, choose M here: the
901 module will be called microcode.
903 config MICROCODE_INTEL
904 bool "Intel microcode patch loading support"
905 depends on MICROCODE
906 default MICROCODE
907 select FW_LOADER
908 ---help---
909 This options enables microcode patch loading support for Intel
910 processors.
912 For latest news and information on obtaining all the required
913 Intel ingredients for this driver, check:
914 <http://www.urbanmyth.org/microcode/>.
916 config MICROCODE_AMD
917 bool "AMD microcode patch loading support"
918 depends on MICROCODE
919 select FW_LOADER
920 ---help---
921 If you select this option, microcode patch loading support for AMD
922 processors will be enabled.
924 config MICROCODE_OLD_INTERFACE
925 def_bool y
926 depends on MICROCODE
928 config X86_MSR
929 tristate "/dev/cpu/*/msr - Model-specific register support"
930 ---help---
931 This device gives privileged processes access to the x86
932 Model-Specific Registers (MSRs). It is a character device with
933 major 202 and minors 0 to 31 for /dev/cpu/0/msr to /dev/cpu/31/msr.
934 MSR accesses are directed to a specific CPU on multi-processor
935 systems.
937 config X86_CPUID
938 tristate "/dev/cpu/*/cpuid - CPU information support"
939 ---help---
940 This device gives processes access to the x86 CPUID instruction to
941 be executed on a specific processor. It is a character device
942 with major 203 and minors 0 to 31 for /dev/cpu/0/cpuid to
943 /dev/cpu/31/cpuid.
945 config X86_CPU_DEBUG
946 tristate "/sys/kernel/debug/x86/cpu/* - CPU Debug support"
947 ---help---
948 If you select this option, this will provide various x86 CPUs
949 information through debugfs.
951 choice
952 prompt "High Memory Support"
953 default HIGHMEM4G if !X86_NUMAQ
954 default HIGHMEM64G if X86_NUMAQ
955 depends on X86_32
957 config NOHIGHMEM
958 bool "off"
959 depends on !X86_NUMAQ
960 ---help---
961 Linux can use up to 64 Gigabytes of physical memory on x86 systems.
962 However, the address space of 32-bit x86 processors is only 4
963 Gigabytes large. That means that, if you have a large amount of
964 physical memory, not all of it can be "permanently mapped" by the
965 kernel. The physical memory that's not permanently mapped is called
966 "high memory".
968 If you are compiling a kernel which will never run on a machine with
969 more than 1 Gigabyte total physical RAM, answer "off" here (default
970 choice and suitable for most users). This will result in a "3GB/1GB"
971 split: 3GB are mapped so that each process sees a 3GB virtual memory
972 space and the remaining part of the 4GB virtual memory space is used
973 by the kernel to permanently map as much physical memory as
974 possible.
976 If the machine has between 1 and 4 Gigabytes physical RAM, then
977 answer "4GB" here.
979 If more than 4 Gigabytes is used then answer "64GB" here. This
980 selection turns Intel PAE (Physical Address Extension) mode on.
981 PAE implements 3-level paging on IA32 processors. PAE is fully
982 supported by Linux, PAE mode is implemented on all recent Intel
983 processors (Pentium Pro and better). NOTE: If you say "64GB" here,
984 then the kernel will not boot on CPUs that don't support PAE!
986 The actual amount of total physical memory will either be
987 auto detected or can be forced by using a kernel command line option
988 such as "mem=256M". (Try "man bootparam" or see the documentation of
989 your boot loader (lilo or loadlin) about how to pass options to the
990 kernel at boot time.)
992 If unsure, say "off".
994 config HIGHMEM4G
995 bool "4GB"
996 depends on !X86_NUMAQ
997 ---help---
998 Select this if you have a 32-bit processor and between 1 and 4
999 gigabytes of physical RAM.
1001 config HIGHMEM64G
1002 bool "64GB"
1003 depends on !M386 && !M486
1004 select X86_PAE
1005 ---help---
1006 Select this if you have a 32-bit processor and more than 4
1007 gigabytes of physical RAM.
1009 endchoice
1011 choice
1012 depends on EXPERIMENTAL
1013 prompt "Memory split" if EMBEDDED
1014 default VMSPLIT_3G
1015 depends on X86_32
1016 ---help---
1017 Select the desired split between kernel and user memory.
1019 If the address range available to the kernel is less than the
1020 physical memory installed, the remaining memory will be available
1021 as "high memory". Accessing high memory is a little more costly
1022 than low memory, as it needs to be mapped into the kernel first.
1023 Note that increasing the kernel address space limits the range
1024 available to user programs, making the address space there
1025 tighter. Selecting anything other than the default 3G/1G split
1026 will also likely make your kernel incompatible with binary-only
1027 kernel modules.
1029 If you are not absolutely sure what you are doing, leave this
1030 option alone!
1032 config VMSPLIT_3G
1033 bool "3G/1G user/kernel split"
1034 config VMSPLIT_3G_OPT
1035 depends on !X86_PAE
1036 bool "3G/1G user/kernel split (for full 1G low memory)"
1037 config VMSPLIT_2G
1038 bool "2G/2G user/kernel split"
1039 config VMSPLIT_2G_OPT
1040 depends on !X86_PAE
1041 bool "2G/2G user/kernel split (for full 2G low memory)"
1042 config VMSPLIT_1G
1043 bool "1G/3G user/kernel split"
1044 endchoice
1046 config PAGE_OFFSET
1047 hex
1048 default 0xB0000000 if VMSPLIT_3G_OPT
1049 default 0x80000000 if VMSPLIT_2G
1050 default 0x78000000 if VMSPLIT_2G_OPT
1051 default 0x40000000 if VMSPLIT_1G
1052 default 0xC0000000
1053 depends on X86_32
1055 config HIGHMEM
1056 def_bool y
1057 depends on X86_32 && (HIGHMEM64G || HIGHMEM4G)
1059 config X86_PAE
1060 bool "PAE (Physical Address Extension) Support"
1061 depends on X86_32 && !HIGHMEM4G
1062 ---help---
1063 PAE is required for NX support, and furthermore enables
1064 larger swapspace support for non-overcommit purposes. It
1065 has the cost of more pagetable lookup overhead, and also
1066 consumes more pagetable space per process.
1068 config ARCH_PHYS_ADDR_T_64BIT
1069 def_bool X86_64 || X86_PAE
1071 config DIRECT_GBPAGES
1072 bool "Enable 1GB pages for kernel pagetables" if EMBEDDED
1073 default y
1074 depends on X86_64
1075 ---help---
1076 Allow the kernel linear mapping to use 1GB pages on CPUs that
1077 support it. This can improve the kernel's performance a tiny bit by
1078 reducing TLB pressure. If in doubt, say "Y".
1080 # Common NUMA Features
1081 config NUMA
1082 bool "Numa Memory Allocation and Scheduler Support"
1083 depends on SMP
1084 depends on X86_64 || (X86_32 && HIGHMEM64G && (X86_NUMAQ || X86_BIGSMP || X86_SUMMIT && ACPI) && EXPERIMENTAL)
1085 default y if (X86_NUMAQ || X86_SUMMIT || X86_BIGSMP)
1086 ---help---
1087 Enable NUMA (Non Uniform Memory Access) support.
1089 The kernel will try to allocate memory used by a CPU on the
1090 local memory controller of the CPU and add some more
1091 NUMA awareness to the kernel.
1093 For 64-bit this is recommended if the system is Intel Core i7
1094 (or later), AMD Opteron, or EM64T NUMA.
1096 For 32-bit this is only needed on (rare) 32-bit-only platforms
1097 that support NUMA topologies, such as NUMAQ / Summit, or if you
1098 boot a 32-bit kernel on a 64-bit NUMA platform.
1100 Otherwise, you should say N.
1102 comment "NUMA (Summit) requires SMP, 64GB highmem support, ACPI"
1103 depends on X86_32 && X86_SUMMIT && (!HIGHMEM64G || !ACPI)
1105 config K8_NUMA
1106 def_bool y
1107 prompt "Old style AMD Opteron NUMA detection"
1108 depends on X86_64 && NUMA && PCI
1109 ---help---
1110 Enable K8 NUMA node topology detection. You should say Y here if
1111 you have a multi processor AMD K8 system. This uses an old
1112 method to read the NUMA configuration directly from the builtin
1113 Northbridge of Opteron. It is recommended to use X86_64_ACPI_NUMA
1114 instead, which also takes priority if both are compiled in.
1116 config X86_64_ACPI_NUMA
1117 def_bool y
1118 prompt "ACPI NUMA detection"
1119 depends on X86_64 && NUMA && ACPI && PCI
1120 select ACPI_NUMA
1121 ---help---
1122 Enable ACPI SRAT based node topology detection.
1124 # Some NUMA nodes have memory ranges that span
1125 # other nodes. Even though a pfn is valid and
1126 # between a node's start and end pfns, it may not
1127 # reside on that node. See memmap_init_zone()
1128 # for details.
1129 config NODES_SPAN_OTHER_NODES
1130 def_bool y
1131 depends on X86_64_ACPI_NUMA
1133 config NUMA_EMU
1134 bool "NUMA emulation"
1135 depends on X86_64 && NUMA
1136 ---help---
1137 Enable NUMA emulation. A flat machine will be split
1138 into virtual nodes when booted with "numa=fake=N", where N is the
1139 number of nodes. This is only useful for debugging.
1141 config NODES_SHIFT
1142 int "Maximum NUMA Nodes (as a power of 2)" if !MAXSMP
1143 range 1 9
1144 default "9" if MAXSMP
1145 default "6" if X86_64
1146 default "4" if X86_NUMAQ
1147 default "3"
1148 depends on NEED_MULTIPLE_NODES
1149 ---help---
1150 Specify the maximum number of NUMA Nodes available on the target
1151 system. Increases memory reserved to accommodate various tables.
1153 config HAVE_ARCH_BOOTMEM
1154 def_bool y
1155 depends on X86_32 && NUMA
1157 config ARCH_HAVE_MEMORY_PRESENT
1158 def_bool y
1159 depends on X86_32 && DISCONTIGMEM
1161 config NEED_NODE_MEMMAP_SIZE
1162 def_bool y
1163 depends on X86_32 && (DISCONTIGMEM || SPARSEMEM)
1165 config HAVE_ARCH_ALLOC_REMAP
1166 def_bool y
1167 depends on X86_32 && NUMA
1169 config ARCH_FLATMEM_ENABLE
1170 def_bool y
1171 depends on X86_32 && ARCH_SELECT_MEMORY_MODEL && !NUMA
1173 config ARCH_DISCONTIGMEM_ENABLE
1174 def_bool y
1175 depends on NUMA && X86_32
1177 config ARCH_DISCONTIGMEM_DEFAULT
1178 def_bool y
1179 depends on NUMA && X86_32
1181 config ARCH_SPARSEMEM_DEFAULT
1182 def_bool y
1183 depends on X86_64
1185 config ARCH_SPARSEMEM_ENABLE
1186 def_bool y
1187 depends on X86_64 || NUMA || (EXPERIMENTAL && X86_32) || X86_32_NON_STANDARD
1188 select SPARSEMEM_STATIC if X86_32
1189 select SPARSEMEM_VMEMMAP_ENABLE if X86_64
1191 config ARCH_SELECT_MEMORY_MODEL
1192 def_bool y
1193 depends on ARCH_SPARSEMEM_ENABLE
1195 config ARCH_MEMORY_PROBE
1196 def_bool X86_64
1197 depends on MEMORY_HOTPLUG
1199 source "mm/Kconfig"
1201 config HIGHPTE
1202 bool "Allocate 3rd-level pagetables from highmem"
1203 depends on X86_32 && (HIGHMEM4G || HIGHMEM64G)
1204 ---help---
1205 The VM uses one page table entry for each page of physical memory.
1206 For systems with a lot of RAM, this can be wasteful of precious
1207 low memory. Setting this option will put user-space page table
1208 entries in high memory.
1210 config X86_CHECK_BIOS_CORRUPTION
1211 bool "Check for low memory corruption"
1212 ---help---
1213 Periodically check for memory corruption in low memory, which
1214 is suspected to be caused by BIOS. Even when enabled in the
1215 configuration, it is disabled at runtime. Enable it by
1216 setting "memory_corruption_check=1" on the kernel command
1217 line. By default it scans the low 64k of memory every 60
1218 seconds; see the memory_corruption_check_size and
1219 memory_corruption_check_period parameters in
1220 Documentation/kernel-parameters.txt to adjust this.
1222 When enabled with the default parameters, this option has
1223 almost no overhead, as it reserves a relatively small amount
1224 of memory and scans it infrequently. It both detects corruption
1225 and prevents it from affecting the running system.
1227 It is, however, intended as a diagnostic tool; if repeatable
1228 BIOS-originated corruption always affects the same memory,
1229 you can use memmap= to prevent the kernel from using that
1230 memory.
1232 config X86_BOOTPARAM_MEMORY_CORRUPTION_CHECK
1233 bool "Set the default setting of memory_corruption_check"
1234 depends on X86_CHECK_BIOS_CORRUPTION
1235 default y
1236 ---help---
1237 Set whether the default state of memory_corruption_check is
1238 on or off.
1240 config X86_RESERVE_LOW_64K
1241 bool "Reserve low 64K of RAM on AMI/Phoenix BIOSen"
1242 default y
1243 ---help---
1244 Reserve the first 64K of physical RAM on BIOSes that are known
1245 to potentially corrupt that memory range. A numbers of BIOSes are
1246 known to utilize this area during suspend/resume, so it must not
1247 be used by the kernel.
1249 Set this to N if you are absolutely sure that you trust the BIOS
1250 to get all its memory reservations and usages right.
1252 If you have doubts about the BIOS (e.g. suspend/resume does not
1253 work or there's kernel crashes after certain hardware hotplug
1254 events) and it's not AMI or Phoenix, then you might want to enable
1255 X86_CHECK_BIOS_CORRUPTION=y to allow the kernel to check typical
1256 corruption patterns.
1258 Say Y if unsure.
1260 config MATH_EMULATION
1261 bool
1262 prompt "Math emulation" if X86_32
1263 ---help---
1264 Linux can emulate a math coprocessor (used for floating point
1265 operations) if you don't have one. 486DX and Pentium processors have
1266 a math coprocessor built in, 486SX and 386 do not, unless you added
1267 a 487DX or 387, respectively. (The messages during boot time can
1268 give you some hints here ["man dmesg"].) Everyone needs either a
1269 coprocessor or this emulation.
1271 If you don't have a math coprocessor, you need to say Y here; if you
1272 say Y here even though you have a coprocessor, the coprocessor will
1273 be used nevertheless. (This behavior can be changed with the kernel
1274 command line option "no387", which comes handy if your coprocessor
1275 is broken. Try "man bootparam" or see the documentation of your boot
1276 loader (lilo or loadlin) about how to pass options to the kernel at
1277 boot time.) This means that it is a good idea to say Y here if you
1278 intend to use this kernel on different machines.
1280 More information about the internals of the Linux math coprocessor
1281 emulation can be found in <file:arch/x86/math-emu/README>.
1283 If you are not sure, say Y; apart from resulting in a 66 KB bigger
1284 kernel, it won't hurt.
1286 config MTRR
1287 bool "MTRR (Memory Type Range Register) support"
1288 ---help---
1289 On Intel P6 family processors (Pentium Pro, Pentium II and later)
1290 the Memory Type Range Registers (MTRRs) may be used to control
1291 processor access to memory ranges. This is most useful if you have
1292 a video (VGA) card on a PCI or AGP bus. Enabling write-combining
1293 allows bus write transfers to be combined into a larger transfer
1294 before bursting over the PCI/AGP bus. This can increase performance
1295 of image write operations 2.5 times or more. Saying Y here creates a
1296 /proc/mtrr file which may be used to manipulate your processor's
1297 MTRRs. Typically the X server should use this.
1299 This code has a reasonably generic interface so that similar
1300 control registers on other processors can be easily supported
1301 as well:
1303 The Cyrix 6x86, 6x86MX and M II processors have Address Range
1304 Registers (ARRs) which provide a similar functionality to MTRRs. For
1305 these, the ARRs are used to emulate the MTRRs.
1306 The AMD K6-2 (stepping 8 and above) and K6-3 processors have two
1307 MTRRs. The Centaur C6 (WinChip) has 8 MCRs, allowing
1308 write-combining. All of these processors are supported by this code
1309 and it makes sense to say Y here if you have one of them.
1311 Saying Y here also fixes a problem with buggy SMP BIOSes which only
1312 set the MTRRs for the boot CPU and not for the secondary CPUs. This
1313 can lead to all sorts of problems, so it's good to say Y here.
1315 You can safely say Y even if your machine doesn't have MTRRs, you'll
1316 just add about 9 KB to your kernel.
1318 See <file:Documentation/x86/mtrr.txt> for more information.
1320 config MTRR_SANITIZER
1321 def_bool y
1322 prompt "MTRR cleanup support"
1323 depends on MTRR
1324 ---help---
1325 Convert MTRR layout from continuous to discrete, so X drivers can
1326 add writeback entries.
1328 Can be disabled with disable_mtrr_cleanup on the kernel command line.
1329 The largest mtrr entry size for a continuous block can be set with
1330 mtrr_chunk_size.
1332 If unsure, say Y.
1334 config MTRR_SANITIZER_ENABLE_DEFAULT
1335 int "MTRR cleanup enable value (0-1)"
1336 range 0 1
1337 default "0"
1338 depends on MTRR_SANITIZER
1339 ---help---
1340 Enable mtrr cleanup default value
1342 config MTRR_SANITIZER_SPARE_REG_NR_DEFAULT
1343 int "MTRR cleanup spare reg num (0-7)"
1344 range 0 7
1345 default "1"
1346 depends on MTRR_SANITIZER
1347 ---help---
1348 mtrr cleanup spare entries default, it can be changed via
1349 mtrr_spare_reg_nr=N on the kernel command line.
1351 config X86_PAT
1352 bool
1353 prompt "x86 PAT support"
1354 depends on MTRR
1355 ---help---
1356 Use PAT attributes to setup page level cache control.
1358 PATs are the modern equivalents of MTRRs and are much more
1359 flexible than MTRRs.
1361 Say N here if you see bootup problems (boot crash, boot hang,
1362 spontaneous reboots) or a non-working video driver.
1364 If unsure, say Y.
1366 config EFI
1367 bool "EFI runtime service support"
1368 depends on ACPI
1369 ---help---
1370 This enables the kernel to use EFI runtime services that are
1371 available (such as the EFI variable services).
1373 This option is only useful on systems that have EFI firmware.
1374 In addition, you should use the latest ELILO loader available
1375 at <http://elilo.sourceforge.net> in order to take advantage
1376 of EFI runtime services. However, even with this option, the
1377 resultant kernel should continue to boot on existing non-EFI
1378 platforms.
1380 config SECCOMP
1381 def_bool y
1382 prompt "Enable seccomp to safely compute untrusted bytecode"
1383 ---help---
1384 This kernel feature is useful for number crunching applications
1385 that may need to compute untrusted bytecode during their
1386 execution. By using pipes or other transports made available to
1387 the process as file descriptors supporting the read/write
1388 syscalls, it's possible to isolate those applications in
1389 their own address space using seccomp. Once seccomp is
1390 enabled via prctl(PR_SET_SECCOMP), it cannot be disabled
1391 and the task is only allowed to execute a few safe syscalls
1392 defined by each seccomp mode.
1394 If unsure, say Y. Only embedded should say N here.
1396 config CC_STACKPROTECTOR_ALL
1397 bool
1399 config CC_STACKPROTECTOR
1400 bool "Enable -fstack-protector buffer overflow detection (EXPERIMENTAL)"
1401 select CC_STACKPROTECTOR_ALL
1402 ---help---
1403 This option turns on the -fstack-protector GCC feature. This
1404 feature puts, at the beginning of functions, a canary value on
1405 the stack just before the return address, and validates
1406 the value just before actually returning. Stack based buffer
1407 overflows (that need to overwrite this return address) now also
1408 overwrite the canary, which gets detected and the attack is then
1409 neutralized via a kernel panic.
1411 This feature requires gcc version 4.2 or above, or a distribution
1412 gcc with the feature backported. Older versions are automatically
1413 detected and for those versions, this configuration option is
1414 ignored. (and a warning is printed during bootup)
1416 source kernel/Kconfig.hz
1418 config KEXEC
1419 bool "kexec system call"
1420 ---help---
1421 kexec is a system call that implements the ability to shutdown your
1422 current kernel, and to start another kernel. It is like a reboot
1423 but it is independent of the system firmware. And like a reboot
1424 you can start any kernel with it, not just Linux.
1426 The name comes from the similarity to the exec system call.
1428 It is an ongoing process to be certain the hardware in a machine
1429 is properly shutdown, so do not be surprised if this code does not
1430 initially work for you. It may help to enable device hotplugging
1431 support. As of this writing the exact hardware interface is
1432 strongly in flux, so no good recommendation can be made.
1434 config CRASH_DUMP
1435 bool "kernel crash dumps"
1436 depends on X86_64 || (X86_32 && HIGHMEM)
1437 ---help---
1438 Generate crash dump after being started by kexec.
1439 This should be normally only set in special crash dump kernels
1440 which are loaded in the main kernel with kexec-tools into
1441 a specially reserved region and then later executed after
1442 a crash by kdump/kexec. The crash dump kernel must be compiled
1443 to a memory address not used by the main kernel or BIOS using
1444 PHYSICAL_START, or it must be built as a relocatable image
1445 (CONFIG_RELOCATABLE=y).
1446 For more details see Documentation/kdump/kdump.txt
1448 config KEXEC_JUMP
1449 bool "kexec jump (EXPERIMENTAL)"
1450 depends on EXPERIMENTAL
1451 depends on KEXEC && HIBERNATION
1452 ---help---
1453 Jump between original kernel and kexeced kernel and invoke
1454 code in physical address mode via KEXEC
1456 config PHYSICAL_START
1457 hex "Physical address where the kernel is loaded" if (EMBEDDED || CRASH_DUMP)
1458 default "0x1000000"
1459 ---help---
1460 This gives the physical address where the kernel is loaded.
1462 If kernel is a not relocatable (CONFIG_RELOCATABLE=n) then
1463 bzImage will decompress itself to above physical address and
1464 run from there. Otherwise, bzImage will run from the address where
1465 it has been loaded by the boot loader and will ignore above physical
1466 address.
1468 In normal kdump cases one does not have to set/change this option
1469 as now bzImage can be compiled as a completely relocatable image
1470 (CONFIG_RELOCATABLE=y) and be used to load and run from a different
1471 address. This option is mainly useful for the folks who don't want
1472 to use a bzImage for capturing the crash dump and want to use a
1473 vmlinux instead. vmlinux is not relocatable hence a kernel needs
1474 to be specifically compiled to run from a specific memory area
1475 (normally a reserved region) and this option comes handy.
1477 So if you are using bzImage for capturing the crash dump,
1478 leave the value here unchanged to 0x1000000 and set
1479 CONFIG_RELOCATABLE=y. Otherwise if you plan to use vmlinux
1480 for capturing the crash dump change this value to start of
1481 the reserved region. In other words, it can be set based on
1482 the "X" value as specified in the "crashkernel=YM@XM"
1483 command line boot parameter passed to the panic-ed
1484 kernel. Please take a look at Documentation/kdump/kdump.txt
1485 for more details about crash dumps.
1487 Usage of bzImage for capturing the crash dump is recommended as
1488 one does not have to build two kernels. Same kernel can be used
1489 as production kernel and capture kernel. Above option should have
1490 gone away after relocatable bzImage support is introduced. But it
1491 is present because there are users out there who continue to use
1492 vmlinux for dump capture. This option should go away down the
1493 line.
1495 Don't change this unless you know what you are doing.
1497 config RELOCATABLE
1498 bool "Build a relocatable kernel"
1499 default y
1500 ---help---
1501 This builds a kernel image that retains relocation information
1502 so it can be loaded someplace besides the default 1MB.
1503 The relocations tend to make the kernel binary about 10% larger,
1504 but are discarded at runtime.
1506 One use is for the kexec on panic case where the recovery kernel
1507 must live at a different physical address than the primary
1508 kernel.
1510 Note: If CONFIG_RELOCATABLE=y, then the kernel runs from the address
1511 it has been loaded at and the compile time physical address
1512 (CONFIG_PHYSICAL_START) is ignored.
1514 # Relocation on x86-32 needs some additional build support
1515 config X86_NEED_RELOCS
1516 def_bool y
1517 depends on X86_32 && RELOCATABLE
1519 config PHYSICAL_ALIGN
1520 hex
1521 prompt "Alignment value to which kernel should be aligned" if X86_32
1522 default "0x1000000"
1523 range 0x2000 0x1000000
1524 ---help---
1525 This value puts the alignment restrictions on physical address
1526 where kernel is loaded and run from. Kernel is compiled for an
1527 address which meets above alignment restriction.
1529 If bootloader loads the kernel at a non-aligned address and
1530 CONFIG_RELOCATABLE is set, kernel will move itself to nearest
1531 address aligned to above value and run from there.
1533 If bootloader loads the kernel at a non-aligned address and
1534 CONFIG_RELOCATABLE is not set, kernel will ignore the run time
1535 load address and decompress itself to the address it has been
1536 compiled for and run from there. The address for which kernel is
1537 compiled already meets above alignment restrictions. Hence the
1538 end result is that kernel runs from a physical address meeting
1539 above alignment restrictions.
1541 Don't change this unless you know what you are doing.
1543 config HOTPLUG_CPU
1544 bool "Support for hot-pluggable CPUs"
1545 depends on SMP && HOTPLUG
1546 ---help---
1547 Say Y here to allow turning CPUs off and on. CPUs can be
1548 controlled through /sys/devices/system/cpu.
1549 ( Note: power management support will enable this option
1550 automatically on SMP systems. )
1551 Say N if you want to disable CPU hotplug.
1553 config COMPAT_VDSO
1554 def_bool y
1555 prompt "Compat VDSO support"
1556 depends on X86_32 || IA32_EMULATION
1557 ---help---
1558 Map the 32-bit VDSO to the predictable old-style address too.
1559 ---help---
1560 Say N here if you are running a sufficiently recent glibc
1561 version (2.3.3 or later), to remove the high-mapped
1562 VDSO mapping and to exclusively use the randomized VDSO.
1564 If unsure, say Y.
1566 config CMDLINE_BOOL
1567 bool "Built-in kernel command line"
1568 default n
1569 ---help---
1570 Allow for specifying boot arguments to the kernel at
1571 build time. On some systems (e.g. embedded ones), it is
1572 necessary or convenient to provide some or all of the
1573 kernel boot arguments with the kernel itself (that is,
1574 to not rely on the boot loader to provide them.)
1576 To compile command line arguments into the kernel,
1577 set this option to 'Y', then fill in the
1578 the boot arguments in CONFIG_CMDLINE.
1580 Systems with fully functional boot loaders (i.e. non-embedded)
1581 should leave this option set to 'N'.
1583 config CMDLINE
1584 string "Built-in kernel command string"
1585 depends on CMDLINE_BOOL
1586 default ""
1587 ---help---
1588 Enter arguments here that should be compiled into the kernel
1589 image and used at boot time. If the boot loader provides a
1590 command line at boot time, it is appended to this string to
1591 form the full kernel command line, when the system boots.
1593 However, you can use the CONFIG_CMDLINE_OVERRIDE option to
1594 change this behavior.
1596 In most cases, the command line (whether built-in or provided
1597 by the boot loader) should specify the device for the root
1598 file system.
1600 config CMDLINE_OVERRIDE
1601 bool "Built-in command line overrides boot loader arguments"
1602 default n
1603 depends on CMDLINE_BOOL
1604 ---help---
1605 Set this option to 'Y' to have the kernel ignore the boot loader
1606 command line, and use ONLY the built-in command line.
1608 This is used to work around broken boot loaders. This should
1609 be set to 'N' under normal conditions.
1611 endmenu
1613 config ARCH_ENABLE_MEMORY_HOTPLUG
1614 def_bool y
1615 depends on X86_64 || (X86_32 && HIGHMEM)
1617 config ARCH_ENABLE_MEMORY_HOTREMOVE
1618 def_bool y
1619 depends on MEMORY_HOTPLUG
1621 config HAVE_ARCH_EARLY_PFN_TO_NID
1622 def_bool X86_64
1623 depends on NUMA
1625 menu "Power management and ACPI options"
1627 config ARCH_HIBERNATION_HEADER
1628 def_bool y
1629 depends on X86_64 && HIBERNATION
1631 source "kernel/power/Kconfig"
1633 source "drivers/acpi/Kconfig"
1635 config X86_APM_BOOT
1636 bool
1637 default y
1638 depends on APM || APM_MODULE
1640 menuconfig APM
1641 tristate "APM (Advanced Power Management) BIOS support"
1642 depends on X86_32 && PM_SLEEP
1643 ---help---
1644 APM is a BIOS specification for saving power using several different
1645 techniques. This is mostly useful for battery powered laptops with
1646 APM compliant BIOSes. If you say Y here, the system time will be
1647 reset after a RESUME operation, the /proc/apm device will provide
1648 battery status information, and user-space programs will receive
1649 notification of APM "events" (e.g. battery status change).
1651 If you select "Y" here, you can disable actual use of the APM
1652 BIOS by passing the "apm=off" option to the kernel at boot time.
1654 Note that the APM support is almost completely disabled for
1655 machines with more than one CPU.
1657 In order to use APM, you will need supporting software. For location
1658 and more information, read <file:Documentation/power/pm.txt> and the
1659 Battery Powered Linux mini-HOWTO, available from
1660 <http://www.tldp.org/docs.html#howto>.
1662 This driver does not spin down disk drives (see the hdparm(8)
1663 manpage ("man 8 hdparm") for that), and it doesn't turn off
1664 VESA-compliant "green" monitors.
1666 This driver does not support the TI 4000M TravelMate and the ACER
1667 486/DX4/75 because they don't have compliant BIOSes. Many "green"
1668 desktop machines also don't have compliant BIOSes, and this driver
1669 may cause those machines to panic during the boot phase.
1671 Generally, if you don't have a battery in your machine, there isn't
1672 much point in using this driver and you should say N. If you get
1673 random kernel OOPSes or reboots that don't seem to be related to
1674 anything, try disabling/enabling this option (or disabling/enabling
1675 APM in your BIOS).
1677 Some other things you should try when experiencing seemingly random,
1678 "weird" problems:
1680 1) make sure that you have enough swap space and that it is
1681 enabled.
1682 2) pass the "no-hlt" option to the kernel
1683 3) switch on floating point emulation in the kernel and pass
1684 the "no387" option to the kernel
1685 4) pass the "floppy=nodma" option to the kernel
1686 5) pass the "mem=4M" option to the kernel (thereby disabling
1687 all but the first 4 MB of RAM)
1688 6) make sure that the CPU is not over clocked.
1689 7) read the sig11 FAQ at <http://www.bitwizard.nl/sig11/>
1690 8) disable the cache from your BIOS settings
1691 9) install a fan for the video card or exchange video RAM
1692 10) install a better fan for the CPU
1693 11) exchange RAM chips
1694 12) exchange the motherboard.
1696 To compile this driver as a module, choose M here: the
1697 module will be called apm.
1699 if APM
1701 config APM_IGNORE_USER_SUSPEND
1702 bool "Ignore USER SUSPEND"
1703 ---help---
1704 This option will ignore USER SUSPEND requests. On machines with a
1705 compliant APM BIOS, you want to say N. However, on the NEC Versa M
1706 series notebooks, it is necessary to say Y because of a BIOS bug.
1708 config APM_DO_ENABLE
1709 bool "Enable PM at boot time"
1710 ---help---
1711 Enable APM features at boot time. From page 36 of the APM BIOS
1712 specification: "When disabled, the APM BIOS does not automatically
1713 power manage devices, enter the Standby State, enter the Suspend
1714 State, or take power saving steps in response to CPU Idle calls."
1715 This driver will make CPU Idle calls when Linux is idle (unless this
1716 feature is turned off -- see "Do CPU IDLE calls", below). This
1717 should always save battery power, but more complicated APM features
1718 will be dependent on your BIOS implementation. You may need to turn
1719 this option off if your computer hangs at boot time when using APM
1720 support, or if it beeps continuously instead of suspending. Turn
1721 this off if you have a NEC UltraLite Versa 33/C or a Toshiba
1722 T400CDT. This is off by default since most machines do fine without
1723 this feature.
1725 config APM_CPU_IDLE
1726 bool "Make CPU Idle calls when idle"
1727 ---help---
1728 Enable calls to APM CPU Idle/CPU Busy inside the kernel's idle loop.
1729 On some machines, this can activate improved power savings, such as
1730 a slowed CPU clock rate, when the machine is idle. These idle calls
1731 are made after the idle loop has run for some length of time (e.g.,
1732 333 mS). On some machines, this will cause a hang at boot time or
1733 whenever the CPU becomes idle. (On machines with more than one CPU,
1734 this option does nothing.)
1736 config APM_DISPLAY_BLANK
1737 bool "Enable console blanking using APM"
1738 ---help---
1739 Enable console blanking using the APM. Some laptops can use this to
1740 turn off the LCD backlight when the screen blanker of the Linux
1741 virtual console blanks the screen. Note that this is only used by
1742 the virtual console screen blanker, and won't turn off the backlight
1743 when using the X Window system. This also doesn't have anything to
1744 do with your VESA-compliant power-saving monitor. Further, this
1745 option doesn't work for all laptops -- it might not turn off your
1746 backlight at all, or it might print a lot of errors to the console,
1747 especially if you are using gpm.
1749 config APM_ALLOW_INTS
1750 bool "Allow interrupts during APM BIOS calls"
1751 ---help---
1752 Normally we disable external interrupts while we are making calls to
1753 the APM BIOS as a measure to lessen the effects of a badly behaving
1754 BIOS implementation. The BIOS should reenable interrupts if it
1755 needs to. Unfortunately, some BIOSes do not -- especially those in
1756 many of the newer IBM Thinkpads. If you experience hangs when you
1757 suspend, try setting this to Y. Otherwise, say N.
1759 endif # APM
1761 source "arch/x86/kernel/cpu/cpufreq/Kconfig"
1763 source "drivers/cpuidle/Kconfig"
1765 source "drivers/idle/Kconfig"
1767 endmenu
1770 menu "Bus options (PCI etc.)"
1772 config PCI
1773 bool "PCI support"
1774 default y
1775 select ARCH_SUPPORTS_MSI if (X86_LOCAL_APIC && X86_IO_APIC)
1776 ---help---
1777 Find out whether you have a PCI motherboard. PCI is the name of a
1778 bus system, i.e. the way the CPU talks to the other stuff inside
1779 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
1780 VESA. If you have PCI, say Y, otherwise N.
1782 choice
1783 prompt "PCI access mode"
1784 depends on X86_32 && PCI
1785 default PCI_GOANY
1786 ---help---
1787 On PCI systems, the BIOS can be used to detect the PCI devices and
1788 determine their configuration. However, some old PCI motherboards
1789 have BIOS bugs and may crash if this is done. Also, some embedded
1790 PCI-based systems don't have any BIOS at all. Linux can also try to
1791 detect the PCI hardware directly without using the BIOS.
1793 With this option, you can specify how Linux should detect the
1794 PCI devices. If you choose "BIOS", the BIOS will be used,
1795 if you choose "Direct", the BIOS won't be used, and if you
1796 choose "MMConfig", then PCI Express MMCONFIG will be used.
1797 If you choose "Any", the kernel will try MMCONFIG, then the
1798 direct access method and falls back to the BIOS if that doesn't
1799 work. If unsure, go with the default, which is "Any".
1801 config PCI_GOBIOS
1802 bool "BIOS"
1804 config PCI_GOMMCONFIG
1805 bool "MMConfig"
1807 config PCI_GODIRECT
1808 bool "Direct"
1810 config PCI_GOOLPC
1811 bool "OLPC"
1812 depends on OLPC
1814 config PCI_GOANY
1815 bool "Any"
1817 endchoice
1819 config PCI_BIOS
1820 def_bool y
1821 depends on X86_32 && PCI && (PCI_GOBIOS || PCI_GOANY)
1823 # x86-64 doesn't support PCI BIOS access from long mode so always go direct.
1824 config PCI_DIRECT
1825 def_bool y
1826 depends on PCI && (X86_64 || (PCI_GODIRECT || PCI_GOANY || PCI_GOOLPC))
1828 config PCI_MMCONFIG
1829 def_bool y
1830 depends on X86_32 && PCI && ACPI && (PCI_GOMMCONFIG || PCI_GOANY)
1832 config PCI_OLPC
1833 def_bool y
1834 depends on PCI && OLPC && (PCI_GOOLPC || PCI_GOANY)
1836 config PCI_DOMAINS
1837 def_bool y
1838 depends on PCI
1840 config PCI_MMCONFIG
1841 bool "Support mmconfig PCI config space access"
1842 depends on X86_64 && PCI && ACPI
1844 config DMAR
1845 bool "Support for DMA Remapping Devices (EXPERIMENTAL)"
1846 depends on PCI_MSI && ACPI && EXPERIMENTAL
1847 help
1848 DMA remapping (DMAR) devices support enables independent address
1849 translations for Direct Memory Access (DMA) from devices.
1850 These DMA remapping devices are reported via ACPI tables
1851 and include PCI device scope covered by these DMA
1852 remapping devices.
1854 config DMAR_DEFAULT_ON
1855 def_bool y
1856 prompt "Enable DMA Remapping Devices by default"
1857 depends on DMAR
1858 help
1859 Selecting this option will enable a DMAR device at boot time if
1860 one is found. If this option is not selected, DMAR support can
1861 be enabled by passing intel_iommu=on to the kernel. It is
1862 recommended you say N here while the DMAR code remains
1863 experimental.
1865 config DMAR_GFX_WA
1866 def_bool y
1867 prompt "Support for Graphics workaround"
1868 depends on DMAR
1869 ---help---
1870 Current Graphics drivers tend to use physical address
1871 for DMA and avoid using DMA APIs. Setting this config
1872 option permits the IOMMU driver to set a unity map for
1873 all the OS-visible memory. Hence the driver can continue
1874 to use physical addresses for DMA.
1876 config DMAR_FLOPPY_WA
1877 def_bool y
1878 depends on DMAR
1879 ---help---
1880 Floppy disk drivers are know to bypass DMA API calls
1881 thereby failing to work when IOMMU is enabled. This
1882 workaround will setup a 1:1 mapping for the first
1883 16M to make floppy (an ISA device) work.
1885 config INTR_REMAP
1886 bool "Support for Interrupt Remapping (EXPERIMENTAL)"
1887 depends on X86_64 && X86_IO_APIC && PCI_MSI && ACPI && EXPERIMENTAL
1888 ---help---
1889 Supports Interrupt remapping for IO-APIC and MSI devices.
1890 To use x2apic mode in the CPU's which support x2APIC enhancements or
1891 to support platforms with CPU's having > 8 bit APIC ID, say Y.
1893 source "drivers/pci/pcie/Kconfig"
1895 source "drivers/pci/Kconfig"
1897 # x86_64 have no ISA slots, but do have ISA-style DMA.
1898 config ISA_DMA_API
1899 def_bool y
1901 if X86_32
1903 config ISA
1904 bool "ISA support"
1905 ---help---
1906 Find out whether you have ISA slots on your motherboard. ISA is the
1907 name of a bus system, i.e. the way the CPU talks to the other stuff
1908 inside your box. Other bus systems are PCI, EISA, MicroChannel
1909 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
1910 newer boards don't support it. If you have ISA, say Y, otherwise N.
1912 config EISA
1913 bool "EISA support"
1914 depends on ISA
1915 ---help---
1916 The Extended Industry Standard Architecture (EISA) bus was
1917 developed as an open alternative to the IBM MicroChannel bus.
1919 The EISA bus provided some of the features of the IBM MicroChannel
1920 bus while maintaining backward compatibility with cards made for
1921 the older ISA bus. The EISA bus saw limited use between 1988 and
1922 1995 when it was made obsolete by the PCI bus.
1924 Say Y here if you are building a kernel for an EISA-based machine.
1926 Otherwise, say N.
1928 source "drivers/eisa/Kconfig"
1930 config MCA
1931 bool "MCA support"
1932 ---help---
1933 MicroChannel Architecture is found in some IBM PS/2 machines and
1934 laptops. It is a bus system similar to PCI or ISA. See
1935 <file:Documentation/mca.txt> (and especially the web page given
1936 there) before attempting to build an MCA bus kernel.
1938 source "drivers/mca/Kconfig"
1940 config SCx200
1941 tristate "NatSemi SCx200 support"
1942 ---help---
1943 This provides basic support for National Semiconductor's
1944 (now AMD's) Geode processors. The driver probes for the
1945 PCI-IDs of several on-chip devices, so its a good dependency
1946 for other scx200_* drivers.
1948 If compiled as a module, the driver is named scx200.
1950 config SCx200HR_TIMER
1951 tristate "NatSemi SCx200 27MHz High-Resolution Timer Support"
1952 depends on SCx200 && GENERIC_TIME
1953 default y
1954 ---help---
1955 This driver provides a clocksource built upon the on-chip
1956 27MHz high-resolution timer. Its also a workaround for
1957 NSC Geode SC-1100's buggy TSC, which loses time when the
1958 processor goes idle (as is done by the scheduler). The
1959 other workaround is idle=poll boot option.
1961 config GEODE_MFGPT_TIMER
1962 def_bool y
1963 prompt "Geode Multi-Function General Purpose Timer (MFGPT) events"
1964 depends on MGEODE_LX && GENERIC_TIME && GENERIC_CLOCKEVENTS
1965 ---help---
1966 This driver provides a clock event source based on the MFGPT
1967 timer(s) in the CS5535 and CS5536 companion chip for the geode.
1968 MFGPTs have a better resolution and max interval than the
1969 generic PIT, and are suitable for use as high-res timers.
1971 config OLPC
1972 bool "One Laptop Per Child support"
1973 default n
1974 ---help---
1975 Add support for detecting the unique features of the OLPC
1976 XO hardware.
1978 endif # X86_32
1980 config K8_NB
1981 def_bool y
1982 depends on AGP_AMD64 || (X86_64 && (GART_IOMMU || (PCI && NUMA)))
1984 source "drivers/pcmcia/Kconfig"
1986 source "drivers/pci/hotplug/Kconfig"
1988 endmenu
1991 menu "Executable file formats / Emulations"
1993 source "fs/Kconfig.binfmt"
1995 config IA32_EMULATION
1996 bool "IA32 Emulation"
1997 depends on X86_64
1998 select COMPAT_BINFMT_ELF
1999 ---help---
2000 Include code to run 32-bit programs under a 64-bit kernel. You should
2001 likely turn this on, unless you're 100% sure that you don't have any
2002 32-bit programs left.
2004 config IA32_AOUT
2005 tristate "IA32 a.out support"
2006 depends on IA32_EMULATION
2007 ---help---
2008 Support old a.out binaries in the 32bit emulation.
2010 config COMPAT
2011 def_bool y
2012 depends on IA32_EMULATION
2014 config COMPAT_FOR_U64_ALIGNMENT
2015 def_bool COMPAT
2016 depends on X86_64
2018 config SYSVIPC_COMPAT
2019 def_bool y
2020 depends on COMPAT && SYSVIPC
2022 endmenu
2025 config HAVE_ATOMIC_IOMAP
2026 def_bool y
2027 depends on X86_32
2029 source "net/Kconfig"
2031 source "drivers/Kconfig"
2033 source "drivers/firmware/Kconfig"
2035 source "fs/Kconfig"
2037 source "arch/x86/Kconfig.debug"
2039 source "security/Kconfig"
2041 source "crypto/Kconfig"
2043 source "arch/x86/kvm/Kconfig"
2045 source "lib/Kconfig"