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_AOUT if X86_32
22 select HAVE_UNSTABLE_SCHED_CLOCK
25 select HAVE_IOREMAP_PROT
27 select ARCH_WANT_OPTIONAL_GPIOLIB
28 select HAVE_KRETPROBES
29 select HAVE_DYNAMIC_FTRACE
31 select HAVE_KVM if ((X86_32 && !X86_VOYAGER && !X86_VISWS && !X86_NUMAQ) || X86_64)
32 select HAVE_ARCH_KGDB if !X86_VOYAGER
33 select HAVE_GENERIC_DMA_COHERENT if X86_32
34 select HAVE_EFFICIENT_UNALIGNED_ACCESS
38 default "arch/x86/configs/i386_defconfig" if X86_32
39 default "arch/x86/configs/x86_64_defconfig" if X86_64
42 config GENERIC_LOCKBREAK
48 config GENERIC_CMOS_UPDATE
51 config CLOCKSOURCE_WATCHDOG
54 config GENERIC_CLOCKEVENTS
57 config GENERIC_CLOCKEVENTS_BROADCAST
59 depends on X86_64 || (X86_32 && X86_LOCAL_APIC)
61 config LOCKDEP_SUPPORT
64 config STACKTRACE_SUPPORT
67 config HAVE_LATENCYTOP_SUPPORT
70 config FAST_CMPXCHG_LOCAL
83 config GENERIC_ISA_DMA
93 config GENERIC_HWEIGHT
99 config ARCH_MAY_HAVE_PC_FDC
102 config RWSEM_GENERIC_SPINLOCK
105 config RWSEM_XCHGADD_ALGORITHM
108 config ARCH_HAS_ILOG2_U32
111 config ARCH_HAS_ILOG2_U64
114 config ARCH_HAS_CPU_IDLE_WAIT
117 config GENERIC_CALIBRATE_DELAY
120 config GENERIC_TIME_VSYSCALL
124 config ARCH_HAS_CPU_RELAX
127 config ARCH_HAS_CACHE_LINE_SIZE
130 config HAVE_SETUP_PER_CPU_AREA
131 def_bool X86_64_SMP || (X86_SMP && !X86_VOYAGER)
133 config HAVE_CPUMASK_OF_CPU_MAP
136 config ARCH_HIBERNATION_POSSIBLE
138 depends on !SMP || !X86_VOYAGER
140 config ARCH_SUSPEND_POSSIBLE
142 depends on !X86_VOYAGER
148 config ARCH_POPULATES_NODE_MAP
155 config ARCH_SUPPORTS_OPTIMIZED_INLINING
158 # Use the generic interrupt handling code in kernel/irq/:
159 config GENERIC_HARDIRQS
163 config GENERIC_IRQ_PROBE
167 config GENERIC_PENDING_IRQ
169 depends on GENERIC_HARDIRQS && SMP
174 depends on SMP && ((X86_32 && !X86_VOYAGER) || X86_64)
175 select USE_GENERIC_SMP_HELPERS
180 depends on X86_32 && SMP
184 depends on X86_64 && SMP
189 depends on (X86_32 && !X86_VOYAGER) || X86_64
192 config X86_BIOS_REBOOT
194 depends on !X86_VOYAGER
197 config X86_TRAMPOLINE
199 depends on X86_SMP || (X86_VOYAGER && SMP) || (64BIT && ACPI_SLEEP)
204 source "init/Kconfig"
206 menu "Processor type and features"
208 source "kernel/time/Kconfig"
211 bool "Symmetric multi-processing support"
213 This enables support for systems with more than one CPU. If you have
214 a system with only one CPU, like most personal computers, say N. If
215 you have a system with more than one CPU, say Y.
217 If you say N here, the kernel will run on single and multiprocessor
218 machines, but will use only one CPU of a multiprocessor machine. If
219 you say Y here, the kernel will run on many, but not all,
220 singleprocessor machines. On a singleprocessor machine, the kernel
221 will run faster if you say N here.
223 Note that if you say Y here and choose architecture "586" or
224 "Pentium" under "Processor family", the kernel will not work on 486
225 architectures. Similarly, multiprocessor kernels for the "PPro"
226 architecture may not work on all Pentium based boards.
228 People using multiprocessor machines who say Y here should also say
229 Y to "Enhanced Real Time Clock Support", below. The "Advanced Power
230 Management" code will be disabled if you say Y here.
232 See also <file:Documentation/i386/IO-APIC.txt>,
233 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
234 <http://www.tldp.org/docs.html#howto>.
236 If you don't know what to do here, say N.
238 config X86_FIND_SMP_CONFIG
240 depends on X86_MPPARSE || X86_VOYAGER
245 bool "Enable MPS table"
246 depends on X86_LOCAL_APIC
248 For old smp systems that do not have proper acpi support. Newer systems
249 (esp with 64bit cpus) with acpi support, MADT and DSDT will override it
255 depends on X86_LOCAL_APIC
259 prompt "Subarchitecture Type"
265 Choose this option if your computer is a standard PC or compatible.
271 Select this for an AMD Elan processor.
273 Do not use this option for K6/Athlon/Opteron processors!
275 If unsure, choose "PC-compatible" instead.
279 depends on X86_32 && (SMP || BROKEN) && !PCI
281 Voyager is an MCA-based 32-way capable SMP architecture proprietary
282 to NCR Corp. Machine classes 345x/35xx/4100/51xx are Voyager-based.
286 If you do not specifically know you have a Voyager based machine,
287 say N here, otherwise the kernel you build will not be bootable.
289 config X86_GENERICARCH
290 bool "Generic architecture"
293 This option compiles in the NUMAQ, Summit, bigsmp, ES7000, default
294 subarchitectures. It is intended for a generic binary kernel.
295 if you select them all, kernel will probe it one by one. and will
301 bool "NUMAQ (IBM/Sequent)"
302 depends on SMP && X86_32 && PCI && X86_MPPARSE
305 This option is used for getting Linux to run on a NUMAQ (IBM/Sequent)
306 NUMA multiquad box. This changes the way that processors are
307 bootstrapped, and uses Clustered Logical APIC addressing mode instead
308 of Flat Logical. You will need a new lynxer.elf file to flash your
309 firmware with - send email to <Martin.Bligh@us.ibm.com>.
312 bool "Summit/EXA (IBM x440)"
313 depends on X86_32 && SMP
315 This option is needed for IBM systems that use the Summit/EXA chipset.
316 In particular, it is needed for the x440.
319 bool "Support for Unisys ES7000 IA32 series"
320 depends on X86_32 && SMP
322 Support for Unisys ES7000 systems. Say 'Y' here if this kernel is
323 supposed to run on an IA32-based Unisys ES7000 system.
326 bool "Support for big SMP systems with more than 8 CPUs"
327 depends on X86_32 && SMP
329 This option is needed for the systems that have more than 8 CPUs
330 and if the system is not of any sub-arch type above.
335 bool "Support for ScaleMP vSMP"
337 depends on X86_64 && PCI
339 Support for ScaleMP vSMP systems. Say 'Y' here if this kernel is
340 supposed to run on these EM64T-based machines. Only choose this option
341 if you have one of these machines.
346 bool "SGI 320/540 (Visual Workstation)"
347 depends on X86_32 && PCI && !X86_VOYAGER && X86_MPPARSE && PCI_GODIRECT
349 The SGI Visual Workstation series is an IA32-based workstation
350 based on SGI systems chips with some legacy PC hardware attached.
352 Say Y here to create a kernel to run on the SGI 320 or 540.
354 A kernel compiled for the Visual Workstation will run on general
355 PCs as well. See <file:Documentation/sgi-visws.txt> for details.
358 bool "RDC R-321x SoC"
361 select X86_REBOOTFIXUPS
363 This option is needed for RDC R-321x system-on-chip, also known
365 If you don't have one of these chips, you should say N here.
367 config SCHED_NO_NO_OMIT_FRAME_POINTER
369 prompt "Single-depth WCHAN output"
372 Calculate simpler /proc/<PID>/wchan values. If this option
373 is disabled then wchan values will recurse back to the
374 caller function. This provides more accurate wchan values,
375 at the expense of slightly more scheduling overhead.
377 If in doubt, say "Y".
379 menuconfig PARAVIRT_GUEST
380 bool "Paravirtualized guest support"
382 Say Y here to get to see options related to running Linux under
383 various hypervisors. This option alone does not add any kernel code.
385 If you say N, all options in this submenu will be skipped and disabled.
389 source "arch/x86/xen/Kconfig"
392 bool "VMI Guest support"
395 depends on !X86_VOYAGER
397 VMI provides a paravirtualized interface to the VMware ESX server
398 (it could be used by other hypervisors in theory too, but is not
399 at the moment), by linking the kernel to a GPL-ed ROM module
400 provided by the hypervisor.
403 bool "KVM paravirtualized clock"
405 select PARAVIRT_CLOCK
406 depends on !X86_VOYAGER
408 Turning on this option will allow you to run a paravirtualized clock
409 when running over the KVM hypervisor. Instead of relying on a PIT
410 (or probably other) emulation by the underlying device model, the host
411 provides the guest with timing infrastructure such as time of day, and
415 bool "KVM Guest support"
417 depends on !X86_VOYAGER
419 This option enables various optimizations for running under the KVM
422 source "arch/x86/lguest/Kconfig"
425 bool "Enable paravirtualization code"
426 depends on !X86_VOYAGER
428 This changes the kernel so it can modify itself when it is run
429 under a hypervisor, potentially improving performance significantly
430 over full virtualization. However, when run without a hypervisor
431 the kernel is theoretically slower and slightly larger.
433 config PARAVIRT_CLOCK
439 config PARAVIRT_DEBUG
440 bool "paravirt-ops debugging"
441 depends on PARAVIRT && DEBUG_KERNEL
443 Enable to debug paravirt_ops internals. Specifically, BUG if
444 a paravirt_op is missing when it is called.
449 This option adds a kernel parameter 'memtest', which allows memtest
451 memtest=0, mean disabled; -- default
452 memtest=1, mean do 1 test pattern;
454 memtest=4, mean do 4 test patterns.
455 If you are unsure how to answer this question, answer N.
457 config X86_SUMMIT_NUMA
459 depends on X86_32 && NUMA && X86_GENERICARCH
461 config X86_CYCLONE_TIMER
463 depends on X86_GENERICARCH
465 config ES7000_CLUSTERED_APIC
467 depends on SMP && X86_ES7000 && MPENTIUMIII
469 source "arch/x86/Kconfig.cpu"
473 prompt "HPET Timer Support" if X86_32
475 Use the IA-PC HPET (High Precision Event Timer) to manage
476 time in preference to the PIT and RTC, if a HPET is
478 HPET is the next generation timer replacing legacy 8254s.
479 The HPET provides a stable time base on SMP
480 systems, unlike the TSC, but it is more expensive to access,
481 as it is off-chip. You can find the HPET spec at
482 <http://www.intel.com/hardwaredesign/hpetspec.htm>.
484 You can safely choose Y here. However, HPET will only be
485 activated if the platform and the BIOS support this feature.
486 Otherwise the 8254 will be used for timing services.
488 Choose N to continue using the legacy 8254 timer.
490 config HPET_EMULATE_RTC
492 depends on HPET_TIMER && (RTC=y || RTC=m || RTC_DRV_CMOS=m || RTC_DRV_CMOS=y)
494 # Mark as embedded because too many people got it wrong.
495 # The code disables itself when not needed.
498 bool "Enable DMI scanning" if EMBEDDED
500 Enabled scanning of DMI to identify machine quirks. Say Y
501 here unless you have verified that your setup is not
502 affected by entries in the DMI blacklist. Required by PNP
506 bool "GART IOMMU support" if EMBEDDED
510 depends on X86_64 && PCI
512 Support for full DMA access of devices with 32bit memory access only
513 on systems with more than 3GB. This is usually needed for USB,
514 sound, many IDE/SATA chipsets and some other devices.
515 Provides a driver for the AMD Athlon64/Opteron/Turion/Sempron GART
516 based hardware IOMMU and a software bounce buffer based IOMMU used
517 on Intel systems and as fallback.
518 The code is only active when needed (enough memory and limited
519 device) unless CONFIG_IOMMU_DEBUG or iommu=force is specified
523 bool "IBM Calgary IOMMU support"
525 depends on X86_64 && PCI && EXPERIMENTAL
527 Support for hardware IOMMUs in IBM's xSeries x366 and x460
528 systems. Needed to run systems with more than 3GB of memory
529 properly with 32-bit PCI devices that do not support DAC
530 (Double Address Cycle). Calgary also supports bus level
531 isolation, where all DMAs pass through the IOMMU. This
532 prevents them from going anywhere except their intended
533 destination. This catches hard-to-find kernel bugs and
534 mis-behaving drivers and devices that do not use the DMA-API
535 properly to set up their DMA buffers. The IOMMU can be
536 turned off at boot time with the iommu=off parameter.
537 Normally the kernel will make the right choice by itself.
540 config CALGARY_IOMMU_ENABLED_BY_DEFAULT
542 prompt "Should Calgary be enabled by default?"
543 depends on CALGARY_IOMMU
545 Should Calgary be enabled by default? if you choose 'y', Calgary
546 will be used (if it exists). If you choose 'n', Calgary will not be
547 used even if it exists. If you choose 'n' and would like to use
548 Calgary anyway, pass 'iommu=calgary' on the kernel command line.
552 bool "AMD IOMMU support"
554 depends on X86_64 && PCI && ACPI
556 With this option you can enable support for AMD IOMMU hardware in
557 your system. An IOMMU is a hardware component which provides
558 remapping of DMA memory accesses from devices. With an AMD IOMMU you
559 can isolate the the DMA memory of different devices and protect the
560 system from misbehaving device drivers or hardware.
562 You can find out if your system has an AMD IOMMU if you look into
563 your BIOS for an option to enable it or if you have an IVRS ACPI
566 # need this always selected by IOMMU for the VIA workaround
570 Support for software bounce buffers used on x86-64 systems
571 which don't have a hardware IOMMU (e.g. the current generation
572 of Intel's x86-64 CPUs). Using this PCI devices which can only
573 access 32-bits of memory can be used on systems with more than
574 3 GB of memory. If unsure, say Y.
577 def_bool (CALGARY_IOMMU || GART_IOMMU || SWIOTLB || AMD_IOMMU)
580 bool "Configure Maximum number of SMP Processors and NUMA Nodes"
581 depends on X86_64 && SMP && BROKEN
584 Configure maximum number of CPUS and NUMA Nodes for this architecture.
588 int "Maximum number of CPUs (2-512)" if !MAXSMP
591 default "4096" if MAXSMP
592 default "32" if X86_NUMAQ || X86_SUMMIT || X86_BIGSMP || X86_ES7000
595 This allows you to specify the maximum number of CPUs which this
596 kernel will support. The maximum supported value is 512 and the
597 minimum value which makes sense is 2.
599 This is purely to save memory - each supported CPU adds
600 approximately eight kilobytes to the kernel image.
603 bool "SMT (Hyperthreading) scheduler support"
606 SMT scheduler support improves the CPU scheduler's decision making
607 when dealing with Intel Pentium 4 chips with HyperThreading at a
608 cost of slightly increased overhead in some places. If unsure say
613 prompt "Multi-core scheduler support"
616 Multi-core scheduler support improves the CPU scheduler's decision
617 making when dealing with multi-core CPU chips at a cost of slightly
618 increased overhead in some places. If unsure say N here.
620 source "kernel/Kconfig.preempt"
623 bool "Local APIC support on uniprocessors"
624 depends on X86_32 && !SMP && !(X86_VOYAGER || X86_GENERICARCH)
626 A local APIC (Advanced Programmable Interrupt Controller) is an
627 integrated interrupt controller in the CPU. If you have a single-CPU
628 system which has a processor with a local APIC, you can say Y here to
629 enable and use it. If you say Y here even though your machine doesn't
630 have a local APIC, then the kernel will still run with no slowdown at
631 all. The local APIC supports CPU-generated self-interrupts (timer,
632 performance counters), and the NMI watchdog which detects hard
636 bool "IO-APIC support on uniprocessors"
637 depends on X86_UP_APIC
639 An IO-APIC (I/O Advanced Programmable Interrupt Controller) is an
640 SMP-capable replacement for PC-style interrupt controllers. Most
641 SMP systems and many recent uniprocessor systems have one.
643 If you have a single-CPU system with an IO-APIC, you can say Y here
644 to use it. If you say Y here even though your machine doesn't have
645 an IO-APIC, then the kernel will still run with no slowdown at all.
647 config X86_LOCAL_APIC
649 depends on X86_64 || (X86_32 && (X86_UP_APIC || (SMP && !X86_VOYAGER) || X86_GENERICARCH))
653 depends on X86_64 || (X86_32 && (X86_UP_IOAPIC || (SMP && !X86_VOYAGER) || X86_GENERICARCH))
655 config X86_VISWS_APIC
657 depends on X86_32 && X86_VISWS
660 bool "Machine Check Exception"
661 depends on !X86_VOYAGER
663 Machine Check Exception support allows the processor to notify the
664 kernel if it detects a problem (e.g. overheating, component failure).
665 The action the kernel takes depends on the severity of the problem,
666 ranging from a warning message on the console, to halting the machine.
667 Your processor must be a Pentium or newer to support this - check the
668 flags in /proc/cpuinfo for mce. Note that some older Pentium systems
669 have a design flaw which leads to false MCE events - hence MCE is
670 disabled on all P5 processors, unless explicitly enabled with "mce"
671 as a boot argument. Similarly, if MCE is built in and creates a
672 problem on some new non-standard machine, you can boot with "nomce"
673 to disable it. MCE support simply ignores non-MCE processors like
674 the 386 and 486, so nearly everyone can say Y here.
678 prompt "Intel MCE features"
679 depends on X86_64 && X86_MCE && X86_LOCAL_APIC
681 Additional support for intel specific MCE features such as
686 prompt "AMD MCE features"
687 depends on X86_64 && X86_MCE && X86_LOCAL_APIC
689 Additional support for AMD specific MCE features such as
690 the DRAM Error Threshold.
692 config X86_MCE_NONFATAL
693 tristate "Check for non-fatal errors on AMD Athlon/Duron / Intel Pentium 4"
694 depends on X86_32 && X86_MCE
696 Enabling this feature starts a timer that triggers every 5 seconds which
697 will look at the machine check registers to see if anything happened.
698 Non-fatal problems automatically get corrected (but still logged).
699 Disable this if you don't want to see these messages.
700 Seeing the messages this option prints out may be indicative of dying
701 or out-of-spec (ie, overclocked) hardware.
702 This option only does something on certain CPUs.
703 (AMD Athlon/Duron and Intel Pentium 4)
705 config X86_MCE_P4THERMAL
706 bool "check for P4 thermal throttling interrupt."
707 depends on X86_32 && X86_MCE && (X86_UP_APIC || SMP)
709 Enabling this feature will cause a message to be printed when the P4
710 enters thermal throttling.
713 bool "Enable VM86 support" if EMBEDDED
717 This option is required by programs like DOSEMU to run 16-bit legacy
718 code on X86 processors. It also may be needed by software like
719 XFree86 to initialize some video cards via BIOS. Disabling this
720 option saves about 6k.
723 tristate "Toshiba Laptop support"
726 This adds a driver to safely access the System Management Mode of
727 the CPU on Toshiba portables with a genuine Toshiba BIOS. It does
728 not work on models with a Phoenix BIOS. The System Management Mode
729 is used to set the BIOS and power saving options on Toshiba portables.
731 For information on utilities to make use of this driver see the
732 Toshiba Linux utilities web site at:
733 <http://www.buzzard.org.uk/toshiba/>.
735 Say Y if you intend to run this kernel on a Toshiba portable.
739 tristate "Dell laptop support"
741 This adds a driver to safely access the System Management Mode
742 of the CPU on the Dell Inspiron 8000. The System Management Mode
743 is used to read cpu temperature and cooling fan status and to
744 control the fans on the I8K portables.
746 This driver has been tested only on the Inspiron 8000 but it may
747 also work with other Dell laptops. You can force loading on other
748 models by passing the parameter `force=1' to the module. Use at
751 For information on utilities to make use of this driver see the
752 I8K Linux utilities web site at:
753 <http://people.debian.org/~dz/i8k/>
755 Say Y if you intend to run this kernel on a Dell Inspiron 8000.
758 config X86_REBOOTFIXUPS
760 prompt "Enable X86 board specific fixups for reboot"
761 depends on X86_32 && X86
763 This enables chipset and/or board specific fixups to be done
764 in order to get reboot to work correctly. This is only needed on
765 some combinations of hardware and BIOS. The symptom, for which
766 this config is intended, is when reboot ends with a stalled/hung
769 Currently, the only fixup is for the Geode machines using
770 CS5530A and CS5536 chipsets and the RDC R-321x SoC.
772 Say Y if you want to enable the fixup. Currently, it's safe to
773 enable this option even if you don't need it.
777 tristate "/dev/cpu/microcode - Intel IA32 CPU microcode support"
780 If you say Y here, you will be able to update the microcode on
781 Intel processors in the IA32 family, e.g. Pentium Pro, Pentium II,
782 Pentium III, Pentium 4, Xeon etc. You will obviously need the
783 actual microcode binary data itself which is not shipped with the
786 For latest news and information on obtaining all the required
787 ingredients for this driver, check:
788 <http://www.urbanmyth.org/microcode/>.
790 To compile this driver as a module, choose M here: the
791 module will be called microcode.
793 config MICROCODE_OLD_INTERFACE
798 tristate "/dev/cpu/*/msr - Model-specific register support"
800 This device gives privileged processes access to the x86
801 Model-Specific Registers (MSRs). It is a character device with
802 major 202 and minors 0 to 31 for /dev/cpu/0/msr to /dev/cpu/31/msr.
803 MSR accesses are directed to a specific CPU on multi-processor
807 tristate "/dev/cpu/*/cpuid - CPU information support"
809 This device gives processes access to the x86 CPUID instruction to
810 be executed on a specific processor. It is a character device
811 with major 203 and minors 0 to 31 for /dev/cpu/0/cpuid to
815 prompt "High Memory Support"
816 default HIGHMEM4G if !X86_NUMAQ
817 default HIGHMEM64G if X86_NUMAQ
822 depends on !X86_NUMAQ
824 Linux can use up to 64 Gigabytes of physical memory on x86 systems.
825 However, the address space of 32-bit x86 processors is only 4
826 Gigabytes large. That means that, if you have a large amount of
827 physical memory, not all of it can be "permanently mapped" by the
828 kernel. The physical memory that's not permanently mapped is called
831 If you are compiling a kernel which will never run on a machine with
832 more than 1 Gigabyte total physical RAM, answer "off" here (default
833 choice and suitable for most users). This will result in a "3GB/1GB"
834 split: 3GB are mapped so that each process sees a 3GB virtual memory
835 space and the remaining part of the 4GB virtual memory space is used
836 by the kernel to permanently map as much physical memory as
839 If the machine has between 1 and 4 Gigabytes physical RAM, then
842 If more than 4 Gigabytes is used then answer "64GB" here. This
843 selection turns Intel PAE (Physical Address Extension) mode on.
844 PAE implements 3-level paging on IA32 processors. PAE is fully
845 supported by Linux, PAE mode is implemented on all recent Intel
846 processors (Pentium Pro and better). NOTE: If you say "64GB" here,
847 then the kernel will not boot on CPUs that don't support PAE!
849 The actual amount of total physical memory will either be
850 auto detected or can be forced by using a kernel command line option
851 such as "mem=256M". (Try "man bootparam" or see the documentation of
852 your boot loader (lilo or loadlin) about how to pass options to the
853 kernel at boot time.)
855 If unsure, say "off".
859 depends on !X86_NUMAQ
861 Select this if you have a 32-bit processor and between 1 and 4
862 gigabytes of physical RAM.
866 depends on !M386 && !M486
869 Select this if you have a 32-bit processor and more than 4
870 gigabytes of physical RAM.
875 depends on EXPERIMENTAL
876 prompt "Memory split" if EMBEDDED
880 Select the desired split between kernel and user memory.
882 If the address range available to the kernel is less than the
883 physical memory installed, the remaining memory will be available
884 as "high memory". Accessing high memory is a little more costly
885 than low memory, as it needs to be mapped into the kernel first.
886 Note that increasing the kernel address space limits the range
887 available to user programs, making the address space there
888 tighter. Selecting anything other than the default 3G/1G split
889 will also likely make your kernel incompatible with binary-only
892 If you are not absolutely sure what you are doing, leave this
896 bool "3G/1G user/kernel split"
897 config VMSPLIT_3G_OPT
899 bool "3G/1G user/kernel split (for full 1G low memory)"
901 bool "2G/2G user/kernel split"
902 config VMSPLIT_2G_OPT
904 bool "2G/2G user/kernel split (for full 2G low memory)"
906 bool "1G/3G user/kernel split"
911 default 0xB0000000 if VMSPLIT_3G_OPT
912 default 0x80000000 if VMSPLIT_2G
913 default 0x78000000 if VMSPLIT_2G_OPT
914 default 0x40000000 if VMSPLIT_1G
920 depends on X86_32 && (HIGHMEM64G || HIGHMEM4G)
924 prompt "PAE (Physical Address Extension) Support"
925 depends on X86_32 && !HIGHMEM4G
926 select RESOURCES_64BIT
928 PAE is required for NX support, and furthermore enables
929 larger swapspace support for non-overcommit purposes. It
930 has the cost of more pagetable lookup overhead, and also
931 consumes more pagetable space per process.
933 # Common NUMA Features
935 bool "Numa Memory Allocation and Scheduler Support (EXPERIMENTAL)"
937 depends on X86_64 || (X86_32 && HIGHMEM64G && (X86_NUMAQ || X86_BIGSMP || X86_SUMMIT && ACPI) && EXPERIMENTAL)
939 default y if (X86_NUMAQ || X86_SUMMIT || X86_BIGSMP)
941 Enable NUMA (Non Uniform Memory Access) support.
942 The kernel will try to allocate memory used by a CPU on the
943 local memory controller of the CPU and add some more
944 NUMA awareness to the kernel.
946 For 32-bit this is currently highly experimental and should be only
947 used for kernel development. It might also cause boot failures.
948 For 64-bit this is recommended on all multiprocessor Opteron systems.
949 If the system is EM64T, you should say N unless your system is
952 comment "NUMA (Summit) requires SMP, 64GB highmem support, ACPI"
953 depends on X86_32 && X86_SUMMIT && (!HIGHMEM64G || !ACPI)
957 prompt "Old style AMD Opteron NUMA detection"
958 depends on X86_64 && NUMA && PCI
960 Enable K8 NUMA node topology detection. You should say Y here if
961 you have a multi processor AMD K8 system. This uses an old
962 method to read the NUMA configuration directly from the builtin
963 Northbridge of Opteron. It is recommended to use X86_64_ACPI_NUMA
964 instead, which also takes priority if both are compiled in.
966 config X86_64_ACPI_NUMA
968 prompt "ACPI NUMA detection"
969 depends on X86_64 && NUMA && ACPI && PCI
972 Enable ACPI SRAT based node topology detection.
974 # Some NUMA nodes have memory ranges that span
975 # other nodes. Even though a pfn is valid and
976 # between a node's start and end pfns, it may not
977 # reside on that node. See memmap_init_zone()
979 config NODES_SPAN_OTHER_NODES
981 depends on X86_64_ACPI_NUMA
984 bool "NUMA emulation"
985 depends on X86_64 && NUMA
987 Enable NUMA emulation. A flat machine will be split
988 into virtual nodes when booted with "numa=fake=N", where N is the
989 number of nodes. This is only useful for debugging.
992 int "Maximum NUMA Nodes (as a power of 2)" if !MAXSMP
994 default "9" if MAXSMP
995 default "6" if X86_64
996 default "4" if X86_NUMAQ
998 depends on NEED_MULTIPLE_NODES
1000 Specify the maximum number of NUMA Nodes available on the target
1001 system. Increases memory reserved to accomodate various tables.
1003 config HAVE_ARCH_BOOTMEM_NODE
1005 depends on X86_32 && NUMA
1007 config ARCH_HAVE_MEMORY_PRESENT
1009 depends on X86_32 && DISCONTIGMEM
1011 config NEED_NODE_MEMMAP_SIZE
1013 depends on X86_32 && (DISCONTIGMEM || SPARSEMEM)
1015 config HAVE_ARCH_ALLOC_REMAP
1017 depends on X86_32 && NUMA
1019 config ARCH_FLATMEM_ENABLE
1021 depends on X86_32 && ARCH_SELECT_MEMORY_MODEL && X86_PC && !NUMA
1023 config ARCH_DISCONTIGMEM_ENABLE
1025 depends on NUMA && X86_32
1027 config ARCH_DISCONTIGMEM_DEFAULT
1029 depends on NUMA && X86_32
1031 config ARCH_SPARSEMEM_DEFAULT
1035 config ARCH_SPARSEMEM_ENABLE
1037 depends on X86_64 || NUMA || (EXPERIMENTAL && X86_PC)
1038 select SPARSEMEM_STATIC if X86_32
1039 select SPARSEMEM_VMEMMAP_ENABLE if X86_64
1041 config ARCH_SELECT_MEMORY_MODEL
1043 depends on ARCH_SPARSEMEM_ENABLE
1045 config ARCH_MEMORY_PROBE
1047 depends on MEMORY_HOTPLUG
1052 bool "Allocate 3rd-level pagetables from highmem"
1053 depends on X86_32 && (HIGHMEM4G || HIGHMEM64G)
1055 The VM uses one page table entry for each page of physical memory.
1056 For systems with a lot of RAM, this can be wasteful of precious
1057 low memory. Setting this option will put user-space page table
1058 entries in high memory.
1060 config MATH_EMULATION
1062 prompt "Math emulation" if X86_32
1064 Linux can emulate a math coprocessor (used for floating point
1065 operations) if you don't have one. 486DX and Pentium processors have
1066 a math coprocessor built in, 486SX and 386 do not, unless you added
1067 a 487DX or 387, respectively. (The messages during boot time can
1068 give you some hints here ["man dmesg"].) Everyone needs either a
1069 coprocessor or this emulation.
1071 If you don't have a math coprocessor, you need to say Y here; if you
1072 say Y here even though you have a coprocessor, the coprocessor will
1073 be used nevertheless. (This behavior can be changed with the kernel
1074 command line option "no387", which comes handy if your coprocessor
1075 is broken. Try "man bootparam" or see the documentation of your boot
1076 loader (lilo or loadlin) about how to pass options to the kernel at
1077 boot time.) This means that it is a good idea to say Y here if you
1078 intend to use this kernel on different machines.
1080 More information about the internals of the Linux math coprocessor
1081 emulation can be found in <file:arch/x86/math-emu/README>.
1083 If you are not sure, say Y; apart from resulting in a 66 KB bigger
1084 kernel, it won't hurt.
1087 bool "MTRR (Memory Type Range Register) support"
1089 On Intel P6 family processors (Pentium Pro, Pentium II and later)
1090 the Memory Type Range Registers (MTRRs) may be used to control
1091 processor access to memory ranges. This is most useful if you have
1092 a video (VGA) card on a PCI or AGP bus. Enabling write-combining
1093 allows bus write transfers to be combined into a larger transfer
1094 before bursting over the PCI/AGP bus. This can increase performance
1095 of image write operations 2.5 times or more. Saying Y here creates a
1096 /proc/mtrr file which may be used to manipulate your processor's
1097 MTRRs. Typically the X server should use this.
1099 This code has a reasonably generic interface so that similar
1100 control registers on other processors can be easily supported
1103 The Cyrix 6x86, 6x86MX and M II processors have Address Range
1104 Registers (ARRs) which provide a similar functionality to MTRRs. For
1105 these, the ARRs are used to emulate the MTRRs.
1106 The AMD K6-2 (stepping 8 and above) and K6-3 processors have two
1107 MTRRs. The Centaur C6 (WinChip) has 8 MCRs, allowing
1108 write-combining. All of these processors are supported by this code
1109 and it makes sense to say Y here if you have one of them.
1111 Saying Y here also fixes a problem with buggy SMP BIOSes which only
1112 set the MTRRs for the boot CPU and not for the secondary CPUs. This
1113 can lead to all sorts of problems, so it's good to say Y here.
1115 You can safely say Y even if your machine doesn't have MTRRs, you'll
1116 just add about 9 KB to your kernel.
1118 See <file:Documentation/mtrr.txt> for more information.
1120 config MTRR_SANITIZER
1122 prompt "MTRR cleanup support"
1125 Convert MTRR layout from continuous to discrete, so X drivers can
1126 add writeback entries.
1128 Can be disabled with disable_mtrr_cleanup on the kernel command line.
1129 The largest mtrr entry size for a continous block can be set with
1134 config MTRR_SANITIZER_ENABLE_DEFAULT
1135 int "MTRR cleanup enable value (0-1)"
1138 depends on MTRR_SANITIZER
1140 Enable mtrr cleanup default value
1142 config MTRR_SANITIZER_SPARE_REG_NR_DEFAULT
1143 int "MTRR cleanup spare reg num (0-7)"
1146 depends on MTRR_SANITIZER
1148 mtrr cleanup spare entries default, it can be changed via
1149 mtrr_spare_reg_nr=N on the kernel command line.
1153 prompt "x86 PAT support"
1156 Use PAT attributes to setup page level cache control.
1158 PATs are the modern equivalents of MTRRs and are much more
1159 flexible than MTRRs.
1161 Say N here if you see bootup problems (boot crash, boot hang,
1162 spontaneous reboots) or a non-working video driver.
1168 prompt "EFI runtime service support"
1171 This enables the kernel to use EFI runtime services that are
1172 available (such as the EFI variable services).
1174 This option is only useful on systems that have EFI firmware.
1175 In addition, you should use the latest ELILO loader available
1176 at <http://elilo.sourceforge.net> in order to take advantage
1177 of EFI runtime services. However, even with this option, the
1178 resultant kernel should continue to boot on existing non-EFI
1183 prompt "Enable kernel irq balancing"
1184 depends on X86_32 && SMP && X86_IO_APIC
1186 The default yes will allow the kernel to do irq load balancing.
1187 Saying no will keep the kernel from doing irq load balancing.
1191 prompt "Enable seccomp to safely compute untrusted bytecode"
1194 This kernel feature is useful for number crunching applications
1195 that may need to compute untrusted bytecode during their
1196 execution. By using pipes or other transports made available to
1197 the process as file descriptors supporting the read/write
1198 syscalls, it's possible to isolate those applications in
1199 their own address space using seccomp. Once seccomp is
1200 enabled via /proc/<pid>/seccomp, it cannot be disabled
1201 and the task is only allowed to execute a few safe syscalls
1202 defined by each seccomp mode.
1204 If unsure, say Y. Only embedded should say N here.
1206 config CC_STACKPROTECTOR
1207 bool "Enable -fstack-protector buffer overflow detection (EXPERIMENTAL)"
1208 depends on X86_64 && EXPERIMENTAL && BROKEN
1210 This option turns on the -fstack-protector GCC feature. This
1211 feature puts, at the beginning of critical functions, a canary
1212 value on the stack just before the return address, and validates
1213 the value just before actually returning. Stack based buffer
1214 overflows (that need to overwrite this return address) now also
1215 overwrite the canary, which gets detected and the attack is then
1216 neutralized via a kernel panic.
1218 This feature requires gcc version 4.2 or above, or a distribution
1219 gcc with the feature backported. Older versions are automatically
1220 detected and for those versions, this configuration option is ignored.
1222 config CC_STACKPROTECTOR_ALL
1223 bool "Use stack-protector for all functions"
1224 depends on CC_STACKPROTECTOR
1226 Normally, GCC only inserts the canary value protection for
1227 functions that use large-ish on-stack buffers. By enabling
1228 this option, GCC will be asked to do this for ALL functions.
1230 source kernel/Kconfig.hz
1233 bool "kexec system call"
1234 depends on X86_BIOS_REBOOT
1236 kexec is a system call that implements the ability to shutdown your
1237 current kernel, and to start another kernel. It is like a reboot
1238 but it is independent of the system firmware. And like a reboot
1239 you can start any kernel with it, not just Linux.
1241 The name comes from the similarity to the exec system call.
1243 It is an ongoing process to be certain the hardware in a machine
1244 is properly shutdown, so do not be surprised if this code does not
1245 initially work for you. It may help to enable device hotplugging
1246 support. As of this writing the exact hardware interface is
1247 strongly in flux, so no good recommendation can be made.
1250 bool "kernel crash dumps"
1251 depends on X86_64 || (X86_32 && HIGHMEM)
1253 Generate crash dump after being started by kexec.
1254 This should be normally only set in special crash dump kernels
1255 which are loaded in the main kernel with kexec-tools into
1256 a specially reserved region and then later executed after
1257 a crash by kdump/kexec. The crash dump kernel must be compiled
1258 to a memory address not used by the main kernel or BIOS using
1259 PHYSICAL_START, or it must be built as a relocatable image
1260 (CONFIG_RELOCATABLE=y).
1261 For more details see Documentation/kdump/kdump.txt
1264 bool "kexec jump (EXPERIMENTAL)"
1265 depends on EXPERIMENTAL
1266 depends on KEXEC && HIBERNATION && X86_32
1268 Jump between original kernel and kexeced kernel and invoke
1269 code in physical address mode via KEXEC
1271 config PHYSICAL_START
1272 hex "Physical address where the kernel is loaded" if (EMBEDDED || CRASH_DUMP)
1273 default "0x1000000" if X86_NUMAQ
1274 default "0x200000" if X86_64
1277 This gives the physical address where the kernel is loaded.
1279 If kernel is a not relocatable (CONFIG_RELOCATABLE=n) then
1280 bzImage will decompress itself to above physical address and
1281 run from there. Otherwise, bzImage will run from the address where
1282 it has been loaded by the boot loader and will ignore above physical
1285 In normal kdump cases one does not have to set/change this option
1286 as now bzImage can be compiled as a completely relocatable image
1287 (CONFIG_RELOCATABLE=y) and be used to load and run from a different
1288 address. This option is mainly useful for the folks who don't want
1289 to use a bzImage for capturing the crash dump and want to use a
1290 vmlinux instead. vmlinux is not relocatable hence a kernel needs
1291 to be specifically compiled to run from a specific memory area
1292 (normally a reserved region) and this option comes handy.
1294 So if you are using bzImage for capturing the crash dump, leave
1295 the value here unchanged to 0x100000 and set CONFIG_RELOCATABLE=y.
1296 Otherwise if you plan to use vmlinux for capturing the crash dump
1297 change this value to start of the reserved region (Typically 16MB
1298 0x1000000). In other words, it can be set based on the "X" value as
1299 specified in the "crashkernel=YM@XM" command line boot parameter
1300 passed to the panic-ed kernel. Typically this parameter is set as
1301 crashkernel=64M@16M. Please take a look at
1302 Documentation/kdump/kdump.txt for more details about crash dumps.
1304 Usage of bzImage for capturing the crash dump is recommended as
1305 one does not have to build two kernels. Same kernel can be used
1306 as production kernel and capture kernel. Above option should have
1307 gone away after relocatable bzImage support is introduced. But it
1308 is present because there are users out there who continue to use
1309 vmlinux for dump capture. This option should go away down the
1312 Don't change this unless you know what you are doing.
1315 bool "Build a relocatable kernel (EXPERIMENTAL)"
1316 depends on EXPERIMENTAL
1318 This builds a kernel image that retains relocation information
1319 so it can be loaded someplace besides the default 1MB.
1320 The relocations tend to make the kernel binary about 10% larger,
1321 but are discarded at runtime.
1323 One use is for the kexec on panic case where the recovery kernel
1324 must live at a different physical address than the primary
1327 Note: If CONFIG_RELOCATABLE=y, then the kernel runs from the address
1328 it has been loaded at and the compile time physical address
1329 (CONFIG_PHYSICAL_START) is ignored.
1331 config PHYSICAL_ALIGN
1333 prompt "Alignment value to which kernel should be aligned" if X86_32
1334 default "0x100000" if X86_32
1335 default "0x200000" if X86_64
1336 range 0x2000 0x400000
1338 This value puts the alignment restrictions on physical address
1339 where kernel is loaded and run from. Kernel is compiled for an
1340 address which meets above alignment restriction.
1342 If bootloader loads the kernel at a non-aligned address and
1343 CONFIG_RELOCATABLE is set, kernel will move itself to nearest
1344 address aligned to above value and run from there.
1346 If bootloader loads the kernel at a non-aligned address and
1347 CONFIG_RELOCATABLE is not set, kernel will ignore the run time
1348 load address and decompress itself to the address it has been
1349 compiled for and run from there. The address for which kernel is
1350 compiled already meets above alignment restrictions. Hence the
1351 end result is that kernel runs from a physical address meeting
1352 above alignment restrictions.
1354 Don't change this unless you know what you are doing.
1357 bool "Support for suspend on SMP and hot-pluggable CPUs (EXPERIMENTAL)"
1358 depends on SMP && HOTPLUG && EXPERIMENTAL && !X86_VOYAGER
1360 Say Y here to experiment with turning CPUs off and on, and to
1361 enable suspend on SMP systems. CPUs can be controlled through
1362 /sys/devices/system/cpu.
1363 Say N if you want to disable CPU hotplug and don't need to
1368 prompt "Compat VDSO support"
1369 depends on X86_32 || IA32_EMULATION
1371 Map the 32-bit VDSO to the predictable old-style address too.
1373 Say N here if you are running a sufficiently recent glibc
1374 version (2.3.3 or later), to remove the high-mapped
1375 VDSO mapping and to exclusively use the randomized VDSO.
1381 config ARCH_ENABLE_MEMORY_HOTPLUG
1383 depends on X86_64 || (X86_32 && HIGHMEM)
1385 config HAVE_ARCH_EARLY_PFN_TO_NID
1389 menu "Power management options"
1390 depends on !X86_VOYAGER
1392 config ARCH_HIBERNATION_HEADER
1394 depends on X86_64 && HIBERNATION
1396 source "kernel/power/Kconfig"
1398 source "drivers/acpi/Kconfig"
1403 depends on APM || APM_MODULE
1406 tristate "APM (Advanced Power Management) BIOS support"
1407 depends on X86_32 && PM_SLEEP
1409 APM is a BIOS specification for saving power using several different
1410 techniques. This is mostly useful for battery powered laptops with
1411 APM compliant BIOSes. If you say Y here, the system time will be
1412 reset after a RESUME operation, the /proc/apm device will provide
1413 battery status information, and user-space programs will receive
1414 notification of APM "events" (e.g. battery status change).
1416 If you select "Y" here, you can disable actual use of the APM
1417 BIOS by passing the "apm=off" option to the kernel at boot time.
1419 Note that the APM support is almost completely disabled for
1420 machines with more than one CPU.
1422 In order to use APM, you will need supporting software. For location
1423 and more information, read <file:Documentation/power/pm.txt> and the
1424 Battery Powered Linux mini-HOWTO, available from
1425 <http://www.tldp.org/docs.html#howto>.
1427 This driver does not spin down disk drives (see the hdparm(8)
1428 manpage ("man 8 hdparm") for that), and it doesn't turn off
1429 VESA-compliant "green" monitors.
1431 This driver does not support the TI 4000M TravelMate and the ACER
1432 486/DX4/75 because they don't have compliant BIOSes. Many "green"
1433 desktop machines also don't have compliant BIOSes, and this driver
1434 may cause those machines to panic during the boot phase.
1436 Generally, if you don't have a battery in your machine, there isn't
1437 much point in using this driver and you should say N. If you get
1438 random kernel OOPSes or reboots that don't seem to be related to
1439 anything, try disabling/enabling this option (or disabling/enabling
1442 Some other things you should try when experiencing seemingly random,
1445 1) make sure that you have enough swap space and that it is
1447 2) pass the "no-hlt" option to the kernel
1448 3) switch on floating point emulation in the kernel and pass
1449 the "no387" option to the kernel
1450 4) pass the "floppy=nodma" option to the kernel
1451 5) pass the "mem=4M" option to the kernel (thereby disabling
1452 all but the first 4 MB of RAM)
1453 6) make sure that the CPU is not over clocked.
1454 7) read the sig11 FAQ at <http://www.bitwizard.nl/sig11/>
1455 8) disable the cache from your BIOS settings
1456 9) install a fan for the video card or exchange video RAM
1457 10) install a better fan for the CPU
1458 11) exchange RAM chips
1459 12) exchange the motherboard.
1461 To compile this driver as a module, choose M here: the
1462 module will be called apm.
1466 config APM_IGNORE_USER_SUSPEND
1467 bool "Ignore USER SUSPEND"
1469 This option will ignore USER SUSPEND requests. On machines with a
1470 compliant APM BIOS, you want to say N. However, on the NEC Versa M
1471 series notebooks, it is necessary to say Y because of a BIOS bug.
1473 config APM_DO_ENABLE
1474 bool "Enable PM at boot time"
1476 Enable APM features at boot time. From page 36 of the APM BIOS
1477 specification: "When disabled, the APM BIOS does not automatically
1478 power manage devices, enter the Standby State, enter the Suspend
1479 State, or take power saving steps in response to CPU Idle calls."
1480 This driver will make CPU Idle calls when Linux is idle (unless this
1481 feature is turned off -- see "Do CPU IDLE calls", below). This
1482 should always save battery power, but more complicated APM features
1483 will be dependent on your BIOS implementation. You may need to turn
1484 this option off if your computer hangs at boot time when using APM
1485 support, or if it beeps continuously instead of suspending. Turn
1486 this off if you have a NEC UltraLite Versa 33/C or a Toshiba
1487 T400CDT. This is off by default since most machines do fine without
1491 bool "Make CPU Idle calls when idle"
1493 Enable calls to APM CPU Idle/CPU Busy inside the kernel's idle loop.
1494 On some machines, this can activate improved power savings, such as
1495 a slowed CPU clock rate, when the machine is idle. These idle calls
1496 are made after the idle loop has run for some length of time (e.g.,
1497 333 mS). On some machines, this will cause a hang at boot time or
1498 whenever the CPU becomes idle. (On machines with more than one CPU,
1499 this option does nothing.)
1501 config APM_DISPLAY_BLANK
1502 bool "Enable console blanking using APM"
1504 Enable console blanking using the APM. Some laptops can use this to
1505 turn off the LCD backlight when the screen blanker of the Linux
1506 virtual console blanks the screen. Note that this is only used by
1507 the virtual console screen blanker, and won't turn off the backlight
1508 when using the X Window system. This also doesn't have anything to
1509 do with your VESA-compliant power-saving monitor. Further, this
1510 option doesn't work for all laptops -- it might not turn off your
1511 backlight at all, or it might print a lot of errors to the console,
1512 especially if you are using gpm.
1514 config APM_ALLOW_INTS
1515 bool "Allow interrupts during APM BIOS calls"
1517 Normally we disable external interrupts while we are making calls to
1518 the APM BIOS as a measure to lessen the effects of a badly behaving
1519 BIOS implementation. The BIOS should reenable interrupts if it
1520 needs to. Unfortunately, some BIOSes do not -- especially those in
1521 many of the newer IBM Thinkpads. If you experience hangs when you
1522 suspend, try setting this to Y. Otherwise, say N.
1524 config APM_REAL_MODE_POWER_OFF
1525 bool "Use real mode APM BIOS call to power off"
1527 Use real mode APM BIOS calls to switch off the computer. This is
1528 a work-around for a number of buggy BIOSes. Switch this option on if
1529 your computer crashes instead of powering off properly.
1533 source "arch/x86/kernel/cpu/cpufreq/Kconfig"
1535 source "drivers/cpuidle/Kconfig"
1540 menu "Bus options (PCI etc.)"
1545 select ARCH_SUPPORTS_MSI if (X86_LOCAL_APIC && X86_IO_APIC)
1547 Find out whether you have a PCI motherboard. PCI is the name of a
1548 bus system, i.e. the way the CPU talks to the other stuff inside
1549 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
1550 VESA. If you have PCI, say Y, otherwise N.
1553 prompt "PCI access mode"
1554 depends on X86_32 && PCI
1557 On PCI systems, the BIOS can be used to detect the PCI devices and
1558 determine their configuration. However, some old PCI motherboards
1559 have BIOS bugs and may crash if this is done. Also, some embedded
1560 PCI-based systems don't have any BIOS at all. Linux can also try to
1561 detect the PCI hardware directly without using the BIOS.
1563 With this option, you can specify how Linux should detect the
1564 PCI devices. If you choose "BIOS", the BIOS will be used,
1565 if you choose "Direct", the BIOS won't be used, and if you
1566 choose "MMConfig", then PCI Express MMCONFIG will be used.
1567 If you choose "Any", the kernel will try MMCONFIG, then the
1568 direct access method and falls back to the BIOS if that doesn't
1569 work. If unsure, go with the default, which is "Any".
1574 config PCI_GOMMCONFIG
1591 depends on X86_32 && PCI && (PCI_GOBIOS || PCI_GOANY)
1593 # x86-64 doesn't support PCI BIOS access from long mode so always go direct.
1596 depends on PCI && (X86_64 || (PCI_GODIRECT || PCI_GOANY || PCI_GOOLPC))
1600 depends on X86_32 && PCI && ACPI && (PCI_GOMMCONFIG || PCI_GOANY)
1604 depends on PCI && OLPC && (PCI_GOOLPC || PCI_GOANY)
1611 bool "Support mmconfig PCI config space access"
1612 depends on X86_64 && PCI && ACPI
1615 bool "Support for DMA Remapping Devices (EXPERIMENTAL)"
1616 depends on X86_64 && PCI_MSI && ACPI && EXPERIMENTAL
1618 DMA remapping (DMAR) devices support enables independent address
1619 translations for Direct Memory Access (DMA) from devices.
1620 These DMA remapping devices are reported via ACPI tables
1621 and include PCI device scope covered by these DMA
1626 prompt "Support for Graphics workaround"
1629 Current Graphics drivers tend to use physical address
1630 for DMA and avoid using DMA APIs. Setting this config
1631 option permits the IOMMU driver to set a unity map for
1632 all the OS-visible memory. Hence the driver can continue
1633 to use physical addresses for DMA.
1635 config DMAR_FLOPPY_WA
1639 Floppy disk drivers are know to bypass DMA API calls
1640 thereby failing to work when IOMMU is enabled. This
1641 workaround will setup a 1:1 mapping for the first
1642 16M to make floppy (an ISA device) work.
1644 source "drivers/pci/pcie/Kconfig"
1646 source "drivers/pci/Kconfig"
1648 # x86_64 have no ISA slots, but do have ISA-style DMA.
1656 depends on !X86_VOYAGER
1658 Find out whether you have ISA slots on your motherboard. ISA is the
1659 name of a bus system, i.e. the way the CPU talks to the other stuff
1660 inside your box. Other bus systems are PCI, EISA, MicroChannel
1661 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
1662 newer boards don't support it. If you have ISA, say Y, otherwise N.
1668 The Extended Industry Standard Architecture (EISA) bus was
1669 developed as an open alternative to the IBM MicroChannel bus.
1671 The EISA bus provided some of the features of the IBM MicroChannel
1672 bus while maintaining backward compatibility with cards made for
1673 the older ISA bus. The EISA bus saw limited use between 1988 and
1674 1995 when it was made obsolete by the PCI bus.
1676 Say Y here if you are building a kernel for an EISA-based machine.
1680 source "drivers/eisa/Kconfig"
1683 bool "MCA support" if !X86_VOYAGER
1684 default y if X86_VOYAGER
1686 MicroChannel Architecture is found in some IBM PS/2 machines and
1687 laptops. It is a bus system similar to PCI or ISA. See
1688 <file:Documentation/mca.txt> (and especially the web page given
1689 there) before attempting to build an MCA bus kernel.
1691 source "drivers/mca/Kconfig"
1694 tristate "NatSemi SCx200 support"
1695 depends on !X86_VOYAGER
1697 This provides basic support for National Semiconductor's
1698 (now AMD's) Geode processors. The driver probes for the
1699 PCI-IDs of several on-chip devices, so its a good dependency
1700 for other scx200_* drivers.
1702 If compiled as a module, the driver is named scx200.
1704 config SCx200HR_TIMER
1705 tristate "NatSemi SCx200 27MHz High-Resolution Timer Support"
1706 depends on SCx200 && GENERIC_TIME
1709 This driver provides a clocksource built upon the on-chip
1710 27MHz high-resolution timer. Its also a workaround for
1711 NSC Geode SC-1100's buggy TSC, which loses time when the
1712 processor goes idle (as is done by the scheduler). The
1713 other workaround is idle=poll boot option.
1715 config GEODE_MFGPT_TIMER
1717 prompt "Geode Multi-Function General Purpose Timer (MFGPT) events"
1718 depends on MGEODE_LX && GENERIC_TIME && GENERIC_CLOCKEVENTS
1720 This driver provides a clock event source based on the MFGPT
1721 timer(s) in the CS5535 and CS5536 companion chip for the geode.
1722 MFGPTs have a better resolution and max interval than the
1723 generic PIT, and are suitable for use as high-res timers.
1726 bool "One Laptop Per Child support"
1729 Add support for detecting the unique features of the OLPC
1736 depends on AGP_AMD64 || (X86_64 && (GART_IOMMU || (PCI && NUMA)))
1738 source "drivers/pcmcia/Kconfig"
1740 source "drivers/pci/hotplug/Kconfig"
1745 menu "Executable file formats / Emulations"
1747 source "fs/Kconfig.binfmt"
1749 config IA32_EMULATION
1750 bool "IA32 Emulation"
1752 select COMPAT_BINFMT_ELF
1754 Include code to run 32-bit programs under a 64-bit kernel. You should
1755 likely turn this on, unless you're 100% sure that you don't have any
1756 32-bit programs left.
1759 tristate "IA32 a.out support"
1760 depends on IA32_EMULATION
1762 Support old a.out binaries in the 32bit emulation.
1766 depends on IA32_EMULATION
1768 config COMPAT_FOR_U64_ALIGNMENT
1772 config SYSVIPC_COMPAT
1774 depends on X86_64 && COMPAT && SYSVIPC
1779 source "net/Kconfig"
1781 source "drivers/Kconfig"
1783 source "drivers/firmware/Kconfig"
1787 source "arch/x86/Kconfig.debug"
1789 source "security/Kconfig"
1791 source "crypto/Kconfig"
1793 source "arch/x86/kvm/Kconfig"
1795 source "lib/Kconfig"
projects / linux-drm-fsl-dcu.git / blob