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
24 select HAVE_KRETPROBES
25 select HAVE_KVM if ((X86_32 && !X86_VOYAGER && !X86_VISWS && !X86_NUMAQ) || X86_64)
26 select HAVE_ARCH_KGDB if !X86_VOYAGER
29 config GENERIC_LOCKBREAK
35 config GENERIC_CMOS_UPDATE
38 config CLOCKSOURCE_WATCHDOG
41 config GENERIC_CLOCKEVENTS
44 config GENERIC_CLOCKEVENTS_BROADCAST
46 depends on X86_64 || (X86_32 && X86_LOCAL_APIC)
48 config LOCKDEP_SUPPORT
51 config STACKTRACE_SUPPORT
54 config HAVE_LATENCYTOP_SUPPORT
57 config FAST_CMPXCHG_LOCAL
70 config GENERIC_ISA_DMA
80 config GENERIC_HWEIGHT
86 config ARCH_MAY_HAVE_PC_FDC
92 config RWSEM_GENERIC_SPINLOCK
95 config RWSEM_XCHGADD_ALGORITHM
98 config ARCH_HAS_ILOG2_U32
101 config ARCH_HAS_ILOG2_U64
104 config ARCH_HAS_CPU_IDLE_WAIT
107 config GENERIC_CALIBRATE_DELAY
110 config GENERIC_TIME_VSYSCALL
114 config ARCH_HAS_CPU_RELAX
117 config ARCH_HAS_CACHE_LINE_SIZE
120 config HAVE_SETUP_PER_CPU_AREA
121 def_bool X86_64 || (X86_SMP && !X86_VOYAGER)
123 config HAVE_CPUMASK_OF_CPU_MAP
126 config ARCH_HIBERNATION_POSSIBLE
128 depends on !SMP || !X86_VOYAGER
130 config ARCH_SUSPEND_POSSIBLE
132 depends on !X86_VOYAGER
138 config ARCH_POPULATES_NODE_MAP
145 config ARCH_SUPPORTS_AOUT
148 config ARCH_SUPPORTS_OPTIMIZED_INLINING
151 # Use the generic interrupt handling code in kernel/irq/:
152 config GENERIC_HARDIRQS
156 config GENERIC_IRQ_PROBE
160 config GENERIC_PENDING_IRQ
162 depends on GENERIC_HARDIRQS && SMP
167 depends on SMP && ((X86_32 && !X86_VOYAGER) || X86_64)
172 depends on X86_32 && SMP
176 depends on X86_64 && SMP
181 depends on (X86_32 && !(X86_VISWS || X86_VOYAGER)) || X86_64
184 config X86_BIOS_REBOOT
186 depends on X86_32 && !(X86_VISWS || X86_VOYAGER)
189 config X86_TRAMPOLINE
191 depends on X86_SMP || (X86_VOYAGER && SMP) || (64BIT && ACPI_SLEEP)
196 source "init/Kconfig"
198 menu "Processor type and features"
200 source "kernel/time/Kconfig"
203 bool "Symmetric multi-processing support"
205 This enables support for systems with more than one CPU. If you have
206 a system with only one CPU, like most personal computers, say N. If
207 you have a system with more than one CPU, say Y.
209 If you say N here, the kernel will run on single and multiprocessor
210 machines, but will use only one CPU of a multiprocessor machine. If
211 you say Y here, the kernel will run on many, but not all,
212 singleprocessor machines. On a singleprocessor machine, the kernel
213 will run faster if you say N here.
215 Note that if you say Y here and choose architecture "586" or
216 "Pentium" under "Processor family", the kernel will not work on 486
217 architectures. Similarly, multiprocessor kernels for the "PPro"
218 architecture may not work on all Pentium based boards.
220 People using multiprocessor machines who say Y here should also say
221 Y to "Enhanced Real Time Clock Support", below. The "Advanced Power
222 Management" code will be disabled if you say Y here.
224 See also <file:Documentation/i386/IO-APIC.txt>,
225 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
226 <http://www.tldp.org/docs.html#howto>.
228 If you don't know what to do here, say N.
231 prompt "Subarchitecture Type"
237 Choose this option if your computer is a standard PC or compatible.
243 Select this for an AMD Elan processor.
245 Do not use this option for K6/Athlon/Opteron processors!
247 If unsure, choose "PC-compatible" instead.
251 depends on X86_32 && (SMP || BROKEN)
253 Voyager is an MCA-based 32-way capable SMP architecture proprietary
254 to NCR Corp. Machine classes 345x/35xx/4100/51xx are Voyager-based.
258 If you do not specifically know you have a Voyager based machine,
259 say N here, otherwise the kernel you build will not be bootable.
262 bool "NUMAQ (IBM/Sequent)"
263 depends on SMP && X86_32
266 This option is used for getting Linux to run on a (IBM/Sequent) NUMA
267 multiquad box. This changes the way that processors are bootstrapped,
268 and uses Clustered Logical APIC addressing mode instead of Flat Logical.
269 You will need a new lynxer.elf file to flash your firmware with - send
270 email to <Martin.Bligh@us.ibm.com>.
273 bool "Summit/EXA (IBM x440)"
274 depends on X86_32 && SMP
276 This option is needed for IBM systems that use the Summit/EXA chipset.
277 In particular, it is needed for the x440.
279 If you don't have one of these computers, you should say N here.
280 If you want to build a NUMA kernel, you must select ACPI.
283 bool "Support for other sub-arch SMP systems with more than 8 CPUs"
284 depends on X86_32 && SMP
286 This option is needed for the systems that have more than 8 CPUs
287 and if the system is not of any sub-arch type above.
289 If you don't have such a system, you should say N here.
292 bool "SGI 320/540 (Visual Workstation)"
295 The SGI Visual Workstation series is an IA32-based workstation
296 based on SGI systems chips with some legacy PC hardware attached.
298 Say Y here to create a kernel to run on the SGI 320 or 540.
300 A kernel compiled for the Visual Workstation will not run on PCs
301 and vice versa. See <file:Documentation/sgi-visws.txt> for details.
303 config X86_GENERICARCH
304 bool "Generic architecture (Summit, bigsmp, ES7000, default)"
307 This option compiles in the Summit, bigsmp, ES7000, default subarchitectures.
308 It is intended for a generic binary kernel.
309 If you want a NUMA kernel, select ACPI. We need SRAT for NUMA.
312 bool "Support for Unisys ES7000 IA32 series"
313 depends on X86_32 && SMP
315 Support for Unisys ES7000 systems. Say 'Y' here if this kernel is
316 supposed to run on an IA32-based Unisys ES7000 system.
317 Only choose this option if you have such a system, otherwise you
321 bool "RDC R-321x SoC"
324 select X86_REBOOTFIXUPS
329 This option is needed for RDC R-321x system-on-chip, also known
331 If you don't have one of these chips, you should say N here.
334 bool "Support for ScaleMP vSMP"
338 Support for ScaleMP vSMP systems. Say 'Y' here if this kernel is
339 supposed to run on these EM64T-based machines. Only choose this option
340 if you have one of these machines.
344 config SCHED_NO_NO_OMIT_FRAME_POINTER
346 prompt "Single-depth WCHAN output"
349 Calculate simpler /proc/<PID>/wchan values. If this option
350 is disabled then wchan values will recurse back to the
351 caller function. This provides more accurate wchan values,
352 at the expense of slightly more scheduling overhead.
354 If in doubt, say "Y".
356 menuconfig PARAVIRT_GUEST
357 bool "Paravirtualized guest support"
359 Say Y here to get to see options related to running Linux under
360 various hypervisors. This option alone does not add any kernel code.
362 If you say N, all options in this submenu will be skipped and disabled.
366 source "arch/x86/xen/Kconfig"
369 bool "VMI Guest support"
372 depends on !(X86_VISWS || X86_VOYAGER)
374 VMI provides a paravirtualized interface to the VMware ESX server
375 (it could be used by other hypervisors in theory too, but is not
376 at the moment), by linking the kernel to a GPL-ed ROM module
377 provided by the hypervisor.
380 bool "KVM paravirtualized clock"
382 depends on !(X86_VISWS || X86_VOYAGER)
384 Turning on this option will allow you to run a paravirtualized clock
385 when running over the KVM hypervisor. Instead of relying on a PIT
386 (or probably other) emulation by the underlying device model, the host
387 provides the guest with timing infrastructure such as time of day, and
391 bool "KVM Guest support"
393 depends on !(X86_VISWS || X86_VOYAGER)
395 This option enables various optimizations for running under the KVM
398 source "arch/x86/lguest/Kconfig"
401 bool "Enable paravirtualization code"
402 depends on !(X86_VISWS || X86_VOYAGER)
404 This changes the kernel so it can modify itself when it is run
405 under a hypervisor, potentially improving performance significantly
406 over full virtualization. However, when run without a hypervisor
407 the kernel is theoretically slower and slightly larger.
411 config MEMTEST_BOOTPARAM
412 bool "Memtest boot parameter"
416 This option adds a kernel parameter 'memtest', which allows memtest
417 to be disabled at boot. If this option is selected, memtest
418 functionality can be disabled with memtest=0 on the kernel
419 command line. The purpose of this option is to allow a single
420 kernel image to be distributed with memtest built in, but not
423 If you are unsure how to answer this question, answer Y.
425 config MEMTEST_BOOTPARAM_VALUE
426 int "Memtest boot parameter default value (0-4)"
427 depends on MEMTEST_BOOTPARAM
431 This option sets the default value for the kernel parameter
432 'memtest', which allows memtest to be disabled at boot. If this
433 option is set to 0 (zero), the memtest kernel parameter will
434 default to 0, disabling memtest at bootup. If this option is
435 set to 4, the memtest kernel parameter will default to 4,
436 enabling memtest at bootup, and use that as pattern number.
438 If you are unsure how to answer this question, answer 0.
442 depends on X86_32 && ACPI && NUMA && (X86_SUMMIT || X86_GENERICARCH)
445 config HAVE_ARCH_PARSE_SRAT
449 config X86_SUMMIT_NUMA
451 depends on X86_32 && NUMA && (X86_SUMMIT || X86_GENERICARCH)
453 config X86_CYCLONE_TIMER
455 depends on X86_32 && X86_SUMMIT || X86_GENERICARCH
457 config ES7000_CLUSTERED_APIC
459 depends on SMP && X86_ES7000 && MPENTIUMIII
461 source "arch/x86/Kconfig.cpu"
465 prompt "HPET Timer Support" if X86_32
467 Use the IA-PC HPET (High Precision Event Timer) to manage
468 time in preference to the PIT and RTC, if a HPET is
470 HPET is the next generation timer replacing legacy 8254s.
471 The HPET provides a stable time base on SMP
472 systems, unlike the TSC, but it is more expensive to access,
473 as it is off-chip. You can find the HPET spec at
474 <http://www.intel.com/hardwaredesign/hpetspec.htm>.
476 You can safely choose Y here. However, HPET will only be
477 activated if the platform and the BIOS support this feature.
478 Otherwise the 8254 will be used for timing services.
480 Choose N to continue using the legacy 8254 timer.
482 config HPET_EMULATE_RTC
484 depends on HPET_TIMER && (RTC=y || RTC=m || RTC_DRV_CMOS=m || RTC_DRV_CMOS=y)
486 # Mark as embedded because too many people got it wrong.
487 # The code disables itself when not needed.
489 bool "GART IOMMU support" if EMBEDDED
493 depends on X86_64 && PCI
495 Support for full DMA access of devices with 32bit memory access only
496 on systems with more than 3GB. This is usually needed for USB,
497 sound, many IDE/SATA chipsets and some other devices.
498 Provides a driver for the AMD Athlon64/Opteron/Turion/Sempron GART
499 based hardware IOMMU and a software bounce buffer based IOMMU used
500 on Intel systems and as fallback.
501 The code is only active when needed (enough memory and limited
502 device) unless CONFIG_IOMMU_DEBUG or iommu=force is specified
506 bool "IBM Calgary IOMMU support"
508 depends on X86_64 && PCI && EXPERIMENTAL
510 Support for hardware IOMMUs in IBM's xSeries x366 and x460
511 systems. Needed to run systems with more than 3GB of memory
512 properly with 32-bit PCI devices that do not support DAC
513 (Double Address Cycle). Calgary also supports bus level
514 isolation, where all DMAs pass through the IOMMU. This
515 prevents them from going anywhere except their intended
516 destination. This catches hard-to-find kernel bugs and
517 mis-behaving drivers and devices that do not use the DMA-API
518 properly to set up their DMA buffers. The IOMMU can be
519 turned off at boot time with the iommu=off parameter.
520 Normally the kernel will make the right choice by itself.
523 config CALGARY_IOMMU_ENABLED_BY_DEFAULT
525 prompt "Should Calgary be enabled by default?"
526 depends on CALGARY_IOMMU
528 Should Calgary be enabled by default? if you choose 'y', Calgary
529 will be used (if it exists). If you choose 'n', Calgary will not be
530 used even if it exists. If you choose 'n' and would like to use
531 Calgary anyway, pass 'iommu=calgary' on the kernel command line.
535 def_bool (CALGARY_IOMMU || GART_IOMMU)
537 # need this always selected by IOMMU for the VIA workaround
541 Support for software bounce buffers used on x86-64 systems
542 which don't have a hardware IOMMU (e.g. the current generation
543 of Intel's x86-64 CPUs). Using this PCI devices which can only
544 access 32-bits of memory can be used on systems with more than
545 3 GB of memory. If unsure, say Y.
549 int "Maximum number of CPUs (2-255)"
552 default "32" if X86_NUMAQ || X86_SUMMIT || X86_BIGSMP || X86_ES7000
555 This allows you to specify the maximum number of CPUs which this
556 kernel will support. The maximum supported value is 255 and the
557 minimum value which makes sense is 2.
559 This is purely to save memory - each supported CPU adds
560 approximately eight kilobytes to the kernel image.
563 bool "SMT (Hyperthreading) scheduler support"
566 SMT scheduler support improves the CPU scheduler's decision making
567 when dealing with Intel Pentium 4 chips with HyperThreading at a
568 cost of slightly increased overhead in some places. If unsure say
573 prompt "Multi-core scheduler support"
576 Multi-core scheduler support improves the CPU scheduler's decision
577 making when dealing with multi-core CPU chips at a cost of slightly
578 increased overhead in some places. If unsure say N here.
580 source "kernel/Kconfig.preempt"
583 bool "Local APIC support on uniprocessors"
584 depends on X86_32 && !SMP && !(X86_VISWS || X86_VOYAGER || X86_GENERICARCH)
586 A local APIC (Advanced Programmable Interrupt Controller) is an
587 integrated interrupt controller in the CPU. If you have a single-CPU
588 system which has a processor with a local APIC, you can say Y here to
589 enable and use it. If you say Y here even though your machine doesn't
590 have a local APIC, then the kernel will still run with no slowdown at
591 all. The local APIC supports CPU-generated self-interrupts (timer,
592 performance counters), and the NMI watchdog which detects hard
596 bool "IO-APIC support on uniprocessors"
597 depends on X86_UP_APIC
599 An IO-APIC (I/O Advanced Programmable Interrupt Controller) is an
600 SMP-capable replacement for PC-style interrupt controllers. Most
601 SMP systems and many recent uniprocessor systems have one.
603 If you have a single-CPU system with an IO-APIC, you can say Y here
604 to use it. If you say Y here even though your machine doesn't have
605 an IO-APIC, then the kernel will still run with no slowdown at all.
607 config X86_LOCAL_APIC
609 depends on X86_64 || (X86_32 && (X86_UP_APIC || ((X86_VISWS || SMP) && !X86_VOYAGER) || X86_GENERICARCH))
613 depends on X86_64 || (X86_32 && (X86_UP_IOAPIC || (SMP && !(X86_VISWS || X86_VOYAGER)) || X86_GENERICARCH))
615 config X86_VISWS_APIC
617 depends on X86_32 && X86_VISWS
620 bool "Machine Check Exception"
621 depends on !X86_VOYAGER
623 Machine Check Exception support allows the processor to notify the
624 kernel if it detects a problem (e.g. overheating, component failure).
625 The action the kernel takes depends on the severity of the problem,
626 ranging from a warning message on the console, to halting the machine.
627 Your processor must be a Pentium or newer to support this - check the
628 flags in /proc/cpuinfo for mce. Note that some older Pentium systems
629 have a design flaw which leads to false MCE events - hence MCE is
630 disabled on all P5 processors, unless explicitly enabled with "mce"
631 as a boot argument. Similarly, if MCE is built in and creates a
632 problem on some new non-standard machine, you can boot with "nomce"
633 to disable it. MCE support simply ignores non-MCE processors like
634 the 386 and 486, so nearly everyone can say Y here.
638 prompt "Intel MCE features"
639 depends on X86_64 && X86_MCE && X86_LOCAL_APIC
641 Additional support for intel specific MCE features such as
646 prompt "AMD MCE features"
647 depends on X86_64 && X86_MCE && X86_LOCAL_APIC
649 Additional support for AMD specific MCE features such as
650 the DRAM Error Threshold.
652 config X86_MCE_NONFATAL
653 tristate "Check for non-fatal errors on AMD Athlon/Duron / Intel Pentium 4"
654 depends on X86_32 && X86_MCE
656 Enabling this feature starts a timer that triggers every 5 seconds which
657 will look at the machine check registers to see if anything happened.
658 Non-fatal problems automatically get corrected (but still logged).
659 Disable this if you don't want to see these messages.
660 Seeing the messages this option prints out may be indicative of dying
661 or out-of-spec (ie, overclocked) hardware.
662 This option only does something on certain CPUs.
663 (AMD Athlon/Duron and Intel Pentium 4)
665 config X86_MCE_P4THERMAL
666 bool "check for P4 thermal throttling interrupt."
667 depends on X86_32 && X86_MCE && (X86_UP_APIC || SMP) && !X86_VISWS
669 Enabling this feature will cause a message to be printed when the P4
670 enters thermal throttling.
673 bool "Enable VM86 support" if EMBEDDED
677 This option is required by programs like DOSEMU to run 16-bit legacy
678 code on X86 processors. It also may be needed by software like
679 XFree86 to initialize some video cards via BIOS. Disabling this
680 option saves about 6k.
683 tristate "Toshiba Laptop support"
686 This adds a driver to safely access the System Management Mode of
687 the CPU on Toshiba portables with a genuine Toshiba BIOS. It does
688 not work on models with a Phoenix BIOS. The System Management Mode
689 is used to set the BIOS and power saving options on Toshiba portables.
691 For information on utilities to make use of this driver see the
692 Toshiba Linux utilities web site at:
693 <http://www.buzzard.org.uk/toshiba/>.
695 Say Y if you intend to run this kernel on a Toshiba portable.
699 tristate "Dell laptop support"
701 This adds a driver to safely access the System Management Mode
702 of the CPU on the Dell Inspiron 8000. The System Management Mode
703 is used to read cpu temperature and cooling fan status and to
704 control the fans on the I8K portables.
706 This driver has been tested only on the Inspiron 8000 but it may
707 also work with other Dell laptops. You can force loading on other
708 models by passing the parameter `force=1' to the module. Use at
711 For information on utilities to make use of this driver see the
712 I8K Linux utilities web site at:
713 <http://people.debian.org/~dz/i8k/>
715 Say Y if you intend to run this kernel on a Dell Inspiron 8000.
718 config X86_REBOOTFIXUPS
720 prompt "Enable X86 board specific fixups for reboot"
721 depends on X86_32 && X86
723 This enables chipset and/or board specific fixups to be done
724 in order to get reboot to work correctly. This is only needed on
725 some combinations of hardware and BIOS. The symptom, for which
726 this config is intended, is when reboot ends with a stalled/hung
729 Currently, the only fixup is for the Geode machines using
730 CS5530A and CS5536 chipsets and the RDC R-321x SoC.
732 Say Y if you want to enable the fixup. Currently, it's safe to
733 enable this option even if you don't need it.
737 tristate "/dev/cpu/microcode - Intel IA32 CPU microcode support"
740 If you say Y here, you will be able to update the microcode on
741 Intel processors in the IA32 family, e.g. Pentium Pro, Pentium II,
742 Pentium III, Pentium 4, Xeon etc. You will obviously need the
743 actual microcode binary data itself which is not shipped with the
746 For latest news and information on obtaining all the required
747 ingredients for this driver, check:
748 <http://www.urbanmyth.org/microcode/>.
750 To compile this driver as a module, choose M here: the
751 module will be called microcode.
753 config MICROCODE_OLD_INTERFACE
758 tristate "/dev/cpu/*/msr - Model-specific register support"
760 This device gives privileged processes access to the x86
761 Model-Specific Registers (MSRs). It is a character device with
762 major 202 and minors 0 to 31 for /dev/cpu/0/msr to /dev/cpu/31/msr.
763 MSR accesses are directed to a specific CPU on multi-processor
767 tristate "/dev/cpu/*/cpuid - CPU information support"
769 This device gives processes access to the x86 CPUID instruction to
770 be executed on a specific processor. It is a character device
771 with major 203 and minors 0 to 31 for /dev/cpu/0/cpuid to
775 prompt "High Memory Support"
776 default HIGHMEM4G if !X86_NUMAQ
777 default HIGHMEM64G if X86_NUMAQ
782 depends on !X86_NUMAQ
784 Linux can use up to 64 Gigabytes of physical memory on x86 systems.
785 However, the address space of 32-bit x86 processors is only 4
786 Gigabytes large. That means that, if you have a large amount of
787 physical memory, not all of it can be "permanently mapped" by the
788 kernel. The physical memory that's not permanently mapped is called
791 If you are compiling a kernel which will never run on a machine with
792 more than 1 Gigabyte total physical RAM, answer "off" here (default
793 choice and suitable for most users). This will result in a "3GB/1GB"
794 split: 3GB are mapped so that each process sees a 3GB virtual memory
795 space and the remaining part of the 4GB virtual memory space is used
796 by the kernel to permanently map as much physical memory as
799 If the machine has between 1 and 4 Gigabytes physical RAM, then
802 If more than 4 Gigabytes is used then answer "64GB" here. This
803 selection turns Intel PAE (Physical Address Extension) mode on.
804 PAE implements 3-level paging on IA32 processors. PAE is fully
805 supported by Linux, PAE mode is implemented on all recent Intel
806 processors (Pentium Pro and better). NOTE: If you say "64GB" here,
807 then the kernel will not boot on CPUs that don't support PAE!
809 The actual amount of total physical memory will either be
810 auto detected or can be forced by using a kernel command line option
811 such as "mem=256M". (Try "man bootparam" or see the documentation of
812 your boot loader (lilo or loadlin) about how to pass options to the
813 kernel at boot time.)
815 If unsure, say "off".
819 depends on !X86_NUMAQ
821 Select this if you have a 32-bit processor and between 1 and 4
822 gigabytes of physical RAM.
826 depends on !M386 && !M486
829 Select this if you have a 32-bit processor and more than 4
830 gigabytes of physical RAM.
835 depends on EXPERIMENTAL
836 prompt "Memory split" if EMBEDDED
840 Select the desired split between kernel and user memory.
842 If the address range available to the kernel is less than the
843 physical memory installed, the remaining memory will be available
844 as "high memory". Accessing high memory is a little more costly
845 than low memory, as it needs to be mapped into the kernel first.
846 Note that increasing the kernel address space limits the range
847 available to user programs, making the address space there
848 tighter. Selecting anything other than the default 3G/1G split
849 will also likely make your kernel incompatible with binary-only
852 If you are not absolutely sure what you are doing, leave this
856 bool "3G/1G user/kernel split"
857 config VMSPLIT_3G_OPT
859 bool "3G/1G user/kernel split (for full 1G low memory)"
861 bool "2G/2G user/kernel split"
862 config VMSPLIT_2G_OPT
864 bool "2G/2G user/kernel split (for full 2G low memory)"
866 bool "1G/3G user/kernel split"
871 default 0xB0000000 if VMSPLIT_3G_OPT
872 default 0x80000000 if VMSPLIT_2G
873 default 0x78000000 if VMSPLIT_2G_OPT
874 default 0x40000000 if VMSPLIT_1G
880 depends on X86_32 && (HIGHMEM64G || HIGHMEM4G)
884 prompt "PAE (Physical Address Extension) Support"
885 depends on X86_32 && !HIGHMEM4G
886 select RESOURCES_64BIT
888 PAE is required for NX support, and furthermore enables
889 larger swapspace support for non-overcommit purposes. It
890 has the cost of more pagetable lookup overhead, and also
891 consumes more pagetable space per process.
893 # Common NUMA Features
895 bool "Numa Memory Allocation and Scheduler Support (EXPERIMENTAL)"
897 depends on X86_64 || (X86_32 && HIGHMEM64G && (X86_NUMAQ || (X86_SUMMIT || X86_GENERICARCH) && ACPI) && EXPERIMENTAL)
899 default y if (X86_NUMAQ || X86_SUMMIT)
901 Enable NUMA (Non Uniform Memory Access) support.
902 The kernel will try to allocate memory used by a CPU on the
903 local memory controller of the CPU and add some more
904 NUMA awareness to the kernel.
906 For i386 this is currently highly experimental and should be only
907 used for kernel development. It might also cause boot failures.
908 For x86_64 this is recommended on all multiprocessor Opteron systems.
909 If the system is EM64T, you should say N unless your system is
912 comment "NUMA (Summit) requires SMP, 64GB highmem support, ACPI"
913 depends on X86_32 && X86_SUMMIT && (!HIGHMEM64G || !ACPI)
917 prompt "Old style AMD Opteron NUMA detection"
918 depends on X86_64 && NUMA && PCI
920 Enable K8 NUMA node topology detection. You should say Y here if
921 you have a multi processor AMD K8 system. This uses an old
922 method to read the NUMA configuration directly from the builtin
923 Northbridge of Opteron. It is recommended to use X86_64_ACPI_NUMA
924 instead, which also takes priority if both are compiled in.
926 config X86_64_ACPI_NUMA
928 prompt "ACPI NUMA detection"
929 depends on X86_64 && NUMA && ACPI && PCI
932 Enable ACPI SRAT based node topology detection.
934 # Some NUMA nodes have memory ranges that span
935 # other nodes. Even though a pfn is valid and
936 # between a node's start and end pfns, it may not
937 # reside on that node. See memmap_init_zone()
939 config NODES_SPAN_OTHER_NODES
941 depends on X86_64_ACPI_NUMA
944 bool "NUMA emulation"
945 depends on X86_64 && NUMA
947 Enable NUMA emulation. A flat machine will be split
948 into virtual nodes when booted with "numa=fake=N", where N is the
949 number of nodes. This is only useful for debugging.
952 int "Max num nodes shift(1-15)"
954 default "6" if X86_64
955 default "4" if X86_NUMAQ
957 depends on NEED_MULTIPLE_NODES
959 config HAVE_ARCH_BOOTMEM_NODE
961 depends on X86_32 && NUMA
963 config ARCH_HAVE_MEMORY_PRESENT
965 depends on X86_32 && DISCONTIGMEM
967 config NEED_NODE_MEMMAP_SIZE
969 depends on X86_32 && (DISCONTIGMEM || SPARSEMEM)
971 config HAVE_ARCH_ALLOC_REMAP
973 depends on X86_32 && NUMA
975 config ARCH_FLATMEM_ENABLE
977 depends on X86_32 && ARCH_SELECT_MEMORY_MODEL && X86_PC && !NUMA
979 config ARCH_DISCONTIGMEM_ENABLE
981 depends on NUMA && X86_32
983 config ARCH_DISCONTIGMEM_DEFAULT
985 depends on NUMA && X86_32
987 config ARCH_SPARSEMEM_DEFAULT
991 config ARCH_SPARSEMEM_ENABLE
993 depends on X86_64 || NUMA || (EXPERIMENTAL && X86_PC)
994 select SPARSEMEM_STATIC if X86_32
995 select SPARSEMEM_VMEMMAP_ENABLE if X86_64
997 config ARCH_SELECT_MEMORY_MODEL
999 depends on ARCH_SPARSEMEM_ENABLE
1001 config ARCH_MEMORY_PROBE
1003 depends on MEMORY_HOTPLUG
1008 bool "Allocate 3rd-level pagetables from highmem"
1009 depends on X86_32 && (HIGHMEM4G || HIGHMEM64G)
1011 The VM uses one page table entry for each page of physical memory.
1012 For systems with a lot of RAM, this can be wasteful of precious
1013 low memory. Setting this option will put user-space page table
1014 entries in high memory.
1016 config MATH_EMULATION
1018 prompt "Math emulation" if X86_32
1020 Linux can emulate a math coprocessor (used for floating point
1021 operations) if you don't have one. 486DX and Pentium processors have
1022 a math coprocessor built in, 486SX and 386 do not, unless you added
1023 a 487DX or 387, respectively. (The messages during boot time can
1024 give you some hints here ["man dmesg"].) Everyone needs either a
1025 coprocessor or this emulation.
1027 If you don't have a math coprocessor, you need to say Y here; if you
1028 say Y here even though you have a coprocessor, the coprocessor will
1029 be used nevertheless. (This behavior can be changed with the kernel
1030 command line option "no387", which comes handy if your coprocessor
1031 is broken. Try "man bootparam" or see the documentation of your boot
1032 loader (lilo or loadlin) about how to pass options to the kernel at
1033 boot time.) This means that it is a good idea to say Y here if you
1034 intend to use this kernel on different machines.
1036 More information about the internals of the Linux math coprocessor
1037 emulation can be found in <file:arch/x86/math-emu/README>.
1039 If you are not sure, say Y; apart from resulting in a 66 KB bigger
1040 kernel, it won't hurt.
1043 bool "MTRR (Memory Type Range Register) support"
1045 On Intel P6 family processors (Pentium Pro, Pentium II and later)
1046 the Memory Type Range Registers (MTRRs) may be used to control
1047 processor access to memory ranges. This is most useful if you have
1048 a video (VGA) card on a PCI or AGP bus. Enabling write-combining
1049 allows bus write transfers to be combined into a larger transfer
1050 before bursting over the PCI/AGP bus. This can increase performance
1051 of image write operations 2.5 times or more. Saying Y here creates a
1052 /proc/mtrr file which may be used to manipulate your processor's
1053 MTRRs. Typically the X server should use this.
1055 This code has a reasonably generic interface so that similar
1056 control registers on other processors can be easily supported
1059 The Cyrix 6x86, 6x86MX and M II processors have Address Range
1060 Registers (ARRs) which provide a similar functionality to MTRRs. For
1061 these, the ARRs are used to emulate the MTRRs.
1062 The AMD K6-2 (stepping 8 and above) and K6-3 processors have two
1063 MTRRs. The Centaur C6 (WinChip) has 8 MCRs, allowing
1064 write-combining. All of these processors are supported by this code
1065 and it makes sense to say Y here if you have one of them.
1067 Saying Y here also fixes a problem with buggy SMP BIOSes which only
1068 set the MTRRs for the boot CPU and not for the secondary CPUs. This
1069 can lead to all sorts of problems, so it's good to say Y here.
1071 You can safely say Y even if your machine doesn't have MTRRs, you'll
1072 just add about 9 KB to your kernel.
1074 See <file:Documentation/mtrr.txt> for more information.
1078 prompt "x86 PAT support"
1081 Use PAT attributes to setup page level cache control.
1083 PATs are the modern equivalents of MTRRs and are much more
1084 flexible than MTRRs.
1086 Say N here if you see bootup problems (boot crash, boot hang,
1087 spontaneous reboots) or a non-working video driver.
1093 prompt "EFI runtime service support"
1096 This enables the kernel to use EFI runtime services that are
1097 available (such as the EFI variable services).
1099 This option is only useful on systems that have EFI firmware.
1100 In addition, you should use the latest ELILO loader available
1101 at <http://elilo.sourceforge.net> in order to take advantage
1102 of EFI runtime services. However, even with this option, the
1103 resultant kernel should continue to boot on existing non-EFI
1108 prompt "Enable kernel irq balancing"
1109 depends on X86_32 && SMP && X86_IO_APIC
1111 The default yes will allow the kernel to do irq load balancing.
1112 Saying no will keep the kernel from doing irq load balancing.
1116 prompt "Enable seccomp to safely compute untrusted bytecode"
1119 This kernel feature is useful for number crunching applications
1120 that may need to compute untrusted bytecode during their
1121 execution. By using pipes or other transports made available to
1122 the process as file descriptors supporting the read/write
1123 syscalls, it's possible to isolate those applications in
1124 their own address space using seccomp. Once seccomp is
1125 enabled via /proc/<pid>/seccomp, it cannot be disabled
1126 and the task is only allowed to execute a few safe syscalls
1127 defined by each seccomp mode.
1129 If unsure, say Y. Only embedded should say N here.
1131 config CC_STACKPROTECTOR
1132 bool "Enable -fstack-protector buffer overflow detection (EXPERIMENTAL)"
1133 depends on X86_64 && EXPERIMENTAL && BROKEN
1135 This option turns on the -fstack-protector GCC feature. This
1136 feature puts, at the beginning of critical functions, a canary
1137 value on the stack just before the return address, and validates
1138 the value just before actually returning. Stack based buffer
1139 overflows (that need to overwrite this return address) now also
1140 overwrite the canary, which gets detected and the attack is then
1141 neutralized via a kernel panic.
1143 This feature requires gcc version 4.2 or above, or a distribution
1144 gcc with the feature backported. Older versions are automatically
1145 detected and for those versions, this configuration option is ignored.
1147 config CC_STACKPROTECTOR_ALL
1148 bool "Use stack-protector for all functions"
1149 depends on CC_STACKPROTECTOR
1151 Normally, GCC only inserts the canary value protection for
1152 functions that use large-ish on-stack buffers. By enabling
1153 this option, GCC will be asked to do this for ALL functions.
1155 source kernel/Kconfig.hz
1158 bool "kexec system call"
1159 depends on X86_64 || X86_BIOS_REBOOT
1161 kexec is a system call that implements the ability to shutdown your
1162 current kernel, and to start another kernel. It is like a reboot
1163 but it is independent of the system firmware. And like a reboot
1164 you can start any kernel with it, not just Linux.
1166 The name comes from the similarity to the exec system call.
1168 It is an ongoing process to be certain the hardware in a machine
1169 is properly shutdown, so do not be surprised if this code does not
1170 initially work for you. It may help to enable device hotplugging
1171 support. As of this writing the exact hardware interface is
1172 strongly in flux, so no good recommendation can be made.
1175 bool "kernel crash dumps (EXPERIMENTAL)"
1176 depends on EXPERIMENTAL
1177 depends on X86_64 || (X86_32 && HIGHMEM)
1179 Generate crash dump after being started by kexec.
1180 This should be normally only set in special crash dump kernels
1181 which are loaded in the main kernel with kexec-tools into
1182 a specially reserved region and then later executed after
1183 a crash by kdump/kexec. The crash dump kernel must be compiled
1184 to a memory address not used by the main kernel or BIOS using
1185 PHYSICAL_START, or it must be built as a relocatable image
1186 (CONFIG_RELOCATABLE=y).
1187 For more details see Documentation/kdump/kdump.txt
1189 config PHYSICAL_START
1190 hex "Physical address where the kernel is loaded" if (EMBEDDED || CRASH_DUMP)
1191 default "0x1000000" if X86_NUMAQ
1192 default "0x200000" if X86_64
1195 This gives the physical address where the kernel is loaded.
1197 If kernel is a not relocatable (CONFIG_RELOCATABLE=n) then
1198 bzImage will decompress itself to above physical address and
1199 run from there. Otherwise, bzImage will run from the address where
1200 it has been loaded by the boot loader and will ignore above physical
1203 In normal kdump cases one does not have to set/change this option
1204 as now bzImage can be compiled as a completely relocatable image
1205 (CONFIG_RELOCATABLE=y) and be used to load and run from a different
1206 address. This option is mainly useful for the folks who don't want
1207 to use a bzImage for capturing the crash dump and want to use a
1208 vmlinux instead. vmlinux is not relocatable hence a kernel needs
1209 to be specifically compiled to run from a specific memory area
1210 (normally a reserved region) and this option comes handy.
1212 So if you are using bzImage for capturing the crash dump, leave
1213 the value here unchanged to 0x100000 and set CONFIG_RELOCATABLE=y.
1214 Otherwise if you plan to use vmlinux for capturing the crash dump
1215 change this value to start of the reserved region (Typically 16MB
1216 0x1000000). In other words, it can be set based on the "X" value as
1217 specified in the "crashkernel=YM@XM" command line boot parameter
1218 passed to the panic-ed kernel. Typically this parameter is set as
1219 crashkernel=64M@16M. Please take a look at
1220 Documentation/kdump/kdump.txt for more details about crash dumps.
1222 Usage of bzImage for capturing the crash dump is recommended as
1223 one does not have to build two kernels. Same kernel can be used
1224 as production kernel and capture kernel. Above option should have
1225 gone away after relocatable bzImage support is introduced. But it
1226 is present because there are users out there who continue to use
1227 vmlinux for dump capture. This option should go away down the
1230 Don't change this unless you know what you are doing.
1233 bool "Build a relocatable kernel (EXPERIMENTAL)"
1234 depends on EXPERIMENTAL
1236 This builds a kernel image that retains relocation information
1237 so it can be loaded someplace besides the default 1MB.
1238 The relocations tend to make the kernel binary about 10% larger,
1239 but are discarded at runtime.
1241 One use is for the kexec on panic case where the recovery kernel
1242 must live at a different physical address than the primary
1245 Note: If CONFIG_RELOCATABLE=y, then the kernel runs from the address
1246 it has been loaded at and the compile time physical address
1247 (CONFIG_PHYSICAL_START) is ignored.
1249 config PHYSICAL_ALIGN
1251 prompt "Alignment value to which kernel should be aligned" if X86_32
1252 default "0x100000" if X86_32
1253 default "0x200000" if X86_64
1254 range 0x2000 0x400000
1256 This value puts the alignment restrictions on physical address
1257 where kernel is loaded and run from. Kernel is compiled for an
1258 address which meets above alignment restriction.
1260 If bootloader loads the kernel at a non-aligned address and
1261 CONFIG_RELOCATABLE is set, kernel will move itself to nearest
1262 address aligned to above value and run from there.
1264 If bootloader loads the kernel at a non-aligned address and
1265 CONFIG_RELOCATABLE is not set, kernel will ignore the run time
1266 load address and decompress itself to the address it has been
1267 compiled for and run from there. The address for which kernel is
1268 compiled already meets above alignment restrictions. Hence the
1269 end result is that kernel runs from a physical address meeting
1270 above alignment restrictions.
1272 Don't change this unless you know what you are doing.
1275 bool "Support for suspend on SMP and hot-pluggable CPUs (EXPERIMENTAL)"
1276 depends on SMP && HOTPLUG && EXPERIMENTAL && !X86_VOYAGER
1278 Say Y here to experiment with turning CPUs off and on, and to
1279 enable suspend on SMP systems. CPUs can be controlled through
1280 /sys/devices/system/cpu.
1281 Say N if you want to disable CPU hotplug and don't need to
1286 prompt "Compat VDSO support"
1287 depends on X86_32 || IA32_EMULATION
1289 Map the 32-bit VDSO to the predictable old-style address too.
1291 Say N here if you are running a sufficiently recent glibc
1292 version (2.3.3 or later), to remove the high-mapped
1293 VDSO mapping and to exclusively use the randomized VDSO.
1299 config ARCH_ENABLE_MEMORY_HOTPLUG
1301 depends on X86_64 || (X86_32 && HIGHMEM)
1303 config HAVE_ARCH_EARLY_PFN_TO_NID
1307 menu "Power management options"
1308 depends on !X86_VOYAGER
1310 config ARCH_HIBERNATION_HEADER
1312 depends on X86_64 && HIBERNATION
1314 source "kernel/power/Kconfig"
1316 source "drivers/acpi/Kconfig"
1321 depends on APM || APM_MODULE
1324 tristate "APM (Advanced Power Management) BIOS support"
1325 depends on X86_32 && PM_SLEEP && !X86_VISWS
1327 APM is a BIOS specification for saving power using several different
1328 techniques. This is mostly useful for battery powered laptops with
1329 APM compliant BIOSes. If you say Y here, the system time will be
1330 reset after a RESUME operation, the /proc/apm device will provide
1331 battery status information, and user-space programs will receive
1332 notification of APM "events" (e.g. battery status change).
1334 If you select "Y" here, you can disable actual use of the APM
1335 BIOS by passing the "apm=off" option to the kernel at boot time.
1337 Note that the APM support is almost completely disabled for
1338 machines with more than one CPU.
1340 In order to use APM, you will need supporting software. For location
1341 and more information, read <file:Documentation/power/pm.txt> and the
1342 Battery Powered Linux mini-HOWTO, available from
1343 <http://www.tldp.org/docs.html#howto>.
1345 This driver does not spin down disk drives (see the hdparm(8)
1346 manpage ("man 8 hdparm") for that), and it doesn't turn off
1347 VESA-compliant "green" monitors.
1349 This driver does not support the TI 4000M TravelMate and the ACER
1350 486/DX4/75 because they don't have compliant BIOSes. Many "green"
1351 desktop machines also don't have compliant BIOSes, and this driver
1352 may cause those machines to panic during the boot phase.
1354 Generally, if you don't have a battery in your machine, there isn't
1355 much point in using this driver and you should say N. If you get
1356 random kernel OOPSes or reboots that don't seem to be related to
1357 anything, try disabling/enabling this option (or disabling/enabling
1360 Some other things you should try when experiencing seemingly random,
1363 1) make sure that you have enough swap space and that it is
1365 2) pass the "no-hlt" option to the kernel
1366 3) switch on floating point emulation in the kernel and pass
1367 the "no387" option to the kernel
1368 4) pass the "floppy=nodma" option to the kernel
1369 5) pass the "mem=4M" option to the kernel (thereby disabling
1370 all but the first 4 MB of RAM)
1371 6) make sure that the CPU is not over clocked.
1372 7) read the sig11 FAQ at <http://www.bitwizard.nl/sig11/>
1373 8) disable the cache from your BIOS settings
1374 9) install a fan for the video card or exchange video RAM
1375 10) install a better fan for the CPU
1376 11) exchange RAM chips
1377 12) exchange the motherboard.
1379 To compile this driver as a module, choose M here: the
1380 module will be called apm.
1384 config APM_IGNORE_USER_SUSPEND
1385 bool "Ignore USER SUSPEND"
1387 This option will ignore USER SUSPEND requests. On machines with a
1388 compliant APM BIOS, you want to say N. However, on the NEC Versa M
1389 series notebooks, it is necessary to say Y because of a BIOS bug.
1391 config APM_DO_ENABLE
1392 bool "Enable PM at boot time"
1394 Enable APM features at boot time. From page 36 of the APM BIOS
1395 specification: "When disabled, the APM BIOS does not automatically
1396 power manage devices, enter the Standby State, enter the Suspend
1397 State, or take power saving steps in response to CPU Idle calls."
1398 This driver will make CPU Idle calls when Linux is idle (unless this
1399 feature is turned off -- see "Do CPU IDLE calls", below). This
1400 should always save battery power, but more complicated APM features
1401 will be dependent on your BIOS implementation. You may need to turn
1402 this option off if your computer hangs at boot time when using APM
1403 support, or if it beeps continuously instead of suspending. Turn
1404 this off if you have a NEC UltraLite Versa 33/C or a Toshiba
1405 T400CDT. This is off by default since most machines do fine without
1409 bool "Make CPU Idle calls when idle"
1411 Enable calls to APM CPU Idle/CPU Busy inside the kernel's idle loop.
1412 On some machines, this can activate improved power savings, such as
1413 a slowed CPU clock rate, when the machine is idle. These idle calls
1414 are made after the idle loop has run for some length of time (e.g.,
1415 333 mS). On some machines, this will cause a hang at boot time or
1416 whenever the CPU becomes idle. (On machines with more than one CPU,
1417 this option does nothing.)
1419 config APM_DISPLAY_BLANK
1420 bool "Enable console blanking using APM"
1422 Enable console blanking using the APM. Some laptops can use this to
1423 turn off the LCD backlight when the screen blanker of the Linux
1424 virtual console blanks the screen. Note that this is only used by
1425 the virtual console screen blanker, and won't turn off the backlight
1426 when using the X Window system. This also doesn't have anything to
1427 do with your VESA-compliant power-saving monitor. Further, this
1428 option doesn't work for all laptops -- it might not turn off your
1429 backlight at all, or it might print a lot of errors to the console,
1430 especially if you are using gpm.
1432 config APM_ALLOW_INTS
1433 bool "Allow interrupts during APM BIOS calls"
1435 Normally we disable external interrupts while we are making calls to
1436 the APM BIOS as a measure to lessen the effects of a badly behaving
1437 BIOS implementation. The BIOS should reenable interrupts if it
1438 needs to. Unfortunately, some BIOSes do not -- especially those in
1439 many of the newer IBM Thinkpads. If you experience hangs when you
1440 suspend, try setting this to Y. Otherwise, say N.
1442 config APM_REAL_MODE_POWER_OFF
1443 bool "Use real mode APM BIOS call to power off"
1445 Use real mode APM BIOS calls to switch off the computer. This is
1446 a work-around for a number of buggy BIOSes. Switch this option on if
1447 your computer crashes instead of powering off properly.
1451 source "arch/x86/kernel/cpu/cpufreq/Kconfig"
1453 source "drivers/cpuidle/Kconfig"
1458 menu "Bus options (PCI etc.)"
1461 bool "PCI support" if !X86_VISWS && !X86_VSMP
1462 depends on !X86_VOYAGER
1464 select ARCH_SUPPORTS_MSI if (X86_LOCAL_APIC && X86_IO_APIC)
1466 Find out whether you have a PCI motherboard. PCI is the name of a
1467 bus system, i.e. the way the CPU talks to the other stuff inside
1468 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
1469 VESA. If you have PCI, say Y, otherwise N.
1472 prompt "PCI access mode"
1473 depends on X86_32 && PCI && !X86_VISWS
1476 On PCI systems, the BIOS can be used to detect the PCI devices and
1477 determine their configuration. However, some old PCI motherboards
1478 have BIOS bugs and may crash if this is done. Also, some embedded
1479 PCI-based systems don't have any BIOS at all. Linux can also try to
1480 detect the PCI hardware directly without using the BIOS.
1482 With this option, you can specify how Linux should detect the
1483 PCI devices. If you choose "BIOS", the BIOS will be used,
1484 if you choose "Direct", the BIOS won't be used, and if you
1485 choose "MMConfig", then PCI Express MMCONFIG will be used.
1486 If you choose "Any", the kernel will try MMCONFIG, then the
1487 direct access method and falls back to the BIOS if that doesn't
1488 work. If unsure, go with the default, which is "Any".
1493 config PCI_GOMMCONFIG
1506 depends on X86_32 && !X86_VISWS && PCI && (PCI_GOBIOS || PCI_GOANY)
1508 # x86-64 doesn't support PCI BIOS access from long mode so always go direct.
1511 depends on PCI && (X86_64 || (PCI_GODIRECT || PCI_GOANY) || X86_VISWS)
1515 depends on X86_32 && PCI && ACPI && (PCI_GOMMCONFIG || PCI_GOANY)
1522 bool "Support mmconfig PCI config space access"
1523 depends on X86_64 && PCI && ACPI
1526 bool "Support for DMA Remapping Devices (EXPERIMENTAL)"
1527 depends on X86_64 && PCI_MSI && ACPI && EXPERIMENTAL
1529 DMA remapping (DMAR) devices support enables independent address
1530 translations for Direct Memory Access (DMA) from devices.
1531 These DMA remapping devices are reported via ACPI tables
1532 and include PCI device scope covered by these DMA
1537 prompt "Support for Graphics workaround"
1540 Current Graphics drivers tend to use physical address
1541 for DMA and avoid using DMA APIs. Setting this config
1542 option permits the IOMMU driver to set a unity map for
1543 all the OS-visible memory. Hence the driver can continue
1544 to use physical addresses for DMA.
1546 config DMAR_FLOPPY_WA
1550 Floppy disk drivers are know to bypass DMA API calls
1551 thereby failing to work when IOMMU is enabled. This
1552 workaround will setup a 1:1 mapping for the first
1553 16M to make floppy (an ISA device) work.
1555 source "drivers/pci/pcie/Kconfig"
1557 source "drivers/pci/Kconfig"
1559 # x86_64 have no ISA slots, but do have ISA-style DMA.
1567 depends on !(X86_VOYAGER || X86_VISWS)
1569 Find out whether you have ISA slots on your motherboard. ISA is the
1570 name of a bus system, i.e. the way the CPU talks to the other stuff
1571 inside your box. Other bus systems are PCI, EISA, MicroChannel
1572 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
1573 newer boards don't support it. If you have ISA, say Y, otherwise N.
1579 The Extended Industry Standard Architecture (EISA) bus was
1580 developed as an open alternative to the IBM MicroChannel bus.
1582 The EISA bus provided some of the features of the IBM MicroChannel
1583 bus while maintaining backward compatibility with cards made for
1584 the older ISA bus. The EISA bus saw limited use between 1988 and
1585 1995 when it was made obsolete by the PCI bus.
1587 Say Y here if you are building a kernel for an EISA-based machine.
1591 source "drivers/eisa/Kconfig"
1594 bool "MCA support" if !(X86_VISWS || X86_VOYAGER)
1595 default y if X86_VOYAGER
1597 MicroChannel Architecture is found in some IBM PS/2 machines and
1598 laptops. It is a bus system similar to PCI or ISA. See
1599 <file:Documentation/mca.txt> (and especially the web page given
1600 there) before attempting to build an MCA bus kernel.
1602 source "drivers/mca/Kconfig"
1605 tristate "NatSemi SCx200 support"
1606 depends on !X86_VOYAGER
1608 This provides basic support for National Semiconductor's
1609 (now AMD's) Geode processors. The driver probes for the
1610 PCI-IDs of several on-chip devices, so its a good dependency
1611 for other scx200_* drivers.
1613 If compiled as a module, the driver is named scx200.
1615 config SCx200HR_TIMER
1616 tristate "NatSemi SCx200 27MHz High-Resolution Timer Support"
1617 depends on SCx200 && GENERIC_TIME
1620 This driver provides a clocksource built upon the on-chip
1621 27MHz high-resolution timer. Its also a workaround for
1622 NSC Geode SC-1100's buggy TSC, which loses time when the
1623 processor goes idle (as is done by the scheduler). The
1624 other workaround is idle=poll boot option.
1626 config GEODE_MFGPT_TIMER
1628 prompt "Geode Multi-Function General Purpose Timer (MFGPT) events"
1629 depends on MGEODE_LX && GENERIC_TIME && GENERIC_CLOCKEVENTS
1631 This driver provides a clock event source based on the MFGPT
1632 timer(s) in the CS5535 and CS5536 companion chip for the geode.
1633 MFGPTs have a better resolution and max interval than the
1634 generic PIT, and are suitable for use as high-res timers.
1640 depends on AGP_AMD64 || (X86_64 && (GART_IOMMU || (PCI && NUMA)))
1642 source "drivers/pcmcia/Kconfig"
1644 source "drivers/pci/hotplug/Kconfig"
1649 menu "Executable file formats / Emulations"
1651 source "fs/Kconfig.binfmt"
1653 config IA32_EMULATION
1654 bool "IA32 Emulation"
1656 select COMPAT_BINFMT_ELF
1658 Include code to run 32-bit programs under a 64-bit kernel. You should
1659 likely turn this on, unless you're 100% sure that you don't have any
1660 32-bit programs left.
1663 tristate "IA32 a.out support"
1664 depends on IA32_EMULATION && ARCH_SUPPORTS_AOUT
1666 Support old a.out binaries in the 32bit emulation.
1670 depends on IA32_EMULATION
1672 config COMPAT_FOR_U64_ALIGNMENT
1676 config SYSVIPC_COMPAT
1678 depends on X86_64 && COMPAT && SYSVIPC
1683 source "net/Kconfig"
1685 source "drivers/Kconfig"
1687 source "drivers/firmware/Kconfig"
1691 source "arch/x86/Kconfig.debug"
1693 source "security/Kconfig"
1695 source "crypto/Kconfig"
1697 source "arch/x86/kvm/Kconfig"
1699 source "lib/Kconfig"
git.openpandora.org / pandora-kernel.git / blob