2 mainmenu "Linux Kernel Configuration for x86"
6 bool "64-bit kernel" if ARCH = "x86"
7 default ARCH = "x86_64"
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
21 select HAVE_UNSTABLE_SCHED_CLOCK
25 select HAVE_KRETPROBES
26 select HAVE_KVM if ((X86_32 && !X86_VOYAGER && !X86_VISWS && !X86_NUMAQ) || X86_64)
27 select HAVE_ARCH_KGDB if !X86_VOYAGER
33 default "arch/x86/configs/i386_defconfig"
39 default "arch/x86/configs/x86_64_defconfig"
42 config GENERIC_LOCKBREAK
48 config GENERIC_CMOS_UPDATE
51 config CLOCKSOURCE_WATCHDOG
54 config GENERIC_CLOCKEVENTS
57 config GENERIC_CLOCKEVENTS_BROADCAST
59 depends on X86_64 || (X86_32 && X86_LOCAL_APIC)
61 config LOCKDEP_SUPPORT
64 config STACKTRACE_SUPPORT
67 config HAVE_LATENCYTOP_SUPPORT
70 config FAST_CMPXCHG_LOCAL
83 config GENERIC_ISA_DMA
93 config GENERIC_HWEIGHT
99 config ARCH_MAY_HAVE_PC_FDC
102 config RWSEM_GENERIC_SPINLOCK
105 config RWSEM_XCHGADD_ALGORITHM
108 config ARCH_HAS_ILOG2_U32
111 config ARCH_HAS_ILOG2_U64
114 config ARCH_HAS_CPU_IDLE_WAIT
117 config GENERIC_CALIBRATE_DELAY
120 config GENERIC_TIME_VSYSCALL
124 config ARCH_HAS_CPU_RELAX
127 config ARCH_HAS_CACHE_LINE_SIZE
130 config HAVE_SETUP_PER_CPU_AREA
131 def_bool X86_64 || (X86_SMP && !X86_VOYAGER)
133 config HAVE_CPUMASK_OF_CPU_MAP
136 config ARCH_HIBERNATION_POSSIBLE
138 depends on !SMP || !X86_VOYAGER
140 config ARCH_SUSPEND_POSSIBLE
142 depends on !X86_VOYAGER
148 config ARCH_POPULATES_NODE_MAP
155 config ARCH_SUPPORTS_AOUT
158 config ARCH_SUPPORTS_OPTIMIZED_INLINING
161 # Use the generic interrupt handling code in kernel/irq/:
162 config GENERIC_HARDIRQS
166 config GENERIC_IRQ_PROBE
170 config GENERIC_PENDING_IRQ
172 depends on GENERIC_HARDIRQS && SMP
177 depends on SMP && ((X86_32 && !X86_VOYAGER) || X86_64)
182 depends on X86_32 && SMP
186 depends on X86_64 && SMP
191 depends on (X86_32 && !(X86_VISWS || X86_VOYAGER)) || X86_64
194 config X86_BIOS_REBOOT
196 depends on !X86_VISWS && !X86_VOYAGER
199 config X86_TRAMPOLINE
201 depends on X86_SMP || (X86_VOYAGER && SMP) || (64BIT && ACPI_SLEEP)
206 source "init/Kconfig"
208 menu "Processor type and features"
210 source "kernel/time/Kconfig"
213 bool "Symmetric multi-processing support"
215 This enables support for systems with more than one CPU. If you have
216 a system with only one CPU, like most personal computers, say N. If
217 you have a system with more than one CPU, say Y.
219 If you say N here, the kernel will run on single and multiprocessor
220 machines, but will use only one CPU of a multiprocessor machine. If
221 you say Y here, the kernel will run on many, but not all,
222 singleprocessor machines. On a singleprocessor machine, the kernel
223 will run faster if you say N here.
225 Note that if you say Y here and choose architecture "586" or
226 "Pentium" under "Processor family", the kernel will not work on 486
227 architectures. Similarly, multiprocessor kernels for the "PPro"
228 architecture may not work on all Pentium based boards.
230 People using multiprocessor machines who say Y here should also say
231 Y to "Enhanced Real Time Clock Support", below. The "Advanced Power
232 Management" code will be disabled if you say Y here.
234 See also <file:Documentation/i386/IO-APIC.txt>,
235 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
236 <http://www.tldp.org/docs.html#howto>.
238 If you don't know what to do here, say N.
241 prompt "Subarchitecture Type"
247 Choose this option if your computer is a standard PC or compatible.
253 Select this for an AMD Elan processor.
255 Do not use this option for K6/Athlon/Opteron processors!
257 If unsure, choose "PC-compatible" instead.
261 depends on X86_32 && (SMP || BROKEN)
263 Voyager is an MCA-based 32-way capable SMP architecture proprietary
264 to NCR Corp. Machine classes 345x/35xx/4100/51xx are Voyager-based.
268 If you do not specifically know you have a Voyager based machine,
269 say N here, otherwise the kernel you build will not be bootable.
272 bool "NUMAQ (IBM/Sequent)"
273 depends on SMP && X86_32
276 This option is used for getting Linux to run on a (IBM/Sequent) NUMA
277 multiquad box. This changes the way that processors are bootstrapped,
278 and uses Clustered Logical APIC addressing mode instead of Flat Logical.
279 You will need a new lynxer.elf file to flash your firmware with - send
280 email to <Martin.Bligh@us.ibm.com>.
283 bool "Summit/EXA (IBM x440)"
284 depends on X86_32 && SMP
286 This option is needed for IBM systems that use the Summit/EXA chipset.
287 In particular, it is needed for the x440.
289 If you don't have one of these computers, you should say N here.
290 If you want to build a NUMA kernel, you must select ACPI.
293 bool "Support for other sub-arch SMP systems with more than 8 CPUs"
294 depends on X86_32 && SMP
296 This option is needed for the systems that have more than 8 CPUs
297 and if the system is not of any sub-arch type above.
299 If you don't have such a system, you should say N here.
302 bool "SGI 320/540 (Visual Workstation)"
305 The SGI Visual Workstation series is an IA32-based workstation
306 based on SGI systems chips with some legacy PC hardware attached.
308 Say Y here to create a kernel to run on the SGI 320 or 540.
310 A kernel compiled for the Visual Workstation will not run on PCs
311 and vice versa. See <file:Documentation/sgi-visws.txt> for details.
313 config X86_GENERICARCH
314 bool "Generic architecture (Summit, bigsmp, ES7000, default)"
317 This option compiles in the Summit, bigsmp, ES7000, default subarchitectures.
318 It is intended for a generic binary kernel.
319 If you want a NUMA kernel, select ACPI. We need SRAT for NUMA.
322 bool "Support for Unisys ES7000 IA32 series"
323 depends on X86_32 && SMP
325 Support for Unisys ES7000 systems. Say 'Y' here if this kernel is
326 supposed to run on an IA32-based Unisys ES7000 system.
327 Only choose this option if you have such a system, otherwise you
331 bool "RDC R-321x SoC"
334 select X86_REBOOTFIXUPS
340 This option is needed for RDC R-321x system-on-chip, also known
342 If you don't have one of these chips, you should say N here.
345 bool "Support for ScaleMP vSMP"
349 Support for ScaleMP vSMP systems. Say 'Y' here if this kernel is
350 supposed to run on these EM64T-based machines. Only choose this option
351 if you have one of these machines.
355 config SCHED_NO_NO_OMIT_FRAME_POINTER
357 prompt "Single-depth WCHAN output"
360 Calculate simpler /proc/<PID>/wchan values. If this option
361 is disabled then wchan values will recurse back to the
362 caller function. This provides more accurate wchan values,
363 at the expense of slightly more scheduling overhead.
365 If in doubt, say "Y".
367 menuconfig PARAVIRT_GUEST
368 bool "Paravirtualized guest support"
370 Say Y here to get to see options related to running Linux under
371 various hypervisors. This option alone does not add any kernel code.
373 If you say N, all options in this submenu will be skipped and disabled.
377 source "arch/x86/xen/Kconfig"
380 bool "VMI Guest support"
383 depends on !(X86_VISWS || X86_VOYAGER)
385 VMI provides a paravirtualized interface to the VMware ESX server
386 (it could be used by other hypervisors in theory too, but is not
387 at the moment), by linking the kernel to a GPL-ed ROM module
388 provided by the hypervisor.
391 bool "KVM paravirtualized clock"
393 depends on !(X86_VISWS || X86_VOYAGER)
395 Turning on this option will allow you to run a paravirtualized clock
396 when running over the KVM hypervisor. Instead of relying on a PIT
397 (or probably other) emulation by the underlying device model, the host
398 provides the guest with timing infrastructure such as time of day, and
402 bool "KVM Guest support"
404 depends on !(X86_VISWS || X86_VOYAGER)
406 This option enables various optimizations for running under the KVM
409 source "arch/x86/lguest/Kconfig"
412 bool "Enable paravirtualization code"
413 depends on !(X86_VISWS || X86_VOYAGER)
415 This changes the kernel so it can modify itself when it is run
416 under a hypervisor, potentially improving performance significantly
417 over full virtualization. However, when run without a hypervisor
418 the kernel is theoretically slower and slightly larger.
427 This option adds a kernel parameter 'memtest', which allows memtest
429 memtest=0, mean disabled; -- default
430 memtest=1, mean do 1 test pattern;
432 memtest=4, mean do 4 test patterns.
433 If you are unsure how to answer this question, answer Y.
437 depends on X86_32 && ACPI && NUMA && (X86_SUMMIT || X86_GENERICARCH)
440 config HAVE_ARCH_PARSE_SRAT
444 config X86_SUMMIT_NUMA
446 depends on X86_32 && NUMA && (X86_SUMMIT || X86_GENERICARCH)
448 config X86_CYCLONE_TIMER
450 depends on X86_32 && X86_SUMMIT || X86_GENERICARCH
452 config ES7000_CLUSTERED_APIC
454 depends on SMP && X86_ES7000 && MPENTIUMIII
456 source "arch/x86/Kconfig.cpu"
460 prompt "HPET Timer Support" if X86_32
462 Use the IA-PC HPET (High Precision Event Timer) to manage
463 time in preference to the PIT and RTC, if a HPET is
465 HPET is the next generation timer replacing legacy 8254s.
466 The HPET provides a stable time base on SMP
467 systems, unlike the TSC, but it is more expensive to access,
468 as it is off-chip. You can find the HPET spec at
469 <http://www.intel.com/hardwaredesign/hpetspec.htm>.
471 You can safely choose Y here. However, HPET will only be
472 activated if the platform and the BIOS support this feature.
473 Otherwise the 8254 will be used for timing services.
475 Choose N to continue using the legacy 8254 timer.
477 config HPET_EMULATE_RTC
479 depends on HPET_TIMER && (RTC=y || RTC=m || RTC_DRV_CMOS=m || RTC_DRV_CMOS=y)
481 # Mark as embedded because too many people got it wrong.
482 # The code disables itself when not needed.
485 bool "Enable DMI scanning" if EMBEDDED
487 Enabled scanning of DMI to identify machine quirks. Say Y
488 here unless you have verified that your setup is not
489 affected by entries in the DMI blacklist. Required by PNP
493 bool "GART IOMMU support" if EMBEDDED
497 depends on X86_64 && PCI
499 Support for full DMA access of devices with 32bit memory access only
500 on systems with more than 3GB. This is usually needed for USB,
501 sound, many IDE/SATA chipsets and some other devices.
502 Provides a driver for the AMD Athlon64/Opteron/Turion/Sempron GART
503 based hardware IOMMU and a software bounce buffer based IOMMU used
504 on Intel systems and as fallback.
505 The code is only active when needed (enough memory and limited
506 device) unless CONFIG_IOMMU_DEBUG or iommu=force is specified
510 bool "IBM Calgary IOMMU support"
512 depends on X86_64 && PCI && EXPERIMENTAL
514 Support for hardware IOMMUs in IBM's xSeries x366 and x460
515 systems. Needed to run systems with more than 3GB of memory
516 properly with 32-bit PCI devices that do not support DAC
517 (Double Address Cycle). Calgary also supports bus level
518 isolation, where all DMAs pass through the IOMMU. This
519 prevents them from going anywhere except their intended
520 destination. This catches hard-to-find kernel bugs and
521 mis-behaving drivers and devices that do not use the DMA-API
522 properly to set up their DMA buffers. The IOMMU can be
523 turned off at boot time with the iommu=off parameter.
524 Normally the kernel will make the right choice by itself.
527 config CALGARY_IOMMU_ENABLED_BY_DEFAULT
529 prompt "Should Calgary be enabled by default?"
530 depends on CALGARY_IOMMU
532 Should Calgary be enabled by default? if you choose 'y', Calgary
533 will be used (if it exists). If you choose 'n', Calgary will not be
534 used even if it exists. If you choose 'n' and would like to use
535 Calgary anyway, pass 'iommu=calgary' on the kernel command line.
538 # need this always selected by IOMMU for the VIA workaround
542 Support for software bounce buffers used on x86-64 systems
543 which don't have a hardware IOMMU (e.g. the current generation
544 of Intel's x86-64 CPUs). Using this PCI devices which can only
545 access 32-bits of memory can be used on systems with more than
546 3 GB of memory. If unsure, say Y.
549 def_bool (CALGARY_IOMMU || GART_IOMMU || SWIOTLB)
552 int "Maximum number of CPUs (2-255)"
555 default "32" if X86_NUMAQ || X86_SUMMIT || X86_BIGSMP || X86_ES7000
558 This allows you to specify the maximum number of CPUs which this
559 kernel will support. The maximum supported value is 255 and the
560 minimum value which makes sense is 2.
562 This is purely to save memory - each supported CPU adds
563 approximately eight kilobytes to the kernel image.
566 bool "SMT (Hyperthreading) scheduler support"
569 SMT scheduler support improves the CPU scheduler's decision making
570 when dealing with Intel Pentium 4 chips with HyperThreading at a
571 cost of slightly increased overhead in some places. If unsure say
576 prompt "Multi-core scheduler support"
579 Multi-core scheduler support improves the CPU scheduler's decision
580 making when dealing with multi-core CPU chips at a cost of slightly
581 increased overhead in some places. If unsure say N here.
583 source "kernel/Kconfig.preempt"
586 bool "Local APIC support on uniprocessors"
587 depends on X86_32 && !SMP && !(X86_VISWS || X86_VOYAGER || X86_GENERICARCH)
589 A local APIC (Advanced Programmable Interrupt Controller) is an
590 integrated interrupt controller in the CPU. If you have a single-CPU
591 system which has a processor with a local APIC, you can say Y here to
592 enable and use it. If you say Y here even though your machine doesn't
593 have a local APIC, then the kernel will still run with no slowdown at
594 all. The local APIC supports CPU-generated self-interrupts (timer,
595 performance counters), and the NMI watchdog which detects hard
599 bool "IO-APIC support on uniprocessors"
600 depends on X86_UP_APIC
602 An IO-APIC (I/O Advanced Programmable Interrupt Controller) is an
603 SMP-capable replacement for PC-style interrupt controllers. Most
604 SMP systems and many recent uniprocessor systems have one.
606 If you have a single-CPU system with an IO-APIC, you can say Y here
607 to use it. If you say Y here even though your machine doesn't have
608 an IO-APIC, then the kernel will still run with no slowdown at all.
610 config X86_LOCAL_APIC
612 depends on X86_64 || (X86_32 && (X86_UP_APIC || ((X86_VISWS || SMP) && !X86_VOYAGER) || X86_GENERICARCH))
616 depends on X86_64 || (X86_32 && (X86_UP_IOAPIC || (SMP && !(X86_VISWS || X86_VOYAGER)) || X86_GENERICARCH))
618 config X86_VISWS_APIC
620 depends on X86_32 && X86_VISWS
623 bool "Machine Check Exception"
624 depends on !X86_VOYAGER
626 Machine Check Exception support allows the processor to notify the
627 kernel if it detects a problem (e.g. overheating, component failure).
628 The action the kernel takes depends on the severity of the problem,
629 ranging from a warning message on the console, to halting the machine.
630 Your processor must be a Pentium or newer to support this - check the
631 flags in /proc/cpuinfo for mce. Note that some older Pentium systems
632 have a design flaw which leads to false MCE events - hence MCE is
633 disabled on all P5 processors, unless explicitly enabled with "mce"
634 as a boot argument. Similarly, if MCE is built in and creates a
635 problem on some new non-standard machine, you can boot with "nomce"
636 to disable it. MCE support simply ignores non-MCE processors like
637 the 386 and 486, so nearly everyone can say Y here.
641 prompt "Intel MCE features"
642 depends on X86_64 && X86_MCE && X86_LOCAL_APIC
644 Additional support for intel specific MCE features such as
649 prompt "AMD MCE features"
650 depends on X86_64 && X86_MCE && X86_LOCAL_APIC
652 Additional support for AMD specific MCE features such as
653 the DRAM Error Threshold.
655 config X86_MCE_NONFATAL
656 tristate "Check for non-fatal errors on AMD Athlon/Duron / Intel Pentium 4"
657 depends on X86_32 && X86_MCE
659 Enabling this feature starts a timer that triggers every 5 seconds which
660 will look at the machine check registers to see if anything happened.
661 Non-fatal problems automatically get corrected (but still logged).
662 Disable this if you don't want to see these messages.
663 Seeing the messages this option prints out may be indicative of dying
664 or out-of-spec (ie, overclocked) hardware.
665 This option only does something on certain CPUs.
666 (AMD Athlon/Duron and Intel Pentium 4)
668 config X86_MCE_P4THERMAL
669 bool "check for P4 thermal throttling interrupt."
670 depends on X86_32 && X86_MCE && (X86_UP_APIC || SMP) && !X86_VISWS
672 Enabling this feature will cause a message to be printed when the P4
673 enters thermal throttling.
676 bool "Enable VM86 support" if EMBEDDED
680 This option is required by programs like DOSEMU to run 16-bit legacy
681 code on X86 processors. It also may be needed by software like
682 XFree86 to initialize some video cards via BIOS. Disabling this
683 option saves about 6k.
686 tristate "Toshiba Laptop support"
689 This adds a driver to safely access the System Management Mode of
690 the CPU on Toshiba portables with a genuine Toshiba BIOS. It does
691 not work on models with a Phoenix BIOS. The System Management Mode
692 is used to set the BIOS and power saving options on Toshiba portables.
694 For information on utilities to make use of this driver see the
695 Toshiba Linux utilities web site at:
696 <http://www.buzzard.org.uk/toshiba/>.
698 Say Y if you intend to run this kernel on a Toshiba portable.
702 tristate "Dell laptop support"
704 This adds a driver to safely access the System Management Mode
705 of the CPU on the Dell Inspiron 8000. The System Management Mode
706 is used to read cpu temperature and cooling fan status and to
707 control the fans on the I8K portables.
709 This driver has been tested only on the Inspiron 8000 but it may
710 also work with other Dell laptops. You can force loading on other
711 models by passing the parameter `force=1' to the module. Use at
714 For information on utilities to make use of this driver see the
715 I8K Linux utilities web site at:
716 <http://people.debian.org/~dz/i8k/>
718 Say Y if you intend to run this kernel on a Dell Inspiron 8000.
721 config X86_REBOOTFIXUPS
723 prompt "Enable X86 board specific fixups for reboot"
724 depends on X86_32 && X86
726 This enables chipset and/or board specific fixups to be done
727 in order to get reboot to work correctly. This is only needed on
728 some combinations of hardware and BIOS. The symptom, for which
729 this config is intended, is when reboot ends with a stalled/hung
732 Currently, the only fixup is for the Geode machines using
733 CS5530A and CS5536 chipsets and the RDC R-321x SoC.
735 Say Y if you want to enable the fixup. Currently, it's safe to
736 enable this option even if you don't need it.
740 tristate "/dev/cpu/microcode - Intel IA32 CPU microcode support"
743 If you say Y here, you will be able to update the microcode on
744 Intel processors in the IA32 family, e.g. Pentium Pro, Pentium II,
745 Pentium III, Pentium 4, Xeon etc. You will obviously need the
746 actual microcode binary data itself which is not shipped with the
749 For latest news and information on obtaining all the required
750 ingredients for this driver, check:
751 <http://www.urbanmyth.org/microcode/>.
753 To compile this driver as a module, choose M here: the
754 module will be called microcode.
756 config MICROCODE_OLD_INTERFACE
761 tristate "/dev/cpu/*/msr - Model-specific register support"
763 This device gives privileged processes access to the x86
764 Model-Specific Registers (MSRs). It is a character device with
765 major 202 and minors 0 to 31 for /dev/cpu/0/msr to /dev/cpu/31/msr.
766 MSR accesses are directed to a specific CPU on multi-processor
770 tristate "/dev/cpu/*/cpuid - CPU information support"
772 This device gives processes access to the x86 CPUID instruction to
773 be executed on a specific processor. It is a character device
774 with major 203 and minors 0 to 31 for /dev/cpu/0/cpuid to
778 prompt "High Memory Support"
779 default HIGHMEM4G if !X86_NUMAQ
780 default HIGHMEM64G if X86_NUMAQ
785 depends on !X86_NUMAQ
787 Linux can use up to 64 Gigabytes of physical memory on x86 systems.
788 However, the address space of 32-bit x86 processors is only 4
789 Gigabytes large. That means that, if you have a large amount of
790 physical memory, not all of it can be "permanently mapped" by the
791 kernel. The physical memory that's not permanently mapped is called
794 If you are compiling a kernel which will never run on a machine with
795 more than 1 Gigabyte total physical RAM, answer "off" here (default
796 choice and suitable for most users). This will result in a "3GB/1GB"
797 split: 3GB are mapped so that each process sees a 3GB virtual memory
798 space and the remaining part of the 4GB virtual memory space is used
799 by the kernel to permanently map as much physical memory as
802 If the machine has between 1 and 4 Gigabytes physical RAM, then
805 If more than 4 Gigabytes is used then answer "64GB" here. This
806 selection turns Intel PAE (Physical Address Extension) mode on.
807 PAE implements 3-level paging on IA32 processors. PAE is fully
808 supported by Linux, PAE mode is implemented on all recent Intel
809 processors (Pentium Pro and better). NOTE: If you say "64GB" here,
810 then the kernel will not boot on CPUs that don't support PAE!
812 The actual amount of total physical memory will either be
813 auto detected or can be forced by using a kernel command line option
814 such as "mem=256M". (Try "man bootparam" or see the documentation of
815 your boot loader (lilo or loadlin) about how to pass options to the
816 kernel at boot time.)
818 If unsure, say "off".
822 depends on !X86_NUMAQ
824 Select this if you have a 32-bit processor and between 1 and 4
825 gigabytes of physical RAM.
829 depends on !M386 && !M486
832 Select this if you have a 32-bit processor and more than 4
833 gigabytes of physical RAM.
838 depends on EXPERIMENTAL
839 prompt "Memory split" if EMBEDDED
843 Select the desired split between kernel and user memory.
845 If the address range available to the kernel is less than the
846 physical memory installed, the remaining memory will be available
847 as "high memory". Accessing high memory is a little more costly
848 than low memory, as it needs to be mapped into the kernel first.
849 Note that increasing the kernel address space limits the range
850 available to user programs, making the address space there
851 tighter. Selecting anything other than the default 3G/1G split
852 will also likely make your kernel incompatible with binary-only
855 If you are not absolutely sure what you are doing, leave this
859 bool "3G/1G user/kernel split"
860 config VMSPLIT_3G_OPT
862 bool "3G/1G user/kernel split (for full 1G low memory)"
864 bool "2G/2G user/kernel split"
865 config VMSPLIT_2G_OPT
867 bool "2G/2G user/kernel split (for full 2G low memory)"
869 bool "1G/3G user/kernel split"
874 default 0xB0000000 if VMSPLIT_3G_OPT
875 default 0x80000000 if VMSPLIT_2G
876 default 0x78000000 if VMSPLIT_2G_OPT
877 default 0x40000000 if VMSPLIT_1G
883 depends on X86_32 && (HIGHMEM64G || HIGHMEM4G)
887 prompt "PAE (Physical Address Extension) Support"
888 depends on X86_32 && !HIGHMEM4G
889 select RESOURCES_64BIT
891 PAE is required for NX support, and furthermore enables
892 larger swapspace support for non-overcommit purposes. It
893 has the cost of more pagetable lookup overhead, and also
894 consumes more pagetable space per process.
896 # Common NUMA Features
898 bool "Numa Memory Allocation and Scheduler Support (EXPERIMENTAL)"
900 depends on X86_64 || (X86_32 && HIGHMEM64G && (X86_NUMAQ || (X86_SUMMIT || X86_GENERICARCH) && ACPI) && EXPERIMENTAL)
902 default y if (X86_NUMAQ || X86_SUMMIT)
904 Enable NUMA (Non Uniform Memory Access) support.
905 The kernel will try to allocate memory used by a CPU on the
906 local memory controller of the CPU and add some more
907 NUMA awareness to the kernel.
909 For i386 this is currently highly experimental and should be only
910 used for kernel development. It might also cause boot failures.
911 For x86_64 this is recommended on all multiprocessor Opteron systems.
912 If the system is EM64T, you should say N unless your system is
915 comment "NUMA (Summit) requires SMP, 64GB highmem support, ACPI"
916 depends on X86_32 && X86_SUMMIT && (!HIGHMEM64G || !ACPI)
920 prompt "Old style AMD Opteron NUMA detection"
921 depends on X86_64 && NUMA && PCI
923 Enable K8 NUMA node topology detection. You should say Y here if
924 you have a multi processor AMD K8 system. This uses an old
925 method to read the NUMA configuration directly from the builtin
926 Northbridge of Opteron. It is recommended to use X86_64_ACPI_NUMA
927 instead, which also takes priority if both are compiled in.
929 config X86_64_ACPI_NUMA
931 prompt "ACPI NUMA detection"
932 depends on X86_64 && NUMA && ACPI && PCI
935 Enable ACPI SRAT based node topology detection.
937 # Some NUMA nodes have memory ranges that span
938 # other nodes. Even though a pfn is valid and
939 # between a node's start and end pfns, it may not
940 # reside on that node. See memmap_init_zone()
942 config NODES_SPAN_OTHER_NODES
944 depends on X86_64_ACPI_NUMA
947 bool "NUMA emulation"
948 depends on X86_64 && NUMA
950 Enable NUMA emulation. A flat machine will be split
951 into virtual nodes when booted with "numa=fake=N", where N is the
952 number of nodes. This is only useful for debugging.
955 int "Max num nodes shift(1-15)"
957 default "6" if X86_64
958 default "4" if X86_NUMAQ
960 depends on NEED_MULTIPLE_NODES
962 config HAVE_ARCH_BOOTMEM_NODE
964 depends on X86_32 && NUMA
966 config ARCH_HAVE_MEMORY_PRESENT
968 depends on X86_32 && DISCONTIGMEM
970 config NEED_NODE_MEMMAP_SIZE
972 depends on X86_32 && (DISCONTIGMEM || SPARSEMEM)
974 config HAVE_ARCH_ALLOC_REMAP
976 depends on X86_32 && NUMA
978 config ARCH_FLATMEM_ENABLE
980 depends on X86_32 && ARCH_SELECT_MEMORY_MODEL && X86_PC && !NUMA
982 config ARCH_DISCONTIGMEM_ENABLE
984 depends on NUMA && X86_32
986 config ARCH_DISCONTIGMEM_DEFAULT
988 depends on NUMA && X86_32
990 config ARCH_SPARSEMEM_DEFAULT
994 config ARCH_SPARSEMEM_ENABLE
996 depends on X86_64 || NUMA || (EXPERIMENTAL && X86_PC)
997 select SPARSEMEM_STATIC if X86_32
998 select SPARSEMEM_VMEMMAP_ENABLE if X86_64
1000 config ARCH_SELECT_MEMORY_MODEL
1002 depends on ARCH_SPARSEMEM_ENABLE
1004 config ARCH_MEMORY_PROBE
1006 depends on MEMORY_HOTPLUG
1011 bool "Allocate 3rd-level pagetables from highmem"
1012 depends on X86_32 && (HIGHMEM4G || HIGHMEM64G)
1014 The VM uses one page table entry for each page of physical memory.
1015 For systems with a lot of RAM, this can be wasteful of precious
1016 low memory. Setting this option will put user-space page table
1017 entries in high memory.
1019 config MATH_EMULATION
1021 prompt "Math emulation" if X86_32
1023 Linux can emulate a math coprocessor (used for floating point
1024 operations) if you don't have one. 486DX and Pentium processors have
1025 a math coprocessor built in, 486SX and 386 do not, unless you added
1026 a 487DX or 387, respectively. (The messages during boot time can
1027 give you some hints here ["man dmesg"].) Everyone needs either a
1028 coprocessor or this emulation.
1030 If you don't have a math coprocessor, you need to say Y here; if you
1031 say Y here even though you have a coprocessor, the coprocessor will
1032 be used nevertheless. (This behavior can be changed with the kernel
1033 command line option "no387", which comes handy if your coprocessor
1034 is broken. Try "man bootparam" or see the documentation of your boot
1035 loader (lilo or loadlin) about how to pass options to the kernel at
1036 boot time.) This means that it is a good idea to say Y here if you
1037 intend to use this kernel on different machines.
1039 More information about the internals of the Linux math coprocessor
1040 emulation can be found in <file:arch/x86/math-emu/README>.
1042 If you are not sure, say Y; apart from resulting in a 66 KB bigger
1043 kernel, it won't hurt.
1046 bool "MTRR (Memory Type Range Register) support"
1048 On Intel P6 family processors (Pentium Pro, Pentium II and later)
1049 the Memory Type Range Registers (MTRRs) may be used to control
1050 processor access to memory ranges. This is most useful if you have
1051 a video (VGA) card on a PCI or AGP bus. Enabling write-combining
1052 allows bus write transfers to be combined into a larger transfer
1053 before bursting over the PCI/AGP bus. This can increase performance
1054 of image write operations 2.5 times or more. Saying Y here creates a
1055 /proc/mtrr file which may be used to manipulate your processor's
1056 MTRRs. Typically the X server should use this.
1058 This code has a reasonably generic interface so that similar
1059 control registers on other processors can be easily supported
1062 The Cyrix 6x86, 6x86MX and M II processors have Address Range
1063 Registers (ARRs) which provide a similar functionality to MTRRs. For
1064 these, the ARRs are used to emulate the MTRRs.
1065 The AMD K6-2 (stepping 8 and above) and K6-3 processors have two
1066 MTRRs. The Centaur C6 (WinChip) has 8 MCRs, allowing
1067 write-combining. All of these processors are supported by this code
1068 and it makes sense to say Y here if you have one of them.
1070 Saying Y here also fixes a problem with buggy SMP BIOSes which only
1071 set the MTRRs for the boot CPU and not for the secondary CPUs. This
1072 can lead to all sorts of problems, so it's good to say Y here.
1074 You can safely say Y even if your machine doesn't have MTRRs, you'll
1075 just add about 9 KB to your kernel.
1077 See <file:Documentation/mtrr.txt> for more information.
1081 prompt "x86 PAT support"
1084 Use PAT attributes to setup page level cache control.
1086 PATs are the modern equivalents of MTRRs and are much more
1087 flexible than MTRRs.
1089 Say N here if you see bootup problems (boot crash, boot hang,
1090 spontaneous reboots) or a non-working video driver.
1096 prompt "EFI runtime service support"
1099 This enables the kernel to use EFI runtime services that are
1100 available (such as the EFI variable services).
1102 This option is only useful on systems that have EFI firmware.
1103 In addition, you should use the latest ELILO loader available
1104 at <http://elilo.sourceforge.net> in order to take advantage
1105 of EFI runtime services. However, even with this option, the
1106 resultant kernel should continue to boot on existing non-EFI
1111 prompt "Enable kernel irq balancing"
1112 depends on X86_32 && SMP && X86_IO_APIC
1114 The default yes will allow the kernel to do irq load balancing.
1115 Saying no will keep the kernel from doing irq load balancing.
1119 prompt "Enable seccomp to safely compute untrusted bytecode"
1122 This kernel feature is useful for number crunching applications
1123 that may need to compute untrusted bytecode during their
1124 execution. By using pipes or other transports made available to
1125 the process as file descriptors supporting the read/write
1126 syscalls, it's possible to isolate those applications in
1127 their own address space using seccomp. Once seccomp is
1128 enabled via /proc/<pid>/seccomp, it cannot be disabled
1129 and the task is only allowed to execute a few safe syscalls
1130 defined by each seccomp mode.
1132 If unsure, say Y. Only embedded should say N here.
1134 config CC_STACKPROTECTOR
1135 bool "Enable -fstack-protector buffer overflow detection (EXPERIMENTAL)"
1136 depends on X86_64 && EXPERIMENTAL && BROKEN
1138 This option turns on the -fstack-protector GCC feature. This
1139 feature puts, at the beginning of critical functions, a canary
1140 value on the stack just before the return address, and validates
1141 the value just before actually returning. Stack based buffer
1142 overflows (that need to overwrite this return address) now also
1143 overwrite the canary, which gets detected and the attack is then
1144 neutralized via a kernel panic.
1146 This feature requires gcc version 4.2 or above, or a distribution
1147 gcc with the feature backported. Older versions are automatically
1148 detected and for those versions, this configuration option is ignored.
1150 config CC_STACKPROTECTOR_ALL
1151 bool "Use stack-protector for all functions"
1152 depends on CC_STACKPROTECTOR
1154 Normally, GCC only inserts the canary value protection for
1155 functions that use large-ish on-stack buffers. By enabling
1156 this option, GCC will be asked to do this for ALL functions.
1158 source kernel/Kconfig.hz
1161 bool "kexec system call"
1162 depends on X86_BIOS_REBOOT
1164 kexec is a system call that implements the ability to shutdown your
1165 current kernel, and to start another kernel. It is like a reboot
1166 but it is independent of the system firmware. And like a reboot
1167 you can start any kernel with it, not just Linux.
1169 The name comes from the similarity to the exec system call.
1171 It is an ongoing process to be certain the hardware in a machine
1172 is properly shutdown, so do not be surprised if this code does not
1173 initially work for you. It may help to enable device hotplugging
1174 support. As of this writing the exact hardware interface is
1175 strongly in flux, so no good recommendation can be made.
1178 bool "kernel crash dumps (EXPERIMENTAL)"
1179 depends on EXPERIMENTAL
1180 depends on X86_64 || (X86_32 && HIGHMEM)
1182 Generate crash dump after being started by kexec.
1183 This should be normally only set in special crash dump kernels
1184 which are loaded in the main kernel with kexec-tools into
1185 a specially reserved region and then later executed after
1186 a crash by kdump/kexec. The crash dump kernel must be compiled
1187 to a memory address not used by the main kernel or BIOS using
1188 PHYSICAL_START, or it must be built as a relocatable image
1189 (CONFIG_RELOCATABLE=y).
1190 For more details see Documentation/kdump/kdump.txt
1192 config PHYSICAL_START
1193 hex "Physical address where the kernel is loaded" if (EMBEDDED || CRASH_DUMP)
1194 default "0x1000000" if X86_NUMAQ
1195 default "0x200000" if X86_64
1198 This gives the physical address where the kernel is loaded.
1200 If kernel is a not relocatable (CONFIG_RELOCATABLE=n) then
1201 bzImage will decompress itself to above physical address and
1202 run from there. Otherwise, bzImage will run from the address where
1203 it has been loaded by the boot loader and will ignore above physical
1206 In normal kdump cases one does not have to set/change this option
1207 as now bzImage can be compiled as a completely relocatable image
1208 (CONFIG_RELOCATABLE=y) and be used to load and run from a different
1209 address. This option is mainly useful for the folks who don't want
1210 to use a bzImage for capturing the crash dump and want to use a
1211 vmlinux instead. vmlinux is not relocatable hence a kernel needs
1212 to be specifically compiled to run from a specific memory area
1213 (normally a reserved region) and this option comes handy.
1215 So if you are using bzImage for capturing the crash dump, leave
1216 the value here unchanged to 0x100000 and set CONFIG_RELOCATABLE=y.
1217 Otherwise if you plan to use vmlinux for capturing the crash dump
1218 change this value to start of the reserved region (Typically 16MB
1219 0x1000000). In other words, it can be set based on the "X" value as
1220 specified in the "crashkernel=YM@XM" command line boot parameter
1221 passed to the panic-ed kernel. Typically this parameter is set as
1222 crashkernel=64M@16M. Please take a look at
1223 Documentation/kdump/kdump.txt for more details about crash dumps.
1225 Usage of bzImage for capturing the crash dump is recommended as
1226 one does not have to build two kernels. Same kernel can be used
1227 as production kernel and capture kernel. Above option should have
1228 gone away after relocatable bzImage support is introduced. But it
1229 is present because there are users out there who continue to use
1230 vmlinux for dump capture. This option should go away down the
1233 Don't change this unless you know what you are doing.
1236 bool "Build a relocatable kernel (EXPERIMENTAL)"
1237 depends on EXPERIMENTAL
1239 This builds a kernel image that retains relocation information
1240 so it can be loaded someplace besides the default 1MB.
1241 The relocations tend to make the kernel binary about 10% larger,
1242 but are discarded at runtime.
1244 One use is for the kexec on panic case where the recovery kernel
1245 must live at a different physical address than the primary
1248 Note: If CONFIG_RELOCATABLE=y, then the kernel runs from the address
1249 it has been loaded at and the compile time physical address
1250 (CONFIG_PHYSICAL_START) is ignored.
1252 config PHYSICAL_ALIGN
1254 prompt "Alignment value to which kernel should be aligned" if X86_32
1255 default "0x100000" if X86_32
1256 default "0x200000" if X86_64
1257 range 0x2000 0x400000
1259 This value puts the alignment restrictions on physical address
1260 where kernel is loaded and run from. Kernel is compiled for an
1261 address which meets above alignment restriction.
1263 If bootloader loads the kernel at a non-aligned address and
1264 CONFIG_RELOCATABLE is set, kernel will move itself to nearest
1265 address aligned to above value and run from there.
1267 If bootloader loads the kernel at a non-aligned address and
1268 CONFIG_RELOCATABLE is not set, kernel will ignore the run time
1269 load address and decompress itself to the address it has been
1270 compiled for and run from there. The address for which kernel is
1271 compiled already meets above alignment restrictions. Hence the
1272 end result is that kernel runs from a physical address meeting
1273 above alignment restrictions.
1275 Don't change this unless you know what you are doing.
1278 bool "Support for suspend on SMP and hot-pluggable CPUs (EXPERIMENTAL)"
1279 depends on SMP && HOTPLUG && EXPERIMENTAL && !X86_VOYAGER
1281 Say Y here to experiment with turning CPUs off and on, and to
1282 enable suspend on SMP systems. CPUs can be controlled through
1283 /sys/devices/system/cpu.
1284 Say N if you want to disable CPU hotplug and don't need to
1289 prompt "Compat VDSO support"
1290 depends on X86_32 || IA32_EMULATION
1292 Map the 32-bit VDSO to the predictable old-style address too.
1294 Say N here if you are running a sufficiently recent glibc
1295 version (2.3.3 or later), to remove the high-mapped
1296 VDSO mapping and to exclusively use the randomized VDSO.
1302 config ARCH_ENABLE_MEMORY_HOTPLUG
1304 depends on X86_64 || (X86_32 && HIGHMEM)
1306 config HAVE_ARCH_EARLY_PFN_TO_NID
1310 menu "Power management options"
1311 depends on !X86_VOYAGER
1313 config ARCH_HIBERNATION_HEADER
1315 depends on X86_64 && HIBERNATION
1317 source "kernel/power/Kconfig"
1319 source "drivers/acpi/Kconfig"
1324 depends on APM || APM_MODULE
1327 tristate "APM (Advanced Power Management) BIOS support"
1328 depends on X86_32 && PM_SLEEP && !X86_VISWS
1330 APM is a BIOS specification for saving power using several different
1331 techniques. This is mostly useful for battery powered laptops with
1332 APM compliant BIOSes. If you say Y here, the system time will be
1333 reset after a RESUME operation, the /proc/apm device will provide
1334 battery status information, and user-space programs will receive
1335 notification of APM "events" (e.g. battery status change).
1337 If you select "Y" here, you can disable actual use of the APM
1338 BIOS by passing the "apm=off" option to the kernel at boot time.
1340 Note that the APM support is almost completely disabled for
1341 machines with more than one CPU.
1343 In order to use APM, you will need supporting software. For location
1344 and more information, read <file:Documentation/power/pm.txt> and the
1345 Battery Powered Linux mini-HOWTO, available from
1346 <http://www.tldp.org/docs.html#howto>.
1348 This driver does not spin down disk drives (see the hdparm(8)
1349 manpage ("man 8 hdparm") for that), and it doesn't turn off
1350 VESA-compliant "green" monitors.
1352 This driver does not support the TI 4000M TravelMate and the ACER
1353 486/DX4/75 because they don't have compliant BIOSes. Many "green"
1354 desktop machines also don't have compliant BIOSes, and this driver
1355 may cause those machines to panic during the boot phase.
1357 Generally, if you don't have a battery in your machine, there isn't
1358 much point in using this driver and you should say N. If you get
1359 random kernel OOPSes or reboots that don't seem to be related to
1360 anything, try disabling/enabling this option (or disabling/enabling
1363 Some other things you should try when experiencing seemingly random,
1366 1) make sure that you have enough swap space and that it is
1368 2) pass the "no-hlt" option to the kernel
1369 3) switch on floating point emulation in the kernel and pass
1370 the "no387" option to the kernel
1371 4) pass the "floppy=nodma" option to the kernel
1372 5) pass the "mem=4M" option to the kernel (thereby disabling
1373 all but the first 4 MB of RAM)
1374 6) make sure that the CPU is not over clocked.
1375 7) read the sig11 FAQ at <http://www.bitwizard.nl/sig11/>
1376 8) disable the cache from your BIOS settings
1377 9) install a fan for the video card or exchange video RAM
1378 10) install a better fan for the CPU
1379 11) exchange RAM chips
1380 12) exchange the motherboard.
1382 To compile this driver as a module, choose M here: the
1383 module will be called apm.
1387 config APM_IGNORE_USER_SUSPEND
1388 bool "Ignore USER SUSPEND"
1390 This option will ignore USER SUSPEND requests. On machines with a
1391 compliant APM BIOS, you want to say N. However, on the NEC Versa M
1392 series notebooks, it is necessary to say Y because of a BIOS bug.
1394 config APM_DO_ENABLE
1395 bool "Enable PM at boot time"
1397 Enable APM features at boot time. From page 36 of the APM BIOS
1398 specification: "When disabled, the APM BIOS does not automatically
1399 power manage devices, enter the Standby State, enter the Suspend
1400 State, or take power saving steps in response to CPU Idle calls."
1401 This driver will make CPU Idle calls when Linux is idle (unless this
1402 feature is turned off -- see "Do CPU IDLE calls", below). This
1403 should always save battery power, but more complicated APM features
1404 will be dependent on your BIOS implementation. You may need to turn
1405 this option off if your computer hangs at boot time when using APM
1406 support, or if it beeps continuously instead of suspending. Turn
1407 this off if you have a NEC UltraLite Versa 33/C or a Toshiba
1408 T400CDT. This is off by default since most machines do fine without
1412 bool "Make CPU Idle calls when idle"
1414 Enable calls to APM CPU Idle/CPU Busy inside the kernel's idle loop.
1415 On some machines, this can activate improved power savings, such as
1416 a slowed CPU clock rate, when the machine is idle. These idle calls
1417 are made after the idle loop has run for some length of time (e.g.,
1418 333 mS). On some machines, this will cause a hang at boot time or
1419 whenever the CPU becomes idle. (On machines with more than one CPU,
1420 this option does nothing.)
1422 config APM_DISPLAY_BLANK
1423 bool "Enable console blanking using APM"
1425 Enable console blanking using the APM. Some laptops can use this to
1426 turn off the LCD backlight when the screen blanker of the Linux
1427 virtual console blanks the screen. Note that this is only used by
1428 the virtual console screen blanker, and won't turn off the backlight
1429 when using the X Window system. This also doesn't have anything to
1430 do with your VESA-compliant power-saving monitor. Further, this
1431 option doesn't work for all laptops -- it might not turn off your
1432 backlight at all, or it might print a lot of errors to the console,
1433 especially if you are using gpm.
1435 config APM_ALLOW_INTS
1436 bool "Allow interrupts during APM BIOS calls"
1438 Normally we disable external interrupts while we are making calls to
1439 the APM BIOS as a measure to lessen the effects of a badly behaving
1440 BIOS implementation. The BIOS should reenable interrupts if it
1441 needs to. Unfortunately, some BIOSes do not -- especially those in
1442 many of the newer IBM Thinkpads. If you experience hangs when you
1443 suspend, try setting this to Y. Otherwise, say N.
1445 config APM_REAL_MODE_POWER_OFF
1446 bool "Use real mode APM BIOS call to power off"
1448 Use real mode APM BIOS calls to switch off the computer. This is
1449 a work-around for a number of buggy BIOSes. Switch this option on if
1450 your computer crashes instead of powering off properly.
1454 source "arch/x86/kernel/cpu/cpufreq/Kconfig"
1456 source "drivers/cpuidle/Kconfig"
1461 menu "Bus options (PCI etc.)"
1464 bool "PCI support" if !X86_VISWS && !X86_VSMP
1465 depends on !X86_VOYAGER
1467 select ARCH_SUPPORTS_MSI if (X86_LOCAL_APIC && X86_IO_APIC)
1469 Find out whether you have a PCI motherboard. PCI is the name of a
1470 bus system, i.e. the way the CPU talks to the other stuff inside
1471 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
1472 VESA. If you have PCI, say Y, otherwise N.
1475 prompt "PCI access mode"
1476 depends on X86_32 && PCI && !X86_VISWS
1479 On PCI systems, the BIOS can be used to detect the PCI devices and
1480 determine their configuration. However, some old PCI motherboards
1481 have BIOS bugs and may crash if this is done. Also, some embedded
1482 PCI-based systems don't have any BIOS at all. Linux can also try to
1483 detect the PCI hardware directly without using the BIOS.
1485 With this option, you can specify how Linux should detect the
1486 PCI devices. If you choose "BIOS", the BIOS will be used,
1487 if you choose "Direct", the BIOS won't be used, and if you
1488 choose "MMConfig", then PCI Express MMCONFIG will be used.
1489 If you choose "Any", the kernel will try MMCONFIG, then the
1490 direct access method and falls back to the BIOS if that doesn't
1491 work. If unsure, go with the default, which is "Any".
1496 config PCI_GOMMCONFIG
1513 depends on X86_32 && !X86_VISWS && PCI && (PCI_GOBIOS || PCI_GOANY)
1515 # x86-64 doesn't support PCI BIOS access from long mode so always go direct.
1518 depends on PCI && (X86_64 || (PCI_GODIRECT || PCI_GOANY || PCI_GOOLPC) || X86_VISWS)
1522 depends on X86_32 && PCI && ACPI && (PCI_GOMMCONFIG || PCI_GOANY)
1526 depends on PCI && PCI_GOOLPC
1534 bool "Support mmconfig PCI config space access"
1535 depends on X86_64 && PCI && ACPI
1538 bool "Support for DMA Remapping Devices (EXPERIMENTAL)"
1539 depends on X86_64 && PCI_MSI && ACPI && EXPERIMENTAL
1541 DMA remapping (DMAR) devices support enables independent address
1542 translations for Direct Memory Access (DMA) from devices.
1543 These DMA remapping devices are reported via ACPI tables
1544 and include PCI device scope covered by these DMA
1549 prompt "Support for Graphics workaround"
1552 Current Graphics drivers tend to use physical address
1553 for DMA and avoid using DMA APIs. Setting this config
1554 option permits the IOMMU driver to set a unity map for
1555 all the OS-visible memory. Hence the driver can continue
1556 to use physical addresses for DMA.
1558 config DMAR_FLOPPY_WA
1562 Floppy disk drivers are know to bypass DMA API calls
1563 thereby failing to work when IOMMU is enabled. This
1564 workaround will setup a 1:1 mapping for the first
1565 16M to make floppy (an ISA device) work.
1567 source "drivers/pci/pcie/Kconfig"
1569 source "drivers/pci/Kconfig"
1571 # x86_64 have no ISA slots, but do have ISA-style DMA.
1579 depends on !(X86_VOYAGER || X86_VISWS)
1581 Find out whether you have ISA slots on your motherboard. ISA is the
1582 name of a bus system, i.e. the way the CPU talks to the other stuff
1583 inside your box. Other bus systems are PCI, EISA, MicroChannel
1584 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
1585 newer boards don't support it. If you have ISA, say Y, otherwise N.
1591 The Extended Industry Standard Architecture (EISA) bus was
1592 developed as an open alternative to the IBM MicroChannel bus.
1594 The EISA bus provided some of the features of the IBM MicroChannel
1595 bus while maintaining backward compatibility with cards made for
1596 the older ISA bus. The EISA bus saw limited use between 1988 and
1597 1995 when it was made obsolete by the PCI bus.
1599 Say Y here if you are building a kernel for an EISA-based machine.
1603 source "drivers/eisa/Kconfig"
1606 bool "MCA support" if !(X86_VISWS || X86_VOYAGER)
1607 default y if X86_VOYAGER
1609 MicroChannel Architecture is found in some IBM PS/2 machines and
1610 laptops. It is a bus system similar to PCI or ISA. See
1611 <file:Documentation/mca.txt> (and especially the web page given
1612 there) before attempting to build an MCA bus kernel.
1614 source "drivers/mca/Kconfig"
1617 tristate "NatSemi SCx200 support"
1618 depends on !X86_VOYAGER
1620 This provides basic support for National Semiconductor's
1621 (now AMD's) Geode processors. The driver probes for the
1622 PCI-IDs of several on-chip devices, so its a good dependency
1623 for other scx200_* drivers.
1625 If compiled as a module, the driver is named scx200.
1627 config SCx200HR_TIMER
1628 tristate "NatSemi SCx200 27MHz High-Resolution Timer Support"
1629 depends on SCx200 && GENERIC_TIME
1632 This driver provides a clocksource built upon the on-chip
1633 27MHz high-resolution timer. Its also a workaround for
1634 NSC Geode SC-1100's buggy TSC, which loses time when the
1635 processor goes idle (as is done by the scheduler). The
1636 other workaround is idle=poll boot option.
1638 config GEODE_MFGPT_TIMER
1640 prompt "Geode Multi-Function General Purpose Timer (MFGPT) events"
1641 depends on MGEODE_LX && GENERIC_TIME && GENERIC_CLOCKEVENTS
1643 This driver provides a clock event source based on the MFGPT
1644 timer(s) in the CS5535 and CS5536 companion chip for the geode.
1645 MFGPTs have a better resolution and max interval than the
1646 generic PIT, and are suitable for use as high-res timers.
1649 bool "One Laptop Per Child support"
1652 Add support for detecting the unique features of the OLPC
1659 depends on AGP_AMD64 || (X86_64 && (GART_IOMMU || (PCI && NUMA)))
1661 source "drivers/pcmcia/Kconfig"
1663 source "drivers/pci/hotplug/Kconfig"
1668 menu "Executable file formats / Emulations"
1670 source "fs/Kconfig.binfmt"
1672 config IA32_EMULATION
1673 bool "IA32 Emulation"
1675 select COMPAT_BINFMT_ELF
1677 Include code to run 32-bit programs under a 64-bit kernel. You should
1678 likely turn this on, unless you're 100% sure that you don't have any
1679 32-bit programs left.
1682 tristate "IA32 a.out support"
1683 depends on IA32_EMULATION && ARCH_SUPPORTS_AOUT
1685 Support old a.out binaries in the 32bit emulation.
1689 depends on IA32_EMULATION
1691 config COMPAT_FOR_U64_ALIGNMENT
1695 config SYSVIPC_COMPAT
1697 depends on X86_64 && COMPAT && SYSVIPC
1702 source "net/Kconfig"
1704 source "drivers/Kconfig"
1706 source "drivers/firmware/Kconfig"
1710 source "arch/x86/Kconfig.debug"
1712 source "security/Kconfig"
1714 source "crypto/Kconfig"
1716 source "arch/x86/kvm/Kconfig"
1718 source "lib/Kconfig"
projects / linux-2.6 / blob