2 mainmenu "Linux Kernel Configuration for x86"
6 bool "64-bit kernel" if ARCH = "x86"
7 default ARCH = "x86_64"
9 Say yes to build a 64-bit kernel - formerly known as x86_64
10 Say no to build a 32-bit kernel - formerly known as i386
24 config GENERIC_LOCKBREAK
30 config GENERIC_CMOS_UPDATE
33 config CLOCKSOURCE_WATCHDOG
36 config GENERIC_CLOCKEVENTS
39 config GENERIC_CLOCKEVENTS_BROADCAST
41 depends on X86_64 || (X86_32 && X86_LOCAL_APIC)
43 config LOCKDEP_SUPPORT
46 config STACKTRACE_SUPPORT
49 config HAVE_LATENCYTOP_SUPPORT
52 config SEMAPHORE_SLEEPERS
67 config GENERIC_ISA_DMA
77 config GENERIC_HWEIGHT
83 config ARCH_MAY_HAVE_PC_FDC
89 config RWSEM_GENERIC_SPINLOCK
92 config RWSEM_XCHGADD_ALGORITHM
95 config ARCH_HAS_ILOG2_U32
98 config ARCH_HAS_ILOG2_U64
101 config ARCH_HAS_CPU_IDLE_WAIT
104 config GENERIC_CALIBRATE_DELAY
107 config GENERIC_TIME_VSYSCALL
111 config ARCH_HAS_CPU_RELAX
114 config HAVE_SETUP_PER_CPU_AREA
119 config ARCH_HIBERNATION_POSSIBLE
121 depends on !SMP || !X86_VOYAGER
123 config ARCH_SUSPEND_POSSIBLE
125 depends on !X86_VOYAGER
131 config ARCH_POPULATES_NODE_MAP
138 # Use the generic interrupt handling code in kernel/irq/:
139 config GENERIC_HARDIRQS
143 config GENERIC_IRQ_PROBE
147 config GENERIC_PENDING_IRQ
149 depends on GENERIC_HARDIRQS && SMP
154 depends on SMP && ((X86_32 && !X86_VOYAGER) || X86_64)
159 depends on X86_32 && SMP
163 depends on X86_64 && SMP
168 depends on (X86_32 && !(X86_VISWS || X86_VOYAGER)) || (X86_64 && !MK8)
171 config X86_BIOS_REBOOT
173 depends on X86_32 && !(X86_VISWS || X86_VOYAGER)
176 config X86_TRAMPOLINE
178 depends on X86_SMP || (X86_VOYAGER && SMP)
183 source "init/Kconfig"
185 menu "Processor type and features"
187 source "kernel/time/Kconfig"
190 bool "Symmetric multi-processing support"
192 This enables support for systems with more than one CPU. If you have
193 a system with only one CPU, like most personal computers, say N. If
194 you have a system with more than one CPU, say Y.
196 If you say N here, the kernel will run on single and multiprocessor
197 machines, but will use only one CPU of a multiprocessor machine. If
198 you say Y here, the kernel will run on many, but not all,
199 singleprocessor machines. On a singleprocessor machine, the kernel
200 will run faster if you say N here.
202 Note that if you say Y here and choose architecture "586" or
203 "Pentium" under "Processor family", the kernel will not work on 486
204 architectures. Similarly, multiprocessor kernels for the "PPro"
205 architecture may not work on all Pentium based boards.
207 People using multiprocessor machines who say Y here should also say
208 Y to "Enhanced Real Time Clock Support", below. The "Advanced Power
209 Management" code will be disabled if you say Y here.
211 See also <file:Documentation/i386/IO-APIC.txt>,
212 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
213 <http://www.tldp.org/docs.html#howto>.
215 If you don't know what to do here, say N.
218 prompt "Subarchitecture Type"
224 Choose this option if your computer is a standard PC or compatible.
230 Select this for an AMD Elan processor.
232 Do not use this option for K6/Athlon/Opteron processors!
234 If unsure, choose "PC-compatible" instead.
239 select SMP if !BROKEN
241 Voyager is an MCA-based 32-way capable SMP architecture proprietary
242 to NCR Corp. Machine classes 345x/35xx/4100/51xx are Voyager-based.
246 If you do not specifically know you have a Voyager based machine,
247 say N here, otherwise the kernel you build will not be bootable.
250 bool "NUMAQ (IBM/Sequent)"
255 This option is used for getting Linux to run on a (IBM/Sequent) NUMA
256 multiquad box. This changes the way that processors are bootstrapped,
257 and uses Clustered Logical APIC addressing mode instead of Flat Logical.
258 You will need a new lynxer.elf file to flash your firmware with - send
259 email to <Martin.Bligh@us.ibm.com>.
262 bool "Summit/EXA (IBM x440)"
263 depends on X86_32 && SMP
265 This option is needed for IBM systems that use the Summit/EXA chipset.
266 In particular, it is needed for the x440.
268 If you don't have one of these computers, you should say N here.
269 If you want to build a NUMA kernel, you must select ACPI.
272 bool "Support for other sub-arch SMP systems with more than 8 CPUs"
273 depends on X86_32 && SMP
275 This option is needed for the systems that have more than 8 CPUs
276 and if the system is not of any sub-arch type above.
278 If you don't have such a system, you should say N here.
281 bool "SGI 320/540 (Visual Workstation)"
284 The SGI Visual Workstation series is an IA32-based workstation
285 based on SGI systems chips with some legacy PC hardware attached.
287 Say Y here to create a kernel to run on the SGI 320 or 540.
289 A kernel compiled for the Visual Workstation will not run on PCs
290 and vice versa. See <file:Documentation/sgi-visws.txt> for details.
292 config X86_GENERICARCH
293 bool "Generic architecture (Summit, bigsmp, ES7000, default)"
296 This option compiles in the Summit, bigsmp, ES7000, default subarchitectures.
297 It is intended for a generic binary kernel.
298 If you want a NUMA kernel, select ACPI. We need SRAT for NUMA.
301 bool "Support for Unisys ES7000 IA32 series"
302 depends on X86_32 && SMP
304 Support for Unisys ES7000 systems. Say 'Y' here if this kernel is
305 supposed to run on an IA32-based Unisys ES7000 system.
306 Only choose this option if you have such a system, otherwise you
310 bool "RDC R-321x SoC"
313 select X86_REBOOTFIXUPS
318 This option is needed for RDC R-321x system-on-chip, also known
320 If you don't have one of these chips, you should say N here.
323 bool "Support for ScaleMP vSMP"
324 depends on X86_64 && PCI
326 Support for ScaleMP vSMP systems. Say 'Y' here if this kernel is
327 supposed to run on these EM64T-based machines. Only choose this option
328 if you have one of these machines.
332 config SCHED_NO_NO_OMIT_FRAME_POINTER
334 prompt "Single-depth WCHAN output"
337 Calculate simpler /proc/<PID>/wchan values. If this option
338 is disabled then wchan values will recurse back to the
339 caller function. This provides more accurate wchan values,
340 at the expense of slightly more scheduling overhead.
342 If in doubt, say "Y".
344 menuconfig PARAVIRT_GUEST
345 bool "Paravirtualized guest support"
347 Say Y here to get to see options related to running Linux under
348 various hypervisors. This option alone does not add any kernel code.
350 If you say N, all options in this submenu will be skipped and disabled.
354 source "arch/x86/xen/Kconfig"
357 bool "VMI Guest support"
360 depends on !(X86_VISWS || X86_VOYAGER)
362 VMI provides a paravirtualized interface to the VMware ESX server
363 (it could be used by other hypervisors in theory too, but is not
364 at the moment), by linking the kernel to a GPL-ed ROM module
365 provided by the hypervisor.
367 source "arch/x86/lguest/Kconfig"
370 bool "Enable paravirtualization code"
371 depends on !(X86_VISWS || X86_VOYAGER)
373 This changes the kernel so it can modify itself when it is run
374 under a hypervisor, potentially improving performance significantly
375 over full virtualization. However, when run without a hypervisor
376 the kernel is theoretically slower and slightly larger.
382 depends on X86_32 && ACPI && NUMA && (X86_SUMMIT || X86_GENERICARCH)
385 config HAVE_ARCH_PARSE_SRAT
389 config X86_SUMMIT_NUMA
391 depends on X86_32 && NUMA && (X86_SUMMIT || X86_GENERICARCH)
393 config X86_CYCLONE_TIMER
395 depends on X86_32 && X86_SUMMIT || X86_GENERICARCH
397 config ES7000_CLUSTERED_APIC
399 depends on SMP && X86_ES7000 && MPENTIUMIII
401 source "arch/x86/Kconfig.cpu"
405 prompt "HPET Timer Support" if X86_32
407 Use the IA-PC HPET (High Precision Event Timer) to manage
408 time in preference to the PIT and RTC, if a HPET is
410 HPET is the next generation timer replacing legacy 8254s.
411 The HPET provides a stable time base on SMP
412 systems, unlike the TSC, but it is more expensive to access,
413 as it is off-chip. You can find the HPET spec at
414 <http://www.intel.com/hardwaredesign/hpetspec.htm>.
416 You can safely choose Y here. However, HPET will only be
417 activated if the platform and the BIOS support this feature.
418 Otherwise the 8254 will be used for timing services.
420 Choose N to continue using the legacy 8254 timer.
422 config HPET_EMULATE_RTC
424 depends on HPET_TIMER && (RTC=y || RTC=m || RTC_DRV_CMOS=m || RTC_DRV_CMOS=y)
426 # Mark as embedded because too many people got it wrong.
427 # The code disables itself when not needed.
429 bool "GART IOMMU support" if EMBEDDED
433 depends on X86_64 && PCI
435 Support for full DMA access of devices with 32bit memory access only
436 on systems with more than 3GB. This is usually needed for USB,
437 sound, many IDE/SATA chipsets and some other devices.
438 Provides a driver for the AMD Athlon64/Opteron/Turion/Sempron GART
439 based hardware IOMMU and a software bounce buffer based IOMMU used
440 on Intel systems and as fallback.
441 The code is only active when needed (enough memory and limited
442 device) unless CONFIG_IOMMU_DEBUG or iommu=force is specified
446 bool "IBM Calgary IOMMU support"
448 depends on X86_64 && PCI && EXPERIMENTAL
450 Support for hardware IOMMUs in IBM's xSeries x366 and x460
451 systems. Needed to run systems with more than 3GB of memory
452 properly with 32-bit PCI devices that do not support DAC
453 (Double Address Cycle). Calgary also supports bus level
454 isolation, where all DMAs pass through the IOMMU. This
455 prevents them from going anywhere except their intended
456 destination. This catches hard-to-find kernel bugs and
457 mis-behaving drivers and devices that do not use the DMA-API
458 properly to set up their DMA buffers. The IOMMU can be
459 turned off at boot time with the iommu=off parameter.
460 Normally the kernel will make the right choice by itself.
463 config CALGARY_IOMMU_ENABLED_BY_DEFAULT
465 prompt "Should Calgary be enabled by default?"
466 depends on CALGARY_IOMMU
468 Should Calgary be enabled by default? if you choose 'y', Calgary
469 will be used (if it exists). If you choose 'n', Calgary will not be
470 used even if it exists. If you choose 'n' and would like to use
471 Calgary anyway, pass 'iommu=calgary' on the kernel command line.
475 def_bool (CALGARY_IOMMU || GART_IOMMU)
477 # need this always selected by IOMMU for the VIA workaround
481 Support for software bounce buffers used on x86-64 systems
482 which don't have a hardware IOMMU (e.g. the current generation
483 of Intel's x86-64 CPUs). Using this PCI devices which can only
484 access 32-bits of memory can be used on systems with more than
485 3 GB of memory. If unsure, say Y.
489 int "Maximum number of CPUs (2-255)"
492 default "32" if X86_NUMAQ || X86_SUMMIT || X86_BIGSMP || X86_ES7000
495 This allows you to specify the maximum number of CPUs which this
496 kernel will support. The maximum supported value is 255 and the
497 minimum value which makes sense is 2.
499 This is purely to save memory - each supported CPU adds
500 approximately eight kilobytes to the kernel image.
503 bool "SMT (Hyperthreading) scheduler support"
504 depends on (X86_64 && SMP) || (X86_32 && X86_HT)
506 SMT scheduler support improves the CPU scheduler's decision making
507 when dealing with Intel Pentium 4 chips with HyperThreading at a
508 cost of slightly increased overhead in some places. If unsure say
513 prompt "Multi-core scheduler support"
514 depends on (X86_64 && SMP) || (X86_32 && X86_HT)
516 Multi-core scheduler support improves the CPU scheduler's decision
517 making when dealing with multi-core CPU chips at a cost of slightly
518 increased overhead in some places. If unsure say N here.
520 source "kernel/Kconfig.preempt"
523 bool "Local APIC support on uniprocessors"
524 depends on X86_32 && !SMP && !(X86_VISWS || X86_VOYAGER || X86_GENERICARCH)
526 A local APIC (Advanced Programmable Interrupt Controller) is an
527 integrated interrupt controller in the CPU. If you have a single-CPU
528 system which has a processor with a local APIC, you can say Y here to
529 enable and use it. If you say Y here even though your machine doesn't
530 have a local APIC, then the kernel will still run with no slowdown at
531 all. The local APIC supports CPU-generated self-interrupts (timer,
532 performance counters), and the NMI watchdog which detects hard
536 bool "IO-APIC support on uniprocessors"
537 depends on X86_UP_APIC
539 An IO-APIC (I/O Advanced Programmable Interrupt Controller) is an
540 SMP-capable replacement for PC-style interrupt controllers. Most
541 SMP systems and many recent uniprocessor systems have one.
543 If you have a single-CPU system with an IO-APIC, you can say Y here
544 to use it. If you say Y here even though your machine doesn't have
545 an IO-APIC, then the kernel will still run with no slowdown at all.
547 config X86_LOCAL_APIC
549 depends on X86_64 || (X86_32 && (X86_UP_APIC || ((X86_VISWS || SMP) && !X86_VOYAGER) || X86_GENERICARCH))
553 depends on X86_64 || (X86_32 && (X86_UP_IOAPIC || (SMP && !(X86_VISWS || X86_VOYAGER)) || X86_GENERICARCH))
555 config X86_VISWS_APIC
557 depends on X86_32 && X86_VISWS
560 bool "Machine Check Exception"
561 depends on !X86_VOYAGER
563 Machine Check Exception support allows the processor to notify the
564 kernel if it detects a problem (e.g. overheating, component failure).
565 The action the kernel takes depends on the severity of the problem,
566 ranging from a warning message on the console, to halting the machine.
567 Your processor must be a Pentium or newer to support this - check the
568 flags in /proc/cpuinfo for mce. Note that some older Pentium systems
569 have a design flaw which leads to false MCE events - hence MCE is
570 disabled on all P5 processors, unless explicitly enabled with "mce"
571 as a boot argument. Similarly, if MCE is built in and creates a
572 problem on some new non-standard machine, you can boot with "nomce"
573 to disable it. MCE support simply ignores non-MCE processors like
574 the 386 and 486, so nearly everyone can say Y here.
578 prompt "Intel MCE features"
579 depends on X86_64 && X86_MCE && X86_LOCAL_APIC
581 Additional support for intel specific MCE features such as
586 prompt "AMD MCE features"
587 depends on X86_64 && X86_MCE && X86_LOCAL_APIC
589 Additional support for AMD specific MCE features such as
590 the DRAM Error Threshold.
592 config X86_MCE_NONFATAL
593 tristate "Check for non-fatal errors on AMD Athlon/Duron / Intel Pentium 4"
594 depends on X86_32 && X86_MCE
596 Enabling this feature starts a timer that triggers every 5 seconds which
597 will look at the machine check registers to see if anything happened.
598 Non-fatal problems automatically get corrected (but still logged).
599 Disable this if you don't want to see these messages.
600 Seeing the messages this option prints out may be indicative of dying
601 or out-of-spec (ie, overclocked) hardware.
602 This option only does something on certain CPUs.
603 (AMD Athlon/Duron and Intel Pentium 4)
605 config X86_MCE_P4THERMAL
606 bool "check for P4 thermal throttling interrupt."
607 depends on X86_32 && X86_MCE && (X86_UP_APIC || SMP) && !X86_VISWS
609 Enabling this feature will cause a message to be printed when the P4
610 enters thermal throttling.
613 bool "Enable VM86 support" if EMBEDDED
617 This option is required by programs like DOSEMU to run 16-bit legacy
618 code on X86 processors. It also may be needed by software like
619 XFree86 to initialize some video cards via BIOS. Disabling this
620 option saves about 6k.
623 tristate "Toshiba Laptop support"
626 This adds a driver to safely access the System Management Mode of
627 the CPU on Toshiba portables with a genuine Toshiba BIOS. It does
628 not work on models with a Phoenix BIOS. The System Management Mode
629 is used to set the BIOS and power saving options on Toshiba portables.
631 For information on utilities to make use of this driver see the
632 Toshiba Linux utilities web site at:
633 <http://www.buzzard.org.uk/toshiba/>.
635 Say Y if you intend to run this kernel on a Toshiba portable.
639 tristate "Dell laptop support"
642 This adds a driver to safely access the System Management Mode
643 of the CPU on the Dell Inspiron 8000. The System Management Mode
644 is used to read cpu temperature and cooling fan status and to
645 control the fans on the I8K portables.
647 This driver has been tested only on the Inspiron 8000 but it may
648 also work with other Dell laptops. You can force loading on other
649 models by passing the parameter `force=1' to the module. Use at
652 For information on utilities to make use of this driver see the
653 I8K Linux utilities web site at:
654 <http://people.debian.org/~dz/i8k/>
656 Say Y if you intend to run this kernel on a Dell Inspiron 8000.
659 config X86_REBOOTFIXUPS
661 prompt "Enable X86 board specific fixups for reboot"
662 depends on X86_32 && X86
664 This enables chipset and/or board specific fixups to be done
665 in order to get reboot to work correctly. This is only needed on
666 some combinations of hardware and BIOS. The symptom, for which
667 this config is intended, is when reboot ends with a stalled/hung
670 Currently, the only fixup is for the Geode machines using
671 CS5530A and CS5536 chipsets and the RDC R-321x SoC.
673 Say Y if you want to enable the fixup. Currently, it's safe to
674 enable this option even if you don't need it.
678 tristate "/dev/cpu/microcode - Intel IA32 CPU microcode support"
681 If you say Y here, you will be able to update the microcode on
682 Intel processors in the IA32 family, e.g. Pentium Pro, Pentium II,
683 Pentium III, Pentium 4, Xeon etc. You will obviously need the
684 actual microcode binary data itself which is not shipped with the
687 For latest news and information on obtaining all the required
688 ingredients for this driver, check:
689 <http://www.urbanmyth.org/microcode/>.
691 To compile this driver as a module, choose M here: the
692 module will be called microcode.
694 config MICROCODE_OLD_INTERFACE
699 tristate "/dev/cpu/*/msr - Model-specific register support"
701 This device gives privileged processes access to the x86
702 Model-Specific Registers (MSRs). It is a character device with
703 major 202 and minors 0 to 31 for /dev/cpu/0/msr to /dev/cpu/31/msr.
704 MSR accesses are directed to a specific CPU on multi-processor
708 tristate "/dev/cpu/*/cpuid - CPU information support"
710 This device gives processes access to the x86 CPUID instruction to
711 be executed on a specific processor. It is a character device
712 with major 203 and minors 0 to 31 for /dev/cpu/0/cpuid to
716 prompt "High Memory Support"
717 default HIGHMEM4G if !X86_NUMAQ
718 default HIGHMEM64G if X86_NUMAQ
723 depends on !X86_NUMAQ
725 Linux can use up to 64 Gigabytes of physical memory on x86 systems.
726 However, the address space of 32-bit x86 processors is only 4
727 Gigabytes large. That means that, if you have a large amount of
728 physical memory, not all of it can be "permanently mapped" by the
729 kernel. The physical memory that's not permanently mapped is called
732 If you are compiling a kernel which will never run on a machine with
733 more than 1 Gigabyte total physical RAM, answer "off" here (default
734 choice and suitable for most users). This will result in a "3GB/1GB"
735 split: 3GB are mapped so that each process sees a 3GB virtual memory
736 space and the remaining part of the 4GB virtual memory space is used
737 by the kernel to permanently map as much physical memory as
740 If the machine has between 1 and 4 Gigabytes physical RAM, then
743 If more than 4 Gigabytes is used then answer "64GB" here. This
744 selection turns Intel PAE (Physical Address Extension) mode on.
745 PAE implements 3-level paging on IA32 processors. PAE is fully
746 supported by Linux, PAE mode is implemented on all recent Intel
747 processors (Pentium Pro and better). NOTE: If you say "64GB" here,
748 then the kernel will not boot on CPUs that don't support PAE!
750 The actual amount of total physical memory will either be
751 auto detected or can be forced by using a kernel command line option
752 such as "mem=256M". (Try "man bootparam" or see the documentation of
753 your boot loader (lilo or loadlin) about how to pass options to the
754 kernel at boot time.)
756 If unsure, say "off".
760 depends on !X86_NUMAQ
762 Select this if you have a 32-bit processor and between 1 and 4
763 gigabytes of physical RAM.
767 depends on !M386 && !M486
770 Select this if you have a 32-bit processor and more than 4
771 gigabytes of physical RAM.
776 depends on EXPERIMENTAL
777 prompt "Memory split" if EMBEDDED
781 Select the desired split between kernel and user memory.
783 If the address range available to the kernel is less than the
784 physical memory installed, the remaining memory will be available
785 as "high memory". Accessing high memory is a little more costly
786 than low memory, as it needs to be mapped into the kernel first.
787 Note that increasing the kernel address space limits the range
788 available to user programs, making the address space there
789 tighter. Selecting anything other than the default 3G/1G split
790 will also likely make your kernel incompatible with binary-only
793 If you are not absolutely sure what you are doing, leave this
797 bool "3G/1G user/kernel split"
798 config VMSPLIT_3G_OPT
800 bool "3G/1G user/kernel split (for full 1G low memory)"
802 bool "2G/2G user/kernel split"
803 config VMSPLIT_2G_OPT
805 bool "2G/2G user/kernel split (for full 2G low memory)"
807 bool "1G/3G user/kernel split"
812 default 0xB0000000 if VMSPLIT_3G_OPT
813 default 0x80000000 if VMSPLIT_2G
814 default 0x78000000 if VMSPLIT_2G_OPT
815 default 0x40000000 if VMSPLIT_1G
821 depends on X86_32 && (HIGHMEM64G || HIGHMEM4G)
825 prompt "PAE (Physical Address Extension) Support"
826 depends on X86_32 && !HIGHMEM4G
827 select RESOURCES_64BIT
829 PAE is required for NX support, and furthermore enables
830 larger swapspace support for non-overcommit purposes. It
831 has the cost of more pagetable lookup overhead, and also
832 consumes more pagetable space per process.
834 # Common NUMA Features
836 bool "Numa Memory Allocation and Scheduler Support (EXPERIMENTAL)"
838 depends on X86_64 || (X86_32 && HIGHMEM64G && (X86_NUMAQ || (X86_SUMMIT || X86_GENERICARCH) && ACPI) && EXPERIMENTAL)
840 default y if (X86_NUMAQ || X86_SUMMIT)
842 Enable NUMA (Non Uniform Memory Access) support.
843 The kernel will try to allocate memory used by a CPU on the
844 local memory controller of the CPU and add some more
845 NUMA awareness to the kernel.
847 For i386 this is currently highly experimental and should be only
848 used for kernel development. It might also cause boot failures.
849 For x86_64 this is recommended on all multiprocessor Opteron systems.
850 If the system is EM64T, you should say N unless your system is
853 comment "NUMA (Summit) requires SMP, 64GB highmem support, ACPI"
854 depends on X86_32 && X86_SUMMIT && (!HIGHMEM64G || !ACPI)
858 prompt "Old style AMD Opteron NUMA detection"
859 depends on X86_64 && NUMA && PCI
861 Enable K8 NUMA node topology detection. You should say Y here if
862 you have a multi processor AMD K8 system. This uses an old
863 method to read the NUMA configuration directly from the builtin
864 Northbridge of Opteron. It is recommended to use X86_64_ACPI_NUMA
865 instead, which also takes priority if both are compiled in.
867 config X86_64_ACPI_NUMA
869 prompt "ACPI NUMA detection"
870 depends on X86_64 && NUMA && ACPI && PCI
873 Enable ACPI SRAT based node topology detection.
876 bool "NUMA emulation"
877 depends on X86_64 && NUMA
879 Enable NUMA emulation. A flat machine will be split
880 into virtual nodes when booted with "numa=fake=N", where N is the
881 number of nodes. This is only useful for debugging.
886 default "6" if X86_64
887 default "4" if X86_NUMAQ
889 depends on NEED_MULTIPLE_NODES
891 config HAVE_ARCH_BOOTMEM_NODE
893 depends on X86_32 && NUMA
895 config ARCH_HAVE_MEMORY_PRESENT
897 depends on X86_32 && DISCONTIGMEM
899 config NEED_NODE_MEMMAP_SIZE
901 depends on X86_32 && (DISCONTIGMEM || SPARSEMEM)
903 config HAVE_ARCH_ALLOC_REMAP
905 depends on X86_32 && NUMA
907 config ARCH_FLATMEM_ENABLE
909 depends on X86_32 && ARCH_SELECT_MEMORY_MODEL && X86_PC && !NUMA
911 config ARCH_DISCONTIGMEM_ENABLE
913 depends on NUMA && X86_32
915 config ARCH_DISCONTIGMEM_DEFAULT
917 depends on NUMA && X86_32
919 config ARCH_SPARSEMEM_DEFAULT
923 config ARCH_SPARSEMEM_ENABLE
925 depends on X86_64 || NUMA || (EXPERIMENTAL && X86_PC)
926 select SPARSEMEM_STATIC if X86_32
927 select SPARSEMEM_VMEMMAP_ENABLE if X86_64
929 config ARCH_SELECT_MEMORY_MODEL
931 depends on ARCH_SPARSEMEM_ENABLE
933 config ARCH_MEMORY_PROBE
935 depends on MEMORY_HOTPLUG
940 bool "Allocate 3rd-level pagetables from highmem"
941 depends on X86_32 && (HIGHMEM4G || HIGHMEM64G)
943 The VM uses one page table entry for each page of physical memory.
944 For systems with a lot of RAM, this can be wasteful of precious
945 low memory. Setting this option will put user-space page table
946 entries in high memory.
948 config MATH_EMULATION
950 prompt "Math emulation" if X86_32
952 Linux can emulate a math coprocessor (used for floating point
953 operations) if you don't have one. 486DX and Pentium processors have
954 a math coprocessor built in, 486SX and 386 do not, unless you added
955 a 487DX or 387, respectively. (The messages during boot time can
956 give you some hints here ["man dmesg"].) Everyone needs either a
957 coprocessor or this emulation.
959 If you don't have a math coprocessor, you need to say Y here; if you
960 say Y here even though you have a coprocessor, the coprocessor will
961 be used nevertheless. (This behavior can be changed with the kernel
962 command line option "no387", which comes handy if your coprocessor
963 is broken. Try "man bootparam" or see the documentation of your boot
964 loader (lilo or loadlin) about how to pass options to the kernel at
965 boot time.) This means that it is a good idea to say Y here if you
966 intend to use this kernel on different machines.
968 More information about the internals of the Linux math coprocessor
969 emulation can be found in <file:arch/x86/math-emu/README>.
971 If you are not sure, say Y; apart from resulting in a 66 KB bigger
972 kernel, it won't hurt.
975 bool "MTRR (Memory Type Range Register) support"
977 On Intel P6 family processors (Pentium Pro, Pentium II and later)
978 the Memory Type Range Registers (MTRRs) may be used to control
979 processor access to memory ranges. This is most useful if you have
980 a video (VGA) card on a PCI or AGP bus. Enabling write-combining
981 allows bus write transfers to be combined into a larger transfer
982 before bursting over the PCI/AGP bus. This can increase performance
983 of image write operations 2.5 times or more. Saying Y here creates a
984 /proc/mtrr file which may be used to manipulate your processor's
985 MTRRs. Typically the X server should use this.
987 This code has a reasonably generic interface so that similar
988 control registers on other processors can be easily supported
991 The Cyrix 6x86, 6x86MX and M II processors have Address Range
992 Registers (ARRs) which provide a similar functionality to MTRRs. For
993 these, the ARRs are used to emulate the MTRRs.
994 The AMD K6-2 (stepping 8 and above) and K6-3 processors have two
995 MTRRs. The Centaur C6 (WinChip) has 8 MCRs, allowing
996 write-combining. All of these processors are supported by this code
997 and it makes sense to say Y here if you have one of them.
999 Saying Y here also fixes a problem with buggy SMP BIOSes which only
1000 set the MTRRs for the boot CPU and not for the secondary CPUs. This
1001 can lead to all sorts of problems, so it's good to say Y here.
1003 You can safely say Y even if your machine doesn't have MTRRs, you'll
1004 just add about 9 KB to your kernel.
1006 See <file:Documentation/mtrr.txt> for more information.
1010 prompt "EFI runtime service support"
1013 This enables the kernel to use EFI runtime services that are
1014 available (such as the EFI variable services).
1016 This option is only useful on systems that have EFI firmware.
1017 In addition, you should use the latest ELILO loader available
1018 at <http://elilo.sourceforge.net> in order to take advantage
1019 of EFI runtime services. However, even with this option, the
1020 resultant kernel should continue to boot on existing non-EFI
1025 prompt "Enable kernel irq balancing"
1026 depends on X86_32 && SMP && X86_IO_APIC
1028 The default yes will allow the kernel to do irq load balancing.
1029 Saying no will keep the kernel from doing irq load balancing.
1033 prompt "Enable seccomp to safely compute untrusted bytecode"
1036 This kernel feature is useful for number crunching applications
1037 that may need to compute untrusted bytecode during their
1038 execution. By using pipes or other transports made available to
1039 the process as file descriptors supporting the read/write
1040 syscalls, it's possible to isolate those applications in
1041 their own address space using seccomp. Once seccomp is
1042 enabled via /proc/<pid>/seccomp, it cannot be disabled
1043 and the task is only allowed to execute a few safe syscalls
1044 defined by each seccomp mode.
1046 If unsure, say Y. Only embedded should say N here.
1048 config CC_STACKPROTECTOR
1049 bool "Enable -fstack-protector buffer overflow detection (EXPERIMENTAL)"
1050 depends on X86_64 && EXPERIMENTAL
1052 This option turns on the -fstack-protector GCC feature. This
1053 feature puts, at the beginning of critical functions, a canary
1054 value on the stack just before the return address, and validates
1055 the value just before actually returning. Stack based buffer
1056 overflows (that need to overwrite this return address) now also
1057 overwrite the canary, which gets detected and the attack is then
1058 neutralized via a kernel panic.
1060 This feature requires gcc version 4.2 or above, or a distribution
1061 gcc with the feature backported. Older versions are automatically
1062 detected and for those versions, this configuration option is ignored.
1064 config CC_STACKPROTECTOR_ALL
1065 bool "Use stack-protector for all functions"
1066 depends on CC_STACKPROTECTOR
1068 Normally, GCC only inserts the canary value protection for
1069 functions that use large-ish on-stack buffers. By enabling
1070 this option, GCC will be asked to do this for ALL functions.
1072 source kernel/Kconfig.hz
1075 bool "kexec system call"
1077 kexec is a system call that implements the ability to shutdown your
1078 current kernel, and to start another kernel. It is like a reboot
1079 but it is independent of the system firmware. And like a reboot
1080 you can start any kernel with it, not just Linux.
1082 The name comes from the similarity to the exec system call.
1084 It is an ongoing process to be certain the hardware in a machine
1085 is properly shutdown, so do not be surprised if this code does not
1086 initially work for you. It may help to enable device hotplugging
1087 support. As of this writing the exact hardware interface is
1088 strongly in flux, so no good recommendation can be made.
1091 bool "kernel crash dumps (EXPERIMENTAL)"
1092 depends on EXPERIMENTAL
1093 depends on X86_64 || (X86_32 && HIGHMEM)
1095 Generate crash dump after being started by kexec.
1096 This should be normally only set in special crash dump kernels
1097 which are loaded in the main kernel with kexec-tools into
1098 a specially reserved region and then later executed after
1099 a crash by kdump/kexec. The crash dump kernel must be compiled
1100 to a memory address not used by the main kernel or BIOS using
1101 PHYSICAL_START, or it must be built as a relocatable image
1102 (CONFIG_RELOCATABLE=y).
1103 For more details see Documentation/kdump/kdump.txt
1105 config PHYSICAL_START
1106 hex "Physical address where the kernel is loaded" if (EMBEDDED || CRASH_DUMP)
1107 default "0x1000000" if X86_NUMAQ
1108 default "0x200000" if X86_64
1111 This gives the physical address where the kernel is loaded.
1113 If kernel is a not relocatable (CONFIG_RELOCATABLE=n) then
1114 bzImage will decompress itself to above physical address and
1115 run from there. Otherwise, bzImage will run from the address where
1116 it has been loaded by the boot loader and will ignore above physical
1119 In normal kdump cases one does not have to set/change this option
1120 as now bzImage can be compiled as a completely relocatable image
1121 (CONFIG_RELOCATABLE=y) and be used to load and run from a different
1122 address. This option is mainly useful for the folks who don't want
1123 to use a bzImage for capturing the crash dump and want to use a
1124 vmlinux instead. vmlinux is not relocatable hence a kernel needs
1125 to be specifically compiled to run from a specific memory area
1126 (normally a reserved region) and this option comes handy.
1128 So if you are using bzImage for capturing the crash dump, leave
1129 the value here unchanged to 0x100000 and set CONFIG_RELOCATABLE=y.
1130 Otherwise if you plan to use vmlinux for capturing the crash dump
1131 change this value to start of the reserved region (Typically 16MB
1132 0x1000000). In other words, it can be set based on the "X" value as
1133 specified in the "crashkernel=YM@XM" command line boot parameter
1134 passed to the panic-ed kernel. Typically this parameter is set as
1135 crashkernel=64M@16M. Please take a look at
1136 Documentation/kdump/kdump.txt for more details about crash dumps.
1138 Usage of bzImage for capturing the crash dump is recommended as
1139 one does not have to build two kernels. Same kernel can be used
1140 as production kernel and capture kernel. Above option should have
1141 gone away after relocatable bzImage support is introduced. But it
1142 is present because there are users out there who continue to use
1143 vmlinux for dump capture. This option should go away down the
1146 Don't change this unless you know what you are doing.
1149 bool "Build a relocatable kernel (EXPERIMENTAL)"
1150 depends on EXPERIMENTAL
1152 This builds a kernel image that retains relocation information
1153 so it can be loaded someplace besides the default 1MB.
1154 The relocations tend to make the kernel binary about 10% larger,
1155 but are discarded at runtime.
1157 One use is for the kexec on panic case where the recovery kernel
1158 must live at a different physical address than the primary
1161 Note: If CONFIG_RELOCATABLE=y, then the kernel runs from the address
1162 it has been loaded at and the compile time physical address
1163 (CONFIG_PHYSICAL_START) is ignored.
1165 config PHYSICAL_ALIGN
1167 prompt "Alignment value to which kernel should be aligned" if X86_32
1168 default "0x100000" if X86_32
1169 default "0x200000" if X86_64
1170 range 0x2000 0x400000
1172 This value puts the alignment restrictions on physical address
1173 where kernel is loaded and run from. Kernel is compiled for an
1174 address which meets above alignment restriction.
1176 If bootloader loads the kernel at a non-aligned address and
1177 CONFIG_RELOCATABLE is set, kernel will move itself to nearest
1178 address aligned to above value and run from there.
1180 If bootloader loads the kernel at a non-aligned address and
1181 CONFIG_RELOCATABLE is not set, kernel will ignore the run time
1182 load address and decompress itself to the address it has been
1183 compiled for and run from there. The address for which kernel is
1184 compiled already meets above alignment restrictions. Hence the
1185 end result is that kernel runs from a physical address meeting
1186 above alignment restrictions.
1188 Don't change this unless you know what you are doing.
1191 bool "Support for suspend on SMP and hot-pluggable CPUs (EXPERIMENTAL)"
1192 depends on SMP && HOTPLUG && EXPERIMENTAL && !X86_VOYAGER
1194 Say Y here to experiment with turning CPUs off and on, and to
1195 enable suspend on SMP systems. CPUs can be controlled through
1196 /sys/devices/system/cpu.
1197 Say N if you want to disable CPU hotplug and don't need to
1202 prompt "Compat VDSO support"
1203 depends on X86_32 || IA32_EMULATION
1205 Map the 32-bit VDSO to the predictable old-style address too.
1207 Say N here if you are running a sufficiently recent glibc
1208 version (2.3.3 or later), to remove the high-mapped
1209 VDSO mapping and to exclusively use the randomized VDSO.
1215 config ARCH_ENABLE_MEMORY_HOTPLUG
1217 depends on X86_64 || (X86_32 && HIGHMEM)
1219 config HAVE_ARCH_EARLY_PFN_TO_NID
1223 menu "Power management options"
1224 depends on !X86_VOYAGER
1226 config ARCH_HIBERNATION_HEADER
1228 depends on X86_64 && HIBERNATION
1230 source "kernel/power/Kconfig"
1232 source "drivers/acpi/Kconfig"
1237 depends on APM || APM_MODULE
1240 tristate "APM (Advanced Power Management) BIOS support"
1241 depends on X86_32 && PM_SLEEP && !X86_VISWS
1243 APM is a BIOS specification for saving power using several different
1244 techniques. This is mostly useful for battery powered laptops with
1245 APM compliant BIOSes. If you say Y here, the system time will be
1246 reset after a RESUME operation, the /proc/apm device will provide
1247 battery status information, and user-space programs will receive
1248 notification of APM "events" (e.g. battery status change).
1250 If you select "Y" here, you can disable actual use of the APM
1251 BIOS by passing the "apm=off" option to the kernel at boot time.
1253 Note that the APM support is almost completely disabled for
1254 machines with more than one CPU.
1256 In order to use APM, you will need supporting software. For location
1257 and more information, read <file:Documentation/pm.txt> and the
1258 Battery Powered Linux mini-HOWTO, available from
1259 <http://www.tldp.org/docs.html#howto>.
1261 This driver does not spin down disk drives (see the hdparm(8)
1262 manpage ("man 8 hdparm") for that), and it doesn't turn off
1263 VESA-compliant "green" monitors.
1265 This driver does not support the TI 4000M TravelMate and the ACER
1266 486/DX4/75 because they don't have compliant BIOSes. Many "green"
1267 desktop machines also don't have compliant BIOSes, and this driver
1268 may cause those machines to panic during the boot phase.
1270 Generally, if you don't have a battery in your machine, there isn't
1271 much point in using this driver and you should say N. If you get
1272 random kernel OOPSes or reboots that don't seem to be related to
1273 anything, try disabling/enabling this option (or disabling/enabling
1276 Some other things you should try when experiencing seemingly random,
1279 1) make sure that you have enough swap space and that it is
1281 2) pass the "no-hlt" option to the kernel
1282 3) switch on floating point emulation in the kernel and pass
1283 the "no387" option to the kernel
1284 4) pass the "floppy=nodma" option to the kernel
1285 5) pass the "mem=4M" option to the kernel (thereby disabling
1286 all but the first 4 MB of RAM)
1287 6) make sure that the CPU is not over clocked.
1288 7) read the sig11 FAQ at <http://www.bitwizard.nl/sig11/>
1289 8) disable the cache from your BIOS settings
1290 9) install a fan for the video card or exchange video RAM
1291 10) install a better fan for the CPU
1292 11) exchange RAM chips
1293 12) exchange the motherboard.
1295 To compile this driver as a module, choose M here: the
1296 module will be called apm.
1300 config APM_IGNORE_USER_SUSPEND
1301 bool "Ignore USER SUSPEND"
1303 This option will ignore USER SUSPEND requests. On machines with a
1304 compliant APM BIOS, you want to say N. However, on the NEC Versa M
1305 series notebooks, it is necessary to say Y because of a BIOS bug.
1307 config APM_DO_ENABLE
1308 bool "Enable PM at boot time"
1310 Enable APM features at boot time. From page 36 of the APM BIOS
1311 specification: "When disabled, the APM BIOS does not automatically
1312 power manage devices, enter the Standby State, enter the Suspend
1313 State, or take power saving steps in response to CPU Idle calls."
1314 This driver will make CPU Idle calls when Linux is idle (unless this
1315 feature is turned off -- see "Do CPU IDLE calls", below). This
1316 should always save battery power, but more complicated APM features
1317 will be dependent on your BIOS implementation. You may need to turn
1318 this option off if your computer hangs at boot time when using APM
1319 support, or if it beeps continuously instead of suspending. Turn
1320 this off if you have a NEC UltraLite Versa 33/C or a Toshiba
1321 T400CDT. This is off by default since most machines do fine without
1325 bool "Make CPU Idle calls when idle"
1327 Enable calls to APM CPU Idle/CPU Busy inside the kernel's idle loop.
1328 On some machines, this can activate improved power savings, such as
1329 a slowed CPU clock rate, when the machine is idle. These idle calls
1330 are made after the idle loop has run for some length of time (e.g.,
1331 333 mS). On some machines, this will cause a hang at boot time or
1332 whenever the CPU becomes idle. (On machines with more than one CPU,
1333 this option does nothing.)
1335 config APM_DISPLAY_BLANK
1336 bool "Enable console blanking using APM"
1338 Enable console blanking using the APM. Some laptops can use this to
1339 turn off the LCD backlight when the screen blanker of the Linux
1340 virtual console blanks the screen. Note that this is only used by
1341 the virtual console screen blanker, and won't turn off the backlight
1342 when using the X Window system. This also doesn't have anything to
1343 do with your VESA-compliant power-saving monitor. Further, this
1344 option doesn't work for all laptops -- it might not turn off your
1345 backlight at all, or it might print a lot of errors to the console,
1346 especially if you are using gpm.
1348 config APM_ALLOW_INTS
1349 bool "Allow interrupts during APM BIOS calls"
1351 Normally we disable external interrupts while we are making calls to
1352 the APM BIOS as a measure to lessen the effects of a badly behaving
1353 BIOS implementation. The BIOS should reenable interrupts if it
1354 needs to. Unfortunately, some BIOSes do not -- especially those in
1355 many of the newer IBM Thinkpads. If you experience hangs when you
1356 suspend, try setting this to Y. Otherwise, say N.
1358 config APM_REAL_MODE_POWER_OFF
1359 bool "Use real mode APM BIOS call to power off"
1361 Use real mode APM BIOS calls to switch off the computer. This is
1362 a work-around for a number of buggy BIOSes. Switch this option on if
1363 your computer crashes instead of powering off properly.
1367 source "arch/x86/kernel/cpu/cpufreq/Kconfig"
1369 source "drivers/cpuidle/Kconfig"
1374 menu "Bus options (PCI etc.)"
1377 bool "PCI support" if !X86_VISWS
1378 depends on !X86_VOYAGER
1380 select ARCH_SUPPORTS_MSI if (X86_LOCAL_APIC && X86_IO_APIC)
1382 Find out whether you have a PCI motherboard. PCI is the name of a
1383 bus system, i.e. the way the CPU talks to the other stuff inside
1384 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
1385 VESA. If you have PCI, say Y, otherwise N.
1388 prompt "PCI access mode"
1389 depends on X86_32 && PCI && !X86_VISWS
1392 On PCI systems, the BIOS can be used to detect the PCI devices and
1393 determine their configuration. However, some old PCI motherboards
1394 have BIOS bugs and may crash if this is done. Also, some embedded
1395 PCI-based systems don't have any BIOS at all. Linux can also try to
1396 detect the PCI hardware directly without using the BIOS.
1398 With this option, you can specify how Linux should detect the
1399 PCI devices. If you choose "BIOS", the BIOS will be used,
1400 if you choose "Direct", the BIOS won't be used, and if you
1401 choose "MMConfig", then PCI Express MMCONFIG will be used.
1402 If you choose "Any", the kernel will try MMCONFIG, then the
1403 direct access method and falls back to the BIOS if that doesn't
1404 work. If unsure, go with the default, which is "Any".
1409 config PCI_GOMMCONFIG
1422 depends on X86_32 && !X86_VISWS && PCI && (PCI_GOBIOS || PCI_GOANY)
1424 # x86-64 doesn't support PCI BIOS access from long mode so always go direct.
1427 depends on PCI && (X86_64 || (PCI_GODIRECT || PCI_GOANY) || X86_VISWS)
1431 depends on X86_32 && PCI && ACPI && (PCI_GOMMCONFIG || PCI_GOANY)
1438 bool "Support mmconfig PCI config space access"
1439 depends on X86_64 && PCI && ACPI
1442 bool "Support for DMA Remapping Devices (EXPERIMENTAL)"
1443 depends on X86_64 && PCI_MSI && ACPI && EXPERIMENTAL
1445 DMA remapping (DMAR) devices support enables independent address
1446 translations for Direct Memory Access (DMA) from devices.
1447 These DMA remapping devices are reported via ACPI tables
1448 and include PCI device scope covered by these DMA
1453 prompt "Support for Graphics workaround"
1456 Current Graphics drivers tend to use physical address
1457 for DMA and avoid using DMA APIs. Setting this config
1458 option permits the IOMMU driver to set a unity map for
1459 all the OS-visible memory. Hence the driver can continue
1460 to use physical addresses for DMA.
1462 config DMAR_FLOPPY_WA
1466 Floppy disk drivers are know to bypass DMA API calls
1467 thereby failing to work when IOMMU is enabled. This
1468 workaround will setup a 1:1 mapping for the first
1469 16M to make floppy (an ISA device) work.
1471 source "drivers/pci/pcie/Kconfig"
1473 source "drivers/pci/Kconfig"
1475 # x86_64 have no ISA slots, but do have ISA-style DMA.
1483 depends on !(X86_VOYAGER || X86_VISWS)
1485 Find out whether you have ISA slots on your motherboard. ISA is the
1486 name of a bus system, i.e. the way the CPU talks to the other stuff
1487 inside your box. Other bus systems are PCI, EISA, MicroChannel
1488 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
1489 newer boards don't support it. If you have ISA, say Y, otherwise N.
1495 The Extended Industry Standard Architecture (EISA) bus was
1496 developed as an open alternative to the IBM MicroChannel bus.
1498 The EISA bus provided some of the features of the IBM MicroChannel
1499 bus while maintaining backward compatibility with cards made for
1500 the older ISA bus. The EISA bus saw limited use between 1988 and
1501 1995 when it was made obsolete by the PCI bus.
1503 Say Y here if you are building a kernel for an EISA-based machine.
1507 source "drivers/eisa/Kconfig"
1510 bool "MCA support" if !(X86_VISWS || X86_VOYAGER)
1511 default y if X86_VOYAGER
1513 MicroChannel Architecture is found in some IBM PS/2 machines and
1514 laptops. It is a bus system similar to PCI or ISA. See
1515 <file:Documentation/mca.txt> (and especially the web page given
1516 there) before attempting to build an MCA bus kernel.
1518 source "drivers/mca/Kconfig"
1521 tristate "NatSemi SCx200 support"
1522 depends on !X86_VOYAGER
1524 This provides basic support for National Semiconductor's
1525 (now AMD's) Geode processors. The driver probes for the
1526 PCI-IDs of several on-chip devices, so its a good dependency
1527 for other scx200_* drivers.
1529 If compiled as a module, the driver is named scx200.
1531 config SCx200HR_TIMER
1532 tristate "NatSemi SCx200 27MHz High-Resolution Timer Support"
1533 depends on SCx200 && GENERIC_TIME
1536 This driver provides a clocksource built upon the on-chip
1537 27MHz high-resolution timer. Its also a workaround for
1538 NSC Geode SC-1100's buggy TSC, which loses time when the
1539 processor goes idle (as is done by the scheduler). The
1540 other workaround is idle=poll boot option.
1542 config GEODE_MFGPT_TIMER
1544 prompt "Geode Multi-Function General Purpose Timer (MFGPT) events"
1545 depends on MGEODE_LX && GENERIC_TIME && GENERIC_CLOCKEVENTS
1547 This driver provides a clock event source based on the MFGPT
1548 timer(s) in the CS5535 and CS5536 companion chip for the geode.
1549 MFGPTs have a better resolution and max interval than the
1550 generic PIT, and are suitable for use as high-res timers.
1556 depends on AGP_AMD64 || (X86_64 && (GART_IOMMU || (PCI && NUMA)))
1558 source "drivers/pcmcia/Kconfig"
1560 source "drivers/pci/hotplug/Kconfig"
1565 menu "Executable file formats / Emulations"
1567 source "fs/Kconfig.binfmt"
1569 config IA32_EMULATION
1570 bool "IA32 Emulation"
1572 select COMPAT_BINFMT_ELF
1574 Include code to run 32-bit programs under a 64-bit kernel. You should
1575 likely turn this on, unless you're 100% sure that you don't have any
1576 32-bit programs left.
1579 tristate "IA32 a.out support"
1580 depends on IA32_EMULATION
1582 Support old a.out binaries in the 32bit emulation.
1586 depends on IA32_EMULATION
1588 config COMPAT_FOR_U64_ALIGNMENT
1592 config SYSVIPC_COMPAT
1594 depends on X86_64 && COMPAT && SYSVIPC
1599 source "net/Kconfig"
1601 source "drivers/Kconfig"
1603 source "drivers/firmware/Kconfig"
1607 source "arch/x86/Kconfig.debug"
1609 source "security/Kconfig"
1611 source "crypto/Kconfig"
1613 source "arch/x86/kvm/Kconfig"
1615 source "lib/Kconfig"
projects / deliverable / linux.git / blob