2 mainmenu "Linux Kernel Configuration for x86"
6 bool "64-bit kernel" if ARCH = "x86"
7 default ARCH = "x86_64"
9 Say yes to build a 64-bit kernel - formerly known as x86_64
10 Say no to build a 32-bit kernel - formerly known as i386
24 select HAVE_KRETPROBES
25 select HAVE_KVM if ((X86_32 && !X86_VOYAGER && !X86_VISWS && !X86_NUMAQ) || X86_64)
26 select HAVE_ARCH_KGDB if !X86_VOYAGER
29 config GENERIC_LOCKBREAK
35 config GENERIC_CMOS_UPDATE
38 config CLOCKSOURCE_WATCHDOG
41 config GENERIC_CLOCKEVENTS
44 config GENERIC_CLOCKEVENTS_BROADCAST
46 depends on X86_64 || (X86_32 && X86_LOCAL_APIC)
48 config LOCKDEP_SUPPORT
51 config STACKTRACE_SUPPORT
54 config HAVE_LATENCYTOP_SUPPORT
57 config FAST_CMPXCHG_LOCAL
70 config GENERIC_ISA_DMA
80 config GENERIC_HWEIGHT
86 config ARCH_MAY_HAVE_PC_FDC
92 config RWSEM_GENERIC_SPINLOCK
95 config RWSEM_XCHGADD_ALGORITHM
98 config ARCH_HAS_ILOG2_U32
101 config ARCH_HAS_ILOG2_U64
104 config ARCH_HAS_CPU_IDLE_WAIT
107 config GENERIC_CALIBRATE_DELAY
110 config GENERIC_TIME_VSYSCALL
114 config ARCH_HAS_CPU_RELAX
117 config 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 config ARCH_SUPPORTS_OPTIMIZED_INLINING
148 # Use the generic interrupt handling code in kernel/irq/:
149 config GENERIC_HARDIRQS
153 config GENERIC_IRQ_PROBE
157 config GENERIC_PENDING_IRQ
159 depends on GENERIC_HARDIRQS && SMP
164 depends on SMP && ((X86_32 && !X86_VOYAGER) || X86_64)
169 depends on X86_32 && SMP
173 depends on X86_64 && SMP
178 depends on (X86_32 && !(X86_VISWS || X86_VOYAGER)) || X86_64
181 config X86_BIOS_REBOOT
183 depends on X86_32 && !(X86_VISWS || X86_VOYAGER)
186 config X86_TRAMPOLINE
188 depends on X86_SMP || (X86_VOYAGER && SMP) || (64BIT && ACPI_SLEEP)
193 source "init/Kconfig"
195 menu "Processor type and features"
197 source "kernel/time/Kconfig"
200 bool "Symmetric multi-processing support"
202 This enables support for systems with more than one CPU. If you have
203 a system with only one CPU, like most personal computers, say N. If
204 you have a system with more than one CPU, say Y.
206 If you say N here, the kernel will run on single and multiprocessor
207 machines, but will use only one CPU of a multiprocessor machine. If
208 you say Y here, the kernel will run on many, but not all,
209 singleprocessor machines. On a singleprocessor machine, the kernel
210 will run faster if you say N here.
212 Note that if you say Y here and choose architecture "586" or
213 "Pentium" under "Processor family", the kernel will not work on 486
214 architectures. Similarly, multiprocessor kernels for the "PPro"
215 architecture may not work on all Pentium based boards.
217 People using multiprocessor machines who say Y here should also say
218 Y to "Enhanced Real Time Clock Support", below. The "Advanced Power
219 Management" code will be disabled if you say Y here.
221 See also <file:Documentation/i386/IO-APIC.txt>,
222 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
223 <http://www.tldp.org/docs.html#howto>.
225 If you don't know what to do here, say N.
228 prompt "Subarchitecture Type"
234 Choose this option if your computer is a standard PC or compatible.
240 Select this for an AMD Elan processor.
242 Do not use this option for K6/Athlon/Opteron processors!
244 If unsure, choose "PC-compatible" instead.
248 depends on X86_32 && (SMP || BROKEN)
250 Voyager is an MCA-based 32-way capable SMP architecture proprietary
251 to NCR Corp. Machine classes 345x/35xx/4100/51xx are Voyager-based.
255 If you do not specifically know you have a Voyager based machine,
256 say N here, otherwise the kernel you build will not be bootable.
259 bool "NUMAQ (IBM/Sequent)"
260 depends on SMP && X86_32
263 This option is used for getting Linux to run on a (IBM/Sequent) NUMA
264 multiquad box. This changes the way that processors are bootstrapped,
265 and uses Clustered Logical APIC addressing mode instead of Flat Logical.
266 You will need a new lynxer.elf file to flash your firmware with - send
267 email to <Martin.Bligh@us.ibm.com>.
270 bool "Summit/EXA (IBM x440)"
271 depends on X86_32 && SMP
273 This option is needed for IBM systems that use the Summit/EXA chipset.
274 In particular, it is needed for the x440.
276 If you don't have one of these computers, you should say N here.
277 If you want to build a NUMA kernel, you must select ACPI.
280 bool "Support for other sub-arch SMP systems with more than 8 CPUs"
281 depends on X86_32 && SMP
283 This option is needed for the systems that have more than 8 CPUs
284 and if the system is not of any sub-arch type above.
286 If you don't have such a system, you should say N here.
289 bool "SGI 320/540 (Visual Workstation)"
292 The SGI Visual Workstation series is an IA32-based workstation
293 based on SGI systems chips with some legacy PC hardware attached.
295 Say Y here to create a kernel to run on the SGI 320 or 540.
297 A kernel compiled for the Visual Workstation will not run on PCs
298 and vice versa. See <file:Documentation/sgi-visws.txt> for details.
300 config X86_GENERICARCH
301 bool "Generic architecture (Summit, bigsmp, ES7000, default)"
304 This option compiles in the Summit, bigsmp, ES7000, default subarchitectures.
305 It is intended for a generic binary kernel.
306 If you want a NUMA kernel, select ACPI. We need SRAT for NUMA.
309 bool "Support for Unisys ES7000 IA32 series"
310 depends on X86_32 && SMP
312 Support for Unisys ES7000 systems. Say 'Y' here if this kernel is
313 supposed to run on an IA32-based Unisys ES7000 system.
314 Only choose this option if you have such a system, otherwise you
318 bool "RDC R-321x SoC"
321 select X86_REBOOTFIXUPS
326 This option is needed for RDC R-321x system-on-chip, also known
328 If you don't have one of these chips, you should say N here.
331 bool "Support for ScaleMP vSMP"
335 Support for ScaleMP vSMP systems. Say 'Y' here if this kernel is
336 supposed to run on these EM64T-based machines. Only choose this option
337 if you have one of these machines.
341 config SCHED_NO_NO_OMIT_FRAME_POINTER
343 prompt "Single-depth WCHAN output"
346 Calculate simpler /proc/<PID>/wchan values. If this option
347 is disabled then wchan values will recurse back to the
348 caller function. This provides more accurate wchan values,
349 at the expense of slightly more scheduling overhead.
351 If in doubt, say "Y".
353 menuconfig PARAVIRT_GUEST
354 bool "Paravirtualized guest support"
356 Say Y here to get to see options related to running Linux under
357 various hypervisors. This option alone does not add any kernel code.
359 If you say N, all options in this submenu will be skipped and disabled.
363 source "arch/x86/xen/Kconfig"
366 bool "VMI Guest support"
369 depends on !(X86_VISWS || X86_VOYAGER)
371 VMI provides a paravirtualized interface to the VMware ESX server
372 (it could be used by other hypervisors in theory too, but is not
373 at the moment), by linking the kernel to a GPL-ed ROM module
374 provided by the hypervisor.
376 source "arch/x86/lguest/Kconfig"
379 bool "Enable paravirtualization code"
380 depends on !(X86_VISWS || X86_VOYAGER)
382 This changes the kernel so it can modify itself when it is run
383 under a hypervisor, potentially improving performance significantly
384 over full virtualization. However, when run without a hypervisor
385 the kernel is theoretically slower and slightly larger.
389 config MEMTEST_BOOTPARAM
390 bool "Memtest boot parameter"
394 This option adds a kernel parameter 'memtest', which allows memtest
395 to be disabled at boot. If this option is selected, memtest
396 functionality can be disabled with memtest=0 on the kernel
397 command line. The purpose of this option is to allow a single
398 kernel image to be distributed with memtest built in, but not
401 If you are unsure how to answer this question, answer Y.
403 config MEMTEST_BOOTPARAM_VALUE
404 int "Memtest boot parameter default value (0-4)"
405 depends on MEMTEST_BOOTPARAM
409 This option sets the default value for the kernel parameter
410 'memtest', which allows memtest to be disabled at boot. If this
411 option is set to 0 (zero), the memtest kernel parameter will
412 default to 0, disabling memtest at bootup. If this option is
413 set to 4, the memtest kernel parameter will default to 4,
414 enabling memtest at bootup, and use that as pattern number.
416 If you are unsure how to answer this question, answer 0.
420 depends on X86_32 && ACPI && NUMA && (X86_SUMMIT || X86_GENERICARCH)
423 config HAVE_ARCH_PARSE_SRAT
427 config X86_SUMMIT_NUMA
429 depends on X86_32 && NUMA && (X86_SUMMIT || X86_GENERICARCH)
431 config X86_CYCLONE_TIMER
433 depends on X86_32 && X86_SUMMIT || X86_GENERICARCH
435 config ES7000_CLUSTERED_APIC
437 depends on SMP && X86_ES7000 && MPENTIUMIII
439 source "arch/x86/Kconfig.cpu"
443 prompt "HPET Timer Support" if X86_32
445 Use the IA-PC HPET (High Precision Event Timer) to manage
446 time in preference to the PIT and RTC, if a HPET is
448 HPET is the next generation timer replacing legacy 8254s.
449 The HPET provides a stable time base on SMP
450 systems, unlike the TSC, but it is more expensive to access,
451 as it is off-chip. You can find the HPET spec at
452 <http://www.intel.com/hardwaredesign/hpetspec.htm>.
454 You can safely choose Y here. However, HPET will only be
455 activated if the platform and the BIOS support this feature.
456 Otherwise the 8254 will be used for timing services.
458 Choose N to continue using the legacy 8254 timer.
460 config HPET_EMULATE_RTC
462 depends on HPET_TIMER && (RTC=y || RTC=m || RTC_DRV_CMOS=m || RTC_DRV_CMOS=y)
464 # Mark as embedded because too many people got it wrong.
465 # The code disables itself when not needed.
467 bool "GART IOMMU support" if EMBEDDED
471 depends on X86_64 && PCI
473 Support for full DMA access of devices with 32bit memory access only
474 on systems with more than 3GB. This is usually needed for USB,
475 sound, many IDE/SATA chipsets and some other devices.
476 Provides a driver for the AMD Athlon64/Opteron/Turion/Sempron GART
477 based hardware IOMMU and a software bounce buffer based IOMMU used
478 on Intel systems and as fallback.
479 The code is only active when needed (enough memory and limited
480 device) unless CONFIG_IOMMU_DEBUG or iommu=force is specified
484 bool "IBM Calgary IOMMU support"
486 depends on X86_64 && PCI && EXPERIMENTAL
488 Support for hardware IOMMUs in IBM's xSeries x366 and x460
489 systems. Needed to run systems with more than 3GB of memory
490 properly with 32-bit PCI devices that do not support DAC
491 (Double Address Cycle). Calgary also supports bus level
492 isolation, where all DMAs pass through the IOMMU. This
493 prevents them from going anywhere except their intended
494 destination. This catches hard-to-find kernel bugs and
495 mis-behaving drivers and devices that do not use the DMA-API
496 properly to set up their DMA buffers. The IOMMU can be
497 turned off at boot time with the iommu=off parameter.
498 Normally the kernel will make the right choice by itself.
501 config CALGARY_IOMMU_ENABLED_BY_DEFAULT
503 prompt "Should Calgary be enabled by default?"
504 depends on CALGARY_IOMMU
506 Should Calgary be enabled by default? if you choose 'y', Calgary
507 will be used (if it exists). If you choose 'n', Calgary will not be
508 used even if it exists. If you choose 'n' and would like to use
509 Calgary anyway, pass 'iommu=calgary' on the kernel command line.
513 def_bool (CALGARY_IOMMU || GART_IOMMU)
515 # need this always selected by IOMMU for the VIA workaround
519 Support for software bounce buffers used on x86-64 systems
520 which don't have a hardware IOMMU (e.g. the current generation
521 of Intel's x86-64 CPUs). Using this PCI devices which can only
522 access 32-bits of memory can be used on systems with more than
523 3 GB of memory. If unsure, say Y.
527 int "Maximum number of CPUs (2-255)"
530 default "32" if X86_NUMAQ || X86_SUMMIT || X86_BIGSMP || X86_ES7000
533 This allows you to specify the maximum number of CPUs which this
534 kernel will support. The maximum supported value is 255 and the
535 minimum value which makes sense is 2.
537 This is purely to save memory - each supported CPU adds
538 approximately eight kilobytes to the kernel image.
541 bool "SMT (Hyperthreading) scheduler support"
544 SMT scheduler support improves the CPU scheduler's decision making
545 when dealing with Intel Pentium 4 chips with HyperThreading at a
546 cost of slightly increased overhead in some places. If unsure say
551 prompt "Multi-core scheduler support"
554 Multi-core scheduler support improves the CPU scheduler's decision
555 making when dealing with multi-core CPU chips at a cost of slightly
556 increased overhead in some places. If unsure say N here.
558 source "kernel/Kconfig.preempt"
561 bool "Local APIC support on uniprocessors"
562 depends on X86_32 && !SMP && !(X86_VISWS || X86_VOYAGER || X86_GENERICARCH)
564 A local APIC (Advanced Programmable Interrupt Controller) is an
565 integrated interrupt controller in the CPU. If you have a single-CPU
566 system which has a processor with a local APIC, you can say Y here to
567 enable and use it. If you say Y here even though your machine doesn't
568 have a local APIC, then the kernel will still run with no slowdown at
569 all. The local APIC supports CPU-generated self-interrupts (timer,
570 performance counters), and the NMI watchdog which detects hard
574 bool "IO-APIC support on uniprocessors"
575 depends on X86_UP_APIC
577 An IO-APIC (I/O Advanced Programmable Interrupt Controller) is an
578 SMP-capable replacement for PC-style interrupt controllers. Most
579 SMP systems and many recent uniprocessor systems have one.
581 If you have a single-CPU system with an IO-APIC, you can say Y here
582 to use it. If you say Y here even though your machine doesn't have
583 an IO-APIC, then the kernel will still run with no slowdown at all.
585 config X86_LOCAL_APIC
587 depends on X86_64 || (X86_32 && (X86_UP_APIC || ((X86_VISWS || SMP) && !X86_VOYAGER) || X86_GENERICARCH))
591 depends on X86_64 || (X86_32 && (X86_UP_IOAPIC || (SMP && !(X86_VISWS || X86_VOYAGER)) || X86_GENERICARCH))
593 config X86_VISWS_APIC
595 depends on X86_32 && X86_VISWS
598 bool "Machine Check Exception"
599 depends on !X86_VOYAGER
601 Machine Check Exception support allows the processor to notify the
602 kernel if it detects a problem (e.g. overheating, component failure).
603 The action the kernel takes depends on the severity of the problem,
604 ranging from a warning message on the console, to halting the machine.
605 Your processor must be a Pentium or newer to support this - check the
606 flags in /proc/cpuinfo for mce. Note that some older Pentium systems
607 have a design flaw which leads to false MCE events - hence MCE is
608 disabled on all P5 processors, unless explicitly enabled with "mce"
609 as a boot argument. Similarly, if MCE is built in and creates a
610 problem on some new non-standard machine, you can boot with "nomce"
611 to disable it. MCE support simply ignores non-MCE processors like
612 the 386 and 486, so nearly everyone can say Y here.
616 prompt "Intel MCE features"
617 depends on X86_64 && X86_MCE && X86_LOCAL_APIC
619 Additional support for intel specific MCE features such as
624 prompt "AMD MCE features"
625 depends on X86_64 && X86_MCE && X86_LOCAL_APIC
627 Additional support for AMD specific MCE features such as
628 the DRAM Error Threshold.
630 config X86_MCE_NONFATAL
631 tristate "Check for non-fatal errors on AMD Athlon/Duron / Intel Pentium 4"
632 depends on X86_32 && X86_MCE
634 Enabling this feature starts a timer that triggers every 5 seconds which
635 will look at the machine check registers to see if anything happened.
636 Non-fatal problems automatically get corrected (but still logged).
637 Disable this if you don't want to see these messages.
638 Seeing the messages this option prints out may be indicative of dying
639 or out-of-spec (ie, overclocked) hardware.
640 This option only does something on certain CPUs.
641 (AMD Athlon/Duron and Intel Pentium 4)
643 config X86_MCE_P4THERMAL
644 bool "check for P4 thermal throttling interrupt."
645 depends on X86_32 && X86_MCE && (X86_UP_APIC || SMP) && !X86_VISWS
647 Enabling this feature will cause a message to be printed when the P4
648 enters thermal throttling.
651 bool "Enable VM86 support" if EMBEDDED
655 This option is required by programs like DOSEMU to run 16-bit legacy
656 code on X86 processors. It also may be needed by software like
657 XFree86 to initialize some video cards via BIOS. Disabling this
658 option saves about 6k.
661 tristate "Toshiba Laptop support"
664 This adds a driver to safely access the System Management Mode of
665 the CPU on Toshiba portables with a genuine Toshiba BIOS. It does
666 not work on models with a Phoenix BIOS. The System Management Mode
667 is used to set the BIOS and power saving options on Toshiba portables.
669 For information on utilities to make use of this driver see the
670 Toshiba Linux utilities web site at:
671 <http://www.buzzard.org.uk/toshiba/>.
673 Say Y if you intend to run this kernel on a Toshiba portable.
677 tristate "Dell laptop support"
679 This adds a driver to safely access the System Management Mode
680 of the CPU on the Dell Inspiron 8000. The System Management Mode
681 is used to read cpu temperature and cooling fan status and to
682 control the fans on the I8K portables.
684 This driver has been tested only on the Inspiron 8000 but it may
685 also work with other Dell laptops. You can force loading on other
686 models by passing the parameter `force=1' to the module. Use at
689 For information on utilities to make use of this driver see the
690 I8K Linux utilities web site at:
691 <http://people.debian.org/~dz/i8k/>
693 Say Y if you intend to run this kernel on a Dell Inspiron 8000.
696 config X86_REBOOTFIXUPS
698 prompt "Enable X86 board specific fixups for reboot"
699 depends on X86_32 && X86
701 This enables chipset and/or board specific fixups to be done
702 in order to get reboot to work correctly. This is only needed on
703 some combinations of hardware and BIOS. The symptom, for which
704 this config is intended, is when reboot ends with a stalled/hung
707 Currently, the only fixup is for the Geode machines using
708 CS5530A and CS5536 chipsets and the RDC R-321x SoC.
710 Say Y if you want to enable the fixup. Currently, it's safe to
711 enable this option even if you don't need it.
715 tristate "/dev/cpu/microcode - Intel IA32 CPU microcode support"
718 If you say Y here, you will be able to update the microcode on
719 Intel processors in the IA32 family, e.g. Pentium Pro, Pentium II,
720 Pentium III, Pentium 4, Xeon etc. You will obviously need the
721 actual microcode binary data itself which is not shipped with the
724 For latest news and information on obtaining all the required
725 ingredients for this driver, check:
726 <http://www.urbanmyth.org/microcode/>.
728 To compile this driver as a module, choose M here: the
729 module will be called microcode.
731 config MICROCODE_OLD_INTERFACE
736 tristate "/dev/cpu/*/msr - Model-specific register support"
738 This device gives privileged processes access to the x86
739 Model-Specific Registers (MSRs). It is a character device with
740 major 202 and minors 0 to 31 for /dev/cpu/0/msr to /dev/cpu/31/msr.
741 MSR accesses are directed to a specific CPU on multi-processor
745 tristate "/dev/cpu/*/cpuid - CPU information support"
747 This device gives processes access to the x86 CPUID instruction to
748 be executed on a specific processor. It is a character device
749 with major 203 and minors 0 to 31 for /dev/cpu/0/cpuid to
753 prompt "High Memory Support"
754 default HIGHMEM4G if !X86_NUMAQ
755 default HIGHMEM64G if X86_NUMAQ
760 depends on !X86_NUMAQ
762 Linux can use up to 64 Gigabytes of physical memory on x86 systems.
763 However, the address space of 32-bit x86 processors is only 4
764 Gigabytes large. That means that, if you have a large amount of
765 physical memory, not all of it can be "permanently mapped" by the
766 kernel. The physical memory that's not permanently mapped is called
769 If you are compiling a kernel which will never run on a machine with
770 more than 1 Gigabyte total physical RAM, answer "off" here (default
771 choice and suitable for most users). This will result in a "3GB/1GB"
772 split: 3GB are mapped so that each process sees a 3GB virtual memory
773 space and the remaining part of the 4GB virtual memory space is used
774 by the kernel to permanently map as much physical memory as
777 If the machine has between 1 and 4 Gigabytes physical RAM, then
780 If more than 4 Gigabytes is used then answer "64GB" here. This
781 selection turns Intel PAE (Physical Address Extension) mode on.
782 PAE implements 3-level paging on IA32 processors. PAE is fully
783 supported by Linux, PAE mode is implemented on all recent Intel
784 processors (Pentium Pro and better). NOTE: If you say "64GB" here,
785 then the kernel will not boot on CPUs that don't support PAE!
787 The actual amount of total physical memory will either be
788 auto detected or can be forced by using a kernel command line option
789 such as "mem=256M". (Try "man bootparam" or see the documentation of
790 your boot loader (lilo or loadlin) about how to pass options to the
791 kernel at boot time.)
793 If unsure, say "off".
797 depends on !X86_NUMAQ
799 Select this if you have a 32-bit processor and between 1 and 4
800 gigabytes of physical RAM.
804 depends on !M386 && !M486
807 Select this if you have a 32-bit processor and more than 4
808 gigabytes of physical RAM.
813 depends on EXPERIMENTAL
814 prompt "Memory split" if EMBEDDED
818 Select the desired split between kernel and user memory.
820 If the address range available to the kernel is less than the
821 physical memory installed, the remaining memory will be available
822 as "high memory". Accessing high memory is a little more costly
823 than low memory, as it needs to be mapped into the kernel first.
824 Note that increasing the kernel address space limits the range
825 available to user programs, making the address space there
826 tighter. Selecting anything other than the default 3G/1G split
827 will also likely make your kernel incompatible with binary-only
830 If you are not absolutely sure what you are doing, leave this
834 bool "3G/1G user/kernel split"
835 config VMSPLIT_3G_OPT
837 bool "3G/1G user/kernel split (for full 1G low memory)"
839 bool "2G/2G user/kernel split"
840 config VMSPLIT_2G_OPT
842 bool "2G/2G user/kernel split (for full 2G low memory)"
844 bool "1G/3G user/kernel split"
849 default 0xB0000000 if VMSPLIT_3G_OPT
850 default 0x80000000 if VMSPLIT_2G
851 default 0x78000000 if VMSPLIT_2G_OPT
852 default 0x40000000 if VMSPLIT_1G
858 depends on X86_32 && (HIGHMEM64G || HIGHMEM4G)
862 prompt "PAE (Physical Address Extension) Support"
863 depends on X86_32 && !HIGHMEM4G
864 select RESOURCES_64BIT
866 PAE is required for NX support, and furthermore enables
867 larger swapspace support for non-overcommit purposes. It
868 has the cost of more pagetable lookup overhead, and also
869 consumes more pagetable space per process.
871 # Common NUMA Features
873 bool "Numa Memory Allocation and Scheduler Support (EXPERIMENTAL)"
875 depends on X86_64 || (X86_32 && HIGHMEM64G && (X86_NUMAQ || (X86_SUMMIT || X86_GENERICARCH) && ACPI) && EXPERIMENTAL)
877 default y if (X86_NUMAQ || X86_SUMMIT)
879 Enable NUMA (Non Uniform Memory Access) support.
880 The kernel will try to allocate memory used by a CPU on the
881 local memory controller of the CPU and add some more
882 NUMA awareness to the kernel.
884 For i386 this is currently highly experimental and should be only
885 used for kernel development. It might also cause boot failures.
886 For x86_64 this is recommended on all multiprocessor Opteron systems.
887 If the system is EM64T, you should say N unless your system is
890 comment "NUMA (Summit) requires SMP, 64GB highmem support, ACPI"
891 depends on X86_32 && X86_SUMMIT && (!HIGHMEM64G || !ACPI)
895 prompt "Old style AMD Opteron NUMA detection"
896 depends on X86_64 && NUMA && PCI
898 Enable K8 NUMA node topology detection. You should say Y here if
899 you have a multi processor AMD K8 system. This uses an old
900 method to read the NUMA configuration directly from the builtin
901 Northbridge of Opteron. It is recommended to use X86_64_ACPI_NUMA
902 instead, which also takes priority if both are compiled in.
904 config X86_64_ACPI_NUMA
906 prompt "ACPI NUMA detection"
907 depends on X86_64 && NUMA && ACPI && PCI
910 Enable ACPI SRAT based node topology detection.
912 # Some NUMA nodes have memory ranges that span
913 # other nodes. Even though a pfn is valid and
914 # between a node's start and end pfns, it may not
915 # reside on that node. See memmap_init_zone()
917 config NODES_SPAN_OTHER_NODES
919 depends on X86_64_ACPI_NUMA
922 bool "NUMA emulation"
923 depends on X86_64 && NUMA
925 Enable NUMA emulation. A flat machine will be split
926 into virtual nodes when booted with "numa=fake=N", where N is the
927 number of nodes. This is only useful for debugging.
930 int "Max num nodes shift(1-15)"
932 default "6" if X86_64
933 default "4" if X86_NUMAQ
935 depends on NEED_MULTIPLE_NODES
937 config HAVE_ARCH_BOOTMEM_NODE
939 depends on X86_32 && NUMA
941 config ARCH_HAVE_MEMORY_PRESENT
943 depends on X86_32 && DISCONTIGMEM
945 config NEED_NODE_MEMMAP_SIZE
947 depends on X86_32 && (DISCONTIGMEM || SPARSEMEM)
949 config HAVE_ARCH_ALLOC_REMAP
951 depends on X86_32 && NUMA
953 config ARCH_FLATMEM_ENABLE
955 depends on X86_32 && ARCH_SELECT_MEMORY_MODEL && X86_PC && !NUMA
957 config ARCH_DISCONTIGMEM_ENABLE
959 depends on NUMA && X86_32
961 config ARCH_DISCONTIGMEM_DEFAULT
963 depends on NUMA && X86_32
965 config ARCH_SPARSEMEM_DEFAULT
969 config ARCH_SPARSEMEM_ENABLE
971 depends on X86_64 || NUMA || (EXPERIMENTAL && X86_PC)
972 select SPARSEMEM_STATIC if X86_32
973 select SPARSEMEM_VMEMMAP_ENABLE if X86_64
975 config ARCH_SELECT_MEMORY_MODEL
977 depends on ARCH_SPARSEMEM_ENABLE
979 config ARCH_MEMORY_PROBE
981 depends on MEMORY_HOTPLUG
986 bool "Allocate 3rd-level pagetables from highmem"
987 depends on X86_32 && (HIGHMEM4G || HIGHMEM64G)
989 The VM uses one page table entry for each page of physical memory.
990 For systems with a lot of RAM, this can be wasteful of precious
991 low memory. Setting this option will put user-space page table
992 entries in high memory.
994 config MATH_EMULATION
996 prompt "Math emulation" if X86_32
998 Linux can emulate a math coprocessor (used for floating point
999 operations) if you don't have one. 486DX and Pentium processors have
1000 a math coprocessor built in, 486SX and 386 do not, unless you added
1001 a 487DX or 387, respectively. (The messages during boot time can
1002 give you some hints here ["man dmesg"].) Everyone needs either a
1003 coprocessor or this emulation.
1005 If you don't have a math coprocessor, you need to say Y here; if you
1006 say Y here even though you have a coprocessor, the coprocessor will
1007 be used nevertheless. (This behavior can be changed with the kernel
1008 command line option "no387", which comes handy if your coprocessor
1009 is broken. Try "man bootparam" or see the documentation of your boot
1010 loader (lilo or loadlin) about how to pass options to the kernel at
1011 boot time.) This means that it is a good idea to say Y here if you
1012 intend to use this kernel on different machines.
1014 More information about the internals of the Linux math coprocessor
1015 emulation can be found in <file:arch/x86/math-emu/README>.
1017 If you are not sure, say Y; apart from resulting in a 66 KB bigger
1018 kernel, it won't hurt.
1021 bool "MTRR (Memory Type Range Register) support"
1023 On Intel P6 family processors (Pentium Pro, Pentium II and later)
1024 the Memory Type Range Registers (MTRRs) may be used to control
1025 processor access to memory ranges. This is most useful if you have
1026 a video (VGA) card on a PCI or AGP bus. Enabling write-combining
1027 allows bus write transfers to be combined into a larger transfer
1028 before bursting over the PCI/AGP bus. This can increase performance
1029 of image write operations 2.5 times or more. Saying Y here creates a
1030 /proc/mtrr file which may be used to manipulate your processor's
1031 MTRRs. Typically the X server should use this.
1033 This code has a reasonably generic interface so that similar
1034 control registers on other processors can be easily supported
1037 The Cyrix 6x86, 6x86MX and M II processors have Address Range
1038 Registers (ARRs) which provide a similar functionality to MTRRs. For
1039 these, the ARRs are used to emulate the MTRRs.
1040 The AMD K6-2 (stepping 8 and above) and K6-3 processors have two
1041 MTRRs. The Centaur C6 (WinChip) has 8 MCRs, allowing
1042 write-combining. All of these processors are supported by this code
1043 and it makes sense to say Y here if you have one of them.
1045 Saying Y here also fixes a problem with buggy SMP BIOSes which only
1046 set the MTRRs for the boot CPU and not for the secondary CPUs. This
1047 can lead to all sorts of problems, so it's good to say Y here.
1049 You can safely say Y even if your machine doesn't have MTRRs, you'll
1050 just add about 9 KB to your kernel.
1052 See <file:Documentation/mtrr.txt> for more information.
1056 prompt "x86 PAT support"
1059 Use PAT attributes to setup page level cache control.
1061 PATs are the modern equivalents of MTRRs and are much more
1062 flexible than MTRRs.
1064 Say N here if you see bootup problems (boot crash, boot hang,
1065 spontaneous reboots) or a non-working video driver.
1071 prompt "EFI runtime service support"
1074 This enables the kernel to use EFI runtime services that are
1075 available (such as the EFI variable services).
1077 This option is only useful on systems that have EFI firmware.
1078 In addition, you should use the latest ELILO loader available
1079 at <http://elilo.sourceforge.net> in order to take advantage
1080 of EFI runtime services. However, even with this option, the
1081 resultant kernel should continue to boot on existing non-EFI
1086 prompt "Enable kernel irq balancing"
1087 depends on X86_32 && SMP && X86_IO_APIC
1089 The default yes will allow the kernel to do irq load balancing.
1090 Saying no will keep the kernel from doing irq load balancing.
1094 prompt "Enable seccomp to safely compute untrusted bytecode"
1097 This kernel feature is useful for number crunching applications
1098 that may need to compute untrusted bytecode during their
1099 execution. By using pipes or other transports made available to
1100 the process as file descriptors supporting the read/write
1101 syscalls, it's possible to isolate those applications in
1102 their own address space using seccomp. Once seccomp is
1103 enabled via /proc/<pid>/seccomp, it cannot be disabled
1104 and the task is only allowed to execute a few safe syscalls
1105 defined by each seccomp mode.
1107 If unsure, say Y. Only embedded should say N here.
1109 config CC_STACKPROTECTOR
1110 bool "Enable -fstack-protector buffer overflow detection (EXPERIMENTAL)"
1111 depends on X86_64 && EXPERIMENTAL && BROKEN
1113 This option turns on the -fstack-protector GCC feature. This
1114 feature puts, at the beginning of critical functions, a canary
1115 value on the stack just before the return address, and validates
1116 the value just before actually returning. Stack based buffer
1117 overflows (that need to overwrite this return address) now also
1118 overwrite the canary, which gets detected and the attack is then
1119 neutralized via a kernel panic.
1121 This feature requires gcc version 4.2 or above, or a distribution
1122 gcc with the feature backported. Older versions are automatically
1123 detected and for those versions, this configuration option is ignored.
1125 config CC_STACKPROTECTOR_ALL
1126 bool "Use stack-protector for all functions"
1127 depends on CC_STACKPROTECTOR
1129 Normally, GCC only inserts the canary value protection for
1130 functions that use large-ish on-stack buffers. By enabling
1131 this option, GCC will be asked to do this for ALL functions.
1133 source kernel/Kconfig.hz
1136 bool "kexec system call"
1137 depends on X86_64 || X86_BIOS_REBOOT
1139 kexec is a system call that implements the ability to shutdown your
1140 current kernel, and to start another kernel. It is like a reboot
1141 but it is independent of the system firmware. And like a reboot
1142 you can start any kernel with it, not just Linux.
1144 The name comes from the similarity to the exec system call.
1146 It is an ongoing process to be certain the hardware in a machine
1147 is properly shutdown, so do not be surprised if this code does not
1148 initially work for you. It may help to enable device hotplugging
1149 support. As of this writing the exact hardware interface is
1150 strongly in flux, so no good recommendation can be made.
1153 bool "kernel crash dumps (EXPERIMENTAL)"
1154 depends on EXPERIMENTAL
1155 depends on X86_64 || (X86_32 && HIGHMEM)
1157 Generate crash dump after being started by kexec.
1158 This should be normally only set in special crash dump kernels
1159 which are loaded in the main kernel with kexec-tools into
1160 a specially reserved region and then later executed after
1161 a crash by kdump/kexec. The crash dump kernel must be compiled
1162 to a memory address not used by the main kernel or BIOS using
1163 PHYSICAL_START, or it must be built as a relocatable image
1164 (CONFIG_RELOCATABLE=y).
1165 For more details see Documentation/kdump/kdump.txt
1167 config PHYSICAL_START
1168 hex "Physical address where the kernel is loaded" if (EMBEDDED || CRASH_DUMP)
1169 default "0x1000000" if X86_NUMAQ
1170 default "0x200000" if X86_64
1173 This gives the physical address where the kernel is loaded.
1175 If kernel is a not relocatable (CONFIG_RELOCATABLE=n) then
1176 bzImage will decompress itself to above physical address and
1177 run from there. Otherwise, bzImage will run from the address where
1178 it has been loaded by the boot loader and will ignore above physical
1181 In normal kdump cases one does not have to set/change this option
1182 as now bzImage can be compiled as a completely relocatable image
1183 (CONFIG_RELOCATABLE=y) and be used to load and run from a different
1184 address. This option is mainly useful for the folks who don't want
1185 to use a bzImage for capturing the crash dump and want to use a
1186 vmlinux instead. vmlinux is not relocatable hence a kernel needs
1187 to be specifically compiled to run from a specific memory area
1188 (normally a reserved region) and this option comes handy.
1190 So if you are using bzImage for capturing the crash dump, leave
1191 the value here unchanged to 0x100000 and set CONFIG_RELOCATABLE=y.
1192 Otherwise if you plan to use vmlinux for capturing the crash dump
1193 change this value to start of the reserved region (Typically 16MB
1194 0x1000000). In other words, it can be set based on the "X" value as
1195 specified in the "crashkernel=YM@XM" command line boot parameter
1196 passed to the panic-ed kernel. Typically this parameter is set as
1197 crashkernel=64M@16M. Please take a look at
1198 Documentation/kdump/kdump.txt for more details about crash dumps.
1200 Usage of bzImage for capturing the crash dump is recommended as
1201 one does not have to build two kernels. Same kernel can be used
1202 as production kernel and capture kernel. Above option should have
1203 gone away after relocatable bzImage support is introduced. But it
1204 is present because there are users out there who continue to use
1205 vmlinux for dump capture. This option should go away down the
1208 Don't change this unless you know what you are doing.
1211 bool "Build a relocatable kernel (EXPERIMENTAL)"
1212 depends on EXPERIMENTAL
1214 This builds a kernel image that retains relocation information
1215 so it can be loaded someplace besides the default 1MB.
1216 The relocations tend to make the kernel binary about 10% larger,
1217 but are discarded at runtime.
1219 One use is for the kexec on panic case where the recovery kernel
1220 must live at a different physical address than the primary
1223 Note: If CONFIG_RELOCATABLE=y, then the kernel runs from the address
1224 it has been loaded at and the compile time physical address
1225 (CONFIG_PHYSICAL_START) is ignored.
1227 config PHYSICAL_ALIGN
1229 prompt "Alignment value to which kernel should be aligned" if X86_32
1230 default "0x100000" if X86_32
1231 default "0x200000" if X86_64
1232 range 0x2000 0x400000
1234 This value puts the alignment restrictions on physical address
1235 where kernel is loaded and run from. Kernel is compiled for an
1236 address which meets above alignment restriction.
1238 If bootloader loads the kernel at a non-aligned address and
1239 CONFIG_RELOCATABLE is set, kernel will move itself to nearest
1240 address aligned to above value and run from there.
1242 If bootloader loads the kernel at a non-aligned address and
1243 CONFIG_RELOCATABLE is not set, kernel will ignore the run time
1244 load address and decompress itself to the address it has been
1245 compiled for and run from there. The address for which kernel is
1246 compiled already meets above alignment restrictions. Hence the
1247 end result is that kernel runs from a physical address meeting
1248 above alignment restrictions.
1250 Don't change this unless you know what you are doing.
1253 bool "Support for suspend on SMP and hot-pluggable CPUs (EXPERIMENTAL)"
1254 depends on SMP && HOTPLUG && EXPERIMENTAL && !X86_VOYAGER
1256 Say Y here to experiment with turning CPUs off and on, and to
1257 enable suspend on SMP systems. CPUs can be controlled through
1258 /sys/devices/system/cpu.
1259 Say N if you want to disable CPU hotplug and don't need to
1264 prompt "Compat VDSO support"
1265 depends on X86_32 || IA32_EMULATION
1267 Map the 32-bit VDSO to the predictable old-style address too.
1269 Say N here if you are running a sufficiently recent glibc
1270 version (2.3.3 or later), to remove the high-mapped
1271 VDSO mapping and to exclusively use the randomized VDSO.
1277 config ARCH_ENABLE_MEMORY_HOTPLUG
1279 depends on X86_64 || (X86_32 && HIGHMEM)
1281 config HAVE_ARCH_EARLY_PFN_TO_NID
1285 menu "Power management options"
1286 depends on !X86_VOYAGER
1288 config ARCH_HIBERNATION_HEADER
1290 depends on X86_64 && HIBERNATION
1292 source "kernel/power/Kconfig"
1294 source "drivers/acpi/Kconfig"
1299 depends on APM || APM_MODULE
1302 tristate "APM (Advanced Power Management) BIOS support"
1303 depends on X86_32 && PM_SLEEP && !X86_VISWS
1305 APM is a BIOS specification for saving power using several different
1306 techniques. This is mostly useful for battery powered laptops with
1307 APM compliant BIOSes. If you say Y here, the system time will be
1308 reset after a RESUME operation, the /proc/apm device will provide
1309 battery status information, and user-space programs will receive
1310 notification of APM "events" (e.g. battery status change).
1312 If you select "Y" here, you can disable actual use of the APM
1313 BIOS by passing the "apm=off" option to the kernel at boot time.
1315 Note that the APM support is almost completely disabled for
1316 machines with more than one CPU.
1318 In order to use APM, you will need supporting software. For location
1319 and more information, read <file:Documentation/power/pm.txt> and the
1320 Battery Powered Linux mini-HOWTO, available from
1321 <http://www.tldp.org/docs.html#howto>.
1323 This driver does not spin down disk drives (see the hdparm(8)
1324 manpage ("man 8 hdparm") for that), and it doesn't turn off
1325 VESA-compliant "green" monitors.
1327 This driver does not support the TI 4000M TravelMate and the ACER
1328 486/DX4/75 because they don't have compliant BIOSes. Many "green"
1329 desktop machines also don't have compliant BIOSes, and this driver
1330 may cause those machines to panic during the boot phase.
1332 Generally, if you don't have a battery in your machine, there isn't
1333 much point in using this driver and you should say N. If you get
1334 random kernel OOPSes or reboots that don't seem to be related to
1335 anything, try disabling/enabling this option (or disabling/enabling
1338 Some other things you should try when experiencing seemingly random,
1341 1) make sure that you have enough swap space and that it is
1343 2) pass the "no-hlt" option to the kernel
1344 3) switch on floating point emulation in the kernel and pass
1345 the "no387" option to the kernel
1346 4) pass the "floppy=nodma" option to the kernel
1347 5) pass the "mem=4M" option to the kernel (thereby disabling
1348 all but the first 4 MB of RAM)
1349 6) make sure that the CPU is not over clocked.
1350 7) read the sig11 FAQ at <http://www.bitwizard.nl/sig11/>
1351 8) disable the cache from your BIOS settings
1352 9) install a fan for the video card or exchange video RAM
1353 10) install a better fan for the CPU
1354 11) exchange RAM chips
1355 12) exchange the motherboard.
1357 To compile this driver as a module, choose M here: the
1358 module will be called apm.
1362 config APM_IGNORE_USER_SUSPEND
1363 bool "Ignore USER SUSPEND"
1365 This option will ignore USER SUSPEND requests. On machines with a
1366 compliant APM BIOS, you want to say N. However, on the NEC Versa M
1367 series notebooks, it is necessary to say Y because of a BIOS bug.
1369 config APM_DO_ENABLE
1370 bool "Enable PM at boot time"
1372 Enable APM features at boot time. From page 36 of the APM BIOS
1373 specification: "When disabled, the APM BIOS does not automatically
1374 power manage devices, enter the Standby State, enter the Suspend
1375 State, or take power saving steps in response to CPU Idle calls."
1376 This driver will make CPU Idle calls when Linux is idle (unless this
1377 feature is turned off -- see "Do CPU IDLE calls", below). This
1378 should always save battery power, but more complicated APM features
1379 will be dependent on your BIOS implementation. You may need to turn
1380 this option off if your computer hangs at boot time when using APM
1381 support, or if it beeps continuously instead of suspending. Turn
1382 this off if you have a NEC UltraLite Versa 33/C or a Toshiba
1383 T400CDT. This is off by default since most machines do fine without
1387 bool "Make CPU Idle calls when idle"
1389 Enable calls to APM CPU Idle/CPU Busy inside the kernel's idle loop.
1390 On some machines, this can activate improved power savings, such as
1391 a slowed CPU clock rate, when the machine is idle. These idle calls
1392 are made after the idle loop has run for some length of time (e.g.,
1393 333 mS). On some machines, this will cause a hang at boot time or
1394 whenever the CPU becomes idle. (On machines with more than one CPU,
1395 this option does nothing.)
1397 config APM_DISPLAY_BLANK
1398 bool "Enable console blanking using APM"
1400 Enable console blanking using the APM. Some laptops can use this to
1401 turn off the LCD backlight when the screen blanker of the Linux
1402 virtual console blanks the screen. Note that this is only used by
1403 the virtual console screen blanker, and won't turn off the backlight
1404 when using the X Window system. This also doesn't have anything to
1405 do with your VESA-compliant power-saving monitor. Further, this
1406 option doesn't work for all laptops -- it might not turn off your
1407 backlight at all, or it might print a lot of errors to the console,
1408 especially if you are using gpm.
1410 config APM_ALLOW_INTS
1411 bool "Allow interrupts during APM BIOS calls"
1413 Normally we disable external interrupts while we are making calls to
1414 the APM BIOS as a measure to lessen the effects of a badly behaving
1415 BIOS implementation. The BIOS should reenable interrupts if it
1416 needs to. Unfortunately, some BIOSes do not -- especially those in
1417 many of the newer IBM Thinkpads. If you experience hangs when you
1418 suspend, try setting this to Y. Otherwise, say N.
1420 config APM_REAL_MODE_POWER_OFF
1421 bool "Use real mode APM BIOS call to power off"
1423 Use real mode APM BIOS calls to switch off the computer. This is
1424 a work-around for a number of buggy BIOSes. Switch this option on if
1425 your computer crashes instead of powering off properly.
1429 source "arch/x86/kernel/cpu/cpufreq/Kconfig"
1431 source "drivers/cpuidle/Kconfig"
1436 menu "Bus options (PCI etc.)"
1439 bool "PCI support" if !X86_VISWS && !X86_VSMP
1440 depends on !X86_VOYAGER
1442 select ARCH_SUPPORTS_MSI if (X86_LOCAL_APIC && X86_IO_APIC)
1444 Find out whether you have a PCI motherboard. PCI is the name of a
1445 bus system, i.e. the way the CPU talks to the other stuff inside
1446 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
1447 VESA. If you have PCI, say Y, otherwise N.
1450 prompt "PCI access mode"
1451 depends on X86_32 && PCI && !X86_VISWS
1454 On PCI systems, the BIOS can be used to detect the PCI devices and
1455 determine their configuration. However, some old PCI motherboards
1456 have BIOS bugs and may crash if this is done. Also, some embedded
1457 PCI-based systems don't have any BIOS at all. Linux can also try to
1458 detect the PCI hardware directly without using the BIOS.
1460 With this option, you can specify how Linux should detect the
1461 PCI devices. If you choose "BIOS", the BIOS will be used,
1462 if you choose "Direct", the BIOS won't be used, and if you
1463 choose "MMConfig", then PCI Express MMCONFIG will be used.
1464 If you choose "Any", the kernel will try MMCONFIG, then the
1465 direct access method and falls back to the BIOS if that doesn't
1466 work. If unsure, go with the default, which is "Any".
1471 config PCI_GOMMCONFIG
1484 depends on X86_32 && !X86_VISWS && PCI && (PCI_GOBIOS || PCI_GOANY)
1486 # x86-64 doesn't support PCI BIOS access from long mode so always go direct.
1489 depends on PCI && (X86_64 || (PCI_GODIRECT || PCI_GOANY) || X86_VISWS)
1493 depends on X86_32 && PCI && ACPI && (PCI_GOMMCONFIG || PCI_GOANY)
1500 bool "Support mmconfig PCI config space access"
1501 depends on X86_64 && PCI && ACPI
1504 bool "Support for DMA Remapping Devices (EXPERIMENTAL)"
1505 depends on X86_64 && PCI_MSI && ACPI && EXPERIMENTAL
1507 DMA remapping (DMAR) devices support enables independent address
1508 translations for Direct Memory Access (DMA) from devices.
1509 These DMA remapping devices are reported via ACPI tables
1510 and include PCI device scope covered by these DMA
1515 prompt "Support for Graphics workaround"
1518 Current Graphics drivers tend to use physical address
1519 for DMA and avoid using DMA APIs. Setting this config
1520 option permits the IOMMU driver to set a unity map for
1521 all the OS-visible memory. Hence the driver can continue
1522 to use physical addresses for DMA.
1524 config DMAR_FLOPPY_WA
1528 Floppy disk drivers are know to bypass DMA API calls
1529 thereby failing to work when IOMMU is enabled. This
1530 workaround will setup a 1:1 mapping for the first
1531 16M to make floppy (an ISA device) work.
1533 source "drivers/pci/pcie/Kconfig"
1535 source "drivers/pci/Kconfig"
1537 # x86_64 have no ISA slots, but do have ISA-style DMA.
1545 depends on !(X86_VOYAGER || X86_VISWS)
1547 Find out whether you have ISA slots on your motherboard. ISA is the
1548 name of a bus system, i.e. the way the CPU talks to the other stuff
1549 inside your box. Other bus systems are PCI, EISA, MicroChannel
1550 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
1551 newer boards don't support it. If you have ISA, say Y, otherwise N.
1557 The Extended Industry Standard Architecture (EISA) bus was
1558 developed as an open alternative to the IBM MicroChannel bus.
1560 The EISA bus provided some of the features of the IBM MicroChannel
1561 bus while maintaining backward compatibility with cards made for
1562 the older ISA bus. The EISA bus saw limited use between 1988 and
1563 1995 when it was made obsolete by the PCI bus.
1565 Say Y here if you are building a kernel for an EISA-based machine.
1569 source "drivers/eisa/Kconfig"
1572 bool "MCA support" if !(X86_VISWS || X86_VOYAGER)
1573 default y if X86_VOYAGER
1575 MicroChannel Architecture is found in some IBM PS/2 machines and
1576 laptops. It is a bus system similar to PCI or ISA. See
1577 <file:Documentation/mca.txt> (and especially the web page given
1578 there) before attempting to build an MCA bus kernel.
1580 source "drivers/mca/Kconfig"
1583 tristate "NatSemi SCx200 support"
1584 depends on !X86_VOYAGER
1586 This provides basic support for National Semiconductor's
1587 (now AMD's) Geode processors. The driver probes for the
1588 PCI-IDs of several on-chip devices, so its a good dependency
1589 for other scx200_* drivers.
1591 If compiled as a module, the driver is named scx200.
1593 config SCx200HR_TIMER
1594 tristate "NatSemi SCx200 27MHz High-Resolution Timer Support"
1595 depends on SCx200 && GENERIC_TIME
1598 This driver provides a clocksource built upon the on-chip
1599 27MHz high-resolution timer. Its also a workaround for
1600 NSC Geode SC-1100's buggy TSC, which loses time when the
1601 processor goes idle (as is done by the scheduler). The
1602 other workaround is idle=poll boot option.
1604 config GEODE_MFGPT_TIMER
1606 prompt "Geode Multi-Function General Purpose Timer (MFGPT) events"
1607 depends on MGEODE_LX && GENERIC_TIME && GENERIC_CLOCKEVENTS
1609 This driver provides a clock event source based on the MFGPT
1610 timer(s) in the CS5535 and CS5536 companion chip for the geode.
1611 MFGPTs have a better resolution and max interval than the
1612 generic PIT, and are suitable for use as high-res timers.
1618 depends on AGP_AMD64 || (X86_64 && (GART_IOMMU || (PCI && NUMA)))
1620 source "drivers/pcmcia/Kconfig"
1622 source "drivers/pci/hotplug/Kconfig"
1627 menu "Executable file formats / Emulations"
1629 source "fs/Kconfig.binfmt"
1631 config IA32_EMULATION
1632 bool "IA32 Emulation"
1634 select COMPAT_BINFMT_ELF
1636 Include code to run 32-bit programs under a 64-bit kernel. You should
1637 likely turn this on, unless you're 100% sure that you don't have any
1638 32-bit programs left.
1641 tristate "IA32 a.out support"
1642 depends on IA32_EMULATION && ARCH_SUPPORTS_AOUT
1644 Support old a.out binaries in the 32bit emulation.
1648 depends on IA32_EMULATION
1650 config COMPAT_FOR_U64_ALIGNMENT
1654 config SYSVIPC_COMPAT
1656 depends on X86_64 && COMPAT && SYSVIPC
1661 source "net/Kconfig"
1663 source "drivers/Kconfig"
1665 source "drivers/firmware/Kconfig"
1669 source "arch/x86/Kconfig.debug"
1671 source "security/Kconfig"
1673 source "crypto/Kconfig"
1675 source "arch/x86/kvm/Kconfig"
1677 source "lib/Kconfig"
projects / deliverable / linux.git / blob