2 mainmenu "Linux Kernel Configuration for x86"
6 bool "64-bit kernel" if ARCH = "x86"
7 default ARCH = "x86_64"
9 Say yes to build a 64-bit kernel - formerly known as x86_64
10 Say no to build a 32-bit kernel - formerly known as i386
21 select HAVE_UNSTABLE_SCHED_CLOCK
25 select HAVE_KRETPROBES
26 select HAVE_KVM if ((X86_32 && !X86_VOYAGER && !X86_VISWS && !X86_NUMAQ) || X86_64)
27 select HAVE_ARCH_KGDB if !X86_VOYAGER
31 default "arch/x86/configs/i386_defconfig" if X86_32
32 default "arch/x86/configs/x86_64_defconfig" if X86_64
35 config GENERIC_LOCKBREAK
41 config GENERIC_CMOS_UPDATE
44 config CLOCKSOURCE_WATCHDOG
47 config GENERIC_CLOCKEVENTS
50 config GENERIC_CLOCKEVENTS_BROADCAST
52 depends on X86_64 || (X86_32 && X86_LOCAL_APIC)
54 config LOCKDEP_SUPPORT
57 config STACKTRACE_SUPPORT
60 config HAVE_LATENCYTOP_SUPPORT
63 config FAST_CMPXCHG_LOCAL
76 config GENERIC_ISA_DMA
86 config GENERIC_HWEIGHT
92 config ARCH_MAY_HAVE_PC_FDC
95 config RWSEM_GENERIC_SPINLOCK
98 config RWSEM_XCHGADD_ALGORITHM
101 config ARCH_HAS_ILOG2_U32
104 config ARCH_HAS_ILOG2_U64
107 config ARCH_HAS_CPU_IDLE_WAIT
110 config GENERIC_CALIBRATE_DELAY
113 config GENERIC_TIME_VSYSCALL
117 config ARCH_HAS_CPU_RELAX
120 config ARCH_HAS_CACHE_LINE_SIZE
123 config HAVE_SETUP_PER_CPU_AREA
124 def_bool X86_64 || (X86_SMP && !X86_VOYAGER)
126 config HAVE_CPUMASK_OF_CPU_MAP
129 config ARCH_HIBERNATION_POSSIBLE
131 depends on !SMP || !X86_VOYAGER
133 config ARCH_SUSPEND_POSSIBLE
135 depends on !X86_VOYAGER
141 config ARCH_POPULATES_NODE_MAP
148 config ARCH_SUPPORTS_AOUT
151 config ARCH_SUPPORTS_OPTIMIZED_INLINING
154 # Use the generic interrupt handling code in kernel/irq/:
155 config GENERIC_HARDIRQS
159 config GENERIC_IRQ_PROBE
163 config GENERIC_PENDING_IRQ
165 depends on GENERIC_HARDIRQS && SMP
170 depends on SMP && ((X86_32 && !X86_VOYAGER) || X86_64)
175 depends on X86_32 && SMP
179 depends on X86_64 && SMP
184 depends on (X86_32 && !(X86_VISWS || X86_VOYAGER)) || X86_64
187 config X86_BIOS_REBOOT
189 depends on !X86_VISWS && !X86_VOYAGER
192 config X86_TRAMPOLINE
194 depends on X86_SMP || (X86_VOYAGER && SMP) || (64BIT && ACPI_SLEEP)
199 source "init/Kconfig"
201 menu "Processor type and features"
203 source "kernel/time/Kconfig"
206 bool "Symmetric multi-processing support"
208 This enables support for systems with more than one CPU. If you have
209 a system with only one CPU, like most personal computers, say N. If
210 you have a system with more than one CPU, say Y.
212 If you say N here, the kernel will run on single and multiprocessor
213 machines, but will use only one CPU of a multiprocessor machine. If
214 you say Y here, the kernel will run on many, but not all,
215 singleprocessor machines. On a singleprocessor machine, the kernel
216 will run faster if you say N here.
218 Note that if you say Y here and choose architecture "586" or
219 "Pentium" under "Processor family", the kernel will not work on 486
220 architectures. Similarly, multiprocessor kernels for the "PPro"
221 architecture may not work on all Pentium based boards.
223 People using multiprocessor machines who say Y here should also say
224 Y to "Enhanced Real Time Clock Support", below. The "Advanced Power
225 Management" code will be disabled if you say Y here.
227 See also <file:Documentation/i386/IO-APIC.txt>,
228 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
229 <http://www.tldp.org/docs.html#howto>.
231 If you don't know what to do here, say N.
234 prompt "Subarchitecture Type"
240 Choose this option if your computer is a standard PC or compatible.
246 Select this for an AMD Elan processor.
248 Do not use this option for K6/Athlon/Opteron processors!
250 If unsure, choose "PC-compatible" instead.
254 depends on X86_32 && (SMP || BROKEN)
256 Voyager is an MCA-based 32-way capable SMP architecture proprietary
257 to NCR Corp. Machine classes 345x/35xx/4100/51xx are Voyager-based.
261 If you do not specifically know you have a Voyager based machine,
262 say N here, otherwise the kernel you build will not be bootable.
265 bool "NUMAQ (IBM/Sequent)"
266 depends on SMP && X86_32
269 This option is used for getting Linux to run on a (IBM/Sequent) NUMA
270 multiquad box. This changes the way that processors are bootstrapped,
271 and uses Clustered Logical APIC addressing mode instead of Flat Logical.
272 You will need a new lynxer.elf file to flash your firmware with - send
273 email to <Martin.Bligh@us.ibm.com>.
276 bool "Summit/EXA (IBM x440)"
277 depends on X86_32 && SMP
279 This option is needed for IBM systems that use the Summit/EXA chipset.
280 In particular, it is needed for the x440.
282 If you don't have one of these computers, you should say N here.
283 If you want to build a NUMA kernel, you must select ACPI.
286 bool "Support for other sub-arch SMP systems with more than 8 CPUs"
287 depends on X86_32 && SMP
289 This option is needed for the systems that have more than 8 CPUs
290 and if the system is not of any sub-arch type above.
292 If you don't have such a system, you should say N here.
295 bool "SGI 320/540 (Visual Workstation)"
298 The SGI Visual Workstation series is an IA32-based workstation
299 based on SGI systems chips with some legacy PC hardware attached.
301 Say Y here to create a kernel to run on the SGI 320 or 540.
303 A kernel compiled for the Visual Workstation will not run on PCs
304 and vice versa. See <file:Documentation/sgi-visws.txt> for details.
306 config X86_GENERICARCH
307 bool "Generic architecture (Summit, bigsmp, ES7000, default)"
310 This option compiles in the Summit, bigsmp, ES7000, default subarchitectures.
311 It is intended for a generic binary kernel.
312 If you want a NUMA kernel, select ACPI. We need SRAT for NUMA.
315 bool "Support for Unisys ES7000 IA32 series"
316 depends on X86_32 && SMP
318 Support for Unisys ES7000 systems. Say 'Y' here if this kernel is
319 supposed to run on an IA32-based Unisys ES7000 system.
320 Only choose this option if you have such a system, otherwise you
324 bool "RDC R-321x SoC"
327 select X86_REBOOTFIXUPS
333 This option is needed for RDC R-321x system-on-chip, also known
335 If you don't have one of these chips, you should say N here.
338 bool "Support for ScaleMP vSMP"
342 Support for ScaleMP vSMP systems. Say 'Y' here if this kernel is
343 supposed to run on these EM64T-based machines. Only choose this option
344 if you have one of these machines.
348 config SCHED_NO_NO_OMIT_FRAME_POINTER
350 prompt "Single-depth WCHAN output"
353 Calculate simpler /proc/<PID>/wchan values. If this option
354 is disabled then wchan values will recurse back to the
355 caller function. This provides more accurate wchan values,
356 at the expense of slightly more scheduling overhead.
358 If in doubt, say "Y".
360 menuconfig PARAVIRT_GUEST
361 bool "Paravirtualized guest support"
363 Say Y here to get to see options related to running Linux under
364 various hypervisors. This option alone does not add any kernel code.
366 If you say N, all options in this submenu will be skipped and disabled.
370 source "arch/x86/xen/Kconfig"
373 bool "VMI Guest support"
376 depends on !(X86_VISWS || X86_VOYAGER)
378 VMI provides a paravirtualized interface to the VMware ESX server
379 (it could be used by other hypervisors in theory too, but is not
380 at the moment), by linking the kernel to a GPL-ed ROM module
381 provided by the hypervisor.
384 bool "KVM paravirtualized clock"
386 select PARAVIRT_CLOCK
387 depends on !(X86_VISWS || X86_VOYAGER)
389 Turning on this option will allow you to run a paravirtualized clock
390 when running over the KVM hypervisor. Instead of relying on a PIT
391 (or probably other) emulation by the underlying device model, the host
392 provides the guest with timing infrastructure such as time of day, and
396 bool "KVM Guest support"
398 depends on !(X86_VISWS || X86_VOYAGER)
400 This option enables various optimizations for running under the KVM
403 source "arch/x86/lguest/Kconfig"
406 bool "Enable paravirtualization code"
407 depends on !(X86_VISWS || X86_VOYAGER)
409 This changes the kernel so it can modify itself when it is run
410 under a hypervisor, potentially improving performance significantly
411 over full virtualization. However, when run without a hypervisor
412 the kernel is theoretically slower and slightly larger.
414 config PARAVIRT_CLOCK
420 config MEMTEST_BOOTPARAM
421 bool "Memtest boot parameter"
425 This option adds a kernel parameter 'memtest', which allows memtest
426 to be disabled at boot. If this option is selected, memtest
427 functionality can be disabled with memtest=0 on the kernel
428 command line. The purpose of this option is to allow a single
429 kernel image to be distributed with memtest built in, but not
432 If you are unsure how to answer this question, answer Y.
434 config MEMTEST_BOOTPARAM_VALUE
435 int "Memtest boot parameter default value (0-4)"
436 depends on MEMTEST_BOOTPARAM
440 This option sets the default value for the kernel parameter
441 'memtest', which allows memtest to be disabled at boot. If this
442 option is set to 0 (zero), the memtest kernel parameter will
443 default to 0, disabling memtest at bootup. If this option is
444 set to 4, the memtest kernel parameter will default to 4,
445 enabling memtest at bootup, and use that as pattern number.
447 If you are unsure how to answer this question, answer 0.
451 depends on X86_32 && ACPI && NUMA && (X86_SUMMIT || X86_GENERICARCH)
454 config HAVE_ARCH_PARSE_SRAT
458 config X86_SUMMIT_NUMA
460 depends on X86_32 && NUMA && (X86_SUMMIT || X86_GENERICARCH)
462 config X86_CYCLONE_TIMER
464 depends on X86_32 && X86_SUMMIT || X86_GENERICARCH
466 config ES7000_CLUSTERED_APIC
468 depends on SMP && X86_ES7000 && MPENTIUMIII
470 source "arch/x86/Kconfig.cpu"
474 prompt "HPET Timer Support" if X86_32
476 Use the IA-PC HPET (High Precision Event Timer) to manage
477 time in preference to the PIT and RTC, if a HPET is
479 HPET is the next generation timer replacing legacy 8254s.
480 The HPET provides a stable time base on SMP
481 systems, unlike the TSC, but it is more expensive to access,
482 as it is off-chip. You can find the HPET spec at
483 <http://www.intel.com/hardwaredesign/hpetspec.htm>.
485 You can safely choose Y here. However, HPET will only be
486 activated if the platform and the BIOS support this feature.
487 Otherwise the 8254 will be used for timing services.
489 Choose N to continue using the legacy 8254 timer.
491 config HPET_EMULATE_RTC
493 depends on HPET_TIMER && (RTC=y || RTC=m || RTC_DRV_CMOS=m || RTC_DRV_CMOS=y)
495 # Mark as embedded because too many people got it wrong.
496 # The code disables itself when not needed.
499 bool "Enable DMI scanning" if EMBEDDED
501 Enabled scanning of DMI to identify machine quirks. Say Y
502 here unless you have verified that your setup is not
503 affected by entries in the DMI blacklist. Required by PNP
507 bool "GART IOMMU support" if EMBEDDED
511 depends on X86_64 && PCI
513 Support for full DMA access of devices with 32bit memory access only
514 on systems with more than 3GB. This is usually needed for USB,
515 sound, many IDE/SATA chipsets and some other devices.
516 Provides a driver for the AMD Athlon64/Opteron/Turion/Sempron GART
517 based hardware IOMMU and a software bounce buffer based IOMMU used
518 on Intel systems and as fallback.
519 The code is only active when needed (enough memory and limited
520 device) unless CONFIG_IOMMU_DEBUG or iommu=force is specified
524 bool "IBM Calgary IOMMU support"
526 depends on X86_64 && PCI && EXPERIMENTAL
528 Support for hardware IOMMUs in IBM's xSeries x366 and x460
529 systems. Needed to run systems with more than 3GB of memory
530 properly with 32-bit PCI devices that do not support DAC
531 (Double Address Cycle). Calgary also supports bus level
532 isolation, where all DMAs pass through the IOMMU. This
533 prevents them from going anywhere except their intended
534 destination. This catches hard-to-find kernel bugs and
535 mis-behaving drivers and devices that do not use the DMA-API
536 properly to set up their DMA buffers. The IOMMU can be
537 turned off at boot time with the iommu=off parameter.
538 Normally the kernel will make the right choice by itself.
541 config CALGARY_IOMMU_ENABLED_BY_DEFAULT
543 prompt "Should Calgary be enabled by default?"
544 depends on CALGARY_IOMMU
546 Should Calgary be enabled by default? if you choose 'y', Calgary
547 will be used (if it exists). If you choose 'n', Calgary will not be
548 used even if it exists. If you choose 'n' and would like to use
549 Calgary anyway, pass 'iommu=calgary' on the kernel command line.
553 bool "AMD IOMMU support"
555 depends on X86_64 && PCI && ACPI
557 With this option you can enable support for AMD IOMMU hardware in
558 your system. An IOMMU is a hardware component which provides
559 remapping of DMA memory accesses from devices. With an AMD IOMMU you
560 can isolate the the DMA memory of different devices and protect the
561 system from misbehaving device drivers or hardware.
563 You can find out if your system has an AMD IOMMU if you look into
564 your BIOS for an option to enable it or if you have an IVRS ACPI
567 # need this always selected by IOMMU for the VIA workaround
571 Support for software bounce buffers used on x86-64 systems
572 which don't have a hardware IOMMU (e.g. the current generation
573 of Intel's x86-64 CPUs). Using this PCI devices which can only
574 access 32-bits of memory can be used on systems with more than
575 3 GB of memory. If unsure, say Y.
578 def_bool (CALGARY_IOMMU || GART_IOMMU || SWIOTLB)
581 int "Maximum number of CPUs (2-255)"
584 default "32" if X86_NUMAQ || X86_SUMMIT || X86_BIGSMP || X86_ES7000
587 This allows you to specify the maximum number of CPUs which this
588 kernel will support. The maximum supported value is 255 and the
589 minimum value which makes sense is 2.
591 This is purely to save memory - each supported CPU adds
592 approximately eight kilobytes to the kernel image.
595 bool "SMT (Hyperthreading) scheduler support"
598 SMT scheduler support improves the CPU scheduler's decision making
599 when dealing with Intel Pentium 4 chips with HyperThreading at a
600 cost of slightly increased overhead in some places. If unsure say
605 prompt "Multi-core scheduler support"
608 Multi-core scheduler support improves the CPU scheduler's decision
609 making when dealing with multi-core CPU chips at a cost of slightly
610 increased overhead in some places. If unsure say N here.
612 source "kernel/Kconfig.preempt"
615 bool "Local APIC support on uniprocessors"
616 depends on X86_32 && !SMP && !(X86_VISWS || X86_VOYAGER || X86_GENERICARCH)
618 A local APIC (Advanced Programmable Interrupt Controller) is an
619 integrated interrupt controller in the CPU. If you have a single-CPU
620 system which has a processor with a local APIC, you can say Y here to
621 enable and use it. If you say Y here even though your machine doesn't
622 have a local APIC, then the kernel will still run with no slowdown at
623 all. The local APIC supports CPU-generated self-interrupts (timer,
624 performance counters), and the NMI watchdog which detects hard
628 bool "IO-APIC support on uniprocessors"
629 depends on X86_UP_APIC
631 An IO-APIC (I/O Advanced Programmable Interrupt Controller) is an
632 SMP-capable replacement for PC-style interrupt controllers. Most
633 SMP systems and many recent uniprocessor systems have one.
635 If you have a single-CPU system with an IO-APIC, you can say Y here
636 to use it. If you say Y here even though your machine doesn't have
637 an IO-APIC, then the kernel will still run with no slowdown at all.
639 config X86_LOCAL_APIC
641 depends on X86_64 || (X86_32 && (X86_UP_APIC || ((X86_VISWS || SMP) && !X86_VOYAGER) || X86_GENERICARCH))
645 depends on X86_64 || (X86_32 && (X86_UP_IOAPIC || (SMP && !(X86_VISWS || X86_VOYAGER)) || X86_GENERICARCH))
647 config X86_VISWS_APIC
649 depends on X86_32 && X86_VISWS
652 bool "Machine Check Exception"
653 depends on !X86_VOYAGER
655 Machine Check Exception support allows the processor to notify the
656 kernel if it detects a problem (e.g. overheating, component failure).
657 The action the kernel takes depends on the severity of the problem,
658 ranging from a warning message on the console, to halting the machine.
659 Your processor must be a Pentium or newer to support this - check the
660 flags in /proc/cpuinfo for mce. Note that some older Pentium systems
661 have a design flaw which leads to false MCE events - hence MCE is
662 disabled on all P5 processors, unless explicitly enabled with "mce"
663 as a boot argument. Similarly, if MCE is built in and creates a
664 problem on some new non-standard machine, you can boot with "nomce"
665 to disable it. MCE support simply ignores non-MCE processors like
666 the 386 and 486, so nearly everyone can say Y here.
670 prompt "Intel MCE features"
671 depends on X86_64 && X86_MCE && X86_LOCAL_APIC
673 Additional support for intel specific MCE features such as
678 prompt "AMD MCE features"
679 depends on X86_64 && X86_MCE && X86_LOCAL_APIC
681 Additional support for AMD specific MCE features such as
682 the DRAM Error Threshold.
684 config X86_MCE_NONFATAL
685 tristate "Check for non-fatal errors on AMD Athlon/Duron / Intel Pentium 4"
686 depends on X86_32 && X86_MCE
688 Enabling this feature starts a timer that triggers every 5 seconds which
689 will look at the machine check registers to see if anything happened.
690 Non-fatal problems automatically get corrected (but still logged).
691 Disable this if you don't want to see these messages.
692 Seeing the messages this option prints out may be indicative of dying
693 or out-of-spec (ie, overclocked) hardware.
694 This option only does something on certain CPUs.
695 (AMD Athlon/Duron and Intel Pentium 4)
697 config X86_MCE_P4THERMAL
698 bool "check for P4 thermal throttling interrupt."
699 depends on X86_32 && X86_MCE && (X86_UP_APIC || SMP) && !X86_VISWS
701 Enabling this feature will cause a message to be printed when the P4
702 enters thermal throttling.
705 bool "Enable VM86 support" if EMBEDDED
709 This option is required by programs like DOSEMU to run 16-bit legacy
710 code on X86 processors. It also may be needed by software like
711 XFree86 to initialize some video cards via BIOS. Disabling this
712 option saves about 6k.
715 tristate "Toshiba Laptop support"
718 This adds a driver to safely access the System Management Mode of
719 the CPU on Toshiba portables with a genuine Toshiba BIOS. It does
720 not work on models with a Phoenix BIOS. The System Management Mode
721 is used to set the BIOS and power saving options on Toshiba portables.
723 For information on utilities to make use of this driver see the
724 Toshiba Linux utilities web site at:
725 <http://www.buzzard.org.uk/toshiba/>.
727 Say Y if you intend to run this kernel on a Toshiba portable.
731 tristate "Dell laptop support"
733 This adds a driver to safely access the System Management Mode
734 of the CPU on the Dell Inspiron 8000. The System Management Mode
735 is used to read cpu temperature and cooling fan status and to
736 control the fans on the I8K portables.
738 This driver has been tested only on the Inspiron 8000 but it may
739 also work with other Dell laptops. You can force loading on other
740 models by passing the parameter `force=1' to the module. Use at
743 For information on utilities to make use of this driver see the
744 I8K Linux utilities web site at:
745 <http://people.debian.org/~dz/i8k/>
747 Say Y if you intend to run this kernel on a Dell Inspiron 8000.
750 config X86_REBOOTFIXUPS
752 prompt "Enable X86 board specific fixups for reboot"
753 depends on X86_32 && X86
755 This enables chipset and/or board specific fixups to be done
756 in order to get reboot to work correctly. This is only needed on
757 some combinations of hardware and BIOS. The symptom, for which
758 this config is intended, is when reboot ends with a stalled/hung
761 Currently, the only fixup is for the Geode machines using
762 CS5530A and CS5536 chipsets and the RDC R-321x SoC.
764 Say Y if you want to enable the fixup. Currently, it's safe to
765 enable this option even if you don't need it.
769 tristate "/dev/cpu/microcode - Intel IA32 CPU microcode support"
772 If you say Y here, you will be able to update the microcode on
773 Intel processors in the IA32 family, e.g. Pentium Pro, Pentium II,
774 Pentium III, Pentium 4, Xeon etc. You will obviously need the
775 actual microcode binary data itself which is not shipped with the
778 For latest news and information on obtaining all the required
779 ingredients for this driver, check:
780 <http://www.urbanmyth.org/microcode/>.
782 To compile this driver as a module, choose M here: the
783 module will be called microcode.
785 config MICROCODE_OLD_INTERFACE
790 tristate "/dev/cpu/*/msr - Model-specific register support"
792 This device gives privileged processes access to the x86
793 Model-Specific Registers (MSRs). It is a character device with
794 major 202 and minors 0 to 31 for /dev/cpu/0/msr to /dev/cpu/31/msr.
795 MSR accesses are directed to a specific CPU on multi-processor
799 tristate "/dev/cpu/*/cpuid - CPU information support"
801 This device gives processes access to the x86 CPUID instruction to
802 be executed on a specific processor. It is a character device
803 with major 203 and minors 0 to 31 for /dev/cpu/0/cpuid to
807 prompt "High Memory Support"
808 default HIGHMEM4G if !X86_NUMAQ
809 default HIGHMEM64G if X86_NUMAQ
814 depends on !X86_NUMAQ
816 Linux can use up to 64 Gigabytes of physical memory on x86 systems.
817 However, the address space of 32-bit x86 processors is only 4
818 Gigabytes large. That means that, if you have a large amount of
819 physical memory, not all of it can be "permanently mapped" by the
820 kernel. The physical memory that's not permanently mapped is called
823 If you are compiling a kernel which will never run on a machine with
824 more than 1 Gigabyte total physical RAM, answer "off" here (default
825 choice and suitable for most users). This will result in a "3GB/1GB"
826 split: 3GB are mapped so that each process sees a 3GB virtual memory
827 space and the remaining part of the 4GB virtual memory space is used
828 by the kernel to permanently map as much physical memory as
831 If the machine has between 1 and 4 Gigabytes physical RAM, then
834 If more than 4 Gigabytes is used then answer "64GB" here. This
835 selection turns Intel PAE (Physical Address Extension) mode on.
836 PAE implements 3-level paging on IA32 processors. PAE is fully
837 supported by Linux, PAE mode is implemented on all recent Intel
838 processors (Pentium Pro and better). NOTE: If you say "64GB" here,
839 then the kernel will not boot on CPUs that don't support PAE!
841 The actual amount of total physical memory will either be
842 auto detected or can be forced by using a kernel command line option
843 such as "mem=256M". (Try "man bootparam" or see the documentation of
844 your boot loader (lilo or loadlin) about how to pass options to the
845 kernel at boot time.)
847 If unsure, say "off".
851 depends on !X86_NUMAQ
853 Select this if you have a 32-bit processor and between 1 and 4
854 gigabytes of physical RAM.
858 depends on !M386 && !M486
861 Select this if you have a 32-bit processor and more than 4
862 gigabytes of physical RAM.
867 depends on EXPERIMENTAL
868 prompt "Memory split" if EMBEDDED
872 Select the desired split between kernel and user memory.
874 If the address range available to the kernel is less than the
875 physical memory installed, the remaining memory will be available
876 as "high memory". Accessing high memory is a little more costly
877 than low memory, as it needs to be mapped into the kernel first.
878 Note that increasing the kernel address space limits the range
879 available to user programs, making the address space there
880 tighter. Selecting anything other than the default 3G/1G split
881 will also likely make your kernel incompatible with binary-only
884 If you are not absolutely sure what you are doing, leave this
888 bool "3G/1G user/kernel split"
889 config VMSPLIT_3G_OPT
891 bool "3G/1G user/kernel split (for full 1G low memory)"
893 bool "2G/2G user/kernel split"
894 config VMSPLIT_2G_OPT
896 bool "2G/2G user/kernel split (for full 2G low memory)"
898 bool "1G/3G user/kernel split"
903 default 0xB0000000 if VMSPLIT_3G_OPT
904 default 0x80000000 if VMSPLIT_2G
905 default 0x78000000 if VMSPLIT_2G_OPT
906 default 0x40000000 if VMSPLIT_1G
912 depends on X86_32 && (HIGHMEM64G || HIGHMEM4G)
916 prompt "PAE (Physical Address Extension) Support"
917 depends on X86_32 && !HIGHMEM4G
918 select RESOURCES_64BIT
920 PAE is required for NX support, and furthermore enables
921 larger swapspace support for non-overcommit purposes. It
922 has the cost of more pagetable lookup overhead, and also
923 consumes more pagetable space per process.
925 # Common NUMA Features
927 bool "Numa Memory Allocation and Scheduler Support (EXPERIMENTAL)"
929 depends on X86_64 || (X86_32 && HIGHMEM64G && (X86_NUMAQ || (X86_SUMMIT || X86_GENERICARCH) && ACPI) && EXPERIMENTAL)
931 default y if (X86_NUMAQ || X86_SUMMIT)
933 Enable NUMA (Non Uniform Memory Access) support.
934 The kernel will try to allocate memory used by a CPU on the
935 local memory controller of the CPU and add some more
936 NUMA awareness to the kernel.
938 For i386 this is currently highly experimental and should be only
939 used for kernel development. It might also cause boot failures.
940 For x86_64 this is recommended on all multiprocessor Opteron systems.
941 If the system is EM64T, you should say N unless your system is
944 comment "NUMA (Summit) requires SMP, 64GB highmem support, ACPI"
945 depends on X86_32 && X86_SUMMIT && (!HIGHMEM64G || !ACPI)
949 prompt "Old style AMD Opteron NUMA detection"
950 depends on X86_64 && NUMA && PCI
952 Enable K8 NUMA node topology detection. You should say Y here if
953 you have a multi processor AMD K8 system. This uses an old
954 method to read the NUMA configuration directly from the builtin
955 Northbridge of Opteron. It is recommended to use X86_64_ACPI_NUMA
956 instead, which also takes priority if both are compiled in.
958 config X86_64_ACPI_NUMA
960 prompt "ACPI NUMA detection"
961 depends on X86_64 && NUMA && ACPI && PCI
964 Enable ACPI SRAT based node topology detection.
966 # Some NUMA nodes have memory ranges that span
967 # other nodes. Even though a pfn is valid and
968 # between a node's start and end pfns, it may not
969 # reside on that node. See memmap_init_zone()
971 config NODES_SPAN_OTHER_NODES
973 depends on X86_64_ACPI_NUMA
976 bool "NUMA emulation"
977 depends on X86_64 && NUMA
979 Enable NUMA emulation. A flat machine will be split
980 into virtual nodes when booted with "numa=fake=N", where N is the
981 number of nodes. This is only useful for debugging.
984 int "Max num nodes shift(1-15)"
986 default "6" if X86_64
987 default "4" if X86_NUMAQ
989 depends on NEED_MULTIPLE_NODES
991 config HAVE_ARCH_BOOTMEM_NODE
993 depends on X86_32 && NUMA
995 config ARCH_HAVE_MEMORY_PRESENT
997 depends on X86_32 && DISCONTIGMEM
999 config NEED_NODE_MEMMAP_SIZE
1001 depends on X86_32 && (DISCONTIGMEM || SPARSEMEM)
1003 config HAVE_ARCH_ALLOC_REMAP
1005 depends on X86_32 && NUMA
1007 config ARCH_FLATMEM_ENABLE
1009 depends on X86_32 && ARCH_SELECT_MEMORY_MODEL && X86_PC && !NUMA
1011 config ARCH_DISCONTIGMEM_ENABLE
1013 depends on NUMA && X86_32
1015 config ARCH_DISCONTIGMEM_DEFAULT
1017 depends on NUMA && X86_32
1019 config ARCH_SPARSEMEM_DEFAULT
1023 config ARCH_SPARSEMEM_ENABLE
1025 depends on X86_64 || NUMA || (EXPERIMENTAL && X86_PC)
1026 select SPARSEMEM_STATIC if X86_32
1027 select SPARSEMEM_VMEMMAP_ENABLE if X86_64
1029 config ARCH_SELECT_MEMORY_MODEL
1031 depends on ARCH_SPARSEMEM_ENABLE
1033 config ARCH_MEMORY_PROBE
1035 depends on MEMORY_HOTPLUG
1040 bool "Allocate 3rd-level pagetables from highmem"
1041 depends on X86_32 && (HIGHMEM4G || HIGHMEM64G)
1043 The VM uses one page table entry for each page of physical memory.
1044 For systems with a lot of RAM, this can be wasteful of precious
1045 low memory. Setting this option will put user-space page table
1046 entries in high memory.
1048 config MATH_EMULATION
1050 prompt "Math emulation" if X86_32
1052 Linux can emulate a math coprocessor (used for floating point
1053 operations) if you don't have one. 486DX and Pentium processors have
1054 a math coprocessor built in, 486SX and 386 do not, unless you added
1055 a 487DX or 387, respectively. (The messages during boot time can
1056 give you some hints here ["man dmesg"].) Everyone needs either a
1057 coprocessor or this emulation.
1059 If you don't have a math coprocessor, you need to say Y here; if you
1060 say Y here even though you have a coprocessor, the coprocessor will
1061 be used nevertheless. (This behavior can be changed with the kernel
1062 command line option "no387", which comes handy if your coprocessor
1063 is broken. Try "man bootparam" or see the documentation of your boot
1064 loader (lilo or loadlin) about how to pass options to the kernel at
1065 boot time.) This means that it is a good idea to say Y here if you
1066 intend to use this kernel on different machines.
1068 More information about the internals of the Linux math coprocessor
1069 emulation can be found in <file:arch/x86/math-emu/README>.
1071 If you are not sure, say Y; apart from resulting in a 66 KB bigger
1072 kernel, it won't hurt.
1075 bool "MTRR (Memory Type Range Register) support"
1077 On Intel P6 family processors (Pentium Pro, Pentium II and later)
1078 the Memory Type Range Registers (MTRRs) may be used to control
1079 processor access to memory ranges. This is most useful if you have
1080 a video (VGA) card on a PCI or AGP bus. Enabling write-combining
1081 allows bus write transfers to be combined into a larger transfer
1082 before bursting over the PCI/AGP bus. This can increase performance
1083 of image write operations 2.5 times or more. Saying Y here creates a
1084 /proc/mtrr file which may be used to manipulate your processor's
1085 MTRRs. Typically the X server should use this.
1087 This code has a reasonably generic interface so that similar
1088 control registers on other processors can be easily supported
1091 The Cyrix 6x86, 6x86MX and M II processors have Address Range
1092 Registers (ARRs) which provide a similar functionality to MTRRs. For
1093 these, the ARRs are used to emulate the MTRRs.
1094 The AMD K6-2 (stepping 8 and above) and K6-3 processors have two
1095 MTRRs. The Centaur C6 (WinChip) has 8 MCRs, allowing
1096 write-combining. All of these processors are supported by this code
1097 and it makes sense to say Y here if you have one of them.
1099 Saying Y here also fixes a problem with buggy SMP BIOSes which only
1100 set the MTRRs for the boot CPU and not for the secondary CPUs. This
1101 can lead to all sorts of problems, so it's good to say Y here.
1103 You can safely say Y even if your machine doesn't have MTRRs, you'll
1104 just add about 9 KB to your kernel.
1106 See <file:Documentation/mtrr.txt> for more information.
1110 prompt "x86 PAT support"
1113 Use PAT attributes to setup page level cache control.
1115 PATs are the modern equivalents of MTRRs and are much more
1116 flexible than MTRRs.
1118 Say N here if you see bootup problems (boot crash, boot hang,
1119 spontaneous reboots) or a non-working video driver.
1125 prompt "EFI runtime service support"
1128 This enables the kernel to use EFI runtime services that are
1129 available (such as the EFI variable services).
1131 This option is only useful on systems that have EFI firmware.
1132 In addition, you should use the latest ELILO loader available
1133 at <http://elilo.sourceforge.net> in order to take advantage
1134 of EFI runtime services. However, even with this option, the
1135 resultant kernel should continue to boot on existing non-EFI
1140 prompt "Enable kernel irq balancing"
1141 depends on X86_32 && SMP && X86_IO_APIC
1143 The default yes will allow the kernel to do irq load balancing.
1144 Saying no will keep the kernel from doing irq load balancing.
1148 prompt "Enable seccomp to safely compute untrusted bytecode"
1151 This kernel feature is useful for number crunching applications
1152 that may need to compute untrusted bytecode during their
1153 execution. By using pipes or other transports made available to
1154 the process as file descriptors supporting the read/write
1155 syscalls, it's possible to isolate those applications in
1156 their own address space using seccomp. Once seccomp is
1157 enabled via /proc/<pid>/seccomp, it cannot be disabled
1158 and the task is only allowed to execute a few safe syscalls
1159 defined by each seccomp mode.
1161 If unsure, say Y. Only embedded should say N here.
1163 config CC_STACKPROTECTOR
1164 bool "Enable -fstack-protector buffer overflow detection (EXPERIMENTAL)"
1165 depends on X86_64 && EXPERIMENTAL && BROKEN
1167 This option turns on the -fstack-protector GCC feature. This
1168 feature puts, at the beginning of critical functions, a canary
1169 value on the stack just before the return address, and validates
1170 the value just before actually returning. Stack based buffer
1171 overflows (that need to overwrite this return address) now also
1172 overwrite the canary, which gets detected and the attack is then
1173 neutralized via a kernel panic.
1175 This feature requires gcc version 4.2 or above, or a distribution
1176 gcc with the feature backported. Older versions are automatically
1177 detected and for those versions, this configuration option is ignored.
1179 config CC_STACKPROTECTOR_ALL
1180 bool "Use stack-protector for all functions"
1181 depends on CC_STACKPROTECTOR
1183 Normally, GCC only inserts the canary value protection for
1184 functions that use large-ish on-stack buffers. By enabling
1185 this option, GCC will be asked to do this for ALL functions.
1187 source kernel/Kconfig.hz
1190 bool "kexec system call"
1191 depends on X86_BIOS_REBOOT
1193 kexec is a system call that implements the ability to shutdown your
1194 current kernel, and to start another kernel. It is like a reboot
1195 but it is independent of the system firmware. And like a reboot
1196 you can start any kernel with it, not just Linux.
1198 The name comes from the similarity to the exec system call.
1200 It is an ongoing process to be certain the hardware in a machine
1201 is properly shutdown, so do not be surprised if this code does not
1202 initially work for you. It may help to enable device hotplugging
1203 support. As of this writing the exact hardware interface is
1204 strongly in flux, so no good recommendation can be made.
1207 bool "kernel crash dumps (EXPERIMENTAL)"
1208 depends on EXPERIMENTAL
1209 depends on X86_64 || (X86_32 && HIGHMEM)
1211 Generate crash dump after being started by kexec.
1212 This should be normally only set in special crash dump kernels
1213 which are loaded in the main kernel with kexec-tools into
1214 a specially reserved region and then later executed after
1215 a crash by kdump/kexec. The crash dump kernel must be compiled
1216 to a memory address not used by the main kernel or BIOS using
1217 PHYSICAL_START, or it must be built as a relocatable image
1218 (CONFIG_RELOCATABLE=y).
1219 For more details see Documentation/kdump/kdump.txt
1221 config PHYSICAL_START
1222 hex "Physical address where the kernel is loaded" if (EMBEDDED || CRASH_DUMP)
1223 default "0x1000000" if X86_NUMAQ
1224 default "0x200000" if X86_64
1227 This gives the physical address where the kernel is loaded.
1229 If kernel is a not relocatable (CONFIG_RELOCATABLE=n) then
1230 bzImage will decompress itself to above physical address and
1231 run from there. Otherwise, bzImage will run from the address where
1232 it has been loaded by the boot loader and will ignore above physical
1235 In normal kdump cases one does not have to set/change this option
1236 as now bzImage can be compiled as a completely relocatable image
1237 (CONFIG_RELOCATABLE=y) and be used to load and run from a different
1238 address. This option is mainly useful for the folks who don't want
1239 to use a bzImage for capturing the crash dump and want to use a
1240 vmlinux instead. vmlinux is not relocatable hence a kernel needs
1241 to be specifically compiled to run from a specific memory area
1242 (normally a reserved region) and this option comes handy.
1244 So if you are using bzImage for capturing the crash dump, leave
1245 the value here unchanged to 0x100000 and set CONFIG_RELOCATABLE=y.
1246 Otherwise if you plan to use vmlinux for capturing the crash dump
1247 change this value to start of the reserved region (Typically 16MB
1248 0x1000000). In other words, it can be set based on the "X" value as
1249 specified in the "crashkernel=YM@XM" command line boot parameter
1250 passed to the panic-ed kernel. Typically this parameter is set as
1251 crashkernel=64M@16M. Please take a look at
1252 Documentation/kdump/kdump.txt for more details about crash dumps.
1254 Usage of bzImage for capturing the crash dump is recommended as
1255 one does not have to build two kernels. Same kernel can be used
1256 as production kernel and capture kernel. Above option should have
1257 gone away after relocatable bzImage support is introduced. But it
1258 is present because there are users out there who continue to use
1259 vmlinux for dump capture. This option should go away down the
1262 Don't change this unless you know what you are doing.
1265 bool "Build a relocatable kernel (EXPERIMENTAL)"
1266 depends on EXPERIMENTAL
1268 This builds a kernel image that retains relocation information
1269 so it can be loaded someplace besides the default 1MB.
1270 The relocations tend to make the kernel binary about 10% larger,
1271 but are discarded at runtime.
1273 One use is for the kexec on panic case where the recovery kernel
1274 must live at a different physical address than the primary
1277 Note: If CONFIG_RELOCATABLE=y, then the kernel runs from the address
1278 it has been loaded at and the compile time physical address
1279 (CONFIG_PHYSICAL_START) is ignored.
1281 config PHYSICAL_ALIGN
1283 prompt "Alignment value to which kernel should be aligned" if X86_32
1284 default "0x100000" if X86_32
1285 default "0x200000" if X86_64
1286 range 0x2000 0x400000
1288 This value puts the alignment restrictions on physical address
1289 where kernel is loaded and run from. Kernel is compiled for an
1290 address which meets above alignment restriction.
1292 If bootloader loads the kernel at a non-aligned address and
1293 CONFIG_RELOCATABLE is set, kernel will move itself to nearest
1294 address aligned to above value and run from there.
1296 If bootloader loads the kernel at a non-aligned address and
1297 CONFIG_RELOCATABLE is not set, kernel will ignore the run time
1298 load address and decompress itself to the address it has been
1299 compiled for and run from there. The address for which kernel is
1300 compiled already meets above alignment restrictions. Hence the
1301 end result is that kernel runs from a physical address meeting
1302 above alignment restrictions.
1304 Don't change this unless you know what you are doing.
1307 bool "Support for suspend on SMP and hot-pluggable CPUs (EXPERIMENTAL)"
1308 depends on SMP && HOTPLUG && EXPERIMENTAL && !X86_VOYAGER
1310 Say Y here to experiment with turning CPUs off and on, and to
1311 enable suspend on SMP systems. CPUs can be controlled through
1312 /sys/devices/system/cpu.
1313 Say N if you want to disable CPU hotplug and don't need to
1318 prompt "Compat VDSO support"
1319 depends on X86_32 || IA32_EMULATION
1321 Map the 32-bit VDSO to the predictable old-style address too.
1323 Say N here if you are running a sufficiently recent glibc
1324 version (2.3.3 or later), to remove the high-mapped
1325 VDSO mapping and to exclusively use the randomized VDSO.
1331 config ARCH_ENABLE_MEMORY_HOTPLUG
1333 depends on X86_64 || (X86_32 && HIGHMEM)
1335 config HAVE_ARCH_EARLY_PFN_TO_NID
1339 menu "Power management options"
1340 depends on !X86_VOYAGER
1342 config ARCH_HIBERNATION_HEADER
1344 depends on X86_64 && HIBERNATION
1346 source "kernel/power/Kconfig"
1348 source "drivers/acpi/Kconfig"
1353 depends on APM || APM_MODULE
1356 tristate "APM (Advanced Power Management) BIOS support"
1357 depends on X86_32 && PM_SLEEP && !X86_VISWS
1359 APM is a BIOS specification for saving power using several different
1360 techniques. This is mostly useful for battery powered laptops with
1361 APM compliant BIOSes. If you say Y here, the system time will be
1362 reset after a RESUME operation, the /proc/apm device will provide
1363 battery status information, and user-space programs will receive
1364 notification of APM "events" (e.g. battery status change).
1366 If you select "Y" here, you can disable actual use of the APM
1367 BIOS by passing the "apm=off" option to the kernel at boot time.
1369 Note that the APM support is almost completely disabled for
1370 machines with more than one CPU.
1372 In order to use APM, you will need supporting software. For location
1373 and more information, read <file:Documentation/power/pm.txt> and the
1374 Battery Powered Linux mini-HOWTO, available from
1375 <http://www.tldp.org/docs.html#howto>.
1377 This driver does not spin down disk drives (see the hdparm(8)
1378 manpage ("man 8 hdparm") for that), and it doesn't turn off
1379 VESA-compliant "green" monitors.
1381 This driver does not support the TI 4000M TravelMate and the ACER
1382 486/DX4/75 because they don't have compliant BIOSes. Many "green"
1383 desktop machines also don't have compliant BIOSes, and this driver
1384 may cause those machines to panic during the boot phase.
1386 Generally, if you don't have a battery in your machine, there isn't
1387 much point in using this driver and you should say N. If you get
1388 random kernel OOPSes or reboots that don't seem to be related to
1389 anything, try disabling/enabling this option (or disabling/enabling
1392 Some other things you should try when experiencing seemingly random,
1395 1) make sure that you have enough swap space and that it is
1397 2) pass the "no-hlt" option to the kernel
1398 3) switch on floating point emulation in the kernel and pass
1399 the "no387" option to the kernel
1400 4) pass the "floppy=nodma" option to the kernel
1401 5) pass the "mem=4M" option to the kernel (thereby disabling
1402 all but the first 4 MB of RAM)
1403 6) make sure that the CPU is not over clocked.
1404 7) read the sig11 FAQ at <http://www.bitwizard.nl/sig11/>
1405 8) disable the cache from your BIOS settings
1406 9) install a fan for the video card or exchange video RAM
1407 10) install a better fan for the CPU
1408 11) exchange RAM chips
1409 12) exchange the motherboard.
1411 To compile this driver as a module, choose M here: the
1412 module will be called apm.
1416 config APM_IGNORE_USER_SUSPEND
1417 bool "Ignore USER SUSPEND"
1419 This option will ignore USER SUSPEND requests. On machines with a
1420 compliant APM BIOS, you want to say N. However, on the NEC Versa M
1421 series notebooks, it is necessary to say Y because of a BIOS bug.
1423 config APM_DO_ENABLE
1424 bool "Enable PM at boot time"
1426 Enable APM features at boot time. From page 36 of the APM BIOS
1427 specification: "When disabled, the APM BIOS does not automatically
1428 power manage devices, enter the Standby State, enter the Suspend
1429 State, or take power saving steps in response to CPU Idle calls."
1430 This driver will make CPU Idle calls when Linux is idle (unless this
1431 feature is turned off -- see "Do CPU IDLE calls", below). This
1432 should always save battery power, but more complicated APM features
1433 will be dependent on your BIOS implementation. You may need to turn
1434 this option off if your computer hangs at boot time when using APM
1435 support, or if it beeps continuously instead of suspending. Turn
1436 this off if you have a NEC UltraLite Versa 33/C or a Toshiba
1437 T400CDT. This is off by default since most machines do fine without
1441 bool "Make CPU Idle calls when idle"
1443 Enable calls to APM CPU Idle/CPU Busy inside the kernel's idle loop.
1444 On some machines, this can activate improved power savings, such as
1445 a slowed CPU clock rate, when the machine is idle. These idle calls
1446 are made after the idle loop has run for some length of time (e.g.,
1447 333 mS). On some machines, this will cause a hang at boot time or
1448 whenever the CPU becomes idle. (On machines with more than one CPU,
1449 this option does nothing.)
1451 config APM_DISPLAY_BLANK
1452 bool "Enable console blanking using APM"
1454 Enable console blanking using the APM. Some laptops can use this to
1455 turn off the LCD backlight when the screen blanker of the Linux
1456 virtual console blanks the screen. Note that this is only used by
1457 the virtual console screen blanker, and won't turn off the backlight
1458 when using the X Window system. This also doesn't have anything to
1459 do with your VESA-compliant power-saving monitor. Further, this
1460 option doesn't work for all laptops -- it might not turn off your
1461 backlight at all, or it might print a lot of errors to the console,
1462 especially if you are using gpm.
1464 config APM_ALLOW_INTS
1465 bool "Allow interrupts during APM BIOS calls"
1467 Normally we disable external interrupts while we are making calls to
1468 the APM BIOS as a measure to lessen the effects of a badly behaving
1469 BIOS implementation. The BIOS should reenable interrupts if it
1470 needs to. Unfortunately, some BIOSes do not -- especially those in
1471 many of the newer IBM Thinkpads. If you experience hangs when you
1472 suspend, try setting this to Y. Otherwise, say N.
1474 config APM_REAL_MODE_POWER_OFF
1475 bool "Use real mode APM BIOS call to power off"
1477 Use real mode APM BIOS calls to switch off the computer. This is
1478 a work-around for a number of buggy BIOSes. Switch this option on if
1479 your computer crashes instead of powering off properly.
1483 source "arch/x86/kernel/cpu/cpufreq/Kconfig"
1485 source "drivers/cpuidle/Kconfig"
1490 menu "Bus options (PCI etc.)"
1493 bool "PCI support" if !X86_VISWS && !X86_VSMP
1494 depends on !X86_VOYAGER
1496 select ARCH_SUPPORTS_MSI if (X86_LOCAL_APIC && X86_IO_APIC)
1498 Find out whether you have a PCI motherboard. PCI is the name of a
1499 bus system, i.e. the way the CPU talks to the other stuff inside
1500 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
1501 VESA. If you have PCI, say Y, otherwise N.
1504 prompt "PCI access mode"
1505 depends on X86_32 && PCI && !X86_VISWS
1508 On PCI systems, the BIOS can be used to detect the PCI devices and
1509 determine their configuration. However, some old PCI motherboards
1510 have BIOS bugs and may crash if this is done. Also, some embedded
1511 PCI-based systems don't have any BIOS at all. Linux can also try to
1512 detect the PCI hardware directly without using the BIOS.
1514 With this option, you can specify how Linux should detect the
1515 PCI devices. If you choose "BIOS", the BIOS will be used,
1516 if you choose "Direct", the BIOS won't be used, and if you
1517 choose "MMConfig", then PCI Express MMCONFIG will be used.
1518 If you choose "Any", the kernel will try MMCONFIG, then the
1519 direct access method and falls back to the BIOS if that doesn't
1520 work. If unsure, go with the default, which is "Any".
1525 config PCI_GOMMCONFIG
1542 depends on X86_32 && !X86_VISWS && PCI && (PCI_GOBIOS || PCI_GOANY)
1544 # x86-64 doesn't support PCI BIOS access from long mode so always go direct.
1547 depends on PCI && (X86_64 || (PCI_GODIRECT || PCI_GOANY || PCI_GOOLPC) || X86_VISWS)
1551 depends on X86_32 && PCI && ACPI && (PCI_GOMMCONFIG || PCI_GOANY)
1555 depends on PCI && OLPC && (PCI_GOOLPC || PCI_GOANY)
1562 bool "Support mmconfig PCI config space access"
1563 depends on X86_64 && PCI && ACPI
1566 bool "Support for DMA Remapping Devices (EXPERIMENTAL)"
1567 depends on X86_64 && PCI_MSI && ACPI && EXPERIMENTAL
1569 DMA remapping (DMAR) devices support enables independent address
1570 translations for Direct Memory Access (DMA) from devices.
1571 These DMA remapping devices are reported via ACPI tables
1572 and include PCI device scope covered by these DMA
1577 prompt "Support for Graphics workaround"
1580 Current Graphics drivers tend to use physical address
1581 for DMA and avoid using DMA APIs. Setting this config
1582 option permits the IOMMU driver to set a unity map for
1583 all the OS-visible memory. Hence the driver can continue
1584 to use physical addresses for DMA.
1586 config DMAR_FLOPPY_WA
1590 Floppy disk drivers are know to bypass DMA API calls
1591 thereby failing to work when IOMMU is enabled. This
1592 workaround will setup a 1:1 mapping for the first
1593 16M to make floppy (an ISA device) work.
1595 source "drivers/pci/pcie/Kconfig"
1597 source "drivers/pci/Kconfig"
1599 # x86_64 have no ISA slots, but do have ISA-style DMA.
1607 depends on !(X86_VOYAGER || X86_VISWS)
1609 Find out whether you have ISA slots on your motherboard. ISA is the
1610 name of a bus system, i.e. the way the CPU talks to the other stuff
1611 inside your box. Other bus systems are PCI, EISA, MicroChannel
1612 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
1613 newer boards don't support it. If you have ISA, say Y, otherwise N.
1619 The Extended Industry Standard Architecture (EISA) bus was
1620 developed as an open alternative to the IBM MicroChannel bus.
1622 The EISA bus provided some of the features of the IBM MicroChannel
1623 bus while maintaining backward compatibility with cards made for
1624 the older ISA bus. The EISA bus saw limited use between 1988 and
1625 1995 when it was made obsolete by the PCI bus.
1627 Say Y here if you are building a kernel for an EISA-based machine.
1631 source "drivers/eisa/Kconfig"
1634 bool "MCA support" if !(X86_VISWS || X86_VOYAGER)
1635 default y if X86_VOYAGER
1637 MicroChannel Architecture is found in some IBM PS/2 machines and
1638 laptops. It is a bus system similar to PCI or ISA. See
1639 <file:Documentation/mca.txt> (and especially the web page given
1640 there) before attempting to build an MCA bus kernel.
1642 source "drivers/mca/Kconfig"
1645 tristate "NatSemi SCx200 support"
1646 depends on !X86_VOYAGER
1648 This provides basic support for National Semiconductor's
1649 (now AMD's) Geode processors. The driver probes for the
1650 PCI-IDs of several on-chip devices, so its a good dependency
1651 for other scx200_* drivers.
1653 If compiled as a module, the driver is named scx200.
1655 config SCx200HR_TIMER
1656 tristate "NatSemi SCx200 27MHz High-Resolution Timer Support"
1657 depends on SCx200 && GENERIC_TIME
1660 This driver provides a clocksource built upon the on-chip
1661 27MHz high-resolution timer. Its also a workaround for
1662 NSC Geode SC-1100's buggy TSC, which loses time when the
1663 processor goes idle (as is done by the scheduler). The
1664 other workaround is idle=poll boot option.
1666 config GEODE_MFGPT_TIMER
1668 prompt "Geode Multi-Function General Purpose Timer (MFGPT) events"
1669 depends on MGEODE_LX && GENERIC_TIME && GENERIC_CLOCKEVENTS
1671 This driver provides a clock event source based on the MFGPT
1672 timer(s) in the CS5535 and CS5536 companion chip for the geode.
1673 MFGPTs have a better resolution and max interval than the
1674 generic PIT, and are suitable for use as high-res timers.
1677 bool "One Laptop Per Child support"
1680 Add support for detecting the unique features of the OLPC
1687 depends on AGP_AMD64 || (X86_64 && (GART_IOMMU || (PCI && NUMA)))
1689 source "drivers/pcmcia/Kconfig"
1691 source "drivers/pci/hotplug/Kconfig"
1696 menu "Executable file formats / Emulations"
1698 source "fs/Kconfig.binfmt"
1700 config IA32_EMULATION
1701 bool "IA32 Emulation"
1703 select COMPAT_BINFMT_ELF
1705 Include code to run 32-bit programs under a 64-bit kernel. You should
1706 likely turn this on, unless you're 100% sure that you don't have any
1707 32-bit programs left.
1710 tristate "IA32 a.out support"
1711 depends on IA32_EMULATION && ARCH_SUPPORTS_AOUT
1713 Support old a.out binaries in the 32bit emulation.
1717 depends on IA32_EMULATION
1719 config COMPAT_FOR_U64_ALIGNMENT
1723 config SYSVIPC_COMPAT
1725 depends on X86_64 && COMPAT && SYSVIPC
1730 source "net/Kconfig"
1732 source "drivers/Kconfig"
1734 source "drivers/firmware/Kconfig"
1738 source "arch/x86/Kconfig.debug"
1740 source "security/Kconfig"
1742 source "crypto/Kconfig"
1744 source "arch/x86/kvm/Kconfig"
1746 source "lib/Kconfig"
projects / linux-2.6-omap-h63xx.git / blob