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)
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 HAVE_SETUP_PER_CPU_AREA
118 def_bool X86_64 || (X86_SMP && !X86_VOYAGER)
120 config HAVE_CPUMASK_OF_CPU_MAP
123 config ARCH_HIBERNATION_POSSIBLE
125 depends on !SMP || !X86_VOYAGER
127 config ARCH_SUSPEND_POSSIBLE
129 depends on !X86_VOYAGER
135 config ARCH_POPULATES_NODE_MAP
142 config ARCH_SUPPORTS_AOUT
145 # Use the generic interrupt handling code in kernel/irq/:
146 config GENERIC_HARDIRQS
150 config GENERIC_IRQ_PROBE
154 config GENERIC_PENDING_IRQ
156 depends on GENERIC_HARDIRQS && SMP
161 depends on SMP && ((X86_32 && !X86_VOYAGER) || X86_64)
166 depends on X86_32 && SMP
170 depends on X86_64 && SMP
175 depends on (X86_32 && !(X86_VISWS || X86_VOYAGER)) || X86_64
178 config X86_BIOS_REBOOT
180 depends on X86_32 && !(X86_VISWS || X86_VOYAGER)
183 config X86_TRAMPOLINE
185 depends on X86_SMP || (X86_VOYAGER && SMP) || (64BIT && ACPI_SLEEP)
190 source "init/Kconfig"
192 menu "Processor type and features"
194 source "kernel/time/Kconfig"
197 bool "Symmetric multi-processing support"
199 This enables support for systems with more than one CPU. If you have
200 a system with only one CPU, like most personal computers, say N. If
201 you have a system with more than one CPU, say Y.
203 If you say N here, the kernel will run on single and multiprocessor
204 machines, but will use only one CPU of a multiprocessor machine. If
205 you say Y here, the kernel will run on many, but not all,
206 singleprocessor machines. On a singleprocessor machine, the kernel
207 will run faster if you say N here.
209 Note that if you say Y here and choose architecture "586" or
210 "Pentium" under "Processor family", the kernel will not work on 486
211 architectures. Similarly, multiprocessor kernels for the "PPro"
212 architecture may not work on all Pentium based boards.
214 People using multiprocessor machines who say Y here should also say
215 Y to "Enhanced Real Time Clock Support", below. The "Advanced Power
216 Management" code will be disabled if you say Y here.
218 See also <file:Documentation/i386/IO-APIC.txt>,
219 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
220 <http://www.tldp.org/docs.html#howto>.
222 If you don't know what to do here, say N.
225 prompt "Subarchitecture Type"
231 Choose this option if your computer is a standard PC or compatible.
237 Select this for an AMD Elan processor.
239 Do not use this option for K6/Athlon/Opteron processors!
241 If unsure, choose "PC-compatible" instead.
245 depends on X86_32 && (SMP || BROKEN)
247 Voyager is an MCA-based 32-way capable SMP architecture proprietary
248 to NCR Corp. Machine classes 345x/35xx/4100/51xx are Voyager-based.
252 If you do not specifically know you have a Voyager based machine,
253 say N here, otherwise the kernel you build will not be bootable.
256 bool "NUMAQ (IBM/Sequent)"
257 depends on SMP && X86_32
260 This option is used for getting Linux to run on a (IBM/Sequent) NUMA
261 multiquad box. This changes the way that processors are bootstrapped,
262 and uses Clustered Logical APIC addressing mode instead of Flat Logical.
263 You will need a new lynxer.elf file to flash your firmware with - send
264 email to <Martin.Bligh@us.ibm.com>.
267 bool "Summit/EXA (IBM x440)"
268 depends on X86_32 && SMP
270 This option is needed for IBM systems that use the Summit/EXA chipset.
271 In particular, it is needed for the x440.
273 If you don't have one of these computers, you should say N here.
274 If you want to build a NUMA kernel, you must select ACPI.
277 bool "Support for other sub-arch SMP systems with more than 8 CPUs"
278 depends on X86_32 && SMP
280 This option is needed for the systems that have more than 8 CPUs
281 and if the system is not of any sub-arch type above.
283 If you don't have such a system, you should say N here.
286 bool "SGI 320/540 (Visual Workstation)"
289 The SGI Visual Workstation series is an IA32-based workstation
290 based on SGI systems chips with some legacy PC hardware attached.
292 Say Y here to create a kernel to run on the SGI 320 or 540.
294 A kernel compiled for the Visual Workstation will not run on PCs
295 and vice versa. See <file:Documentation/sgi-visws.txt> for details.
297 config X86_GENERICARCH
298 bool "Generic architecture (Summit, bigsmp, ES7000, default)"
301 This option compiles in the Summit, bigsmp, ES7000, default subarchitectures.
302 It is intended for a generic binary kernel.
303 If you want a NUMA kernel, select ACPI. We need SRAT for NUMA.
306 bool "Support for Unisys ES7000 IA32 series"
307 depends on X86_32 && SMP
309 Support for Unisys ES7000 systems. Say 'Y' here if this kernel is
310 supposed to run on an IA32-based Unisys ES7000 system.
311 Only choose this option if you have such a system, otherwise you
315 bool "RDC R-321x SoC"
318 select X86_REBOOTFIXUPS
323 This option is needed for RDC R-321x system-on-chip, also known
325 If you don't have one of these chips, you should say N here.
328 bool "Support for ScaleMP vSMP"
332 Support for ScaleMP vSMP systems. Say 'Y' here if this kernel is
333 supposed to run on these EM64T-based machines. Only choose this option
334 if you have one of these machines.
338 config SCHED_NO_NO_OMIT_FRAME_POINTER
340 prompt "Single-depth WCHAN output"
343 Calculate simpler /proc/<PID>/wchan values. If this option
344 is disabled then wchan values will recurse back to the
345 caller function. This provides more accurate wchan values,
346 at the expense of slightly more scheduling overhead.
348 If in doubt, say "Y".
350 menuconfig PARAVIRT_GUEST
351 bool "Paravirtualized guest support"
353 Say Y here to get to see options related to running Linux under
354 various hypervisors. This option alone does not add any kernel code.
356 If you say N, all options in this submenu will be skipped and disabled.
360 source "arch/x86/xen/Kconfig"
363 bool "VMI Guest support"
366 depends on !(X86_VISWS || X86_VOYAGER)
368 VMI provides a paravirtualized interface to the VMware ESX server
369 (it could be used by other hypervisors in theory too, but is not
370 at the moment), by linking the kernel to a GPL-ed ROM module
371 provided by the hypervisor.
373 source "arch/x86/lguest/Kconfig"
376 bool "Enable paravirtualization code"
377 depends on !(X86_VISWS || X86_VOYAGER)
379 This changes the kernel so it can modify itself when it is run
380 under a hypervisor, potentially improving performance significantly
381 over full virtualization. However, when run without a hypervisor
382 the kernel is theoretically slower and slightly larger.
386 config MEMTEST_BOOTPARAM
387 bool "Memtest boot parameter"
391 This option adds a kernel parameter 'memtest', which allows memtest
392 to be disabled at boot. If this option is selected, memtest
393 functionality can be disabled with memtest=0 on the kernel
394 command line. The purpose of this option is to allow a single
395 kernel image to be distributed with memtest built in, but not
398 If you are unsure how to answer this question, answer Y.
400 config MEMTEST_BOOTPARAM_VALUE
401 int "Memtest boot parameter default value (0-4)"
402 depends on MEMTEST_BOOTPARAM
406 This option sets the default value for the kernel parameter
407 'memtest', which allows memtest to be disabled at boot. If this
408 option is set to 0 (zero), the memtest kernel parameter will
409 default to 0, disabling memtest at bootup. If this option is
410 set to 4, the memtest kernel parameter will default to 4,
411 enabling memtest at bootup, and use that as pattern number.
413 If you are unsure how to answer this question, answer 0.
417 depends on X86_32 && ACPI && NUMA && (X86_SUMMIT || X86_GENERICARCH)
420 config HAVE_ARCH_PARSE_SRAT
424 config X86_SUMMIT_NUMA
426 depends on X86_32 && NUMA && (X86_SUMMIT || X86_GENERICARCH)
428 config X86_CYCLONE_TIMER
430 depends on X86_32 && X86_SUMMIT || X86_GENERICARCH
432 config ES7000_CLUSTERED_APIC
434 depends on SMP && X86_ES7000 && MPENTIUMIII
436 source "arch/x86/Kconfig.cpu"
440 prompt "HPET Timer Support" if X86_32
442 Use the IA-PC HPET (High Precision Event Timer) to manage
443 time in preference to the PIT and RTC, if a HPET is
445 HPET is the next generation timer replacing legacy 8254s.
446 The HPET provides a stable time base on SMP
447 systems, unlike the TSC, but it is more expensive to access,
448 as it is off-chip. You can find the HPET spec at
449 <http://www.intel.com/hardwaredesign/hpetspec.htm>.
451 You can safely choose Y here. However, HPET will only be
452 activated if the platform and the BIOS support this feature.
453 Otherwise the 8254 will be used for timing services.
455 Choose N to continue using the legacy 8254 timer.
457 config HPET_EMULATE_RTC
459 depends on HPET_TIMER && (RTC=y || RTC=m || RTC_DRV_CMOS=m || RTC_DRV_CMOS=y)
461 # Mark as embedded because too many people got it wrong.
462 # The code disables itself when not needed.
464 bool "GART IOMMU support" if EMBEDDED
468 depends on X86_64 && PCI
470 Support for full DMA access of devices with 32bit memory access only
471 on systems with more than 3GB. This is usually needed for USB,
472 sound, many IDE/SATA chipsets and some other devices.
473 Provides a driver for the AMD Athlon64/Opteron/Turion/Sempron GART
474 based hardware IOMMU and a software bounce buffer based IOMMU used
475 on Intel systems and as fallback.
476 The code is only active when needed (enough memory and limited
477 device) unless CONFIG_IOMMU_DEBUG or iommu=force is specified
481 bool "IBM Calgary IOMMU support"
483 depends on X86_64 && PCI && EXPERIMENTAL
485 Support for hardware IOMMUs in IBM's xSeries x366 and x460
486 systems. Needed to run systems with more than 3GB of memory
487 properly with 32-bit PCI devices that do not support DAC
488 (Double Address Cycle). Calgary also supports bus level
489 isolation, where all DMAs pass through the IOMMU. This
490 prevents them from going anywhere except their intended
491 destination. This catches hard-to-find kernel bugs and
492 mis-behaving drivers and devices that do not use the DMA-API
493 properly to set up their DMA buffers. The IOMMU can be
494 turned off at boot time with the iommu=off parameter.
495 Normally the kernel will make the right choice by itself.
498 config CALGARY_IOMMU_ENABLED_BY_DEFAULT
500 prompt "Should Calgary be enabled by default?"
501 depends on CALGARY_IOMMU
503 Should Calgary be enabled by default? if you choose 'y', Calgary
504 will be used (if it exists). If you choose 'n', Calgary will not be
505 used even if it exists. If you choose 'n' and would like to use
506 Calgary anyway, pass 'iommu=calgary' on the kernel command line.
510 def_bool (CALGARY_IOMMU || GART_IOMMU)
512 # need this always selected by IOMMU for the VIA workaround
516 Support for software bounce buffers used on x86-64 systems
517 which don't have a hardware IOMMU (e.g. the current generation
518 of Intel's x86-64 CPUs). Using this PCI devices which can only
519 access 32-bits of memory can be used on systems with more than
520 3 GB of memory. If unsure, say Y.
524 int "Maximum number of CPUs (2-255)"
527 default "32" if X86_NUMAQ || X86_SUMMIT || X86_BIGSMP || X86_ES7000
530 This allows you to specify the maximum number of CPUs which this
531 kernel will support. The maximum supported value is 255 and the
532 minimum value which makes sense is 2.
534 This is purely to save memory - each supported CPU adds
535 approximately eight kilobytes to the kernel image.
538 bool "SMT (Hyperthreading) scheduler support"
541 SMT scheduler support improves the CPU scheduler's decision making
542 when dealing with Intel Pentium 4 chips with HyperThreading at a
543 cost of slightly increased overhead in some places. If unsure say
548 prompt "Multi-core scheduler support"
551 Multi-core scheduler support improves the CPU scheduler's decision
552 making when dealing with multi-core CPU chips at a cost of slightly
553 increased overhead in some places. If unsure say N here.
555 source "kernel/Kconfig.preempt"
558 bool "Local APIC support on uniprocessors"
559 depends on X86_32 && !SMP && !(X86_VISWS || X86_VOYAGER || X86_GENERICARCH)
561 A local APIC (Advanced Programmable Interrupt Controller) is an
562 integrated interrupt controller in the CPU. If you have a single-CPU
563 system which has a processor with a local APIC, you can say Y here to
564 enable and use it. If you say Y here even though your machine doesn't
565 have a local APIC, then the kernel will still run with no slowdown at
566 all. The local APIC supports CPU-generated self-interrupts (timer,
567 performance counters), and the NMI watchdog which detects hard
571 bool "IO-APIC support on uniprocessors"
572 depends on X86_UP_APIC
574 An IO-APIC (I/O Advanced Programmable Interrupt Controller) is an
575 SMP-capable replacement for PC-style interrupt controllers. Most
576 SMP systems and many recent uniprocessor systems have one.
578 If you have a single-CPU system with an IO-APIC, you can say Y here
579 to use it. If you say Y here even though your machine doesn't have
580 an IO-APIC, then the kernel will still run with no slowdown at all.
582 config X86_LOCAL_APIC
584 depends on X86_64 || (X86_32 && (X86_UP_APIC || ((X86_VISWS || SMP) && !X86_VOYAGER) || X86_GENERICARCH))
588 depends on X86_64 || (X86_32 && (X86_UP_IOAPIC || (SMP && !(X86_VISWS || X86_VOYAGER)) || X86_GENERICARCH))
590 config X86_VISWS_APIC
592 depends on X86_32 && X86_VISWS
595 bool "Machine Check Exception"
596 depends on !X86_VOYAGER
598 Machine Check Exception support allows the processor to notify the
599 kernel if it detects a problem (e.g. overheating, component failure).
600 The action the kernel takes depends on the severity of the problem,
601 ranging from a warning message on the console, to halting the machine.
602 Your processor must be a Pentium or newer to support this - check the
603 flags in /proc/cpuinfo for mce. Note that some older Pentium systems
604 have a design flaw which leads to false MCE events - hence MCE is
605 disabled on all P5 processors, unless explicitly enabled with "mce"
606 as a boot argument. Similarly, if MCE is built in and creates a
607 problem on some new non-standard machine, you can boot with "nomce"
608 to disable it. MCE support simply ignores non-MCE processors like
609 the 386 and 486, so nearly everyone can say Y here.
613 prompt "Intel MCE features"
614 depends on X86_64 && X86_MCE && X86_LOCAL_APIC
616 Additional support for intel specific MCE features such as
621 prompt "AMD MCE features"
622 depends on X86_64 && X86_MCE && X86_LOCAL_APIC
624 Additional support for AMD specific MCE features such as
625 the DRAM Error Threshold.
627 config X86_MCE_NONFATAL
628 tristate "Check for non-fatal errors on AMD Athlon/Duron / Intel Pentium 4"
629 depends on X86_32 && X86_MCE
631 Enabling this feature starts a timer that triggers every 5 seconds which
632 will look at the machine check registers to see if anything happened.
633 Non-fatal problems automatically get corrected (but still logged).
634 Disable this if you don't want to see these messages.
635 Seeing the messages this option prints out may be indicative of dying
636 or out-of-spec (ie, overclocked) hardware.
637 This option only does something on certain CPUs.
638 (AMD Athlon/Duron and Intel Pentium 4)
640 config X86_MCE_P4THERMAL
641 bool "check for P4 thermal throttling interrupt."
642 depends on X86_32 && X86_MCE && (X86_UP_APIC || SMP) && !X86_VISWS
644 Enabling this feature will cause a message to be printed when the P4
645 enters thermal throttling.
648 bool "Enable VM86 support" if EMBEDDED
652 This option is required by programs like DOSEMU to run 16-bit legacy
653 code on X86 processors. It also may be needed by software like
654 XFree86 to initialize some video cards via BIOS. Disabling this
655 option saves about 6k.
658 tristate "Toshiba Laptop support"
661 This adds a driver to safely access the System Management Mode of
662 the CPU on Toshiba portables with a genuine Toshiba BIOS. It does
663 not work on models with a Phoenix BIOS. The System Management Mode
664 is used to set the BIOS and power saving options on Toshiba portables.
666 For information on utilities to make use of this driver see the
667 Toshiba Linux utilities web site at:
668 <http://www.buzzard.org.uk/toshiba/>.
670 Say Y if you intend to run this kernel on a Toshiba portable.
674 tristate "Dell laptop support"
676 This adds a driver to safely access the System Management Mode
677 of the CPU on the Dell Inspiron 8000. The System Management Mode
678 is used to read cpu temperature and cooling fan status and to
679 control the fans on the I8K portables.
681 This driver has been tested only on the Inspiron 8000 but it may
682 also work with other Dell laptops. You can force loading on other
683 models by passing the parameter `force=1' to the module. Use at
686 For information on utilities to make use of this driver see the
687 I8K Linux utilities web site at:
688 <http://people.debian.org/~dz/i8k/>
690 Say Y if you intend to run this kernel on a Dell Inspiron 8000.
693 config X86_REBOOTFIXUPS
695 prompt "Enable X86 board specific fixups for reboot"
696 depends on X86_32 && X86
698 This enables chipset and/or board specific fixups to be done
699 in order to get reboot to work correctly. This is only needed on
700 some combinations of hardware and BIOS. The symptom, for which
701 this config is intended, is when reboot ends with a stalled/hung
704 Currently, the only fixup is for the Geode machines using
705 CS5530A and CS5536 chipsets and the RDC R-321x SoC.
707 Say Y if you want to enable the fixup. Currently, it's safe to
708 enable this option even if you don't need it.
712 tristate "/dev/cpu/microcode - Intel IA32 CPU microcode support"
715 If you say Y here, you will be able to update the microcode on
716 Intel processors in the IA32 family, e.g. Pentium Pro, Pentium II,
717 Pentium III, Pentium 4, Xeon etc. You will obviously need the
718 actual microcode binary data itself which is not shipped with the
721 For latest news and information on obtaining all the required
722 ingredients for this driver, check:
723 <http://www.urbanmyth.org/microcode/>.
725 To compile this driver as a module, choose M here: the
726 module will be called microcode.
728 config MICROCODE_OLD_INTERFACE
733 tristate "/dev/cpu/*/msr - Model-specific register support"
735 This device gives privileged processes access to the x86
736 Model-Specific Registers (MSRs). It is a character device with
737 major 202 and minors 0 to 31 for /dev/cpu/0/msr to /dev/cpu/31/msr.
738 MSR accesses are directed to a specific CPU on multi-processor
742 tristate "/dev/cpu/*/cpuid - CPU information support"
744 This device gives processes access to the x86 CPUID instruction to
745 be executed on a specific processor. It is a character device
746 with major 203 and minors 0 to 31 for /dev/cpu/0/cpuid to
750 prompt "High Memory Support"
751 default HIGHMEM4G if !X86_NUMAQ
752 default HIGHMEM64G if X86_NUMAQ
757 depends on !X86_NUMAQ
759 Linux can use up to 64 Gigabytes of physical memory on x86 systems.
760 However, the address space of 32-bit x86 processors is only 4
761 Gigabytes large. That means that, if you have a large amount of
762 physical memory, not all of it can be "permanently mapped" by the
763 kernel. The physical memory that's not permanently mapped is called
766 If you are compiling a kernel which will never run on a machine with
767 more than 1 Gigabyte total physical RAM, answer "off" here (default
768 choice and suitable for most users). This will result in a "3GB/1GB"
769 split: 3GB are mapped so that each process sees a 3GB virtual memory
770 space and the remaining part of the 4GB virtual memory space is used
771 by the kernel to permanently map as much physical memory as
774 If the machine has between 1 and 4 Gigabytes physical RAM, then
777 If more than 4 Gigabytes is used then answer "64GB" here. This
778 selection turns Intel PAE (Physical Address Extension) mode on.
779 PAE implements 3-level paging on IA32 processors. PAE is fully
780 supported by Linux, PAE mode is implemented on all recent Intel
781 processors (Pentium Pro and better). NOTE: If you say "64GB" here,
782 then the kernel will not boot on CPUs that don't support PAE!
784 The actual amount of total physical memory will either be
785 auto detected or can be forced by using a kernel command line option
786 such as "mem=256M". (Try "man bootparam" or see the documentation of
787 your boot loader (lilo or loadlin) about how to pass options to the
788 kernel at boot time.)
790 If unsure, say "off".
794 depends on !X86_NUMAQ
796 Select this if you have a 32-bit processor and between 1 and 4
797 gigabytes of physical RAM.
801 depends on !M386 && !M486
804 Select this if you have a 32-bit processor and more than 4
805 gigabytes of physical RAM.
810 depends on EXPERIMENTAL
811 prompt "Memory split" if EMBEDDED
815 Select the desired split between kernel and user memory.
817 If the address range available to the kernel is less than the
818 physical memory installed, the remaining memory will be available
819 as "high memory". Accessing high memory is a little more costly
820 than low memory, as it needs to be mapped into the kernel first.
821 Note that increasing the kernel address space limits the range
822 available to user programs, making the address space there
823 tighter. Selecting anything other than the default 3G/1G split
824 will also likely make your kernel incompatible with binary-only
827 If you are not absolutely sure what you are doing, leave this
831 bool "3G/1G user/kernel split"
832 config VMSPLIT_3G_OPT
834 bool "3G/1G user/kernel split (for full 1G low memory)"
836 bool "2G/2G user/kernel split"
837 config VMSPLIT_2G_OPT
839 bool "2G/2G user/kernel split (for full 2G low memory)"
841 bool "1G/3G user/kernel split"
846 default 0xB0000000 if VMSPLIT_3G_OPT
847 default 0x80000000 if VMSPLIT_2G
848 default 0x78000000 if VMSPLIT_2G_OPT
849 default 0x40000000 if VMSPLIT_1G
855 depends on X86_32 && (HIGHMEM64G || HIGHMEM4G)
859 prompt "PAE (Physical Address Extension) Support"
860 depends on X86_32 && !HIGHMEM4G
861 select RESOURCES_64BIT
863 PAE is required for NX support, and furthermore enables
864 larger swapspace support for non-overcommit purposes. It
865 has the cost of more pagetable lookup overhead, and also
866 consumes more pagetable space per process.
868 # Common NUMA Features
870 bool "Numa Memory Allocation and Scheduler Support (EXPERIMENTAL)"
872 depends on X86_64 || (X86_32 && HIGHMEM64G && (X86_NUMAQ || (X86_SUMMIT || X86_GENERICARCH) && ACPI) && EXPERIMENTAL)
874 default y if (X86_NUMAQ || X86_SUMMIT)
876 Enable NUMA (Non Uniform Memory Access) support.
877 The kernel will try to allocate memory used by a CPU on the
878 local memory controller of the CPU and add some more
879 NUMA awareness to the kernel.
881 For i386 this is currently highly experimental and should be only
882 used for kernel development. It might also cause boot failures.
883 For x86_64 this is recommended on all multiprocessor Opteron systems.
884 If the system is EM64T, you should say N unless your system is
887 comment "NUMA (Summit) requires SMP, 64GB highmem support, ACPI"
888 depends on X86_32 && X86_SUMMIT && (!HIGHMEM64G || !ACPI)
892 prompt "Old style AMD Opteron NUMA detection"
893 depends on X86_64 && NUMA && PCI
895 Enable K8 NUMA node topology detection. You should say Y here if
896 you have a multi processor AMD K8 system. This uses an old
897 method to read the NUMA configuration directly from the builtin
898 Northbridge of Opteron. It is recommended to use X86_64_ACPI_NUMA
899 instead, which also takes priority if both are compiled in.
901 config X86_64_ACPI_NUMA
903 prompt "ACPI NUMA detection"
904 depends on X86_64 && NUMA && ACPI && PCI
907 Enable ACPI SRAT based node topology detection.
910 bool "NUMA emulation"
911 depends on X86_64 && NUMA
913 Enable NUMA emulation. A flat machine will be split
914 into virtual nodes when booted with "numa=fake=N", where N is the
915 number of nodes. This is only useful for debugging.
918 int "Max num nodes shift(1-15)"
920 default "6" if X86_64
921 default "4" if X86_NUMAQ
923 depends on NEED_MULTIPLE_NODES
925 config HAVE_ARCH_BOOTMEM_NODE
927 depends on X86_32 && NUMA
929 config ARCH_HAVE_MEMORY_PRESENT
931 depends on X86_32 && DISCONTIGMEM
933 config NEED_NODE_MEMMAP_SIZE
935 depends on X86_32 && (DISCONTIGMEM || SPARSEMEM)
937 config HAVE_ARCH_ALLOC_REMAP
939 depends on X86_32 && NUMA
941 config ARCH_FLATMEM_ENABLE
943 depends on X86_32 && ARCH_SELECT_MEMORY_MODEL && X86_PC && !NUMA
945 config ARCH_DISCONTIGMEM_ENABLE
947 depends on NUMA && X86_32
949 config ARCH_DISCONTIGMEM_DEFAULT
951 depends on NUMA && X86_32
953 config ARCH_SPARSEMEM_DEFAULT
957 config ARCH_SPARSEMEM_ENABLE
959 depends on X86_64 || NUMA || (EXPERIMENTAL && X86_PC)
960 select SPARSEMEM_STATIC if X86_32
961 select SPARSEMEM_VMEMMAP_ENABLE if X86_64
963 config ARCH_SELECT_MEMORY_MODEL
965 depends on ARCH_SPARSEMEM_ENABLE
967 config ARCH_MEMORY_PROBE
969 depends on MEMORY_HOTPLUG
974 bool "Allocate 3rd-level pagetables from highmem"
975 depends on X86_32 && (HIGHMEM4G || HIGHMEM64G)
977 The VM uses one page table entry for each page of physical memory.
978 For systems with a lot of RAM, this can be wasteful of precious
979 low memory. Setting this option will put user-space page table
980 entries in high memory.
982 config MATH_EMULATION
984 prompt "Math emulation" if X86_32
986 Linux can emulate a math coprocessor (used for floating point
987 operations) if you don't have one. 486DX and Pentium processors have
988 a math coprocessor built in, 486SX and 386 do not, unless you added
989 a 487DX or 387, respectively. (The messages during boot time can
990 give you some hints here ["man dmesg"].) Everyone needs either a
991 coprocessor or this emulation.
993 If you don't have a math coprocessor, you need to say Y here; if you
994 say Y here even though you have a coprocessor, the coprocessor will
995 be used nevertheless. (This behavior can be changed with the kernel
996 command line option "no387", which comes handy if your coprocessor
997 is broken. Try "man bootparam" or see the documentation of your boot
998 loader (lilo or loadlin) about how to pass options to the kernel at
999 boot time.) This means that it is a good idea to say Y here if you
1000 intend to use this kernel on different machines.
1002 More information about the internals of the Linux math coprocessor
1003 emulation can be found in <file:arch/x86/math-emu/README>.
1005 If you are not sure, say Y; apart from resulting in a 66 KB bigger
1006 kernel, it won't hurt.
1009 bool "MTRR (Memory Type Range Register) support"
1011 On Intel P6 family processors (Pentium Pro, Pentium II and later)
1012 the Memory Type Range Registers (MTRRs) may be used to control
1013 processor access to memory ranges. This is most useful if you have
1014 a video (VGA) card on a PCI or AGP bus. Enabling write-combining
1015 allows bus write transfers to be combined into a larger transfer
1016 before bursting over the PCI/AGP bus. This can increase performance
1017 of image write operations 2.5 times or more. Saying Y here creates a
1018 /proc/mtrr file which may be used to manipulate your processor's
1019 MTRRs. Typically the X server should use this.
1021 This code has a reasonably generic interface so that similar
1022 control registers on other processors can be easily supported
1025 The Cyrix 6x86, 6x86MX and M II processors have Address Range
1026 Registers (ARRs) which provide a similar functionality to MTRRs. For
1027 these, the ARRs are used to emulate the MTRRs.
1028 The AMD K6-2 (stepping 8 and above) and K6-3 processors have two
1029 MTRRs. The Centaur C6 (WinChip) has 8 MCRs, allowing
1030 write-combining. All of these processors are supported by this code
1031 and it makes sense to say Y here if you have one of them.
1033 Saying Y here also fixes a problem with buggy SMP BIOSes which only
1034 set the MTRRs for the boot CPU and not for the secondary CPUs. This
1035 can lead to all sorts of problems, so it's good to say Y here.
1037 You can safely say Y even if your machine doesn't have MTRRs, you'll
1038 just add about 9 KB to your kernel.
1040 See <file:Documentation/mtrr.txt> for more information.
1044 prompt "x86 PAT support"
1045 depends on MTRR && NONPROMISC_DEVMEM
1047 Use PAT attributes to setup page level cache control.
1049 PATs are the modern equivalents of MTRRs and are much more
1050 flexible than MTRRs.
1052 Say N here if you see bootup problems (boot crash, boot hang,
1053 spontaneous reboots) or a non-working video driver.
1059 prompt "EFI runtime service support"
1062 This enables the kernel to use EFI runtime services that are
1063 available (such as the EFI variable services).
1065 This option is only useful on systems that have EFI firmware.
1066 In addition, you should use the latest ELILO loader available
1067 at <http://elilo.sourceforge.net> in order to take advantage
1068 of EFI runtime services. However, even with this option, the
1069 resultant kernel should continue to boot on existing non-EFI
1074 prompt "Enable kernel irq balancing"
1075 depends on X86_32 && SMP && X86_IO_APIC
1077 The default yes will allow the kernel to do irq load balancing.
1078 Saying no will keep the kernel from doing irq load balancing.
1082 prompt "Enable seccomp to safely compute untrusted bytecode"
1085 This kernel feature is useful for number crunching applications
1086 that may need to compute untrusted bytecode during their
1087 execution. By using pipes or other transports made available to
1088 the process as file descriptors supporting the read/write
1089 syscalls, it's possible to isolate those applications in
1090 their own address space using seccomp. Once seccomp is
1091 enabled via /proc/<pid>/seccomp, it cannot be disabled
1092 and the task is only allowed to execute a few safe syscalls
1093 defined by each seccomp mode.
1095 If unsure, say Y. Only embedded should say N here.
1097 config CC_STACKPROTECTOR
1098 bool "Enable -fstack-protector buffer overflow detection (EXPERIMENTAL)"
1099 depends on X86_64 && EXPERIMENTAL && BROKEN
1101 This option turns on the -fstack-protector GCC feature. This
1102 feature puts, at the beginning of critical functions, a canary
1103 value on the stack just before the return address, and validates
1104 the value just before actually returning. Stack based buffer
1105 overflows (that need to overwrite this return address) now also
1106 overwrite the canary, which gets detected and the attack is then
1107 neutralized via a kernel panic.
1109 This feature requires gcc version 4.2 or above, or a distribution
1110 gcc with the feature backported. Older versions are automatically
1111 detected and for those versions, this configuration option is ignored.
1113 config CC_STACKPROTECTOR_ALL
1114 bool "Use stack-protector for all functions"
1115 depends on CC_STACKPROTECTOR
1117 Normally, GCC only inserts the canary value protection for
1118 functions that use large-ish on-stack buffers. By enabling
1119 this option, GCC will be asked to do this for ALL functions.
1121 source kernel/Kconfig.hz
1124 bool "kexec system call"
1125 depends on X86_64 || X86_BIOS_REBOOT
1127 kexec is a system call that implements the ability to shutdown your
1128 current kernel, and to start another kernel. It is like a reboot
1129 but it is independent of the system firmware. And like a reboot
1130 you can start any kernel with it, not just Linux.
1132 The name comes from the similarity to the exec system call.
1134 It is an ongoing process to be certain the hardware in a machine
1135 is properly shutdown, so do not be surprised if this code does not
1136 initially work for you. It may help to enable device hotplugging
1137 support. As of this writing the exact hardware interface is
1138 strongly in flux, so no good recommendation can be made.
1141 bool "kernel crash dumps (EXPERIMENTAL)"
1142 depends on EXPERIMENTAL
1143 depends on X86_64 || (X86_32 && HIGHMEM)
1145 Generate crash dump after being started by kexec.
1146 This should be normally only set in special crash dump kernels
1147 which are loaded in the main kernel with kexec-tools into
1148 a specially reserved region and then later executed after
1149 a crash by kdump/kexec. The crash dump kernel must be compiled
1150 to a memory address not used by the main kernel or BIOS using
1151 PHYSICAL_START, or it must be built as a relocatable image
1152 (CONFIG_RELOCATABLE=y).
1153 For more details see Documentation/kdump/kdump.txt
1155 config PHYSICAL_START
1156 hex "Physical address where the kernel is loaded" if (EMBEDDED || CRASH_DUMP)
1157 default "0x1000000" if X86_NUMAQ
1158 default "0x200000" if X86_64
1161 This gives the physical address where the kernel is loaded.
1163 If kernel is a not relocatable (CONFIG_RELOCATABLE=n) then
1164 bzImage will decompress itself to above physical address and
1165 run from there. Otherwise, bzImage will run from the address where
1166 it has been loaded by the boot loader and will ignore above physical
1169 In normal kdump cases one does not have to set/change this option
1170 as now bzImage can be compiled as a completely relocatable image
1171 (CONFIG_RELOCATABLE=y) and be used to load and run from a different
1172 address. This option is mainly useful for the folks who don't want
1173 to use a bzImage for capturing the crash dump and want to use a
1174 vmlinux instead. vmlinux is not relocatable hence a kernel needs
1175 to be specifically compiled to run from a specific memory area
1176 (normally a reserved region) and this option comes handy.
1178 So if you are using bzImage for capturing the crash dump, leave
1179 the value here unchanged to 0x100000 and set CONFIG_RELOCATABLE=y.
1180 Otherwise if you plan to use vmlinux for capturing the crash dump
1181 change this value to start of the reserved region (Typically 16MB
1182 0x1000000). In other words, it can be set based on the "X" value as
1183 specified in the "crashkernel=YM@XM" command line boot parameter
1184 passed to the panic-ed kernel. Typically this parameter is set as
1185 crashkernel=64M@16M. Please take a look at
1186 Documentation/kdump/kdump.txt for more details about crash dumps.
1188 Usage of bzImage for capturing the crash dump is recommended as
1189 one does not have to build two kernels. Same kernel can be used
1190 as production kernel and capture kernel. Above option should have
1191 gone away after relocatable bzImage support is introduced. But it
1192 is present because there are users out there who continue to use
1193 vmlinux for dump capture. This option should go away down the
1196 Don't change this unless you know what you are doing.
1199 bool "Build a relocatable kernel (EXPERIMENTAL)"
1200 depends on EXPERIMENTAL
1202 This builds a kernel image that retains relocation information
1203 so it can be loaded someplace besides the default 1MB.
1204 The relocations tend to make the kernel binary about 10% larger,
1205 but are discarded at runtime.
1207 One use is for the kexec on panic case where the recovery kernel
1208 must live at a different physical address than the primary
1211 Note: If CONFIG_RELOCATABLE=y, then the kernel runs from the address
1212 it has been loaded at and the compile time physical address
1213 (CONFIG_PHYSICAL_START) is ignored.
1215 config PHYSICAL_ALIGN
1217 prompt "Alignment value to which kernel should be aligned" if X86_32
1218 default "0x100000" if X86_32
1219 default "0x200000" if X86_64
1220 range 0x2000 0x400000
1222 This value puts the alignment restrictions on physical address
1223 where kernel is loaded and run from. Kernel is compiled for an
1224 address which meets above alignment restriction.
1226 If bootloader loads the kernel at a non-aligned address and
1227 CONFIG_RELOCATABLE is set, kernel will move itself to nearest
1228 address aligned to above value and run from there.
1230 If bootloader loads the kernel at a non-aligned address and
1231 CONFIG_RELOCATABLE is not set, kernel will ignore the run time
1232 load address and decompress itself to the address it has been
1233 compiled for and run from there. The address for which kernel is
1234 compiled already meets above alignment restrictions. Hence the
1235 end result is that kernel runs from a physical address meeting
1236 above alignment restrictions.
1238 Don't change this unless you know what you are doing.
1241 bool "Support for suspend on SMP and hot-pluggable CPUs (EXPERIMENTAL)"
1242 depends on SMP && HOTPLUG && EXPERIMENTAL && !X86_VOYAGER
1244 Say Y here to experiment with turning CPUs off and on, and to
1245 enable suspend on SMP systems. CPUs can be controlled through
1246 /sys/devices/system/cpu.
1247 Say N if you want to disable CPU hotplug and don't need to
1252 prompt "Compat VDSO support"
1253 depends on X86_32 || IA32_EMULATION
1255 Map the 32-bit VDSO to the predictable old-style address too.
1257 Say N here if you are running a sufficiently recent glibc
1258 version (2.3.3 or later), to remove the high-mapped
1259 VDSO mapping and to exclusively use the randomized VDSO.
1265 config ARCH_ENABLE_MEMORY_HOTPLUG
1267 depends on X86_64 || (X86_32 && HIGHMEM)
1269 config HAVE_ARCH_EARLY_PFN_TO_NID
1273 menu "Power management options"
1274 depends on !X86_VOYAGER
1276 config ARCH_HIBERNATION_HEADER
1278 depends on X86_64 && HIBERNATION
1280 source "kernel/power/Kconfig"
1282 source "drivers/acpi/Kconfig"
1287 depends on APM || APM_MODULE
1290 tristate "APM (Advanced Power Management) BIOS support"
1291 depends on X86_32 && PM_SLEEP && !X86_VISWS
1293 APM is a BIOS specification for saving power using several different
1294 techniques. This is mostly useful for battery powered laptops with
1295 APM compliant BIOSes. If you say Y here, the system time will be
1296 reset after a RESUME operation, the /proc/apm device will provide
1297 battery status information, and user-space programs will receive
1298 notification of APM "events" (e.g. battery status change).
1300 If you select "Y" here, you can disable actual use of the APM
1301 BIOS by passing the "apm=off" option to the kernel at boot time.
1303 Note that the APM support is almost completely disabled for
1304 machines with more than one CPU.
1306 In order to use APM, you will need supporting software. For location
1307 and more information, read <file:Documentation/power/pm.txt> and the
1308 Battery Powered Linux mini-HOWTO, available from
1309 <http://www.tldp.org/docs.html#howto>.
1311 This driver does not spin down disk drives (see the hdparm(8)
1312 manpage ("man 8 hdparm") for that), and it doesn't turn off
1313 VESA-compliant "green" monitors.
1315 This driver does not support the TI 4000M TravelMate and the ACER
1316 486/DX4/75 because they don't have compliant BIOSes. Many "green"
1317 desktop machines also don't have compliant BIOSes, and this driver
1318 may cause those machines to panic during the boot phase.
1320 Generally, if you don't have a battery in your machine, there isn't
1321 much point in using this driver and you should say N. If you get
1322 random kernel OOPSes or reboots that don't seem to be related to
1323 anything, try disabling/enabling this option (or disabling/enabling
1326 Some other things you should try when experiencing seemingly random,
1329 1) make sure that you have enough swap space and that it is
1331 2) pass the "no-hlt" option to the kernel
1332 3) switch on floating point emulation in the kernel and pass
1333 the "no387" option to the kernel
1334 4) pass the "floppy=nodma" option to the kernel
1335 5) pass the "mem=4M" option to the kernel (thereby disabling
1336 all but the first 4 MB of RAM)
1337 6) make sure that the CPU is not over clocked.
1338 7) read the sig11 FAQ at <http://www.bitwizard.nl/sig11/>
1339 8) disable the cache from your BIOS settings
1340 9) install a fan for the video card or exchange video RAM
1341 10) install a better fan for the CPU
1342 11) exchange RAM chips
1343 12) exchange the motherboard.
1345 To compile this driver as a module, choose M here: the
1346 module will be called apm.
1350 config APM_IGNORE_USER_SUSPEND
1351 bool "Ignore USER SUSPEND"
1353 This option will ignore USER SUSPEND requests. On machines with a
1354 compliant APM BIOS, you want to say N. However, on the NEC Versa M
1355 series notebooks, it is necessary to say Y because of a BIOS bug.
1357 config APM_DO_ENABLE
1358 bool "Enable PM at boot time"
1360 Enable APM features at boot time. From page 36 of the APM BIOS
1361 specification: "When disabled, the APM BIOS does not automatically
1362 power manage devices, enter the Standby State, enter the Suspend
1363 State, or take power saving steps in response to CPU Idle calls."
1364 This driver will make CPU Idle calls when Linux is idle (unless this
1365 feature is turned off -- see "Do CPU IDLE calls", below). This
1366 should always save battery power, but more complicated APM features
1367 will be dependent on your BIOS implementation. You may need to turn
1368 this option off if your computer hangs at boot time when using APM
1369 support, or if it beeps continuously instead of suspending. Turn
1370 this off if you have a NEC UltraLite Versa 33/C or a Toshiba
1371 T400CDT. This is off by default since most machines do fine without
1375 bool "Make CPU Idle calls when idle"
1377 Enable calls to APM CPU Idle/CPU Busy inside the kernel's idle loop.
1378 On some machines, this can activate improved power savings, such as
1379 a slowed CPU clock rate, when the machine is idle. These idle calls
1380 are made after the idle loop has run for some length of time (e.g.,
1381 333 mS). On some machines, this will cause a hang at boot time or
1382 whenever the CPU becomes idle. (On machines with more than one CPU,
1383 this option does nothing.)
1385 config APM_DISPLAY_BLANK
1386 bool "Enable console blanking using APM"
1388 Enable console blanking using the APM. Some laptops can use this to
1389 turn off the LCD backlight when the screen blanker of the Linux
1390 virtual console blanks the screen. Note that this is only used by
1391 the virtual console screen blanker, and won't turn off the backlight
1392 when using the X Window system. This also doesn't have anything to
1393 do with your VESA-compliant power-saving monitor. Further, this
1394 option doesn't work for all laptops -- it might not turn off your
1395 backlight at all, or it might print a lot of errors to the console,
1396 especially if you are using gpm.
1398 config APM_ALLOW_INTS
1399 bool "Allow interrupts during APM BIOS calls"
1401 Normally we disable external interrupts while we are making calls to
1402 the APM BIOS as a measure to lessen the effects of a badly behaving
1403 BIOS implementation. The BIOS should reenable interrupts if it
1404 needs to. Unfortunately, some BIOSes do not -- especially those in
1405 many of the newer IBM Thinkpads. If you experience hangs when you
1406 suspend, try setting this to Y. Otherwise, say N.
1408 config APM_REAL_MODE_POWER_OFF
1409 bool "Use real mode APM BIOS call to power off"
1411 Use real mode APM BIOS calls to switch off the computer. This is
1412 a work-around for a number of buggy BIOSes. Switch this option on if
1413 your computer crashes instead of powering off properly.
1417 source "arch/x86/kernel/cpu/cpufreq/Kconfig"
1419 source "drivers/cpuidle/Kconfig"
1424 menu "Bus options (PCI etc.)"
1427 bool "PCI support" if !X86_VISWS && !X86_VSMP
1428 depends on !X86_VOYAGER
1430 select ARCH_SUPPORTS_MSI if (X86_LOCAL_APIC && X86_IO_APIC)
1432 Find out whether you have a PCI motherboard. PCI is the name of a
1433 bus system, i.e. the way the CPU talks to the other stuff inside
1434 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
1435 VESA. If you have PCI, say Y, otherwise N.
1438 prompt "PCI access mode"
1439 depends on X86_32 && PCI && !X86_VISWS
1442 On PCI systems, the BIOS can be used to detect the PCI devices and
1443 determine their configuration. However, some old PCI motherboards
1444 have BIOS bugs and may crash if this is done. Also, some embedded
1445 PCI-based systems don't have any BIOS at all. Linux can also try to
1446 detect the PCI hardware directly without using the BIOS.
1448 With this option, you can specify how Linux should detect the
1449 PCI devices. If you choose "BIOS", the BIOS will be used,
1450 if you choose "Direct", the BIOS won't be used, and if you
1451 choose "MMConfig", then PCI Express MMCONFIG will be used.
1452 If you choose "Any", the kernel will try MMCONFIG, then the
1453 direct access method and falls back to the BIOS if that doesn't
1454 work. If unsure, go with the default, which is "Any".
1459 config PCI_GOMMCONFIG
1472 depends on X86_32 && !X86_VISWS && PCI && (PCI_GOBIOS || PCI_GOANY)
1474 # x86-64 doesn't support PCI BIOS access from long mode so always go direct.
1477 depends on PCI && (X86_64 || (PCI_GODIRECT || PCI_GOANY) || X86_VISWS)
1481 depends on X86_32 && PCI && ACPI && (PCI_GOMMCONFIG || PCI_GOANY)
1488 bool "Support mmconfig PCI config space access"
1489 depends on X86_64 && PCI && ACPI
1492 bool "Support for DMA Remapping Devices (EXPERIMENTAL)"
1493 depends on X86_64 && PCI_MSI && ACPI && EXPERIMENTAL
1495 DMA remapping (DMAR) devices support enables independent address
1496 translations for Direct Memory Access (DMA) from devices.
1497 These DMA remapping devices are reported via ACPI tables
1498 and include PCI device scope covered by these DMA
1503 prompt "Support for Graphics workaround"
1506 Current Graphics drivers tend to use physical address
1507 for DMA and avoid using DMA APIs. Setting this config
1508 option permits the IOMMU driver to set a unity map for
1509 all the OS-visible memory. Hence the driver can continue
1510 to use physical addresses for DMA.
1512 config DMAR_FLOPPY_WA
1516 Floppy disk drivers are know to bypass DMA API calls
1517 thereby failing to work when IOMMU is enabled. This
1518 workaround will setup a 1:1 mapping for the first
1519 16M to make floppy (an ISA device) work.
1521 source "drivers/pci/pcie/Kconfig"
1523 source "drivers/pci/Kconfig"
1525 # x86_64 have no ISA slots, but do have ISA-style DMA.
1533 depends on !(X86_VOYAGER || X86_VISWS)
1535 Find out whether you have ISA slots on your motherboard. ISA is the
1536 name of a bus system, i.e. the way the CPU talks to the other stuff
1537 inside your box. Other bus systems are PCI, EISA, MicroChannel
1538 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
1539 newer boards don't support it. If you have ISA, say Y, otherwise N.
1545 The Extended Industry Standard Architecture (EISA) bus was
1546 developed as an open alternative to the IBM MicroChannel bus.
1548 The EISA bus provided some of the features of the IBM MicroChannel
1549 bus while maintaining backward compatibility with cards made for
1550 the older ISA bus. The EISA bus saw limited use between 1988 and
1551 1995 when it was made obsolete by the PCI bus.
1553 Say Y here if you are building a kernel for an EISA-based machine.
1557 source "drivers/eisa/Kconfig"
1560 bool "MCA support" if !(X86_VISWS || X86_VOYAGER)
1561 default y if X86_VOYAGER
1563 MicroChannel Architecture is found in some IBM PS/2 machines and
1564 laptops. It is a bus system similar to PCI or ISA. See
1565 <file:Documentation/mca.txt> (and especially the web page given
1566 there) before attempting to build an MCA bus kernel.
1568 source "drivers/mca/Kconfig"
1571 tristate "NatSemi SCx200 support"
1572 depends on !X86_VOYAGER
1574 This provides basic support for National Semiconductor's
1575 (now AMD's) Geode processors. The driver probes for the
1576 PCI-IDs of several on-chip devices, so its a good dependency
1577 for other scx200_* drivers.
1579 If compiled as a module, the driver is named scx200.
1581 config SCx200HR_TIMER
1582 tristate "NatSemi SCx200 27MHz High-Resolution Timer Support"
1583 depends on SCx200 && GENERIC_TIME
1586 This driver provides a clocksource built upon the on-chip
1587 27MHz high-resolution timer. Its also a workaround for
1588 NSC Geode SC-1100's buggy TSC, which loses time when the
1589 processor goes idle (as is done by the scheduler). The
1590 other workaround is idle=poll boot option.
1592 config GEODE_MFGPT_TIMER
1594 prompt "Geode Multi-Function General Purpose Timer (MFGPT) events"
1595 depends on MGEODE_LX && GENERIC_TIME && GENERIC_CLOCKEVENTS
1597 This driver provides a clock event source based on the MFGPT
1598 timer(s) in the CS5535 and CS5536 companion chip for the geode.
1599 MFGPTs have a better resolution and max interval than the
1600 generic PIT, and are suitable for use as high-res timers.
1606 depends on AGP_AMD64 || (X86_64 && (GART_IOMMU || (PCI && NUMA)))
1608 source "drivers/pcmcia/Kconfig"
1610 source "drivers/pci/hotplug/Kconfig"
1615 menu "Executable file formats / Emulations"
1617 source "fs/Kconfig.binfmt"
1619 config IA32_EMULATION
1620 bool "IA32 Emulation"
1622 select COMPAT_BINFMT_ELF
1624 Include code to run 32-bit programs under a 64-bit kernel. You should
1625 likely turn this on, unless you're 100% sure that you don't have any
1626 32-bit programs left.
1629 tristate "IA32 a.out support"
1630 depends on IA32_EMULATION && ARCH_SUPPORTS_AOUT
1632 Support old a.out binaries in the 32bit emulation.
1636 depends on IA32_EMULATION
1638 config COMPAT_FOR_U64_ALIGNMENT
1642 config SYSVIPC_COMPAT
1644 depends on X86_64 && COMPAT && SYSVIPC
1649 source "net/Kconfig"
1651 source "drivers/Kconfig"
1653 source "drivers/firmware/Kconfig"
1657 source "arch/x86/Kconfig.debug"
1659 source "security/Kconfig"
1661 source "crypto/Kconfig"
1663 source "arch/x86/kvm/Kconfig"
1665 source "lib/Kconfig"
projects / deliverable / linux.git / blob