| blob | d8ba42418d339092118e303e8ca742ef3273e194 |
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_PERF_COUNTERS if (!M386 && !M486)
28 select HAVE_IOREMAP_PROT
29 select HAVE_KPROBES
30 select ARCH_WANT_OPTIONAL_GPIOLIB
31 select ARCH_WANT_FRAME_POINTERS
32 select HAVE_DMA_ATTRS
33 select HAVE_KRETPROBES
34 select HAVE_FTRACE_MCOUNT_RECORD
35 select HAVE_DYNAMIC_FTRACE
36 select HAVE_FUNCTION_TRACER
37 select HAVE_FUNCTION_GRAPH_TRACER
38 select HAVE_FUNCTION_GRAPH_FP_TEST
39 select HAVE_FUNCTION_TRACE_MCOUNT_TEST
40 select HAVE_FTRACE_NMI_ENTER if DYNAMIC_FTRACE
41 select HAVE_FTRACE_SYSCALLS
42 select HAVE_KVM
43 select HAVE_ARCH_KGDB
44 select HAVE_ARCH_TRACEHOOK
45 select HAVE_GENERIC_DMA_COHERENT if X86_32
46 select HAVE_EFFICIENT_UNALIGNED_ACCESS
47 select USER_STACKTRACE_SUPPORT
48 select HAVE_DMA_API_DEBUG
49 select HAVE_KERNEL_GZIP
50 select HAVE_KERNEL_BZIP2
51 select HAVE_KERNEL_LZMA
52 select HAVE_ARCH_KMEMCHECK
54 config OUTPUT_FORMAT
55 string
56 default "elf32-i386" if X86_32
57 default "elf64-x86-64" if X86_64
59 config ARCH_DEFCONFIG
60 string
61 default "arch/x86/configs/i386_defconfig" if X86_32
62 default "arch/x86/configs/x86_64_defconfig" if X86_64
64 config GENERIC_TIME
65 def_bool y
67 config GENERIC_CMOS_UPDATE
68 def_bool y
70 config CLOCKSOURCE_WATCHDOG
71 def_bool y
73 config GENERIC_CLOCKEVENTS
74 def_bool y
76 config GENERIC_CLOCKEVENTS_BROADCAST
77 def_bool y
78 depends on X86_64 || (X86_32 && X86_LOCAL_APIC)
80 config LOCKDEP_SUPPORT
81 def_bool y
83 config STACKTRACE_SUPPORT
84 def_bool y
86 config HAVE_LATENCYTOP_SUPPORT
87 def_bool y
89 config FAST_CMPXCHG_LOCAL
90 bool
91 default y
93 config MMU
94 def_bool y
96 config ZONE_DMA
97 def_bool y
99 config SBUS
100 bool
102 config GENERIC_ISA_DMA
103 def_bool y
105 config GENERIC_IOMAP
106 def_bool y
108 config GENERIC_BUG
109 def_bool y
110 depends on BUG
111 select GENERIC_BUG_RELATIVE_POINTERS if X86_64
113 config GENERIC_BUG_RELATIVE_POINTERS
114 bool
116 config GENERIC_HWEIGHT
117 def_bool y
119 config GENERIC_GPIO
120 bool
122 config ARCH_MAY_HAVE_PC_FDC
123 def_bool y
125 config RWSEM_GENERIC_SPINLOCK
126 def_bool !X86_XADD
128 config RWSEM_XCHGADD_ALGORITHM
129 def_bool X86_XADD
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 config ARCH_SUPPORTS_DEBUG_PAGEALLOC
180 def_bool y
182 # Use the generic interrupt handling code in kernel/irq/:
183 config GENERIC_HARDIRQS
184 bool
185 default y
187 config GENERIC_HARDIRQS_NO__DO_IRQ
188 def_bool y
190 config GENERIC_IRQ_PROBE
191 bool
192 default y
194 config GENERIC_PENDING_IRQ
195 bool
196 depends on GENERIC_HARDIRQS && SMP
197 default y
199 config USE_GENERIC_SMP_HELPERS
200 def_bool y
201 depends on SMP
203 config X86_32_SMP
204 def_bool y
205 depends on X86_32 && SMP
207 config X86_64_SMP
208 def_bool y
209 depends on X86_64 && SMP
211 config X86_HT
212 bool
213 depends on SMP
214 default y
216 config X86_TRAMPOLINE
217 bool
218 depends on SMP || (64BIT && ACPI_SLEEP)
219 default y
221 config X86_32_LAZY_GS
222 def_bool y
223 depends on X86_32 && !CC_STACKPROTECTOR
225 config KTIME_SCALAR
226 def_bool X86_32
227 source "init/Kconfig"
228 source "kernel/Kconfig.freezer"
230 menu "Processor type and features"
232 source "kernel/time/Kconfig"
234 config SMP
235 bool "Symmetric multi-processing support"
236 ---help---
237 This enables support for systems with more than one CPU. If you have
238 a system with only one CPU, like most personal computers, say N. If
239 you have a system with more than one CPU, say Y.
241 If you say N here, the kernel will run on single and multiprocessor
242 machines, but will use only one CPU of a multiprocessor machine. If
243 you say Y here, the kernel will run on many, but not all,
244 singleprocessor machines. On a singleprocessor machine, the kernel
245 will run faster if you say N here.
247 Note that if you say Y here and choose architecture "586" or
248 "Pentium" under "Processor family", the kernel will not work on 486
249 architectures. Similarly, multiprocessor kernels for the "PPro"
250 architecture may not work on all Pentium based boards.
252 People using multiprocessor machines who say Y here should also say
253 Y to "Enhanced Real Time Clock Support", below. The "Advanced Power
254 Management" code will be disabled if you say Y here.
256 See also <file:Documentation/i386/IO-APIC.txt>,
257 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
258 <http://www.tldp.org/docs.html#howto>.
260 If you don't know what to do here, say N.
262 config X86_X2APIC
263 bool "Support x2apic"
264 depends on X86_LOCAL_APIC && X86_64 && INTR_REMAP
265 ---help---
266 This enables x2apic support on CPUs that have this feature.
268 This allows 32-bit apic IDs (so it can support very large systems),
269 and accesses the local apic via MSRs not via mmio.
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_IRQ_DESC
287 def_bool y
288 depends on SPARSE_IRQ && NUMA
290 config X86_MPPARSE
291 bool "Enable MPS table" if ACPI
292 default y
293 depends on X86_LOCAL_APIC
294 ---help---
295 For old smp systems that do not have proper acpi support. Newer systems
296 (esp with 64bit cpus) with acpi support, MADT and DSDT will override it
298 config X86_BIGSMP
299 bool "Support for big SMP systems with more than 8 CPUs"
300 depends on X86_32 && SMP
301 ---help---
302 This option is needed for the systems that have more than 8 CPUs
304 if X86_32
305 config X86_EXTENDED_PLATFORM
306 bool "Support for extended (non-PC) x86 platforms"
307 default y
308 ---help---
309 If you disable this option then the kernel will only support
310 standard PC platforms. (which covers the vast majority of
311 systems out there.)
313 If you enable this option then you'll be able to select support
314 for the following (non-PC) 32 bit x86 platforms:
315 AMD Elan
316 NUMAQ (IBM/Sequent)
317 RDC R-321x SoC
318 SGI 320/540 (Visual Workstation)
319 Summit/EXA (IBM x440)
320 Unisys ES7000 IA32 series
322 If you have one of these systems, or if you want to build a
323 generic distribution kernel, say Y here - otherwise say N.
324 endif
326 if X86_64
327 config X86_EXTENDED_PLATFORM
328 bool "Support for extended (non-PC) x86 platforms"
329 default y
330 ---help---
331 If you disable this option then the kernel will only support
332 standard PC platforms. (which covers the vast majority of
333 systems out there.)
335 If you enable this option then you'll be able to select support
336 for the following (non-PC) 64 bit x86 platforms:
337 ScaleMP vSMP
338 SGI Ultraviolet
340 If you have one of these systems, or if you want to build a
341 generic distribution kernel, say Y here - otherwise say N.
342 endif
343 # This is an alphabetically sorted list of 64 bit extended platforms
344 # Please maintain the alphabetic order if and when there are additions
346 config X86_VSMP
347 bool "ScaleMP vSMP"
348 select PARAVIRT
349 depends on X86_64 && PCI
350 depends on X86_EXTENDED_PLATFORM
351 ---help---
352 Support for ScaleMP vSMP systems. Say 'Y' here if this kernel is
353 supposed to run on these EM64T-based machines. Only choose this option
354 if you have one of these machines.
356 config X86_UV
357 bool "SGI Ultraviolet"
358 depends on X86_64
359 depends on X86_EXTENDED_PLATFORM
360 depends on NUMA
361 depends on 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_SPINLOCKS
505 bool "Paravirtualization layer for spinlocks"
506 depends on PARAVIRT && SMP && EXPERIMENTAL
507 ---help---
508 Paravirtualized spinlocks allow a pvops backend to replace the
509 spinlock implementation with something virtualization-friendly
510 (for example, block the virtual CPU rather than spinning).
512 Unfortunately the downside is an up to 5% performance hit on
513 native kernels, with various workloads.
515 If you are unsure how to answer this question, answer N.
517 config PARAVIRT_CLOCK
518 bool
519 default n
521 endif
523 config PARAVIRT_DEBUG
524 bool "paravirt-ops debugging"
525 depends on PARAVIRT && DEBUG_KERNEL
526 ---help---
527 Enable to debug paravirt_ops internals. Specifically, BUG if
528 a paravirt_op is missing when it is called.
530 config MEMTEST
531 bool "Memtest"
532 ---help---
533 This option adds a kernel parameter 'memtest', which allows memtest
534 to be set.
535 memtest=0, mean disabled; -- default
536 memtest=1, mean do 1 test pattern;
537 ...
538 memtest=4, mean do 4 test patterns.
539 If you are unsure how to answer this question, answer N.
541 config X86_SUMMIT_NUMA
542 def_bool y
543 depends on X86_32 && NUMA && X86_32_NON_STANDARD
545 config X86_CYCLONE_TIMER
546 def_bool y
547 depends on X86_32_NON_STANDARD
549 source "arch/x86/Kconfig.cpu"
551 config HPET_TIMER
552 def_bool X86_64
553 prompt "HPET Timer Support" if X86_32
554 ---help---
555 Use the IA-PC HPET (High Precision Event Timer) to manage
556 time in preference to the PIT and RTC, if a HPET is
557 present.
558 HPET is the next generation timer replacing legacy 8254s.
559 The HPET provides a stable time base on SMP
560 systems, unlike the TSC, but it is more expensive to access,
561 as it is off-chip. You can find the HPET spec at
562 <http://www.intel.com/hardwaredesign/hpetspec_1.pdf>.
564 You can safely choose Y here. However, HPET will only be
565 activated if the platform and the BIOS support this feature.
566 Otherwise the 8254 will be used for timing services.
568 Choose N to continue using the legacy 8254 timer.
570 config HPET_EMULATE_RTC
571 def_bool y
572 depends on HPET_TIMER && (RTC=y || RTC=m || RTC_DRV_CMOS=m || RTC_DRV_CMOS=y)
574 # Mark as embedded because too many people got it wrong.
575 # The code disables itself when not needed.
576 config DMI
577 default y
578 bool "Enable DMI scanning" if EMBEDDED
579 ---help---
580 Enabled scanning of DMI to identify machine quirks. Say Y
581 here unless you have verified that your setup is not
582 affected by entries in the DMI blacklist. Required by PNP
583 BIOS code.
585 config GART_IOMMU
586 bool "GART IOMMU support" if EMBEDDED
587 default y
588 select SWIOTLB
589 select AGP
590 depends on X86_64 && PCI
591 ---help---
592 Support for full DMA access of devices with 32bit memory access only
593 on systems with more than 3GB. This is usually needed for USB,
594 sound, many IDE/SATA chipsets and some other devices.
595 Provides a driver for the AMD Athlon64/Opteron/Turion/Sempron GART
596 based hardware IOMMU and a software bounce buffer based IOMMU used
597 on Intel systems and as fallback.
598 The code is only active when needed (enough memory and limited
599 device) unless CONFIG_IOMMU_DEBUG or iommu=force is specified
600 too.
602 config CALGARY_IOMMU
603 bool "IBM Calgary IOMMU support"
604 select SWIOTLB
605 depends on X86_64 && PCI && EXPERIMENTAL
606 ---help---
607 Support for hardware IOMMUs in IBM's xSeries x366 and x460
608 systems. Needed to run systems with more than 3GB of memory
609 properly with 32-bit PCI devices that do not support DAC
610 (Double Address Cycle). Calgary also supports bus level
611 isolation, where all DMAs pass through the IOMMU. This
612 prevents them from going anywhere except their intended
613 destination. This catches hard-to-find kernel bugs and
614 mis-behaving drivers and devices that do not use the DMA-API
615 properly to set up their DMA buffers. The IOMMU can be
616 turned off at boot time with the iommu=off parameter.
617 Normally the kernel will make the right choice by itself.
618 If unsure, say Y.
620 config CALGARY_IOMMU_ENABLED_BY_DEFAULT
621 def_bool y
622 prompt "Should Calgary be enabled by default?"
623 depends on CALGARY_IOMMU
624 ---help---
625 Should Calgary be enabled by default? if you choose 'y', Calgary
626 will be used (if it exists). If you choose 'n', Calgary will not be
627 used even if it exists. If you choose 'n' and would like to use
628 Calgary anyway, pass 'iommu=calgary' on the kernel command line.
629 If unsure, say Y.
631 config AMD_IOMMU
632 bool "AMD IOMMU support"
633 select SWIOTLB
634 select PCI_MSI
635 depends on X86_64 && PCI && ACPI
636 ---help---
637 With this option you can enable support for AMD IOMMU hardware in
638 your system. An IOMMU is a hardware component which provides
639 remapping of DMA memory accesses from devices. With an AMD IOMMU you
640 can isolate the the DMA memory of different devices and protect the
641 system from misbehaving device drivers or hardware.
643 You can find out if your system has an AMD IOMMU if you look into
644 your BIOS for an option to enable it or if you have an IVRS ACPI
645 table.
647 config AMD_IOMMU_STATS
648 bool "Export AMD IOMMU statistics to debugfs"
649 depends on AMD_IOMMU
650 select DEBUG_FS
651 ---help---
652 This option enables code in the AMD IOMMU driver to collect various
653 statistics about whats happening in the driver and exports that
654 information to userspace via debugfs.
655 If unsure, say N.
657 # need this always selected by IOMMU for the VIA workaround
658 config SWIOTLB
659 def_bool y if X86_64
660 ---help---
661 Support for software bounce buffers used on x86-64 systems
662 which don't have a hardware IOMMU (e.g. the current generation
663 of Intel's x86-64 CPUs). Using this PCI devices which can only
664 access 32-bits of memory can be used on systems with more than
665 3 GB of memory. If unsure, say Y.
667 config IOMMU_HELPER
668 def_bool (CALGARY_IOMMU || GART_IOMMU || SWIOTLB || AMD_IOMMU)
670 config IOMMU_API
671 def_bool (AMD_IOMMU || DMAR)
673 config MAXSMP
674 bool "Configure Maximum number of SMP Processors and NUMA Nodes"
675 depends on X86_64 && SMP && DEBUG_KERNEL && EXPERIMENTAL
676 select CPUMASK_OFFSTACK
677 default n
678 ---help---
679 Configure maximum number of CPUS and NUMA Nodes for this architecture.
680 If unsure, say N.
682 config NR_CPUS
683 int "Maximum number of CPUs" if SMP && !MAXSMP
684 range 2 8 if SMP && X86_32 && !X86_BIGSMP
685 range 2 512 if SMP && !MAXSMP
686 default "1" if !SMP
687 default "4096" if MAXSMP
688 default "32" if SMP && (X86_NUMAQ || X86_SUMMIT || X86_BIGSMP || X86_ES7000)
689 default "8" if SMP
690 ---help---
691 This allows you to specify the maximum number of CPUs which this
692 kernel will support. The maximum supported value is 512 and the
693 minimum value which makes sense is 2.
695 This is purely to save memory - each supported CPU adds
696 approximately eight kilobytes to the kernel image.
698 config SCHED_SMT
699 bool "SMT (Hyperthreading) scheduler support"
700 depends on X86_HT
701 ---help---
702 SMT scheduler support improves the CPU scheduler's decision making
703 when dealing with Intel Pentium 4 chips with HyperThreading at a
704 cost of slightly increased overhead in some places. If unsure say
705 N here.
707 config SCHED_MC
708 def_bool y
709 prompt "Multi-core scheduler support"
710 depends on X86_HT
711 ---help---
712 Multi-core scheduler support improves the CPU scheduler's decision
713 making when dealing with multi-core CPU chips at a cost of slightly
714 increased overhead in some places. If unsure say N here.
716 source "kernel/Kconfig.preempt"
718 config X86_UP_APIC
719 bool "Local APIC support on uniprocessors"
720 depends on X86_32 && !SMP && !X86_32_NON_STANDARD
721 ---help---
722 A local APIC (Advanced Programmable Interrupt Controller) is an
723 integrated interrupt controller in the CPU. If you have a single-CPU
724 system which has a processor with a local APIC, you can say Y here to
725 enable and use it. If you say Y here even though your machine doesn't
726 have a local APIC, then the kernel will still run with no slowdown at
727 all. The local APIC supports CPU-generated self-interrupts (timer,
728 performance counters), and the NMI watchdog which detects hard
729 lockups.
731 config X86_UP_IOAPIC
732 bool "IO-APIC support on uniprocessors"
733 depends on X86_UP_APIC
734 ---help---
735 An IO-APIC (I/O Advanced Programmable Interrupt Controller) is an
736 SMP-capable replacement for PC-style interrupt controllers. Most
737 SMP systems and many recent uniprocessor systems have one.
739 If you have a single-CPU system with an IO-APIC, you can say Y here
740 to use it. If you say Y here even though your machine doesn't have
741 an IO-APIC, then the kernel will still run with no slowdown at all.
743 config X86_LOCAL_APIC
744 def_bool y
745 depends on X86_64 || SMP || X86_32_NON_STANDARD || X86_UP_APIC
747 config X86_IO_APIC
748 def_bool y
749 depends on X86_64 || SMP || X86_32_NON_STANDARD || X86_UP_APIC
751 config X86_VISWS_APIC
752 def_bool y
753 depends on X86_32 && X86_VISWS
755 config X86_REROUTE_FOR_BROKEN_BOOT_IRQS
756 bool "Reroute for broken boot IRQs"
757 default n
758 depends on X86_IO_APIC
759 ---help---
760 This option enables a workaround that fixes a source of
761 spurious interrupts. This is recommended when threaded
762 interrupt handling is used on systems where the generation of
763 superfluous "boot interrupts" cannot be disabled.
765 Some chipsets generate a legacy INTx "boot IRQ" when the IRQ
766 entry in the chipset's IO-APIC is masked (as, e.g. the RT
767 kernel does during interrupt handling). On chipsets where this
768 boot IRQ generation cannot be disabled, this workaround keeps
769 the original IRQ line masked so that only the equivalent "boot
770 IRQ" is delivered to the CPUs. The workaround also tells the
771 kernel to set up the IRQ handler on the boot IRQ line. In this
772 way only one interrupt is delivered to the kernel. Otherwise
773 the spurious second interrupt may cause the kernel to bring
774 down (vital) interrupt lines.
776 Only affects "broken" chipsets. Interrupt sharing may be
777 increased on these systems.
779 config X86_MCE
780 bool "Machine Check Exception"
781 ---help---
782 Machine Check Exception support allows the processor to notify the
783 kernel if it detects a problem (e.g. overheating, component failure).
784 The action the kernel takes depends on the severity of the problem,
785 ranging from a warning message on the console, to halting the machine.
786 Your processor must be a Pentium or newer to support this - check the
787 flags in /proc/cpuinfo for mce. Note that some older Pentium systems
788 have a design flaw which leads to false MCE events - hence MCE is
789 disabled on all P5 processors, unless explicitly enabled with "mce"
790 as a boot argument. Similarly, if MCE is built in and creates a
791 problem on some new non-standard machine, you can boot with "nomce"
792 to disable it. MCE support simply ignores non-MCE processors like
793 the 386 and 486, so nearly everyone can say Y here.
795 config X86_OLD_MCE
796 depends on X86_32 && X86_MCE
797 bool "Use legacy machine check code (will go away)"
798 default n
799 select X86_ANCIENT_MCE
800 ---help---
801 Use the old i386 machine check code. This is merely intended for
802 testing in a transition period. Try this if you run into any machine
803 check related software problems, but report the problem to
804 linux-kernel. When in doubt say no.
806 config X86_NEW_MCE
807 depends on X86_MCE
808 bool
809 default y if (!X86_OLD_MCE && X86_32) || X86_64
811 config X86_MCE_INTEL
812 def_bool y
813 prompt "Intel MCE features"
814 depends on X86_NEW_MCE && X86_LOCAL_APIC
815 ---help---
816 Additional support for intel specific MCE features such as
817 the thermal monitor.
819 config X86_MCE_AMD
820 def_bool y
821 prompt "AMD MCE features"
822 depends on X86_NEW_MCE && X86_LOCAL_APIC
823 ---help---
824 Additional support for AMD specific MCE features such as
825 the DRAM Error Threshold.
827 config X86_ANCIENT_MCE
828 def_bool n
829 depends on X86_32
830 prompt "Support for old Pentium 5 / WinChip machine checks"
831 ---help---
832 Include support for machine check handling on old Pentium 5 or WinChip
833 systems. These typically need to be enabled explicitely on the command
834 line.
836 config X86_MCE_THRESHOLD
837 depends on X86_MCE_AMD || X86_MCE_INTEL
838 bool
839 default y
841 config X86_MCE_INJECT
842 depends on X86_NEW_MCE
843 tristate "Machine check injector support"
844 ---help---
845 Provide support for injecting machine checks for testing purposes.
846 If you don't know what a machine check is and you don't do kernel
847 QA it is safe to say n.
849 config X86_MCE_NONFATAL
850 tristate "Check for non-fatal errors on AMD Athlon/Duron / Intel Pentium 4"
851 depends on X86_OLD_MCE
852 ---help---
853 Enabling this feature starts a timer that triggers every 5 seconds which
854 will look at the machine check registers to see if anything happened.
855 Non-fatal problems automatically get corrected (but still logged).
856 Disable this if you don't want to see these messages.
857 Seeing the messages this option prints out may be indicative of dying
858 or out-of-spec (ie, overclocked) hardware.
859 This option only does something on certain CPUs.
860 (AMD Athlon/Duron and Intel Pentium 4)
862 config X86_MCE_P4THERMAL
863 bool "check for P4 thermal throttling interrupt."
864 depends on X86_OLD_MCE && X86_MCE && (X86_UP_APIC || SMP)
865 ---help---
866 Enabling this feature will cause a message to be printed when the P4
867 enters thermal throttling.
869 config X86_THERMAL_VECTOR
870 def_bool y
871 depends on X86_MCE_P4THERMAL || X86_MCE_INTEL
873 config VM86
874 bool "Enable VM86 support" if EMBEDDED
875 default y
876 depends on X86_32
877 ---help---
878 This option is required by programs like DOSEMU to run 16-bit legacy
879 code on X86 processors. It also may be needed by software like
880 XFree86 to initialize some video cards via BIOS. Disabling this
881 option saves about 6k.
883 config TOSHIBA
884 tristate "Toshiba Laptop support"
885 depends on X86_32
886 ---help---
887 This adds a driver to safely access the System Management Mode of
888 the CPU on Toshiba portables with a genuine Toshiba BIOS. It does
889 not work on models with a Phoenix BIOS. The System Management Mode
890 is used to set the BIOS and power saving options on Toshiba portables.
892 For information on utilities to make use of this driver see the
893 Toshiba Linux utilities web site at:
894 <http://www.buzzard.org.uk/toshiba/>.
896 Say Y if you intend to run this kernel on a Toshiba portable.
897 Say N otherwise.
899 config I8K
900 tristate "Dell laptop support"
901 ---help---
902 This adds a driver to safely access the System Management Mode
903 of the CPU on the Dell Inspiron 8000. The System Management Mode
904 is used to read cpu temperature and cooling fan status and to
905 control the fans on the I8K portables.
907 This driver has been tested only on the Inspiron 8000 but it may
908 also work with other Dell laptops. You can force loading on other
909 models by passing the parameter `force=1' to the module. Use at
910 your own risk.
912 For information on utilities to make use of this driver see the
913 I8K Linux utilities web site at:
914 <http://people.debian.org/~dz/i8k/>
916 Say Y if you intend to run this kernel on a Dell Inspiron 8000.
917 Say N otherwise.
919 config X86_REBOOTFIXUPS
920 bool "Enable X86 board specific fixups for reboot"
921 depends on X86_32
922 ---help---
923 This enables chipset and/or board specific fixups to be done
924 in order to get reboot to work correctly. This is only needed on
925 some combinations of hardware and BIOS. The symptom, for which
926 this config is intended, is when reboot ends with a stalled/hung
927 system.
929 Currently, the only fixup is for the Geode machines using
930 CS5530A and CS5536 chipsets and the RDC R-321x SoC.
932 Say Y if you want to enable the fixup. Currently, it's safe to
933 enable this option even if you don't need it.
934 Say N otherwise.
936 config MICROCODE
937 tristate "/dev/cpu/microcode - microcode support"
938 select FW_LOADER
939 ---help---
940 If you say Y here, you will be able to update the microcode on
941 certain Intel and AMD processors. The Intel support is for the
942 IA32 family, e.g. Pentium Pro, Pentium II, Pentium III,
943 Pentium 4, Xeon etc. The AMD support is for family 0x10 and
944 0x11 processors, e.g. Opteron, Phenom and Turion 64 Ultra.
945 You will obviously need the actual microcode binary data itself
946 which is not shipped with the Linux kernel.
948 This option selects the general module only, you need to select
949 at least one vendor specific module as well.
951 To compile this driver as a module, choose M here: the
952 module will be called microcode.
954 config MICROCODE_INTEL
955 bool "Intel microcode patch loading support"
956 depends on MICROCODE
957 default MICROCODE
958 select FW_LOADER
959 ---help---
960 This options enables microcode patch loading support for Intel
961 processors.
963 For latest news and information on obtaining all the required
964 Intel ingredients for this driver, check:
965 <http://www.urbanmyth.org/microcode/>.
967 config MICROCODE_AMD
968 bool "AMD microcode patch loading support"
969 depends on MICROCODE
970 select FW_LOADER
971 ---help---
972 If you select this option, microcode patch loading support for AMD
973 processors will be enabled.
975 config MICROCODE_OLD_INTERFACE
976 def_bool y
977 depends on MICROCODE
979 config X86_MSR
980 tristate "/dev/cpu/*/msr - Model-specific register support"
981 ---help---
982 This device gives privileged processes access to the x86
983 Model-Specific Registers (MSRs). It is a character device with
984 major 202 and minors 0 to 31 for /dev/cpu/0/msr to /dev/cpu/31/msr.
985 MSR accesses are directed to a specific CPU on multi-processor
986 systems.
988 config X86_CPUID
989 tristate "/dev/cpu/*/cpuid - CPU information support"
990 ---help---
991 This device gives processes access to the x86 CPUID instruction to
992 be executed on a specific processor. It is a character device
993 with major 203 and minors 0 to 31 for /dev/cpu/0/cpuid to
994 /dev/cpu/31/cpuid.
996 config X86_CPU_DEBUG
997 tristate "/sys/kernel/debug/x86/cpu/* - CPU Debug support"
998 ---help---
999 If you select this option, this will provide various x86 CPUs
1000 information through debugfs.
1002 choice
1003 prompt "High Memory Support"
1004 default HIGHMEM4G if !X86_NUMAQ
1005 default HIGHMEM64G if X86_NUMAQ
1006 depends on X86_32
1008 config NOHIGHMEM
1009 bool "off"
1010 depends on !X86_NUMAQ
1011 ---help---
1012 Linux can use up to 64 Gigabytes of physical memory on x86 systems.
1013 However, the address space of 32-bit x86 processors is only 4
1014 Gigabytes large. That means that, if you have a large amount of
1015 physical memory, not all of it can be "permanently mapped" by the
1016 kernel. The physical memory that's not permanently mapped is called
1017 "high memory".
1019 If you are compiling a kernel which will never run on a machine with
1020 more than 1 Gigabyte total physical RAM, answer "off" here (default
1021 choice and suitable for most users). This will result in a "3GB/1GB"
1022 split: 3GB are mapped so that each process sees a 3GB virtual memory
1023 space and the remaining part of the 4GB virtual memory space is used
1024 by the kernel to permanently map as much physical memory as
1025 possible.
1027 If the machine has between 1 and 4 Gigabytes physical RAM, then
1028 answer "4GB" here.
1030 If more than 4 Gigabytes is used then answer "64GB" here. This
1031 selection turns Intel PAE (Physical Address Extension) mode on.
1032 PAE implements 3-level paging on IA32 processors. PAE is fully
1033 supported by Linux, PAE mode is implemented on all recent Intel
1034 processors (Pentium Pro and better). NOTE: If you say "64GB" here,
1035 then the kernel will not boot on CPUs that don't support PAE!
1037 The actual amount of total physical memory will either be
1038 auto detected or can be forced by using a kernel command line option
1039 such as "mem=256M". (Try "man bootparam" or see the documentation of
1040 your boot loader (lilo or loadlin) about how to pass options to the
1041 kernel at boot time.)
1043 If unsure, say "off".
1045 config HIGHMEM4G
1046 bool "4GB"
1047 depends on !X86_NUMAQ
1048 ---help---
1049 Select this if you have a 32-bit processor and between 1 and 4
1050 gigabytes of physical RAM.
1052 config HIGHMEM64G
1053 bool "64GB"
1054 depends on !M386 && !M486
1055 select X86_PAE
1056 ---help---
1057 Select this if you have a 32-bit processor and more than 4
1058 gigabytes of physical RAM.
1060 endchoice
1062 choice
1063 depends on EXPERIMENTAL
1064 prompt "Memory split" if EMBEDDED
1065 default VMSPLIT_3G
1066 depends on X86_32
1067 ---help---
1068 Select the desired split between kernel and user memory.
1070 If the address range available to the kernel is less than the
1071 physical memory installed, the remaining memory will be available
1072 as "high memory". Accessing high memory is a little more costly
1073 than low memory, as it needs to be mapped into the kernel first.
1074 Note that increasing the kernel address space limits the range
1075 available to user programs, making the address space there
1076 tighter. Selecting anything other than the default 3G/1G split
1077 will also likely make your kernel incompatible with binary-only
1078 kernel modules.
1080 If you are not absolutely sure what you are doing, leave this
1081 option alone!
1083 config VMSPLIT_3G
1084 bool "3G/1G user/kernel split"
1085 config VMSPLIT_3G_OPT
1086 depends on !X86_PAE
1087 bool "3G/1G user/kernel split (for full 1G low memory)"
1088 config VMSPLIT_2G
1089 bool "2G/2G user/kernel split"
1090 config VMSPLIT_2G_OPT
1091 depends on !X86_PAE
1092 bool "2G/2G user/kernel split (for full 2G low memory)"
1093 config VMSPLIT_1G
1094 bool "1G/3G user/kernel split"
1095 endchoice
1097 config PAGE_OFFSET
1098 hex
1099 default 0xB0000000 if VMSPLIT_3G_OPT
1100 default 0x80000000 if VMSPLIT_2G
1101 default 0x78000000 if VMSPLIT_2G_OPT
1102 default 0x40000000 if VMSPLIT_1G
1103 default 0xC0000000
1104 depends on X86_32
1106 config HIGHMEM
1107 def_bool y
1108 depends on X86_32 && (HIGHMEM64G || HIGHMEM4G)
1110 config X86_PAE
1111 bool "PAE (Physical Address Extension) Support"
1112 depends on X86_32 && !HIGHMEM4G
1113 ---help---
1114 PAE is required for NX support, and furthermore enables
1115 larger swapspace support for non-overcommit purposes. It
1116 has the cost of more pagetable lookup overhead, and also
1117 consumes more pagetable space per process.
1119 config ARCH_PHYS_ADDR_T_64BIT
1120 def_bool X86_64 || X86_PAE
1122 config DIRECT_GBPAGES
1123 bool "Enable 1GB pages for kernel pagetables" if EMBEDDED
1124 default y
1125 depends on X86_64
1126 ---help---
1127 Allow the kernel linear mapping to use 1GB pages on CPUs that
1128 support it. This can improve the kernel's performance a tiny bit by
1129 reducing TLB pressure. If in doubt, say "Y".
1131 # Common NUMA Features
1132 config NUMA
1133 bool "Numa Memory Allocation and Scheduler Support"
1134 depends on SMP
1135 depends on X86_64 || (X86_32 && HIGHMEM64G && (X86_NUMAQ || X86_BIGSMP || X86_SUMMIT && ACPI) && EXPERIMENTAL)
1136 default y if (X86_NUMAQ || X86_SUMMIT || X86_BIGSMP)
1137 ---help---
1138 Enable NUMA (Non Uniform Memory Access) support.
1140 The kernel will try to allocate memory used by a CPU on the
1141 local memory controller of the CPU and add some more
1142 NUMA awareness to the kernel.
1144 For 64-bit this is recommended if the system is Intel Core i7
1145 (or later), AMD Opteron, or EM64T NUMA.
1147 For 32-bit this is only needed on (rare) 32-bit-only platforms
1148 that support NUMA topologies, such as NUMAQ / Summit, or if you
1149 boot a 32-bit kernel on a 64-bit NUMA platform.
1151 Otherwise, you should say N.
1153 comment "NUMA (Summit) requires SMP, 64GB highmem support, ACPI"
1154 depends on X86_32 && X86_SUMMIT && (!HIGHMEM64G || !ACPI)
1156 config K8_NUMA
1157 def_bool y
1158 prompt "Old style AMD Opteron NUMA detection"
1159 depends on X86_64 && NUMA && PCI
1160 ---help---
1161 Enable K8 NUMA node topology detection. You should say Y here if
1162 you have a multi processor AMD K8 system. This uses an old
1163 method to read the NUMA configuration directly from the builtin
1164 Northbridge of Opteron. It is recommended to use X86_64_ACPI_NUMA
1165 instead, which also takes priority if both are compiled in.
1167 config X86_64_ACPI_NUMA
1168 def_bool y
1169 prompt "ACPI NUMA detection"
1170 depends on X86_64 && NUMA && ACPI && PCI
1171 select ACPI_NUMA
1172 ---help---
1173 Enable ACPI SRAT based node topology detection.
1175 # Some NUMA nodes have memory ranges that span
1176 # other nodes. Even though a pfn is valid and
1177 # between a node's start and end pfns, it may not
1178 # reside on that node. See memmap_init_zone()
1179 # for details.
1180 config NODES_SPAN_OTHER_NODES
1181 def_bool y
1182 depends on X86_64_ACPI_NUMA
1184 config NUMA_EMU
1185 bool "NUMA emulation"
1186 depends on X86_64 && NUMA
1187 ---help---
1188 Enable NUMA emulation. A flat machine will be split
1189 into virtual nodes when booted with "numa=fake=N", where N is the
1190 number of nodes. This is only useful for debugging.
1192 config NODES_SHIFT
1193 int "Maximum NUMA Nodes (as a power of 2)" if !MAXSMP
1194 range 1 9
1195 default "9" if MAXSMP
1196 default "6" if X86_64
1197 default "4" if X86_NUMAQ
1198 default "3"
1199 depends on NEED_MULTIPLE_NODES
1200 ---help---
1201 Specify the maximum number of NUMA Nodes available on the target
1202 system. Increases memory reserved to accommodate various tables.
1204 config HAVE_ARCH_BOOTMEM
1205 def_bool y
1206 depends on X86_32 && NUMA
1208 config ARCH_HAVE_MEMORY_PRESENT
1209 def_bool y
1210 depends on X86_32 && DISCONTIGMEM
1212 config NEED_NODE_MEMMAP_SIZE
1213 def_bool y
1214 depends on X86_32 && (DISCONTIGMEM || SPARSEMEM)
1216 config HAVE_ARCH_ALLOC_REMAP
1217 def_bool y
1218 depends on X86_32 && NUMA
1220 config ARCH_FLATMEM_ENABLE
1221 def_bool y
1222 depends on X86_32 && ARCH_SELECT_MEMORY_MODEL && !NUMA
1224 config ARCH_DISCONTIGMEM_ENABLE
1225 def_bool y
1226 depends on NUMA && X86_32
1228 config ARCH_DISCONTIGMEM_DEFAULT
1229 def_bool y
1230 depends on NUMA && X86_32
1232 config ARCH_SPARSEMEM_DEFAULT
1233 def_bool y
1234 depends on X86_64
1236 config ARCH_SPARSEMEM_ENABLE
1237 def_bool y
1238 depends on X86_64 || NUMA || (EXPERIMENTAL && X86_32) || X86_32_NON_STANDARD
1239 select SPARSEMEM_STATIC if X86_32
1240 select SPARSEMEM_VMEMMAP_ENABLE if X86_64
1242 config ARCH_SELECT_MEMORY_MODEL
1243 def_bool y
1244 depends on ARCH_SPARSEMEM_ENABLE
1246 config ARCH_MEMORY_PROBE
1247 def_bool X86_64
1248 depends on MEMORY_HOTPLUG
1250 source "mm/Kconfig"
1252 config HIGHPTE
1253 bool "Allocate 3rd-level pagetables from highmem"
1254 depends on X86_32 && (HIGHMEM4G || HIGHMEM64G)
1255 ---help---
1256 The VM uses one page table entry for each page of physical memory.
1257 For systems with a lot of RAM, this can be wasteful of precious
1258 low memory. Setting this option will put user-space page table
1259 entries in high memory.
1261 config X86_CHECK_BIOS_CORRUPTION
1262 bool "Check for low memory corruption"
1263 ---help---
1264 Periodically check for memory corruption in low memory, which
1265 is suspected to be caused by BIOS. Even when enabled in the
1266 configuration, it is disabled at runtime. Enable it by
1267 setting "memory_corruption_check=1" on the kernel command
1268 line. By default it scans the low 64k of memory every 60
1269 seconds; see the memory_corruption_check_size and
1270 memory_corruption_check_period parameters in
1271 Documentation/kernel-parameters.txt to adjust this.
1273 When enabled with the default parameters, this option has
1274 almost no overhead, as it reserves a relatively small amount
1275 of memory and scans it infrequently. It both detects corruption
1276 and prevents it from affecting the running system.
1278 It is, however, intended as a diagnostic tool; if repeatable
1279 BIOS-originated corruption always affects the same memory,
1280 you can use memmap= to prevent the kernel from using that
1281 memory.
1283 config X86_BOOTPARAM_MEMORY_CORRUPTION_CHECK
1284 bool "Set the default setting of memory_corruption_check"
1285 depends on X86_CHECK_BIOS_CORRUPTION
1286 default y
1287 ---help---
1288 Set whether the default state of memory_corruption_check is
1289 on or off.
1291 config X86_RESERVE_LOW_64K
1292 bool "Reserve low 64K of RAM on AMI/Phoenix BIOSen"
1293 default y
1294 ---help---
1295 Reserve the first 64K of physical RAM on BIOSes that are known
1296 to potentially corrupt that memory range. A numbers of BIOSes are
1297 known to utilize this area during suspend/resume, so it must not
1298 be used by the kernel.
1300 Set this to N if you are absolutely sure that you trust the BIOS
1301 to get all its memory reservations and usages right.
1303 If you have doubts about the BIOS (e.g. suspend/resume does not
1304 work or there's kernel crashes after certain hardware hotplug
1305 events) and it's not AMI or Phoenix, then you might want to enable
1306 X86_CHECK_BIOS_CORRUPTION=y to allow the kernel to check typical
1307 corruption patterns.
1309 Say Y if unsure.
1311 config MATH_EMULATION
1312 bool
1313 prompt "Math emulation" if X86_32
1314 ---help---
1315 Linux can emulate a math coprocessor (used for floating point
1316 operations) if you don't have one. 486DX and Pentium processors have
1317 a math coprocessor built in, 486SX and 386 do not, unless you added
1318 a 487DX or 387, respectively. (The messages during boot time can
1319 give you some hints here ["man dmesg"].) Everyone needs either a
1320 coprocessor or this emulation.
1322 If you don't have a math coprocessor, you need to say Y here; if you
1323 say Y here even though you have a coprocessor, the coprocessor will
1324 be used nevertheless. (This behavior can be changed with the kernel
1325 command line option "no387", which comes handy if your coprocessor
1326 is broken. Try "man bootparam" or see the documentation of your boot
1327 loader (lilo or loadlin) about how to pass options to the kernel at
1328 boot time.) This means that it is a good idea to say Y here if you
1329 intend to use this kernel on different machines.
1331 More information about the internals of the Linux math coprocessor
1332 emulation can be found in <file:arch/x86/math-emu/README>.
1334 If you are not sure, say Y; apart from resulting in a 66 KB bigger
1335 kernel, it won't hurt.
1337 config MTRR
1338 bool "MTRR (Memory Type Range Register) support"
1339 ---help---
1340 On Intel P6 family processors (Pentium Pro, Pentium II and later)
1341 the Memory Type Range Registers (MTRRs) may be used to control
1342 processor access to memory ranges. This is most useful if you have
1343 a video (VGA) card on a PCI or AGP bus. Enabling write-combining
1344 allows bus write transfers to be combined into a larger transfer
1345 before bursting over the PCI/AGP bus. This can increase performance
1346 of image write operations 2.5 times or more. Saying Y here creates a
1347 /proc/mtrr file which may be used to manipulate your processor's
1348 MTRRs. Typically the X server should use this.
1350 This code has a reasonably generic interface so that similar
1351 control registers on other processors can be easily supported
1352 as well:
1354 The Cyrix 6x86, 6x86MX and M II processors have Address Range
1355 Registers (ARRs) which provide a similar functionality to MTRRs. For
1356 these, the ARRs are used to emulate the MTRRs.
1357 The AMD K6-2 (stepping 8 and above) and K6-3 processors have two
1358 MTRRs. The Centaur C6 (WinChip) has 8 MCRs, allowing
1359 write-combining. All of these processors are supported by this code
1360 and it makes sense to say Y here if you have one of them.
1362 Saying Y here also fixes a problem with buggy SMP BIOSes which only
1363 set the MTRRs for the boot CPU and not for the secondary CPUs. This
1364 can lead to all sorts of problems, so it's good to say Y here.
1366 You can safely say Y even if your machine doesn't have MTRRs, you'll
1367 just add about 9 KB to your kernel.
1369 See <file:Documentation/x86/mtrr.txt> for more information.
1371 config MTRR_SANITIZER
1372 def_bool y
1373 prompt "MTRR cleanup support"
1374 depends on MTRR
1375 ---help---
1376 Convert MTRR layout from continuous to discrete, so X drivers can
1377 add writeback entries.
1379 Can be disabled with disable_mtrr_cleanup on the kernel command line.
1380 The largest mtrr entry size for a continuous block can be set with
1381 mtrr_chunk_size.
1383 If unsure, say Y.
1385 config MTRR_SANITIZER_ENABLE_DEFAULT
1386 int "MTRR cleanup enable value (0-1)"
1387 range 0 1
1388 default "0"
1389 depends on MTRR_SANITIZER
1390 ---help---
1391 Enable mtrr cleanup default value
1393 config MTRR_SANITIZER_SPARE_REG_NR_DEFAULT
1394 int "MTRR cleanup spare reg num (0-7)"
1395 range 0 7
1396 default "1"
1397 depends on MTRR_SANITIZER
1398 ---help---
1399 mtrr cleanup spare entries default, it can be changed via
1400 mtrr_spare_reg_nr=N on the kernel command line.
1402 config X86_PAT
1403 bool
1404 prompt "x86 PAT support"
1405 depends on MTRR
1406 ---help---
1407 Use PAT attributes to setup page level cache control.
1409 PATs are the modern equivalents of MTRRs and are much more
1410 flexible than MTRRs.
1412 Say N here if you see bootup problems (boot crash, boot hang,
1413 spontaneous reboots) or a non-working video driver.
1415 If unsure, say Y.
1417 config EFI
1418 bool "EFI runtime service support"
1419 depends on ACPI
1420 ---help---
1421 This enables the kernel to use EFI runtime services that are
1422 available (such as the EFI variable services).
1424 This option is only useful on systems that have EFI firmware.
1425 In addition, you should use the latest ELILO loader available
1426 at <http://elilo.sourceforge.net> in order to take advantage
1427 of EFI runtime services. However, even with this option, the
1428 resultant kernel should continue to boot on existing non-EFI
1429 platforms.
1431 config SECCOMP
1432 def_bool y
1433 prompt "Enable seccomp to safely compute untrusted bytecode"
1434 ---help---
1435 This kernel feature is useful for number crunching applications
1436 that may need to compute untrusted bytecode during their
1437 execution. By using pipes or other transports made available to
1438 the process as file descriptors supporting the read/write
1439 syscalls, it's possible to isolate those applications in
1440 their own address space using seccomp. Once seccomp is
1441 enabled via prctl(PR_SET_SECCOMP), it cannot be disabled
1442 and the task is only allowed to execute a few safe syscalls
1443 defined by each seccomp mode.
1445 If unsure, say Y. Only embedded should say N here.
1447 config CC_STACKPROTECTOR_ALL
1448 bool
1450 config CC_STACKPROTECTOR
1451 bool "Enable -fstack-protector buffer overflow detection (EXPERIMENTAL)"
1452 select CC_STACKPROTECTOR_ALL
1453 ---help---
1454 This option turns on the -fstack-protector GCC feature. This
1455 feature puts, at the beginning of functions, a canary value on
1456 the stack just before the return address, and validates
1457 the value just before actually returning. Stack based buffer
1458 overflows (that need to overwrite this return address) now also
1459 overwrite the canary, which gets detected and the attack is then
1460 neutralized via a kernel panic.
1462 This feature requires gcc version 4.2 or above, or a distribution
1463 gcc with the feature backported. Older versions are automatically
1464 detected and for those versions, this configuration option is
1465 ignored. (and a warning is printed during bootup)
1467 source kernel/Kconfig.hz
1469 config KEXEC
1470 bool "kexec system call"
1471 ---help---
1472 kexec is a system call that implements the ability to shutdown your
1473 current kernel, and to start another kernel. It is like a reboot
1474 but it is independent of the system firmware. And like a reboot
1475 you can start any kernel with it, not just Linux.
1477 The name comes from the similarity to the exec system call.
1479 It is an ongoing process to be certain the hardware in a machine
1480 is properly shutdown, so do not be surprised if this code does not
1481 initially work for you. It may help to enable device hotplugging
1482 support. As of this writing the exact hardware interface is
1483 strongly in flux, so no good recommendation can be made.
1485 config CRASH_DUMP
1486 bool "kernel crash dumps"
1487 depends on X86_64 || (X86_32 && HIGHMEM)
1488 ---help---
1489 Generate crash dump after being started by kexec.
1490 This should be normally only set in special crash dump kernels
1491 which are loaded in the main kernel with kexec-tools into
1492 a specially reserved region and then later executed after
1493 a crash by kdump/kexec. The crash dump kernel must be compiled
1494 to a memory address not used by the main kernel or BIOS using
1495 PHYSICAL_START, or it must be built as a relocatable image
1496 (CONFIG_RELOCATABLE=y).
1497 For more details see Documentation/kdump/kdump.txt
1499 config KEXEC_JUMP
1500 bool "kexec jump (EXPERIMENTAL)"
1501 depends on EXPERIMENTAL
1502 depends on KEXEC && HIBERNATION
1503 ---help---
1504 Jump between original kernel and kexeced kernel and invoke
1505 code in physical address mode via KEXEC
1507 config PHYSICAL_START
1508 hex "Physical address where the kernel is loaded" if (EMBEDDED || CRASH_DUMP)
1509 default "0x1000000"
1510 ---help---
1511 This gives the physical address where the kernel is loaded.
1513 If kernel is a not relocatable (CONFIG_RELOCATABLE=n) then
1514 bzImage will decompress itself to above physical address and
1515 run from there. Otherwise, bzImage will run from the address where
1516 it has been loaded by the boot loader and will ignore above physical
1517 address.
1519 In normal kdump cases one does not have to set/change this option
1520 as now bzImage can be compiled as a completely relocatable image
1521 (CONFIG_RELOCATABLE=y) and be used to load and run from a different
1522 address. This option is mainly useful for the folks who don't want
1523 to use a bzImage for capturing the crash dump and want to use a
1524 vmlinux instead. vmlinux is not relocatable hence a kernel needs
1525 to be specifically compiled to run from a specific memory area
1526 (normally a reserved region) and this option comes handy.
1528 So if you are using bzImage for capturing the crash dump,
1529 leave the value here unchanged to 0x1000000 and set
1530 CONFIG_RELOCATABLE=y. Otherwise if you plan to use vmlinux
1531 for capturing the crash dump change this value to start of
1532 the reserved region. In other words, it can be set based on
1533 the "X" value as specified in the "crashkernel=YM@XM"
1534 command line boot parameter passed to the panic-ed
1535 kernel. Please take a look at Documentation/kdump/kdump.txt
1536 for more details about crash dumps.
1538 Usage of bzImage for capturing the crash dump is recommended as
1539 one does not have to build two kernels. Same kernel can be used
1540 as production kernel and capture kernel. Above option should have
1541 gone away after relocatable bzImage support is introduced. But it
1542 is present because there are users out there who continue to use
1543 vmlinux for dump capture. This option should go away down the
1544 line.
1546 Don't change this unless you know what you are doing.
1548 config RELOCATABLE
1549 bool "Build a relocatable kernel"
1550 default y
1551 ---help---
1552 This builds a kernel image that retains relocation information
1553 so it can be loaded someplace besides the default 1MB.
1554 The relocations tend to make the kernel binary about 10% larger,
1555 but are discarded at runtime.
1557 One use is for the kexec on panic case where the recovery kernel
1558 must live at a different physical address than the primary
1559 kernel.
1561 Note: If CONFIG_RELOCATABLE=y, then the kernel runs from the address
1562 it has been loaded at and the compile time physical address
1563 (CONFIG_PHYSICAL_START) is ignored.
1565 # Relocation on x86-32 needs some additional build support
1566 config X86_NEED_RELOCS
1567 def_bool y
1568 depends on X86_32 && RELOCATABLE
1570 config PHYSICAL_ALIGN
1571 hex
1572 prompt "Alignment value to which kernel should be aligned" if X86_32
1573 default "0x1000000"
1574 range 0x2000 0x1000000
1575 ---help---
1576 This value puts the alignment restrictions on physical address
1577 where kernel is loaded and run from. Kernel is compiled for an
1578 address which meets above alignment restriction.
1580 If bootloader loads the kernel at a non-aligned address and
1581 CONFIG_RELOCATABLE is set, kernel will move itself to nearest
1582 address aligned to above value and run from there.
1584 If bootloader loads the kernel at a non-aligned address and
1585 CONFIG_RELOCATABLE is not set, kernel will ignore the run time
1586 load address and decompress itself to the address it has been
1587 compiled for and run from there. The address for which kernel is
1588 compiled already meets above alignment restrictions. Hence the
1589 end result is that kernel runs from a physical address meeting
1590 above alignment restrictions.
1592 Don't change this unless you know what you are doing.
1594 config HOTPLUG_CPU
1595 bool "Support for hot-pluggable CPUs"
1596 depends on SMP && HOTPLUG
1597 ---help---
1598 Say Y here to allow turning CPUs off and on. CPUs can be
1599 controlled through /sys/devices/system/cpu.
1600 ( Note: power management support will enable this option
1601 automatically on SMP systems. )
1602 Say N if you want to disable CPU hotplug.
1604 config COMPAT_VDSO
1605 def_bool y
1606 prompt "Compat VDSO support"
1607 depends on X86_32 || IA32_EMULATION
1608 ---help---
1609 Map the 32-bit VDSO to the predictable old-style address too.
1610 ---help---
1611 Say N here if you are running a sufficiently recent glibc
1612 version (2.3.3 or later), to remove the high-mapped
1613 VDSO mapping and to exclusively use the randomized VDSO.
1615 If unsure, say Y.
1617 config CMDLINE_BOOL
1618 bool "Built-in kernel command line"
1619 default n
1620 ---help---
1621 Allow for specifying boot arguments to the kernel at
1622 build time. On some systems (e.g. embedded ones), it is
1623 necessary or convenient to provide some or all of the
1624 kernel boot arguments with the kernel itself (that is,
1625 to not rely on the boot loader to provide them.)
1627 To compile command line arguments into the kernel,
1628 set this option to 'Y', then fill in the
1629 the boot arguments in CONFIG_CMDLINE.
1631 Systems with fully functional boot loaders (i.e. non-embedded)
1632 should leave this option set to 'N'.
1634 config CMDLINE
1635 string "Built-in kernel command string"
1636 depends on CMDLINE_BOOL
1637 default ""
1638 ---help---
1639 Enter arguments here that should be compiled into the kernel
1640 image and used at boot time. If the boot loader provides a
1641 command line at boot time, it is appended to this string to
1642 form the full kernel command line, when the system boots.
1644 However, you can use the CONFIG_CMDLINE_OVERRIDE option to
1645 change this behavior.
1647 In most cases, the command line (whether built-in or provided
1648 by the boot loader) should specify the device for the root
1649 file system.
1651 config CMDLINE_OVERRIDE
1652 bool "Built-in command line overrides boot loader arguments"
1653 default n
1654 depends on CMDLINE_BOOL
1655 ---help---
1656 Set this option to 'Y' to have the kernel ignore the boot loader
1657 command line, and use ONLY the built-in command line.
1659 This is used to work around broken boot loaders. This should
1660 be set to 'N' under normal conditions.
1662 endmenu
1664 config ARCH_ENABLE_MEMORY_HOTPLUG
1665 def_bool y
1666 depends on X86_64 || (X86_32 && HIGHMEM)
1668 config ARCH_ENABLE_MEMORY_HOTREMOVE
1669 def_bool y
1670 depends on MEMORY_HOTPLUG
1672 config HAVE_ARCH_EARLY_PFN_TO_NID
1673 def_bool X86_64
1674 depends on NUMA
1676 menu "Power management and ACPI options"
1678 config ARCH_HIBERNATION_HEADER
1679 def_bool y
1680 depends on X86_64 && HIBERNATION
1682 source "kernel/power/Kconfig"
1684 source "drivers/acpi/Kconfig"
1686 source "drivers/sfi/Kconfig"
1688 config X86_APM_BOOT
1689 bool
1690 default y
1691 depends on APM || APM_MODULE
1693 menuconfig APM
1694 tristate "APM (Advanced Power Management) BIOS support"
1695 depends on X86_32 && PM_SLEEP
1696 ---help---
1697 APM is a BIOS specification for saving power using several different
1698 techniques. This is mostly useful for battery powered laptops with
1699 APM compliant BIOSes. If you say Y here, the system time will be
1700 reset after a RESUME operation, the /proc/apm device will provide
1701 battery status information, and user-space programs will receive
1702 notification of APM "events" (e.g. battery status change).
1704 If you select "Y" here, you can disable actual use of the APM
1705 BIOS by passing the "apm=off" option to the kernel at boot time.
1707 Note that the APM support is almost completely disabled for
1708 machines with more than one CPU.
1710 In order to use APM, you will need supporting software. For location
1711 and more information, read <file:Documentation/power/pm.txt> and the
1712 Battery Powered Linux mini-HOWTO, available from
1713 <http://www.tldp.org/docs.html#howto>.
1715 This driver does not spin down disk drives (see the hdparm(8)
1716 manpage ("man 8 hdparm") for that), and it doesn't turn off
1717 VESA-compliant "green" monitors.
1719 This driver does not support the TI 4000M TravelMate and the ACER
1720 486/DX4/75 because they don't have compliant BIOSes. Many "green"
1721 desktop machines also don't have compliant BIOSes, and this driver
1722 may cause those machines to panic during the boot phase.
1724 Generally, if you don't have a battery in your machine, there isn't
1725 much point in using this driver and you should say N. If you get
1726 random kernel OOPSes or reboots that don't seem to be related to
1727 anything, try disabling/enabling this option (or disabling/enabling
1728 APM in your BIOS).
1730 Some other things you should try when experiencing seemingly random,
1731 "weird" problems:
1733 1) make sure that you have enough swap space and that it is
1734 enabled.
1735 2) pass the "no-hlt" option to the kernel
1736 3) switch on floating point emulation in the kernel and pass
1737 the "no387" option to the kernel
1738 4) pass the "floppy=nodma" option to the kernel
1739 5) pass the "mem=4M" option to the kernel (thereby disabling
1740 all but the first 4 MB of RAM)
1741 6) make sure that the CPU is not over clocked.
1742 7) read the sig11 FAQ at <http://www.bitwizard.nl/sig11/>
1743 8) disable the cache from your BIOS settings
1744 9) install a fan for the video card or exchange video RAM
1745 10) install a better fan for the CPU
1746 11) exchange RAM chips
1747 12) exchange the motherboard.
1749 To compile this driver as a module, choose M here: the
1750 module will be called apm.
1752 if APM
1754 config APM_IGNORE_USER_SUSPEND
1755 bool "Ignore USER SUSPEND"
1756 ---help---
1757 This option will ignore USER SUSPEND requests. On machines with a
1758 compliant APM BIOS, you want to say N. However, on the NEC Versa M
1759 series notebooks, it is necessary to say Y because of a BIOS bug.
1761 config APM_DO_ENABLE
1762 bool "Enable PM at boot time"
1763 ---help---
1764 Enable APM features at boot time. From page 36 of the APM BIOS
1765 specification: "When disabled, the APM BIOS does not automatically
1766 power manage devices, enter the Standby State, enter the Suspend
1767 State, or take power saving steps in response to CPU Idle calls."
1768 This driver will make CPU Idle calls when Linux is idle (unless this
1769 feature is turned off -- see "Do CPU IDLE calls", below). This
1770 should always save battery power, but more complicated APM features
1771 will be dependent on your BIOS implementation. You may need to turn
1772 this option off if your computer hangs at boot time when using APM
1773 support, or if it beeps continuously instead of suspending. Turn
1774 this off if you have a NEC UltraLite Versa 33/C or a Toshiba
1775 T400CDT. This is off by default since most machines do fine without
1776 this feature.
1778 config APM_CPU_IDLE
1779 bool "Make CPU Idle calls when idle"
1780 ---help---
1781 Enable calls to APM CPU Idle/CPU Busy inside the kernel's idle loop.
1782 On some machines, this can activate improved power savings, such as
1783 a slowed CPU clock rate, when the machine is idle. These idle calls
1784 are made after the idle loop has run for some length of time (e.g.,
1785 333 mS). On some machines, this will cause a hang at boot time or
1786 whenever the CPU becomes idle. (On machines with more than one CPU,
1787 this option does nothing.)
1789 config APM_DISPLAY_BLANK
1790 bool "Enable console blanking using APM"
1791 ---help---
1792 Enable console blanking using the APM. Some laptops can use this to
1793 turn off the LCD backlight when the screen blanker of the Linux
1794 virtual console blanks the screen. Note that this is only used by
1795 the virtual console screen blanker, and won't turn off the backlight
1796 when using the X Window system. This also doesn't have anything to
1797 do with your VESA-compliant power-saving monitor. Further, this
1798 option doesn't work for all laptops -- it might not turn off your
1799 backlight at all, or it might print a lot of errors to the console,
1800 especially if you are using gpm.
1802 config APM_ALLOW_INTS
1803 bool "Allow interrupts during APM BIOS calls"
1804 ---help---
1805 Normally we disable external interrupts while we are making calls to
1806 the APM BIOS as a measure to lessen the effects of a badly behaving
1807 BIOS implementation. The BIOS should reenable interrupts if it
1808 needs to. Unfortunately, some BIOSes do not -- especially those in
1809 many of the newer IBM Thinkpads. If you experience hangs when you
1810 suspend, try setting this to Y. Otherwise, say N.
1812 endif # APM
1814 source "arch/x86/kernel/cpu/cpufreq/Kconfig"
1816 source "drivers/cpuidle/Kconfig"
1818 source "drivers/idle/Kconfig"
1820 endmenu
1823 menu "Bus options (PCI etc.)"
1825 config PCI
1826 bool "PCI support"
1827 default y
1828 select ARCH_SUPPORTS_MSI if (X86_LOCAL_APIC && X86_IO_APIC)
1829 ---help---
1830 Find out whether you have a PCI motherboard. PCI is the name of a
1831 bus system, i.e. the way the CPU talks to the other stuff inside
1832 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
1833 VESA. If you have PCI, say Y, otherwise N.
1835 choice
1836 prompt "PCI access mode"
1837 depends on X86_32 && PCI
1838 default PCI_GOANY
1839 ---help---
1840 On PCI systems, the BIOS can be used to detect the PCI devices and
1841 determine their configuration. However, some old PCI motherboards
1842 have BIOS bugs and may crash if this is done. Also, some embedded
1843 PCI-based systems don't have any BIOS at all. Linux can also try to
1844 detect the PCI hardware directly without using the BIOS.
1846 With this option, you can specify how Linux should detect the
1847 PCI devices. If you choose "BIOS", the BIOS will be used,
1848 if you choose "Direct", the BIOS won't be used, and if you
1849 choose "MMConfig", then PCI Express MMCONFIG will be used.
1850 If you choose "Any", the kernel will try MMCONFIG, then the
1851 direct access method and falls back to the BIOS if that doesn't
1852 work. If unsure, go with the default, which is "Any".
1854 config PCI_GOBIOS
1855 bool "BIOS"
1857 config PCI_GOMMCONFIG
1858 bool "MMConfig"
1860 config PCI_GODIRECT
1861 bool "Direct"
1863 config PCI_GOOLPC
1864 bool "OLPC"
1865 depends on OLPC
1867 config PCI_GOANY
1868 bool "Any"
1870 endchoice
1872 config PCI_BIOS
1873 def_bool y
1874 depends on X86_32 && PCI && (PCI_GOBIOS || PCI_GOANY)
1876 # x86-64 doesn't support PCI BIOS access from long mode so always go direct.
1877 config PCI_DIRECT
1878 def_bool y
1879 depends on PCI && (X86_64 || (PCI_GODIRECT || PCI_GOANY || PCI_GOOLPC))
1881 config PCI_MMCONFIG
1882 def_bool y
1883 depends on X86_32 && PCI && ACPI && (PCI_GOMMCONFIG || PCI_GOANY)
1885 config PCI_OLPC
1886 def_bool y
1887 depends on PCI && OLPC && (PCI_GOOLPC || PCI_GOANY)
1889 config PCI_DOMAINS
1890 def_bool y
1891 depends on PCI
1893 config PCI_MMCONFIG
1894 bool "Support mmconfig PCI config space access"
1895 depends on X86_64 && PCI && ACPI
1897 config DMAR
1898 bool "Support for DMA Remapping Devices (EXPERIMENTAL)"
1899 depends on PCI_MSI && ACPI && EXPERIMENTAL
1900 help
1901 DMA remapping (DMAR) devices support enables independent address
1902 translations for Direct Memory Access (DMA) from devices.
1903 These DMA remapping devices are reported via ACPI tables
1904 and include PCI device scope covered by these DMA
1905 remapping devices.
1907 config DMAR_DEFAULT_ON
1908 def_bool y
1909 prompt "Enable DMA Remapping Devices by default"
1910 depends on DMAR
1911 help
1912 Selecting this option will enable a DMAR device at boot time if
1913 one is found. If this option is not selected, DMAR support can
1914 be enabled by passing intel_iommu=on to the kernel. It is
1915 recommended you say N here while the DMAR code remains
1916 experimental.
1918 config DMAR_BROKEN_GFX_WA
1919 def_bool n
1920 prompt "Workaround broken graphics drivers (going away soon)"
1921 depends on DMAR
1922 ---help---
1923 Current Graphics drivers tend to use physical address
1924 for DMA and avoid using DMA APIs. Setting this config
1925 option permits the IOMMU driver to set a unity map for
1926 all the OS-visible memory. Hence the driver can continue
1927 to use physical addresses for DMA, at least until this
1928 option is removed in the 2.6.32 kernel.
1930 config DMAR_FLOPPY_WA
1931 def_bool y
1932 depends on DMAR
1933 ---help---
1934 Floppy disk drivers are known to bypass DMA API calls
1935 thereby failing to work when IOMMU is enabled. This
1936 workaround will setup a 1:1 mapping for the first
1937 16MiB to make floppy (an ISA device) work.
1939 config INTR_REMAP
1940 bool "Support for Interrupt Remapping (EXPERIMENTAL)"
1941 depends on X86_64 && X86_IO_APIC && PCI_MSI && ACPI && EXPERIMENTAL
1942 ---help---
1943 Supports Interrupt remapping for IO-APIC and MSI devices.
1944 To use x2apic mode in the CPU's which support x2APIC enhancements or
1945 to support platforms with CPU's having > 8 bit APIC ID, say Y.
1947 source "drivers/pci/pcie/Kconfig"
1949 source "drivers/pci/Kconfig"
1951 # x86_64 have no ISA slots, but do have ISA-style DMA.
1952 config ISA_DMA_API
1953 def_bool y
1955 if X86_32
1957 config ISA
1958 bool "ISA support"
1959 ---help---
1960 Find out whether you have ISA slots on your motherboard. ISA is the
1961 name of a bus system, i.e. the way the CPU talks to the other stuff
1962 inside your box. Other bus systems are PCI, EISA, MicroChannel
1963 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
1964 newer boards don't support it. If you have ISA, say Y, otherwise N.
1966 config EISA
1967 bool "EISA support"
1968 depends on ISA
1969 ---help---
1970 The Extended Industry Standard Architecture (EISA) bus was
1971 developed as an open alternative to the IBM MicroChannel bus.
1973 The EISA bus provided some of the features of the IBM MicroChannel
1974 bus while maintaining backward compatibility with cards made for
1975 the older ISA bus. The EISA bus saw limited use between 1988 and
1976 1995 when it was made obsolete by the PCI bus.
1978 Say Y here if you are building a kernel for an EISA-based machine.
1980 Otherwise, say N.
1982 source "drivers/eisa/Kconfig"
1984 config MCA
1985 bool "MCA support"
1986 ---help---
1987 MicroChannel Architecture is found in some IBM PS/2 machines and
1988 laptops. It is a bus system similar to PCI or ISA. See
1989 <file:Documentation/mca.txt> (and especially the web page given
1990 there) before attempting to build an MCA bus kernel.
1992 source "drivers/mca/Kconfig"
1994 config SCx200
1995 tristate "NatSemi SCx200 support"
1996 ---help---
1997 This provides basic support for National Semiconductor's
1998 (now AMD's) Geode processors. The driver probes for the
1999 PCI-IDs of several on-chip devices, so its a good dependency
2000 for other scx200_* drivers.
2002 If compiled as a module, the driver is named scx200.
2004 config SCx200HR_TIMER
2005 tristate "NatSemi SCx200 27MHz High-Resolution Timer Support"
2006 depends on SCx200 && GENERIC_TIME
2007 default y
2008 ---help---
2009 This driver provides a clocksource built upon the on-chip
2010 27MHz high-resolution timer. Its also a workaround for
2011 NSC Geode SC-1100's buggy TSC, which loses time when the
2012 processor goes idle (as is done by the scheduler). The
2013 other workaround is idle=poll boot option.
2015 config GEODE_MFGPT_TIMER
2016 def_bool y
2017 prompt "Geode Multi-Function General Purpose Timer (MFGPT) events"
2018 depends on MGEODE_LX && GENERIC_TIME && GENERIC_CLOCKEVENTS
2019 ---help---
2020 This driver provides a clock event source based on the MFGPT
2021 timer(s) in the CS5535 and CS5536 companion chip for the geode.
2022 MFGPTs have a better resolution and max interval than the
2023 generic PIT, and are suitable for use as high-res timers.
2025 config OLPC
2026 bool "One Laptop Per Child support"
2027 default n
2028 ---help---
2029 Add support for detecting the unique features of the OLPC
2030 XO hardware.
2032 endif # X86_32
2034 config K8_NB
2035 def_bool y
2036 depends on AGP_AMD64 || (X86_64 && (GART_IOMMU || (PCI && NUMA)))
2038 source "drivers/pcmcia/Kconfig"
2040 source "drivers/pci/hotplug/Kconfig"
2042 endmenu
2045 menu "Executable file formats / Emulations"
2047 source "fs/Kconfig.binfmt"
2049 config IA32_EMULATION
2050 bool "IA32 Emulation"
2051 depends on X86_64
2052 select COMPAT_BINFMT_ELF
2053 ---help---
2054 Include code to run 32-bit programs under a 64-bit kernel. You should
2055 likely turn this on, unless you're 100% sure that you don't have any
2056 32-bit programs left.
2058 config IA32_AOUT
2059 tristate "IA32 a.out support"
2060 depends on IA32_EMULATION
2061 ---help---
2062 Support old a.out binaries in the 32bit emulation.
2064 config COMPAT
2065 def_bool y
2066 depends on IA32_EMULATION
2068 config COMPAT_FOR_U64_ALIGNMENT
2069 def_bool COMPAT
2070 depends on X86_64
2072 config SYSVIPC_COMPAT
2073 def_bool y
2074 depends on COMPAT && SYSVIPC
2076 endmenu
2079 config HAVE_ATOMIC_IOMAP
2080 def_bool y
2081 depends on X86_32
2083 source "net/Kconfig"
2085 source "drivers/Kconfig"
2087 source "drivers/firmware/Kconfig"
2089 source "fs/Kconfig"
2091 source "arch/x86/Kconfig.debug"
2093 source "security/Kconfig"
2095 source "crypto/Kconfig"
2097 source "arch/x86/kvm/Kconfig"
2099 source "lib/Kconfig"