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
24 select HAVE_IOREMAP_PROT
26 select ARCH_WANT_OPTIONAL_GPIOLIB
27 select HAVE_KRETPROBES
28 select HAVE_DYNAMIC_FTRACE
30 select HAVE_KVM if ((X86_32 && !X86_VOYAGER && !X86_VISWS && !X86_NUMAQ) || X86_64)
31 select HAVE_ARCH_KGDB if !X86_VOYAGER
32 select HAVE_GENERIC_DMA_COHERENT if X86_32
33 select HAVE_EFFICIENT_UNALIGNED_ACCESS
37 default "arch/x86/configs/i386_defconfig" if X86_32
38 default "arch/x86/configs/x86_64_defconfig" if X86_64
41 config GENERIC_LOCKBREAK
47 config GENERIC_CMOS_UPDATE
50 config CLOCKSOURCE_WATCHDOG
53 config GENERIC_CLOCKEVENTS
56 config GENERIC_CLOCKEVENTS_BROADCAST
58 depends on X86_64 || (X86_32 && X86_LOCAL_APIC)
60 config LOCKDEP_SUPPORT
63 config STACKTRACE_SUPPORT
66 config HAVE_LATENCYTOP_SUPPORT
69 config FAST_CMPXCHG_LOCAL
82 config GENERIC_ISA_DMA
92 config GENERIC_HWEIGHT
98 config ARCH_MAY_HAVE_PC_FDC
101 config RWSEM_GENERIC_SPINLOCK
104 config RWSEM_XCHGADD_ALGORITHM
107 config ARCH_HAS_ILOG2_U32
110 config ARCH_HAS_ILOG2_U64
113 config ARCH_HAS_CPU_IDLE_WAIT
116 config GENERIC_CALIBRATE_DELAY
119 config GENERIC_TIME_VSYSCALL
123 config ARCH_HAS_CPU_RELAX
126 config ARCH_HAS_DEFAULT_IDLE
129 config ARCH_HAS_CACHE_LINE_SIZE
132 config HAVE_SETUP_PER_CPU_AREA
133 def_bool X86_64_SMP || (X86_SMP && !X86_VOYAGER)
135 config HAVE_CPUMASK_OF_CPU_MAP
138 config ARCH_HIBERNATION_POSSIBLE
140 depends on !SMP || !X86_VOYAGER
142 config ARCH_SUSPEND_POSSIBLE
144 depends on !X86_VOYAGER
150 config ARCH_POPULATES_NODE_MAP
157 config ARCH_SUPPORTS_AOUT
160 config ARCH_SUPPORTS_OPTIMIZED_INLINING
163 # Use the generic interrupt handling code in kernel/irq/:
164 config GENERIC_HARDIRQS
168 config GENERIC_IRQ_PROBE
172 config GENERIC_PENDING_IRQ
174 depends on GENERIC_HARDIRQS && SMP
179 depends on SMP && ((X86_32 && !X86_VOYAGER) || X86_64)
180 select USE_GENERIC_SMP_HELPERS
185 depends on X86_32 && SMP
189 depends on X86_64 && SMP
194 depends on (X86_32 && !X86_VOYAGER) || X86_64
197 config X86_BIOS_REBOOT
199 depends on !X86_VOYAGER
202 config X86_TRAMPOLINE
204 depends on X86_SMP || (X86_VOYAGER && SMP) || (64BIT && ACPI_SLEEP)
209 source "init/Kconfig"
211 menu "Processor type and features"
213 source "kernel/time/Kconfig"
216 bool "Symmetric multi-processing support"
218 This enables support for systems with more than one CPU. If you have
219 a system with only one CPU, like most personal computers, say N. If
220 you have a system with more than one CPU, say Y.
222 If you say N here, the kernel will run on single and multiprocessor
223 machines, but will use only one CPU of a multiprocessor machine. If
224 you say Y here, the kernel will run on many, but not all,
225 singleprocessor machines. On a singleprocessor machine, the kernel
226 will run faster if you say N here.
228 Note that if you say Y here and choose architecture "586" or
229 "Pentium" under "Processor family", the kernel will not work on 486
230 architectures. Similarly, multiprocessor kernels for the "PPro"
231 architecture may not work on all Pentium based boards.
233 People using multiprocessor machines who say Y here should also say
234 Y to "Enhanced Real Time Clock Support", below. The "Advanced Power
235 Management" code will be disabled if you say Y here.
237 See also <file:Documentation/i386/IO-APIC.txt>,
238 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
239 <http://www.tldp.org/docs.html#howto>.
241 If you don't know what to do here, say N.
243 config X86_FIND_SMP_CONFIG
245 depends on X86_MPPARSE || X86_VOYAGER
250 bool "Enable MPS table"
251 depends on X86_LOCAL_APIC
253 For old smp systems that do not have proper acpi support. Newer systems
254 (esp with 64bit cpus) with acpi support, MADT and DSDT will override it
260 depends on X86_LOCAL_APIC
264 prompt "Subarchitecture Type"
270 Choose this option if your computer is a standard PC or compatible.
276 Select this for an AMD Elan processor.
278 Do not use this option for K6/Athlon/Opteron processors!
280 If unsure, choose "PC-compatible" instead.
284 depends on X86_32 && (SMP || BROKEN) && !PCI
286 Voyager is an MCA-based 32-way capable SMP architecture proprietary
287 to NCR Corp. Machine classes 345x/35xx/4100/51xx are Voyager-based.
291 If you do not specifically know you have a Voyager based machine,
292 say N here, otherwise the kernel you build will not be bootable.
294 config X86_GENERICARCH
295 bool "Generic architecture"
298 This option compiles in the NUMAQ, Summit, bigsmp, ES7000, default
299 subarchitectures. It is intended for a generic binary kernel.
300 if you select them all, kernel will probe it one by one. and will
306 bool "NUMAQ (IBM/Sequent)"
307 depends on SMP && X86_32 && PCI && X86_MPPARSE
310 This option is used for getting Linux to run on a NUMAQ (IBM/Sequent)
311 NUMA multiquad box. This changes the way that processors are
312 bootstrapped, and uses Clustered Logical APIC addressing mode instead
313 of Flat Logical. You will need a new lynxer.elf file to flash your
314 firmware with - send email to <Martin.Bligh@us.ibm.com>.
317 bool "Summit/EXA (IBM x440)"
318 depends on X86_32 && SMP
320 This option is needed for IBM systems that use the Summit/EXA chipset.
321 In particular, it is needed for the x440.
324 bool "Support for Unisys ES7000 IA32 series"
325 depends on X86_32 && SMP
327 Support for Unisys ES7000 systems. Say 'Y' here if this kernel is
328 supposed to run on an IA32-based Unisys ES7000 system.
331 bool "Support for big SMP systems with more than 8 CPUs"
332 depends on X86_32 && SMP
334 This option is needed for the systems that have more than 8 CPUs
335 and if the system is not of any sub-arch type above.
340 bool "Support for ScaleMP vSMP"
342 depends on X86_64 && PCI
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.
351 bool "SGI 320/540 (Visual Workstation)"
352 depends on X86_32 && PCI && !X86_VOYAGER && X86_MPPARSE && PCI_GODIRECT
354 The SGI Visual Workstation series is an IA32-based workstation
355 based on SGI systems chips with some legacy PC hardware attached.
357 Say Y here to create a kernel to run on the SGI 320 or 540.
359 A kernel compiled for the Visual Workstation will run on general
360 PCs as well. See <file:Documentation/sgi-visws.txt> for details.
363 bool "RDC R-321x SoC"
366 select X86_REBOOTFIXUPS
368 This option is needed for RDC R-321x system-on-chip, also known
370 If you don't have one of these chips, you should say N here.
372 config SCHED_NO_NO_OMIT_FRAME_POINTER
374 prompt "Single-depth WCHAN output"
377 Calculate simpler /proc/<PID>/wchan values. If this option
378 is disabled then wchan values will recurse back to the
379 caller function. This provides more accurate wchan values,
380 at the expense of slightly more scheduling overhead.
382 If in doubt, say "Y".
384 menuconfig PARAVIRT_GUEST
385 bool "Paravirtualized guest support"
387 Say Y here to get to see options related to running Linux under
388 various hypervisors. This option alone does not add any kernel code.
390 If you say N, all options in this submenu will be skipped and disabled.
394 source "arch/x86/xen/Kconfig"
397 bool "VMI Guest support"
400 depends on !X86_VOYAGER
402 VMI provides a paravirtualized interface to the VMware ESX server
403 (it could be used by other hypervisors in theory too, but is not
404 at the moment), by linking the kernel to a GPL-ed ROM module
405 provided by the hypervisor.
408 bool "KVM paravirtualized clock"
410 select PARAVIRT_CLOCK
411 depends on !X86_VOYAGER
413 Turning on this option will allow you to run a paravirtualized clock
414 when running over the KVM hypervisor. Instead of relying on a PIT
415 (or probably other) emulation by the underlying device model, the host
416 provides the guest with timing infrastructure such as time of day, and
420 bool "KVM Guest support"
422 depends on !X86_VOYAGER
424 This option enables various optimizations for running under the KVM
427 source "arch/x86/lguest/Kconfig"
430 bool "Enable paravirtualization code"
431 depends on !X86_VOYAGER
433 This changes the kernel so it can modify itself when it is run
434 under a hypervisor, potentially improving performance significantly
435 over full virtualization. However, when run without a hypervisor
436 the kernel is theoretically slower and slightly larger.
438 config PARAVIRT_CLOCK
444 config PARAVIRT_DEBUG
445 bool "paravirt-ops debugging"
446 depends on PARAVIRT && DEBUG_KERNEL
448 Enable to debug paravirt_ops internals. Specifically, BUG if
449 a paravirt_op is missing when it is called.
454 This option adds a kernel parameter 'memtest', which allows memtest
456 memtest=0, mean disabled; -- default
457 memtest=1, mean do 1 test pattern;
459 memtest=4, mean do 4 test patterns.
460 If you are unsure how to answer this question, answer N.
462 config X86_SUMMIT_NUMA
464 depends on X86_32 && NUMA && X86_GENERICARCH
466 config X86_CYCLONE_TIMER
468 depends on X86_GENERICARCH
470 config ES7000_CLUSTERED_APIC
472 depends on SMP && X86_ES7000 && MPENTIUMIII
474 source "arch/x86/Kconfig.cpu"
478 prompt "HPET Timer Support" if X86_32
480 Use the IA-PC HPET (High Precision Event Timer) to manage
481 time in preference to the PIT and RTC, if a HPET is
483 HPET is the next generation timer replacing legacy 8254s.
484 The HPET provides a stable time base on SMP
485 systems, unlike the TSC, but it is more expensive to access,
486 as it is off-chip. You can find the HPET spec at
487 <http://www.intel.com/hardwaredesign/hpetspec.htm>.
489 You can safely choose Y here. However, HPET will only be
490 activated if the platform and the BIOS support this feature.
491 Otherwise the 8254 will be used for timing services.
493 Choose N to continue using the legacy 8254 timer.
495 config HPET_EMULATE_RTC
497 depends on HPET_TIMER && (RTC=y || RTC=m || RTC_DRV_CMOS=m || RTC_DRV_CMOS=y)
499 # Mark as embedded because too many people got it wrong.
500 # The code disables itself when not needed.
503 bool "Enable DMI scanning" if EMBEDDED
505 Enabled scanning of DMI to identify machine quirks. Say Y
506 here unless you have verified that your setup is not
507 affected by entries in the DMI blacklist. Required by PNP
511 bool "GART IOMMU support" if EMBEDDED
515 depends on X86_64 && PCI
517 Support for full DMA access of devices with 32bit memory access only
518 on systems with more than 3GB. This is usually needed for USB,
519 sound, many IDE/SATA chipsets and some other devices.
520 Provides a driver for the AMD Athlon64/Opteron/Turion/Sempron GART
521 based hardware IOMMU and a software bounce buffer based IOMMU used
522 on Intel systems and as fallback.
523 The code is only active when needed (enough memory and limited
524 device) unless CONFIG_IOMMU_DEBUG or iommu=force is specified
528 bool "IBM Calgary IOMMU support"
530 depends on X86_64 && PCI && EXPERIMENTAL
532 Support for hardware IOMMUs in IBM's xSeries x366 and x460
533 systems. Needed to run systems with more than 3GB of memory
534 properly with 32-bit PCI devices that do not support DAC
535 (Double Address Cycle). Calgary also supports bus level
536 isolation, where all DMAs pass through the IOMMU. This
537 prevents them from going anywhere except their intended
538 destination. This catches hard-to-find kernel bugs and
539 mis-behaving drivers and devices that do not use the DMA-API
540 properly to set up their DMA buffers. The IOMMU can be
541 turned off at boot time with the iommu=off parameter.
542 Normally the kernel will make the right choice by itself.
545 config CALGARY_IOMMU_ENABLED_BY_DEFAULT
547 prompt "Should Calgary be enabled by default?"
548 depends on CALGARY_IOMMU
550 Should Calgary be enabled by default? if you choose 'y', Calgary
551 will be used (if it exists). If you choose 'n', Calgary will not be
552 used even if it exists. If you choose 'n' and would like to use
553 Calgary anyway, pass 'iommu=calgary' on the kernel command line.
557 bool "AMD IOMMU support"
559 depends on X86_64 && PCI && ACPI
561 With this option you can enable support for AMD IOMMU hardware in
562 your system. An IOMMU is a hardware component which provides
563 remapping of DMA memory accesses from devices. With an AMD IOMMU you
564 can isolate the the DMA memory of different devices and protect the
565 system from misbehaving device drivers or hardware.
567 You can find out if your system has an AMD IOMMU if you look into
568 your BIOS for an option to enable it or if you have an IVRS ACPI
571 # need this always selected by IOMMU for the VIA workaround
575 Support for software bounce buffers used on x86-64 systems
576 which don't have a hardware IOMMU (e.g. the current generation
577 of Intel's x86-64 CPUs). Using this PCI devices which can only
578 access 32-bits of memory can be used on systems with more than
579 3 GB of memory. If unsure, say Y.
582 def_bool (CALGARY_IOMMU || GART_IOMMU || SWIOTLB || AMD_IOMMU)
585 bool "Configure Maximum number of SMP Processors and NUMA Nodes"
586 depends on X86_64 && SMP && BROKEN
589 Configure maximum number of CPUS and NUMA Nodes for this architecture.
593 int "Maximum number of CPUs (2-512)" if !MAXSMP
596 default "4096" if MAXSMP
597 default "32" if X86_NUMAQ || X86_SUMMIT || X86_BIGSMP || X86_ES7000
600 This allows you to specify the maximum number of CPUs which this
601 kernel will support. The maximum supported value is 512 and the
602 minimum value which makes sense is 2.
604 This is purely to save memory - each supported CPU adds
605 approximately eight kilobytes to the kernel image.
608 bool "SMT (Hyperthreading) scheduler support"
611 SMT scheduler support improves the CPU scheduler's decision making
612 when dealing with Intel Pentium 4 chips with HyperThreading at a
613 cost of slightly increased overhead in some places. If unsure say
618 prompt "Multi-core scheduler support"
621 Multi-core scheduler support improves the CPU scheduler's decision
622 making when dealing with multi-core CPU chips at a cost of slightly
623 increased overhead in some places. If unsure say N here.
625 source "kernel/Kconfig.preempt"
628 bool "Local APIC support on uniprocessors"
629 depends on X86_32 && !SMP && !(X86_VOYAGER || X86_GENERICARCH)
631 A local APIC (Advanced Programmable Interrupt Controller) is an
632 integrated interrupt controller in the CPU. If you have a single-CPU
633 system which has a processor with a local APIC, you can say Y here to
634 enable and use it. If you say Y here even though your machine doesn't
635 have a local APIC, then the kernel will still run with no slowdown at
636 all. The local APIC supports CPU-generated self-interrupts (timer,
637 performance counters), and the NMI watchdog which detects hard
641 bool "IO-APIC support on uniprocessors"
642 depends on X86_UP_APIC
644 An IO-APIC (I/O Advanced Programmable Interrupt Controller) is an
645 SMP-capable replacement for PC-style interrupt controllers. Most
646 SMP systems and many recent uniprocessor systems have one.
648 If you have a single-CPU system with an IO-APIC, you can say Y here
649 to use it. If you say Y here even though your machine doesn't have
650 an IO-APIC, then the kernel will still run with no slowdown at all.
652 config X86_LOCAL_APIC
654 depends on X86_64 || (X86_32 && (X86_UP_APIC || (SMP && !X86_VOYAGER) || X86_GENERICARCH))
658 depends on X86_64 || (X86_32 && (X86_UP_IOAPIC || (SMP && !X86_VOYAGER) || X86_GENERICARCH))
660 config X86_VISWS_APIC
662 depends on X86_32 && X86_VISWS
665 bool "Machine Check Exception"
666 depends on !X86_VOYAGER
668 Machine Check Exception support allows the processor to notify the
669 kernel if it detects a problem (e.g. overheating, component failure).
670 The action the kernel takes depends on the severity of the problem,
671 ranging from a warning message on the console, to halting the machine.
672 Your processor must be a Pentium or newer to support this - check the
673 flags in /proc/cpuinfo for mce. Note that some older Pentium systems
674 have a design flaw which leads to false MCE events - hence MCE is
675 disabled on all P5 processors, unless explicitly enabled with "mce"
676 as a boot argument. Similarly, if MCE is built in and creates a
677 problem on some new non-standard machine, you can boot with "nomce"
678 to disable it. MCE support simply ignores non-MCE processors like
679 the 386 and 486, so nearly everyone can say Y here.
683 prompt "Intel MCE features"
684 depends on X86_64 && X86_MCE && X86_LOCAL_APIC
686 Additional support for intel specific MCE features such as
691 prompt "AMD MCE features"
692 depends on X86_64 && X86_MCE && X86_LOCAL_APIC
694 Additional support for AMD specific MCE features such as
695 the DRAM Error Threshold.
697 config X86_MCE_NONFATAL
698 tristate "Check for non-fatal errors on AMD Athlon/Duron / Intel Pentium 4"
699 depends on X86_32 && X86_MCE
701 Enabling this feature starts a timer that triggers every 5 seconds which
702 will look at the machine check registers to see if anything happened.
703 Non-fatal problems automatically get corrected (but still logged).
704 Disable this if you don't want to see these messages.
705 Seeing the messages this option prints out may be indicative of dying
706 or out-of-spec (ie, overclocked) hardware.
707 This option only does something on certain CPUs.
708 (AMD Athlon/Duron and Intel Pentium 4)
710 config X86_MCE_P4THERMAL
711 bool "check for P4 thermal throttling interrupt."
712 depends on X86_32 && X86_MCE && (X86_UP_APIC || SMP)
714 Enabling this feature will cause a message to be printed when the P4
715 enters thermal throttling.
718 bool "Enable VM86 support" if EMBEDDED
722 This option is required by programs like DOSEMU to run 16-bit legacy
723 code on X86 processors. It also may be needed by software like
724 XFree86 to initialize some video cards via BIOS. Disabling this
725 option saves about 6k.
728 tristate "Toshiba Laptop support"
731 This adds a driver to safely access the System Management Mode of
732 the CPU on Toshiba portables with a genuine Toshiba BIOS. It does
733 not work on models with a Phoenix BIOS. The System Management Mode
734 is used to set the BIOS and power saving options on Toshiba portables.
736 For information on utilities to make use of this driver see the
737 Toshiba Linux utilities web site at:
738 <http://www.buzzard.org.uk/toshiba/>.
740 Say Y if you intend to run this kernel on a Toshiba portable.
744 tristate "Dell laptop support"
746 This adds a driver to safely access the System Management Mode
747 of the CPU on the Dell Inspiron 8000. The System Management Mode
748 is used to read cpu temperature and cooling fan status and to
749 control the fans on the I8K portables.
751 This driver has been tested only on the Inspiron 8000 but it may
752 also work with other Dell laptops. You can force loading on other
753 models by passing the parameter `force=1' to the module. Use at
756 For information on utilities to make use of this driver see the
757 I8K Linux utilities web site at:
758 <http://people.debian.org/~dz/i8k/>
760 Say Y if you intend to run this kernel on a Dell Inspiron 8000.
763 config X86_REBOOTFIXUPS
765 prompt "Enable X86 board specific fixups for reboot"
766 depends on X86_32 && X86
768 This enables chipset and/or board specific fixups to be done
769 in order to get reboot to work correctly. This is only needed on
770 some combinations of hardware and BIOS. The symptom, for which
771 this config is intended, is when reboot ends with a stalled/hung
774 Currently, the only fixup is for the Geode machines using
775 CS5530A and CS5536 chipsets and the RDC R-321x SoC.
777 Say Y if you want to enable the fixup. Currently, it's safe to
778 enable this option even if you don't need it.
782 tristate "/dev/cpu/microcode - Intel IA32 CPU microcode support"
785 If you say Y here, you will be able to update the microcode on
786 Intel processors in the IA32 family, e.g. Pentium Pro, Pentium II,
787 Pentium III, Pentium 4, Xeon etc. You will obviously need the
788 actual microcode binary data itself which is not shipped with the
791 For latest news and information on obtaining all the required
792 ingredients for this driver, check:
793 <http://www.urbanmyth.org/microcode/>.
795 To compile this driver as a module, choose M here: the
796 module will be called microcode.
798 config MICROCODE_OLD_INTERFACE
803 tristate "/dev/cpu/*/msr - Model-specific register support"
805 This device gives privileged processes access to the x86
806 Model-Specific Registers (MSRs). It is a character device with
807 major 202 and minors 0 to 31 for /dev/cpu/0/msr to /dev/cpu/31/msr.
808 MSR accesses are directed to a specific CPU on multi-processor
812 tristate "/dev/cpu/*/cpuid - CPU information support"
814 This device gives processes access to the x86 CPUID instruction to
815 be executed on a specific processor. It is a character device
816 with major 203 and minors 0 to 31 for /dev/cpu/0/cpuid to
820 prompt "High Memory Support"
821 default HIGHMEM4G if !X86_NUMAQ
822 default HIGHMEM64G if X86_NUMAQ
827 depends on !X86_NUMAQ
829 Linux can use up to 64 Gigabytes of physical memory on x86 systems.
830 However, the address space of 32-bit x86 processors is only 4
831 Gigabytes large. That means that, if you have a large amount of
832 physical memory, not all of it can be "permanently mapped" by the
833 kernel. The physical memory that's not permanently mapped is called
836 If you are compiling a kernel which will never run on a machine with
837 more than 1 Gigabyte total physical RAM, answer "off" here (default
838 choice and suitable for most users). This will result in a "3GB/1GB"
839 split: 3GB are mapped so that each process sees a 3GB virtual memory
840 space and the remaining part of the 4GB virtual memory space is used
841 by the kernel to permanently map as much physical memory as
844 If the machine has between 1 and 4 Gigabytes physical RAM, then
847 If more than 4 Gigabytes is used then answer "64GB" here. This
848 selection turns Intel PAE (Physical Address Extension) mode on.
849 PAE implements 3-level paging on IA32 processors. PAE is fully
850 supported by Linux, PAE mode is implemented on all recent Intel
851 processors (Pentium Pro and better). NOTE: If you say "64GB" here,
852 then the kernel will not boot on CPUs that don't support PAE!
854 The actual amount of total physical memory will either be
855 auto detected or can be forced by using a kernel command line option
856 such as "mem=256M". (Try "man bootparam" or see the documentation of
857 your boot loader (lilo or loadlin) about how to pass options to the
858 kernel at boot time.)
860 If unsure, say "off".
864 depends on !X86_NUMAQ
866 Select this if you have a 32-bit processor and between 1 and 4
867 gigabytes of physical RAM.
871 depends on !M386 && !M486
874 Select this if you have a 32-bit processor and more than 4
875 gigabytes of physical RAM.
880 depends on EXPERIMENTAL
881 prompt "Memory split" if EMBEDDED
885 Select the desired split between kernel and user memory.
887 If the address range available to the kernel is less than the
888 physical memory installed, the remaining memory will be available
889 as "high memory". Accessing high memory is a little more costly
890 than low memory, as it needs to be mapped into the kernel first.
891 Note that increasing the kernel address space limits the range
892 available to user programs, making the address space there
893 tighter. Selecting anything other than the default 3G/1G split
894 will also likely make your kernel incompatible with binary-only
897 If you are not absolutely sure what you are doing, leave this
901 bool "3G/1G user/kernel split"
902 config VMSPLIT_3G_OPT
904 bool "3G/1G user/kernel split (for full 1G low memory)"
906 bool "2G/2G user/kernel split"
907 config VMSPLIT_2G_OPT
909 bool "2G/2G user/kernel split (for full 2G low memory)"
911 bool "1G/3G user/kernel split"
916 default 0xB0000000 if VMSPLIT_3G_OPT
917 default 0x80000000 if VMSPLIT_2G
918 default 0x78000000 if VMSPLIT_2G_OPT
919 default 0x40000000 if VMSPLIT_1G
925 depends on X86_32 && (HIGHMEM64G || HIGHMEM4G)
929 prompt "PAE (Physical Address Extension) Support"
930 depends on X86_32 && !HIGHMEM4G
931 select RESOURCES_64BIT
933 PAE is required for NX support, and furthermore enables
934 larger swapspace support for non-overcommit purposes. It
935 has the cost of more pagetable lookup overhead, and also
936 consumes more pagetable space per process.
938 # Common NUMA Features
940 bool "Numa Memory Allocation and Scheduler Support (EXPERIMENTAL)"
942 depends on X86_64 || (X86_32 && HIGHMEM64G && (X86_NUMAQ || X86_BIGSMP || X86_SUMMIT && ACPI) && EXPERIMENTAL)
944 default y if (X86_NUMAQ || X86_SUMMIT || X86_BIGSMP)
946 Enable NUMA (Non Uniform Memory Access) support.
947 The kernel will try to allocate memory used by a CPU on the
948 local memory controller of the CPU and add some more
949 NUMA awareness to the kernel.
951 For 32-bit this is currently highly experimental and should be only
952 used for kernel development. It might also cause boot failures.
953 For 64-bit this is recommended on all multiprocessor Opteron systems.
954 If the system is EM64T, you should say N unless your system is
957 comment "NUMA (Summit) requires SMP, 64GB highmem support, ACPI"
958 depends on X86_32 && X86_SUMMIT && (!HIGHMEM64G || !ACPI)
962 prompt "Old style AMD Opteron NUMA detection"
963 depends on X86_64 && NUMA && PCI
965 Enable K8 NUMA node topology detection. You should say Y here if
966 you have a multi processor AMD K8 system. This uses an old
967 method to read the NUMA configuration directly from the builtin
968 Northbridge of Opteron. It is recommended to use X86_64_ACPI_NUMA
969 instead, which also takes priority if both are compiled in.
971 config X86_64_ACPI_NUMA
973 prompt "ACPI NUMA detection"
974 depends on X86_64 && NUMA && ACPI && PCI
977 Enable ACPI SRAT based node topology detection.
979 # Some NUMA nodes have memory ranges that span
980 # other nodes. Even though a pfn is valid and
981 # between a node's start and end pfns, it may not
982 # reside on that node. See memmap_init_zone()
984 config NODES_SPAN_OTHER_NODES
986 depends on X86_64_ACPI_NUMA
989 bool "NUMA emulation"
990 depends on X86_64 && NUMA
992 Enable NUMA emulation. A flat machine will be split
993 into virtual nodes when booted with "numa=fake=N", where N is the
994 number of nodes. This is only useful for debugging.
997 int "Maximum NUMA Nodes (as a power of 2)" if !MAXSMP
999 default "9" if MAXSMP
1000 default "6" if X86_64
1001 default "4" if X86_NUMAQ
1003 depends on NEED_MULTIPLE_NODES
1005 Specify the maximum number of NUMA Nodes available on the target
1006 system. Increases memory reserved to accomodate various tables.
1008 config HAVE_ARCH_BOOTMEM_NODE
1010 depends on X86_32 && NUMA
1012 config ARCH_HAVE_MEMORY_PRESENT
1014 depends on X86_32 && DISCONTIGMEM
1016 config NEED_NODE_MEMMAP_SIZE
1018 depends on X86_32 && (DISCONTIGMEM || SPARSEMEM)
1020 config HAVE_ARCH_ALLOC_REMAP
1022 depends on X86_32 && NUMA
1024 config ARCH_FLATMEM_ENABLE
1026 depends on X86_32 && ARCH_SELECT_MEMORY_MODEL && X86_PC && !NUMA
1028 config ARCH_DISCONTIGMEM_ENABLE
1030 depends on NUMA && X86_32
1032 config ARCH_DISCONTIGMEM_DEFAULT
1034 depends on NUMA && X86_32
1036 config ARCH_SPARSEMEM_DEFAULT
1040 config ARCH_SPARSEMEM_ENABLE
1042 depends on X86_64 || NUMA || (EXPERIMENTAL && X86_PC)
1043 select SPARSEMEM_STATIC if X86_32
1044 select SPARSEMEM_VMEMMAP_ENABLE if X86_64
1046 config ARCH_SELECT_MEMORY_MODEL
1048 depends on ARCH_SPARSEMEM_ENABLE
1050 config ARCH_MEMORY_PROBE
1052 depends on MEMORY_HOTPLUG
1057 bool "Allocate 3rd-level pagetables from highmem"
1058 depends on X86_32 && (HIGHMEM4G || HIGHMEM64G)
1060 The VM uses one page table entry for each page of physical memory.
1061 For systems with a lot of RAM, this can be wasteful of precious
1062 low memory. Setting this option will put user-space page table
1063 entries in high memory.
1065 config MATH_EMULATION
1067 prompt "Math emulation" if X86_32
1069 Linux can emulate a math coprocessor (used for floating point
1070 operations) if you don't have one. 486DX and Pentium processors have
1071 a math coprocessor built in, 486SX and 386 do not, unless you added
1072 a 487DX or 387, respectively. (The messages during boot time can
1073 give you some hints here ["man dmesg"].) Everyone needs either a
1074 coprocessor or this emulation.
1076 If you don't have a math coprocessor, you need to say Y here; if you
1077 say Y here even though you have a coprocessor, the coprocessor will
1078 be used nevertheless. (This behavior can be changed with the kernel
1079 command line option "no387", which comes handy if your coprocessor
1080 is broken. Try "man bootparam" or see the documentation of your boot
1081 loader (lilo or loadlin) about how to pass options to the kernel at
1082 boot time.) This means that it is a good idea to say Y here if you
1083 intend to use this kernel on different machines.
1085 More information about the internals of the Linux math coprocessor
1086 emulation can be found in <file:arch/x86/math-emu/README>.
1088 If you are not sure, say Y; apart from resulting in a 66 KB bigger
1089 kernel, it won't hurt.
1092 bool "MTRR (Memory Type Range Register) support"
1094 On Intel P6 family processors (Pentium Pro, Pentium II and later)
1095 the Memory Type Range Registers (MTRRs) may be used to control
1096 processor access to memory ranges. This is most useful if you have
1097 a video (VGA) card on a PCI or AGP bus. Enabling write-combining
1098 allows bus write transfers to be combined into a larger transfer
1099 before bursting over the PCI/AGP bus. This can increase performance
1100 of image write operations 2.5 times or more. Saying Y here creates a
1101 /proc/mtrr file which may be used to manipulate your processor's
1102 MTRRs. Typically the X server should use this.
1104 This code has a reasonably generic interface so that similar
1105 control registers on other processors can be easily supported
1108 The Cyrix 6x86, 6x86MX and M II processors have Address Range
1109 Registers (ARRs) which provide a similar functionality to MTRRs. For
1110 these, the ARRs are used to emulate the MTRRs.
1111 The AMD K6-2 (stepping 8 and above) and K6-3 processors have two
1112 MTRRs. The Centaur C6 (WinChip) has 8 MCRs, allowing
1113 write-combining. All of these processors are supported by this code
1114 and it makes sense to say Y here if you have one of them.
1116 Saying Y here also fixes a problem with buggy SMP BIOSes which only
1117 set the MTRRs for the boot CPU and not for the secondary CPUs. This
1118 can lead to all sorts of problems, so it's good to say Y here.
1120 You can safely say Y even if your machine doesn't have MTRRs, you'll
1121 just add about 9 KB to your kernel.
1123 See <file:Documentation/mtrr.txt> for more information.
1125 config MTRR_SANITIZER
1127 prompt "MTRR cleanup support"
1130 Convert MTRR layout from continuous to discrete, so X drivers can
1131 add writeback entries.
1133 Can be disabled with disable_mtrr_cleanup on the kernel command line.
1134 The largest mtrr entry size for a continous block can be set with
1139 config MTRR_SANITIZER_ENABLE_DEFAULT
1140 int "MTRR cleanup enable value (0-1)"
1143 depends on MTRR_SANITIZER
1145 Enable mtrr cleanup default value
1147 config MTRR_SANITIZER_SPARE_REG_NR_DEFAULT
1148 int "MTRR cleanup spare reg num (0-7)"
1151 depends on MTRR_SANITIZER
1153 mtrr cleanup spare entries default, it can be changed via
1154 mtrr_spare_reg_nr=N on the kernel command line.
1158 prompt "x86 PAT support"
1161 Use PAT attributes to setup page level cache control.
1163 PATs are the modern equivalents of MTRRs and are much more
1164 flexible than MTRRs.
1166 Say N here if you see bootup problems (boot crash, boot hang,
1167 spontaneous reboots) or a non-working video driver.
1173 prompt "EFI runtime service support"
1176 This enables the kernel to use EFI runtime services that are
1177 available (such as the EFI variable services).
1179 This option is only useful on systems that have EFI firmware.
1180 In addition, you should use the latest ELILO loader available
1181 at <http://elilo.sourceforge.net> in order to take advantage
1182 of EFI runtime services. However, even with this option, the
1183 resultant kernel should continue to boot on existing non-EFI
1188 prompt "Enable kernel irq balancing"
1189 depends on X86_32 && SMP && X86_IO_APIC
1191 The default yes will allow the kernel to do irq load balancing.
1192 Saying no will keep the kernel from doing irq load balancing.
1196 prompt "Enable seccomp to safely compute untrusted bytecode"
1199 This kernel feature is useful for number crunching applications
1200 that may need to compute untrusted bytecode during their
1201 execution. By using pipes or other transports made available to
1202 the process as file descriptors supporting the read/write
1203 syscalls, it's possible to isolate those applications in
1204 their own address space using seccomp. Once seccomp is
1205 enabled via /proc/<pid>/seccomp, it cannot be disabled
1206 and the task is only allowed to execute a few safe syscalls
1207 defined by each seccomp mode.
1209 If unsure, say Y. Only embedded should say N here.
1211 config CC_STACKPROTECTOR
1212 bool "Enable -fstack-protector buffer overflow detection (EXPERIMENTAL)"
1213 depends on X86_64 && EXPERIMENTAL && BROKEN
1215 This option turns on the -fstack-protector GCC feature. This
1216 feature puts, at the beginning of critical functions, a canary
1217 value on the stack just before the return address, and validates
1218 the value just before actually returning. Stack based buffer
1219 overflows (that need to overwrite this return address) now also
1220 overwrite the canary, which gets detected and the attack is then
1221 neutralized via a kernel panic.
1223 This feature requires gcc version 4.2 or above, or a distribution
1224 gcc with the feature backported. Older versions are automatically
1225 detected and for those versions, this configuration option is ignored.
1227 config CC_STACKPROTECTOR_ALL
1228 bool "Use stack-protector for all functions"
1229 depends on CC_STACKPROTECTOR
1231 Normally, GCC only inserts the canary value protection for
1232 functions that use large-ish on-stack buffers. By enabling
1233 this option, GCC will be asked to do this for ALL functions.
1235 source kernel/Kconfig.hz
1238 bool "kexec system call"
1239 depends on X86_BIOS_REBOOT
1241 kexec is a system call that implements the ability to shutdown your
1242 current kernel, and to start another kernel. It is like a reboot
1243 but it is independent of the system firmware. And like a reboot
1244 you can start any kernel with it, not just Linux.
1246 The name comes from the similarity to the exec system call.
1248 It is an ongoing process to be certain the hardware in a machine
1249 is properly shutdown, so do not be surprised if this code does not
1250 initially work for you. It may help to enable device hotplugging
1251 support. As of this writing the exact hardware interface is
1252 strongly in flux, so no good recommendation can be made.
1255 bool "kernel crash dumps"
1256 depends on X86_64 || (X86_32 && HIGHMEM)
1258 Generate crash dump after being started by kexec.
1259 This should be normally only set in special crash dump kernels
1260 which are loaded in the main kernel with kexec-tools into
1261 a specially reserved region and then later executed after
1262 a crash by kdump/kexec. The crash dump kernel must be compiled
1263 to a memory address not used by the main kernel or BIOS using
1264 PHYSICAL_START, or it must be built as a relocatable image
1265 (CONFIG_RELOCATABLE=y).
1266 For more details see Documentation/kdump/kdump.txt
1269 bool "kexec jump (EXPERIMENTAL)"
1270 depends on EXPERIMENTAL
1271 depends on KEXEC && HIBERNATION && X86_32
1273 Jump between original kernel and kexeced kernel and invoke
1274 code in physical address mode via KEXEC
1276 config PHYSICAL_START
1277 hex "Physical address where the kernel is loaded" if (EMBEDDED || CRASH_DUMP)
1278 default "0x1000000" if X86_NUMAQ
1279 default "0x200000" if X86_64
1282 This gives the physical address where the kernel is loaded.
1284 If kernel is a not relocatable (CONFIG_RELOCATABLE=n) then
1285 bzImage will decompress itself to above physical address and
1286 run from there. Otherwise, bzImage will run from the address where
1287 it has been loaded by the boot loader and will ignore above physical
1290 In normal kdump cases one does not have to set/change this option
1291 as now bzImage can be compiled as a completely relocatable image
1292 (CONFIG_RELOCATABLE=y) and be used to load and run from a different
1293 address. This option is mainly useful for the folks who don't want
1294 to use a bzImage for capturing the crash dump and want to use a
1295 vmlinux instead. vmlinux is not relocatable hence a kernel needs
1296 to be specifically compiled to run from a specific memory area
1297 (normally a reserved region) and this option comes handy.
1299 So if you are using bzImage for capturing the crash dump, leave
1300 the value here unchanged to 0x100000 and set CONFIG_RELOCATABLE=y.
1301 Otherwise if you plan to use vmlinux for capturing the crash dump
1302 change this value to start of the reserved region (Typically 16MB
1303 0x1000000). In other words, it can be set based on the "X" value as
1304 specified in the "crashkernel=YM@XM" command line boot parameter
1305 passed to the panic-ed kernel. Typically this parameter is set as
1306 crashkernel=64M@16M. Please take a look at
1307 Documentation/kdump/kdump.txt for more details about crash dumps.
1309 Usage of bzImage for capturing the crash dump is recommended as
1310 one does not have to build two kernels. Same kernel can be used
1311 as production kernel and capture kernel. Above option should have
1312 gone away after relocatable bzImage support is introduced. But it
1313 is present because there are users out there who continue to use
1314 vmlinux for dump capture. This option should go away down the
1317 Don't change this unless you know what you are doing.
1320 bool "Build a relocatable kernel (EXPERIMENTAL)"
1321 depends on EXPERIMENTAL
1323 This builds a kernel image that retains relocation information
1324 so it can be loaded someplace besides the default 1MB.
1325 The relocations tend to make the kernel binary about 10% larger,
1326 but are discarded at runtime.
1328 One use is for the kexec on panic case where the recovery kernel
1329 must live at a different physical address than the primary
1332 Note: If CONFIG_RELOCATABLE=y, then the kernel runs from the address
1333 it has been loaded at and the compile time physical address
1334 (CONFIG_PHYSICAL_START) is ignored.
1336 config PHYSICAL_ALIGN
1338 prompt "Alignment value to which kernel should be aligned" if X86_32
1339 default "0x100000" if X86_32
1340 default "0x200000" if X86_64
1341 range 0x2000 0x400000
1343 This value puts the alignment restrictions on physical address
1344 where kernel is loaded and run from. Kernel is compiled for an
1345 address which meets above alignment restriction.
1347 If bootloader loads the kernel at a non-aligned address and
1348 CONFIG_RELOCATABLE is set, kernel will move itself to nearest
1349 address aligned to above value and run from there.
1351 If bootloader loads the kernel at a non-aligned address and
1352 CONFIG_RELOCATABLE is not set, kernel will ignore the run time
1353 load address and decompress itself to the address it has been
1354 compiled for and run from there. The address for which kernel is
1355 compiled already meets above alignment restrictions. Hence the
1356 end result is that kernel runs from a physical address meeting
1357 above alignment restrictions.
1359 Don't change this unless you know what you are doing.
1362 bool "Support for suspend on SMP and hot-pluggable CPUs (EXPERIMENTAL)"
1363 depends on SMP && HOTPLUG && EXPERIMENTAL && !X86_VOYAGER
1365 Say Y here to experiment with turning CPUs off and on, and to
1366 enable suspend on SMP systems. CPUs can be controlled through
1367 /sys/devices/system/cpu.
1368 Say N if you want to disable CPU hotplug and don't need to
1373 prompt "Compat VDSO support"
1374 depends on X86_32 || IA32_EMULATION
1376 Map the 32-bit VDSO to the predictable old-style address too.
1378 Say N here if you are running a sufficiently recent glibc
1379 version (2.3.3 or later), to remove the high-mapped
1380 VDSO mapping and to exclusively use the randomized VDSO.
1386 config ARCH_ENABLE_MEMORY_HOTPLUG
1388 depends on X86_64 || (X86_32 && HIGHMEM)
1390 config HAVE_ARCH_EARLY_PFN_TO_NID
1394 menu "Power management options"
1395 depends on !X86_VOYAGER
1397 config ARCH_HIBERNATION_HEADER
1399 depends on X86_64 && HIBERNATION
1401 source "kernel/power/Kconfig"
1403 source "drivers/acpi/Kconfig"
1408 depends on APM || APM_MODULE
1411 tristate "APM (Advanced Power Management) BIOS support"
1412 depends on X86_32 && PM_SLEEP
1414 APM is a BIOS specification for saving power using several different
1415 techniques. This is mostly useful for battery powered laptops with
1416 APM compliant BIOSes. If you say Y here, the system time will be
1417 reset after a RESUME operation, the /proc/apm device will provide
1418 battery status information, and user-space programs will receive
1419 notification of APM "events" (e.g. battery status change).
1421 If you select "Y" here, you can disable actual use of the APM
1422 BIOS by passing the "apm=off" option to the kernel at boot time.
1424 Note that the APM support is almost completely disabled for
1425 machines with more than one CPU.
1427 In order to use APM, you will need supporting software. For location
1428 and more information, read <file:Documentation/power/pm.txt> and the
1429 Battery Powered Linux mini-HOWTO, available from
1430 <http://www.tldp.org/docs.html#howto>.
1432 This driver does not spin down disk drives (see the hdparm(8)
1433 manpage ("man 8 hdparm") for that), and it doesn't turn off
1434 VESA-compliant "green" monitors.
1436 This driver does not support the TI 4000M TravelMate and the ACER
1437 486/DX4/75 because they don't have compliant BIOSes. Many "green"
1438 desktop machines also don't have compliant BIOSes, and this driver
1439 may cause those machines to panic during the boot phase.
1441 Generally, if you don't have a battery in your machine, there isn't
1442 much point in using this driver and you should say N. If you get
1443 random kernel OOPSes or reboots that don't seem to be related to
1444 anything, try disabling/enabling this option (or disabling/enabling
1447 Some other things you should try when experiencing seemingly random,
1450 1) make sure that you have enough swap space and that it is
1452 2) pass the "no-hlt" option to the kernel
1453 3) switch on floating point emulation in the kernel and pass
1454 the "no387" option to the kernel
1455 4) pass the "floppy=nodma" option to the kernel
1456 5) pass the "mem=4M" option to the kernel (thereby disabling
1457 all but the first 4 MB of RAM)
1458 6) make sure that the CPU is not over clocked.
1459 7) read the sig11 FAQ at <http://www.bitwizard.nl/sig11/>
1460 8) disable the cache from your BIOS settings
1461 9) install a fan for the video card or exchange video RAM
1462 10) install a better fan for the CPU
1463 11) exchange RAM chips
1464 12) exchange the motherboard.
1466 To compile this driver as a module, choose M here: the
1467 module will be called apm.
1471 config APM_IGNORE_USER_SUSPEND
1472 bool "Ignore USER SUSPEND"
1474 This option will ignore USER SUSPEND requests. On machines with a
1475 compliant APM BIOS, you want to say N. However, on the NEC Versa M
1476 series notebooks, it is necessary to say Y because of a BIOS bug.
1478 config APM_DO_ENABLE
1479 bool "Enable PM at boot time"
1481 Enable APM features at boot time. From page 36 of the APM BIOS
1482 specification: "When disabled, the APM BIOS does not automatically
1483 power manage devices, enter the Standby State, enter the Suspend
1484 State, or take power saving steps in response to CPU Idle calls."
1485 This driver will make CPU Idle calls when Linux is idle (unless this
1486 feature is turned off -- see "Do CPU IDLE calls", below). This
1487 should always save battery power, but more complicated APM features
1488 will be dependent on your BIOS implementation. You may need to turn
1489 this option off if your computer hangs at boot time when using APM
1490 support, or if it beeps continuously instead of suspending. Turn
1491 this off if you have a NEC UltraLite Versa 33/C or a Toshiba
1492 T400CDT. This is off by default since most machines do fine without
1496 bool "Make CPU Idle calls when idle"
1498 Enable calls to APM CPU Idle/CPU Busy inside the kernel's idle loop.
1499 On some machines, this can activate improved power savings, such as
1500 a slowed CPU clock rate, when the machine is idle. These idle calls
1501 are made after the idle loop has run for some length of time (e.g.,
1502 333 mS). On some machines, this will cause a hang at boot time or
1503 whenever the CPU becomes idle. (On machines with more than one CPU,
1504 this option does nothing.)
1506 config APM_DISPLAY_BLANK
1507 bool "Enable console blanking using APM"
1509 Enable console blanking using the APM. Some laptops can use this to
1510 turn off the LCD backlight when the screen blanker of the Linux
1511 virtual console blanks the screen. Note that this is only used by
1512 the virtual console screen blanker, and won't turn off the backlight
1513 when using the X Window system. This also doesn't have anything to
1514 do with your VESA-compliant power-saving monitor. Further, this
1515 option doesn't work for all laptops -- it might not turn off your
1516 backlight at all, or it might print a lot of errors to the console,
1517 especially if you are using gpm.
1519 config APM_ALLOW_INTS
1520 bool "Allow interrupts during APM BIOS calls"
1522 Normally we disable external interrupts while we are making calls to
1523 the APM BIOS as a measure to lessen the effects of a badly behaving
1524 BIOS implementation. The BIOS should reenable interrupts if it
1525 needs to. Unfortunately, some BIOSes do not -- especially those in
1526 many of the newer IBM Thinkpads. If you experience hangs when you
1527 suspend, try setting this to Y. Otherwise, say N.
1529 config APM_REAL_MODE_POWER_OFF
1530 bool "Use real mode APM BIOS call to power off"
1532 Use real mode APM BIOS calls to switch off the computer. This is
1533 a work-around for a number of buggy BIOSes. Switch this option on if
1534 your computer crashes instead of powering off properly.
1538 source "arch/x86/kernel/cpu/cpufreq/Kconfig"
1540 source "drivers/cpuidle/Kconfig"
1545 menu "Bus options (PCI etc.)"
1550 select ARCH_SUPPORTS_MSI if (X86_LOCAL_APIC && X86_IO_APIC)
1552 Find out whether you have a PCI motherboard. PCI is the name of a
1553 bus system, i.e. the way the CPU talks to the other stuff inside
1554 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
1555 VESA. If you have PCI, say Y, otherwise N.
1558 prompt "PCI access mode"
1559 depends on X86_32 && PCI
1562 On PCI systems, the BIOS can be used to detect the PCI devices and
1563 determine their configuration. However, some old PCI motherboards
1564 have BIOS bugs and may crash if this is done. Also, some embedded
1565 PCI-based systems don't have any BIOS at all. Linux can also try to
1566 detect the PCI hardware directly without using the BIOS.
1568 With this option, you can specify how Linux should detect the
1569 PCI devices. If you choose "BIOS", the BIOS will be used,
1570 if you choose "Direct", the BIOS won't be used, and if you
1571 choose "MMConfig", then PCI Express MMCONFIG will be used.
1572 If you choose "Any", the kernel will try MMCONFIG, then the
1573 direct access method and falls back to the BIOS if that doesn't
1574 work. If unsure, go with the default, which is "Any".
1579 config PCI_GOMMCONFIG
1596 depends on X86_32 && PCI && (PCI_GOBIOS || PCI_GOANY)
1598 # x86-64 doesn't support PCI BIOS access from long mode so always go direct.
1601 depends on PCI && (X86_64 || (PCI_GODIRECT || PCI_GOANY || PCI_GOOLPC))
1605 depends on X86_32 && PCI && ACPI && (PCI_GOMMCONFIG || PCI_GOANY)
1609 depends on PCI && OLPC && (PCI_GOOLPC || PCI_GOANY)
1616 bool "Support mmconfig PCI config space access"
1617 depends on X86_64 && PCI && ACPI
1620 bool "Support for DMA Remapping Devices (EXPERIMENTAL)"
1621 depends on X86_64 && PCI_MSI && ACPI && EXPERIMENTAL
1623 DMA remapping (DMAR) devices support enables independent address
1624 translations for Direct Memory Access (DMA) from devices.
1625 These DMA remapping devices are reported via ACPI tables
1626 and include PCI device scope covered by these DMA
1631 prompt "Support for Graphics workaround"
1634 Current Graphics drivers tend to use physical address
1635 for DMA and avoid using DMA APIs. Setting this config
1636 option permits the IOMMU driver to set a unity map for
1637 all the OS-visible memory. Hence the driver can continue
1638 to use physical addresses for DMA.
1640 config DMAR_FLOPPY_WA
1644 Floppy disk drivers are know to bypass DMA API calls
1645 thereby failing to work when IOMMU is enabled. This
1646 workaround will setup a 1:1 mapping for the first
1647 16M to make floppy (an ISA device) work.
1649 source "drivers/pci/pcie/Kconfig"
1651 source "drivers/pci/Kconfig"
1653 # x86_64 have no ISA slots, but do have ISA-style DMA.
1661 depends on !X86_VOYAGER
1663 Find out whether you have ISA slots on your motherboard. ISA is the
1664 name of a bus system, i.e. the way the CPU talks to the other stuff
1665 inside your box. Other bus systems are PCI, EISA, MicroChannel
1666 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
1667 newer boards don't support it. If you have ISA, say Y, otherwise N.
1673 The Extended Industry Standard Architecture (EISA) bus was
1674 developed as an open alternative to the IBM MicroChannel bus.
1676 The EISA bus provided some of the features of the IBM MicroChannel
1677 bus while maintaining backward compatibility with cards made for
1678 the older ISA bus. The EISA bus saw limited use between 1988 and
1679 1995 when it was made obsolete by the PCI bus.
1681 Say Y here if you are building a kernel for an EISA-based machine.
1685 source "drivers/eisa/Kconfig"
1688 bool "MCA support" if !X86_VOYAGER
1689 default y if X86_VOYAGER
1691 MicroChannel Architecture is found in some IBM PS/2 machines and
1692 laptops. It is a bus system similar to PCI or ISA. See
1693 <file:Documentation/mca.txt> (and especially the web page given
1694 there) before attempting to build an MCA bus kernel.
1696 source "drivers/mca/Kconfig"
1699 tristate "NatSemi SCx200 support"
1700 depends on !X86_VOYAGER
1702 This provides basic support for National Semiconductor's
1703 (now AMD's) Geode processors. The driver probes for the
1704 PCI-IDs of several on-chip devices, so its a good dependency
1705 for other scx200_* drivers.
1707 If compiled as a module, the driver is named scx200.
1709 config SCx200HR_TIMER
1710 tristate "NatSemi SCx200 27MHz High-Resolution Timer Support"
1711 depends on SCx200 && GENERIC_TIME
1714 This driver provides a clocksource built upon the on-chip
1715 27MHz high-resolution timer. Its also a workaround for
1716 NSC Geode SC-1100's buggy TSC, which loses time when the
1717 processor goes idle (as is done by the scheduler). The
1718 other workaround is idle=poll boot option.
1720 config GEODE_MFGPT_TIMER
1722 prompt "Geode Multi-Function General Purpose Timer (MFGPT) events"
1723 depends on MGEODE_LX && GENERIC_TIME && GENERIC_CLOCKEVENTS
1725 This driver provides a clock event source based on the MFGPT
1726 timer(s) in the CS5535 and CS5536 companion chip for the geode.
1727 MFGPTs have a better resolution and max interval than the
1728 generic PIT, and are suitable for use as high-res timers.
1731 bool "One Laptop Per Child support"
1734 Add support for detecting the unique features of the OLPC
1741 depends on AGP_AMD64 || (X86_64 && (GART_IOMMU || (PCI && NUMA)))
1743 source "drivers/pcmcia/Kconfig"
1745 source "drivers/pci/hotplug/Kconfig"
1750 menu "Executable file formats / Emulations"
1752 source "fs/Kconfig.binfmt"
1754 config IA32_EMULATION
1755 bool "IA32 Emulation"
1757 select COMPAT_BINFMT_ELF
1759 Include code to run 32-bit programs under a 64-bit kernel. You should
1760 likely turn this on, unless you're 100% sure that you don't have any
1761 32-bit programs left.
1764 tristate "IA32 a.out support"
1765 depends on IA32_EMULATION && ARCH_SUPPORTS_AOUT
1767 Support old a.out binaries in the 32bit emulation.
1771 depends on IA32_EMULATION
1773 config COMPAT_FOR_U64_ALIGNMENT
1777 config SYSVIPC_COMPAT
1779 depends on X86_64 && COMPAT && SYSVIPC
1784 source "net/Kconfig"
1786 source "drivers/Kconfig"
1788 source "drivers/firmware/Kconfig"
1792 source "arch/x86/Kconfig.debug"
1794 source "security/Kconfig"
1796 source "crypto/Kconfig"
1798 source "arch/x86/kvm/Kconfig"
1800 source "lib/Kconfig"
projects / linux-2.6 / blob