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_DYNAMIC_FTRACE
28 select HAVE_KVM if ((X86_32 && !X86_VOYAGER && !X86_VISWS && !X86_NUMAQ) || X86_64)
29 select HAVE_ARCH_KGDB if !X86_VOYAGER
33 default "arch/x86/configs/i386_defconfig" if X86_32
34 default "arch/x86/configs/x86_64_defconfig" if X86_64
37 config GENERIC_LOCKBREAK
43 config GENERIC_CMOS_UPDATE
46 config CLOCKSOURCE_WATCHDOG
49 config GENERIC_CLOCKEVENTS
52 config GENERIC_CLOCKEVENTS_BROADCAST
54 depends on X86_64 || (X86_32 && X86_LOCAL_APIC)
56 config LOCKDEP_SUPPORT
59 config STACKTRACE_SUPPORT
62 config HAVE_LATENCYTOP_SUPPORT
65 config FAST_CMPXCHG_LOCAL
78 config GENERIC_ISA_DMA
88 config GENERIC_HWEIGHT
94 config ARCH_MAY_HAVE_PC_FDC
97 config RWSEM_GENERIC_SPINLOCK
100 config RWSEM_XCHGADD_ALGORITHM
103 config ARCH_HAS_ILOG2_U32
106 config ARCH_HAS_ILOG2_U64
109 config ARCH_HAS_CPU_IDLE_WAIT
112 config GENERIC_CALIBRATE_DELAY
115 config GENERIC_TIME_VSYSCALL
119 config ARCH_HAS_CPU_RELAX
122 config ARCH_HAS_CACHE_LINE_SIZE
125 config HAVE_SETUP_PER_CPU_AREA
126 def_bool X86_64 || (X86_SMP && !X86_VOYAGER)
128 config HAVE_CPUMASK_OF_CPU_MAP
131 config ARCH_HIBERNATION_POSSIBLE
133 depends on !SMP || !X86_VOYAGER
135 config ARCH_SUSPEND_POSSIBLE
137 depends on !X86_VOYAGER
143 config ARCH_POPULATES_NODE_MAP
150 config ARCH_SUPPORTS_AOUT
153 config ARCH_SUPPORTS_OPTIMIZED_INLINING
156 # Use the generic interrupt handling code in kernel/irq/:
157 config GENERIC_HARDIRQS
161 config GENERIC_IRQ_PROBE
165 config GENERIC_PENDING_IRQ
167 depends on GENERIC_HARDIRQS && SMP
172 depends on SMP && ((X86_32 && !X86_VOYAGER) || X86_64)
177 depends on X86_32 && SMP
181 depends on X86_64 && SMP
186 depends on (X86_32 && !(X86_VISWS || X86_VOYAGER)) || X86_64
189 config X86_BIOS_REBOOT
191 depends on !X86_VISWS && !X86_VOYAGER
194 config X86_TRAMPOLINE
196 depends on X86_SMP || (X86_VOYAGER && SMP) || (64BIT && ACPI_SLEEP)
201 source "init/Kconfig"
203 menu "Processor type and features"
205 source "kernel/time/Kconfig"
208 bool "Symmetric multi-processing support"
210 This enables support for systems with more than one CPU. If you have
211 a system with only one CPU, like most personal computers, say N. If
212 you have a system with more than one CPU, say Y.
214 If you say N here, the kernel will run on single and multiprocessor
215 machines, but will use only one CPU of a multiprocessor machine. If
216 you say Y here, the kernel will run on many, but not all,
217 singleprocessor machines. On a singleprocessor machine, the kernel
218 will run faster if you say N here.
220 Note that if you say Y here and choose architecture "586" or
221 "Pentium" under "Processor family", the kernel will not work on 486
222 architectures. Similarly, multiprocessor kernels for the "PPro"
223 architecture may not work on all Pentium based boards.
225 People using multiprocessor machines who say Y here should also say
226 Y to "Enhanced Real Time Clock Support", below. The "Advanced Power
227 Management" code will be disabled if you say Y here.
229 See also <file:Documentation/i386/IO-APIC.txt>,
230 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
231 <http://www.tldp.org/docs.html#howto>.
233 If you don't know what to do here, say N.
236 prompt "Subarchitecture Type"
242 Choose this option if your computer is a standard PC or compatible.
248 Select this for an AMD Elan processor.
250 Do not use this option for K6/Athlon/Opteron processors!
252 If unsure, choose "PC-compatible" instead.
256 depends on X86_32 && (SMP || BROKEN)
258 Voyager is an MCA-based 32-way capable SMP architecture proprietary
259 to NCR Corp. Machine classes 345x/35xx/4100/51xx are Voyager-based.
263 If you do not specifically know you have a Voyager based machine,
264 say N here, otherwise the kernel you build will not be bootable.
267 bool "NUMAQ (IBM/Sequent)"
268 depends on SMP && X86_32
271 This option is used for getting Linux to run on a (IBM/Sequent) NUMA
272 multiquad box. This changes the way that processors are bootstrapped,
273 and uses Clustered Logical APIC addressing mode instead of Flat Logical.
274 You will need a new lynxer.elf file to flash your firmware with - send
275 email to <Martin.Bligh@us.ibm.com>.
278 bool "Summit/EXA (IBM x440)"
279 depends on X86_32 && SMP
281 This option is needed for IBM systems that use the Summit/EXA chipset.
282 In particular, it is needed for the x440.
284 If you don't have one of these computers, you should say N here.
285 If you want to build a NUMA kernel, you must select ACPI.
288 bool "Support for other sub-arch SMP systems with more than 8 CPUs"
289 depends on X86_32 && SMP
291 This option is needed for the systems that have more than 8 CPUs
292 and if the system is not of any sub-arch type above.
294 If you don't have such a system, you should say N here.
297 bool "SGI 320/540 (Visual Workstation)"
300 The SGI Visual Workstation series is an IA32-based workstation
301 based on SGI systems chips with some legacy PC hardware attached.
303 Say Y here to create a kernel to run on the SGI 320 or 540.
305 A kernel compiled for the Visual Workstation will not run on PCs
306 and vice versa. See <file:Documentation/sgi-visws.txt> for details.
308 config X86_GENERICARCH
309 bool "Generic architecture (Summit, bigsmp, ES7000, default)"
312 This option compiles in the Summit, bigsmp, ES7000, default subarchitectures.
313 It is intended for a generic binary kernel.
314 If you want a NUMA kernel, select ACPI. We need SRAT for NUMA.
317 bool "Support for Unisys ES7000 IA32 series"
318 depends on X86_32 && SMP
320 Support for Unisys ES7000 systems. Say 'Y' here if this kernel is
321 supposed to run on an IA32-based Unisys ES7000 system.
322 Only choose this option if you have such a system, otherwise you
326 bool "RDC R-321x SoC"
329 select X86_REBOOTFIXUPS
335 This option is needed for RDC R-321x system-on-chip, also known
337 If you don't have one of these chips, you should say N here.
340 bool "Support for ScaleMP vSMP"
344 Support for ScaleMP vSMP systems. Say 'Y' here if this kernel is
345 supposed to run on these EM64T-based machines. Only choose this option
346 if you have one of these machines.
350 config SCHED_NO_NO_OMIT_FRAME_POINTER
352 prompt "Single-depth WCHAN output"
355 Calculate simpler /proc/<PID>/wchan values. If this option
356 is disabled then wchan values will recurse back to the
357 caller function. This provides more accurate wchan values,
358 at the expense of slightly more scheduling overhead.
360 If in doubt, say "Y".
362 menuconfig PARAVIRT_GUEST
363 bool "Paravirtualized guest support"
365 Say Y here to get to see options related to running Linux under
366 various hypervisors. This option alone does not add any kernel code.
368 If you say N, all options in this submenu will be skipped and disabled.
372 source "arch/x86/xen/Kconfig"
375 bool "VMI Guest support"
378 depends on !(X86_VISWS || X86_VOYAGER)
380 VMI provides a paravirtualized interface to the VMware ESX server
381 (it could be used by other hypervisors in theory too, but is not
382 at the moment), by linking the kernel to a GPL-ed ROM module
383 provided by the hypervisor.
386 bool "KVM paravirtualized clock"
388 depends on !(X86_VISWS || X86_VOYAGER)
390 Turning on this option will allow you to run a paravirtualized clock
391 when running over the KVM hypervisor. Instead of relying on a PIT
392 (or probably other) emulation by the underlying device model, the host
393 provides the guest with timing infrastructure such as time of day, and
397 bool "KVM Guest support"
399 depends on !(X86_VISWS || X86_VOYAGER)
401 This option enables various optimizations for running under the KVM
404 source "arch/x86/lguest/Kconfig"
407 bool "Enable paravirtualization code"
408 depends on !(X86_VISWS || X86_VOYAGER)
410 This changes the kernel so it can modify itself when it is run
411 under a hypervisor, potentially improving performance significantly
412 over full virtualization. However, when run without a hypervisor
413 the kernel is theoretically slower and slightly larger.
417 config MEMTEST_BOOTPARAM
418 bool "Memtest boot parameter"
422 This option adds a kernel parameter 'memtest', which allows memtest
423 to be disabled at boot. If this option is selected, memtest
424 functionality can be disabled with memtest=0 on the kernel
425 command line. The purpose of this option is to allow a single
426 kernel image to be distributed with memtest built in, but not
429 If you are unsure how to answer this question, answer Y.
431 config MEMTEST_BOOTPARAM_VALUE
432 int "Memtest boot parameter default value (0-4)"
433 depends on MEMTEST_BOOTPARAM
437 This option sets the default value for the kernel parameter
438 'memtest', which allows memtest to be disabled at boot. If this
439 option is set to 0 (zero), the memtest kernel parameter will
440 default to 0, disabling memtest at bootup. If this option is
441 set to 4, the memtest kernel parameter will default to 4,
442 enabling memtest at bootup, and use that as pattern number.
444 If you are unsure how to answer this question, answer 0.
448 depends on X86_32 && ACPI && NUMA && (X86_SUMMIT || X86_GENERICARCH)
451 config HAVE_ARCH_PARSE_SRAT
455 config X86_SUMMIT_NUMA
457 depends on X86_32 && NUMA && (X86_SUMMIT || X86_GENERICARCH)
459 config X86_CYCLONE_TIMER
461 depends on X86_32 && X86_SUMMIT || X86_GENERICARCH
463 config ES7000_CLUSTERED_APIC
465 depends on SMP && X86_ES7000 && MPENTIUMIII
467 source "arch/x86/Kconfig.cpu"
471 prompt "HPET Timer Support" if X86_32
473 Use the IA-PC HPET (High Precision Event Timer) to manage
474 time in preference to the PIT and RTC, if a HPET is
476 HPET is the next generation timer replacing legacy 8254s.
477 The HPET provides a stable time base on SMP
478 systems, unlike the TSC, but it is more expensive to access,
479 as it is off-chip. You can find the HPET spec at
480 <http://www.intel.com/hardwaredesign/hpetspec.htm>.
482 You can safely choose Y here. However, HPET will only be
483 activated if the platform and the BIOS support this feature.
484 Otherwise the 8254 will be used for timing services.
486 Choose N to continue using the legacy 8254 timer.
488 config HPET_EMULATE_RTC
490 depends on HPET_TIMER && (RTC=y || RTC=m || RTC_DRV_CMOS=m || RTC_DRV_CMOS=y)
492 # Mark as embedded because too many people got it wrong.
493 # The code disables itself when not needed.
496 bool "Enable DMI scanning" if EMBEDDED
498 Enabled scanning of DMI to identify machine quirks. Say Y
499 here unless you have verified that your setup is not
500 affected by entries in the DMI blacklist. Required by PNP
504 bool "GART IOMMU support" if EMBEDDED
508 depends on X86_64 && PCI
510 Support for full DMA access of devices with 32bit memory access only
511 on systems with more than 3GB. This is usually needed for USB,
512 sound, many IDE/SATA chipsets and some other devices.
513 Provides a driver for the AMD Athlon64/Opteron/Turion/Sempron GART
514 based hardware IOMMU and a software bounce buffer based IOMMU used
515 on Intel systems and as fallback.
516 The code is only active when needed (enough memory and limited
517 device) unless CONFIG_IOMMU_DEBUG or iommu=force is specified
521 bool "IBM Calgary IOMMU support"
523 depends on X86_64 && PCI && EXPERIMENTAL
525 Support for hardware IOMMUs in IBM's xSeries x366 and x460
526 systems. Needed to run systems with more than 3GB of memory
527 properly with 32-bit PCI devices that do not support DAC
528 (Double Address Cycle). Calgary also supports bus level
529 isolation, where all DMAs pass through the IOMMU. This
530 prevents them from going anywhere except their intended
531 destination. This catches hard-to-find kernel bugs and
532 mis-behaving drivers and devices that do not use the DMA-API
533 properly to set up their DMA buffers. The IOMMU can be
534 turned off at boot time with the iommu=off parameter.
535 Normally the kernel will make the right choice by itself.
538 config CALGARY_IOMMU_ENABLED_BY_DEFAULT
540 prompt "Should Calgary be enabled by default?"
541 depends on CALGARY_IOMMU
543 Should Calgary be enabled by default? if you choose 'y', Calgary
544 will be used (if it exists). If you choose 'n', Calgary will not be
545 used even if it exists. If you choose 'n' and would like to use
546 Calgary anyway, pass 'iommu=calgary' on the kernel command line.
549 # need this always selected by IOMMU for the VIA workaround
553 Support for software bounce buffers used on x86-64 systems
554 which don't have a hardware IOMMU (e.g. the current generation
555 of Intel's x86-64 CPUs). Using this PCI devices which can only
556 access 32-bits of memory can be used on systems with more than
557 3 GB of memory. If unsure, say Y.
560 def_bool (CALGARY_IOMMU || GART_IOMMU || SWIOTLB)
563 int "Maximum number of CPUs (2-255)"
566 default "32" if X86_NUMAQ || X86_SUMMIT || X86_BIGSMP || X86_ES7000
569 This allows you to specify the maximum number of CPUs which this
570 kernel will support. The maximum supported value is 255 and the
571 minimum value which makes sense is 2.
573 This is purely to save memory - each supported CPU adds
574 approximately eight kilobytes to the kernel image.
577 bool "SMT (Hyperthreading) scheduler support"
580 SMT scheduler support improves the CPU scheduler's decision making
581 when dealing with Intel Pentium 4 chips with HyperThreading at a
582 cost of slightly increased overhead in some places. If unsure say
587 prompt "Multi-core scheduler support"
590 Multi-core scheduler support improves the CPU scheduler's decision
591 making when dealing with multi-core CPU chips at a cost of slightly
592 increased overhead in some places. If unsure say N here.
594 source "kernel/Kconfig.preempt"
597 bool "Local APIC support on uniprocessors"
598 depends on X86_32 && !SMP && !(X86_VISWS || X86_VOYAGER || X86_GENERICARCH)
600 A local APIC (Advanced Programmable Interrupt Controller) is an
601 integrated interrupt controller in the CPU. If you have a single-CPU
602 system which has a processor with a local APIC, you can say Y here to
603 enable and use it. If you say Y here even though your machine doesn't
604 have a local APIC, then the kernel will still run with no slowdown at
605 all. The local APIC supports CPU-generated self-interrupts (timer,
606 performance counters), and the NMI watchdog which detects hard
610 bool "IO-APIC support on uniprocessors"
611 depends on X86_UP_APIC
613 An IO-APIC (I/O Advanced Programmable Interrupt Controller) is an
614 SMP-capable replacement for PC-style interrupt controllers. Most
615 SMP systems and many recent uniprocessor systems have one.
617 If you have a single-CPU system with an IO-APIC, you can say Y here
618 to use it. If you say Y here even though your machine doesn't have
619 an IO-APIC, then the kernel will still run with no slowdown at all.
621 config X86_LOCAL_APIC
623 depends on X86_64 || (X86_32 && (X86_UP_APIC || ((X86_VISWS || SMP) && !X86_VOYAGER) || X86_GENERICARCH))
627 depends on X86_64 || (X86_32 && (X86_UP_IOAPIC || (SMP && !(X86_VISWS || X86_VOYAGER)) || X86_GENERICARCH))
629 config X86_VISWS_APIC
631 depends on X86_32 && X86_VISWS
634 bool "Machine Check Exception"
635 depends on !X86_VOYAGER
637 Machine Check Exception support allows the processor to notify the
638 kernel if it detects a problem (e.g. overheating, component failure).
639 The action the kernel takes depends on the severity of the problem,
640 ranging from a warning message on the console, to halting the machine.
641 Your processor must be a Pentium or newer to support this - check the
642 flags in /proc/cpuinfo for mce. Note that some older Pentium systems
643 have a design flaw which leads to false MCE events - hence MCE is
644 disabled on all P5 processors, unless explicitly enabled with "mce"
645 as a boot argument. Similarly, if MCE is built in and creates a
646 problem on some new non-standard machine, you can boot with "nomce"
647 to disable it. MCE support simply ignores non-MCE processors like
648 the 386 and 486, so nearly everyone can say Y here.
652 prompt "Intel MCE features"
653 depends on X86_64 && X86_MCE && X86_LOCAL_APIC
655 Additional support for intel specific MCE features such as
660 prompt "AMD MCE features"
661 depends on X86_64 && X86_MCE && X86_LOCAL_APIC
663 Additional support for AMD specific MCE features such as
664 the DRAM Error Threshold.
666 config X86_MCE_NONFATAL
667 tristate "Check for non-fatal errors on AMD Athlon/Duron / Intel Pentium 4"
668 depends on X86_32 && X86_MCE
670 Enabling this feature starts a timer that triggers every 5 seconds which
671 will look at the machine check registers to see if anything happened.
672 Non-fatal problems automatically get corrected (but still logged).
673 Disable this if you don't want to see these messages.
674 Seeing the messages this option prints out may be indicative of dying
675 or out-of-spec (ie, overclocked) hardware.
676 This option only does something on certain CPUs.
677 (AMD Athlon/Duron and Intel Pentium 4)
679 config X86_MCE_P4THERMAL
680 bool "check for P4 thermal throttling interrupt."
681 depends on X86_32 && X86_MCE && (X86_UP_APIC || SMP) && !X86_VISWS
683 Enabling this feature will cause a message to be printed when the P4
684 enters thermal throttling.
687 bool "Enable VM86 support" if EMBEDDED
691 This option is required by programs like DOSEMU to run 16-bit legacy
692 code on X86 processors. It also may be needed by software like
693 XFree86 to initialize some video cards via BIOS. Disabling this
694 option saves about 6k.
697 tristate "Toshiba Laptop support"
700 This adds a driver to safely access the System Management Mode of
701 the CPU on Toshiba portables with a genuine Toshiba BIOS. It does
702 not work on models with a Phoenix BIOS. The System Management Mode
703 is used to set the BIOS and power saving options on Toshiba portables.
705 For information on utilities to make use of this driver see the
706 Toshiba Linux utilities web site at:
707 <http://www.buzzard.org.uk/toshiba/>.
709 Say Y if you intend to run this kernel on a Toshiba portable.
713 tristate "Dell laptop support"
715 This adds a driver to safely access the System Management Mode
716 of the CPU on the Dell Inspiron 8000. The System Management Mode
717 is used to read cpu temperature and cooling fan status and to
718 control the fans on the I8K portables.
720 This driver has been tested only on the Inspiron 8000 but it may
721 also work with other Dell laptops. You can force loading on other
722 models by passing the parameter `force=1' to the module. Use at
725 For information on utilities to make use of this driver see the
726 I8K Linux utilities web site at:
727 <http://people.debian.org/~dz/i8k/>
729 Say Y if you intend to run this kernel on a Dell Inspiron 8000.
732 config X86_REBOOTFIXUPS
734 prompt "Enable X86 board specific fixups for reboot"
735 depends on X86_32 && X86
737 This enables chipset and/or board specific fixups to be done
738 in order to get reboot to work correctly. This is only needed on
739 some combinations of hardware and BIOS. The symptom, for which
740 this config is intended, is when reboot ends with a stalled/hung
743 Currently, the only fixup is for the Geode machines using
744 CS5530A and CS5536 chipsets and the RDC R-321x SoC.
746 Say Y if you want to enable the fixup. Currently, it's safe to
747 enable this option even if you don't need it.
751 tristate "/dev/cpu/microcode - Intel IA32 CPU microcode support"
754 If you say Y here, you will be able to update the microcode on
755 Intel processors in the IA32 family, e.g. Pentium Pro, Pentium II,
756 Pentium III, Pentium 4, Xeon etc. You will obviously need the
757 actual microcode binary data itself which is not shipped with the
760 For latest news and information on obtaining all the required
761 ingredients for this driver, check:
762 <http://www.urbanmyth.org/microcode/>.
764 To compile this driver as a module, choose M here: the
765 module will be called microcode.
767 config MICROCODE_OLD_INTERFACE
772 tristate "/dev/cpu/*/msr - Model-specific register support"
774 This device gives privileged processes access to the x86
775 Model-Specific Registers (MSRs). It is a character device with
776 major 202 and minors 0 to 31 for /dev/cpu/0/msr to /dev/cpu/31/msr.
777 MSR accesses are directed to a specific CPU on multi-processor
781 tristate "/dev/cpu/*/cpuid - CPU information support"
783 This device gives processes access to the x86 CPUID instruction to
784 be executed on a specific processor. It is a character device
785 with major 203 and minors 0 to 31 for /dev/cpu/0/cpuid to
789 prompt "High Memory Support"
790 default HIGHMEM4G if !X86_NUMAQ
791 default HIGHMEM64G if X86_NUMAQ
796 depends on !X86_NUMAQ
798 Linux can use up to 64 Gigabytes of physical memory on x86 systems.
799 However, the address space of 32-bit x86 processors is only 4
800 Gigabytes large. That means that, if you have a large amount of
801 physical memory, not all of it can be "permanently mapped" by the
802 kernel. The physical memory that's not permanently mapped is called
805 If you are compiling a kernel which will never run on a machine with
806 more than 1 Gigabyte total physical RAM, answer "off" here (default
807 choice and suitable for most users). This will result in a "3GB/1GB"
808 split: 3GB are mapped so that each process sees a 3GB virtual memory
809 space and the remaining part of the 4GB virtual memory space is used
810 by the kernel to permanently map as much physical memory as
813 If the machine has between 1 and 4 Gigabytes physical RAM, then
816 If more than 4 Gigabytes is used then answer "64GB" here. This
817 selection turns Intel PAE (Physical Address Extension) mode on.
818 PAE implements 3-level paging on IA32 processors. PAE is fully
819 supported by Linux, PAE mode is implemented on all recent Intel
820 processors (Pentium Pro and better). NOTE: If you say "64GB" here,
821 then the kernel will not boot on CPUs that don't support PAE!
823 The actual amount of total physical memory will either be
824 auto detected or can be forced by using a kernel command line option
825 such as "mem=256M". (Try "man bootparam" or see the documentation of
826 your boot loader (lilo or loadlin) about how to pass options to the
827 kernel at boot time.)
829 If unsure, say "off".
833 depends on !X86_NUMAQ
835 Select this if you have a 32-bit processor and between 1 and 4
836 gigabytes of physical RAM.
840 depends on !M386 && !M486
843 Select this if you have a 32-bit processor and more than 4
844 gigabytes of physical RAM.
849 depends on EXPERIMENTAL
850 prompt "Memory split" if EMBEDDED
854 Select the desired split between kernel and user memory.
856 If the address range available to the kernel is less than the
857 physical memory installed, the remaining memory will be available
858 as "high memory". Accessing high memory is a little more costly
859 than low memory, as it needs to be mapped into the kernel first.
860 Note that increasing the kernel address space limits the range
861 available to user programs, making the address space there
862 tighter. Selecting anything other than the default 3G/1G split
863 will also likely make your kernel incompatible with binary-only
866 If you are not absolutely sure what you are doing, leave this
870 bool "3G/1G user/kernel split"
871 config VMSPLIT_3G_OPT
873 bool "3G/1G user/kernel split (for full 1G low memory)"
875 bool "2G/2G user/kernel split"
876 config VMSPLIT_2G_OPT
878 bool "2G/2G user/kernel split (for full 2G low memory)"
880 bool "1G/3G user/kernel split"
885 default 0xB0000000 if VMSPLIT_3G_OPT
886 default 0x80000000 if VMSPLIT_2G
887 default 0x78000000 if VMSPLIT_2G_OPT
888 default 0x40000000 if VMSPLIT_1G
894 depends on X86_32 && (HIGHMEM64G || HIGHMEM4G)
898 prompt "PAE (Physical Address Extension) Support"
899 depends on X86_32 && !HIGHMEM4G
900 select RESOURCES_64BIT
902 PAE is required for NX support, and furthermore enables
903 larger swapspace support for non-overcommit purposes. It
904 has the cost of more pagetable lookup overhead, and also
905 consumes more pagetable space per process.
907 # Common NUMA Features
909 bool "Numa Memory Allocation and Scheduler Support (EXPERIMENTAL)"
911 depends on X86_64 || (X86_32 && HIGHMEM64G && (X86_NUMAQ || (X86_SUMMIT || X86_GENERICARCH) && ACPI) && EXPERIMENTAL)
913 default y if (X86_NUMAQ || X86_SUMMIT)
915 Enable NUMA (Non Uniform Memory Access) support.
916 The kernel will try to allocate memory used by a CPU on the
917 local memory controller of the CPU and add some more
918 NUMA awareness to the kernel.
920 For i386 this is currently highly experimental and should be only
921 used for kernel development. It might also cause boot failures.
922 For x86_64 this is recommended on all multiprocessor Opteron systems.
923 If the system is EM64T, you should say N unless your system is
926 comment "NUMA (Summit) requires SMP, 64GB highmem support, ACPI"
927 depends on X86_32 && X86_SUMMIT && (!HIGHMEM64G || !ACPI)
931 prompt "Old style AMD Opteron NUMA detection"
932 depends on X86_64 && NUMA && PCI
934 Enable K8 NUMA node topology detection. You should say Y here if
935 you have a multi processor AMD K8 system. This uses an old
936 method to read the NUMA configuration directly from the builtin
937 Northbridge of Opteron. It is recommended to use X86_64_ACPI_NUMA
938 instead, which also takes priority if both are compiled in.
940 config X86_64_ACPI_NUMA
942 prompt "ACPI NUMA detection"
943 depends on X86_64 && NUMA && ACPI && PCI
946 Enable ACPI SRAT based node topology detection.
948 # Some NUMA nodes have memory ranges that span
949 # other nodes. Even though a pfn is valid and
950 # between a node's start and end pfns, it may not
951 # reside on that node. See memmap_init_zone()
953 config NODES_SPAN_OTHER_NODES
955 depends on X86_64_ACPI_NUMA
958 bool "NUMA emulation"
959 depends on X86_64 && NUMA
961 Enable NUMA emulation. A flat machine will be split
962 into virtual nodes when booted with "numa=fake=N", where N is the
963 number of nodes. This is only useful for debugging.
966 int "Max num nodes shift(1-15)"
968 default "6" if X86_64
969 default "4" if X86_NUMAQ
971 depends on NEED_MULTIPLE_NODES
973 config HAVE_ARCH_BOOTMEM_NODE
975 depends on X86_32 && NUMA
977 config ARCH_HAVE_MEMORY_PRESENT
979 depends on X86_32 && DISCONTIGMEM
981 config NEED_NODE_MEMMAP_SIZE
983 depends on X86_32 && (DISCONTIGMEM || SPARSEMEM)
985 config HAVE_ARCH_ALLOC_REMAP
987 depends on X86_32 && NUMA
989 config ARCH_FLATMEM_ENABLE
991 depends on X86_32 && ARCH_SELECT_MEMORY_MODEL && X86_PC && !NUMA
993 config ARCH_DISCONTIGMEM_ENABLE
995 depends on NUMA && X86_32
997 config ARCH_DISCONTIGMEM_DEFAULT
999 depends on NUMA && X86_32
1001 config ARCH_SPARSEMEM_DEFAULT
1005 config ARCH_SPARSEMEM_ENABLE
1007 depends on X86_64 || NUMA || (EXPERIMENTAL && X86_PC)
1008 select SPARSEMEM_STATIC if X86_32
1009 select SPARSEMEM_VMEMMAP_ENABLE if X86_64
1011 config ARCH_SELECT_MEMORY_MODEL
1013 depends on ARCH_SPARSEMEM_ENABLE
1015 config ARCH_MEMORY_PROBE
1017 depends on MEMORY_HOTPLUG
1022 bool "Allocate 3rd-level pagetables from highmem"
1023 depends on X86_32 && (HIGHMEM4G || HIGHMEM64G)
1025 The VM uses one page table entry for each page of physical memory.
1026 For systems with a lot of RAM, this can be wasteful of precious
1027 low memory. Setting this option will put user-space page table
1028 entries in high memory.
1030 config MATH_EMULATION
1032 prompt "Math emulation" if X86_32
1034 Linux can emulate a math coprocessor (used for floating point
1035 operations) if you don't have one. 486DX and Pentium processors have
1036 a math coprocessor built in, 486SX and 386 do not, unless you added
1037 a 487DX or 387, respectively. (The messages during boot time can
1038 give you some hints here ["man dmesg"].) Everyone needs either a
1039 coprocessor or this emulation.
1041 If you don't have a math coprocessor, you need to say Y here; if you
1042 say Y here even though you have a coprocessor, the coprocessor will
1043 be used nevertheless. (This behavior can be changed with the kernel
1044 command line option "no387", which comes handy if your coprocessor
1045 is broken. Try "man bootparam" or see the documentation of your boot
1046 loader (lilo or loadlin) about how to pass options to the kernel at
1047 boot time.) This means that it is a good idea to say Y here if you
1048 intend to use this kernel on different machines.
1050 More information about the internals of the Linux math coprocessor
1051 emulation can be found in <file:arch/x86/math-emu/README>.
1053 If you are not sure, say Y; apart from resulting in a 66 KB bigger
1054 kernel, it won't hurt.
1057 bool "MTRR (Memory Type Range Register) support"
1059 On Intel P6 family processors (Pentium Pro, Pentium II and later)
1060 the Memory Type Range Registers (MTRRs) may be used to control
1061 processor access to memory ranges. This is most useful if you have
1062 a video (VGA) card on a PCI or AGP bus. Enabling write-combining
1063 allows bus write transfers to be combined into a larger transfer
1064 before bursting over the PCI/AGP bus. This can increase performance
1065 of image write operations 2.5 times or more. Saying Y here creates a
1066 /proc/mtrr file which may be used to manipulate your processor's
1067 MTRRs. Typically the X server should use this.
1069 This code has a reasonably generic interface so that similar
1070 control registers on other processors can be easily supported
1073 The Cyrix 6x86, 6x86MX and M II processors have Address Range
1074 Registers (ARRs) which provide a similar functionality to MTRRs. For
1075 these, the ARRs are used to emulate the MTRRs.
1076 The AMD K6-2 (stepping 8 and above) and K6-3 processors have two
1077 MTRRs. The Centaur C6 (WinChip) has 8 MCRs, allowing
1078 write-combining. All of these processors are supported by this code
1079 and it makes sense to say Y here if you have one of them.
1081 Saying Y here also fixes a problem with buggy SMP BIOSes which only
1082 set the MTRRs for the boot CPU and not for the secondary CPUs. This
1083 can lead to all sorts of problems, so it's good to say Y here.
1085 You can safely say Y even if your machine doesn't have MTRRs, you'll
1086 just add about 9 KB to your kernel.
1088 See <file:Documentation/mtrr.txt> for more information.
1092 prompt "x86 PAT support"
1095 Use PAT attributes to setup page level cache control.
1097 PATs are the modern equivalents of MTRRs and are much more
1098 flexible than MTRRs.
1100 Say N here if you see bootup problems (boot crash, boot hang,
1101 spontaneous reboots) or a non-working video driver.
1107 prompt "EFI runtime service support"
1110 This enables the kernel to use EFI runtime services that are
1111 available (such as the EFI variable services).
1113 This option is only useful on systems that have EFI firmware.
1114 In addition, you should use the latest ELILO loader available
1115 at <http://elilo.sourceforge.net> in order to take advantage
1116 of EFI runtime services. However, even with this option, the
1117 resultant kernel should continue to boot on existing non-EFI
1122 prompt "Enable kernel irq balancing"
1123 depends on X86_32 && SMP && X86_IO_APIC
1125 The default yes will allow the kernel to do irq load balancing.
1126 Saying no will keep the kernel from doing irq load balancing.
1130 prompt "Enable seccomp to safely compute untrusted bytecode"
1133 This kernel feature is useful for number crunching applications
1134 that may need to compute untrusted bytecode during their
1135 execution. By using pipes or other transports made available to
1136 the process as file descriptors supporting the read/write
1137 syscalls, it's possible to isolate those applications in
1138 their own address space using seccomp. Once seccomp is
1139 enabled via /proc/<pid>/seccomp, it cannot be disabled
1140 and the task is only allowed to execute a few safe syscalls
1141 defined by each seccomp mode.
1143 If unsure, say Y. Only embedded should say N here.
1145 config CC_STACKPROTECTOR
1146 bool "Enable -fstack-protector buffer overflow detection (EXPERIMENTAL)"
1147 depends on X86_64 && EXPERIMENTAL && BROKEN
1149 This option turns on the -fstack-protector GCC feature. This
1150 feature puts, at the beginning of critical functions, a canary
1151 value on the stack just before the return address, and validates
1152 the value just before actually returning. Stack based buffer
1153 overflows (that need to overwrite this return address) now also
1154 overwrite the canary, which gets detected and the attack is then
1155 neutralized via a kernel panic.
1157 This feature requires gcc version 4.2 or above, or a distribution
1158 gcc with the feature backported. Older versions are automatically
1159 detected and for those versions, this configuration option is ignored.
1161 config CC_STACKPROTECTOR_ALL
1162 bool "Use stack-protector for all functions"
1163 depends on CC_STACKPROTECTOR
1165 Normally, GCC only inserts the canary value protection for
1166 functions that use large-ish on-stack buffers. By enabling
1167 this option, GCC will be asked to do this for ALL functions.
1169 source kernel/Kconfig.hz
1172 bool "kexec system call"
1173 depends on X86_BIOS_REBOOT
1175 kexec is a system call that implements the ability to shutdown your
1176 current kernel, and to start another kernel. It is like a reboot
1177 but it is independent of the system firmware. And like a reboot
1178 you can start any kernel with it, not just Linux.
1180 The name comes from the similarity to the exec system call.
1182 It is an ongoing process to be certain the hardware in a machine
1183 is properly shutdown, so do not be surprised if this code does not
1184 initially work for you. It may help to enable device hotplugging
1185 support. As of this writing the exact hardware interface is
1186 strongly in flux, so no good recommendation can be made.
1189 bool "kernel crash dumps (EXPERIMENTAL)"
1190 depends on EXPERIMENTAL
1191 depends on X86_64 || (X86_32 && HIGHMEM)
1193 Generate crash dump after being started by kexec.
1194 This should be normally only set in special crash dump kernels
1195 which are loaded in the main kernel with kexec-tools into
1196 a specially reserved region and then later executed after
1197 a crash by kdump/kexec. The crash dump kernel must be compiled
1198 to a memory address not used by the main kernel or BIOS using
1199 PHYSICAL_START, or it must be built as a relocatable image
1200 (CONFIG_RELOCATABLE=y).
1201 For more details see Documentation/kdump/kdump.txt
1203 config PHYSICAL_START
1204 hex "Physical address where the kernel is loaded" if (EMBEDDED || CRASH_DUMP)
1205 default "0x1000000" if X86_NUMAQ
1206 default "0x200000" if X86_64
1209 This gives the physical address where the kernel is loaded.
1211 If kernel is a not relocatable (CONFIG_RELOCATABLE=n) then
1212 bzImage will decompress itself to above physical address and
1213 run from there. Otherwise, bzImage will run from the address where
1214 it has been loaded by the boot loader and will ignore above physical
1217 In normal kdump cases one does not have to set/change this option
1218 as now bzImage can be compiled as a completely relocatable image
1219 (CONFIG_RELOCATABLE=y) and be used to load and run from a different
1220 address. This option is mainly useful for the folks who don't want
1221 to use a bzImage for capturing the crash dump and want to use a
1222 vmlinux instead. vmlinux is not relocatable hence a kernel needs
1223 to be specifically compiled to run from a specific memory area
1224 (normally a reserved region) and this option comes handy.
1226 So if you are using bzImage for capturing the crash dump, leave
1227 the value here unchanged to 0x100000 and set CONFIG_RELOCATABLE=y.
1228 Otherwise if you plan to use vmlinux for capturing the crash dump
1229 change this value to start of the reserved region (Typically 16MB
1230 0x1000000). In other words, it can be set based on the "X" value as
1231 specified in the "crashkernel=YM@XM" command line boot parameter
1232 passed to the panic-ed kernel. Typically this parameter is set as
1233 crashkernel=64M@16M. Please take a look at
1234 Documentation/kdump/kdump.txt for more details about crash dumps.
1236 Usage of bzImage for capturing the crash dump is recommended as
1237 one does not have to build two kernels. Same kernel can be used
1238 as production kernel and capture kernel. Above option should have
1239 gone away after relocatable bzImage support is introduced. But it
1240 is present because there are users out there who continue to use
1241 vmlinux for dump capture. This option should go away down the
1244 Don't change this unless you know what you are doing.
1247 bool "Build a relocatable kernel (EXPERIMENTAL)"
1248 depends on EXPERIMENTAL
1250 This builds a kernel image that retains relocation information
1251 so it can be loaded someplace besides the default 1MB.
1252 The relocations tend to make the kernel binary about 10% larger,
1253 but are discarded at runtime.
1255 One use is for the kexec on panic case where the recovery kernel
1256 must live at a different physical address than the primary
1259 Note: If CONFIG_RELOCATABLE=y, then the kernel runs from the address
1260 it has been loaded at and the compile time physical address
1261 (CONFIG_PHYSICAL_START) is ignored.
1263 config PHYSICAL_ALIGN
1265 prompt "Alignment value to which kernel should be aligned" if X86_32
1266 default "0x100000" if X86_32
1267 default "0x200000" if X86_64
1268 range 0x2000 0x400000
1270 This value puts the alignment restrictions on physical address
1271 where kernel is loaded and run from. Kernel is compiled for an
1272 address which meets above alignment restriction.
1274 If bootloader loads the kernel at a non-aligned address and
1275 CONFIG_RELOCATABLE is set, kernel will move itself to nearest
1276 address aligned to above value and run from there.
1278 If bootloader loads the kernel at a non-aligned address and
1279 CONFIG_RELOCATABLE is not set, kernel will ignore the run time
1280 load address and decompress itself to the address it has been
1281 compiled for and run from there. The address for which kernel is
1282 compiled already meets above alignment restrictions. Hence the
1283 end result is that kernel runs from a physical address meeting
1284 above alignment restrictions.
1286 Don't change this unless you know what you are doing.
1289 bool "Support for suspend on SMP and hot-pluggable CPUs (EXPERIMENTAL)"
1290 depends on SMP && HOTPLUG && EXPERIMENTAL && !X86_VOYAGER
1292 Say Y here to experiment with turning CPUs off and on, and to
1293 enable suspend on SMP systems. CPUs can be controlled through
1294 /sys/devices/system/cpu.
1295 Say N if you want to disable CPU hotplug and don't need to
1300 prompt "Compat VDSO support"
1301 depends on X86_32 || IA32_EMULATION
1303 Map the 32-bit VDSO to the predictable old-style address too.
1305 Say N here if you are running a sufficiently recent glibc
1306 version (2.3.3 or later), to remove the high-mapped
1307 VDSO mapping and to exclusively use the randomized VDSO.
1313 config ARCH_ENABLE_MEMORY_HOTPLUG
1315 depends on X86_64 || (X86_32 && HIGHMEM)
1317 config HAVE_ARCH_EARLY_PFN_TO_NID
1321 menu "Power management options"
1322 depends on !X86_VOYAGER
1324 config ARCH_HIBERNATION_HEADER
1326 depends on X86_64 && HIBERNATION
1328 source "kernel/power/Kconfig"
1330 source "drivers/acpi/Kconfig"
1335 depends on APM || APM_MODULE
1338 tristate "APM (Advanced Power Management) BIOS support"
1339 depends on X86_32 && PM_SLEEP && !X86_VISWS
1341 APM is a BIOS specification for saving power using several different
1342 techniques. This is mostly useful for battery powered laptops with
1343 APM compliant BIOSes. If you say Y here, the system time will be
1344 reset after a RESUME operation, the /proc/apm device will provide
1345 battery status information, and user-space programs will receive
1346 notification of APM "events" (e.g. battery status change).
1348 If you select "Y" here, you can disable actual use of the APM
1349 BIOS by passing the "apm=off" option to the kernel at boot time.
1351 Note that the APM support is almost completely disabled for
1352 machines with more than one CPU.
1354 In order to use APM, you will need supporting software. For location
1355 and more information, read <file:Documentation/power/pm.txt> and the
1356 Battery Powered Linux mini-HOWTO, available from
1357 <http://www.tldp.org/docs.html#howto>.
1359 This driver does not spin down disk drives (see the hdparm(8)
1360 manpage ("man 8 hdparm") for that), and it doesn't turn off
1361 VESA-compliant "green" monitors.
1363 This driver does not support the TI 4000M TravelMate and the ACER
1364 486/DX4/75 because they don't have compliant BIOSes. Many "green"
1365 desktop machines also don't have compliant BIOSes, and this driver
1366 may cause those machines to panic during the boot phase.
1368 Generally, if you don't have a battery in your machine, there isn't
1369 much point in using this driver and you should say N. If you get
1370 random kernel OOPSes or reboots that don't seem to be related to
1371 anything, try disabling/enabling this option (or disabling/enabling
1374 Some other things you should try when experiencing seemingly random,
1377 1) make sure that you have enough swap space and that it is
1379 2) pass the "no-hlt" option to the kernel
1380 3) switch on floating point emulation in the kernel and pass
1381 the "no387" option to the kernel
1382 4) pass the "floppy=nodma" option to the kernel
1383 5) pass the "mem=4M" option to the kernel (thereby disabling
1384 all but the first 4 MB of RAM)
1385 6) make sure that the CPU is not over clocked.
1386 7) read the sig11 FAQ at <http://www.bitwizard.nl/sig11/>
1387 8) disable the cache from your BIOS settings
1388 9) install a fan for the video card or exchange video RAM
1389 10) install a better fan for the CPU
1390 11) exchange RAM chips
1391 12) exchange the motherboard.
1393 To compile this driver as a module, choose M here: the
1394 module will be called apm.
1398 config APM_IGNORE_USER_SUSPEND
1399 bool "Ignore USER SUSPEND"
1401 This option will ignore USER SUSPEND requests. On machines with a
1402 compliant APM BIOS, you want to say N. However, on the NEC Versa M
1403 series notebooks, it is necessary to say Y because of a BIOS bug.
1405 config APM_DO_ENABLE
1406 bool "Enable PM at boot time"
1408 Enable APM features at boot time. From page 36 of the APM BIOS
1409 specification: "When disabled, the APM BIOS does not automatically
1410 power manage devices, enter the Standby State, enter the Suspend
1411 State, or take power saving steps in response to CPU Idle calls."
1412 This driver will make CPU Idle calls when Linux is idle (unless this
1413 feature is turned off -- see "Do CPU IDLE calls", below). This
1414 should always save battery power, but more complicated APM features
1415 will be dependent on your BIOS implementation. You may need to turn
1416 this option off if your computer hangs at boot time when using APM
1417 support, or if it beeps continuously instead of suspending. Turn
1418 this off if you have a NEC UltraLite Versa 33/C or a Toshiba
1419 T400CDT. This is off by default since most machines do fine without
1423 bool "Make CPU Idle calls when idle"
1425 Enable calls to APM CPU Idle/CPU Busy inside the kernel's idle loop.
1426 On some machines, this can activate improved power savings, such as
1427 a slowed CPU clock rate, when the machine is idle. These idle calls
1428 are made after the idle loop has run for some length of time (e.g.,
1429 333 mS). On some machines, this will cause a hang at boot time or
1430 whenever the CPU becomes idle. (On machines with more than one CPU,
1431 this option does nothing.)
1433 config APM_DISPLAY_BLANK
1434 bool "Enable console blanking using APM"
1436 Enable console blanking using the APM. Some laptops can use this to
1437 turn off the LCD backlight when the screen blanker of the Linux
1438 virtual console blanks the screen. Note that this is only used by
1439 the virtual console screen blanker, and won't turn off the backlight
1440 when using the X Window system. This also doesn't have anything to
1441 do with your VESA-compliant power-saving monitor. Further, this
1442 option doesn't work for all laptops -- it might not turn off your
1443 backlight at all, or it might print a lot of errors to the console,
1444 especially if you are using gpm.
1446 config APM_ALLOW_INTS
1447 bool "Allow interrupts during APM BIOS calls"
1449 Normally we disable external interrupts while we are making calls to
1450 the APM BIOS as a measure to lessen the effects of a badly behaving
1451 BIOS implementation. The BIOS should reenable interrupts if it
1452 needs to. Unfortunately, some BIOSes do not -- especially those in
1453 many of the newer IBM Thinkpads. If you experience hangs when you
1454 suspend, try setting this to Y. Otherwise, say N.
1456 config APM_REAL_MODE_POWER_OFF
1457 bool "Use real mode APM BIOS call to power off"
1459 Use real mode APM BIOS calls to switch off the computer. This is
1460 a work-around for a number of buggy BIOSes. Switch this option on if
1461 your computer crashes instead of powering off properly.
1465 source "arch/x86/kernel/cpu/cpufreq/Kconfig"
1467 source "drivers/cpuidle/Kconfig"
1472 menu "Bus options (PCI etc.)"
1475 bool "PCI support" if !X86_VISWS && !X86_VSMP
1476 depends on !X86_VOYAGER
1478 select ARCH_SUPPORTS_MSI if (X86_LOCAL_APIC && X86_IO_APIC)
1480 Find out whether you have a PCI motherboard. PCI is the name of a
1481 bus system, i.e. the way the CPU talks to the other stuff inside
1482 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
1483 VESA. If you have PCI, say Y, otherwise N.
1486 prompt "PCI access mode"
1487 depends on X86_32 && PCI && !X86_VISWS
1490 On PCI systems, the BIOS can be used to detect the PCI devices and
1491 determine their configuration. However, some old PCI motherboards
1492 have BIOS bugs and may crash if this is done. Also, some embedded
1493 PCI-based systems don't have any BIOS at all. Linux can also try to
1494 detect the PCI hardware directly without using the BIOS.
1496 With this option, you can specify how Linux should detect the
1497 PCI devices. If you choose "BIOS", the BIOS will be used,
1498 if you choose "Direct", the BIOS won't be used, and if you
1499 choose "MMConfig", then PCI Express MMCONFIG will be used.
1500 If you choose "Any", the kernel will try MMCONFIG, then the
1501 direct access method and falls back to the BIOS if that doesn't
1502 work. If unsure, go with the default, which is "Any".
1507 config PCI_GOMMCONFIG
1524 depends on X86_32 && !X86_VISWS && PCI && (PCI_GOBIOS || PCI_GOANY)
1526 # x86-64 doesn't support PCI BIOS access from long mode so always go direct.
1529 depends on PCI && (X86_64 || (PCI_GODIRECT || PCI_GOANY || PCI_GOOLPC) || X86_VISWS)
1533 depends on X86_32 && PCI && ACPI && (PCI_GOMMCONFIG || PCI_GOANY)
1537 depends on PCI && OLPC && (PCI_GOOLPC || PCI_GOANY)
1544 bool "Support mmconfig PCI config space access"
1545 depends on X86_64 && PCI && ACPI
1548 bool "Support for DMA Remapping Devices (EXPERIMENTAL)"
1549 depends on X86_64 && PCI_MSI && ACPI && EXPERIMENTAL
1551 DMA remapping (DMAR) devices support enables independent address
1552 translations for Direct Memory Access (DMA) from devices.
1553 These DMA remapping devices are reported via ACPI tables
1554 and include PCI device scope covered by these DMA
1559 prompt "Support for Graphics workaround"
1562 Current Graphics drivers tend to use physical address
1563 for DMA and avoid using DMA APIs. Setting this config
1564 option permits the IOMMU driver to set a unity map for
1565 all the OS-visible memory. Hence the driver can continue
1566 to use physical addresses for DMA.
1568 config DMAR_FLOPPY_WA
1572 Floppy disk drivers are know to bypass DMA API calls
1573 thereby failing to work when IOMMU is enabled. This
1574 workaround will setup a 1:1 mapping for the first
1575 16M to make floppy (an ISA device) work.
1577 source "drivers/pci/pcie/Kconfig"
1579 source "drivers/pci/Kconfig"
1581 # x86_64 have no ISA slots, but do have ISA-style DMA.
1589 depends on !(X86_VOYAGER || X86_VISWS)
1591 Find out whether you have ISA slots on your motherboard. ISA is the
1592 name of a bus system, i.e. the way the CPU talks to the other stuff
1593 inside your box. Other bus systems are PCI, EISA, MicroChannel
1594 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
1595 newer boards don't support it. If you have ISA, say Y, otherwise N.
1601 The Extended Industry Standard Architecture (EISA) bus was
1602 developed as an open alternative to the IBM MicroChannel bus.
1604 The EISA bus provided some of the features of the IBM MicroChannel
1605 bus while maintaining backward compatibility with cards made for
1606 the older ISA bus. The EISA bus saw limited use between 1988 and
1607 1995 when it was made obsolete by the PCI bus.
1609 Say Y here if you are building a kernel for an EISA-based machine.
1613 source "drivers/eisa/Kconfig"
1616 bool "MCA support" if !(X86_VISWS || X86_VOYAGER)
1617 default y if X86_VOYAGER
1619 MicroChannel Architecture is found in some IBM PS/2 machines and
1620 laptops. It is a bus system similar to PCI or ISA. See
1621 <file:Documentation/mca.txt> (and especially the web page given
1622 there) before attempting to build an MCA bus kernel.
1624 source "drivers/mca/Kconfig"
1627 tristate "NatSemi SCx200 support"
1628 depends on !X86_VOYAGER
1630 This provides basic support for National Semiconductor's
1631 (now AMD's) Geode processors. The driver probes for the
1632 PCI-IDs of several on-chip devices, so its a good dependency
1633 for other scx200_* drivers.
1635 If compiled as a module, the driver is named scx200.
1637 config SCx200HR_TIMER
1638 tristate "NatSemi SCx200 27MHz High-Resolution Timer Support"
1639 depends on SCx200 && GENERIC_TIME
1642 This driver provides a clocksource built upon the on-chip
1643 27MHz high-resolution timer. Its also a workaround for
1644 NSC Geode SC-1100's buggy TSC, which loses time when the
1645 processor goes idle (as is done by the scheduler). The
1646 other workaround is idle=poll boot option.
1648 config GEODE_MFGPT_TIMER
1650 prompt "Geode Multi-Function General Purpose Timer (MFGPT) events"
1651 depends on MGEODE_LX && GENERIC_TIME && GENERIC_CLOCKEVENTS
1653 This driver provides a clock event source based on the MFGPT
1654 timer(s) in the CS5535 and CS5536 companion chip for the geode.
1655 MFGPTs have a better resolution and max interval than the
1656 generic PIT, and are suitable for use as high-res timers.
1659 bool "One Laptop Per Child support"
1662 Add support for detecting the unique features of the OLPC
1669 depends on AGP_AMD64 || (X86_64 && (GART_IOMMU || (PCI && NUMA)))
1671 source "drivers/pcmcia/Kconfig"
1673 source "drivers/pci/hotplug/Kconfig"
1678 menu "Executable file formats / Emulations"
1680 source "fs/Kconfig.binfmt"
1682 config IA32_EMULATION
1683 bool "IA32 Emulation"
1685 select COMPAT_BINFMT_ELF
1687 Include code to run 32-bit programs under a 64-bit kernel. You should
1688 likely turn this on, unless you're 100% sure that you don't have any
1689 32-bit programs left.
1692 tristate "IA32 a.out support"
1693 depends on IA32_EMULATION && ARCH_SUPPORTS_AOUT
1695 Support old a.out binaries in the 32bit emulation.
1699 depends on IA32_EMULATION
1701 config COMPAT_FOR_U64_ALIGNMENT
1705 config SYSVIPC_COMPAT
1707 depends on X86_64 && COMPAT && SYSVIPC
1712 source "net/Kconfig"
1714 source "drivers/Kconfig"
1716 source "drivers/firmware/Kconfig"
1720 source "arch/x86/Kconfig.debug"
1722 source "security/Kconfig"
1724 source "crypto/Kconfig"
1726 source "arch/x86/kvm/Kconfig"
1728 source "lib/Kconfig"
projects / deliverable / linux.git / blob