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
22 config GENERIC_LOCKBREAK
28 config GENERIC_CMOS_UPDATE
31 config CLOCKSOURCE_WATCHDOG
34 config GENERIC_CLOCKEVENTS
37 config GENERIC_CLOCKEVENTS_BROADCAST
39 depends on X86_64 || (X86_32 && X86_LOCAL_APIC)
41 config LOCKDEP_SUPPORT
44 config STACKTRACE_SUPPORT
47 config HAVE_LATENCYTOP_SUPPORT
50 config SEMAPHORE_SLEEPERS
65 config GENERIC_ISA_DMA
75 config GENERIC_HWEIGHT
81 config ARCH_MAY_HAVE_PC_FDC
87 config RWSEM_GENERIC_SPINLOCK
90 config RWSEM_XCHGADD_ALGORITHM
93 config ARCH_HAS_ILOG2_U32
96 config ARCH_HAS_ILOG2_U64
99 config GENERIC_CALIBRATE_DELAY
102 config GENERIC_TIME_VSYSCALL
106 config HAVE_SETUP_PER_CPU_AREA
109 config ARCH_SUPPORTS_OPROFILE
115 config ARCH_HIBERNATION_POSSIBLE
117 depends on !SMP || !X86_VOYAGER
119 config ARCH_SUSPEND_POSSIBLE
121 depends on !X86_VOYAGER
127 config ARCH_POPULATES_NODE_MAP
134 # Use the generic interrupt handling code in kernel/irq/:
135 config GENERIC_HARDIRQS
139 config GENERIC_IRQ_PROBE
143 config GENERIC_PENDING_IRQ
145 depends on GENERIC_HARDIRQS && SMP
150 depends on SMP && ((X86_32 && !X86_VOYAGER) || X86_64)
155 depends on X86_32 && SMP
159 depends on X86_64 && SMP
164 depends on (X86_32 && !(X86_VISWS || X86_VOYAGER)) || (X86_64 && !MK8)
167 config X86_BIOS_REBOOT
169 depends on X86_32 && !(X86_VISWS || X86_VOYAGER)
172 config X86_TRAMPOLINE
174 depends on X86_SMP || (X86_VOYAGER && SMP)
179 source "init/Kconfig"
181 menu "Processor type and features"
183 source "kernel/time/Kconfig"
186 bool "Symmetric multi-processing support"
188 This enables support for systems with more than one CPU. If you have
189 a system with only one CPU, like most personal computers, say N. If
190 you have a system with more than one CPU, say Y.
192 If you say N here, the kernel will run on single and multiprocessor
193 machines, but will use only one CPU of a multiprocessor machine. If
194 you say Y here, the kernel will run on many, but not all,
195 singleprocessor machines. On a singleprocessor machine, the kernel
196 will run faster if you say N here.
198 Note that if you say Y here and choose architecture "586" or
199 "Pentium" under "Processor family", the kernel will not work on 486
200 architectures. Similarly, multiprocessor kernels for the "PPro"
201 architecture may not work on all Pentium based boards.
203 People using multiprocessor machines who say Y here should also say
204 Y to "Enhanced Real Time Clock Support", below. The "Advanced Power
205 Management" code will be disabled if you say Y here.
207 See also the <file:Documentation/smp.txt>,
208 <file:Documentation/i386/IO-APIC.txt>,
209 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
210 <http://www.tldp.org/docs.html#howto>.
212 If you don't know what to do here, say N.
215 prompt "Subarchitecture Type"
221 Choose this option if your computer is a standard PC or compatible.
227 Select this for an AMD Elan processor.
229 Do not use this option for K6/Athlon/Opteron processors!
231 If unsure, choose "PC-compatible" instead.
236 select SMP if !BROKEN
238 Voyager is an MCA-based 32-way capable SMP architecture proprietary
239 to NCR Corp. Machine classes 345x/35xx/4100/51xx are Voyager-based.
243 If you do not specifically know you have a Voyager based machine,
244 say N here, otherwise the kernel you build will not be bootable.
247 bool "NUMAQ (IBM/Sequent)"
252 This option is used for getting Linux to run on a (IBM/Sequent) NUMA
253 multiquad box. This changes the way that processors are bootstrapped,
254 and uses Clustered Logical APIC addressing mode instead of Flat Logical.
255 You will need a new lynxer.elf file to flash your firmware with - send
256 email to <Martin.Bligh@us.ibm.com>.
259 bool "Summit/EXA (IBM x440)"
260 depends on X86_32 && SMP
262 This option is needed for IBM systems that use the Summit/EXA chipset.
263 In particular, it is needed for the x440.
265 If you don't have one of these computers, you should say N here.
266 If you want to build a NUMA kernel, you must select ACPI.
269 bool "Support for other sub-arch SMP systems with more than 8 CPUs"
270 depends on X86_32 && SMP
272 This option is needed for the systems that have more than 8 CPUs
273 and if the system is not of any sub-arch type above.
275 If you don't have such a system, you should say N here.
278 bool "SGI 320/540 (Visual Workstation)"
281 The SGI Visual Workstation series is an IA32-based workstation
282 based on SGI systems chips with some legacy PC hardware attached.
284 Say Y here to create a kernel to run on the SGI 320 or 540.
286 A kernel compiled for the Visual Workstation will not run on PCs
287 and vice versa. See <file:Documentation/sgi-visws.txt> for details.
289 config X86_GENERICARCH
290 bool "Generic architecture (Summit, bigsmp, ES7000, default)"
293 This option compiles in the Summit, bigsmp, ES7000, default subarchitectures.
294 It is intended for a generic binary kernel.
295 If you want a NUMA kernel, select ACPI. We need SRAT for NUMA.
298 bool "Support for Unisys ES7000 IA32 series"
299 depends on X86_32 && SMP
301 Support for Unisys ES7000 systems. Say 'Y' here if this kernel is
302 supposed to run on an IA32-based Unisys ES7000 system.
303 Only choose this option if you have such a system, otherwise you
307 bool "RDC R-321x SoC"
310 select X86_REBOOTFIXUPS
314 This option is needed for RDC R-321x system-on-chip, also known
316 If you don't have one of these chips, you should say N here.
319 bool "Support for ScaleMP vSMP"
320 depends on X86_64 && PCI
322 Support for ScaleMP vSMP systems. Say 'Y' here if this kernel is
323 supposed to run on these EM64T-based machines. Only choose this option
324 if you have one of these machines.
328 config SCHED_NO_NO_OMIT_FRAME_POINTER
330 prompt "Single-depth WCHAN output"
333 Calculate simpler /proc/<PID>/wchan values. If this option
334 is disabled then wchan values will recurse back to the
335 caller function. This provides more accurate wchan values,
336 at the expense of slightly more scheduling overhead.
338 If in doubt, say "Y".
340 menuconfig PARAVIRT_GUEST
341 bool "Paravirtualized guest support"
343 Say Y here to get to see options related to running Linux under
344 various hypervisors. This option alone does not add any kernel code.
346 If you say N, all options in this submenu will be skipped and disabled.
350 source "arch/x86/xen/Kconfig"
353 bool "VMI Guest support"
356 depends on !(X86_VISWS || X86_VOYAGER)
358 VMI provides a paravirtualized interface to the VMware ESX server
359 (it could be used by other hypervisors in theory too, but is not
360 at the moment), by linking the kernel to a GPL-ed ROM module
361 provided by the hypervisor.
363 source "arch/x86/lguest/Kconfig"
366 bool "Enable paravirtualization code"
367 depends on !(X86_VISWS || X86_VOYAGER)
369 This changes the kernel so it can modify itself when it is run
370 under a hypervisor, potentially improving performance significantly
371 over full virtualization. However, when run without a hypervisor
372 the kernel is theoretically slower and slightly larger.
378 depends on X86_32 && ACPI && NUMA && (X86_SUMMIT || X86_GENERICARCH)
381 config HAVE_ARCH_PARSE_SRAT
385 config X86_SUMMIT_NUMA
387 depends on X86_32 && NUMA && (X86_SUMMIT || X86_GENERICARCH)
389 config X86_CYCLONE_TIMER
391 depends on X86_32 && X86_SUMMIT || X86_GENERICARCH
393 config ES7000_CLUSTERED_APIC
395 depends on SMP && X86_ES7000 && MPENTIUMIII
397 source "arch/x86/Kconfig.cpu"
401 prompt "HPET Timer Support" if X86_32
403 Use the IA-PC HPET (High Precision Event Timer) to manage
404 time in preference to the PIT and RTC, if a HPET is
406 HPET is the next generation timer replacing legacy 8254s.
407 The HPET provides a stable time base on SMP
408 systems, unlike the TSC, but it is more expensive to access,
409 as it is off-chip. You can find the HPET spec at
410 <http://www.intel.com/hardwaredesign/hpetspec.htm>.
412 You can safely choose Y here. However, HPET will only be
413 activated if the platform and the BIOS support this feature.
414 Otherwise the 8254 will be used for timing services.
416 Choose N to continue using the legacy 8254 timer.
418 config HPET_EMULATE_RTC
420 depends on HPET_TIMER && (RTC=y || RTC=m)
422 # Mark as embedded because too many people got it wrong.
423 # The code disables itself when not needed.
425 bool "GART IOMMU support" if EMBEDDED
429 depends on X86_64 && PCI
431 Support for full DMA access of devices with 32bit memory access only
432 on systems with more than 3GB. This is usually needed for USB,
433 sound, many IDE/SATA chipsets and some other devices.
434 Provides a driver for the AMD Athlon64/Opteron/Turion/Sempron GART
435 based hardware IOMMU and a software bounce buffer based IOMMU used
436 on Intel systems and as fallback.
437 The code is only active when needed (enough memory and limited
438 device) unless CONFIG_IOMMU_DEBUG or iommu=force is specified
442 bool "IBM Calgary IOMMU support"
444 depends on X86_64 && PCI && EXPERIMENTAL
446 Support for hardware IOMMUs in IBM's xSeries x366 and x460
447 systems. Needed to run systems with more than 3GB of memory
448 properly with 32-bit PCI devices that do not support DAC
449 (Double Address Cycle). Calgary also supports bus level
450 isolation, where all DMAs pass through the IOMMU. This
451 prevents them from going anywhere except their intended
452 destination. This catches hard-to-find kernel bugs and
453 mis-behaving drivers and devices that do not use the DMA-API
454 properly to set up their DMA buffers. The IOMMU can be
455 turned off at boot time with the iommu=off parameter.
456 Normally the kernel will make the right choice by itself.
459 config CALGARY_IOMMU_ENABLED_BY_DEFAULT
461 prompt "Should Calgary be enabled by default?"
462 depends on CALGARY_IOMMU
464 Should Calgary be enabled by default? if you choose 'y', Calgary
465 will be used (if it exists). If you choose 'n', Calgary will not be
466 used even if it exists. If you choose 'n' and would like to use
467 Calgary anyway, pass 'iommu=calgary' on the kernel command line.
470 # need this always selected by IOMMU for the VIA workaround
474 Support for software bounce buffers used on x86-64 systems
475 which don't have a hardware IOMMU (e.g. the current generation
476 of Intel's x86-64 CPUs). Using this PCI devices which can only
477 access 32-bits of memory can be used on systems with more than
478 3 GB of memory. If unsure, say Y.
482 int "Maximum number of CPUs (2-255)"
485 default "32" if X86_NUMAQ || X86_SUMMIT || X86_BIGSMP || X86_ES7000
488 This allows you to specify the maximum number of CPUs which this
489 kernel will support. The maximum supported value is 255 and the
490 minimum value which makes sense is 2.
492 This is purely to save memory - each supported CPU adds
493 approximately eight kilobytes to the kernel image.
496 bool "SMT (Hyperthreading) scheduler support"
497 depends on (X86_64 && SMP) || (X86_32 && X86_HT)
499 SMT scheduler support improves the CPU scheduler's decision making
500 when dealing with Intel Pentium 4 chips with HyperThreading at a
501 cost of slightly increased overhead in some places. If unsure say
506 prompt "Multi-core scheduler support"
507 depends on (X86_64 && SMP) || (X86_32 && X86_HT)
509 Multi-core scheduler support improves the CPU scheduler's decision
510 making when dealing with multi-core CPU chips at a cost of slightly
511 increased overhead in some places. If unsure say N here.
513 source "kernel/Kconfig.preempt"
516 bool "Local APIC support on uniprocessors"
517 depends on X86_32 && !SMP && !(X86_VISWS || X86_VOYAGER || X86_GENERICARCH)
519 A local APIC (Advanced Programmable Interrupt Controller) is an
520 integrated interrupt controller in the CPU. If you have a single-CPU
521 system which has a processor with a local APIC, you can say Y here to
522 enable and use it. If you say Y here even though your machine doesn't
523 have a local APIC, then the kernel will still run with no slowdown at
524 all. The local APIC supports CPU-generated self-interrupts (timer,
525 performance counters), and the NMI watchdog which detects hard
529 bool "IO-APIC support on uniprocessors"
530 depends on X86_UP_APIC
532 An IO-APIC (I/O Advanced Programmable Interrupt Controller) is an
533 SMP-capable replacement for PC-style interrupt controllers. Most
534 SMP systems and many recent uniprocessor systems have one.
536 If you have a single-CPU system with an IO-APIC, you can say Y here
537 to use it. If you say Y here even though your machine doesn't have
538 an IO-APIC, then the kernel will still run with no slowdown at all.
540 config X86_LOCAL_APIC
542 depends on X86_64 || (X86_32 && (X86_UP_APIC || ((X86_VISWS || SMP) && !X86_VOYAGER) || X86_GENERICARCH))
546 depends on X86_64 || (X86_32 && (X86_UP_IOAPIC || (SMP && !(X86_VISWS || X86_VOYAGER)) || X86_GENERICARCH))
548 config X86_VISWS_APIC
550 depends on X86_32 && X86_VISWS
553 bool "Machine Check Exception"
554 depends on !X86_VOYAGER
556 Machine Check Exception support allows the processor to notify the
557 kernel if it detects a problem (e.g. overheating, component failure).
558 The action the kernel takes depends on the severity of the problem,
559 ranging from a warning message on the console, to halting the machine.
560 Your processor must be a Pentium or newer to support this - check the
561 flags in /proc/cpuinfo for mce. Note that some older Pentium systems
562 have a design flaw which leads to false MCE events - hence MCE is
563 disabled on all P5 processors, unless explicitly enabled with "mce"
564 as a boot argument. Similarly, if MCE is built in and creates a
565 problem on some new non-standard machine, you can boot with "nomce"
566 to disable it. MCE support simply ignores non-MCE processors like
567 the 386 and 486, so nearly everyone can say Y here.
571 prompt "Intel MCE features"
572 depends on X86_64 && X86_MCE && X86_LOCAL_APIC
574 Additional support for intel specific MCE features such as
579 prompt "AMD MCE features"
580 depends on X86_64 && X86_MCE && X86_LOCAL_APIC
582 Additional support for AMD specific MCE features such as
583 the DRAM Error Threshold.
585 config X86_MCE_NONFATAL
586 tristate "Check for non-fatal errors on AMD Athlon/Duron / Intel Pentium 4"
587 depends on X86_32 && X86_MCE
589 Enabling this feature starts a timer that triggers every 5 seconds which
590 will look at the machine check registers to see if anything happened.
591 Non-fatal problems automatically get corrected (but still logged).
592 Disable this if you don't want to see these messages.
593 Seeing the messages this option prints out may be indicative of dying
594 or out-of-spec (ie, overclocked) hardware.
595 This option only does something on certain CPUs.
596 (AMD Athlon/Duron and Intel Pentium 4)
598 config X86_MCE_P4THERMAL
599 bool "check for P4 thermal throttling interrupt."
600 depends on X86_32 && X86_MCE && (X86_UP_APIC || SMP) && !X86_VISWS
602 Enabling this feature will cause a message to be printed when the P4
603 enters thermal throttling.
606 bool "Enable VM86 support" if EMBEDDED
610 This option is required by programs like DOSEMU to run 16-bit legacy
611 code on X86 processors. It also may be needed by software like
612 XFree86 to initialize some video cards via BIOS. Disabling this
613 option saves about 6k.
616 tristate "Toshiba Laptop support"
619 This adds a driver to safely access the System Management Mode of
620 the CPU on Toshiba portables with a genuine Toshiba BIOS. It does
621 not work on models with a Phoenix BIOS. The System Management Mode
622 is used to set the BIOS and power saving options on Toshiba portables.
624 For information on utilities to make use of this driver see the
625 Toshiba Linux utilities web site at:
626 <http://www.buzzard.org.uk/toshiba/>.
628 Say Y if you intend to run this kernel on a Toshiba portable.
632 tristate "Dell laptop support"
635 This adds a driver to safely access the System Management Mode
636 of the CPU on the Dell Inspiron 8000. The System Management Mode
637 is used to read cpu temperature and cooling fan status and to
638 control the fans on the I8K portables.
640 This driver has been tested only on the Inspiron 8000 but it may
641 also work with other Dell laptops. You can force loading on other
642 models by passing the parameter `force=1' to the module. Use at
645 For information on utilities to make use of this driver see the
646 I8K Linux utilities web site at:
647 <http://people.debian.org/~dz/i8k/>
649 Say Y if you intend to run this kernel on a Dell Inspiron 8000.
652 config X86_REBOOTFIXUPS
654 prompt "Enable X86 board specific fixups for reboot"
655 depends on X86_32 && X86
657 This enables chipset and/or board specific fixups to be done
658 in order to get reboot to work correctly. This is only needed on
659 some combinations of hardware and BIOS. The symptom, for which
660 this config is intended, is when reboot ends with a stalled/hung
663 Currently, the only fixup is for the Geode machines using
664 CS5530A and CS5536 chipsets and the RDC R-321x SoC.
666 Say Y if you want to enable the fixup. Currently, it's safe to
667 enable this option even if you don't need it.
671 tristate "/dev/cpu/microcode - Intel IA32 CPU microcode support"
674 If you say Y here, you will be able to update the microcode on
675 Intel processors in the IA32 family, e.g. Pentium Pro, Pentium II,
676 Pentium III, Pentium 4, Xeon etc. You will obviously need the
677 actual microcode binary data itself which is not shipped with the
680 For latest news and information on obtaining all the required
681 ingredients for this driver, check:
682 <http://www.urbanmyth.org/microcode/>.
684 To compile this driver as a module, choose M here: the
685 module will be called microcode.
687 config MICROCODE_OLD_INTERFACE
692 tristate "/dev/cpu/*/msr - Model-specific register support"
694 This device gives privileged processes access to the x86
695 Model-Specific Registers (MSRs). It is a character device with
696 major 202 and minors 0 to 31 for /dev/cpu/0/msr to /dev/cpu/31/msr.
697 MSR accesses are directed to a specific CPU on multi-processor
701 tristate "/dev/cpu/*/cpuid - CPU information support"
703 This device gives processes access to the x86 CPUID instruction to
704 be executed on a specific processor. It is a character device
705 with major 203 and minors 0 to 31 for /dev/cpu/0/cpuid to
709 prompt "High Memory Support"
710 default HIGHMEM4G if !X86_NUMAQ
711 default HIGHMEM64G if X86_NUMAQ
716 depends on !X86_NUMAQ
718 Linux can use up to 64 Gigabytes of physical memory on x86 systems.
719 However, the address space of 32-bit x86 processors is only 4
720 Gigabytes large. That means that, if you have a large amount of
721 physical memory, not all of it can be "permanently mapped" by the
722 kernel. The physical memory that's not permanently mapped is called
725 If you are compiling a kernel which will never run on a machine with
726 more than 1 Gigabyte total physical RAM, answer "off" here (default
727 choice and suitable for most users). This will result in a "3GB/1GB"
728 split: 3GB are mapped so that each process sees a 3GB virtual memory
729 space and the remaining part of the 4GB virtual memory space is used
730 by the kernel to permanently map as much physical memory as
733 If the machine has between 1 and 4 Gigabytes physical RAM, then
736 If more than 4 Gigabytes is used then answer "64GB" here. This
737 selection turns Intel PAE (Physical Address Extension) mode on.
738 PAE implements 3-level paging on IA32 processors. PAE is fully
739 supported by Linux, PAE mode is implemented on all recent Intel
740 processors (Pentium Pro and better). NOTE: If you say "64GB" here,
741 then the kernel will not boot on CPUs that don't support PAE!
743 The actual amount of total physical memory will either be
744 auto detected or can be forced by using a kernel command line option
745 such as "mem=256M". (Try "man bootparam" or see the documentation of
746 your boot loader (lilo or loadlin) about how to pass options to the
747 kernel at boot time.)
749 If unsure, say "off".
753 depends on !X86_NUMAQ
755 Select this if you have a 32-bit processor and between 1 and 4
756 gigabytes of physical RAM.
760 depends on !M386 && !M486
763 Select this if you have a 32-bit processor and more than 4
764 gigabytes of physical RAM.
769 depends on EXPERIMENTAL
770 prompt "Memory split" if EMBEDDED
774 Select the desired split between kernel and user memory.
776 If the address range available to the kernel is less than the
777 physical memory installed, the remaining memory will be available
778 as "high memory". Accessing high memory is a little more costly
779 than low memory, as it needs to be mapped into the kernel first.
780 Note that increasing the kernel address space limits the range
781 available to user programs, making the address space there
782 tighter. Selecting anything other than the default 3G/1G split
783 will also likely make your kernel incompatible with binary-only
786 If you are not absolutely sure what you are doing, leave this
790 bool "3G/1G user/kernel split"
791 config VMSPLIT_3G_OPT
793 bool "3G/1G user/kernel split (for full 1G low memory)"
795 bool "2G/2G user/kernel split"
796 config VMSPLIT_2G_OPT
798 bool "2G/2G user/kernel split (for full 2G low memory)"
800 bool "1G/3G user/kernel split"
805 default 0xB0000000 if VMSPLIT_3G_OPT
806 default 0x80000000 if VMSPLIT_2G
807 default 0x78000000 if VMSPLIT_2G_OPT
808 default 0x40000000 if VMSPLIT_1G
814 depends on X86_32 && (HIGHMEM64G || HIGHMEM4G)
818 prompt "PAE (Physical Address Extension) Support"
819 depends on X86_32 && !HIGHMEM4G
820 select RESOURCES_64BIT
822 PAE is required for NX support, and furthermore enables
823 larger swapspace support for non-overcommit purposes. It
824 has the cost of more pagetable lookup overhead, and also
825 consumes more pagetable space per process.
827 # Common NUMA Features
829 bool "Numa Memory Allocation and Scheduler Support (EXPERIMENTAL)"
831 depends on X86_64 || (X86_32 && HIGHMEM64G && (X86_NUMAQ || (X86_SUMMIT || X86_GENERICARCH) && ACPI) && EXPERIMENTAL)
833 default y if (X86_NUMAQ || X86_SUMMIT)
835 Enable NUMA (Non Uniform Memory Access) support.
836 The kernel will try to allocate memory used by a CPU on the
837 local memory controller of the CPU and add some more
838 NUMA awareness to the kernel.
840 For i386 this is currently highly experimental and should be only
841 used for kernel development. It might also cause boot failures.
842 For x86_64 this is recommended on all multiprocessor Opteron systems.
843 If the system is EM64T, you should say N unless your system is
846 comment "NUMA (Summit) requires SMP, 64GB highmem support, ACPI"
847 depends on X86_32 && X86_SUMMIT && (!HIGHMEM64G || !ACPI)
851 prompt "Old style AMD Opteron NUMA detection"
852 depends on X86_64 && NUMA && PCI
854 Enable K8 NUMA node topology detection. You should say Y here if
855 you have a multi processor AMD K8 system. This uses an old
856 method to read the NUMA configuration directly from the builtin
857 Northbridge of Opteron. It is recommended to use X86_64_ACPI_NUMA
858 instead, which also takes priority if both are compiled in.
860 config X86_64_ACPI_NUMA
862 prompt "ACPI NUMA detection"
863 depends on X86_64 && NUMA && ACPI && PCI
866 Enable ACPI SRAT based node topology detection.
869 bool "NUMA emulation"
870 depends on X86_64 && NUMA
872 Enable NUMA emulation. A flat machine will be split
873 into virtual nodes when booted with "numa=fake=N", where N is the
874 number of nodes. This is only useful for debugging.
879 default "6" if X86_64
880 default "4" if X86_NUMAQ
882 depends on NEED_MULTIPLE_NODES
884 config HAVE_ARCH_BOOTMEM_NODE
886 depends on X86_32 && NUMA
888 config ARCH_HAVE_MEMORY_PRESENT
890 depends on X86_32 && DISCONTIGMEM
892 config NEED_NODE_MEMMAP_SIZE
894 depends on X86_32 && (DISCONTIGMEM || SPARSEMEM)
896 config HAVE_ARCH_ALLOC_REMAP
898 depends on X86_32 && NUMA
900 config ARCH_FLATMEM_ENABLE
902 depends on X86_32 && ARCH_SELECT_MEMORY_MODEL && X86_PC && !NUMA
904 config ARCH_DISCONTIGMEM_ENABLE
906 depends on NUMA && X86_32
908 config ARCH_DISCONTIGMEM_DEFAULT
910 depends on NUMA && X86_32
912 config ARCH_SPARSEMEM_DEFAULT
916 config ARCH_SPARSEMEM_ENABLE
918 depends on X86_64 || NUMA || (EXPERIMENTAL && X86_PC)
919 select SPARSEMEM_STATIC if X86_32
920 select SPARSEMEM_VMEMMAP_ENABLE if X86_64
922 config ARCH_SELECT_MEMORY_MODEL
924 depends on ARCH_SPARSEMEM_ENABLE
926 config ARCH_MEMORY_PROBE
928 depends on MEMORY_HOTPLUG
933 bool "Allocate 3rd-level pagetables from highmem"
934 depends on X86_32 && (HIGHMEM4G || HIGHMEM64G)
936 The VM uses one page table entry for each page of physical memory.
937 For systems with a lot of RAM, this can be wasteful of precious
938 low memory. Setting this option will put user-space page table
939 entries in high memory.
941 config MATH_EMULATION
943 prompt "Math emulation" if X86_32
945 Linux can emulate a math coprocessor (used for floating point
946 operations) if you don't have one. 486DX and Pentium processors have
947 a math coprocessor built in, 486SX and 386 do not, unless you added
948 a 487DX or 387, respectively. (The messages during boot time can
949 give you some hints here ["man dmesg"].) Everyone needs either a
950 coprocessor or this emulation.
952 If you don't have a math coprocessor, you need to say Y here; if you
953 say Y here even though you have a coprocessor, the coprocessor will
954 be used nevertheless. (This behavior can be changed with the kernel
955 command line option "no387", which comes handy if your coprocessor
956 is broken. Try "man bootparam" or see the documentation of your boot
957 loader (lilo or loadlin) about how to pass options to the kernel at
958 boot time.) This means that it is a good idea to say Y here if you
959 intend to use this kernel on different machines.
961 More information about the internals of the Linux math coprocessor
962 emulation can be found in <file:arch/x86/math-emu/README>.
964 If you are not sure, say Y; apart from resulting in a 66 KB bigger
965 kernel, it won't hurt.
968 bool "MTRR (Memory Type Range Register) support"
970 On Intel P6 family processors (Pentium Pro, Pentium II and later)
971 the Memory Type Range Registers (MTRRs) may be used to control
972 processor access to memory ranges. This is most useful if you have
973 a video (VGA) card on a PCI or AGP bus. Enabling write-combining
974 allows bus write transfers to be combined into a larger transfer
975 before bursting over the PCI/AGP bus. This can increase performance
976 of image write operations 2.5 times or more. Saying Y here creates a
977 /proc/mtrr file which may be used to manipulate your processor's
978 MTRRs. Typically the X server should use this.
980 This code has a reasonably generic interface so that similar
981 control registers on other processors can be easily supported
984 The Cyrix 6x86, 6x86MX and M II processors have Address Range
985 Registers (ARRs) which provide a similar functionality to MTRRs. For
986 these, the ARRs are used to emulate the MTRRs.
987 The AMD K6-2 (stepping 8 and above) and K6-3 processors have two
988 MTRRs. The Centaur C6 (WinChip) has 8 MCRs, allowing
989 write-combining. All of these processors are supported by this code
990 and it makes sense to say Y here if you have one of them.
992 Saying Y here also fixes a problem with buggy SMP BIOSes which only
993 set the MTRRs for the boot CPU and not for the secondary CPUs. This
994 can lead to all sorts of problems, so it's good to say Y here.
996 You can safely say Y even if your machine doesn't have MTRRs, you'll
997 just add about 9 KB to your kernel.
999 See <file:Documentation/mtrr.txt> for more information.
1003 prompt "EFI runtime service support"
1006 This enables the kernel to use EFI runtime services that are
1007 available (such as the EFI variable services).
1009 This option is only useful on systems that have EFI firmware.
1010 In addition, you should use the latest ELILO loader available
1011 at <http://elilo.sourceforge.net> in order to take advantage
1012 of EFI runtime services. However, even with this option, the
1013 resultant kernel should continue to boot on existing non-EFI
1018 prompt "Enable kernel irq balancing"
1019 depends on X86_32 && SMP && X86_IO_APIC
1021 The default yes will allow the kernel to do irq load balancing.
1022 Saying no will keep the kernel from doing irq load balancing.
1026 prompt "Enable seccomp to safely compute untrusted bytecode"
1029 This kernel feature is useful for number crunching applications
1030 that may need to compute untrusted bytecode during their
1031 execution. By using pipes or other transports made available to
1032 the process as file descriptors supporting the read/write
1033 syscalls, it's possible to isolate those applications in
1034 their own address space using seccomp. Once seccomp is
1035 enabled via /proc/<pid>/seccomp, it cannot be disabled
1036 and the task is only allowed to execute a few safe syscalls
1037 defined by each seccomp mode.
1039 If unsure, say Y. Only embedded should say N here.
1041 config CC_STACKPROTECTOR
1042 bool "Enable -fstack-protector buffer overflow detection (EXPERIMENTAL)"
1043 depends on X86_64 && EXPERIMENTAL
1045 This option turns on the -fstack-protector GCC feature. This
1046 feature puts, at the beginning of critical functions, a canary
1047 value on the stack just before the return address, and validates
1048 the value just before actually returning. Stack based buffer
1049 overflows (that need to overwrite this return address) now also
1050 overwrite the canary, which gets detected and the attack is then
1051 neutralized via a kernel panic.
1053 This feature requires gcc version 4.2 or above, or a distribution
1054 gcc with the feature backported. Older versions are automatically
1055 detected and for those versions, this configuration option is ignored.
1057 config CC_STACKPROTECTOR_ALL
1058 bool "Use stack-protector for all functions"
1059 depends on CC_STACKPROTECTOR
1061 Normally, GCC only inserts the canary value protection for
1062 functions that use large-ish on-stack buffers. By enabling
1063 this option, GCC will be asked to do this for ALL functions.
1065 source kernel/Kconfig.hz
1068 bool "kexec system call"
1070 kexec is a system call that implements the ability to shutdown your
1071 current kernel, and to start another kernel. It is like a reboot
1072 but it is independent of the system firmware. And like a reboot
1073 you can start any kernel with it, not just Linux.
1075 The name comes from the similarity to the exec system call.
1077 It is an ongoing process to be certain the hardware in a machine
1078 is properly shutdown, so do not be surprised if this code does not
1079 initially work for you. It may help to enable device hotplugging
1080 support. As of this writing the exact hardware interface is
1081 strongly in flux, so no good recommendation can be made.
1084 bool "kernel crash dumps (EXPERIMENTAL)"
1085 depends on EXPERIMENTAL
1086 depends on X86_64 || (X86_32 && HIGHMEM)
1088 Generate crash dump after being started by kexec.
1089 This should be normally only set in special crash dump kernels
1090 which are loaded in the main kernel with kexec-tools into
1091 a specially reserved region and then later executed after
1092 a crash by kdump/kexec. The crash dump kernel must be compiled
1093 to a memory address not used by the main kernel or BIOS using
1094 PHYSICAL_START, or it must be built as a relocatable image
1095 (CONFIG_RELOCATABLE=y).
1096 For more details see Documentation/kdump/kdump.txt
1098 config PHYSICAL_START
1099 hex "Physical address where the kernel is loaded" if (EMBEDDED || CRASH_DUMP)
1100 default "0x1000000" if X86_NUMAQ
1101 default "0x200000" if X86_64
1104 This gives the physical address where the kernel is loaded.
1106 If kernel is a not relocatable (CONFIG_RELOCATABLE=n) then
1107 bzImage will decompress itself to above physical address and
1108 run from there. Otherwise, bzImage will run from the address where
1109 it has been loaded by the boot loader and will ignore above physical
1112 In normal kdump cases one does not have to set/change this option
1113 as now bzImage can be compiled as a completely relocatable image
1114 (CONFIG_RELOCATABLE=y) and be used to load and run from a different
1115 address. This option is mainly useful for the folks who don't want
1116 to use a bzImage for capturing the crash dump and want to use a
1117 vmlinux instead. vmlinux is not relocatable hence a kernel needs
1118 to be specifically compiled to run from a specific memory area
1119 (normally a reserved region) and this option comes handy.
1121 So if you are using bzImage for capturing the crash dump, leave
1122 the value here unchanged to 0x100000 and set CONFIG_RELOCATABLE=y.
1123 Otherwise if you plan to use vmlinux for capturing the crash dump
1124 change this value to start of the reserved region (Typically 16MB
1125 0x1000000). In other words, it can be set based on the "X" value as
1126 specified in the "crashkernel=YM@XM" command line boot parameter
1127 passed to the panic-ed kernel. Typically this parameter is set as
1128 crashkernel=64M@16M. Please take a look at
1129 Documentation/kdump/kdump.txt for more details about crash dumps.
1131 Usage of bzImage for capturing the crash dump is recommended as
1132 one does not have to build two kernels. Same kernel can be used
1133 as production kernel and capture kernel. Above option should have
1134 gone away after relocatable bzImage support is introduced. But it
1135 is present because there are users out there who continue to use
1136 vmlinux for dump capture. This option should go away down the
1139 Don't change this unless you know what you are doing.
1142 bool "Build a relocatable kernel (EXPERIMENTAL)"
1143 depends on EXPERIMENTAL
1145 This builds a kernel image that retains relocation information
1146 so it can be loaded someplace besides the default 1MB.
1147 The relocations tend to make the kernel binary about 10% larger,
1148 but are discarded at runtime.
1150 One use is for the kexec on panic case where the recovery kernel
1151 must live at a different physical address than the primary
1154 Note: If CONFIG_RELOCATABLE=y, then the kernel runs from the address
1155 it has been loaded at and the compile time physical address
1156 (CONFIG_PHYSICAL_START) is ignored.
1158 config PHYSICAL_ALIGN
1160 prompt "Alignment value to which kernel should be aligned" if X86_32
1161 default "0x100000" if X86_32
1162 default "0x200000" if X86_64
1163 range 0x2000 0x400000
1165 This value puts the alignment restrictions on physical address
1166 where kernel is loaded and run from. Kernel is compiled for an
1167 address which meets above alignment restriction.
1169 If bootloader loads the kernel at a non-aligned address and
1170 CONFIG_RELOCATABLE is set, kernel will move itself to nearest
1171 address aligned to above value and run from there.
1173 If bootloader loads the kernel at a non-aligned address and
1174 CONFIG_RELOCATABLE is not set, kernel will ignore the run time
1175 load address and decompress itself to the address it has been
1176 compiled for and run from there. The address for which kernel is
1177 compiled already meets above alignment restrictions. Hence the
1178 end result is that kernel runs from a physical address meeting
1179 above alignment restrictions.
1181 Don't change this unless you know what you are doing.
1184 bool "Support for suspend on SMP and hot-pluggable CPUs (EXPERIMENTAL)"
1185 depends on SMP && HOTPLUG && EXPERIMENTAL && !X86_VOYAGER
1187 Say Y here to experiment with turning CPUs off and on, and to
1188 enable suspend on SMP systems. CPUs can be controlled through
1189 /sys/devices/system/cpu.
1190 Say N if you want to disable CPU hotplug and don't need to
1195 prompt "Compat VDSO support"
1196 depends on X86_32 || IA32_EMULATION
1198 Map the 32-bit VDSO to the predictable old-style address too.
1200 Say N here if you are running a sufficiently recent glibc
1201 version (2.3.3 or later), to remove the high-mapped
1202 VDSO mapping and to exclusively use the randomized VDSO.
1208 config ARCH_ENABLE_MEMORY_HOTPLUG
1210 depends on X86_64 || (X86_32 && HIGHMEM)
1212 config HAVE_ARCH_EARLY_PFN_TO_NID
1216 menu "Power management options"
1217 depends on !X86_VOYAGER
1219 config ARCH_HIBERNATION_HEADER
1221 depends on X86_64 && HIBERNATION
1223 source "kernel/power/Kconfig"
1225 source "drivers/acpi/Kconfig"
1230 depends on APM || APM_MODULE
1233 tristate "APM (Advanced Power Management) BIOS support"
1234 depends on X86_32 && PM_SLEEP && !X86_VISWS
1236 APM is a BIOS specification for saving power using several different
1237 techniques. This is mostly useful for battery powered laptops with
1238 APM compliant BIOSes. If you say Y here, the system time will be
1239 reset after a RESUME operation, the /proc/apm device will provide
1240 battery status information, and user-space programs will receive
1241 notification of APM "events" (e.g. battery status change).
1243 If you select "Y" here, you can disable actual use of the APM
1244 BIOS by passing the "apm=off" option to the kernel at boot time.
1246 Note that the APM support is almost completely disabled for
1247 machines with more than one CPU.
1249 In order to use APM, you will need supporting software. For location
1250 and more information, read <file:Documentation/pm.txt> and the
1251 Battery Powered Linux mini-HOWTO, available from
1252 <http://www.tldp.org/docs.html#howto>.
1254 This driver does not spin down disk drives (see the hdparm(8)
1255 manpage ("man 8 hdparm") for that), and it doesn't turn off
1256 VESA-compliant "green" monitors.
1258 This driver does not support the TI 4000M TravelMate and the ACER
1259 486/DX4/75 because they don't have compliant BIOSes. Many "green"
1260 desktop machines also don't have compliant BIOSes, and this driver
1261 may cause those machines to panic during the boot phase.
1263 Generally, if you don't have a battery in your machine, there isn't
1264 much point in using this driver and you should say N. If you get
1265 random kernel OOPSes or reboots that don't seem to be related to
1266 anything, try disabling/enabling this option (or disabling/enabling
1269 Some other things you should try when experiencing seemingly random,
1272 1) make sure that you have enough swap space and that it is
1274 2) pass the "no-hlt" option to the kernel
1275 3) switch on floating point emulation in the kernel and pass
1276 the "no387" option to the kernel
1277 4) pass the "floppy=nodma" option to the kernel
1278 5) pass the "mem=4M" option to the kernel (thereby disabling
1279 all but the first 4 MB of RAM)
1280 6) make sure that the CPU is not over clocked.
1281 7) read the sig11 FAQ at <http://www.bitwizard.nl/sig11/>
1282 8) disable the cache from your BIOS settings
1283 9) install a fan for the video card or exchange video RAM
1284 10) install a better fan for the CPU
1285 11) exchange RAM chips
1286 12) exchange the motherboard.
1288 To compile this driver as a module, choose M here: the
1289 module will be called apm.
1293 config APM_IGNORE_USER_SUSPEND
1294 bool "Ignore USER SUSPEND"
1296 This option will ignore USER SUSPEND requests. On machines with a
1297 compliant APM BIOS, you want to say N. However, on the NEC Versa M
1298 series notebooks, it is necessary to say Y because of a BIOS bug.
1300 config APM_DO_ENABLE
1301 bool "Enable PM at boot time"
1303 Enable APM features at boot time. From page 36 of the APM BIOS
1304 specification: "When disabled, the APM BIOS does not automatically
1305 power manage devices, enter the Standby State, enter the Suspend
1306 State, or take power saving steps in response to CPU Idle calls."
1307 This driver will make CPU Idle calls when Linux is idle (unless this
1308 feature is turned off -- see "Do CPU IDLE calls", below). This
1309 should always save battery power, but more complicated APM features
1310 will be dependent on your BIOS implementation. You may need to turn
1311 this option off if your computer hangs at boot time when using APM
1312 support, or if it beeps continuously instead of suspending. Turn
1313 this off if you have a NEC UltraLite Versa 33/C or a Toshiba
1314 T400CDT. This is off by default since most machines do fine without
1318 bool "Make CPU Idle calls when idle"
1320 Enable calls to APM CPU Idle/CPU Busy inside the kernel's idle loop.
1321 On some machines, this can activate improved power savings, such as
1322 a slowed CPU clock rate, when the machine is idle. These idle calls
1323 are made after the idle loop has run for some length of time (e.g.,
1324 333 mS). On some machines, this will cause a hang at boot time or
1325 whenever the CPU becomes idle. (On machines with more than one CPU,
1326 this option does nothing.)
1328 config APM_DISPLAY_BLANK
1329 bool "Enable console blanking using APM"
1331 Enable console blanking using the APM. Some laptops can use this to
1332 turn off the LCD backlight when the screen blanker of the Linux
1333 virtual console blanks the screen. Note that this is only used by
1334 the virtual console screen blanker, and won't turn off the backlight
1335 when using the X Window system. This also doesn't have anything to
1336 do with your VESA-compliant power-saving monitor. Further, this
1337 option doesn't work for all laptops -- it might not turn off your
1338 backlight at all, or it might print a lot of errors to the console,
1339 especially if you are using gpm.
1341 config APM_ALLOW_INTS
1342 bool "Allow interrupts during APM BIOS calls"
1344 Normally we disable external interrupts while we are making calls to
1345 the APM BIOS as a measure to lessen the effects of a badly behaving
1346 BIOS implementation. The BIOS should reenable interrupts if it
1347 needs to. Unfortunately, some BIOSes do not -- especially those in
1348 many of the newer IBM Thinkpads. If you experience hangs when you
1349 suspend, try setting this to Y. Otherwise, say N.
1351 config APM_REAL_MODE_POWER_OFF
1352 bool "Use real mode APM BIOS call to power off"
1354 Use real mode APM BIOS calls to switch off the computer. This is
1355 a work-around for a number of buggy BIOSes. Switch this option on if
1356 your computer crashes instead of powering off properly.
1360 source "arch/x86/kernel/cpu/cpufreq/Kconfig"
1362 source "drivers/cpuidle/Kconfig"
1367 menu "Bus options (PCI etc.)"
1370 bool "PCI support" if !X86_VISWS
1371 depends on !X86_VOYAGER
1373 select ARCH_SUPPORTS_MSI if (X86_LOCAL_APIC && X86_IO_APIC)
1375 Find out whether you have a PCI motherboard. PCI is the name of a
1376 bus system, i.e. the way the CPU talks to the other stuff inside
1377 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
1378 VESA. If you have PCI, say Y, otherwise N.
1381 prompt "PCI access mode"
1382 depends on X86_32 && PCI && !X86_VISWS
1385 On PCI systems, the BIOS can be used to detect the PCI devices and
1386 determine their configuration. However, some old PCI motherboards
1387 have BIOS bugs and may crash if this is done. Also, some embedded
1388 PCI-based systems don't have any BIOS at all. Linux can also try to
1389 detect the PCI hardware directly without using the BIOS.
1391 With this option, you can specify how Linux should detect the
1392 PCI devices. If you choose "BIOS", the BIOS will be used,
1393 if you choose "Direct", the BIOS won't be used, and if you
1394 choose "MMConfig", then PCI Express MMCONFIG will be used.
1395 If you choose "Any", the kernel will try MMCONFIG, then the
1396 direct access method and falls back to the BIOS if that doesn't
1397 work. If unsure, go with the default, which is "Any".
1402 config PCI_GOMMCONFIG
1415 depends on X86_32 && !X86_VISWS && PCI && (PCI_GOBIOS || PCI_GOANY)
1417 # x86-64 doesn't support PCI BIOS access from long mode so always go direct.
1420 depends on PCI && (X86_64 || (PCI_GODIRECT || PCI_GOANY) || X86_VISWS)
1424 depends on X86_32 && PCI && ACPI && (PCI_GOMMCONFIG || PCI_GOANY)
1431 bool "Support mmconfig PCI config space access"
1432 depends on X86_64 && PCI && ACPI
1435 bool "Support for DMA Remapping Devices (EXPERIMENTAL)"
1436 depends on X86_64 && PCI_MSI && ACPI && EXPERIMENTAL
1438 DMA remapping (DMAR) devices support enables independent address
1439 translations for Direct Memory Access (DMA) from devices.
1440 These DMA remapping devices are reported via ACPI tables
1441 and include PCI device scope covered by these DMA
1446 prompt "Support for Graphics workaround"
1449 Current Graphics drivers tend to use physical address
1450 for DMA and avoid using DMA APIs. Setting this config
1451 option permits the IOMMU driver to set a unity map for
1452 all the OS-visible memory. Hence the driver can continue
1453 to use physical addresses for DMA.
1455 config DMAR_FLOPPY_WA
1459 Floppy disk drivers are know to bypass DMA API calls
1460 thereby failing to work when IOMMU is enabled. This
1461 workaround will setup a 1:1 mapping for the first
1462 16M to make floppy (an ISA device) work.
1464 source "drivers/pci/pcie/Kconfig"
1466 source "drivers/pci/Kconfig"
1468 # x86_64 have no ISA slots, but do have ISA-style DMA.
1476 depends on !(X86_VOYAGER || X86_VISWS)
1478 Find out whether you have ISA slots on your motherboard. ISA is the
1479 name of a bus system, i.e. the way the CPU talks to the other stuff
1480 inside your box. Other bus systems are PCI, EISA, MicroChannel
1481 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
1482 newer boards don't support it. If you have ISA, say Y, otherwise N.
1488 The Extended Industry Standard Architecture (EISA) bus was
1489 developed as an open alternative to the IBM MicroChannel bus.
1491 The EISA bus provided some of the features of the IBM MicroChannel
1492 bus while maintaining backward compatibility with cards made for
1493 the older ISA bus. The EISA bus saw limited use between 1988 and
1494 1995 when it was made obsolete by the PCI bus.
1496 Say Y here if you are building a kernel for an EISA-based machine.
1500 source "drivers/eisa/Kconfig"
1503 bool "MCA support" if !(X86_VISWS || X86_VOYAGER)
1504 default y if X86_VOYAGER
1506 MicroChannel Architecture is found in some IBM PS/2 machines and
1507 laptops. It is a bus system similar to PCI or ISA. See
1508 <file:Documentation/mca.txt> (and especially the web page given
1509 there) before attempting to build an MCA bus kernel.
1511 source "drivers/mca/Kconfig"
1514 tristate "NatSemi SCx200 support"
1515 depends on !X86_VOYAGER
1517 This provides basic support for National Semiconductor's
1518 (now AMD's) Geode processors. The driver probes for the
1519 PCI-IDs of several on-chip devices, so its a good dependency
1520 for other scx200_* drivers.
1522 If compiled as a module, the driver is named scx200.
1524 config SCx200HR_TIMER
1525 tristate "NatSemi SCx200 27MHz High-Resolution Timer Support"
1526 depends on SCx200 && GENERIC_TIME
1529 This driver provides a clocksource built upon the on-chip
1530 27MHz high-resolution timer. Its also a workaround for
1531 NSC Geode SC-1100's buggy TSC, which loses time when the
1532 processor goes idle (as is done by the scheduler). The
1533 other workaround is idle=poll boot option.
1535 config GEODE_MFGPT_TIMER
1537 prompt "Geode Multi-Function General Purpose Timer (MFGPT) events"
1538 depends on MGEODE_LX && GENERIC_TIME && GENERIC_CLOCKEVENTS
1540 This driver provides a clock event source based on the MFGPT
1541 timer(s) in the CS5535 and CS5536 companion chip for the geode.
1542 MFGPTs have a better resolution and max interval than the
1543 generic PIT, and are suitable for use as high-res timers.
1549 depends on AGP_AMD64 || (X86_64 && (GART_IOMMU || (PCI && NUMA)))
1551 source "drivers/pcmcia/Kconfig"
1553 source "drivers/pci/hotplug/Kconfig"
1558 menu "Executable file formats / Emulations"
1560 source "fs/Kconfig.binfmt"
1562 config IA32_EMULATION
1563 bool "IA32 Emulation"
1565 select COMPAT_BINFMT_ELF
1567 Include code to run 32-bit programs under a 64-bit kernel. You should
1568 likely turn this on, unless you're 100% sure that you don't have any
1569 32-bit programs left.
1572 tristate "IA32 a.out support"
1573 depends on IA32_EMULATION
1575 Support old a.out binaries in the 32bit emulation.
1579 depends on IA32_EMULATION
1581 config COMPAT_FOR_U64_ALIGNMENT
1585 config SYSVIPC_COMPAT
1587 depends on X86_64 && COMPAT && SYSVIPC
1592 source "net/Kconfig"
1594 source "drivers/Kconfig"
1596 source "drivers/firmware/Kconfig"
1600 source "kernel/Kconfig.instrumentation"
1602 source "arch/x86/Kconfig.debug"
1604 source "security/Kconfig"
1606 source "crypto/Kconfig"
1608 source "arch/x86/kvm/Kconfig"
1610 source "lib/Kconfig"
projects / linux-2.6 / blob