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
339 This option is needed for RDC R-321x system-on-chip, also known
341 If you don't have one of these chips, you should say N here.
344 bool "Support for ScaleMP vSMP"
348 Support for ScaleMP vSMP systems. Say 'Y' here if this kernel is
349 supposed to run on these EM64T-based machines. Only choose this option
350 if you have one of these machines.
354 config SCHED_NO_NO_OMIT_FRAME_POINTER
356 prompt "Single-depth WCHAN output"
359 Calculate simpler /proc/<PID>/wchan values. If this option
360 is disabled then wchan values will recurse back to the
361 caller function. This provides more accurate wchan values,
362 at the expense of slightly more scheduling overhead.
364 If in doubt, say "Y".
366 menuconfig PARAVIRT_GUEST
367 bool "Paravirtualized guest support"
369 Say Y here to get to see options related to running Linux under
370 various hypervisors. This option alone does not add any kernel code.
372 If you say N, all options in this submenu will be skipped and disabled.
376 source "arch/x86/xen/Kconfig"
379 bool "VMI Guest support"
382 depends on !(X86_VISWS || X86_VOYAGER)
384 VMI provides a paravirtualized interface to the VMware ESX server
385 (it could be used by other hypervisors in theory too, but is not
386 at the moment), by linking the kernel to a GPL-ed ROM module
387 provided by the hypervisor.
390 bool "KVM paravirtualized clock"
392 depends on !(X86_VISWS || X86_VOYAGER)
394 Turning on this option will allow you to run a paravirtualized clock
395 when running over the KVM hypervisor. Instead of relying on a PIT
396 (or probably other) emulation by the underlying device model, the host
397 provides the guest with timing infrastructure such as time of day, and
401 bool "KVM Guest support"
403 depends on !(X86_VISWS || X86_VOYAGER)
405 This option enables various optimizations for running under the KVM
408 source "arch/x86/lguest/Kconfig"
411 bool "Enable paravirtualization code"
412 depends on !(X86_VISWS || X86_VOYAGER)
414 This changes the kernel so it can modify itself when it is run
415 under a hypervisor, potentially improving performance significantly
416 over full virtualization. However, when run without a hypervisor
417 the kernel is theoretically slower and slightly larger.
421 config MEMTEST_BOOTPARAM
422 bool "Memtest boot parameter"
426 This option adds a kernel parameter 'memtest', which allows memtest
427 to be disabled at boot. If this option is selected, memtest
428 functionality can be disabled with memtest=0 on the kernel
429 command line. The purpose of this option is to allow a single
430 kernel image to be distributed with memtest built in, but not
433 If you are unsure how to answer this question, answer Y.
435 config MEMTEST_BOOTPARAM_VALUE
436 int "Memtest boot parameter default value (0-4)"
437 depends on MEMTEST_BOOTPARAM
441 This option sets the default value for the kernel parameter
442 'memtest', which allows memtest to be disabled at boot. If this
443 option is set to 0 (zero), the memtest kernel parameter will
444 default to 0, disabling memtest at bootup. If this option is
445 set to 4, the memtest kernel parameter will default to 4,
446 enabling memtest at bootup, and use that as pattern number.
448 If you are unsure how to answer this question, answer 0.
452 depends on X86_32 && ACPI && NUMA && (X86_SUMMIT || X86_GENERICARCH)
455 config HAVE_ARCH_PARSE_SRAT
459 config X86_SUMMIT_NUMA
461 depends on X86_32 && NUMA && (X86_SUMMIT || X86_GENERICARCH)
463 config X86_CYCLONE_TIMER
465 depends on X86_32 && X86_SUMMIT || X86_GENERICARCH
467 config ES7000_CLUSTERED_APIC
469 depends on SMP && X86_ES7000 && MPENTIUMIII
471 source "arch/x86/Kconfig.cpu"
475 prompt "HPET Timer Support" if X86_32
477 Use the IA-PC HPET (High Precision Event Timer) to manage
478 time in preference to the PIT and RTC, if a HPET is
480 HPET is the next generation timer replacing legacy 8254s.
481 The HPET provides a stable time base on SMP
482 systems, unlike the TSC, but it is more expensive to access,
483 as it is off-chip. You can find the HPET spec at
484 <http://www.intel.com/hardwaredesign/hpetspec.htm>.
486 You can safely choose Y here. However, HPET will only be
487 activated if the platform and the BIOS support this feature.
488 Otherwise the 8254 will be used for timing services.
490 Choose N to continue using the legacy 8254 timer.
492 config HPET_EMULATE_RTC
494 depends on HPET_TIMER && (RTC=y || RTC=m || RTC_DRV_CMOS=m || RTC_DRV_CMOS=y)
496 # Mark as embedded because too many people got it wrong.
497 # The code disables itself when not needed.
500 bool "Enable DMI scanning" if EMBEDDED
502 Enabled scanning of DMI to identify machine quirks. Say Y
503 here unless you have verified that your setup is not
504 affected by entries in the DMI blacklist. Required by PNP
508 bool "GART IOMMU support" if EMBEDDED
512 depends on X86_64 && PCI
514 Support for full DMA access of devices with 32bit memory access only
515 on systems with more than 3GB. This is usually needed for USB,
516 sound, many IDE/SATA chipsets and some other devices.
517 Provides a driver for the AMD Athlon64/Opteron/Turion/Sempron GART
518 based hardware IOMMU and a software bounce buffer based IOMMU used
519 on Intel systems and as fallback.
520 The code is only active when needed (enough memory and limited
521 device) unless CONFIG_IOMMU_DEBUG or iommu=force is specified
525 bool "IBM Calgary IOMMU support"
527 depends on X86_64 && PCI && EXPERIMENTAL
529 Support for hardware IOMMUs in IBM's xSeries x366 and x460
530 systems. Needed to run systems with more than 3GB of memory
531 properly with 32-bit PCI devices that do not support DAC
532 (Double Address Cycle). Calgary also supports bus level
533 isolation, where all DMAs pass through the IOMMU. This
534 prevents them from going anywhere except their intended
535 destination. This catches hard-to-find kernel bugs and
536 mis-behaving drivers and devices that do not use the DMA-API
537 properly to set up their DMA buffers. The IOMMU can be
538 turned off at boot time with the iommu=off parameter.
539 Normally the kernel will make the right choice by itself.
542 config CALGARY_IOMMU_ENABLED_BY_DEFAULT
544 prompt "Should Calgary be enabled by default?"
545 depends on CALGARY_IOMMU
547 Should Calgary be enabled by default? if you choose 'y', Calgary
548 will be used (if it exists). If you choose 'n', Calgary will not be
549 used even if it exists. If you choose 'n' and would like to use
550 Calgary anyway, pass 'iommu=calgary' on the kernel command line.
553 # need this always selected by IOMMU for the VIA workaround
557 Support for software bounce buffers used on x86-64 systems
558 which don't have a hardware IOMMU (e.g. the current generation
559 of Intel's x86-64 CPUs). Using this PCI devices which can only
560 access 32-bits of memory can be used on systems with more than
561 3 GB of memory. If unsure, say Y.
564 def_bool (CALGARY_IOMMU || GART_IOMMU || SWIOTLB)
567 int "Maximum number of CPUs (2-255)"
570 default "32" if X86_NUMAQ || X86_SUMMIT || X86_BIGSMP || X86_ES7000
573 This allows you to specify the maximum number of CPUs which this
574 kernel will support. The maximum supported value is 255 and the
575 minimum value which makes sense is 2.
577 This is purely to save memory - each supported CPU adds
578 approximately eight kilobytes to the kernel image.
581 bool "SMT (Hyperthreading) scheduler support"
584 SMT scheduler support improves the CPU scheduler's decision making
585 when dealing with Intel Pentium 4 chips with HyperThreading at a
586 cost of slightly increased overhead in some places. If unsure say
591 prompt "Multi-core scheduler support"
594 Multi-core scheduler support improves the CPU scheduler's decision
595 making when dealing with multi-core CPU chips at a cost of slightly
596 increased overhead in some places. If unsure say N here.
598 source "kernel/Kconfig.preempt"
601 bool "Local APIC support on uniprocessors"
602 depends on X86_32 && !SMP && !(X86_VISWS || X86_VOYAGER || X86_GENERICARCH)
604 A local APIC (Advanced Programmable Interrupt Controller) is an
605 integrated interrupt controller in the CPU. If you have a single-CPU
606 system which has a processor with a local APIC, you can say Y here to
607 enable and use it. If you say Y here even though your machine doesn't
608 have a local APIC, then the kernel will still run with no slowdown at
609 all. The local APIC supports CPU-generated self-interrupts (timer,
610 performance counters), and the NMI watchdog which detects hard
614 bool "IO-APIC support on uniprocessors"
615 depends on X86_UP_APIC
617 An IO-APIC (I/O Advanced Programmable Interrupt Controller) is an
618 SMP-capable replacement for PC-style interrupt controllers. Most
619 SMP systems and many recent uniprocessor systems have one.
621 If you have a single-CPU system with an IO-APIC, you can say Y here
622 to use it. If you say Y here even though your machine doesn't have
623 an IO-APIC, then the kernel will still run with no slowdown at all.
625 config X86_LOCAL_APIC
627 depends on X86_64 || (X86_32 && (X86_UP_APIC || ((X86_VISWS || SMP) && !X86_VOYAGER) || X86_GENERICARCH))
631 depends on X86_64 || (X86_32 && (X86_UP_IOAPIC || (SMP && !(X86_VISWS || X86_VOYAGER)) || X86_GENERICARCH))
633 config X86_VISWS_APIC
635 depends on X86_32 && X86_VISWS
638 bool "Machine Check Exception"
639 depends on !X86_VOYAGER
641 Machine Check Exception support allows the processor to notify the
642 kernel if it detects a problem (e.g. overheating, component failure).
643 The action the kernel takes depends on the severity of the problem,
644 ranging from a warning message on the console, to halting the machine.
645 Your processor must be a Pentium or newer to support this - check the
646 flags in /proc/cpuinfo for mce. Note that some older Pentium systems
647 have a design flaw which leads to false MCE events - hence MCE is
648 disabled on all P5 processors, unless explicitly enabled with "mce"
649 as a boot argument. Similarly, if MCE is built in and creates a
650 problem on some new non-standard machine, you can boot with "nomce"
651 to disable it. MCE support simply ignores non-MCE processors like
652 the 386 and 486, so nearly everyone can say Y here.
656 prompt "Intel MCE features"
657 depends on X86_64 && X86_MCE && X86_LOCAL_APIC
659 Additional support for intel specific MCE features such as
664 prompt "AMD MCE features"
665 depends on X86_64 && X86_MCE && X86_LOCAL_APIC
667 Additional support for AMD specific MCE features such as
668 the DRAM Error Threshold.
670 config X86_MCE_NONFATAL
671 tristate "Check for non-fatal errors on AMD Athlon/Duron / Intel Pentium 4"
672 depends on X86_32 && X86_MCE
674 Enabling this feature starts a timer that triggers every 5 seconds which
675 will look at the machine check registers to see if anything happened.
676 Non-fatal problems automatically get corrected (but still logged).
677 Disable this if you don't want to see these messages.
678 Seeing the messages this option prints out may be indicative of dying
679 or out-of-spec (ie, overclocked) hardware.
680 This option only does something on certain CPUs.
681 (AMD Athlon/Duron and Intel Pentium 4)
683 config X86_MCE_P4THERMAL
684 bool "check for P4 thermal throttling interrupt."
685 depends on X86_32 && X86_MCE && (X86_UP_APIC || SMP) && !X86_VISWS
687 Enabling this feature will cause a message to be printed when the P4
688 enters thermal throttling.
691 bool "Enable VM86 support" if EMBEDDED
695 This option is required by programs like DOSEMU to run 16-bit legacy
696 code on X86 processors. It also may be needed by software like
697 XFree86 to initialize some video cards via BIOS. Disabling this
698 option saves about 6k.
701 tristate "Toshiba Laptop support"
704 This adds a driver to safely access the System Management Mode of
705 the CPU on Toshiba portables with a genuine Toshiba BIOS. It does
706 not work on models with a Phoenix BIOS. The System Management Mode
707 is used to set the BIOS and power saving options on Toshiba portables.
709 For information on utilities to make use of this driver see the
710 Toshiba Linux utilities web site at:
711 <http://www.buzzard.org.uk/toshiba/>.
713 Say Y if you intend to run this kernel on a Toshiba portable.
717 tristate "Dell laptop support"
719 This adds a driver to safely access the System Management Mode
720 of the CPU on the Dell Inspiron 8000. The System Management Mode
721 is used to read cpu temperature and cooling fan status and to
722 control the fans on the I8K portables.
724 This driver has been tested only on the Inspiron 8000 but it may
725 also work with other Dell laptops. You can force loading on other
726 models by passing the parameter `force=1' to the module. Use at
729 For information on utilities to make use of this driver see the
730 I8K Linux utilities web site at:
731 <http://people.debian.org/~dz/i8k/>
733 Say Y if you intend to run this kernel on a Dell Inspiron 8000.
736 config X86_REBOOTFIXUPS
738 prompt "Enable X86 board specific fixups for reboot"
739 depends on X86_32 && X86
741 This enables chipset and/or board specific fixups to be done
742 in order to get reboot to work correctly. This is only needed on
743 some combinations of hardware and BIOS. The symptom, for which
744 this config is intended, is when reboot ends with a stalled/hung
747 Currently, the only fixup is for the Geode machines using
748 CS5530A and CS5536 chipsets and the RDC R-321x SoC.
750 Say Y if you want to enable the fixup. Currently, it's safe to
751 enable this option even if you don't need it.
755 tristate "/dev/cpu/microcode - Intel IA32 CPU microcode support"
758 If you say Y here, you will be able to update the microcode on
759 Intel processors in the IA32 family, e.g. Pentium Pro, Pentium II,
760 Pentium III, Pentium 4, Xeon etc. You will obviously need the
761 actual microcode binary data itself which is not shipped with the
764 For latest news and information on obtaining all the required
765 ingredients for this driver, check:
766 <http://www.urbanmyth.org/microcode/>.
768 To compile this driver as a module, choose M here: the
769 module will be called microcode.
771 config MICROCODE_OLD_INTERFACE
776 tristate "/dev/cpu/*/msr - Model-specific register support"
778 This device gives privileged processes access to the x86
779 Model-Specific Registers (MSRs). It is a character device with
780 major 202 and minors 0 to 31 for /dev/cpu/0/msr to /dev/cpu/31/msr.
781 MSR accesses are directed to a specific CPU on multi-processor
785 tristate "/dev/cpu/*/cpuid - CPU information support"
787 This device gives processes access to the x86 CPUID instruction to
788 be executed on a specific processor. It is a character device
789 with major 203 and minors 0 to 31 for /dev/cpu/0/cpuid to
793 prompt "High Memory Support"
794 default HIGHMEM4G if !X86_NUMAQ
795 default HIGHMEM64G if X86_NUMAQ
800 depends on !X86_NUMAQ
802 Linux can use up to 64 Gigabytes of physical memory on x86 systems.
803 However, the address space of 32-bit x86 processors is only 4
804 Gigabytes large. That means that, if you have a large amount of
805 physical memory, not all of it can be "permanently mapped" by the
806 kernel. The physical memory that's not permanently mapped is called
809 If you are compiling a kernel which will never run on a machine with
810 more than 1 Gigabyte total physical RAM, answer "off" here (default
811 choice and suitable for most users). This will result in a "3GB/1GB"
812 split: 3GB are mapped so that each process sees a 3GB virtual memory
813 space and the remaining part of the 4GB virtual memory space is used
814 by the kernel to permanently map as much physical memory as
817 If the machine has between 1 and 4 Gigabytes physical RAM, then
820 If more than 4 Gigabytes is used then answer "64GB" here. This
821 selection turns Intel PAE (Physical Address Extension) mode on.
822 PAE implements 3-level paging on IA32 processors. PAE is fully
823 supported by Linux, PAE mode is implemented on all recent Intel
824 processors (Pentium Pro and better). NOTE: If you say "64GB" here,
825 then the kernel will not boot on CPUs that don't support PAE!
827 The actual amount of total physical memory will either be
828 auto detected or can be forced by using a kernel command line option
829 such as "mem=256M". (Try "man bootparam" or see the documentation of
830 your boot loader (lilo or loadlin) about how to pass options to the
831 kernel at boot time.)
833 If unsure, say "off".
837 depends on !X86_NUMAQ
839 Select this if you have a 32-bit processor and between 1 and 4
840 gigabytes of physical RAM.
844 depends on !M386 && !M486
847 Select this if you have a 32-bit processor and more than 4
848 gigabytes of physical RAM.
853 depends on EXPERIMENTAL
854 prompt "Memory split" if EMBEDDED
858 Select the desired split between kernel and user memory.
860 If the address range available to the kernel is less than the
861 physical memory installed, the remaining memory will be available
862 as "high memory". Accessing high memory is a little more costly
863 than low memory, as it needs to be mapped into the kernel first.
864 Note that increasing the kernel address space limits the range
865 available to user programs, making the address space there
866 tighter. Selecting anything other than the default 3G/1G split
867 will also likely make your kernel incompatible with binary-only
870 If you are not absolutely sure what you are doing, leave this
874 bool "3G/1G user/kernel split"
875 config VMSPLIT_3G_OPT
877 bool "3G/1G user/kernel split (for full 1G low memory)"
879 bool "2G/2G user/kernel split"
880 config VMSPLIT_2G_OPT
882 bool "2G/2G user/kernel split (for full 2G low memory)"
884 bool "1G/3G user/kernel split"
889 default 0xB0000000 if VMSPLIT_3G_OPT
890 default 0x80000000 if VMSPLIT_2G
891 default 0x78000000 if VMSPLIT_2G_OPT
892 default 0x40000000 if VMSPLIT_1G
898 depends on X86_32 && (HIGHMEM64G || HIGHMEM4G)
902 prompt "PAE (Physical Address Extension) Support"
903 depends on X86_32 && !HIGHMEM4G
904 select RESOURCES_64BIT
906 PAE is required for NX support, and furthermore enables
907 larger swapspace support for non-overcommit purposes. It
908 has the cost of more pagetable lookup overhead, and also
909 consumes more pagetable space per process.
911 # Common NUMA Features
913 bool "Numa Memory Allocation and Scheduler Support (EXPERIMENTAL)"
915 depends on X86_64 || (X86_32 && HIGHMEM64G && (X86_NUMAQ || (X86_SUMMIT || X86_GENERICARCH) && ACPI) && EXPERIMENTAL)
917 default y if (X86_NUMAQ || X86_SUMMIT)
919 Enable NUMA (Non Uniform Memory Access) support.
920 The kernel will try to allocate memory used by a CPU on the
921 local memory controller of the CPU and add some more
922 NUMA awareness to the kernel.
924 For i386 this is currently highly experimental and should be only
925 used for kernel development. It might also cause boot failures.
926 For x86_64 this is recommended on all multiprocessor Opteron systems.
927 If the system is EM64T, you should say N unless your system is
930 comment "NUMA (Summit) requires SMP, 64GB highmem support, ACPI"
931 depends on X86_32 && X86_SUMMIT && (!HIGHMEM64G || !ACPI)
935 prompt "Old style AMD Opteron NUMA detection"
936 depends on X86_64 && NUMA && PCI
938 Enable K8 NUMA node topology detection. You should say Y here if
939 you have a multi processor AMD K8 system. This uses an old
940 method to read the NUMA configuration directly from the builtin
941 Northbridge of Opteron. It is recommended to use X86_64_ACPI_NUMA
942 instead, which also takes priority if both are compiled in.
944 config X86_64_ACPI_NUMA
946 prompt "ACPI NUMA detection"
947 depends on X86_64 && NUMA && ACPI && PCI
950 Enable ACPI SRAT based node topology detection.
952 # Some NUMA nodes have memory ranges that span
953 # other nodes. Even though a pfn is valid and
954 # between a node's start and end pfns, it may not
955 # reside on that node. See memmap_init_zone()
957 config NODES_SPAN_OTHER_NODES
959 depends on X86_64_ACPI_NUMA
962 bool "NUMA emulation"
963 depends on X86_64 && NUMA
965 Enable NUMA emulation. A flat machine will be split
966 into virtual nodes when booted with "numa=fake=N", where N is the
967 number of nodes. This is only useful for debugging.
970 int "Max num nodes shift(1-15)"
972 default "6" if X86_64
973 default "4" if X86_NUMAQ
975 depends on NEED_MULTIPLE_NODES
977 config HAVE_ARCH_BOOTMEM_NODE
979 depends on X86_32 && NUMA
981 config ARCH_HAVE_MEMORY_PRESENT
983 depends on X86_32 && DISCONTIGMEM
985 config NEED_NODE_MEMMAP_SIZE
987 depends on X86_32 && (DISCONTIGMEM || SPARSEMEM)
989 config HAVE_ARCH_ALLOC_REMAP
991 depends on X86_32 && NUMA
993 config ARCH_FLATMEM_ENABLE
995 depends on X86_32 && ARCH_SELECT_MEMORY_MODEL && X86_PC && !NUMA
997 config ARCH_DISCONTIGMEM_ENABLE
999 depends on NUMA && X86_32
1001 config ARCH_DISCONTIGMEM_DEFAULT
1003 depends on NUMA && X86_32
1005 config ARCH_SPARSEMEM_DEFAULT
1009 config ARCH_SPARSEMEM_ENABLE
1011 depends on X86_64 || NUMA || (EXPERIMENTAL && X86_PC)
1012 select SPARSEMEM_STATIC if X86_32
1013 select SPARSEMEM_VMEMMAP_ENABLE if X86_64
1015 config ARCH_SELECT_MEMORY_MODEL
1017 depends on ARCH_SPARSEMEM_ENABLE
1019 config ARCH_MEMORY_PROBE
1021 depends on MEMORY_HOTPLUG
1026 bool "Allocate 3rd-level pagetables from highmem"
1027 depends on X86_32 && (HIGHMEM4G || HIGHMEM64G)
1029 The VM uses one page table entry for each page of physical memory.
1030 For systems with a lot of RAM, this can be wasteful of precious
1031 low memory. Setting this option will put user-space page table
1032 entries in high memory.
1034 config MATH_EMULATION
1036 prompt "Math emulation" if X86_32
1038 Linux can emulate a math coprocessor (used for floating point
1039 operations) if you don't have one. 486DX and Pentium processors have
1040 a math coprocessor built in, 486SX and 386 do not, unless you added
1041 a 487DX or 387, respectively. (The messages during boot time can
1042 give you some hints here ["man dmesg"].) Everyone needs either a
1043 coprocessor or this emulation.
1045 If you don't have a math coprocessor, you need to say Y here; if you
1046 say Y here even though you have a coprocessor, the coprocessor will
1047 be used nevertheless. (This behavior can be changed with the kernel
1048 command line option "no387", which comes handy if your coprocessor
1049 is broken. Try "man bootparam" or see the documentation of your boot
1050 loader (lilo or loadlin) about how to pass options to the kernel at
1051 boot time.) This means that it is a good idea to say Y here if you
1052 intend to use this kernel on different machines.
1054 More information about the internals of the Linux math coprocessor
1055 emulation can be found in <file:arch/x86/math-emu/README>.
1057 If you are not sure, say Y; apart from resulting in a 66 KB bigger
1058 kernel, it won't hurt.
1061 bool "MTRR (Memory Type Range Register) support"
1063 On Intel P6 family processors (Pentium Pro, Pentium II and later)
1064 the Memory Type Range Registers (MTRRs) may be used to control
1065 processor access to memory ranges. This is most useful if you have
1066 a video (VGA) card on a PCI or AGP bus. Enabling write-combining
1067 allows bus write transfers to be combined into a larger transfer
1068 before bursting over the PCI/AGP bus. This can increase performance
1069 of image write operations 2.5 times or more. Saying Y here creates a
1070 /proc/mtrr file which may be used to manipulate your processor's
1071 MTRRs. Typically the X server should use this.
1073 This code has a reasonably generic interface so that similar
1074 control registers on other processors can be easily supported
1077 The Cyrix 6x86, 6x86MX and M II processors have Address Range
1078 Registers (ARRs) which provide a similar functionality to MTRRs. For
1079 these, the ARRs are used to emulate the MTRRs.
1080 The AMD K6-2 (stepping 8 and above) and K6-3 processors have two
1081 MTRRs. The Centaur C6 (WinChip) has 8 MCRs, allowing
1082 write-combining. All of these processors are supported by this code
1083 and it makes sense to say Y here if you have one of them.
1085 Saying Y here also fixes a problem with buggy SMP BIOSes which only
1086 set the MTRRs for the boot CPU and not for the secondary CPUs. This
1087 can lead to all sorts of problems, so it's good to say Y here.
1089 You can safely say Y even if your machine doesn't have MTRRs, you'll
1090 just add about 9 KB to your kernel.
1092 See <file:Documentation/mtrr.txt> for more information.
1096 prompt "x86 PAT support"
1099 Use PAT attributes to setup page level cache control.
1101 PATs are the modern equivalents of MTRRs and are much more
1102 flexible than MTRRs.
1104 Say N here if you see bootup problems (boot crash, boot hang,
1105 spontaneous reboots) or a non-working video driver.
1111 prompt "EFI runtime service support"
1114 This enables the kernel to use EFI runtime services that are
1115 available (such as the EFI variable services).
1117 This option is only useful on systems that have EFI firmware.
1118 In addition, you should use the latest ELILO loader available
1119 at <http://elilo.sourceforge.net> in order to take advantage
1120 of EFI runtime services. However, even with this option, the
1121 resultant kernel should continue to boot on existing non-EFI
1126 prompt "Enable kernel irq balancing"
1127 depends on X86_32 && SMP && X86_IO_APIC
1129 The default yes will allow the kernel to do irq load balancing.
1130 Saying no will keep the kernel from doing irq load balancing.
1134 prompt "Enable seccomp to safely compute untrusted bytecode"
1137 This kernel feature is useful for number crunching applications
1138 that may need to compute untrusted bytecode during their
1139 execution. By using pipes or other transports made available to
1140 the process as file descriptors supporting the read/write
1141 syscalls, it's possible to isolate those applications in
1142 their own address space using seccomp. Once seccomp is
1143 enabled via /proc/<pid>/seccomp, it cannot be disabled
1144 and the task is only allowed to execute a few safe syscalls
1145 defined by each seccomp mode.
1147 If unsure, say Y. Only embedded should say N here.
1149 config CC_STACKPROTECTOR
1150 bool "Enable -fstack-protector buffer overflow detection (EXPERIMENTAL)"
1151 depends on X86_64 && EXPERIMENTAL && BROKEN
1153 This option turns on the -fstack-protector GCC feature. This
1154 feature puts, at the beginning of critical functions, a canary
1155 value on the stack just before the return address, and validates
1156 the value just before actually returning. Stack based buffer
1157 overflows (that need to overwrite this return address) now also
1158 overwrite the canary, which gets detected and the attack is then
1159 neutralized via a kernel panic.
1161 This feature requires gcc version 4.2 or above, or a distribution
1162 gcc with the feature backported. Older versions are automatically
1163 detected and for those versions, this configuration option is ignored.
1165 config CC_STACKPROTECTOR_ALL
1166 bool "Use stack-protector for all functions"
1167 depends on CC_STACKPROTECTOR
1169 Normally, GCC only inserts the canary value protection for
1170 functions that use large-ish on-stack buffers. By enabling
1171 this option, GCC will be asked to do this for ALL functions.
1173 source kernel/Kconfig.hz
1176 bool "kexec system call"
1177 depends on X86_BIOS_REBOOT
1179 kexec is a system call that implements the ability to shutdown your
1180 current kernel, and to start another kernel. It is like a reboot
1181 but it is independent of the system firmware. And like a reboot
1182 you can start any kernel with it, not just Linux.
1184 The name comes from the similarity to the exec system call.
1186 It is an ongoing process to be certain the hardware in a machine
1187 is properly shutdown, so do not be surprised if this code does not
1188 initially work for you. It may help to enable device hotplugging
1189 support. As of this writing the exact hardware interface is
1190 strongly in flux, so no good recommendation can be made.
1193 bool "kernel crash dumps (EXPERIMENTAL)"
1194 depends on EXPERIMENTAL
1195 depends on X86_64 || (X86_32 && HIGHMEM)
1197 Generate crash dump after being started by kexec.
1198 This should be normally only set in special crash dump kernels
1199 which are loaded in the main kernel with kexec-tools into
1200 a specially reserved region and then later executed after
1201 a crash by kdump/kexec. The crash dump kernel must be compiled
1202 to a memory address not used by the main kernel or BIOS using
1203 PHYSICAL_START, or it must be built as a relocatable image
1204 (CONFIG_RELOCATABLE=y).
1205 For more details see Documentation/kdump/kdump.txt
1207 config PHYSICAL_START
1208 hex "Physical address where the kernel is loaded" if (EMBEDDED || CRASH_DUMP)
1209 default "0x1000000" if X86_NUMAQ
1210 default "0x200000" if X86_64
1213 This gives the physical address where the kernel is loaded.
1215 If kernel is a not relocatable (CONFIG_RELOCATABLE=n) then
1216 bzImage will decompress itself to above physical address and
1217 run from there. Otherwise, bzImage will run from the address where
1218 it has been loaded by the boot loader and will ignore above physical
1221 In normal kdump cases one does not have to set/change this option
1222 as now bzImage can be compiled as a completely relocatable image
1223 (CONFIG_RELOCATABLE=y) and be used to load and run from a different
1224 address. This option is mainly useful for the folks who don't want
1225 to use a bzImage for capturing the crash dump and want to use a
1226 vmlinux instead. vmlinux is not relocatable hence a kernel needs
1227 to be specifically compiled to run from a specific memory area
1228 (normally a reserved region) and this option comes handy.
1230 So if you are using bzImage for capturing the crash dump, leave
1231 the value here unchanged to 0x100000 and set CONFIG_RELOCATABLE=y.
1232 Otherwise if you plan to use vmlinux for capturing the crash dump
1233 change this value to start of the reserved region (Typically 16MB
1234 0x1000000). In other words, it can be set based on the "X" value as
1235 specified in the "crashkernel=YM@XM" command line boot parameter
1236 passed to the panic-ed kernel. Typically this parameter is set as
1237 crashkernel=64M@16M. Please take a look at
1238 Documentation/kdump/kdump.txt for more details about crash dumps.
1240 Usage of bzImage for capturing the crash dump is recommended as
1241 one does not have to build two kernels. Same kernel can be used
1242 as production kernel and capture kernel. Above option should have
1243 gone away after relocatable bzImage support is introduced. But it
1244 is present because there are users out there who continue to use
1245 vmlinux for dump capture. This option should go away down the
1248 Don't change this unless you know what you are doing.
1251 bool "Build a relocatable kernel (EXPERIMENTAL)"
1252 depends on EXPERIMENTAL
1254 This builds a kernel image that retains relocation information
1255 so it can be loaded someplace besides the default 1MB.
1256 The relocations tend to make the kernel binary about 10% larger,
1257 but are discarded at runtime.
1259 One use is for the kexec on panic case where the recovery kernel
1260 must live at a different physical address than the primary
1263 Note: If CONFIG_RELOCATABLE=y, then the kernel runs from the address
1264 it has been loaded at and the compile time physical address
1265 (CONFIG_PHYSICAL_START) is ignored.
1267 config PHYSICAL_ALIGN
1269 prompt "Alignment value to which kernel should be aligned" if X86_32
1270 default "0x100000" if X86_32
1271 default "0x200000" if X86_64
1272 range 0x2000 0x400000
1274 This value puts the alignment restrictions on physical address
1275 where kernel is loaded and run from. Kernel is compiled for an
1276 address which meets above alignment restriction.
1278 If bootloader loads the kernel at a non-aligned address and
1279 CONFIG_RELOCATABLE is set, kernel will move itself to nearest
1280 address aligned to above value and run from there.
1282 If bootloader loads the kernel at a non-aligned address and
1283 CONFIG_RELOCATABLE is not set, kernel will ignore the run time
1284 load address and decompress itself to the address it has been
1285 compiled for and run from there. The address for which kernel is
1286 compiled already meets above alignment restrictions. Hence the
1287 end result is that kernel runs from a physical address meeting
1288 above alignment restrictions.
1290 Don't change this unless you know what you are doing.
1293 bool "Support for suspend on SMP and hot-pluggable CPUs (EXPERIMENTAL)"
1294 depends on SMP && HOTPLUG && EXPERIMENTAL && !X86_VOYAGER
1296 Say Y here to experiment with turning CPUs off and on, and to
1297 enable suspend on SMP systems. CPUs can be controlled through
1298 /sys/devices/system/cpu.
1299 Say N if you want to disable CPU hotplug and don't need to
1304 prompt "Compat VDSO support"
1305 depends on X86_32 || IA32_EMULATION
1307 Map the 32-bit VDSO to the predictable old-style address too.
1309 Say N here if you are running a sufficiently recent glibc
1310 version (2.3.3 or later), to remove the high-mapped
1311 VDSO mapping and to exclusively use the randomized VDSO.
1317 config ARCH_ENABLE_MEMORY_HOTPLUG
1319 depends on X86_64 || (X86_32 && HIGHMEM)
1321 config HAVE_ARCH_EARLY_PFN_TO_NID
1325 menu "Power management options"
1326 depends on !X86_VOYAGER
1328 config ARCH_HIBERNATION_HEADER
1330 depends on X86_64 && HIBERNATION
1332 source "kernel/power/Kconfig"
1334 source "drivers/acpi/Kconfig"
1339 depends on APM || APM_MODULE
1342 tristate "APM (Advanced Power Management) BIOS support"
1343 depends on X86_32 && PM_SLEEP && !X86_VISWS
1345 APM is a BIOS specification for saving power using several different
1346 techniques. This is mostly useful for battery powered laptops with
1347 APM compliant BIOSes. If you say Y here, the system time will be
1348 reset after a RESUME operation, the /proc/apm device will provide
1349 battery status information, and user-space programs will receive
1350 notification of APM "events" (e.g. battery status change).
1352 If you select "Y" here, you can disable actual use of the APM
1353 BIOS by passing the "apm=off" option to the kernel at boot time.
1355 Note that the APM support is almost completely disabled for
1356 machines with more than one CPU.
1358 In order to use APM, you will need supporting software. For location
1359 and more information, read <file:Documentation/power/pm.txt> and the
1360 Battery Powered Linux mini-HOWTO, available from
1361 <http://www.tldp.org/docs.html#howto>.
1363 This driver does not spin down disk drives (see the hdparm(8)
1364 manpage ("man 8 hdparm") for that), and it doesn't turn off
1365 VESA-compliant "green" monitors.
1367 This driver does not support the TI 4000M TravelMate and the ACER
1368 486/DX4/75 because they don't have compliant BIOSes. Many "green"
1369 desktop machines also don't have compliant BIOSes, and this driver
1370 may cause those machines to panic during the boot phase.
1372 Generally, if you don't have a battery in your machine, there isn't
1373 much point in using this driver and you should say N. If you get
1374 random kernel OOPSes or reboots that don't seem to be related to
1375 anything, try disabling/enabling this option (or disabling/enabling
1378 Some other things you should try when experiencing seemingly random,
1381 1) make sure that you have enough swap space and that it is
1383 2) pass the "no-hlt" option to the kernel
1384 3) switch on floating point emulation in the kernel and pass
1385 the "no387" option to the kernel
1386 4) pass the "floppy=nodma" option to the kernel
1387 5) pass the "mem=4M" option to the kernel (thereby disabling
1388 all but the first 4 MB of RAM)
1389 6) make sure that the CPU is not over clocked.
1390 7) read the sig11 FAQ at <http://www.bitwizard.nl/sig11/>
1391 8) disable the cache from your BIOS settings
1392 9) install a fan for the video card or exchange video RAM
1393 10) install a better fan for the CPU
1394 11) exchange RAM chips
1395 12) exchange the motherboard.
1397 To compile this driver as a module, choose M here: the
1398 module will be called apm.
1402 config APM_IGNORE_USER_SUSPEND
1403 bool "Ignore USER SUSPEND"
1405 This option will ignore USER SUSPEND requests. On machines with a
1406 compliant APM BIOS, you want to say N. However, on the NEC Versa M
1407 series notebooks, it is necessary to say Y because of a BIOS bug.
1409 config APM_DO_ENABLE
1410 bool "Enable PM at boot time"
1412 Enable APM features at boot time. From page 36 of the APM BIOS
1413 specification: "When disabled, the APM BIOS does not automatically
1414 power manage devices, enter the Standby State, enter the Suspend
1415 State, or take power saving steps in response to CPU Idle calls."
1416 This driver will make CPU Idle calls when Linux is idle (unless this
1417 feature is turned off -- see "Do CPU IDLE calls", below). This
1418 should always save battery power, but more complicated APM features
1419 will be dependent on your BIOS implementation. You may need to turn
1420 this option off if your computer hangs at boot time when using APM
1421 support, or if it beeps continuously instead of suspending. Turn
1422 this off if you have a NEC UltraLite Versa 33/C or a Toshiba
1423 T400CDT. This is off by default since most machines do fine without
1427 bool "Make CPU Idle calls when idle"
1429 Enable calls to APM CPU Idle/CPU Busy inside the kernel's idle loop.
1430 On some machines, this can activate improved power savings, such as
1431 a slowed CPU clock rate, when the machine is idle. These idle calls
1432 are made after the idle loop has run for some length of time (e.g.,
1433 333 mS). On some machines, this will cause a hang at boot time or
1434 whenever the CPU becomes idle. (On machines with more than one CPU,
1435 this option does nothing.)
1437 config APM_DISPLAY_BLANK
1438 bool "Enable console blanking using APM"
1440 Enable console blanking using the APM. Some laptops can use this to
1441 turn off the LCD backlight when the screen blanker of the Linux
1442 virtual console blanks the screen. Note that this is only used by
1443 the virtual console screen blanker, and won't turn off the backlight
1444 when using the X Window system. This also doesn't have anything to
1445 do with your VESA-compliant power-saving monitor. Further, this
1446 option doesn't work for all laptops -- it might not turn off your
1447 backlight at all, or it might print a lot of errors to the console,
1448 especially if you are using gpm.
1450 config APM_ALLOW_INTS
1451 bool "Allow interrupts during APM BIOS calls"
1453 Normally we disable external interrupts while we are making calls to
1454 the APM BIOS as a measure to lessen the effects of a badly behaving
1455 BIOS implementation. The BIOS should reenable interrupts if it
1456 needs to. Unfortunately, some BIOSes do not -- especially those in
1457 many of the newer IBM Thinkpads. If you experience hangs when you
1458 suspend, try setting this to Y. Otherwise, say N.
1460 config APM_REAL_MODE_POWER_OFF
1461 bool "Use real mode APM BIOS call to power off"
1463 Use real mode APM BIOS calls to switch off the computer. This is
1464 a work-around for a number of buggy BIOSes. Switch this option on if
1465 your computer crashes instead of powering off properly.
1469 source "arch/x86/kernel/cpu/cpufreq/Kconfig"
1471 source "drivers/cpuidle/Kconfig"
1476 menu "Bus options (PCI etc.)"
1479 bool "PCI support" if !X86_VISWS && !X86_VSMP
1480 depends on !X86_VOYAGER
1482 select ARCH_SUPPORTS_MSI if (X86_LOCAL_APIC && X86_IO_APIC)
1484 Find out whether you have a PCI motherboard. PCI is the name of a
1485 bus system, i.e. the way the CPU talks to the other stuff inside
1486 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
1487 VESA. If you have PCI, say Y, otherwise N.
1490 prompt "PCI access mode"
1491 depends on X86_32 && PCI && !X86_VISWS
1494 On PCI systems, the BIOS can be used to detect the PCI devices and
1495 determine their configuration. However, some old PCI motherboards
1496 have BIOS bugs and may crash if this is done. Also, some embedded
1497 PCI-based systems don't have any BIOS at all. Linux can also try to
1498 detect the PCI hardware directly without using the BIOS.
1500 With this option, you can specify how Linux should detect the
1501 PCI devices. If you choose "BIOS", the BIOS will be used,
1502 if you choose "Direct", the BIOS won't be used, and if you
1503 choose "MMConfig", then PCI Express MMCONFIG will be used.
1504 If you choose "Any", the kernel will try MMCONFIG, then the
1505 direct access method and falls back to the BIOS if that doesn't
1506 work. If unsure, go with the default, which is "Any".
1511 config PCI_GOMMCONFIG
1528 depends on X86_32 && !X86_VISWS && PCI && (PCI_GOBIOS || PCI_GOANY)
1530 # x86-64 doesn't support PCI BIOS access from long mode so always go direct.
1533 depends on PCI && (X86_64 || (PCI_GODIRECT || PCI_GOANY || PCI_GOOLPC) || X86_VISWS)
1537 depends on X86_32 && PCI && ACPI && (PCI_GOMMCONFIG || PCI_GOANY)
1541 depends on PCI && PCI_GOOLPC
1549 bool "Support mmconfig PCI config space access"
1550 depends on X86_64 && PCI && ACPI
1553 bool "Support for DMA Remapping Devices (EXPERIMENTAL)"
1554 depends on X86_64 && PCI_MSI && ACPI && EXPERIMENTAL
1556 DMA remapping (DMAR) devices support enables independent address
1557 translations for Direct Memory Access (DMA) from devices.
1558 These DMA remapping devices are reported via ACPI tables
1559 and include PCI device scope covered by these DMA
1564 prompt "Support for Graphics workaround"
1567 Current Graphics drivers tend to use physical address
1568 for DMA and avoid using DMA APIs. Setting this config
1569 option permits the IOMMU driver to set a unity map for
1570 all the OS-visible memory. Hence the driver can continue
1571 to use physical addresses for DMA.
1573 config DMAR_FLOPPY_WA
1577 Floppy disk drivers are know to bypass DMA API calls
1578 thereby failing to work when IOMMU is enabled. This
1579 workaround will setup a 1:1 mapping for the first
1580 16M to make floppy (an ISA device) work.
1582 source "drivers/pci/pcie/Kconfig"
1584 source "drivers/pci/Kconfig"
1586 # x86_64 have no ISA slots, but do have ISA-style DMA.
1594 depends on !(X86_VOYAGER || X86_VISWS)
1596 Find out whether you have ISA slots on your motherboard. ISA is the
1597 name of a bus system, i.e. the way the CPU talks to the other stuff
1598 inside your box. Other bus systems are PCI, EISA, MicroChannel
1599 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
1600 newer boards don't support it. If you have ISA, say Y, otherwise N.
1606 The Extended Industry Standard Architecture (EISA) bus was
1607 developed as an open alternative to the IBM MicroChannel bus.
1609 The EISA bus provided some of the features of the IBM MicroChannel
1610 bus while maintaining backward compatibility with cards made for
1611 the older ISA bus. The EISA bus saw limited use between 1988 and
1612 1995 when it was made obsolete by the PCI bus.
1614 Say Y here if you are building a kernel for an EISA-based machine.
1618 source "drivers/eisa/Kconfig"
1621 bool "MCA support" if !(X86_VISWS || X86_VOYAGER)
1622 default y if X86_VOYAGER
1624 MicroChannel Architecture is found in some IBM PS/2 machines and
1625 laptops. It is a bus system similar to PCI or ISA. See
1626 <file:Documentation/mca.txt> (and especially the web page given
1627 there) before attempting to build an MCA bus kernel.
1629 source "drivers/mca/Kconfig"
1632 tristate "NatSemi SCx200 support"
1633 depends on !X86_VOYAGER
1635 This provides basic support for National Semiconductor's
1636 (now AMD's) Geode processors. The driver probes for the
1637 PCI-IDs of several on-chip devices, so its a good dependency
1638 for other scx200_* drivers.
1640 If compiled as a module, the driver is named scx200.
1642 config SCx200HR_TIMER
1643 tristate "NatSemi SCx200 27MHz High-Resolution Timer Support"
1644 depends on SCx200 && GENERIC_TIME
1647 This driver provides a clocksource built upon the on-chip
1648 27MHz high-resolution timer. Its also a workaround for
1649 NSC Geode SC-1100's buggy TSC, which loses time when the
1650 processor goes idle (as is done by the scheduler). The
1651 other workaround is idle=poll boot option.
1653 config GEODE_MFGPT_TIMER
1655 prompt "Geode Multi-Function General Purpose Timer (MFGPT) events"
1656 depends on MGEODE_LX && GENERIC_TIME && GENERIC_CLOCKEVENTS
1658 This driver provides a clock event source based on the MFGPT
1659 timer(s) in the CS5535 and CS5536 companion chip for the geode.
1660 MFGPTs have a better resolution and max interval than the
1661 generic PIT, and are suitable for use as high-res timers.
1664 bool "One Laptop Per Child support"
1665 depends on MGEODE_LX
1668 Add support for detecting the unique features of the OLPC
1675 depends on AGP_AMD64 || (X86_64 && (GART_IOMMU || (PCI && NUMA)))
1677 source "drivers/pcmcia/Kconfig"
1679 source "drivers/pci/hotplug/Kconfig"
1684 menu "Executable file formats / Emulations"
1686 source "fs/Kconfig.binfmt"
1688 config IA32_EMULATION
1689 bool "IA32 Emulation"
1691 select COMPAT_BINFMT_ELF
1693 Include code to run 32-bit programs under a 64-bit kernel. You should
1694 likely turn this on, unless you're 100% sure that you don't have any
1695 32-bit programs left.
1698 tristate "IA32 a.out support"
1699 depends on IA32_EMULATION && ARCH_SUPPORTS_AOUT
1701 Support old a.out binaries in the 32bit emulation.
1705 depends on IA32_EMULATION
1707 config COMPAT_FOR_U64_ALIGNMENT
1711 config SYSVIPC_COMPAT
1713 depends on X86_64 && COMPAT && SYSVIPC
1718 source "net/Kconfig"
1720 source "drivers/Kconfig"
1722 source "drivers/firmware/Kconfig"
1726 source "arch/x86/Kconfig.debug"
1728 source "security/Kconfig"
1730 source "crypto/Kconfig"
1732 source "arch/x86/kvm/Kconfig"
1734 source "lib/Kconfig"
git.openpandora.org / pandora-kernel.git / blob