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)
28 config GENERIC_LOCKBREAK
34 config GENERIC_CMOS_UPDATE
37 config CLOCKSOURCE_WATCHDOG
40 config GENERIC_CLOCKEVENTS
43 config GENERIC_CLOCKEVENTS_BROADCAST
45 depends on X86_64 || (X86_32 && X86_LOCAL_APIC)
47 config LOCKDEP_SUPPORT
50 config STACKTRACE_SUPPORT
53 config HAVE_LATENCYTOP_SUPPORT
56 config SEMAPHORE_SLEEPERS
59 config FAST_CMPXCHG_LOCAL
72 config GENERIC_ISA_DMA
82 config GENERIC_HWEIGHT
88 config ARCH_MAY_HAVE_PC_FDC
94 config RWSEM_GENERIC_SPINLOCK
97 config RWSEM_XCHGADD_ALGORITHM
100 config ARCH_HAS_ILOG2_U32
103 config ARCH_HAS_ILOG2_U64
106 config ARCH_HAS_CPU_IDLE_WAIT
109 config GENERIC_CALIBRATE_DELAY
112 config GENERIC_TIME_VSYSCALL
116 config ARCH_HAS_CPU_RELAX
119 config HAVE_SETUP_PER_CPU_AREA
120 def_bool X86_64 || (X86_SMP && !X86_VOYAGER)
122 config ARCH_HIBERNATION_POSSIBLE
124 depends on !SMP || !X86_VOYAGER
126 config ARCH_SUSPEND_POSSIBLE
128 depends on !X86_VOYAGER
134 config ARCH_POPULATES_NODE_MAP
141 config ARCH_SUPPORTS_AOUT
144 # Use the generic interrupt handling code in kernel/irq/:
145 config GENERIC_HARDIRQS
149 config GENERIC_IRQ_PROBE
153 config GENERIC_PENDING_IRQ
155 depends on GENERIC_HARDIRQS && SMP
160 depends on SMP && ((X86_32 && !X86_VOYAGER) || X86_64)
165 depends on X86_32 && SMP
169 depends on X86_64 && SMP
174 depends on (X86_32 && !(X86_VISWS || X86_VOYAGER)) || X86_64
177 config X86_BIOS_REBOOT
179 depends on X86_32 && !(X86_VISWS || X86_VOYAGER)
182 config X86_TRAMPOLINE
184 depends on X86_SMP || (X86_VOYAGER && SMP)
189 source "init/Kconfig"
191 menu "Processor type and features"
193 source "kernel/time/Kconfig"
196 bool "Symmetric multi-processing support"
198 This enables support for systems with more than one CPU. If you have
199 a system with only one CPU, like most personal computers, say N. If
200 you have a system with more than one CPU, say Y.
202 If you say N here, the kernel will run on single and multiprocessor
203 machines, but will use only one CPU of a multiprocessor machine. If
204 you say Y here, the kernel will run on many, but not all,
205 singleprocessor machines. On a singleprocessor machine, the kernel
206 will run faster if you say N here.
208 Note that if you say Y here and choose architecture "586" or
209 "Pentium" under "Processor family", the kernel will not work on 486
210 architectures. Similarly, multiprocessor kernels for the "PPro"
211 architecture may not work on all Pentium based boards.
213 People using multiprocessor machines who say Y here should also say
214 Y to "Enhanced Real Time Clock Support", below. The "Advanced Power
215 Management" code will be disabled if you say Y here.
217 See also <file:Documentation/i386/IO-APIC.txt>,
218 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
219 <http://www.tldp.org/docs.html#howto>.
221 If you don't know what to do here, say N.
224 prompt "Subarchitecture Type"
230 Choose this option if your computer is a standard PC or compatible.
236 Select this for an AMD Elan processor.
238 Do not use this option for K6/Athlon/Opteron processors!
240 If unsure, choose "PC-compatible" instead.
244 depends on X86_32 && (SMP || BROKEN)
246 Voyager is an MCA-based 32-way capable SMP architecture proprietary
247 to NCR Corp. Machine classes 345x/35xx/4100/51xx are Voyager-based.
251 If you do not specifically know you have a Voyager based machine,
252 say N here, otherwise the kernel you build will not be bootable.
255 bool "NUMAQ (IBM/Sequent)"
256 depends on SMP && X86_32
259 This option is used for getting Linux to run on a (IBM/Sequent) NUMA
260 multiquad box. This changes the way that processors are bootstrapped,
261 and uses Clustered Logical APIC addressing mode instead of Flat Logical.
262 You will need a new lynxer.elf file to flash your firmware with - send
263 email to <Martin.Bligh@us.ibm.com>.
266 bool "Summit/EXA (IBM x440)"
267 depends on X86_32 && SMP
269 This option is needed for IBM systems that use the Summit/EXA chipset.
270 In particular, it is needed for the x440.
272 If you don't have one of these computers, you should say N here.
273 If you want to build a NUMA kernel, you must select ACPI.
276 bool "Support for other sub-arch SMP systems with more than 8 CPUs"
277 depends on X86_32 && SMP
279 This option is needed for the systems that have more than 8 CPUs
280 and if the system is not of any sub-arch type above.
282 If you don't have such a system, you should say N here.
285 bool "SGI 320/540 (Visual Workstation)"
288 The SGI Visual Workstation series is an IA32-based workstation
289 based on SGI systems chips with some legacy PC hardware attached.
291 Say Y here to create a kernel to run on the SGI 320 or 540.
293 A kernel compiled for the Visual Workstation will not run on PCs
294 and vice versa. See <file:Documentation/sgi-visws.txt> for details.
296 config X86_GENERICARCH
297 bool "Generic architecture (Summit, bigsmp, ES7000, default)"
300 This option compiles in the Summit, bigsmp, ES7000, default subarchitectures.
301 It is intended for a generic binary kernel.
302 If you want a NUMA kernel, select ACPI. We need SRAT for NUMA.
305 bool "Support for Unisys ES7000 IA32 series"
306 depends on X86_32 && SMP
308 Support for Unisys ES7000 systems. Say 'Y' here if this kernel is
309 supposed to run on an IA32-based Unisys ES7000 system.
310 Only choose this option if you have such a system, otherwise you
314 bool "RDC R-321x SoC"
317 select X86_REBOOTFIXUPS
322 This option is needed for RDC R-321x system-on-chip, also known
324 If you don't have one of these chips, you should say N here.
327 bool "Support for ScaleMP vSMP"
331 Support for ScaleMP vSMP systems. Say 'Y' here if this kernel is
332 supposed to run on these EM64T-based machines. Only choose this option
333 if you have one of these machines.
337 config SCHED_NO_NO_OMIT_FRAME_POINTER
339 prompt "Single-depth WCHAN output"
342 Calculate simpler /proc/<PID>/wchan values. If this option
343 is disabled then wchan values will recurse back to the
344 caller function. This provides more accurate wchan values,
345 at the expense of slightly more scheduling overhead.
347 If in doubt, say "Y".
349 menuconfig PARAVIRT_GUEST
350 bool "Paravirtualized guest support"
352 Say Y here to get to see options related to running Linux under
353 various hypervisors. This option alone does not add any kernel code.
355 If you say N, all options in this submenu will be skipped and disabled.
359 source "arch/x86/xen/Kconfig"
362 bool "VMI Guest support"
365 depends on !(X86_VISWS || X86_VOYAGER)
367 VMI provides a paravirtualized interface to the VMware ESX server
368 (it could be used by other hypervisors in theory too, but is not
369 at the moment), by linking the kernel to a GPL-ed ROM module
370 provided by the hypervisor.
372 source "arch/x86/lguest/Kconfig"
375 bool "Enable paravirtualization code"
376 depends on !(X86_VISWS || X86_VOYAGER)
378 This changes the kernel so it can modify itself when it is run
379 under a hypervisor, potentially improving performance significantly
380 over full virtualization. However, when run without a hypervisor
381 the kernel is theoretically slower and slightly larger.
385 config MEMTEST_BOOTPARAM
386 bool "Memtest boot parameter"
390 This option adds a kernel parameter 'memtest', which allows memtest
391 to be disabled at boot. If this option is selected, memtest
392 functionality can be disabled with memtest=0 on the kernel
393 command line. The purpose of this option is to allow a single
394 kernel image to be distributed with memtest built in, but not
397 If you are unsure how to answer this question, answer Y.
399 config MEMTEST_BOOTPARAM_VALUE
400 int "Memtest boot parameter default value (0-4)"
401 depends on MEMTEST_BOOTPARAM
405 This option sets the default value for the kernel parameter
406 'memtest', which allows memtest to be disabled at boot. If this
407 option is set to 0 (zero), the memtest kernel parameter will
408 default to 0, disabling memtest at bootup. If this option is
409 set to 4, the memtest kernel parameter will default to 4,
410 enabling memtest at bootup, and use that as pattern number.
412 If you are unsure how to answer this question, answer 0.
416 depends on X86_32 && ACPI && NUMA && (X86_SUMMIT || X86_GENERICARCH)
419 config HAVE_ARCH_PARSE_SRAT
423 config X86_SUMMIT_NUMA
425 depends on X86_32 && NUMA && (X86_SUMMIT || X86_GENERICARCH)
427 config X86_CYCLONE_TIMER
429 depends on X86_32 && X86_SUMMIT || X86_GENERICARCH
431 config ES7000_CLUSTERED_APIC
433 depends on SMP && X86_ES7000 && MPENTIUMIII
435 source "arch/x86/Kconfig.cpu"
439 prompt "HPET Timer Support" if X86_32
441 Use the IA-PC HPET (High Precision Event Timer) to manage
442 time in preference to the PIT and RTC, if a HPET is
444 HPET is the next generation timer replacing legacy 8254s.
445 The HPET provides a stable time base on SMP
446 systems, unlike the TSC, but it is more expensive to access,
447 as it is off-chip. You can find the HPET spec at
448 <http://www.intel.com/hardwaredesign/hpetspec.htm>.
450 You can safely choose Y here. However, HPET will only be
451 activated if the platform and the BIOS support this feature.
452 Otherwise the 8254 will be used for timing services.
454 Choose N to continue using the legacy 8254 timer.
456 config HPET_EMULATE_RTC
458 depends on HPET_TIMER && (RTC=y || RTC=m || RTC_DRV_CMOS=m || RTC_DRV_CMOS=y)
460 # Mark as embedded because too many people got it wrong.
461 # The code disables itself when not needed.
463 bool "GART IOMMU support" if EMBEDDED
467 depends on X86_64 && PCI
469 Support for full DMA access of devices with 32bit memory access only
470 on systems with more than 3GB. This is usually needed for USB,
471 sound, many IDE/SATA chipsets and some other devices.
472 Provides a driver for the AMD Athlon64/Opteron/Turion/Sempron GART
473 based hardware IOMMU and a software bounce buffer based IOMMU used
474 on Intel systems and as fallback.
475 The code is only active when needed (enough memory and limited
476 device) unless CONFIG_IOMMU_DEBUG or iommu=force is specified
480 bool "IBM Calgary IOMMU support"
482 depends on X86_64 && PCI && EXPERIMENTAL
484 Support for hardware IOMMUs in IBM's xSeries x366 and x460
485 systems. Needed to run systems with more than 3GB of memory
486 properly with 32-bit PCI devices that do not support DAC
487 (Double Address Cycle). Calgary also supports bus level
488 isolation, where all DMAs pass through the IOMMU. This
489 prevents them from going anywhere except their intended
490 destination. This catches hard-to-find kernel bugs and
491 mis-behaving drivers and devices that do not use the DMA-API
492 properly to set up their DMA buffers. The IOMMU can be
493 turned off at boot time with the iommu=off parameter.
494 Normally the kernel will make the right choice by itself.
497 config CALGARY_IOMMU_ENABLED_BY_DEFAULT
499 prompt "Should Calgary be enabled by default?"
500 depends on CALGARY_IOMMU
502 Should Calgary be enabled by default? if you choose 'y', Calgary
503 will be used (if it exists). If you choose 'n', Calgary will not be
504 used even if it exists. If you choose 'n' and would like to use
505 Calgary anyway, pass 'iommu=calgary' on the kernel command line.
509 def_bool (CALGARY_IOMMU || GART_IOMMU)
511 # need this always selected by IOMMU for the VIA workaround
515 Support for software bounce buffers used on x86-64 systems
516 which don't have a hardware IOMMU (e.g. the current generation
517 of Intel's x86-64 CPUs). Using this PCI devices which can only
518 access 32-bits of memory can be used on systems with more than
519 3 GB of memory. If unsure, say Y.
523 int "Maximum number of CPUs (2-255)"
526 default "32" if X86_NUMAQ || X86_SUMMIT || X86_BIGSMP || X86_ES7000
529 This allows you to specify the maximum number of CPUs which this
530 kernel will support. The maximum supported value is 255 and the
531 minimum value which makes sense is 2.
533 This is purely to save memory - each supported CPU adds
534 approximately eight kilobytes to the kernel image.
537 bool "SMT (Hyperthreading) scheduler support"
540 SMT scheduler support improves the CPU scheduler's decision making
541 when dealing with Intel Pentium 4 chips with HyperThreading at a
542 cost of slightly increased overhead in some places. If unsure say
547 prompt "Multi-core scheduler support"
550 Multi-core scheduler support improves the CPU scheduler's decision
551 making when dealing with multi-core CPU chips at a cost of slightly
552 increased overhead in some places. If unsure say N here.
554 source "kernel/Kconfig.preempt"
557 bool "Local APIC support on uniprocessors"
558 depends on X86_32 && !SMP && !(X86_VISWS || X86_VOYAGER || X86_GENERICARCH)
560 A local APIC (Advanced Programmable Interrupt Controller) is an
561 integrated interrupt controller in the CPU. If you have a single-CPU
562 system which has a processor with a local APIC, you can say Y here to
563 enable and use it. If you say Y here even though your machine doesn't
564 have a local APIC, then the kernel will still run with no slowdown at
565 all. The local APIC supports CPU-generated self-interrupts (timer,
566 performance counters), and the NMI watchdog which detects hard
570 bool "IO-APIC support on uniprocessors"
571 depends on X86_UP_APIC
573 An IO-APIC (I/O Advanced Programmable Interrupt Controller) is an
574 SMP-capable replacement for PC-style interrupt controllers. Most
575 SMP systems and many recent uniprocessor systems have one.
577 If you have a single-CPU system with an IO-APIC, you can say Y here
578 to use it. If you say Y here even though your machine doesn't have
579 an IO-APIC, then the kernel will still run with no slowdown at all.
581 config X86_LOCAL_APIC
583 depends on X86_64 || (X86_32 && (X86_UP_APIC || ((X86_VISWS || SMP) && !X86_VOYAGER) || X86_GENERICARCH))
587 depends on X86_64 || (X86_32 && (X86_UP_IOAPIC || (SMP && !(X86_VISWS || X86_VOYAGER)) || X86_GENERICARCH))
589 config X86_VISWS_APIC
591 depends on X86_32 && X86_VISWS
594 bool "Machine Check Exception"
595 depends on !X86_VOYAGER
597 Machine Check Exception support allows the processor to notify the
598 kernel if it detects a problem (e.g. overheating, component failure).
599 The action the kernel takes depends on the severity of the problem,
600 ranging from a warning message on the console, to halting the machine.
601 Your processor must be a Pentium or newer to support this - check the
602 flags in /proc/cpuinfo for mce. Note that some older Pentium systems
603 have a design flaw which leads to false MCE events - hence MCE is
604 disabled on all P5 processors, unless explicitly enabled with "mce"
605 as a boot argument. Similarly, if MCE is built in and creates a
606 problem on some new non-standard machine, you can boot with "nomce"
607 to disable it. MCE support simply ignores non-MCE processors like
608 the 386 and 486, so nearly everyone can say Y here.
612 prompt "Intel MCE features"
613 depends on X86_64 && X86_MCE && X86_LOCAL_APIC
615 Additional support for intel specific MCE features such as
620 prompt "AMD MCE features"
621 depends on X86_64 && X86_MCE && X86_LOCAL_APIC
623 Additional support for AMD specific MCE features such as
624 the DRAM Error Threshold.
626 config X86_MCE_NONFATAL
627 tristate "Check for non-fatal errors on AMD Athlon/Duron / Intel Pentium 4"
628 depends on X86_32 && X86_MCE
630 Enabling this feature starts a timer that triggers every 5 seconds which
631 will look at the machine check registers to see if anything happened.
632 Non-fatal problems automatically get corrected (but still logged).
633 Disable this if you don't want to see these messages.
634 Seeing the messages this option prints out may be indicative of dying
635 or out-of-spec (ie, overclocked) hardware.
636 This option only does something on certain CPUs.
637 (AMD Athlon/Duron and Intel Pentium 4)
639 config X86_MCE_P4THERMAL
640 bool "check for P4 thermal throttling interrupt."
641 depends on X86_32 && X86_MCE && (X86_UP_APIC || SMP) && !X86_VISWS
643 Enabling this feature will cause a message to be printed when the P4
644 enters thermal throttling.
647 bool "Enable VM86 support" if EMBEDDED
651 This option is required by programs like DOSEMU to run 16-bit legacy
652 code on X86 processors. It also may be needed by software like
653 XFree86 to initialize some video cards via BIOS. Disabling this
654 option saves about 6k.
657 tristate "Toshiba Laptop support"
660 This adds a driver to safely access the System Management Mode of
661 the CPU on Toshiba portables with a genuine Toshiba BIOS. It does
662 not work on models with a Phoenix BIOS. The System Management Mode
663 is used to set the BIOS and power saving options on Toshiba portables.
665 For information on utilities to make use of this driver see the
666 Toshiba Linux utilities web site at:
667 <http://www.buzzard.org.uk/toshiba/>.
669 Say Y if you intend to run this kernel on a Toshiba portable.
673 tristate "Dell laptop support"
675 This adds a driver to safely access the System Management Mode
676 of the CPU on the Dell Inspiron 8000. The System Management Mode
677 is used to read cpu temperature and cooling fan status and to
678 control the fans on the I8K portables.
680 This driver has been tested only on the Inspiron 8000 but it may
681 also work with other Dell laptops. You can force loading on other
682 models by passing the parameter `force=1' to the module. Use at
685 For information on utilities to make use of this driver see the
686 I8K Linux utilities web site at:
687 <http://people.debian.org/~dz/i8k/>
689 Say Y if you intend to run this kernel on a Dell Inspiron 8000.
692 config X86_REBOOTFIXUPS
694 prompt "Enable X86 board specific fixups for reboot"
695 depends on X86_32 && X86
697 This enables chipset and/or board specific fixups to be done
698 in order to get reboot to work correctly. This is only needed on
699 some combinations of hardware and BIOS. The symptom, for which
700 this config is intended, is when reboot ends with a stalled/hung
703 Currently, the only fixup is for the Geode machines using
704 CS5530A and CS5536 chipsets and the RDC R-321x SoC.
706 Say Y if you want to enable the fixup. Currently, it's safe to
707 enable this option even if you don't need it.
711 tristate "/dev/cpu/microcode - Intel IA32 CPU microcode support"
714 If you say Y here, you will be able to update the microcode on
715 Intel processors in the IA32 family, e.g. Pentium Pro, Pentium II,
716 Pentium III, Pentium 4, Xeon etc. You will obviously need the
717 actual microcode binary data itself which is not shipped with the
720 For latest news and information on obtaining all the required
721 ingredients for this driver, check:
722 <http://www.urbanmyth.org/microcode/>.
724 To compile this driver as a module, choose M here: the
725 module will be called microcode.
727 config MICROCODE_OLD_INTERFACE
732 tristate "/dev/cpu/*/msr - Model-specific register support"
734 This device gives privileged processes access to the x86
735 Model-Specific Registers (MSRs). It is a character device with
736 major 202 and minors 0 to 31 for /dev/cpu/0/msr to /dev/cpu/31/msr.
737 MSR accesses are directed to a specific CPU on multi-processor
741 tristate "/dev/cpu/*/cpuid - CPU information support"
743 This device gives processes access to the x86 CPUID instruction to
744 be executed on a specific processor. It is a character device
745 with major 203 and minors 0 to 31 for /dev/cpu/0/cpuid to
749 prompt "High Memory Support"
750 default HIGHMEM4G if !X86_NUMAQ
751 default HIGHMEM64G if X86_NUMAQ
756 depends on !X86_NUMAQ
758 Linux can use up to 64 Gigabytes of physical memory on x86 systems.
759 However, the address space of 32-bit x86 processors is only 4
760 Gigabytes large. That means that, if you have a large amount of
761 physical memory, not all of it can be "permanently mapped" by the
762 kernel. The physical memory that's not permanently mapped is called
765 If you are compiling a kernel which will never run on a machine with
766 more than 1 Gigabyte total physical RAM, answer "off" here (default
767 choice and suitable for most users). This will result in a "3GB/1GB"
768 split: 3GB are mapped so that each process sees a 3GB virtual memory
769 space and the remaining part of the 4GB virtual memory space is used
770 by the kernel to permanently map as much physical memory as
773 If the machine has between 1 and 4 Gigabytes physical RAM, then
776 If more than 4 Gigabytes is used then answer "64GB" here. This
777 selection turns Intel PAE (Physical Address Extension) mode on.
778 PAE implements 3-level paging on IA32 processors. PAE is fully
779 supported by Linux, PAE mode is implemented on all recent Intel
780 processors (Pentium Pro and better). NOTE: If you say "64GB" here,
781 then the kernel will not boot on CPUs that don't support PAE!
783 The actual amount of total physical memory will either be
784 auto detected or can be forced by using a kernel command line option
785 such as "mem=256M". (Try "man bootparam" or see the documentation of
786 your boot loader (lilo or loadlin) about how to pass options to the
787 kernel at boot time.)
789 If unsure, say "off".
793 depends on !X86_NUMAQ
795 Select this if you have a 32-bit processor and between 1 and 4
796 gigabytes of physical RAM.
800 depends on !M386 && !M486
803 Select this if you have a 32-bit processor and more than 4
804 gigabytes of physical RAM.
809 depends on EXPERIMENTAL
810 prompt "Memory split" if EMBEDDED
814 Select the desired split between kernel and user memory.
816 If the address range available to the kernel is less than the
817 physical memory installed, the remaining memory will be available
818 as "high memory". Accessing high memory is a little more costly
819 than low memory, as it needs to be mapped into the kernel first.
820 Note that increasing the kernel address space limits the range
821 available to user programs, making the address space there
822 tighter. Selecting anything other than the default 3G/1G split
823 will also likely make your kernel incompatible with binary-only
826 If you are not absolutely sure what you are doing, leave this
830 bool "3G/1G user/kernel split"
831 config VMSPLIT_3G_OPT
833 bool "3G/1G user/kernel split (for full 1G low memory)"
835 bool "2G/2G user/kernel split"
836 config VMSPLIT_2G_OPT
838 bool "2G/2G user/kernel split (for full 2G low memory)"
840 bool "1G/3G user/kernel split"
845 default 0xB0000000 if VMSPLIT_3G_OPT
846 default 0x80000000 if VMSPLIT_2G
847 default 0x78000000 if VMSPLIT_2G_OPT
848 default 0x40000000 if VMSPLIT_1G
854 depends on X86_32 && (HIGHMEM64G || HIGHMEM4G)
858 prompt "PAE (Physical Address Extension) Support"
859 depends on X86_32 && !HIGHMEM4G
860 select RESOURCES_64BIT
862 PAE is required for NX support, and furthermore enables
863 larger swapspace support for non-overcommit purposes. It
864 has the cost of more pagetable lookup overhead, and also
865 consumes more pagetable space per process.
867 # Common NUMA Features
869 bool "Numa Memory Allocation and Scheduler Support (EXPERIMENTAL)"
871 depends on X86_64 || (X86_32 && HIGHMEM64G && (X86_NUMAQ || (X86_SUMMIT || X86_GENERICARCH) && ACPI) && EXPERIMENTAL)
873 default y if (X86_NUMAQ || X86_SUMMIT)
875 Enable NUMA (Non Uniform Memory Access) support.
876 The kernel will try to allocate memory used by a CPU on the
877 local memory controller of the CPU and add some more
878 NUMA awareness to the kernel.
880 For i386 this is currently highly experimental and should be only
881 used for kernel development. It might also cause boot failures.
882 For x86_64 this is recommended on all multiprocessor Opteron systems.
883 If the system is EM64T, you should say N unless your system is
886 comment "NUMA (Summit) requires SMP, 64GB highmem support, ACPI"
887 depends on X86_32 && X86_SUMMIT && (!HIGHMEM64G || !ACPI)
891 prompt "Old style AMD Opteron NUMA detection"
892 depends on X86_64 && NUMA && PCI
894 Enable K8 NUMA node topology detection. You should say Y here if
895 you have a multi processor AMD K8 system. This uses an old
896 method to read the NUMA configuration directly from the builtin
897 Northbridge of Opteron. It is recommended to use X86_64_ACPI_NUMA
898 instead, which also takes priority if both are compiled in.
900 config X86_64_ACPI_NUMA
902 prompt "ACPI NUMA detection"
903 depends on X86_64 && NUMA && ACPI && PCI
906 Enable ACPI SRAT based node topology detection.
909 bool "NUMA emulation"
910 depends on X86_64 && NUMA
912 Enable NUMA emulation. A flat machine will be split
913 into virtual nodes when booted with "numa=fake=N", where N is the
914 number of nodes. This is only useful for debugging.
917 int "Max num nodes shift(1-15)"
919 default "6" if X86_64
920 default "4" if X86_NUMAQ
922 depends on NEED_MULTIPLE_NODES
924 config HAVE_ARCH_BOOTMEM_NODE
926 depends on X86_32 && NUMA
928 config ARCH_HAVE_MEMORY_PRESENT
930 depends on X86_32 && DISCONTIGMEM
932 config NEED_NODE_MEMMAP_SIZE
934 depends on X86_32 && (DISCONTIGMEM || SPARSEMEM)
936 config HAVE_ARCH_ALLOC_REMAP
938 depends on X86_32 && NUMA
940 config ARCH_FLATMEM_ENABLE
942 depends on X86_32 && ARCH_SELECT_MEMORY_MODEL && X86_PC && !NUMA
944 config ARCH_DISCONTIGMEM_ENABLE
946 depends on NUMA && X86_32
948 config ARCH_DISCONTIGMEM_DEFAULT
950 depends on NUMA && X86_32
952 config ARCH_SPARSEMEM_DEFAULT
956 config ARCH_SPARSEMEM_ENABLE
958 depends on X86_64 || NUMA || (EXPERIMENTAL && X86_PC)
959 select SPARSEMEM_STATIC if X86_32
960 select SPARSEMEM_VMEMMAP_ENABLE if X86_64
962 config ARCH_SELECT_MEMORY_MODEL
964 depends on ARCH_SPARSEMEM_ENABLE
966 config ARCH_MEMORY_PROBE
968 depends on MEMORY_HOTPLUG
973 bool "Allocate 3rd-level pagetables from highmem"
974 depends on X86_32 && (HIGHMEM4G || HIGHMEM64G)
976 The VM uses one page table entry for each page of physical memory.
977 For systems with a lot of RAM, this can be wasteful of precious
978 low memory. Setting this option will put user-space page table
979 entries in high memory.
981 config MATH_EMULATION
983 prompt "Math emulation" if X86_32
985 Linux can emulate a math coprocessor (used for floating point
986 operations) if you don't have one. 486DX and Pentium processors have
987 a math coprocessor built in, 486SX and 386 do not, unless you added
988 a 487DX or 387, respectively. (The messages during boot time can
989 give you some hints here ["man dmesg"].) Everyone needs either a
990 coprocessor or this emulation.
992 If you don't have a math coprocessor, you need to say Y here; if you
993 say Y here even though you have a coprocessor, the coprocessor will
994 be used nevertheless. (This behavior can be changed with the kernel
995 command line option "no387", which comes handy if your coprocessor
996 is broken. Try "man bootparam" or see the documentation of your boot
997 loader (lilo or loadlin) about how to pass options to the kernel at
998 boot time.) This means that it is a good idea to say Y here if you
999 intend to use this kernel on different machines.
1001 More information about the internals of the Linux math coprocessor
1002 emulation can be found in <file:arch/x86/math-emu/README>.
1004 If you are not sure, say Y; apart from resulting in a 66 KB bigger
1005 kernel, it won't hurt.
1008 bool "MTRR (Memory Type Range Register) support"
1010 On Intel P6 family processors (Pentium Pro, Pentium II and later)
1011 the Memory Type Range Registers (MTRRs) may be used to control
1012 processor access to memory ranges. This is most useful if you have
1013 a video (VGA) card on a PCI or AGP bus. Enabling write-combining
1014 allows bus write transfers to be combined into a larger transfer
1015 before bursting over the PCI/AGP bus. This can increase performance
1016 of image write operations 2.5 times or more. Saying Y here creates a
1017 /proc/mtrr file which may be used to manipulate your processor's
1018 MTRRs. Typically the X server should use this.
1020 This code has a reasonably generic interface so that similar
1021 control registers on other processors can be easily supported
1024 The Cyrix 6x86, 6x86MX and M II processors have Address Range
1025 Registers (ARRs) which provide a similar functionality to MTRRs. For
1026 these, the ARRs are used to emulate the MTRRs.
1027 The AMD K6-2 (stepping 8 and above) and K6-3 processors have two
1028 MTRRs. The Centaur C6 (WinChip) has 8 MCRs, allowing
1029 write-combining. All of these processors are supported by this code
1030 and it makes sense to say Y here if you have one of them.
1032 Saying Y here also fixes a problem with buggy SMP BIOSes which only
1033 set the MTRRs for the boot CPU and not for the secondary CPUs. This
1034 can lead to all sorts of problems, so it's good to say Y here.
1036 You can safely say Y even if your machine doesn't have MTRRs, you'll
1037 just add about 9 KB to your kernel.
1039 See <file:Documentation/mtrr.txt> for more information.
1043 prompt "x86 PAT support"
1044 depends on MTRR && NONPROMISC_DEVMEM
1046 Use PAT attributes to setup page level cache control.
1048 PATs are the modern equivalents of MTRRs and are much more
1049 flexible than MTRRs.
1051 Say N here if you see bootup problems (boot crash, boot hang,
1052 spontaneous reboots) or a non-working video driver.
1058 prompt "EFI runtime service support"
1061 This enables the kernel to use EFI runtime services that are
1062 available (such as the EFI variable services).
1064 This option is only useful on systems that have EFI firmware.
1065 In addition, you should use the latest ELILO loader available
1066 at <http://elilo.sourceforge.net> in order to take advantage
1067 of EFI runtime services. However, even with this option, the
1068 resultant kernel should continue to boot on existing non-EFI
1073 prompt "Enable kernel irq balancing"
1074 depends on X86_32 && SMP && X86_IO_APIC
1076 The default yes will allow the kernel to do irq load balancing.
1077 Saying no will keep the kernel from doing irq load balancing.
1081 prompt "Enable seccomp to safely compute untrusted bytecode"
1084 This kernel feature is useful for number crunching applications
1085 that may need to compute untrusted bytecode during their
1086 execution. By using pipes or other transports made available to
1087 the process as file descriptors supporting the read/write
1088 syscalls, it's possible to isolate those applications in
1089 their own address space using seccomp. Once seccomp is
1090 enabled via /proc/<pid>/seccomp, it cannot be disabled
1091 and the task is only allowed to execute a few safe syscalls
1092 defined by each seccomp mode.
1094 If unsure, say Y. Only embedded should say N here.
1096 config CC_STACKPROTECTOR
1097 bool "Enable -fstack-protector buffer overflow detection (EXPERIMENTAL)"
1098 depends on X86_64 && EXPERIMENTAL && BROKEN
1100 This option turns on the -fstack-protector GCC feature. This
1101 feature puts, at the beginning of critical functions, a canary
1102 value on the stack just before the return address, and validates
1103 the value just before actually returning. Stack based buffer
1104 overflows (that need to overwrite this return address) now also
1105 overwrite the canary, which gets detected and the attack is then
1106 neutralized via a kernel panic.
1108 This feature requires gcc version 4.2 or above, or a distribution
1109 gcc with the feature backported. Older versions are automatically
1110 detected and for those versions, this configuration option is ignored.
1112 config CC_STACKPROTECTOR_ALL
1113 bool "Use stack-protector for all functions"
1114 depends on CC_STACKPROTECTOR
1116 Normally, GCC only inserts the canary value protection for
1117 functions that use large-ish on-stack buffers. By enabling
1118 this option, GCC will be asked to do this for ALL functions.
1120 source kernel/Kconfig.hz
1123 bool "kexec system call"
1124 depends on X86_64 || X86_BIOS_REBOOT
1126 kexec is a system call that implements the ability to shutdown your
1127 current kernel, and to start another kernel. It is like a reboot
1128 but it is independent of the system firmware. And like a reboot
1129 you can start any kernel with it, not just Linux.
1131 The name comes from the similarity to the exec system call.
1133 It is an ongoing process to be certain the hardware in a machine
1134 is properly shutdown, so do not be surprised if this code does not
1135 initially work for you. It may help to enable device hotplugging
1136 support. As of this writing the exact hardware interface is
1137 strongly in flux, so no good recommendation can be made.
1140 bool "kernel crash dumps (EXPERIMENTAL)"
1141 depends on EXPERIMENTAL
1142 depends on X86_64 || (X86_32 && HIGHMEM)
1144 Generate crash dump after being started by kexec.
1145 This should be normally only set in special crash dump kernels
1146 which are loaded in the main kernel with kexec-tools into
1147 a specially reserved region and then later executed after
1148 a crash by kdump/kexec. The crash dump kernel must be compiled
1149 to a memory address not used by the main kernel or BIOS using
1150 PHYSICAL_START, or it must be built as a relocatable image
1151 (CONFIG_RELOCATABLE=y).
1152 For more details see Documentation/kdump/kdump.txt
1154 config PHYSICAL_START
1155 hex "Physical address where the kernel is loaded" if (EMBEDDED || CRASH_DUMP)
1156 default "0x1000000" if X86_NUMAQ
1157 default "0x200000" if X86_64
1160 This gives the physical address where the kernel is loaded.
1162 If kernel is a not relocatable (CONFIG_RELOCATABLE=n) then
1163 bzImage will decompress itself to above physical address and
1164 run from there. Otherwise, bzImage will run from the address where
1165 it has been loaded by the boot loader and will ignore above physical
1168 In normal kdump cases one does not have to set/change this option
1169 as now bzImage can be compiled as a completely relocatable image
1170 (CONFIG_RELOCATABLE=y) and be used to load and run from a different
1171 address. This option is mainly useful for the folks who don't want
1172 to use a bzImage for capturing the crash dump and want to use a
1173 vmlinux instead. vmlinux is not relocatable hence a kernel needs
1174 to be specifically compiled to run from a specific memory area
1175 (normally a reserved region) and this option comes handy.
1177 So if you are using bzImage for capturing the crash dump, leave
1178 the value here unchanged to 0x100000 and set CONFIG_RELOCATABLE=y.
1179 Otherwise if you plan to use vmlinux for capturing the crash dump
1180 change this value to start of the reserved region (Typically 16MB
1181 0x1000000). In other words, it can be set based on the "X" value as
1182 specified in the "crashkernel=YM@XM" command line boot parameter
1183 passed to the panic-ed kernel. Typically this parameter is set as
1184 crashkernel=64M@16M. Please take a look at
1185 Documentation/kdump/kdump.txt for more details about crash dumps.
1187 Usage of bzImage for capturing the crash dump is recommended as
1188 one does not have to build two kernels. Same kernel can be used
1189 as production kernel and capture kernel. Above option should have
1190 gone away after relocatable bzImage support is introduced. But it
1191 is present because there are users out there who continue to use
1192 vmlinux for dump capture. This option should go away down the
1195 Don't change this unless you know what you are doing.
1198 bool "Build a relocatable kernel (EXPERIMENTAL)"
1199 depends on EXPERIMENTAL
1201 This builds a kernel image that retains relocation information
1202 so it can be loaded someplace besides the default 1MB.
1203 The relocations tend to make the kernel binary about 10% larger,
1204 but are discarded at runtime.
1206 One use is for the kexec on panic case where the recovery kernel
1207 must live at a different physical address than the primary
1210 Note: If CONFIG_RELOCATABLE=y, then the kernel runs from the address
1211 it has been loaded at and the compile time physical address
1212 (CONFIG_PHYSICAL_START) is ignored.
1214 config PHYSICAL_ALIGN
1216 prompt "Alignment value to which kernel should be aligned" if X86_32
1217 default "0x100000" if X86_32
1218 default "0x200000" if X86_64
1219 range 0x2000 0x400000
1221 This value puts the alignment restrictions on physical address
1222 where kernel is loaded and run from. Kernel is compiled for an
1223 address which meets above alignment restriction.
1225 If bootloader loads the kernel at a non-aligned address and
1226 CONFIG_RELOCATABLE is set, kernel will move itself to nearest
1227 address aligned to above value and run from there.
1229 If bootloader loads the kernel at a non-aligned address and
1230 CONFIG_RELOCATABLE is not set, kernel will ignore the run time
1231 load address and decompress itself to the address it has been
1232 compiled for and run from there. The address for which kernel is
1233 compiled already meets above alignment restrictions. Hence the
1234 end result is that kernel runs from a physical address meeting
1235 above alignment restrictions.
1237 Don't change this unless you know what you are doing.
1240 bool "Support for suspend on SMP and hot-pluggable CPUs (EXPERIMENTAL)"
1241 depends on SMP && HOTPLUG && EXPERIMENTAL && !X86_VOYAGER
1243 Say Y here to experiment with turning CPUs off and on, and to
1244 enable suspend on SMP systems. CPUs can be controlled through
1245 /sys/devices/system/cpu.
1246 Say N if you want to disable CPU hotplug and don't need to
1251 prompt "Compat VDSO support"
1252 depends on X86_32 || IA32_EMULATION
1254 Map the 32-bit VDSO to the predictable old-style address too.
1256 Say N here if you are running a sufficiently recent glibc
1257 version (2.3.3 or later), to remove the high-mapped
1258 VDSO mapping and to exclusively use the randomized VDSO.
1264 config ARCH_ENABLE_MEMORY_HOTPLUG
1266 depends on X86_64 || (X86_32 && HIGHMEM)
1268 config HAVE_ARCH_EARLY_PFN_TO_NID
1272 menu "Power management options"
1273 depends on !X86_VOYAGER
1275 config ARCH_HIBERNATION_HEADER
1277 depends on X86_64 && HIBERNATION
1279 source "kernel/power/Kconfig"
1281 source "drivers/acpi/Kconfig"
1286 depends on APM || APM_MODULE
1289 tristate "APM (Advanced Power Management) BIOS support"
1290 depends on X86_32 && PM_SLEEP && !X86_VISWS
1292 APM is a BIOS specification for saving power using several different
1293 techniques. This is mostly useful for battery powered laptops with
1294 APM compliant BIOSes. If you say Y here, the system time will be
1295 reset after a RESUME operation, the /proc/apm device will provide
1296 battery status information, and user-space programs will receive
1297 notification of APM "events" (e.g. battery status change).
1299 If you select "Y" here, you can disable actual use of the APM
1300 BIOS by passing the "apm=off" option to the kernel at boot time.
1302 Note that the APM support is almost completely disabled for
1303 machines with more than one CPU.
1305 In order to use APM, you will need supporting software. For location
1306 and more information, read <file:Documentation/power/pm.txt> and the
1307 Battery Powered Linux mini-HOWTO, available from
1308 <http://www.tldp.org/docs.html#howto>.
1310 This driver does not spin down disk drives (see the hdparm(8)
1311 manpage ("man 8 hdparm") for that), and it doesn't turn off
1312 VESA-compliant "green" monitors.
1314 This driver does not support the TI 4000M TravelMate and the ACER
1315 486/DX4/75 because they don't have compliant BIOSes. Many "green"
1316 desktop machines also don't have compliant BIOSes, and this driver
1317 may cause those machines to panic during the boot phase.
1319 Generally, if you don't have a battery in your machine, there isn't
1320 much point in using this driver and you should say N. If you get
1321 random kernel OOPSes or reboots that don't seem to be related to
1322 anything, try disabling/enabling this option (or disabling/enabling
1325 Some other things you should try when experiencing seemingly random,
1328 1) make sure that you have enough swap space and that it is
1330 2) pass the "no-hlt" option to the kernel
1331 3) switch on floating point emulation in the kernel and pass
1332 the "no387" option to the kernel
1333 4) pass the "floppy=nodma" option to the kernel
1334 5) pass the "mem=4M" option to the kernel (thereby disabling
1335 all but the first 4 MB of RAM)
1336 6) make sure that the CPU is not over clocked.
1337 7) read the sig11 FAQ at <http://www.bitwizard.nl/sig11/>
1338 8) disable the cache from your BIOS settings
1339 9) install a fan for the video card or exchange video RAM
1340 10) install a better fan for the CPU
1341 11) exchange RAM chips
1342 12) exchange the motherboard.
1344 To compile this driver as a module, choose M here: the
1345 module will be called apm.
1349 config APM_IGNORE_USER_SUSPEND
1350 bool "Ignore USER SUSPEND"
1352 This option will ignore USER SUSPEND requests. On machines with a
1353 compliant APM BIOS, you want to say N. However, on the NEC Versa M
1354 series notebooks, it is necessary to say Y because of a BIOS bug.
1356 config APM_DO_ENABLE
1357 bool "Enable PM at boot time"
1359 Enable APM features at boot time. From page 36 of the APM BIOS
1360 specification: "When disabled, the APM BIOS does not automatically
1361 power manage devices, enter the Standby State, enter the Suspend
1362 State, or take power saving steps in response to CPU Idle calls."
1363 This driver will make CPU Idle calls when Linux is idle (unless this
1364 feature is turned off -- see "Do CPU IDLE calls", below). This
1365 should always save battery power, but more complicated APM features
1366 will be dependent on your BIOS implementation. You may need to turn
1367 this option off if your computer hangs at boot time when using APM
1368 support, or if it beeps continuously instead of suspending. Turn
1369 this off if you have a NEC UltraLite Versa 33/C or a Toshiba
1370 T400CDT. This is off by default since most machines do fine without
1374 bool "Make CPU Idle calls when idle"
1376 Enable calls to APM CPU Idle/CPU Busy inside the kernel's idle loop.
1377 On some machines, this can activate improved power savings, such as
1378 a slowed CPU clock rate, when the machine is idle. These idle calls
1379 are made after the idle loop has run for some length of time (e.g.,
1380 333 mS). On some machines, this will cause a hang at boot time or
1381 whenever the CPU becomes idle. (On machines with more than one CPU,
1382 this option does nothing.)
1384 config APM_DISPLAY_BLANK
1385 bool "Enable console blanking using APM"
1387 Enable console blanking using the APM. Some laptops can use this to
1388 turn off the LCD backlight when the screen blanker of the Linux
1389 virtual console blanks the screen. Note that this is only used by
1390 the virtual console screen blanker, and won't turn off the backlight
1391 when using the X Window system. This also doesn't have anything to
1392 do with your VESA-compliant power-saving monitor. Further, this
1393 option doesn't work for all laptops -- it might not turn off your
1394 backlight at all, or it might print a lot of errors to the console,
1395 especially if you are using gpm.
1397 config APM_ALLOW_INTS
1398 bool "Allow interrupts during APM BIOS calls"
1400 Normally we disable external interrupts while we are making calls to
1401 the APM BIOS as a measure to lessen the effects of a badly behaving
1402 BIOS implementation. The BIOS should reenable interrupts if it
1403 needs to. Unfortunately, some BIOSes do not -- especially those in
1404 many of the newer IBM Thinkpads. If you experience hangs when you
1405 suspend, try setting this to Y. Otherwise, say N.
1407 config APM_REAL_MODE_POWER_OFF
1408 bool "Use real mode APM BIOS call to power off"
1410 Use real mode APM BIOS calls to switch off the computer. This is
1411 a work-around for a number of buggy BIOSes. Switch this option on if
1412 your computer crashes instead of powering off properly.
1416 source "arch/x86/kernel/cpu/cpufreq/Kconfig"
1418 source "drivers/cpuidle/Kconfig"
1423 menu "Bus options (PCI etc.)"
1426 bool "PCI support" if !X86_VISWS && !X86_VSMP
1427 depends on !X86_VOYAGER
1429 select ARCH_SUPPORTS_MSI if (X86_LOCAL_APIC && X86_IO_APIC)
1431 Find out whether you have a PCI motherboard. PCI is the name of a
1432 bus system, i.e. the way the CPU talks to the other stuff inside
1433 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
1434 VESA. If you have PCI, say Y, otherwise N.
1437 prompt "PCI access mode"
1438 depends on X86_32 && PCI && !X86_VISWS
1441 On PCI systems, the BIOS can be used to detect the PCI devices and
1442 determine their configuration. However, some old PCI motherboards
1443 have BIOS bugs and may crash if this is done. Also, some embedded
1444 PCI-based systems don't have any BIOS at all. Linux can also try to
1445 detect the PCI hardware directly without using the BIOS.
1447 With this option, you can specify how Linux should detect the
1448 PCI devices. If you choose "BIOS", the BIOS will be used,
1449 if you choose "Direct", the BIOS won't be used, and if you
1450 choose "MMConfig", then PCI Express MMCONFIG will be used.
1451 If you choose "Any", the kernel will try MMCONFIG, then the
1452 direct access method and falls back to the BIOS if that doesn't
1453 work. If unsure, go with the default, which is "Any".
1458 config PCI_GOMMCONFIG
1471 depends on X86_32 && !X86_VISWS && PCI && (PCI_GOBIOS || PCI_GOANY)
1473 # x86-64 doesn't support PCI BIOS access from long mode so always go direct.
1476 depends on PCI && (X86_64 || (PCI_GODIRECT || PCI_GOANY) || X86_VISWS)
1480 depends on X86_32 && PCI && ACPI && (PCI_GOMMCONFIG || PCI_GOANY)
1487 bool "Support mmconfig PCI config space access"
1488 depends on X86_64 && PCI && ACPI
1491 bool "Support for DMA Remapping Devices (EXPERIMENTAL)"
1492 depends on X86_64 && PCI_MSI && ACPI && EXPERIMENTAL
1494 DMA remapping (DMAR) devices support enables independent address
1495 translations for Direct Memory Access (DMA) from devices.
1496 These DMA remapping devices are reported via ACPI tables
1497 and include PCI device scope covered by these DMA
1502 prompt "Support for Graphics workaround"
1505 Current Graphics drivers tend to use physical address
1506 for DMA and avoid using DMA APIs. Setting this config
1507 option permits the IOMMU driver to set a unity map for
1508 all the OS-visible memory. Hence the driver can continue
1509 to use physical addresses for DMA.
1511 config DMAR_FLOPPY_WA
1515 Floppy disk drivers are know to bypass DMA API calls
1516 thereby failing to work when IOMMU is enabled. This
1517 workaround will setup a 1:1 mapping for the first
1518 16M to make floppy (an ISA device) work.
1520 source "drivers/pci/pcie/Kconfig"
1522 source "drivers/pci/Kconfig"
1524 # x86_64 have no ISA slots, but do have ISA-style DMA.
1532 depends on !(X86_VOYAGER || X86_VISWS)
1534 Find out whether you have ISA slots on your motherboard. ISA is the
1535 name of a bus system, i.e. the way the CPU talks to the other stuff
1536 inside your box. Other bus systems are PCI, EISA, MicroChannel
1537 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
1538 newer boards don't support it. If you have ISA, say Y, otherwise N.
1544 The Extended Industry Standard Architecture (EISA) bus was
1545 developed as an open alternative to the IBM MicroChannel bus.
1547 The EISA bus provided some of the features of the IBM MicroChannel
1548 bus while maintaining backward compatibility with cards made for
1549 the older ISA bus. The EISA bus saw limited use between 1988 and
1550 1995 when it was made obsolete by the PCI bus.
1552 Say Y here if you are building a kernel for an EISA-based machine.
1556 source "drivers/eisa/Kconfig"
1559 bool "MCA support" if !(X86_VISWS || X86_VOYAGER)
1560 default y if X86_VOYAGER
1562 MicroChannel Architecture is found in some IBM PS/2 machines and
1563 laptops. It is a bus system similar to PCI or ISA. See
1564 <file:Documentation/mca.txt> (and especially the web page given
1565 there) before attempting to build an MCA bus kernel.
1567 source "drivers/mca/Kconfig"
1570 tristate "NatSemi SCx200 support"
1571 depends on !X86_VOYAGER
1573 This provides basic support for National Semiconductor's
1574 (now AMD's) Geode processors. The driver probes for the
1575 PCI-IDs of several on-chip devices, so its a good dependency
1576 for other scx200_* drivers.
1578 If compiled as a module, the driver is named scx200.
1580 config SCx200HR_TIMER
1581 tristate "NatSemi SCx200 27MHz High-Resolution Timer Support"
1582 depends on SCx200 && GENERIC_TIME
1585 This driver provides a clocksource built upon the on-chip
1586 27MHz high-resolution timer. Its also a workaround for
1587 NSC Geode SC-1100's buggy TSC, which loses time when the
1588 processor goes idle (as is done by the scheduler). The
1589 other workaround is idle=poll boot option.
1591 config GEODE_MFGPT_TIMER
1593 prompt "Geode Multi-Function General Purpose Timer (MFGPT) events"
1594 depends on MGEODE_LX && GENERIC_TIME && GENERIC_CLOCKEVENTS
1596 This driver provides a clock event source based on the MFGPT
1597 timer(s) in the CS5535 and CS5536 companion chip for the geode.
1598 MFGPTs have a better resolution and max interval than the
1599 generic PIT, and are suitable for use as high-res timers.
1605 depends on AGP_AMD64 || (X86_64 && (GART_IOMMU || (PCI && NUMA)))
1607 source "drivers/pcmcia/Kconfig"
1609 source "drivers/pci/hotplug/Kconfig"
1614 menu "Executable file formats / Emulations"
1616 source "fs/Kconfig.binfmt"
1618 config IA32_EMULATION
1619 bool "IA32 Emulation"
1621 select COMPAT_BINFMT_ELF
1623 Include code to run 32-bit programs under a 64-bit kernel. You should
1624 likely turn this on, unless you're 100% sure that you don't have any
1625 32-bit programs left.
1628 tristate "IA32 a.out support"
1629 depends on IA32_EMULATION && ARCH_SUPPORTS_AOUT
1631 Support old a.out binaries in the 32bit emulation.
1635 depends on IA32_EMULATION
1637 config COMPAT_FOR_U64_ALIGNMENT
1641 config SYSVIPC_COMPAT
1643 depends on X86_64 && COMPAT && SYSVIPC
1648 source "net/Kconfig"
1650 source "drivers/Kconfig"
1652 source "drivers/firmware/Kconfig"
1656 source "arch/x86/Kconfig.debug"
1658 source "security/Kconfig"
1660 source "crypto/Kconfig"
1662 source "arch/x86/kvm/Kconfig"
1664 source "lib/Kconfig"
projects / linux-2.6 / blob