2 mainmenu "Linux Kernel Configuration for x86"
6 bool "64-bit kernel" if ARCH = "x86"
7 default ARCH = "x86_64"
9 Say yes to build a 64-bit kernel - formerly known as x86_64
10 Say no to build a 32-bit kernel - formerly known as i386
21 select HAVE_UNSTABLE_SCHED_CLOCK
25 select HAVE_KRETPROBES
26 select HAVE_KVM if ((X86_32 && !X86_VOYAGER && !X86_VISWS && !X86_NUMAQ) || X86_64)
27 select HAVE_ARCH_KGDB if !X86_VOYAGER
31 default "arch/x86/configs/i386_defconfig" if X86_32
32 default "arch/x86/configs/x86_64_defconfig" if X86_64
35 config GENERIC_LOCKBREAK
41 config GENERIC_CMOS_UPDATE
44 config CLOCKSOURCE_WATCHDOG
47 config GENERIC_CLOCKEVENTS
50 config GENERIC_CLOCKEVENTS_BROADCAST
52 depends on X86_64 || (X86_32 && X86_LOCAL_APIC)
54 config LOCKDEP_SUPPORT
57 config STACKTRACE_SUPPORT
60 config HAVE_LATENCYTOP_SUPPORT
63 config FAST_CMPXCHG_LOCAL
76 config GENERIC_ISA_DMA
86 config GENERIC_HWEIGHT
92 config ARCH_MAY_HAVE_PC_FDC
95 config RWSEM_GENERIC_SPINLOCK
98 config RWSEM_XCHGADD_ALGORITHM
101 config ARCH_HAS_ILOG2_U32
104 config ARCH_HAS_ILOG2_U64
107 config ARCH_HAS_CPU_IDLE_WAIT
110 config GENERIC_CALIBRATE_DELAY
113 config GENERIC_TIME_VSYSCALL
117 config ARCH_HAS_CPU_RELAX
120 config ARCH_HAS_CACHE_LINE_SIZE
123 config HAVE_SETUP_PER_CPU_AREA
124 def_bool X86_64 || (X86_SMP && !X86_VOYAGER)
126 config HAVE_CPUMASK_OF_CPU_MAP
129 config ARCH_HIBERNATION_POSSIBLE
131 depends on !SMP || !X86_VOYAGER
133 config ARCH_SUSPEND_POSSIBLE
135 depends on !X86_VOYAGER
141 config ARCH_POPULATES_NODE_MAP
148 config ARCH_SUPPORTS_AOUT
151 config ARCH_SUPPORTS_OPTIMIZED_INLINING
154 # Use the generic interrupt handling code in kernel/irq/:
155 config GENERIC_HARDIRQS
159 config GENERIC_IRQ_PROBE
163 config GENERIC_PENDING_IRQ
165 depends on GENERIC_HARDIRQS && SMP
170 depends on SMP && ((X86_32 && !X86_VOYAGER) || X86_64)
175 depends on X86_32 && SMP
179 depends on X86_64 && SMP
184 depends on (X86_32 && !(X86_VISWS || X86_VOYAGER)) || X86_64
187 config X86_BIOS_REBOOT
189 depends on !X86_VISWS && !X86_VOYAGER
192 config X86_TRAMPOLINE
194 depends on X86_SMP || (X86_VOYAGER && SMP) || (64BIT && ACPI_SLEEP)
199 source "init/Kconfig"
201 menu "Processor type and features"
203 source "kernel/time/Kconfig"
206 bool "Symmetric multi-processing support"
208 This enables support for systems with more than one CPU. If you have
209 a system with only one CPU, like most personal computers, say N. If
210 you have a system with more than one CPU, say Y.
212 If you say N here, the kernel will run on single and multiprocessor
213 machines, but will use only one CPU of a multiprocessor machine. If
214 you say Y here, the kernel will run on many, but not all,
215 singleprocessor machines. On a singleprocessor machine, the kernel
216 will run faster if you say N here.
218 Note that if you say Y here and choose architecture "586" or
219 "Pentium" under "Processor family", the kernel will not work on 486
220 architectures. Similarly, multiprocessor kernels for the "PPro"
221 architecture may not work on all Pentium based boards.
223 People using multiprocessor machines who say Y here should also say
224 Y to "Enhanced Real Time Clock Support", below. The "Advanced Power
225 Management" code will be disabled if you say Y here.
227 See also <file:Documentation/i386/IO-APIC.txt>,
228 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
229 <http://www.tldp.org/docs.html#howto>.
231 If you don't know what to do here, say N.
234 prompt "Subarchitecture Type"
240 Choose this option if your computer is a standard PC or compatible.
246 Select this for an AMD Elan processor.
248 Do not use this option for K6/Athlon/Opteron processors!
250 If unsure, choose "PC-compatible" instead.
254 depends on X86_32 && (SMP || BROKEN) && !PCI
256 Voyager is an MCA-based 32-way capable SMP architecture proprietary
257 to NCR Corp. Machine classes 345x/35xx/4100/51xx are Voyager-based.
261 If you do not specifically know you have a Voyager based machine,
262 say N here, otherwise the kernel you build will not be bootable.
265 bool "NUMAQ (IBM/Sequent)"
266 depends on SMP && X86_32 && PCI
269 This option is used for getting Linux to run on a (IBM/Sequent) NUMA
270 multiquad box. This changes the way that processors are bootstrapped,
271 and uses Clustered Logical APIC addressing mode instead of Flat Logical.
272 You will need a new lynxer.elf file to flash your firmware with - send
273 email to <Martin.Bligh@us.ibm.com>.
276 bool "Summit/EXA (IBM x440)"
277 depends on X86_32 && SMP
279 This option is needed for IBM systems that use the Summit/EXA chipset.
280 In particular, it is needed for the x440.
282 If you don't have one of these computers, you should say N here.
283 If you want to build a NUMA kernel, you must select ACPI.
286 bool "Support for other sub-arch SMP systems with more than 8 CPUs"
287 depends on X86_32 && SMP
289 This option is needed for the systems that have more than 8 CPUs
290 and if the system is not of any sub-arch type above.
292 If you don't have such a system, you should say N here.
295 bool "SGI 320/540 (Visual Workstation)"
296 depends on X86_32 && !PCI
298 The SGI Visual Workstation series is an IA32-based workstation
299 based on SGI systems chips with some legacy PC hardware attached.
301 Say Y here to create a kernel to run on the SGI 320 or 540.
303 A kernel compiled for the Visual Workstation will not run on PCs
304 and vice versa. See <file:Documentation/sgi-visws.txt> for details.
306 config X86_GENERICARCH
307 bool "Generic architecture (Summit, bigsmp, ES7000, default)"
310 This option compiles in the Summit, bigsmp, ES7000, default subarchitectures.
311 It is intended for a generic binary kernel.
312 If you want a NUMA kernel, select ACPI. We need SRAT for NUMA.
315 bool "Support for Unisys ES7000 IA32 series"
316 depends on X86_32 && SMP
318 Support for Unisys ES7000 systems. Say 'Y' here if this kernel is
319 supposed to run on an IA32-based Unisys ES7000 system.
320 Only choose this option if you have such a system, otherwise you
324 bool "RDC R-321x SoC"
327 select X86_REBOOTFIXUPS
333 This option is needed for RDC R-321x system-on-chip, also known
335 If you don't have one of these chips, you should say N here.
338 bool "Support for ScaleMP vSMP"
340 depends on X86_64 && !PCI
342 Support for ScaleMP vSMP systems. Say 'Y' here if this kernel is
343 supposed to run on these EM64T-based machines. Only choose this option
344 if you have one of these machines.
348 config SCHED_NO_NO_OMIT_FRAME_POINTER
350 prompt "Single-depth WCHAN output"
353 Calculate simpler /proc/<PID>/wchan values. If this option
354 is disabled then wchan values will recurse back to the
355 caller function. This provides more accurate wchan values,
356 at the expense of slightly more scheduling overhead.
358 If in doubt, say "Y".
360 menuconfig PARAVIRT_GUEST
361 bool "Paravirtualized guest support"
363 Say Y here to get to see options related to running Linux under
364 various hypervisors. This option alone does not add any kernel code.
366 If you say N, all options in this submenu will be skipped and disabled.
370 source "arch/x86/xen/Kconfig"
373 bool "VMI Guest support"
376 depends on !(X86_VISWS || X86_VOYAGER)
378 VMI provides a paravirtualized interface to the VMware ESX server
379 (it could be used by other hypervisors in theory too, but is not
380 at the moment), by linking the kernel to a GPL-ed ROM module
381 provided by the hypervisor.
384 bool "KVM paravirtualized clock"
386 select PARAVIRT_CLOCK
387 depends on !(X86_VISWS || X86_VOYAGER)
389 Turning on this option will allow you to run a paravirtualized clock
390 when running over the KVM hypervisor. Instead of relying on a PIT
391 (or probably other) emulation by the underlying device model, the host
392 provides the guest with timing infrastructure such as time of day, and
396 bool "KVM Guest support"
398 depends on !(X86_VISWS || X86_VOYAGER)
400 This option enables various optimizations for running under the KVM
403 source "arch/x86/lguest/Kconfig"
406 bool "Enable paravirtualization code"
407 depends on !(X86_VISWS || X86_VOYAGER)
409 This changes the kernel so it can modify itself when it is run
410 under a hypervisor, potentially improving performance significantly
411 over full virtualization. However, when run without a hypervisor
412 the kernel is theoretically slower and slightly larger.
414 config PARAVIRT_CLOCK
425 This option adds a kernel parameter 'memtest', which allows memtest
427 memtest=0, mean disabled; -- default
428 memtest=1, mean do 1 test pattern;
430 memtest=4, mean do 4 test patterns.
431 If you are unsure how to answer this question, answer Y.
435 depends on X86_32 && ACPI && NUMA && (X86_SUMMIT || X86_GENERICARCH)
438 config HAVE_ARCH_PARSE_SRAT
442 config X86_SUMMIT_NUMA
444 depends on X86_32 && NUMA && (X86_SUMMIT || X86_GENERICARCH)
446 config X86_CYCLONE_TIMER
448 depends on X86_32 && X86_SUMMIT || X86_GENERICARCH
450 config ES7000_CLUSTERED_APIC
452 depends on SMP && X86_ES7000 && MPENTIUMIII
454 source "arch/x86/Kconfig.cpu"
458 prompt "HPET Timer Support" if X86_32
460 Use the IA-PC HPET (High Precision Event Timer) to manage
461 time in preference to the PIT and RTC, if a HPET is
463 HPET is the next generation timer replacing legacy 8254s.
464 The HPET provides a stable time base on SMP
465 systems, unlike the TSC, but it is more expensive to access,
466 as it is off-chip. You can find the HPET spec at
467 <http://www.intel.com/hardwaredesign/hpetspec.htm>.
469 You can safely choose Y here. However, HPET will only be
470 activated if the platform and the BIOS support this feature.
471 Otherwise the 8254 will be used for timing services.
473 Choose N to continue using the legacy 8254 timer.
475 config HPET_EMULATE_RTC
477 depends on HPET_TIMER && (RTC=y || RTC=m || RTC_DRV_CMOS=m || RTC_DRV_CMOS=y)
479 # Mark as embedded because too many people got it wrong.
480 # The code disables itself when not needed.
483 bool "Enable DMI scanning" if EMBEDDED
485 Enabled scanning of DMI to identify machine quirks. Say Y
486 here unless you have verified that your setup is not
487 affected by entries in the DMI blacklist. Required by PNP
491 bool "GART IOMMU support" if EMBEDDED
495 depends on X86_64 && PCI
497 Support for full DMA access of devices with 32bit memory access only
498 on systems with more than 3GB. This is usually needed for USB,
499 sound, many IDE/SATA chipsets and some other devices.
500 Provides a driver for the AMD Athlon64/Opteron/Turion/Sempron GART
501 based hardware IOMMU and a software bounce buffer based IOMMU used
502 on Intel systems and as fallback.
503 The code is only active when needed (enough memory and limited
504 device) unless CONFIG_IOMMU_DEBUG or iommu=force is specified
508 bool "IBM Calgary IOMMU support"
510 depends on X86_64 && PCI && EXPERIMENTAL
512 Support for hardware IOMMUs in IBM's xSeries x366 and x460
513 systems. Needed to run systems with more than 3GB of memory
514 properly with 32-bit PCI devices that do not support DAC
515 (Double Address Cycle). Calgary also supports bus level
516 isolation, where all DMAs pass through the IOMMU. This
517 prevents them from going anywhere except their intended
518 destination. This catches hard-to-find kernel bugs and
519 mis-behaving drivers and devices that do not use the DMA-API
520 properly to set up their DMA buffers. The IOMMU can be
521 turned off at boot time with the iommu=off parameter.
522 Normally the kernel will make the right choice by itself.
525 config CALGARY_IOMMU_ENABLED_BY_DEFAULT
527 prompt "Should Calgary be enabled by default?"
528 depends on CALGARY_IOMMU
530 Should Calgary be enabled by default? if you choose 'y', Calgary
531 will be used (if it exists). If you choose 'n', Calgary will not be
532 used even if it exists. If you choose 'n' and would like to use
533 Calgary anyway, pass 'iommu=calgary' on the kernel command line.
536 # need this always selected by IOMMU for the VIA workaround
540 Support for software bounce buffers used on x86-64 systems
541 which don't have a hardware IOMMU (e.g. the current generation
542 of Intel's x86-64 CPUs). Using this PCI devices which can only
543 access 32-bits of memory can be used on systems with more than
544 3 GB of memory. If unsure, say Y.
547 def_bool (CALGARY_IOMMU || GART_IOMMU || SWIOTLB)
550 int "Maximum number of CPUs (2-4096)"
553 default "32" if X86_NUMAQ || X86_SUMMIT || X86_BIGSMP || X86_ES7000
556 This allows you to specify the maximum number of CPUs which this
557 kernel will support. The maximum supported value is 4096 and the
558 minimum value which makes sense is 2.
560 This is purely to save memory - each supported CPU adds
561 approximately one kilobyte to the kernel image.
564 bool "SMT (Hyperthreading) scheduler support"
567 SMT scheduler support improves the CPU scheduler's decision making
568 when dealing with Intel Pentium 4 chips with HyperThreading at a
569 cost of slightly increased overhead in some places. If unsure say
574 prompt "Multi-core scheduler support"
577 Multi-core scheduler support improves the CPU scheduler's decision
578 making when dealing with multi-core CPU chips at a cost of slightly
579 increased overhead in some places. If unsure say N here.
581 source "kernel/Kconfig.preempt"
584 bool "Local APIC support on uniprocessors"
585 depends on X86_32 && !SMP && !(X86_VISWS || X86_VOYAGER || X86_GENERICARCH)
587 A local APIC (Advanced Programmable Interrupt Controller) is an
588 integrated interrupt controller in the CPU. If you have a single-CPU
589 system which has a processor with a local APIC, you can say Y here to
590 enable and use it. If you say Y here even though your machine doesn't
591 have a local APIC, then the kernel will still run with no slowdown at
592 all. The local APIC supports CPU-generated self-interrupts (timer,
593 performance counters), and the NMI watchdog which detects hard
597 bool "IO-APIC support on uniprocessors"
598 depends on X86_UP_APIC
600 An IO-APIC (I/O Advanced Programmable Interrupt Controller) is an
601 SMP-capable replacement for PC-style interrupt controllers. Most
602 SMP systems and many recent uniprocessor systems have one.
604 If you have a single-CPU system with an IO-APIC, you can say Y here
605 to use it. If you say Y here even though your machine doesn't have
606 an IO-APIC, then the kernel will still run with no slowdown at all.
608 config X86_LOCAL_APIC
610 depends on X86_64 || (X86_32 && (X86_UP_APIC || ((X86_VISWS || SMP) && !X86_VOYAGER) || X86_GENERICARCH))
614 depends on X86_64 || (X86_32 && (X86_UP_IOAPIC || (SMP && !(X86_VISWS || X86_VOYAGER)) || X86_GENERICARCH))
616 config X86_VISWS_APIC
618 depends on X86_32 && X86_VISWS
621 bool "Machine Check Exception"
622 depends on !X86_VOYAGER
624 Machine Check Exception support allows the processor to notify the
625 kernel if it detects a problem (e.g. overheating, component failure).
626 The action the kernel takes depends on the severity of the problem,
627 ranging from a warning message on the console, to halting the machine.
628 Your processor must be a Pentium or newer to support this - check the
629 flags in /proc/cpuinfo for mce. Note that some older Pentium systems
630 have a design flaw which leads to false MCE events - hence MCE is
631 disabled on all P5 processors, unless explicitly enabled with "mce"
632 as a boot argument. Similarly, if MCE is built in and creates a
633 problem on some new non-standard machine, you can boot with "nomce"
634 to disable it. MCE support simply ignores non-MCE processors like
635 the 386 and 486, so nearly everyone can say Y here.
639 prompt "Intel MCE features"
640 depends on X86_64 && X86_MCE && X86_LOCAL_APIC
642 Additional support for intel specific MCE features such as
647 prompt "AMD MCE features"
648 depends on X86_64 && X86_MCE && X86_LOCAL_APIC
650 Additional support for AMD specific MCE features such as
651 the DRAM Error Threshold.
653 config X86_MCE_NONFATAL
654 tristate "Check for non-fatal errors on AMD Athlon/Duron / Intel Pentium 4"
655 depends on X86_32 && X86_MCE
657 Enabling this feature starts a timer that triggers every 5 seconds which
658 will look at the machine check registers to see if anything happened.
659 Non-fatal problems automatically get corrected (but still logged).
660 Disable this if you don't want to see these messages.
661 Seeing the messages this option prints out may be indicative of dying
662 or out-of-spec (ie, overclocked) hardware.
663 This option only does something on certain CPUs.
664 (AMD Athlon/Duron and Intel Pentium 4)
666 config X86_MCE_P4THERMAL
667 bool "check for P4 thermal throttling interrupt."
668 depends on X86_32 && X86_MCE && (X86_UP_APIC || SMP) && !X86_VISWS
670 Enabling this feature will cause a message to be printed when the P4
671 enters thermal throttling.
674 bool "Enable VM86 support" if EMBEDDED
678 This option is required by programs like DOSEMU to run 16-bit legacy
679 code on X86 processors. It also may be needed by software like
680 XFree86 to initialize some video cards via BIOS. Disabling this
681 option saves about 6k.
684 tristate "Toshiba Laptop support"
687 This adds a driver to safely access the System Management Mode of
688 the CPU on Toshiba portables with a genuine Toshiba BIOS. It does
689 not work on models with a Phoenix BIOS. The System Management Mode
690 is used to set the BIOS and power saving options on Toshiba portables.
692 For information on utilities to make use of this driver see the
693 Toshiba Linux utilities web site at:
694 <http://www.buzzard.org.uk/toshiba/>.
696 Say Y if you intend to run this kernel on a Toshiba portable.
700 tristate "Dell laptop support"
702 This adds a driver to safely access the System Management Mode
703 of the CPU on the Dell Inspiron 8000. The System Management Mode
704 is used to read cpu temperature and cooling fan status and to
705 control the fans on the I8K portables.
707 This driver has been tested only on the Inspiron 8000 but it may
708 also work with other Dell laptops. You can force loading on other
709 models by passing the parameter `force=1' to the module. Use at
712 For information on utilities to make use of this driver see the
713 I8K Linux utilities web site at:
714 <http://people.debian.org/~dz/i8k/>
716 Say Y if you intend to run this kernel on a Dell Inspiron 8000.
719 config X86_REBOOTFIXUPS
721 prompt "Enable X86 board specific fixups for reboot"
722 depends on X86_32 && X86
724 This enables chipset and/or board specific fixups to be done
725 in order to get reboot to work correctly. This is only needed on
726 some combinations of hardware and BIOS. The symptom, for which
727 this config is intended, is when reboot ends with a stalled/hung
730 Currently, the only fixup is for the Geode machines using
731 CS5530A and CS5536 chipsets and the RDC R-321x SoC.
733 Say Y if you want to enable the fixup. Currently, it's safe to
734 enable this option even if you don't need it.
738 tristate "/dev/cpu/microcode - Intel IA32 CPU microcode support"
741 If you say Y here, you will be able to update the microcode on
742 Intel processors in the IA32 family, e.g. Pentium Pro, Pentium II,
743 Pentium III, Pentium 4, Xeon etc. You will obviously need the
744 actual microcode binary data itself which is not shipped with the
747 For latest news and information on obtaining all the required
748 ingredients for this driver, check:
749 <http://www.urbanmyth.org/microcode/>.
751 To compile this driver as a module, choose M here: the
752 module will be called microcode.
754 config MICROCODE_OLD_INTERFACE
759 tristate "/dev/cpu/*/msr - Model-specific register support"
761 This device gives privileged processes access to the x86
762 Model-Specific Registers (MSRs). It is a character device with
763 major 202 and minors 0 to 31 for /dev/cpu/0/msr to /dev/cpu/31/msr.
764 MSR accesses are directed to a specific CPU on multi-processor
768 tristate "/dev/cpu/*/cpuid - CPU information support"
770 This device gives processes access to the x86 CPUID instruction to
771 be executed on a specific processor. It is a character device
772 with major 203 and minors 0 to 31 for /dev/cpu/0/cpuid to
776 prompt "High Memory Support"
777 default HIGHMEM4G if !X86_NUMAQ
778 default HIGHMEM64G if X86_NUMAQ
783 depends on !X86_NUMAQ
785 Linux can use up to 64 Gigabytes of physical memory on x86 systems.
786 However, the address space of 32-bit x86 processors is only 4
787 Gigabytes large. That means that, if you have a large amount of
788 physical memory, not all of it can be "permanently mapped" by the
789 kernel. The physical memory that's not permanently mapped is called
792 If you are compiling a kernel which will never run on a machine with
793 more than 1 Gigabyte total physical RAM, answer "off" here (default
794 choice and suitable for most users). This will result in a "3GB/1GB"
795 split: 3GB are mapped so that each process sees a 3GB virtual memory
796 space and the remaining part of the 4GB virtual memory space is used
797 by the kernel to permanently map as much physical memory as
800 If the machine has between 1 and 4 Gigabytes physical RAM, then
803 If more than 4 Gigabytes is used then answer "64GB" here. This
804 selection turns Intel PAE (Physical Address Extension) mode on.
805 PAE implements 3-level paging on IA32 processors. PAE is fully
806 supported by Linux, PAE mode is implemented on all recent Intel
807 processors (Pentium Pro and better). NOTE: If you say "64GB" here,
808 then the kernel will not boot on CPUs that don't support PAE!
810 The actual amount of total physical memory will either be
811 auto detected or can be forced by using a kernel command line option
812 such as "mem=256M". (Try "man bootparam" or see the documentation of
813 your boot loader (lilo or loadlin) about how to pass options to the
814 kernel at boot time.)
816 If unsure, say "off".
820 depends on !X86_NUMAQ
822 Select this if you have a 32-bit processor and between 1 and 4
823 gigabytes of physical RAM.
827 depends on !M386 && !M486
830 Select this if you have a 32-bit processor and more than 4
831 gigabytes of physical RAM.
836 depends on EXPERIMENTAL
837 prompt "Memory split" if EMBEDDED
841 Select the desired split between kernel and user memory.
843 If the address range available to the kernel is less than the
844 physical memory installed, the remaining memory will be available
845 as "high memory". Accessing high memory is a little more costly
846 than low memory, as it needs to be mapped into the kernel first.
847 Note that increasing the kernel address space limits the range
848 available to user programs, making the address space there
849 tighter. Selecting anything other than the default 3G/1G split
850 will also likely make your kernel incompatible with binary-only
853 If you are not absolutely sure what you are doing, leave this
857 bool "3G/1G user/kernel split"
858 config VMSPLIT_3G_OPT
860 bool "3G/1G user/kernel split (for full 1G low memory)"
862 bool "2G/2G user/kernel split"
863 config VMSPLIT_2G_OPT
865 bool "2G/2G user/kernel split (for full 2G low memory)"
867 bool "1G/3G user/kernel split"
872 default 0xB0000000 if VMSPLIT_3G_OPT
873 default 0x80000000 if VMSPLIT_2G
874 default 0x78000000 if VMSPLIT_2G_OPT
875 default 0x40000000 if VMSPLIT_1G
881 depends on X86_32 && (HIGHMEM64G || HIGHMEM4G)
885 prompt "PAE (Physical Address Extension) Support"
886 depends on X86_32 && !HIGHMEM4G
887 select RESOURCES_64BIT
889 PAE is required for NX support, and furthermore enables
890 larger swapspace support for non-overcommit purposes. It
891 has the cost of more pagetable lookup overhead, and also
892 consumes more pagetable space per process.
894 # Common NUMA Features
896 bool "Numa Memory Allocation and Scheduler Support (EXPERIMENTAL)"
898 depends on X86_64 || (X86_32 && HIGHMEM64G && (X86_NUMAQ || (X86_SUMMIT || X86_GENERICARCH) && ACPI) && EXPERIMENTAL)
900 default y if (X86_NUMAQ || X86_SUMMIT)
902 Enable NUMA (Non Uniform Memory Access) support.
903 The kernel will try to allocate memory used by a CPU on the
904 local memory controller of the CPU and add some more
905 NUMA awareness to the kernel.
907 For i386 this is currently highly experimental and should be only
908 used for kernel development. It might also cause boot failures.
909 For x86_64 this is recommended on all multiprocessor Opteron systems.
910 If the system is EM64T, you should say N unless your system is
913 comment "NUMA (Summit) requires SMP, 64GB highmem support, ACPI"
914 depends on X86_32 && X86_SUMMIT && (!HIGHMEM64G || !ACPI)
918 prompt "Old style AMD Opteron NUMA detection"
919 depends on X86_64 && NUMA && PCI
921 Enable K8 NUMA node topology detection. You should say Y here if
922 you have a multi processor AMD K8 system. This uses an old
923 method to read the NUMA configuration directly from the builtin
924 Northbridge of Opteron. It is recommended to use X86_64_ACPI_NUMA
925 instead, which also takes priority if both are compiled in.
927 config X86_64_ACPI_NUMA
929 prompt "ACPI NUMA detection"
930 depends on X86_64 && NUMA && ACPI && PCI
933 Enable ACPI SRAT based node topology detection.
935 # Some NUMA nodes have memory ranges that span
936 # other nodes. Even though a pfn is valid and
937 # between a node's start and end pfns, it may not
938 # reside on that node. See memmap_init_zone()
940 config NODES_SPAN_OTHER_NODES
942 depends on X86_64_ACPI_NUMA
945 bool "NUMA emulation"
946 depends on X86_64 && NUMA
948 Enable NUMA emulation. A flat machine will be split
949 into virtual nodes when booted with "numa=fake=N", where N is the
950 number of nodes. This is only useful for debugging.
953 int "Max num nodes shift(1-9)"
955 default "6" if X86_64
956 default "4" if X86_NUMAQ
958 depends on NEED_MULTIPLE_NODES
960 config HAVE_ARCH_BOOTMEM_NODE
962 depends on X86_32 && NUMA
964 config ARCH_HAVE_MEMORY_PRESENT
966 depends on X86_32 && DISCONTIGMEM
968 config NEED_NODE_MEMMAP_SIZE
970 depends on X86_32 && (DISCONTIGMEM || SPARSEMEM)
972 config HAVE_ARCH_ALLOC_REMAP
974 depends on X86_32 && NUMA
976 config ARCH_FLATMEM_ENABLE
978 depends on X86_32 && ARCH_SELECT_MEMORY_MODEL && X86_PC && !NUMA
980 config ARCH_DISCONTIGMEM_ENABLE
982 depends on NUMA && X86_32
984 config ARCH_DISCONTIGMEM_DEFAULT
986 depends on NUMA && X86_32
988 config ARCH_SPARSEMEM_DEFAULT
992 config ARCH_SPARSEMEM_ENABLE
994 depends on X86_64 || NUMA || (EXPERIMENTAL && X86_PC)
995 select SPARSEMEM_STATIC if X86_32
996 select SPARSEMEM_VMEMMAP_ENABLE if X86_64
998 config ARCH_SELECT_MEMORY_MODEL
1000 depends on ARCH_SPARSEMEM_ENABLE
1002 config ARCH_MEMORY_PROBE
1004 depends on MEMORY_HOTPLUG
1009 bool "Allocate 3rd-level pagetables from highmem"
1010 depends on X86_32 && (HIGHMEM4G || HIGHMEM64G)
1012 The VM uses one page table entry for each page of physical memory.
1013 For systems with a lot of RAM, this can be wasteful of precious
1014 low memory. Setting this option will put user-space page table
1015 entries in high memory.
1017 config MATH_EMULATION
1019 prompt "Math emulation" if X86_32
1021 Linux can emulate a math coprocessor (used for floating point
1022 operations) if you don't have one. 486DX and Pentium processors have
1023 a math coprocessor built in, 486SX and 386 do not, unless you added
1024 a 487DX or 387, respectively. (The messages during boot time can
1025 give you some hints here ["man dmesg"].) Everyone needs either a
1026 coprocessor or this emulation.
1028 If you don't have a math coprocessor, you need to say Y here; if you
1029 say Y here even though you have a coprocessor, the coprocessor will
1030 be used nevertheless. (This behavior can be changed with the kernel
1031 command line option "no387", which comes handy if your coprocessor
1032 is broken. Try "man bootparam" or see the documentation of your boot
1033 loader (lilo or loadlin) about how to pass options to the kernel at
1034 boot time.) This means that it is a good idea to say Y here if you
1035 intend to use this kernel on different machines.
1037 More information about the internals of the Linux math coprocessor
1038 emulation can be found in <file:arch/x86/math-emu/README>.
1040 If you are not sure, say Y; apart from resulting in a 66 KB bigger
1041 kernel, it won't hurt.
1044 bool "MTRR (Memory Type Range Register) support"
1046 On Intel P6 family processors (Pentium Pro, Pentium II and later)
1047 the Memory Type Range Registers (MTRRs) may be used to control
1048 processor access to memory ranges. This is most useful if you have
1049 a video (VGA) card on a PCI or AGP bus. Enabling write-combining
1050 allows bus write transfers to be combined into a larger transfer
1051 before bursting over the PCI/AGP bus. This can increase performance
1052 of image write operations 2.5 times or more. Saying Y here creates a
1053 /proc/mtrr file which may be used to manipulate your processor's
1054 MTRRs. Typically the X server should use this.
1056 This code has a reasonably generic interface so that similar
1057 control registers on other processors can be easily supported
1060 The Cyrix 6x86, 6x86MX and M II processors have Address Range
1061 Registers (ARRs) which provide a similar functionality to MTRRs. For
1062 these, the ARRs are used to emulate the MTRRs.
1063 The AMD K6-2 (stepping 8 and above) and K6-3 processors have two
1064 MTRRs. The Centaur C6 (WinChip) has 8 MCRs, allowing
1065 write-combining. All of these processors are supported by this code
1066 and it makes sense to say Y here if you have one of them.
1068 Saying Y here also fixes a problem with buggy SMP BIOSes which only
1069 set the MTRRs for the boot CPU and not for the secondary CPUs. This
1070 can lead to all sorts of problems, so it's good to say Y here.
1072 You can safely say Y even if your machine doesn't have MTRRs, you'll
1073 just add about 9 KB to your kernel.
1075 See <file:Documentation/mtrr.txt> for more information.
1079 prompt "x86 PAT support"
1082 Use PAT attributes to setup page level cache control.
1084 PATs are the modern equivalents of MTRRs and are much more
1085 flexible than MTRRs.
1087 Say N here if you see bootup problems (boot crash, boot hang,
1088 spontaneous reboots) or a non-working video driver.
1094 prompt "EFI runtime service support"
1097 This enables the kernel to use EFI runtime services that are
1098 available (such as the EFI variable services).
1100 This option is only useful on systems that have EFI firmware.
1101 In addition, you should use the latest ELILO loader available
1102 at <http://elilo.sourceforge.net> in order to take advantage
1103 of EFI runtime services. However, even with this option, the
1104 resultant kernel should continue to boot on existing non-EFI
1109 prompt "Enable kernel irq balancing"
1110 depends on X86_32 && SMP && X86_IO_APIC
1112 The default yes will allow the kernel to do irq load balancing.
1113 Saying no will keep the kernel from doing irq load balancing.
1117 prompt "Enable seccomp to safely compute untrusted bytecode"
1120 This kernel feature is useful for number crunching applications
1121 that may need to compute untrusted bytecode during their
1122 execution. By using pipes or other transports made available to
1123 the process as file descriptors supporting the read/write
1124 syscalls, it's possible to isolate those applications in
1125 their own address space using seccomp. Once seccomp is
1126 enabled via /proc/<pid>/seccomp, it cannot be disabled
1127 and the task is only allowed to execute a few safe syscalls
1128 defined by each seccomp mode.
1130 If unsure, say Y. Only embedded should say N here.
1132 config CC_STACKPROTECTOR
1133 bool "Enable -fstack-protector buffer overflow detection (EXPERIMENTAL)"
1134 depends on X86_64 && EXPERIMENTAL && BROKEN
1136 This option turns on the -fstack-protector GCC feature. This
1137 feature puts, at the beginning of critical functions, a canary
1138 value on the stack just before the return address, and validates
1139 the value just before actually returning. Stack based buffer
1140 overflows (that need to overwrite this return address) now also
1141 overwrite the canary, which gets detected and the attack is then
1142 neutralized via a kernel panic.
1144 This feature requires gcc version 4.2 or above, or a distribution
1145 gcc with the feature backported. Older versions are automatically
1146 detected and for those versions, this configuration option is ignored.
1148 config CC_STACKPROTECTOR_ALL
1149 bool "Use stack-protector for all functions"
1150 depends on CC_STACKPROTECTOR
1152 Normally, GCC only inserts the canary value protection for
1153 functions that use large-ish on-stack buffers. By enabling
1154 this option, GCC will be asked to do this for ALL functions.
1156 source kernel/Kconfig.hz
1159 bool "kexec system call"
1160 depends on X86_BIOS_REBOOT
1162 kexec is a system call that implements the ability to shutdown your
1163 current kernel, and to start another kernel. It is like a reboot
1164 but it is independent of the system firmware. And like a reboot
1165 you can start any kernel with it, not just Linux.
1167 The name comes from the similarity to the exec system call.
1169 It is an ongoing process to be certain the hardware in a machine
1170 is properly shutdown, so do not be surprised if this code does not
1171 initially work for you. It may help to enable device hotplugging
1172 support. As of this writing the exact hardware interface is
1173 strongly in flux, so no good recommendation can be made.
1176 bool "kernel crash dumps (EXPERIMENTAL)"
1177 depends on EXPERIMENTAL
1178 depends on X86_64 || (X86_32 && HIGHMEM)
1180 Generate crash dump after being started by kexec.
1181 This should be normally only set in special crash dump kernels
1182 which are loaded in the main kernel with kexec-tools into
1183 a specially reserved region and then later executed after
1184 a crash by kdump/kexec. The crash dump kernel must be compiled
1185 to a memory address not used by the main kernel or BIOS using
1186 PHYSICAL_START, or it must be built as a relocatable image
1187 (CONFIG_RELOCATABLE=y).
1188 For more details see Documentation/kdump/kdump.txt
1190 config PHYSICAL_START
1191 hex "Physical address where the kernel is loaded" if (EMBEDDED || CRASH_DUMP)
1192 default "0x1000000" if X86_NUMAQ
1193 default "0x200000" if X86_64
1196 This gives the physical address where the kernel is loaded.
1198 If kernel is a not relocatable (CONFIG_RELOCATABLE=n) then
1199 bzImage will decompress itself to above physical address and
1200 run from there. Otherwise, bzImage will run from the address where
1201 it has been loaded by the boot loader and will ignore above physical
1204 In normal kdump cases one does not have to set/change this option
1205 as now bzImage can be compiled as a completely relocatable image
1206 (CONFIG_RELOCATABLE=y) and be used to load and run from a different
1207 address. This option is mainly useful for the folks who don't want
1208 to use a bzImage for capturing the crash dump and want to use a
1209 vmlinux instead. vmlinux is not relocatable hence a kernel needs
1210 to be specifically compiled to run from a specific memory area
1211 (normally a reserved region) and this option comes handy.
1213 So if you are using bzImage for capturing the crash dump, leave
1214 the value here unchanged to 0x100000 and set CONFIG_RELOCATABLE=y.
1215 Otherwise if you plan to use vmlinux for capturing the crash dump
1216 change this value to start of the reserved region (Typically 16MB
1217 0x1000000). In other words, it can be set based on the "X" value as
1218 specified in the "crashkernel=YM@XM" command line boot parameter
1219 passed to the panic-ed kernel. Typically this parameter is set as
1220 crashkernel=64M@16M. Please take a look at
1221 Documentation/kdump/kdump.txt for more details about crash dumps.
1223 Usage of bzImage for capturing the crash dump is recommended as
1224 one does not have to build two kernels. Same kernel can be used
1225 as production kernel and capture kernel. Above option should have
1226 gone away after relocatable bzImage support is introduced. But it
1227 is present because there are users out there who continue to use
1228 vmlinux for dump capture. This option should go away down the
1231 Don't change this unless you know what you are doing.
1234 bool "Build a relocatable kernel (EXPERIMENTAL)"
1235 depends on EXPERIMENTAL
1237 This builds a kernel image that retains relocation information
1238 so it can be loaded someplace besides the default 1MB.
1239 The relocations tend to make the kernel binary about 10% larger,
1240 but are discarded at runtime.
1242 One use is for the kexec on panic case where the recovery kernel
1243 must live at a different physical address than the primary
1246 Note: If CONFIG_RELOCATABLE=y, then the kernel runs from the address
1247 it has been loaded at and the compile time physical address
1248 (CONFIG_PHYSICAL_START) is ignored.
1250 config PHYSICAL_ALIGN
1252 prompt "Alignment value to which kernel should be aligned" if X86_32
1253 default "0x100000" if X86_32
1254 default "0x200000" if X86_64
1255 range 0x2000 0x400000
1257 This value puts the alignment restrictions on physical address
1258 where kernel is loaded and run from. Kernel is compiled for an
1259 address which meets above alignment restriction.
1261 If bootloader loads the kernel at a non-aligned address and
1262 CONFIG_RELOCATABLE is set, kernel will move itself to nearest
1263 address aligned to above value and run from there.
1265 If bootloader loads the kernel at a non-aligned address and
1266 CONFIG_RELOCATABLE is not set, kernel will ignore the run time
1267 load address and decompress itself to the address it has been
1268 compiled for and run from there. The address for which kernel is
1269 compiled already meets above alignment restrictions. Hence the
1270 end result is that kernel runs from a physical address meeting
1271 above alignment restrictions.
1273 Don't change this unless you know what you are doing.
1276 bool "Support for suspend on SMP and hot-pluggable CPUs (EXPERIMENTAL)"
1277 depends on SMP && HOTPLUG && EXPERIMENTAL && !X86_VOYAGER
1279 Say Y here to experiment with turning CPUs off and on, and to
1280 enable suspend on SMP systems. CPUs can be controlled through
1281 /sys/devices/system/cpu.
1282 Say N if you want to disable CPU hotplug and don't need to
1287 prompt "Compat VDSO support"
1288 depends on X86_32 || IA32_EMULATION
1290 Map the 32-bit VDSO to the predictable old-style address too.
1292 Say N here if you are running a sufficiently recent glibc
1293 version (2.3.3 or later), to remove the high-mapped
1294 VDSO mapping and to exclusively use the randomized VDSO.
1300 config ARCH_ENABLE_MEMORY_HOTPLUG
1302 depends on X86_64 || (X86_32 && HIGHMEM)
1304 config HAVE_ARCH_EARLY_PFN_TO_NID
1308 menu "Power management options"
1309 depends on !X86_VOYAGER
1311 config ARCH_HIBERNATION_HEADER
1313 depends on X86_64 && HIBERNATION
1315 source "kernel/power/Kconfig"
1317 source "drivers/acpi/Kconfig"
1322 depends on APM || APM_MODULE
1325 tristate "APM (Advanced Power Management) BIOS support"
1326 depends on X86_32 && PM_SLEEP && !X86_VISWS
1328 APM is a BIOS specification for saving power using several different
1329 techniques. This is mostly useful for battery powered laptops with
1330 APM compliant BIOSes. If you say Y here, the system time will be
1331 reset after a RESUME operation, the /proc/apm device will provide
1332 battery status information, and user-space programs will receive
1333 notification of APM "events" (e.g. battery status change).
1335 If you select "Y" here, you can disable actual use of the APM
1336 BIOS by passing the "apm=off" option to the kernel at boot time.
1338 Note that the APM support is almost completely disabled for
1339 machines with more than one CPU.
1341 In order to use APM, you will need supporting software. For location
1342 and more information, read <file:Documentation/power/pm.txt> and the
1343 Battery Powered Linux mini-HOWTO, available from
1344 <http://www.tldp.org/docs.html#howto>.
1346 This driver does not spin down disk drives (see the hdparm(8)
1347 manpage ("man 8 hdparm") for that), and it doesn't turn off
1348 VESA-compliant "green" monitors.
1350 This driver does not support the TI 4000M TravelMate and the ACER
1351 486/DX4/75 because they don't have compliant BIOSes. Many "green"
1352 desktop machines also don't have compliant BIOSes, and this driver
1353 may cause those machines to panic during the boot phase.
1355 Generally, if you don't have a battery in your machine, there isn't
1356 much point in using this driver and you should say N. If you get
1357 random kernel OOPSes or reboots that don't seem to be related to
1358 anything, try disabling/enabling this option (or disabling/enabling
1361 Some other things you should try when experiencing seemingly random,
1364 1) make sure that you have enough swap space and that it is
1366 2) pass the "no-hlt" option to the kernel
1367 3) switch on floating point emulation in the kernel and pass
1368 the "no387" option to the kernel
1369 4) pass the "floppy=nodma" option to the kernel
1370 5) pass the "mem=4M" option to the kernel (thereby disabling
1371 all but the first 4 MB of RAM)
1372 6) make sure that the CPU is not over clocked.
1373 7) read the sig11 FAQ at <http://www.bitwizard.nl/sig11/>
1374 8) disable the cache from your BIOS settings
1375 9) install a fan for the video card or exchange video RAM
1376 10) install a better fan for the CPU
1377 11) exchange RAM chips
1378 12) exchange the motherboard.
1380 To compile this driver as a module, choose M here: the
1381 module will be called apm.
1385 config APM_IGNORE_USER_SUSPEND
1386 bool "Ignore USER SUSPEND"
1388 This option will ignore USER SUSPEND requests. On machines with a
1389 compliant APM BIOS, you want to say N. However, on the NEC Versa M
1390 series notebooks, it is necessary to say Y because of a BIOS bug.
1392 config APM_DO_ENABLE
1393 bool "Enable PM at boot time"
1395 Enable APM features at boot time. From page 36 of the APM BIOS
1396 specification: "When disabled, the APM BIOS does not automatically
1397 power manage devices, enter the Standby State, enter the Suspend
1398 State, or take power saving steps in response to CPU Idle calls."
1399 This driver will make CPU Idle calls when Linux is idle (unless this
1400 feature is turned off -- see "Do CPU IDLE calls", below). This
1401 should always save battery power, but more complicated APM features
1402 will be dependent on your BIOS implementation. You may need to turn
1403 this option off if your computer hangs at boot time when using APM
1404 support, or if it beeps continuously instead of suspending. Turn
1405 this off if you have a NEC UltraLite Versa 33/C or a Toshiba
1406 T400CDT. This is off by default since most machines do fine without
1410 bool "Make CPU Idle calls when idle"
1412 Enable calls to APM CPU Idle/CPU Busy inside the kernel's idle loop.
1413 On some machines, this can activate improved power savings, such as
1414 a slowed CPU clock rate, when the machine is idle. These idle calls
1415 are made after the idle loop has run for some length of time (e.g.,
1416 333 mS). On some machines, this will cause a hang at boot time or
1417 whenever the CPU becomes idle. (On machines with more than one CPU,
1418 this option does nothing.)
1420 config APM_DISPLAY_BLANK
1421 bool "Enable console blanking using APM"
1423 Enable console blanking using the APM. Some laptops can use this to
1424 turn off the LCD backlight when the screen blanker of the Linux
1425 virtual console blanks the screen. Note that this is only used by
1426 the virtual console screen blanker, and won't turn off the backlight
1427 when using the X Window system. This also doesn't have anything to
1428 do with your VESA-compliant power-saving monitor. Further, this
1429 option doesn't work for all laptops -- it might not turn off your
1430 backlight at all, or it might print a lot of errors to the console,
1431 especially if you are using gpm.
1433 config APM_ALLOW_INTS
1434 bool "Allow interrupts during APM BIOS calls"
1436 Normally we disable external interrupts while we are making calls to
1437 the APM BIOS as a measure to lessen the effects of a badly behaving
1438 BIOS implementation. The BIOS should reenable interrupts if it
1439 needs to. Unfortunately, some BIOSes do not -- especially those in
1440 many of the newer IBM Thinkpads. If you experience hangs when you
1441 suspend, try setting this to Y. Otherwise, say N.
1443 config APM_REAL_MODE_POWER_OFF
1444 bool "Use real mode APM BIOS call to power off"
1446 Use real mode APM BIOS calls to switch off the computer. This is
1447 a work-around for a number of buggy BIOSes. Switch this option on if
1448 your computer crashes instead of powering off properly.
1452 source "arch/x86/kernel/cpu/cpufreq/Kconfig"
1454 source "drivers/cpuidle/Kconfig"
1459 menu "Bus options (PCI etc.)"
1464 select ARCH_SUPPORTS_MSI if (X86_LOCAL_APIC && X86_IO_APIC)
1466 Find out whether you have a PCI motherboard. PCI is the name of a
1467 bus system, i.e. the way the CPU talks to the other stuff inside
1468 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
1469 VESA. If you have PCI, say Y, otherwise N.
1472 prompt "PCI access mode"
1473 depends on X86_32 && PCI && !X86_VISWS
1476 On PCI systems, the BIOS can be used to detect the PCI devices and
1477 determine their configuration. However, some old PCI motherboards
1478 have BIOS bugs and may crash if this is done. Also, some embedded
1479 PCI-based systems don't have any BIOS at all. Linux can also try to
1480 detect the PCI hardware directly without using the BIOS.
1482 With this option, you can specify how Linux should detect the
1483 PCI devices. If you choose "BIOS", the BIOS will be used,
1484 if you choose "Direct", the BIOS won't be used, and if you
1485 choose "MMConfig", then PCI Express MMCONFIG will be used.
1486 If you choose "Any", the kernel will try MMCONFIG, then the
1487 direct access method and falls back to the BIOS if that doesn't
1488 work. If unsure, go with the default, which is "Any".
1493 config PCI_GOMMCONFIG
1510 depends on X86_32 && !X86_VISWS && PCI && (PCI_GOBIOS || PCI_GOANY)
1512 # x86-64 doesn't support PCI BIOS access from long mode so always go direct.
1515 depends on PCI && (X86_64 || (PCI_GODIRECT || PCI_GOANY || PCI_GOOLPC) || X86_VISWS)
1519 depends on X86_32 && PCI && ACPI && (PCI_GOMMCONFIG || PCI_GOANY)
1523 depends on PCI && OLPC && (PCI_GOOLPC || PCI_GOANY)
1530 bool "Support mmconfig PCI config space access"
1531 depends on X86_64 && PCI && ACPI
1534 bool "Support for DMA Remapping Devices (EXPERIMENTAL)"
1535 depends on X86_64 && PCI_MSI && ACPI && EXPERIMENTAL
1537 DMA remapping (DMAR) devices support enables independent address
1538 translations for Direct Memory Access (DMA) from devices.
1539 These DMA remapping devices are reported via ACPI tables
1540 and include PCI device scope covered by these DMA
1545 prompt "Support for Graphics workaround"
1548 Current Graphics drivers tend to use physical address
1549 for DMA and avoid using DMA APIs. Setting this config
1550 option permits the IOMMU driver to set a unity map for
1551 all the OS-visible memory. Hence the driver can continue
1552 to use physical addresses for DMA.
1554 config DMAR_FLOPPY_WA
1558 Floppy disk drivers are know to bypass DMA API calls
1559 thereby failing to work when IOMMU is enabled. This
1560 workaround will setup a 1:1 mapping for the first
1561 16M to make floppy (an ISA device) work.
1563 source "drivers/pci/pcie/Kconfig"
1565 source "drivers/pci/Kconfig"
1567 # x86_64 have no ISA slots, but do have ISA-style DMA.
1575 depends on !(X86_VOYAGER || X86_VISWS)
1577 Find out whether you have ISA slots on your motherboard. ISA is the
1578 name of a bus system, i.e. the way the CPU talks to the other stuff
1579 inside your box. Other bus systems are PCI, EISA, MicroChannel
1580 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
1581 newer boards don't support it. If you have ISA, say Y, otherwise N.
1587 The Extended Industry Standard Architecture (EISA) bus was
1588 developed as an open alternative to the IBM MicroChannel bus.
1590 The EISA bus provided some of the features of the IBM MicroChannel
1591 bus while maintaining backward compatibility with cards made for
1592 the older ISA bus. The EISA bus saw limited use between 1988 and
1593 1995 when it was made obsolete by the PCI bus.
1595 Say Y here if you are building a kernel for an EISA-based machine.
1599 source "drivers/eisa/Kconfig"
1602 bool "MCA support" if !(X86_VISWS || X86_VOYAGER)
1603 default y if X86_VOYAGER
1605 MicroChannel Architecture is found in some IBM PS/2 machines and
1606 laptops. It is a bus system similar to PCI or ISA. See
1607 <file:Documentation/mca.txt> (and especially the web page given
1608 there) before attempting to build an MCA bus kernel.
1610 source "drivers/mca/Kconfig"
1613 tristate "NatSemi SCx200 support"
1614 depends on !X86_VOYAGER
1616 This provides basic support for National Semiconductor's
1617 (now AMD's) Geode processors. The driver probes for the
1618 PCI-IDs of several on-chip devices, so its a good dependency
1619 for other scx200_* drivers.
1621 If compiled as a module, the driver is named scx200.
1623 config SCx200HR_TIMER
1624 tristate "NatSemi SCx200 27MHz High-Resolution Timer Support"
1625 depends on SCx200 && GENERIC_TIME
1628 This driver provides a clocksource built upon the on-chip
1629 27MHz high-resolution timer. Its also a workaround for
1630 NSC Geode SC-1100's buggy TSC, which loses time when the
1631 processor goes idle (as is done by the scheduler). The
1632 other workaround is idle=poll boot option.
1634 config GEODE_MFGPT_TIMER
1636 prompt "Geode Multi-Function General Purpose Timer (MFGPT) events"
1637 depends on MGEODE_LX && GENERIC_TIME && GENERIC_CLOCKEVENTS
1639 This driver provides a clock event source based on the MFGPT
1640 timer(s) in the CS5535 and CS5536 companion chip for the geode.
1641 MFGPTs have a better resolution and max interval than the
1642 generic PIT, and are suitable for use as high-res timers.
1645 bool "One Laptop Per Child support"
1648 Add support for detecting the unique features of the OLPC
1655 depends on AGP_AMD64 || (X86_64 && (GART_IOMMU || (PCI && NUMA)))
1657 source "drivers/pcmcia/Kconfig"
1659 source "drivers/pci/hotplug/Kconfig"
1664 menu "Executable file formats / Emulations"
1666 source "fs/Kconfig.binfmt"
1668 config IA32_EMULATION
1669 bool "IA32 Emulation"
1671 select COMPAT_BINFMT_ELF
1673 Include code to run 32-bit programs under a 64-bit kernel. You should
1674 likely turn this on, unless you're 100% sure that you don't have any
1675 32-bit programs left.
1678 tristate "IA32 a.out support"
1679 depends on IA32_EMULATION && ARCH_SUPPORTS_AOUT
1681 Support old a.out binaries in the 32bit emulation.
1685 depends on IA32_EMULATION
1687 config COMPAT_FOR_U64_ALIGNMENT
1691 config SYSVIPC_COMPAT
1693 depends on X86_64 && COMPAT && SYSVIPC
1698 source "net/Kconfig"
1700 source "drivers/Kconfig"
1702 source "drivers/firmware/Kconfig"
1706 source "arch/x86/Kconfig.debug"
1708 source "security/Kconfig"
1710 source "crypto/Kconfig"
1712 source "arch/x86/kvm/Kconfig"
1714 source "lib/Kconfig"
projects / linux-2.6 / blob