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
119 config ARCH_POPULATES_NODE_MAP
126 # Use the generic interrupt handling code in kernel/irq/:
127 config GENERIC_HARDIRQS
131 config GENERIC_IRQ_PROBE
135 config GENERIC_PENDING_IRQ
137 depends on GENERIC_HARDIRQS && SMP
142 depends on SMP && ((X86_32 && !X86_VOYAGER) || X86_64)
147 depends on X86_32 && SMP
151 depends on X86_64 && SMP
156 depends on (X86_32 && !(X86_VISWS || X86_VOYAGER)) || (X86_64 && !MK8)
159 config X86_BIOS_REBOOT
161 depends on X86_32 && !(X86_VISWS || X86_VOYAGER)
164 config X86_TRAMPOLINE
166 depends on X86_SMP || (X86_VOYAGER && SMP)
171 source "init/Kconfig"
173 menu "Processor type and features"
175 source "kernel/time/Kconfig"
178 bool "Symmetric multi-processing support"
180 This enables support for systems with more than one CPU. If you have
181 a system with only one CPU, like most personal computers, say N. If
182 you have a system with more than one CPU, say Y.
184 If you say N here, the kernel will run on single and multiprocessor
185 machines, but will use only one CPU of a multiprocessor machine. If
186 you say Y here, the kernel will run on many, but not all,
187 singleprocessor machines. On a singleprocessor machine, the kernel
188 will run faster if you say N here.
190 Note that if you say Y here and choose architecture "586" or
191 "Pentium" under "Processor family", the kernel will not work on 486
192 architectures. Similarly, multiprocessor kernels for the "PPro"
193 architecture may not work on all Pentium based boards.
195 People using multiprocessor machines who say Y here should also say
196 Y to "Enhanced Real Time Clock Support", below. The "Advanced Power
197 Management" code will be disabled if you say Y here.
199 See also the <file:Documentation/smp.txt>,
200 <file:Documentation/i386/IO-APIC.txt>,
201 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
202 <http://www.tldp.org/docs.html#howto>.
204 If you don't know what to do here, say N.
207 prompt "Subarchitecture Type"
213 Choose this option if your computer is a standard PC or compatible.
219 Select this for an AMD Elan processor.
221 Do not use this option for K6/Athlon/Opteron processors!
223 If unsure, choose "PC-compatible" instead.
228 select SMP if !BROKEN
230 Voyager is an MCA-based 32-way capable SMP architecture proprietary
231 to NCR Corp. Machine classes 345x/35xx/4100/51xx are Voyager-based.
235 If you do not specifically know you have a Voyager based machine,
236 say N here, otherwise the kernel you build will not be bootable.
239 bool "NUMAQ (IBM/Sequent)"
244 This option is used for getting Linux to run on a (IBM/Sequent) NUMA
245 multiquad box. This changes the way that processors are bootstrapped,
246 and uses Clustered Logical APIC addressing mode instead of Flat Logical.
247 You will need a new lynxer.elf file to flash your firmware with - send
248 email to <Martin.Bligh@us.ibm.com>.
251 bool "Summit/EXA (IBM x440)"
252 depends on X86_32 && SMP
254 This option is needed for IBM systems that use the Summit/EXA chipset.
255 In particular, it is needed for the x440.
257 If you don't have one of these computers, you should say N here.
258 If you want to build a NUMA kernel, you must select ACPI.
261 bool "Support for other sub-arch SMP systems with more than 8 CPUs"
262 depends on X86_32 && SMP
264 This option is needed for the systems that have more than 8 CPUs
265 and if the system is not of any sub-arch type above.
267 If you don't have such a system, you should say N here.
270 bool "SGI 320/540 (Visual Workstation)"
273 The SGI Visual Workstation series is an IA32-based workstation
274 based on SGI systems chips with some legacy PC hardware attached.
276 Say Y here to create a kernel to run on the SGI 320 or 540.
278 A kernel compiled for the Visual Workstation will not run on PCs
279 and vice versa. See <file:Documentation/sgi-visws.txt> for details.
281 config X86_GENERICARCH
282 bool "Generic architecture (Summit, bigsmp, ES7000, default)"
285 This option compiles in the Summit, bigsmp, ES7000, default subarchitectures.
286 It is intended for a generic binary kernel.
287 If you want a NUMA kernel, select ACPI. We need SRAT for NUMA.
290 bool "Support for Unisys ES7000 IA32 series"
291 depends on X86_32 && SMP
293 Support for Unisys ES7000 systems. Say 'Y' here if this kernel is
294 supposed to run on an IA32-based Unisys ES7000 system.
295 Only choose this option if you have such a system, otherwise you
299 bool "RDC R-321x SoC"
302 select X86_REBOOTFIXUPS
306 This option is needed for RDC R-321x system-on-chip, also known
308 If you don't have one of these chips, you should say N here.
311 bool "Support for ScaleMP vSMP"
312 depends on X86_64 && PCI
314 Support for ScaleMP vSMP systems. Say 'Y' here if this kernel is
315 supposed to run on these EM64T-based machines. Only choose this option
316 if you have one of these machines.
320 config SCHED_NO_NO_OMIT_FRAME_POINTER
322 prompt "Single-depth WCHAN output"
325 Calculate simpler /proc/<PID>/wchan values. If this option
326 is disabled then wchan values will recurse back to the
327 caller function. This provides more accurate wchan values,
328 at the expense of slightly more scheduling overhead.
330 If in doubt, say "Y".
332 menuconfig PARAVIRT_GUEST
333 bool "Paravirtualized guest support"
335 Say Y here to get to see options related to running Linux under
336 various hypervisors. This option alone does not add any kernel code.
338 If you say N, all options in this submenu will be skipped and disabled.
342 source "arch/x86/xen/Kconfig"
345 bool "VMI Guest support"
348 depends on !(X86_VISWS || X86_VOYAGER)
350 VMI provides a paravirtualized interface to the VMware ESX server
351 (it could be used by other hypervisors in theory too, but is not
352 at the moment), by linking the kernel to a GPL-ed ROM module
353 provided by the hypervisor.
355 source "arch/x86/lguest/Kconfig"
358 bool "Enable paravirtualization code"
359 depends on !(X86_VISWS || X86_VOYAGER)
361 This changes the kernel so it can modify itself when it is run
362 under a hypervisor, potentially improving performance significantly
363 over full virtualization. However, when run without a hypervisor
364 the kernel is theoretically slower and slightly larger.
370 depends on X86_32 && ACPI && NUMA && (X86_SUMMIT || X86_GENERICARCH)
373 config HAVE_ARCH_PARSE_SRAT
377 config X86_SUMMIT_NUMA
379 depends on X86_32 && NUMA && (X86_SUMMIT || X86_GENERICARCH)
381 config X86_CYCLONE_TIMER
383 depends on X86_32 && X86_SUMMIT || X86_GENERICARCH
385 config ES7000_CLUSTERED_APIC
387 depends on SMP && X86_ES7000 && MPENTIUMIII
389 source "arch/x86/Kconfig.cpu"
393 prompt "HPET Timer Support" if X86_32
395 Use the IA-PC HPET (High Precision Event Timer) to manage
396 time in preference to the PIT and RTC, if a HPET is
398 HPET is the next generation timer replacing legacy 8254s.
399 The HPET provides a stable time base on SMP
400 systems, unlike the TSC, but it is more expensive to access,
401 as it is off-chip. You can find the HPET spec at
402 <http://www.intel.com/hardwaredesign/hpetspec.htm>.
404 You can safely choose Y here. However, HPET will only be
405 activated if the platform and the BIOS support this feature.
406 Otherwise the 8254 will be used for timing services.
408 Choose N to continue using the legacy 8254 timer.
410 config HPET_EMULATE_RTC
412 depends on HPET_TIMER && (RTC=y || RTC=m)
414 # Mark as embedded because too many people got it wrong.
415 # The code disables itself when not needed.
417 bool "GART IOMMU support" if EMBEDDED
421 depends on X86_64 && PCI
423 Support for full DMA access of devices with 32bit memory access only
424 on systems with more than 3GB. This is usually needed for USB,
425 sound, many IDE/SATA chipsets and some other devices.
426 Provides a driver for the AMD Athlon64/Opteron/Turion/Sempron GART
427 based hardware IOMMU and a software bounce buffer based IOMMU used
428 on Intel systems and as fallback.
429 The code is only active when needed (enough memory and limited
430 device) unless CONFIG_IOMMU_DEBUG or iommu=force is specified
434 bool "IBM Calgary IOMMU support"
436 depends on X86_64 && PCI && EXPERIMENTAL
438 Support for hardware IOMMUs in IBM's xSeries x366 and x460
439 systems. Needed to run systems with more than 3GB of memory
440 properly with 32-bit PCI devices that do not support DAC
441 (Double Address Cycle). Calgary also supports bus level
442 isolation, where all DMAs pass through the IOMMU. This
443 prevents them from going anywhere except their intended
444 destination. This catches hard-to-find kernel bugs and
445 mis-behaving drivers and devices that do not use the DMA-API
446 properly to set up their DMA buffers. The IOMMU can be
447 turned off at boot time with the iommu=off parameter.
448 Normally the kernel will make the right choice by itself.
451 config CALGARY_IOMMU_ENABLED_BY_DEFAULT
453 prompt "Should Calgary be enabled by default?"
454 depends on CALGARY_IOMMU
456 Should Calgary be enabled by default? if you choose 'y', Calgary
457 will be used (if it exists). If you choose 'n', Calgary will not be
458 used even if it exists. If you choose 'n' and would like to use
459 Calgary anyway, pass 'iommu=calgary' on the kernel command line.
462 # need this always selected by IOMMU for the VIA workaround
466 Support for software bounce buffers used on x86-64 systems
467 which don't have a hardware IOMMU (e.g. the current generation
468 of Intel's x86-64 CPUs). Using this PCI devices which can only
469 access 32-bits of memory can be used on systems with more than
470 3 GB of memory. If unsure, say Y.
474 int "Maximum number of CPUs (2-255)"
477 default "32" if X86_NUMAQ || X86_SUMMIT || X86_BIGSMP || X86_ES7000
480 This allows you to specify the maximum number of CPUs which this
481 kernel will support. The maximum supported value is 255 and the
482 minimum value which makes sense is 2.
484 This is purely to save memory - each supported CPU adds
485 approximately eight kilobytes to the kernel image.
488 bool "SMT (Hyperthreading) scheduler support"
489 depends on (X86_64 && SMP) || (X86_32 && X86_HT)
491 SMT scheduler support improves the CPU scheduler's decision making
492 when dealing with Intel Pentium 4 chips with HyperThreading at a
493 cost of slightly increased overhead in some places. If unsure say
498 prompt "Multi-core scheduler support"
499 depends on (X86_64 && SMP) || (X86_32 && X86_HT)
501 Multi-core scheduler support improves the CPU scheduler's decision
502 making when dealing with multi-core CPU chips at a cost of slightly
503 increased overhead in some places. If unsure say N here.
505 source "kernel/Kconfig.preempt"
508 bool "Local APIC support on uniprocessors"
509 depends on X86_32 && !SMP && !(X86_VISWS || X86_VOYAGER || X86_GENERICARCH)
511 A local APIC (Advanced Programmable Interrupt Controller) is an
512 integrated interrupt controller in the CPU. If you have a single-CPU
513 system which has a processor with a local APIC, you can say Y here to
514 enable and use it. If you say Y here even though your machine doesn't
515 have a local APIC, then the kernel will still run with no slowdown at
516 all. The local APIC supports CPU-generated self-interrupts (timer,
517 performance counters), and the NMI watchdog which detects hard
521 bool "IO-APIC support on uniprocessors"
522 depends on X86_UP_APIC
524 An IO-APIC (I/O Advanced Programmable Interrupt Controller) is an
525 SMP-capable replacement for PC-style interrupt controllers. Most
526 SMP systems and many recent uniprocessor systems have one.
528 If you have a single-CPU system with an IO-APIC, you can say Y here
529 to use it. If you say Y here even though your machine doesn't have
530 an IO-APIC, then the kernel will still run with no slowdown at all.
532 config X86_LOCAL_APIC
534 depends on X86_64 || (X86_32 && (X86_UP_APIC || ((X86_VISWS || SMP) && !X86_VOYAGER) || X86_GENERICARCH))
538 depends on X86_64 || (X86_32 && (X86_UP_IOAPIC || (SMP && !(X86_VISWS || X86_VOYAGER)) || X86_GENERICARCH))
540 config X86_VISWS_APIC
542 depends on X86_32 && X86_VISWS
545 bool "Machine Check Exception"
546 depends on !X86_VOYAGER
548 Machine Check Exception support allows the processor to notify the
549 kernel if it detects a problem (e.g. overheating, component failure).
550 The action the kernel takes depends on the severity of the problem,
551 ranging from a warning message on the console, to halting the machine.
552 Your processor must be a Pentium or newer to support this - check the
553 flags in /proc/cpuinfo for mce. Note that some older Pentium systems
554 have a design flaw which leads to false MCE events - hence MCE is
555 disabled on all P5 processors, unless explicitly enabled with "mce"
556 as a boot argument. Similarly, if MCE is built in and creates a
557 problem on some new non-standard machine, you can boot with "nomce"
558 to disable it. MCE support simply ignores non-MCE processors like
559 the 386 and 486, so nearly everyone can say Y here.
563 prompt "Intel MCE features"
564 depends on X86_64 && X86_MCE && X86_LOCAL_APIC
566 Additional support for intel specific MCE features such as
571 prompt "AMD MCE features"
572 depends on X86_64 && X86_MCE && X86_LOCAL_APIC
574 Additional support for AMD specific MCE features such as
575 the DRAM Error Threshold.
577 config X86_MCE_NONFATAL
578 tristate "Check for non-fatal errors on AMD Athlon/Duron / Intel Pentium 4"
579 depends on X86_32 && X86_MCE
581 Enabling this feature starts a timer that triggers every 5 seconds which
582 will look at the machine check registers to see if anything happened.
583 Non-fatal problems automatically get corrected (but still logged).
584 Disable this if you don't want to see these messages.
585 Seeing the messages this option prints out may be indicative of dying
586 or out-of-spec (ie, overclocked) hardware.
587 This option only does something on certain CPUs.
588 (AMD Athlon/Duron and Intel Pentium 4)
590 config X86_MCE_P4THERMAL
591 bool "check for P4 thermal throttling interrupt."
592 depends on X86_32 && X86_MCE && (X86_UP_APIC || SMP) && !X86_VISWS
594 Enabling this feature will cause a message to be printed when the P4
595 enters thermal throttling.
598 bool "Enable VM86 support" if EMBEDDED
602 This option is required by programs like DOSEMU to run 16-bit legacy
603 code on X86 processors. It also may be needed by software like
604 XFree86 to initialize some video cards via BIOS. Disabling this
605 option saves about 6k.
608 tristate "Toshiba Laptop support"
611 This adds a driver to safely access the System Management Mode of
612 the CPU on Toshiba portables with a genuine Toshiba BIOS. It does
613 not work on models with a Phoenix BIOS. The System Management Mode
614 is used to set the BIOS and power saving options on Toshiba portables.
616 For information on utilities to make use of this driver see the
617 Toshiba Linux utilities web site at:
618 <http://www.buzzard.org.uk/toshiba/>.
620 Say Y if you intend to run this kernel on a Toshiba portable.
624 tristate "Dell laptop support"
627 This adds a driver to safely access the System Management Mode
628 of the CPU on the Dell Inspiron 8000. The System Management Mode
629 is used to read cpu temperature and cooling fan status and to
630 control the fans on the I8K portables.
632 This driver has been tested only on the Inspiron 8000 but it may
633 also work with other Dell laptops. You can force loading on other
634 models by passing the parameter `force=1' to the module. Use at
637 For information on utilities to make use of this driver see the
638 I8K Linux utilities web site at:
639 <http://people.debian.org/~dz/i8k/>
641 Say Y if you intend to run this kernel on a Dell Inspiron 8000.
644 config X86_REBOOTFIXUPS
646 prompt "Enable X86 board specific fixups for reboot"
647 depends on X86_32 && X86
649 This enables chipset and/or board specific fixups to be done
650 in order to get reboot to work correctly. This is only needed on
651 some combinations of hardware and BIOS. The symptom, for which
652 this config is intended, is when reboot ends with a stalled/hung
655 Currently, the only fixup is for the Geode machines using
656 CS5530A and CS5536 chipsets and the RDC R-321x SoC.
658 Say Y if you want to enable the fixup. Currently, it's safe to
659 enable this option even if you don't need it.
663 tristate "/dev/cpu/microcode - Intel IA32 CPU microcode support"
666 If you say Y here, you will be able to update the microcode on
667 Intel processors in the IA32 family, e.g. Pentium Pro, Pentium II,
668 Pentium III, Pentium 4, Xeon etc. You will obviously need the
669 actual microcode binary data itself which is not shipped with the
672 For latest news and information on obtaining all the required
673 ingredients for this driver, check:
674 <http://www.urbanmyth.org/microcode/>.
676 To compile this driver as a module, choose M here: the
677 module will be called microcode.
679 config MICROCODE_OLD_INTERFACE
684 tristate "/dev/cpu/*/msr - Model-specific register support"
686 This device gives privileged processes access to the x86
687 Model-Specific Registers (MSRs). It is a character device with
688 major 202 and minors 0 to 31 for /dev/cpu/0/msr to /dev/cpu/31/msr.
689 MSR accesses are directed to a specific CPU on multi-processor
693 tristate "/dev/cpu/*/cpuid - CPU information support"
695 This device gives processes access to the x86 CPUID instruction to
696 be executed on a specific processor. It is a character device
697 with major 203 and minors 0 to 31 for /dev/cpu/0/cpuid to
701 prompt "High Memory Support"
702 default HIGHMEM4G if !X86_NUMAQ
703 default HIGHMEM64G if X86_NUMAQ
708 depends on !X86_NUMAQ
710 Linux can use up to 64 Gigabytes of physical memory on x86 systems.
711 However, the address space of 32-bit x86 processors is only 4
712 Gigabytes large. That means that, if you have a large amount of
713 physical memory, not all of it can be "permanently mapped" by the
714 kernel. The physical memory that's not permanently mapped is called
717 If you are compiling a kernel which will never run on a machine with
718 more than 1 Gigabyte total physical RAM, answer "off" here (default
719 choice and suitable for most users). This will result in a "3GB/1GB"
720 split: 3GB are mapped so that each process sees a 3GB virtual memory
721 space and the remaining part of the 4GB virtual memory space is used
722 by the kernel to permanently map as much physical memory as
725 If the machine has between 1 and 4 Gigabytes physical RAM, then
728 If more than 4 Gigabytes is used then answer "64GB" here. This
729 selection turns Intel PAE (Physical Address Extension) mode on.
730 PAE implements 3-level paging on IA32 processors. PAE is fully
731 supported by Linux, PAE mode is implemented on all recent Intel
732 processors (Pentium Pro and better). NOTE: If you say "64GB" here,
733 then the kernel will not boot on CPUs that don't support PAE!
735 The actual amount of total physical memory will either be
736 auto detected or can be forced by using a kernel command line option
737 such as "mem=256M". (Try "man bootparam" or see the documentation of
738 your boot loader (lilo or loadlin) about how to pass options to the
739 kernel at boot time.)
741 If unsure, say "off".
745 depends on !X86_NUMAQ
747 Select this if you have a 32-bit processor and between 1 and 4
748 gigabytes of physical RAM.
752 depends on !M386 && !M486
755 Select this if you have a 32-bit processor and more than 4
756 gigabytes of physical RAM.
761 depends on EXPERIMENTAL
762 prompt "Memory split" if EMBEDDED
766 Select the desired split between kernel and user memory.
768 If the address range available to the kernel is less than the
769 physical memory installed, the remaining memory will be available
770 as "high memory". Accessing high memory is a little more costly
771 than low memory, as it needs to be mapped into the kernel first.
772 Note that increasing the kernel address space limits the range
773 available to user programs, making the address space there
774 tighter. Selecting anything other than the default 3G/1G split
775 will also likely make your kernel incompatible with binary-only
778 If you are not absolutely sure what you are doing, leave this
782 bool "3G/1G user/kernel split"
783 config VMSPLIT_3G_OPT
785 bool "3G/1G user/kernel split (for full 1G low memory)"
787 bool "2G/2G user/kernel split"
788 config VMSPLIT_2G_OPT
790 bool "2G/2G user/kernel split (for full 2G low memory)"
792 bool "1G/3G user/kernel split"
797 default 0xB0000000 if VMSPLIT_3G_OPT
798 default 0x80000000 if VMSPLIT_2G
799 default 0x78000000 if VMSPLIT_2G_OPT
800 default 0x40000000 if VMSPLIT_1G
806 depends on X86_32 && (HIGHMEM64G || HIGHMEM4G)
810 prompt "PAE (Physical Address Extension) Support"
811 depends on X86_32 && !HIGHMEM4G
812 select RESOURCES_64BIT
814 PAE is required for NX support, and furthermore enables
815 larger swapspace support for non-overcommit purposes. It
816 has the cost of more pagetable lookup overhead, and also
817 consumes more pagetable space per process.
819 # Common NUMA Features
821 bool "Numa Memory Allocation and Scheduler Support (EXPERIMENTAL)"
823 depends on X86_64 || (X86_32 && HIGHMEM64G && (X86_NUMAQ || (X86_SUMMIT || X86_GENERICARCH) && ACPI) && EXPERIMENTAL)
825 default y if (X86_NUMAQ || X86_SUMMIT)
827 Enable NUMA (Non Uniform Memory Access) support.
828 The kernel will try to allocate memory used by a CPU on the
829 local memory controller of the CPU and add some more
830 NUMA awareness to the kernel.
832 For i386 this is currently highly experimental and should be only
833 used for kernel development. It might also cause boot failures.
834 For x86_64 this is recommended on all multiprocessor Opteron systems.
835 If the system is EM64T, you should say N unless your system is
838 comment "NUMA (Summit) requires SMP, 64GB highmem support, ACPI"
839 depends on X86_32 && X86_SUMMIT && (!HIGHMEM64G || !ACPI)
843 prompt "Old style AMD Opteron NUMA detection"
844 depends on X86_64 && NUMA && PCI
846 Enable K8 NUMA node topology detection. You should say Y here if
847 you have a multi processor AMD K8 system. This uses an old
848 method to read the NUMA configuration directly from the builtin
849 Northbridge of Opteron. It is recommended to use X86_64_ACPI_NUMA
850 instead, which also takes priority if both are compiled in.
852 config X86_64_ACPI_NUMA
854 prompt "ACPI NUMA detection"
855 depends on X86_64 && NUMA && ACPI && PCI
858 Enable ACPI SRAT based node topology detection.
861 bool "NUMA emulation"
862 depends on X86_64 && NUMA
864 Enable NUMA emulation. A flat machine will be split
865 into virtual nodes when booted with "numa=fake=N", where N is the
866 number of nodes. This is only useful for debugging.
871 default "6" if X86_64
872 default "4" if X86_NUMAQ
874 depends on NEED_MULTIPLE_NODES
876 config HAVE_ARCH_BOOTMEM_NODE
878 depends on X86_32 && NUMA
880 config ARCH_HAVE_MEMORY_PRESENT
882 depends on X86_32 && DISCONTIGMEM
884 config NEED_NODE_MEMMAP_SIZE
886 depends on X86_32 && (DISCONTIGMEM || SPARSEMEM)
888 config HAVE_ARCH_ALLOC_REMAP
890 depends on X86_32 && NUMA
892 config ARCH_FLATMEM_ENABLE
894 depends on X86_32 && ARCH_SELECT_MEMORY_MODEL && X86_PC && !NUMA
896 config ARCH_DISCONTIGMEM_ENABLE
898 depends on NUMA && X86_32
900 config ARCH_DISCONTIGMEM_DEFAULT
902 depends on NUMA && X86_32
904 config ARCH_SPARSEMEM_DEFAULT
908 config ARCH_SPARSEMEM_ENABLE
910 depends on X86_64 || NUMA || (EXPERIMENTAL && X86_PC)
911 select SPARSEMEM_STATIC if X86_32
912 select SPARSEMEM_VMEMMAP_ENABLE if X86_64
914 config ARCH_SELECT_MEMORY_MODEL
916 depends on ARCH_SPARSEMEM_ENABLE
918 config ARCH_MEMORY_PROBE
920 depends on MEMORY_HOTPLUG
925 bool "Allocate 3rd-level pagetables from highmem"
926 depends on X86_32 && (HIGHMEM4G || HIGHMEM64G)
928 The VM uses one page table entry for each page of physical memory.
929 For systems with a lot of RAM, this can be wasteful of precious
930 low memory. Setting this option will put user-space page table
931 entries in high memory.
933 config MATH_EMULATION
935 prompt "Math emulation" if X86_32
937 Linux can emulate a math coprocessor (used for floating point
938 operations) if you don't have one. 486DX and Pentium processors have
939 a math coprocessor built in, 486SX and 386 do not, unless you added
940 a 487DX or 387, respectively. (The messages during boot time can
941 give you some hints here ["man dmesg"].) Everyone needs either a
942 coprocessor or this emulation.
944 If you don't have a math coprocessor, you need to say Y here; if you
945 say Y here even though you have a coprocessor, the coprocessor will
946 be used nevertheless. (This behavior can be changed with the kernel
947 command line option "no387", which comes handy if your coprocessor
948 is broken. Try "man bootparam" or see the documentation of your boot
949 loader (lilo or loadlin) about how to pass options to the kernel at
950 boot time.) This means that it is a good idea to say Y here if you
951 intend to use this kernel on different machines.
953 More information about the internals of the Linux math coprocessor
954 emulation can be found in <file:arch/x86/math-emu/README>.
956 If you are not sure, say Y; apart from resulting in a 66 KB bigger
957 kernel, it won't hurt.
960 bool "MTRR (Memory Type Range Register) support"
962 On Intel P6 family processors (Pentium Pro, Pentium II and later)
963 the Memory Type Range Registers (MTRRs) may be used to control
964 processor access to memory ranges. This is most useful if you have
965 a video (VGA) card on a PCI or AGP bus. Enabling write-combining
966 allows bus write transfers to be combined into a larger transfer
967 before bursting over the PCI/AGP bus. This can increase performance
968 of image write operations 2.5 times or more. Saying Y here creates a
969 /proc/mtrr file which may be used to manipulate your processor's
970 MTRRs. Typically the X server should use this.
972 This code has a reasonably generic interface so that similar
973 control registers on other processors can be easily supported
976 The Cyrix 6x86, 6x86MX and M II processors have Address Range
977 Registers (ARRs) which provide a similar functionality to MTRRs. For
978 these, the ARRs are used to emulate the MTRRs.
979 The AMD K6-2 (stepping 8 and above) and K6-3 processors have two
980 MTRRs. The Centaur C6 (WinChip) has 8 MCRs, allowing
981 write-combining. All of these processors are supported by this code
982 and it makes sense to say Y here if you have one of them.
984 Saying Y here also fixes a problem with buggy SMP BIOSes which only
985 set the MTRRs for the boot CPU and not for the secondary CPUs. This
986 can lead to all sorts of problems, so it's good to say Y here.
988 You can safely say Y even if your machine doesn't have MTRRs, you'll
989 just add about 9 KB to your kernel.
991 See <file:Documentation/mtrr.txt> for more information.
995 prompt "EFI runtime service support"
998 This enables the kernel to use EFI runtime services that are
999 available (such as the EFI variable services).
1001 This option is only useful on systems that have EFI firmware.
1002 In addition, you should use the latest ELILO loader available
1003 at <http://elilo.sourceforge.net> in order to take advantage
1004 of EFI runtime services. However, even with this option, the
1005 resultant kernel should continue to boot on existing non-EFI
1010 prompt "Enable kernel irq balancing"
1011 depends on X86_32 && SMP && X86_IO_APIC
1013 The default yes will allow the kernel to do irq load balancing.
1014 Saying no will keep the kernel from doing irq load balancing.
1018 prompt "Enable seccomp to safely compute untrusted bytecode"
1021 This kernel feature is useful for number crunching applications
1022 that may need to compute untrusted bytecode during their
1023 execution. By using pipes or other transports made available to
1024 the process as file descriptors supporting the read/write
1025 syscalls, it's possible to isolate those applications in
1026 their own address space using seccomp. Once seccomp is
1027 enabled via /proc/<pid>/seccomp, it cannot be disabled
1028 and the task is only allowed to execute a few safe syscalls
1029 defined by each seccomp mode.
1031 If unsure, say Y. Only embedded should say N here.
1033 config CC_STACKPROTECTOR
1034 bool "Enable -fstack-protector buffer overflow detection (EXPERIMENTAL)"
1035 depends on X86_64 && EXPERIMENTAL
1037 This option turns on the -fstack-protector GCC feature. This
1038 feature puts, at the beginning of critical functions, a canary
1039 value on the stack just before the return address, and validates
1040 the value just before actually returning. Stack based buffer
1041 overflows (that need to overwrite this return address) now also
1042 overwrite the canary, which gets detected and the attack is then
1043 neutralized via a kernel panic.
1045 This feature requires gcc version 4.2 or above, or a distribution
1046 gcc with the feature backported. Older versions are automatically
1047 detected and for those versions, this configuration option is ignored.
1049 config CC_STACKPROTECTOR_ALL
1050 bool "Use stack-protector for all functions"
1051 depends on CC_STACKPROTECTOR
1053 Normally, GCC only inserts the canary value protection for
1054 functions that use large-ish on-stack buffers. By enabling
1055 this option, GCC will be asked to do this for ALL functions.
1057 source kernel/Kconfig.hz
1060 bool "kexec system call"
1062 kexec is a system call that implements the ability to shutdown your
1063 current kernel, and to start another kernel. It is like a reboot
1064 but it is independent of the system firmware. And like a reboot
1065 you can start any kernel with it, not just Linux.
1067 The name comes from the similarity to the exec system call.
1069 It is an ongoing process to be certain the hardware in a machine
1070 is properly shutdown, so do not be surprised if this code does not
1071 initially work for you. It may help to enable device hotplugging
1072 support. As of this writing the exact hardware interface is
1073 strongly in flux, so no good recommendation can be made.
1076 bool "kernel crash dumps (EXPERIMENTAL)"
1077 depends on EXPERIMENTAL
1078 depends on X86_64 || (X86_32 && HIGHMEM)
1080 Generate crash dump after being started by kexec.
1081 This should be normally only set in special crash dump kernels
1082 which are loaded in the main kernel with kexec-tools into
1083 a specially reserved region and then later executed after
1084 a crash by kdump/kexec. The crash dump kernel must be compiled
1085 to a memory address not used by the main kernel or BIOS using
1086 PHYSICAL_START, or it must be built as a relocatable image
1087 (CONFIG_RELOCATABLE=y).
1088 For more details see Documentation/kdump/kdump.txt
1090 config PHYSICAL_START
1091 hex "Physical address where the kernel is loaded" if (EMBEDDED || CRASH_DUMP)
1092 default "0x1000000" if X86_NUMAQ
1093 default "0x200000" if X86_64
1096 This gives the physical address where the kernel is loaded.
1098 If kernel is a not relocatable (CONFIG_RELOCATABLE=n) then
1099 bzImage will decompress itself to above physical address and
1100 run from there. Otherwise, bzImage will run from the address where
1101 it has been loaded by the boot loader and will ignore above physical
1104 In normal kdump cases one does not have to set/change this option
1105 as now bzImage can be compiled as a completely relocatable image
1106 (CONFIG_RELOCATABLE=y) and be used to load and run from a different
1107 address. This option is mainly useful for the folks who don't want
1108 to use a bzImage for capturing the crash dump and want to use a
1109 vmlinux instead. vmlinux is not relocatable hence a kernel needs
1110 to be specifically compiled to run from a specific memory area
1111 (normally a reserved region) and this option comes handy.
1113 So if you are using bzImage for capturing the crash dump, leave
1114 the value here unchanged to 0x100000 and set CONFIG_RELOCATABLE=y.
1115 Otherwise if you plan to use vmlinux for capturing the crash dump
1116 change this value to start of the reserved region (Typically 16MB
1117 0x1000000). In other words, it can be set based on the "X" value as
1118 specified in the "crashkernel=YM@XM" command line boot parameter
1119 passed to the panic-ed kernel. Typically this parameter is set as
1120 crashkernel=64M@16M. Please take a look at
1121 Documentation/kdump/kdump.txt for more details about crash dumps.
1123 Usage of bzImage for capturing the crash dump is recommended as
1124 one does not have to build two kernels. Same kernel can be used
1125 as production kernel and capture kernel. Above option should have
1126 gone away after relocatable bzImage support is introduced. But it
1127 is present because there are users out there who continue to use
1128 vmlinux for dump capture. This option should go away down the
1131 Don't change this unless you know what you are doing.
1134 bool "Build a relocatable kernel (EXPERIMENTAL)"
1135 depends on EXPERIMENTAL
1137 This builds a kernel image that retains relocation information
1138 so it can be loaded someplace besides the default 1MB.
1139 The relocations tend to make the kernel binary about 10% larger,
1140 but are discarded at runtime.
1142 One use is for the kexec on panic case where the recovery kernel
1143 must live at a different physical address than the primary
1146 Note: If CONFIG_RELOCATABLE=y, then the kernel runs from the address
1147 it has been loaded at and the compile time physical address
1148 (CONFIG_PHYSICAL_START) is ignored.
1150 config PHYSICAL_ALIGN
1152 prompt "Alignment value to which kernel should be aligned" if X86_32
1153 default "0x100000" if X86_32
1154 default "0x200000" if X86_64
1155 range 0x2000 0x400000
1157 This value puts the alignment restrictions on physical address
1158 where kernel is loaded and run from. Kernel is compiled for an
1159 address which meets above alignment restriction.
1161 If bootloader loads the kernel at a non-aligned address and
1162 CONFIG_RELOCATABLE is set, kernel will move itself to nearest
1163 address aligned to above value and run from there.
1165 If bootloader loads the kernel at a non-aligned address and
1166 CONFIG_RELOCATABLE is not set, kernel will ignore the run time
1167 load address and decompress itself to the address it has been
1168 compiled for and run from there. The address for which kernel is
1169 compiled already meets above alignment restrictions. Hence the
1170 end result is that kernel runs from a physical address meeting
1171 above alignment restrictions.
1173 Don't change this unless you know what you are doing.
1176 bool "Support for suspend on SMP and hot-pluggable CPUs (EXPERIMENTAL)"
1177 depends on SMP && HOTPLUG && EXPERIMENTAL && !X86_VOYAGER
1179 Say Y here to experiment with turning CPUs off and on, and to
1180 enable suspend on SMP systems. CPUs can be controlled through
1181 /sys/devices/system/cpu.
1182 Say N if you want to disable CPU hotplug and don't need to
1187 prompt "Compat VDSO support"
1188 depends on X86_32 || IA32_EMULATION
1190 Map the 32-bit VDSO to the predictable old-style address too.
1192 Say N here if you are running a sufficiently recent glibc
1193 version (2.3.3 or later), to remove the high-mapped
1194 VDSO mapping and to exclusively use the randomized VDSO.
1200 config ARCH_ENABLE_MEMORY_HOTPLUG
1202 depends on X86_64 || (X86_32 && HIGHMEM)
1204 config HAVE_ARCH_EARLY_PFN_TO_NID
1208 menu "Power management options"
1209 depends on !X86_VOYAGER
1211 config ARCH_HIBERNATION_HEADER
1213 depends on X86_64 && HIBERNATION
1215 source "kernel/power/Kconfig"
1217 source "drivers/acpi/Kconfig"
1222 depends on APM || APM_MODULE
1225 tristate "APM (Advanced Power Management) BIOS support"
1226 depends on X86_32 && PM_SLEEP && !X86_VISWS
1228 APM is a BIOS specification for saving power using several different
1229 techniques. This is mostly useful for battery powered laptops with
1230 APM compliant BIOSes. If you say Y here, the system time will be
1231 reset after a RESUME operation, the /proc/apm device will provide
1232 battery status information, and user-space programs will receive
1233 notification of APM "events" (e.g. battery status change).
1235 If you select "Y" here, you can disable actual use of the APM
1236 BIOS by passing the "apm=off" option to the kernel at boot time.
1238 Note that the APM support is almost completely disabled for
1239 machines with more than one CPU.
1241 In order to use APM, you will need supporting software. For location
1242 and more information, read <file:Documentation/pm.txt> and the
1243 Battery Powered Linux mini-HOWTO, available from
1244 <http://www.tldp.org/docs.html#howto>.
1246 This driver does not spin down disk drives (see the hdparm(8)
1247 manpage ("man 8 hdparm") for that), and it doesn't turn off
1248 VESA-compliant "green" monitors.
1250 This driver does not support the TI 4000M TravelMate and the ACER
1251 486/DX4/75 because they don't have compliant BIOSes. Many "green"
1252 desktop machines also don't have compliant BIOSes, and this driver
1253 may cause those machines to panic during the boot phase.
1255 Generally, if you don't have a battery in your machine, there isn't
1256 much point in using this driver and you should say N. If you get
1257 random kernel OOPSes or reboots that don't seem to be related to
1258 anything, try disabling/enabling this option (or disabling/enabling
1261 Some other things you should try when experiencing seemingly random,
1264 1) make sure that you have enough swap space and that it is
1266 2) pass the "no-hlt" option to the kernel
1267 3) switch on floating point emulation in the kernel and pass
1268 the "no387" option to the kernel
1269 4) pass the "floppy=nodma" option to the kernel
1270 5) pass the "mem=4M" option to the kernel (thereby disabling
1271 all but the first 4 MB of RAM)
1272 6) make sure that the CPU is not over clocked.
1273 7) read the sig11 FAQ at <http://www.bitwizard.nl/sig11/>
1274 8) disable the cache from your BIOS settings
1275 9) install a fan for the video card or exchange video RAM
1276 10) install a better fan for the CPU
1277 11) exchange RAM chips
1278 12) exchange the motherboard.
1280 To compile this driver as a module, choose M here: the
1281 module will be called apm.
1285 config APM_IGNORE_USER_SUSPEND
1286 bool "Ignore USER SUSPEND"
1288 This option will ignore USER SUSPEND requests. On machines with a
1289 compliant APM BIOS, you want to say N. However, on the NEC Versa M
1290 series notebooks, it is necessary to say Y because of a BIOS bug.
1292 config APM_DO_ENABLE
1293 bool "Enable PM at boot time"
1295 Enable APM features at boot time. From page 36 of the APM BIOS
1296 specification: "When disabled, the APM BIOS does not automatically
1297 power manage devices, enter the Standby State, enter the Suspend
1298 State, or take power saving steps in response to CPU Idle calls."
1299 This driver will make CPU Idle calls when Linux is idle (unless this
1300 feature is turned off -- see "Do CPU IDLE calls", below). This
1301 should always save battery power, but more complicated APM features
1302 will be dependent on your BIOS implementation. You may need to turn
1303 this option off if your computer hangs at boot time when using APM
1304 support, or if it beeps continuously instead of suspending. Turn
1305 this off if you have a NEC UltraLite Versa 33/C or a Toshiba
1306 T400CDT. This is off by default since most machines do fine without
1310 bool "Make CPU Idle calls when idle"
1312 Enable calls to APM CPU Idle/CPU Busy inside the kernel's idle loop.
1313 On some machines, this can activate improved power savings, such as
1314 a slowed CPU clock rate, when the machine is idle. These idle calls
1315 are made after the idle loop has run for some length of time (e.g.,
1316 333 mS). On some machines, this will cause a hang at boot time or
1317 whenever the CPU becomes idle. (On machines with more than one CPU,
1318 this option does nothing.)
1320 config APM_DISPLAY_BLANK
1321 bool "Enable console blanking using APM"
1323 Enable console blanking using the APM. Some laptops can use this to
1324 turn off the LCD backlight when the screen blanker of the Linux
1325 virtual console blanks the screen. Note that this is only used by
1326 the virtual console screen blanker, and won't turn off the backlight
1327 when using the X Window system. This also doesn't have anything to
1328 do with your VESA-compliant power-saving monitor. Further, this
1329 option doesn't work for all laptops -- it might not turn off your
1330 backlight at all, or it might print a lot of errors to the console,
1331 especially if you are using gpm.
1333 config APM_ALLOW_INTS
1334 bool "Allow interrupts during APM BIOS calls"
1336 Normally we disable external interrupts while we are making calls to
1337 the APM BIOS as a measure to lessen the effects of a badly behaving
1338 BIOS implementation. The BIOS should reenable interrupts if it
1339 needs to. Unfortunately, some BIOSes do not -- especially those in
1340 many of the newer IBM Thinkpads. If you experience hangs when you
1341 suspend, try setting this to Y. Otherwise, say N.
1343 config APM_REAL_MODE_POWER_OFF
1344 bool "Use real mode APM BIOS call to power off"
1346 Use real mode APM BIOS calls to switch off the computer. This is
1347 a work-around for a number of buggy BIOSes. Switch this option on if
1348 your computer crashes instead of powering off properly.
1352 source "arch/x86/kernel/cpu/cpufreq/Kconfig"
1354 source "drivers/cpuidle/Kconfig"
1359 menu "Bus options (PCI etc.)"
1362 bool "PCI support" if !X86_VISWS
1363 depends on !X86_VOYAGER
1365 select ARCH_SUPPORTS_MSI if (X86_LOCAL_APIC && X86_IO_APIC)
1367 Find out whether you have a PCI motherboard. PCI is the name of a
1368 bus system, i.e. the way the CPU talks to the other stuff inside
1369 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
1370 VESA. If you have PCI, say Y, otherwise N.
1372 The PCI-HOWTO, available from
1373 <http://www.tldp.org/docs.html#howto>, contains valuable
1374 information about which PCI hardware does work under Linux and which
1378 prompt "PCI access mode"
1379 depends on X86_32 && PCI && !X86_VISWS
1382 On PCI systems, the BIOS can be used to detect the PCI devices and
1383 determine their configuration. However, some old PCI motherboards
1384 have BIOS bugs and may crash if this is done. Also, some embedded
1385 PCI-based systems don't have any BIOS at all. Linux can also try to
1386 detect the PCI hardware directly without using the BIOS.
1388 With this option, you can specify how Linux should detect the
1389 PCI devices. If you choose "BIOS", the BIOS will be used,
1390 if you choose "Direct", the BIOS won't be used, and if you
1391 choose "MMConfig", then PCI Express MMCONFIG will be used.
1392 If you choose "Any", the kernel will try MMCONFIG, then the
1393 direct access method and falls back to the BIOS if that doesn't
1394 work. If unsure, go with the default, which is "Any".
1399 config PCI_GOMMCONFIG
1412 depends on X86_32 && !X86_VISWS && PCI && (PCI_GOBIOS || PCI_GOANY)
1414 # x86-64 doesn't support PCI BIOS access from long mode so always go direct.
1417 depends on PCI && (X86_64 || (PCI_GODIRECT || PCI_GOANY) || X86_VISWS)
1421 depends on X86_32 && PCI && ACPI && (PCI_GOMMCONFIG || PCI_GOANY)
1428 bool "Support mmconfig PCI config space access"
1429 depends on X86_64 && PCI && ACPI
1432 bool "Support for DMA Remapping Devices (EXPERIMENTAL)"
1433 depends on X86_64 && PCI_MSI && ACPI && EXPERIMENTAL
1435 DMA remapping (DMAR) devices support enables independent address
1436 translations for Direct Memory Access (DMA) from devices.
1437 These DMA remapping devices are reported via ACPI tables
1438 and include PCI device scope covered by these DMA
1443 prompt "Support for Graphics workaround"
1446 Current Graphics drivers tend to use physical address
1447 for DMA and avoid using DMA APIs. Setting this config
1448 option permits the IOMMU driver to set a unity map for
1449 all the OS-visible memory. Hence the driver can continue
1450 to use physical addresses for DMA.
1452 config DMAR_FLOPPY_WA
1456 Floppy disk drivers are know to bypass DMA API calls
1457 thereby failing to work when IOMMU is enabled. This
1458 workaround will setup a 1:1 mapping for the first
1459 16M to make floppy (an ISA device) work.
1461 source "drivers/pci/pcie/Kconfig"
1463 source "drivers/pci/Kconfig"
1465 # x86_64 have no ISA slots, but do have ISA-style DMA.
1473 depends on !(X86_VOYAGER || X86_VISWS)
1475 Find out whether you have ISA slots on your motherboard. ISA is the
1476 name of a bus system, i.e. the way the CPU talks to the other stuff
1477 inside your box. Other bus systems are PCI, EISA, MicroChannel
1478 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
1479 newer boards don't support it. If you have ISA, say Y, otherwise N.
1485 The Extended Industry Standard Architecture (EISA) bus was
1486 developed as an open alternative to the IBM MicroChannel bus.
1488 The EISA bus provided some of the features of the IBM MicroChannel
1489 bus while maintaining backward compatibility with cards made for
1490 the older ISA bus. The EISA bus saw limited use between 1988 and
1491 1995 when it was made obsolete by the PCI bus.
1493 Say Y here if you are building a kernel for an EISA-based machine.
1497 source "drivers/eisa/Kconfig"
1500 bool "MCA support" if !(X86_VISWS || X86_VOYAGER)
1501 default y if X86_VOYAGER
1503 MicroChannel Architecture is found in some IBM PS/2 machines and
1504 laptops. It is a bus system similar to PCI or ISA. See
1505 <file:Documentation/mca.txt> (and especially the web page given
1506 there) before attempting to build an MCA bus kernel.
1508 source "drivers/mca/Kconfig"
1511 tristate "NatSemi SCx200 support"
1512 depends on !X86_VOYAGER
1514 This provides basic support for National Semiconductor's
1515 (now AMD's) Geode processors. The driver probes for the
1516 PCI-IDs of several on-chip devices, so its a good dependency
1517 for other scx200_* drivers.
1519 If compiled as a module, the driver is named scx200.
1521 config SCx200HR_TIMER
1522 tristate "NatSemi SCx200 27MHz High-Resolution Timer Support"
1523 depends on SCx200 && GENERIC_TIME
1526 This driver provides a clocksource built upon the on-chip
1527 27MHz high-resolution timer. Its also a workaround for
1528 NSC Geode SC-1100's buggy TSC, which loses time when the
1529 processor goes idle (as is done by the scheduler). The
1530 other workaround is idle=poll boot option.
1532 config GEODE_MFGPT_TIMER
1534 prompt "Geode Multi-Function General Purpose Timer (MFGPT) events"
1535 depends on MGEODE_LX && GENERIC_TIME && GENERIC_CLOCKEVENTS
1537 This driver provides a clock event source based on the MFGPT
1538 timer(s) in the CS5535 and CS5536 companion chip for the geode.
1539 MFGPTs have a better resolution and max interval than the
1540 generic PIT, and are suitable for use as high-res timers.
1546 depends on AGP_AMD64 || (X86_64 && (GART_IOMMU || (PCI && NUMA)))
1548 source "drivers/pcmcia/Kconfig"
1550 source "drivers/pci/hotplug/Kconfig"
1555 menu "Executable file formats / Emulations"
1557 source "fs/Kconfig.binfmt"
1559 config IA32_EMULATION
1560 bool "IA32 Emulation"
1562 select COMPAT_BINFMT_ELF
1564 Include code to run 32-bit programs under a 64-bit kernel. You should
1565 likely turn this on, unless you're 100% sure that you don't have any
1566 32-bit programs left.
1569 tristate "IA32 a.out support"
1570 depends on IA32_EMULATION
1572 Support old a.out binaries in the 32bit emulation.
1576 depends on IA32_EMULATION
1578 config COMPAT_FOR_U64_ALIGNMENT
1582 config SYSVIPC_COMPAT
1584 depends on X86_64 && COMPAT && SYSVIPC
1589 source "net/Kconfig"
1591 source "drivers/Kconfig"
1593 source "drivers/firmware/Kconfig"
1597 source "kernel/Kconfig.instrumentation"
1599 source "arch/x86/Kconfig.debug"
1601 source "security/Kconfig"
1603 source "crypto/Kconfig"
1605 source "arch/x86/kvm/Kconfig"
1607 source "lib/Kconfig"
projects / linux-2.6 / blob