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