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
123 config ARCH_POPULATES_NODE_MAP
130 # Use the generic interrupt handling code in kernel/irq/:
131 config GENERIC_HARDIRQS
135 config GENERIC_IRQ_PROBE
139 config GENERIC_PENDING_IRQ
141 depends on GENERIC_HARDIRQS && SMP
146 depends on SMP && ((X86_32 && !X86_VOYAGER) || X86_64)
151 depends on X86_32 && SMP
155 depends on X86_64 && SMP
160 depends on (X86_32 && !(X86_VISWS || X86_VOYAGER)) || (X86_64 && !MK8)
163 config X86_BIOS_REBOOT
165 depends on X86_32 && !(X86_VISWS || X86_VOYAGER)
168 config X86_TRAMPOLINE
170 depends on X86_SMP || (X86_VOYAGER && SMP)
175 source "init/Kconfig"
177 menu "Processor type and features"
179 source "kernel/time/Kconfig"
182 bool "Symmetric multi-processing support"
184 This enables support for systems with more than one CPU. If you have
185 a system with only one CPU, like most personal computers, say N. If
186 you have a system with more than one CPU, say Y.
188 If you say N here, the kernel will run on single and multiprocessor
189 machines, but will use only one CPU of a multiprocessor machine. If
190 you say Y here, the kernel will run on many, but not all,
191 singleprocessor machines. On a singleprocessor machine, the kernel
192 will run faster if you say N here.
194 Note that if you say Y here and choose architecture "586" or
195 "Pentium" under "Processor family", the kernel will not work on 486
196 architectures. Similarly, multiprocessor kernels for the "PPro"
197 architecture may not work on all Pentium based boards.
199 People using multiprocessor machines who say Y here should also say
200 Y to "Enhanced Real Time Clock Support", below. The "Advanced Power
201 Management" code will be disabled if you say Y here.
203 See also the <file:Documentation/smp.txt>,
204 <file:Documentation/i386/IO-APIC.txt>,
205 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
206 <http://www.tldp.org/docs.html#howto>.
208 If you don't know what to do here, say N.
211 prompt "Subarchitecture Type"
217 Choose this option if your computer is a standard PC or compatible.
223 Select this for an AMD Elan processor.
225 Do not use this option for K6/Athlon/Opteron processors!
227 If unsure, choose "PC-compatible" instead.
232 select SMP if !BROKEN
234 Voyager is an MCA-based 32-way capable SMP architecture proprietary
235 to NCR Corp. Machine classes 345x/35xx/4100/51xx are Voyager-based.
239 If you do not specifically know you have a Voyager based machine,
240 say N here, otherwise the kernel you build will not be bootable.
243 bool "NUMAQ (IBM/Sequent)"
248 This option is used for getting Linux to run on a (IBM/Sequent) NUMA
249 multiquad box. This changes the way that processors are bootstrapped,
250 and uses Clustered Logical APIC addressing mode instead of Flat Logical.
251 You will need a new lynxer.elf file to flash your firmware with - send
252 email to <Martin.Bligh@us.ibm.com>.
255 bool "Summit/EXA (IBM x440)"
256 depends on X86_32 && SMP
258 This option is needed for IBM systems that use the Summit/EXA chipset.
259 In particular, it is needed for the x440.
261 If you don't have one of these computers, you should say N here.
262 If you want to build a NUMA kernel, you must select ACPI.
265 bool "Support for other sub-arch SMP systems with more than 8 CPUs"
266 depends on X86_32 && SMP
268 This option is needed for the systems that have more than 8 CPUs
269 and if the system is not of any sub-arch type above.
271 If you don't have such a system, you should say N here.
274 bool "SGI 320/540 (Visual Workstation)"
277 The SGI Visual Workstation series is an IA32-based workstation
278 based on SGI systems chips with some legacy PC hardware attached.
280 Say Y here to create a kernel to run on the SGI 320 or 540.
282 A kernel compiled for the Visual Workstation will not run on PCs
283 and vice versa. See <file:Documentation/sgi-visws.txt> for details.
285 config X86_GENERICARCH
286 bool "Generic architecture (Summit, bigsmp, ES7000, default)"
289 This option compiles in the Summit, bigsmp, ES7000, default subarchitectures.
290 It is intended for a generic binary kernel.
291 If you want a NUMA kernel, select ACPI. We need SRAT for NUMA.
294 bool "Support for Unisys ES7000 IA32 series"
295 depends on X86_32 && SMP
297 Support for Unisys ES7000 systems. Say 'Y' here if this kernel is
298 supposed to run on an IA32-based Unisys ES7000 system.
299 Only choose this option if you have such a system, otherwise you
303 bool "RDC R-321x SoC"
306 select X86_REBOOTFIXUPS
310 This option is needed for RDC R-321x system-on-chip, also known
312 If you don't have one of these chips, you should say N here.
315 bool "Support for ScaleMP vSMP"
316 depends on X86_64 && PCI
318 Support for ScaleMP vSMP systems. Say 'Y' here if this kernel is
319 supposed to run on these EM64T-based machines. Only choose this option
320 if you have one of these machines.
324 config SCHED_NO_NO_OMIT_FRAME_POINTER
326 prompt "Single-depth WCHAN output"
329 Calculate simpler /proc/<PID>/wchan values. If this option
330 is disabled then wchan values will recurse back to the
331 caller function. This provides more accurate wchan values,
332 at the expense of slightly more scheduling overhead.
334 If in doubt, say "Y".
336 menuconfig PARAVIRT_GUEST
337 bool "Paravirtualized guest support"
339 Say Y here to get to see options related to running Linux under
340 various hypervisors. This option alone does not add any kernel code.
342 If you say N, all options in this submenu will be skipped and disabled.
346 source "arch/x86/xen/Kconfig"
349 bool "VMI Guest support"
352 depends on !(X86_VISWS || X86_VOYAGER)
354 VMI provides a paravirtualized interface to the VMware ESX server
355 (it could be used by other hypervisors in theory too, but is not
356 at the moment), by linking the kernel to a GPL-ed ROM module
357 provided by the hypervisor.
359 source "arch/x86/lguest/Kconfig"
362 bool "Enable paravirtualization code"
363 depends on !(X86_VISWS || X86_VOYAGER)
365 This changes the kernel so it can modify itself when it is run
366 under a hypervisor, potentially improving performance significantly
367 over full virtualization. However, when run without a hypervisor
368 the kernel is theoretically slower and slightly larger.
374 depends on X86_32 && ACPI && NUMA && (X86_SUMMIT || X86_GENERICARCH)
377 config HAVE_ARCH_PARSE_SRAT
381 config X86_SUMMIT_NUMA
383 depends on X86_32 && NUMA && (X86_SUMMIT || X86_GENERICARCH)
385 config X86_CYCLONE_TIMER
387 depends on X86_32 && X86_SUMMIT || X86_GENERICARCH
389 config ES7000_CLUSTERED_APIC
391 depends on SMP && X86_ES7000 && MPENTIUMIII
393 source "arch/x86/Kconfig.cpu"
397 prompt "HPET Timer Support" if X86_32
399 Use the IA-PC HPET (High Precision Event Timer) to manage
400 time in preference to the PIT and RTC, if a HPET is
402 HPET is the next generation timer replacing legacy 8254s.
403 The HPET provides a stable time base on SMP
404 systems, unlike the TSC, but it is more expensive to access,
405 as it is off-chip. You can find the HPET spec at
406 <http://www.intel.com/hardwaredesign/hpetspec.htm>.
408 You can safely choose Y here. However, HPET will only be
409 activated if the platform and the BIOS support this feature.
410 Otherwise the 8254 will be used for timing services.
412 Choose N to continue using the legacy 8254 timer.
414 config HPET_EMULATE_RTC
416 depends on HPET_TIMER && (RTC=y || RTC=m)
418 # Mark as embedded because too many people got it wrong.
419 # The code disables itself when not needed.
421 bool "GART IOMMU support" if EMBEDDED
425 depends on X86_64 && PCI
427 Support for full DMA access of devices with 32bit memory access only
428 on systems with more than 3GB. This is usually needed for USB,
429 sound, many IDE/SATA chipsets and some other devices.
430 Provides a driver for the AMD Athlon64/Opteron/Turion/Sempron GART
431 based hardware IOMMU and a software bounce buffer based IOMMU used
432 on Intel systems and as fallback.
433 The code is only active when needed (enough memory and limited
434 device) unless CONFIG_IOMMU_DEBUG or iommu=force is specified
438 bool "IBM Calgary IOMMU support"
440 depends on X86_64 && PCI && EXPERIMENTAL
442 Support for hardware IOMMUs in IBM's xSeries x366 and x460
443 systems. Needed to run systems with more than 3GB of memory
444 properly with 32-bit PCI devices that do not support DAC
445 (Double Address Cycle). Calgary also supports bus level
446 isolation, where all DMAs pass through the IOMMU. This
447 prevents them from going anywhere except their intended
448 destination. This catches hard-to-find kernel bugs and
449 mis-behaving drivers and devices that do not use the DMA-API
450 properly to set up their DMA buffers. The IOMMU can be
451 turned off at boot time with the iommu=off parameter.
452 Normally the kernel will make the right choice by itself.
455 config CALGARY_IOMMU_ENABLED_BY_DEFAULT
457 prompt "Should Calgary be enabled by default?"
458 depends on CALGARY_IOMMU
460 Should Calgary be enabled by default? if you choose 'y', Calgary
461 will be used (if it exists). If you choose 'n', Calgary will not be
462 used even if it exists. If you choose 'n' and would like to use
463 Calgary anyway, pass 'iommu=calgary' on the kernel command line.
466 # need this always selected by IOMMU for the VIA workaround
470 Support for software bounce buffers used on x86-64 systems
471 which don't have a hardware IOMMU (e.g. the current generation
472 of Intel's x86-64 CPUs). Using this PCI devices which can only
473 access 32-bits of memory can be used on systems with more than
474 3 GB of memory. If unsure, say Y.
478 int "Maximum number of CPUs (2-255)"
481 default "32" if X86_NUMAQ || X86_SUMMIT || X86_BIGSMP || X86_ES7000
484 This allows you to specify the maximum number of CPUs which this
485 kernel will support. The maximum supported value is 255 and the
486 minimum value which makes sense is 2.
488 This is purely to save memory - each supported CPU adds
489 approximately eight kilobytes to the kernel image.
492 bool "SMT (Hyperthreading) scheduler support"
493 depends on (X86_64 && SMP) || (X86_32 && X86_HT)
495 SMT scheduler support improves the CPU scheduler's decision making
496 when dealing with Intel Pentium 4 chips with HyperThreading at a
497 cost of slightly increased overhead in some places. If unsure say
502 prompt "Multi-core scheduler support"
503 depends on (X86_64 && SMP) || (X86_32 && X86_HT)
505 Multi-core scheduler support improves the CPU scheduler's decision
506 making when dealing with multi-core CPU chips at a cost of slightly
507 increased overhead in some places. If unsure say N here.
509 source "kernel/Kconfig.preempt"
512 bool "Local APIC support on uniprocessors"
513 depends on X86_32 && !SMP && !(X86_VISWS || X86_VOYAGER || X86_GENERICARCH)
515 A local APIC (Advanced Programmable Interrupt Controller) is an
516 integrated interrupt controller in the CPU. If you have a single-CPU
517 system which has a processor with a local APIC, you can say Y here to
518 enable and use it. If you say Y here even though your machine doesn't
519 have a local APIC, then the kernel will still run with no slowdown at
520 all. The local APIC supports CPU-generated self-interrupts (timer,
521 performance counters), and the NMI watchdog which detects hard
525 bool "IO-APIC support on uniprocessors"
526 depends on X86_UP_APIC
528 An IO-APIC (I/O Advanced Programmable Interrupt Controller) is an
529 SMP-capable replacement for PC-style interrupt controllers. Most
530 SMP systems and many recent uniprocessor systems have one.
532 If you have a single-CPU system with an IO-APIC, you can say Y here
533 to use it. If you say Y here even though your machine doesn't have
534 an IO-APIC, then the kernel will still run with no slowdown at all.
536 config X86_LOCAL_APIC
538 depends on X86_64 || (X86_32 && (X86_UP_APIC || ((X86_VISWS || SMP) && !X86_VOYAGER) || X86_GENERICARCH))
542 depends on X86_64 || (X86_32 && (X86_UP_IOAPIC || (SMP && !(X86_VISWS || X86_VOYAGER)) || X86_GENERICARCH))
544 config X86_VISWS_APIC
546 depends on X86_32 && X86_VISWS
549 bool "Machine Check Exception"
550 depends on !X86_VOYAGER
552 Machine Check Exception support allows the processor to notify the
553 kernel if it detects a problem (e.g. overheating, component failure).
554 The action the kernel takes depends on the severity of the problem,
555 ranging from a warning message on the console, to halting the machine.
556 Your processor must be a Pentium or newer to support this - check the
557 flags in /proc/cpuinfo for mce. Note that some older Pentium systems
558 have a design flaw which leads to false MCE events - hence MCE is
559 disabled on all P5 processors, unless explicitly enabled with "mce"
560 as a boot argument. Similarly, if MCE is built in and creates a
561 problem on some new non-standard machine, you can boot with "nomce"
562 to disable it. MCE support simply ignores non-MCE processors like
563 the 386 and 486, so nearly everyone can say Y here.
567 prompt "Intel MCE features"
568 depends on X86_64 && X86_MCE && X86_LOCAL_APIC
570 Additional support for intel specific MCE features such as
575 prompt "AMD MCE features"
576 depends on X86_64 && X86_MCE && X86_LOCAL_APIC
578 Additional support for AMD specific MCE features such as
579 the DRAM Error Threshold.
581 config X86_MCE_NONFATAL
582 tristate "Check for non-fatal errors on AMD Athlon/Duron / Intel Pentium 4"
583 depends on X86_32 && X86_MCE
585 Enabling this feature starts a timer that triggers every 5 seconds which
586 will look at the machine check registers to see if anything happened.
587 Non-fatal problems automatically get corrected (but still logged).
588 Disable this if you don't want to see these messages.
589 Seeing the messages this option prints out may be indicative of dying
590 or out-of-spec (ie, overclocked) hardware.
591 This option only does something on certain CPUs.
592 (AMD Athlon/Duron and Intel Pentium 4)
594 config X86_MCE_P4THERMAL
595 bool "check for P4 thermal throttling interrupt."
596 depends on X86_32 && X86_MCE && (X86_UP_APIC || SMP) && !X86_VISWS
598 Enabling this feature will cause a message to be printed when the P4
599 enters thermal throttling.
602 bool "Enable VM86 support" if EMBEDDED
606 This option is required by programs like DOSEMU to run 16-bit legacy
607 code on X86 processors. It also may be needed by software like
608 XFree86 to initialize some video cards via BIOS. Disabling this
609 option saves about 6k.
612 tristate "Toshiba Laptop support"
615 This adds a driver to safely access the System Management Mode of
616 the CPU on Toshiba portables with a genuine Toshiba BIOS. It does
617 not work on models with a Phoenix BIOS. The System Management Mode
618 is used to set the BIOS and power saving options on Toshiba portables.
620 For information on utilities to make use of this driver see the
621 Toshiba Linux utilities web site at:
622 <http://www.buzzard.org.uk/toshiba/>.
624 Say Y if you intend to run this kernel on a Toshiba portable.
628 tristate "Dell laptop support"
631 This adds a driver to safely access the System Management Mode
632 of the CPU on the Dell Inspiron 8000. The System Management Mode
633 is used to read cpu temperature and cooling fan status and to
634 control the fans on the I8K portables.
636 This driver has been tested only on the Inspiron 8000 but it may
637 also work with other Dell laptops. You can force loading on other
638 models by passing the parameter `force=1' to the module. Use at
641 For information on utilities to make use of this driver see the
642 I8K Linux utilities web site at:
643 <http://people.debian.org/~dz/i8k/>
645 Say Y if you intend to run this kernel on a Dell Inspiron 8000.
648 config X86_REBOOTFIXUPS
650 prompt "Enable X86 board specific fixups for reboot"
651 depends on X86_32 && X86
653 This enables chipset and/or board specific fixups to be done
654 in order to get reboot to work correctly. This is only needed on
655 some combinations of hardware and BIOS. The symptom, for which
656 this config is intended, is when reboot ends with a stalled/hung
659 Currently, the only fixup is for the Geode machines using
660 CS5530A and CS5536 chipsets and the RDC R-321x SoC.
662 Say Y if you want to enable the fixup. Currently, it's safe to
663 enable this option even if you don't need it.
667 tristate "/dev/cpu/microcode - Intel IA32 CPU microcode support"
670 If you say Y here, you will be able to update the microcode on
671 Intel processors in the IA32 family, e.g. Pentium Pro, Pentium II,
672 Pentium III, Pentium 4, Xeon etc. You will obviously need the
673 actual microcode binary data itself which is not shipped with the
676 For latest news and information on obtaining all the required
677 ingredients for this driver, check:
678 <http://www.urbanmyth.org/microcode/>.
680 To compile this driver as a module, choose M here: the
681 module will be called microcode.
683 config MICROCODE_OLD_INTERFACE
688 tristate "/dev/cpu/*/msr - Model-specific register support"
690 This device gives privileged processes access to the x86
691 Model-Specific Registers (MSRs). It is a character device with
692 major 202 and minors 0 to 31 for /dev/cpu/0/msr to /dev/cpu/31/msr.
693 MSR accesses are directed to a specific CPU on multi-processor
697 tristate "/dev/cpu/*/cpuid - CPU information support"
699 This device gives processes access to the x86 CPUID instruction to
700 be executed on a specific processor. It is a character device
701 with major 203 and minors 0 to 31 for /dev/cpu/0/cpuid to
705 prompt "High Memory Support"
706 default HIGHMEM4G if !X86_NUMAQ
707 default HIGHMEM64G if X86_NUMAQ
712 depends on !X86_NUMAQ
714 Linux can use up to 64 Gigabytes of physical memory on x86 systems.
715 However, the address space of 32-bit x86 processors is only 4
716 Gigabytes large. That means that, if you have a large amount of
717 physical memory, not all of it can be "permanently mapped" by the
718 kernel. The physical memory that's not permanently mapped is called
721 If you are compiling a kernel which will never run on a machine with
722 more than 1 Gigabyte total physical RAM, answer "off" here (default
723 choice and suitable for most users). This will result in a "3GB/1GB"
724 split: 3GB are mapped so that each process sees a 3GB virtual memory
725 space and the remaining part of the 4GB virtual memory space is used
726 by the kernel to permanently map as much physical memory as
729 If the machine has between 1 and 4 Gigabytes physical RAM, then
732 If more than 4 Gigabytes is used then answer "64GB" here. This
733 selection turns Intel PAE (Physical Address Extension) mode on.
734 PAE implements 3-level paging on IA32 processors. PAE is fully
735 supported by Linux, PAE mode is implemented on all recent Intel
736 processors (Pentium Pro and better). NOTE: If you say "64GB" here,
737 then the kernel will not boot on CPUs that don't support PAE!
739 The actual amount of total physical memory will either be
740 auto detected or can be forced by using a kernel command line option
741 such as "mem=256M". (Try "man bootparam" or see the documentation of
742 your boot loader (lilo or loadlin) about how to pass options to the
743 kernel at boot time.)
745 If unsure, say "off".
749 depends on !X86_NUMAQ
751 Select this if you have a 32-bit processor and between 1 and 4
752 gigabytes of physical RAM.
756 depends on !M386 && !M486
759 Select this if you have a 32-bit processor and more than 4
760 gigabytes of physical RAM.
765 depends on EXPERIMENTAL
766 prompt "Memory split" if EMBEDDED
770 Select the desired split between kernel and user memory.
772 If the address range available to the kernel is less than the
773 physical memory installed, the remaining memory will be available
774 as "high memory". Accessing high memory is a little more costly
775 than low memory, as it needs to be mapped into the kernel first.
776 Note that increasing the kernel address space limits the range
777 available to user programs, making the address space there
778 tighter. Selecting anything other than the default 3G/1G split
779 will also likely make your kernel incompatible with binary-only
782 If you are not absolutely sure what you are doing, leave this
786 bool "3G/1G user/kernel split"
787 config VMSPLIT_3G_OPT
789 bool "3G/1G user/kernel split (for full 1G low memory)"
791 bool "2G/2G user/kernel split"
792 config VMSPLIT_2G_OPT
794 bool "2G/2G user/kernel split (for full 2G low memory)"
796 bool "1G/3G user/kernel split"
801 default 0xB0000000 if VMSPLIT_3G_OPT
802 default 0x80000000 if VMSPLIT_2G
803 default 0x78000000 if VMSPLIT_2G_OPT
804 default 0x40000000 if VMSPLIT_1G
810 depends on X86_32 && (HIGHMEM64G || HIGHMEM4G)
814 prompt "PAE (Physical Address Extension) Support"
815 depends on X86_32 && !HIGHMEM4G
816 select RESOURCES_64BIT
818 PAE is required for NX support, and furthermore enables
819 larger swapspace support for non-overcommit purposes. It
820 has the cost of more pagetable lookup overhead, and also
821 consumes more pagetable space per process.
823 # Common NUMA Features
825 bool "Numa Memory Allocation and Scheduler Support (EXPERIMENTAL)"
827 depends on X86_64 || (X86_32 && HIGHMEM64G && (X86_NUMAQ || (X86_SUMMIT || X86_GENERICARCH) && ACPI) && EXPERIMENTAL)
829 default y if (X86_NUMAQ || X86_SUMMIT)
831 Enable NUMA (Non Uniform Memory Access) support.
832 The kernel will try to allocate memory used by a CPU on the
833 local memory controller of the CPU and add some more
834 NUMA awareness to the kernel.
836 For i386 this is currently highly experimental and should be only
837 used for kernel development. It might also cause boot failures.
838 For x86_64 this is recommended on all multiprocessor Opteron systems.
839 If the system is EM64T, you should say N unless your system is
842 comment "NUMA (Summit) requires SMP, 64GB highmem support, ACPI"
843 depends on X86_32 && X86_SUMMIT && (!HIGHMEM64G || !ACPI)
847 prompt "Old style AMD Opteron NUMA detection"
848 depends on X86_64 && NUMA && PCI
850 Enable K8 NUMA node topology detection. You should say Y here if
851 you have a multi processor AMD K8 system. This uses an old
852 method to read the NUMA configuration directly from the builtin
853 Northbridge of Opteron. It is recommended to use X86_64_ACPI_NUMA
854 instead, which also takes priority if both are compiled in.
856 config X86_64_ACPI_NUMA
858 prompt "ACPI NUMA detection"
859 depends on X86_64 && NUMA && ACPI && PCI
862 Enable ACPI SRAT based node topology detection.
865 bool "NUMA emulation"
866 depends on X86_64 && NUMA
868 Enable NUMA emulation. A flat machine will be split
869 into virtual nodes when booted with "numa=fake=N", where N is the
870 number of nodes. This is only useful for debugging.
875 default "6" if X86_64
876 default "4" if X86_NUMAQ
878 depends on NEED_MULTIPLE_NODES
880 config HAVE_ARCH_BOOTMEM_NODE
882 depends on X86_32 && NUMA
884 config ARCH_HAVE_MEMORY_PRESENT
886 depends on X86_32 && DISCONTIGMEM
888 config NEED_NODE_MEMMAP_SIZE
890 depends on X86_32 && (DISCONTIGMEM || SPARSEMEM)
892 config HAVE_ARCH_ALLOC_REMAP
894 depends on X86_32 && NUMA
896 config ARCH_FLATMEM_ENABLE
898 depends on X86_32 && ARCH_SELECT_MEMORY_MODEL && X86_PC && !NUMA
900 config ARCH_DISCONTIGMEM_ENABLE
902 depends on NUMA && X86_32
904 config ARCH_DISCONTIGMEM_DEFAULT
906 depends on NUMA && X86_32
908 config ARCH_SPARSEMEM_DEFAULT
912 config ARCH_SPARSEMEM_ENABLE
914 depends on X86_64 || NUMA || (EXPERIMENTAL && X86_PC)
915 select SPARSEMEM_STATIC if X86_32
916 select SPARSEMEM_VMEMMAP_ENABLE if X86_64
918 config ARCH_SELECT_MEMORY_MODEL
920 depends on ARCH_SPARSEMEM_ENABLE
922 config ARCH_MEMORY_PROBE
924 depends on MEMORY_HOTPLUG
929 bool "Allocate 3rd-level pagetables from highmem"
930 depends on X86_32 && (HIGHMEM4G || HIGHMEM64G)
932 The VM uses one page table entry for each page of physical memory.
933 For systems with a lot of RAM, this can be wasteful of precious
934 low memory. Setting this option will put user-space page table
935 entries in high memory.
937 config MATH_EMULATION
939 prompt "Math emulation" if X86_32
941 Linux can emulate a math coprocessor (used for floating point
942 operations) if you don't have one. 486DX and Pentium processors have
943 a math coprocessor built in, 486SX and 386 do not, unless you added
944 a 487DX or 387, respectively. (The messages during boot time can
945 give you some hints here ["man dmesg"].) Everyone needs either a
946 coprocessor or this emulation.
948 If you don't have a math coprocessor, you need to say Y here; if you
949 say Y here even though you have a coprocessor, the coprocessor will
950 be used nevertheless. (This behavior can be changed with the kernel
951 command line option "no387", which comes handy if your coprocessor
952 is broken. Try "man bootparam" or see the documentation of your boot
953 loader (lilo or loadlin) about how to pass options to the kernel at
954 boot time.) This means that it is a good idea to say Y here if you
955 intend to use this kernel on different machines.
957 More information about the internals of the Linux math coprocessor
958 emulation can be found in <file:arch/x86/math-emu/README>.
960 If you are not sure, say Y; apart from resulting in a 66 KB bigger
961 kernel, it won't hurt.
964 bool "MTRR (Memory Type Range Register) support"
966 On Intel P6 family processors (Pentium Pro, Pentium II and later)
967 the Memory Type Range Registers (MTRRs) may be used to control
968 processor access to memory ranges. This is most useful if you have
969 a video (VGA) card on a PCI or AGP bus. Enabling write-combining
970 allows bus write transfers to be combined into a larger transfer
971 before bursting over the PCI/AGP bus. This can increase performance
972 of image write operations 2.5 times or more. Saying Y here creates a
973 /proc/mtrr file which may be used to manipulate your processor's
974 MTRRs. Typically the X server should use this.
976 This code has a reasonably generic interface so that similar
977 control registers on other processors can be easily supported
980 The Cyrix 6x86, 6x86MX and M II processors have Address Range
981 Registers (ARRs) which provide a similar functionality to MTRRs. For
982 these, the ARRs are used to emulate the MTRRs.
983 The AMD K6-2 (stepping 8 and above) and K6-3 processors have two
984 MTRRs. The Centaur C6 (WinChip) has 8 MCRs, allowing
985 write-combining. All of these processors are supported by this code
986 and it makes sense to say Y here if you have one of them.
988 Saying Y here also fixes a problem with buggy SMP BIOSes which only
989 set the MTRRs for the boot CPU and not for the secondary CPUs. This
990 can lead to all sorts of problems, so it's good to say Y here.
992 You can safely say Y even if your machine doesn't have MTRRs, you'll
993 just add about 9 KB to your kernel.
995 See <file:Documentation/mtrr.txt> for more information.
999 prompt "EFI runtime service support"
1002 This enables the kernel to use EFI runtime services that are
1003 available (such as the EFI variable services).
1005 This option is only useful on systems that have EFI firmware.
1006 In addition, you should use the latest ELILO loader available
1007 at <http://elilo.sourceforge.net> in order to take advantage
1008 of EFI runtime services. However, even with this option, the
1009 resultant kernel should continue to boot on existing non-EFI
1014 prompt "Enable kernel irq balancing"
1015 depends on X86_32 && SMP && X86_IO_APIC
1017 The default yes will allow the kernel to do irq load balancing.
1018 Saying no will keep the kernel from doing irq load balancing.
1022 prompt "Enable seccomp to safely compute untrusted bytecode"
1025 This kernel feature is useful for number crunching applications
1026 that may need to compute untrusted bytecode during their
1027 execution. By using pipes or other transports made available to
1028 the process as file descriptors supporting the read/write
1029 syscalls, it's possible to isolate those applications in
1030 their own address space using seccomp. Once seccomp is
1031 enabled via /proc/<pid>/seccomp, it cannot be disabled
1032 and the task is only allowed to execute a few safe syscalls
1033 defined by each seccomp mode.
1035 If unsure, say Y. Only embedded should say N here.
1037 config CC_STACKPROTECTOR
1038 bool "Enable -fstack-protector buffer overflow detection (EXPERIMENTAL)"
1039 depends on X86_64 && EXPERIMENTAL
1041 This option turns on the -fstack-protector GCC feature. This
1042 feature puts, at the beginning of critical functions, a canary
1043 value on the stack just before the return address, and validates
1044 the value just before actually returning. Stack based buffer
1045 overflows (that need to overwrite this return address) now also
1046 overwrite the canary, which gets detected and the attack is then
1047 neutralized via a kernel panic.
1049 This feature requires gcc version 4.2 or above, or a distribution
1050 gcc with the feature backported. Older versions are automatically
1051 detected and for those versions, this configuration option is ignored.
1053 config CC_STACKPROTECTOR_ALL
1054 bool "Use stack-protector for all functions"
1055 depends on CC_STACKPROTECTOR
1057 Normally, GCC only inserts the canary value protection for
1058 functions that use large-ish on-stack buffers. By enabling
1059 this option, GCC will be asked to do this for ALL functions.
1061 source kernel/Kconfig.hz
1064 bool "kexec system call"
1066 kexec is a system call that implements the ability to shutdown your
1067 current kernel, and to start another kernel. It is like a reboot
1068 but it is independent of the system firmware. And like a reboot
1069 you can start any kernel with it, not just Linux.
1071 The name comes from the similarity to the exec system call.
1073 It is an ongoing process to be certain the hardware in a machine
1074 is properly shutdown, so do not be surprised if this code does not
1075 initially work for you. It may help to enable device hotplugging
1076 support. As of this writing the exact hardware interface is
1077 strongly in flux, so no good recommendation can be made.
1080 bool "kernel crash dumps (EXPERIMENTAL)"
1081 depends on EXPERIMENTAL
1082 depends on X86_64 || (X86_32 && HIGHMEM)
1084 Generate crash dump after being started by kexec.
1085 This should be normally only set in special crash dump kernels
1086 which are loaded in the main kernel with kexec-tools into
1087 a specially reserved region and then later executed after
1088 a crash by kdump/kexec. The crash dump kernel must be compiled
1089 to a memory address not used by the main kernel or BIOS using
1090 PHYSICAL_START, or it must be built as a relocatable image
1091 (CONFIG_RELOCATABLE=y).
1092 For more details see Documentation/kdump/kdump.txt
1094 config PHYSICAL_START
1095 hex "Physical address where the kernel is loaded" if (EMBEDDED || CRASH_DUMP)
1096 default "0x1000000" if X86_NUMAQ
1097 default "0x200000" if X86_64
1100 This gives the physical address where the kernel is loaded.
1102 If kernel is a not relocatable (CONFIG_RELOCATABLE=n) then
1103 bzImage will decompress itself to above physical address and
1104 run from there. Otherwise, bzImage will run from the address where
1105 it has been loaded by the boot loader and will ignore above physical
1108 In normal kdump cases one does not have to set/change this option
1109 as now bzImage can be compiled as a completely relocatable image
1110 (CONFIG_RELOCATABLE=y) and be used to load and run from a different
1111 address. This option is mainly useful for the folks who don't want
1112 to use a bzImage for capturing the crash dump and want to use a
1113 vmlinux instead. vmlinux is not relocatable hence a kernel needs
1114 to be specifically compiled to run from a specific memory area
1115 (normally a reserved region) and this option comes handy.
1117 So if you are using bzImage for capturing the crash dump, leave
1118 the value here unchanged to 0x100000 and set CONFIG_RELOCATABLE=y.
1119 Otherwise if you plan to use vmlinux for capturing the crash dump
1120 change this value to start of the reserved region (Typically 16MB
1121 0x1000000). In other words, it can be set based on the "X" value as
1122 specified in the "crashkernel=YM@XM" command line boot parameter
1123 passed to the panic-ed kernel. Typically this parameter is set as
1124 crashkernel=64M@16M. Please take a look at
1125 Documentation/kdump/kdump.txt for more details about crash dumps.
1127 Usage of bzImage for capturing the crash dump is recommended as
1128 one does not have to build two kernels. Same kernel can be used
1129 as production kernel and capture kernel. Above option should have
1130 gone away after relocatable bzImage support is introduced. But it
1131 is present because there are users out there who continue to use
1132 vmlinux for dump capture. This option should go away down the
1135 Don't change this unless you know what you are doing.
1138 bool "Build a relocatable kernel (EXPERIMENTAL)"
1139 depends on EXPERIMENTAL
1141 This builds a kernel image that retains relocation information
1142 so it can be loaded someplace besides the default 1MB.
1143 The relocations tend to make the kernel binary about 10% larger,
1144 but are discarded at runtime.
1146 One use is for the kexec on panic case where the recovery kernel
1147 must live at a different physical address than the primary
1150 Note: If CONFIG_RELOCATABLE=y, then the kernel runs from the address
1151 it has been loaded at and the compile time physical address
1152 (CONFIG_PHYSICAL_START) is ignored.
1154 config PHYSICAL_ALIGN
1156 prompt "Alignment value to which kernel should be aligned" if X86_32
1157 default "0x100000" if X86_32
1158 default "0x200000" if X86_64
1159 range 0x2000 0x400000
1161 This value puts the alignment restrictions on physical address
1162 where kernel is loaded and run from. Kernel is compiled for an
1163 address which meets above alignment restriction.
1165 If bootloader loads the kernel at a non-aligned address and
1166 CONFIG_RELOCATABLE is set, kernel will move itself to nearest
1167 address aligned to above value and run from there.
1169 If bootloader loads the kernel at a non-aligned address and
1170 CONFIG_RELOCATABLE is not set, kernel will ignore the run time
1171 load address and decompress itself to the address it has been
1172 compiled for and run from there. The address for which kernel is
1173 compiled already meets above alignment restrictions. Hence the
1174 end result is that kernel runs from a physical address meeting
1175 above alignment restrictions.
1177 Don't change this unless you know what you are doing.
1180 bool "Support for suspend on SMP and hot-pluggable CPUs (EXPERIMENTAL)"
1181 depends on SMP && HOTPLUG && EXPERIMENTAL && !X86_VOYAGER
1183 Say Y here to experiment with turning CPUs off and on, and to
1184 enable suspend on SMP systems. CPUs can be controlled through
1185 /sys/devices/system/cpu.
1186 Say N if you want to disable CPU hotplug and don't need to
1191 prompt "Compat VDSO support"
1192 depends on X86_32 || IA32_EMULATION
1194 Map the 32-bit VDSO to the predictable old-style address too.
1196 Say N here if you are running a sufficiently recent glibc
1197 version (2.3.3 or later), to remove the high-mapped
1198 VDSO mapping and to exclusively use the randomized VDSO.
1204 config ARCH_ENABLE_MEMORY_HOTPLUG
1206 depends on X86_64 || (X86_32 && HIGHMEM)
1208 config HAVE_ARCH_EARLY_PFN_TO_NID
1212 menu "Power management options"
1213 depends on !X86_VOYAGER
1215 config ARCH_HIBERNATION_HEADER
1217 depends on X86_64 && HIBERNATION
1219 source "kernel/power/Kconfig"
1221 source "drivers/acpi/Kconfig"
1226 depends on APM || APM_MODULE
1229 tristate "APM (Advanced Power Management) BIOS support"
1230 depends on X86_32 && PM_SLEEP && !X86_VISWS
1232 APM is a BIOS specification for saving power using several different
1233 techniques. This is mostly useful for battery powered laptops with
1234 APM compliant BIOSes. If you say Y here, the system time will be
1235 reset after a RESUME operation, the /proc/apm device will provide
1236 battery status information, and user-space programs will receive
1237 notification of APM "events" (e.g. battery status change).
1239 If you select "Y" here, you can disable actual use of the APM
1240 BIOS by passing the "apm=off" option to the kernel at boot time.
1242 Note that the APM support is almost completely disabled for
1243 machines with more than one CPU.
1245 In order to use APM, you will need supporting software. For location
1246 and more information, read <file:Documentation/pm.txt> and the
1247 Battery Powered Linux mini-HOWTO, available from
1248 <http://www.tldp.org/docs.html#howto>.
1250 This driver does not spin down disk drives (see the hdparm(8)
1251 manpage ("man 8 hdparm") for that), and it doesn't turn off
1252 VESA-compliant "green" monitors.
1254 This driver does not support the TI 4000M TravelMate and the ACER
1255 486/DX4/75 because they don't have compliant BIOSes. Many "green"
1256 desktop machines also don't have compliant BIOSes, and this driver
1257 may cause those machines to panic during the boot phase.
1259 Generally, if you don't have a battery in your machine, there isn't
1260 much point in using this driver and you should say N. If you get
1261 random kernel OOPSes or reboots that don't seem to be related to
1262 anything, try disabling/enabling this option (or disabling/enabling
1265 Some other things you should try when experiencing seemingly random,
1268 1) make sure that you have enough swap space and that it is
1270 2) pass the "no-hlt" option to the kernel
1271 3) switch on floating point emulation in the kernel and pass
1272 the "no387" option to the kernel
1273 4) pass the "floppy=nodma" option to the kernel
1274 5) pass the "mem=4M" option to the kernel (thereby disabling
1275 all but the first 4 MB of RAM)
1276 6) make sure that the CPU is not over clocked.
1277 7) read the sig11 FAQ at <http://www.bitwizard.nl/sig11/>
1278 8) disable the cache from your BIOS settings
1279 9) install a fan for the video card or exchange video RAM
1280 10) install a better fan for the CPU
1281 11) exchange RAM chips
1282 12) exchange the motherboard.
1284 To compile this driver as a module, choose M here: the
1285 module will be called apm.
1289 config APM_IGNORE_USER_SUSPEND
1290 bool "Ignore USER SUSPEND"
1292 This option will ignore USER SUSPEND requests. On machines with a
1293 compliant APM BIOS, you want to say N. However, on the NEC Versa M
1294 series notebooks, it is necessary to say Y because of a BIOS bug.
1296 config APM_DO_ENABLE
1297 bool "Enable PM at boot time"
1299 Enable APM features at boot time. From page 36 of the APM BIOS
1300 specification: "When disabled, the APM BIOS does not automatically
1301 power manage devices, enter the Standby State, enter the Suspend
1302 State, or take power saving steps in response to CPU Idle calls."
1303 This driver will make CPU Idle calls when Linux is idle (unless this
1304 feature is turned off -- see "Do CPU IDLE calls", below). This
1305 should always save battery power, but more complicated APM features
1306 will be dependent on your BIOS implementation. You may need to turn
1307 this option off if your computer hangs at boot time when using APM
1308 support, or if it beeps continuously instead of suspending. Turn
1309 this off if you have a NEC UltraLite Versa 33/C or a Toshiba
1310 T400CDT. This is off by default since most machines do fine without
1314 bool "Make CPU Idle calls when idle"
1316 Enable calls to APM CPU Idle/CPU Busy inside the kernel's idle loop.
1317 On some machines, this can activate improved power savings, such as
1318 a slowed CPU clock rate, when the machine is idle. These idle calls
1319 are made after the idle loop has run for some length of time (e.g.,
1320 333 mS). On some machines, this will cause a hang at boot time or
1321 whenever the CPU becomes idle. (On machines with more than one CPU,
1322 this option does nothing.)
1324 config APM_DISPLAY_BLANK
1325 bool "Enable console blanking using APM"
1327 Enable console blanking using the APM. Some laptops can use this to
1328 turn off the LCD backlight when the screen blanker of the Linux
1329 virtual console blanks the screen. Note that this is only used by
1330 the virtual console screen blanker, and won't turn off the backlight
1331 when using the X Window system. This also doesn't have anything to
1332 do with your VESA-compliant power-saving monitor. Further, this
1333 option doesn't work for all laptops -- it might not turn off your
1334 backlight at all, or it might print a lot of errors to the console,
1335 especially if you are using gpm.
1337 config APM_ALLOW_INTS
1338 bool "Allow interrupts during APM BIOS calls"
1340 Normally we disable external interrupts while we are making calls to
1341 the APM BIOS as a measure to lessen the effects of a badly behaving
1342 BIOS implementation. The BIOS should reenable interrupts if it
1343 needs to. Unfortunately, some BIOSes do not -- especially those in
1344 many of the newer IBM Thinkpads. If you experience hangs when you
1345 suspend, try setting this to Y. Otherwise, say N.
1347 config APM_REAL_MODE_POWER_OFF
1348 bool "Use real mode APM BIOS call to power off"
1350 Use real mode APM BIOS calls to switch off the computer. This is
1351 a work-around for a number of buggy BIOSes. Switch this option on if
1352 your computer crashes instead of powering off properly.
1356 source "arch/x86/kernel/cpu/cpufreq/Kconfig"
1358 source "drivers/cpuidle/Kconfig"
1363 menu "Bus options (PCI etc.)"
1366 bool "PCI support" if !X86_VISWS
1367 depends on !X86_VOYAGER
1369 select ARCH_SUPPORTS_MSI if (X86_LOCAL_APIC && X86_IO_APIC)
1371 Find out whether you have a PCI motherboard. PCI is the name of a
1372 bus system, i.e. the way the CPU talks to the other stuff inside
1373 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
1374 VESA. If you have PCI, say Y, otherwise N.
1376 The PCI-HOWTO, available from
1377 <http://www.tldp.org/docs.html#howto>, contains valuable
1378 information about which PCI hardware does work under Linux and which
1382 prompt "PCI access mode"
1383 depends on X86_32 && PCI && !X86_VISWS
1386 On PCI systems, the BIOS can be used to detect the PCI devices and
1387 determine their configuration. However, some old PCI motherboards
1388 have BIOS bugs and may crash if this is done. Also, some embedded
1389 PCI-based systems don't have any BIOS at all. Linux can also try to
1390 detect the PCI hardware directly without using the BIOS.
1392 With this option, you can specify how Linux should detect the
1393 PCI devices. If you choose "BIOS", the BIOS will be used,
1394 if you choose "Direct", the BIOS won't be used, and if you
1395 choose "MMConfig", then PCI Express MMCONFIG will be used.
1396 If you choose "Any", the kernel will try MMCONFIG, then the
1397 direct access method and falls back to the BIOS if that doesn't
1398 work. If unsure, go with the default, which is "Any".
1403 config PCI_GOMMCONFIG
1416 depends on X86_32 && !X86_VISWS && PCI && (PCI_GOBIOS || PCI_GOANY)
1418 # x86-64 doesn't support PCI BIOS access from long mode so always go direct.
1421 depends on PCI && (X86_64 || (PCI_GODIRECT || PCI_GOANY) || X86_VISWS)
1425 depends on X86_32 && PCI && ACPI && (PCI_GOMMCONFIG || PCI_GOANY)
1432 bool "Support mmconfig PCI config space access"
1433 depends on X86_64 && PCI && ACPI
1436 bool "Support for DMA Remapping Devices (EXPERIMENTAL)"
1437 depends on X86_64 && PCI_MSI && ACPI && EXPERIMENTAL
1439 DMA remapping (DMAR) devices support enables independent address
1440 translations for Direct Memory Access (DMA) from devices.
1441 These DMA remapping devices are reported via ACPI tables
1442 and include PCI device scope covered by these DMA
1447 prompt "Support for Graphics workaround"
1450 Current Graphics drivers tend to use physical address
1451 for DMA and avoid using DMA APIs. Setting this config
1452 option permits the IOMMU driver to set a unity map for
1453 all the OS-visible memory. Hence the driver can continue
1454 to use physical addresses for DMA.
1456 config DMAR_FLOPPY_WA
1460 Floppy disk drivers are know to bypass DMA API calls
1461 thereby failing to work when IOMMU is enabled. This
1462 workaround will setup a 1:1 mapping for the first
1463 16M to make floppy (an ISA device) work.
1465 source "drivers/pci/pcie/Kconfig"
1467 source "drivers/pci/Kconfig"
1469 # x86_64 have no ISA slots, but do have ISA-style DMA.
1477 depends on !(X86_VOYAGER || X86_VISWS)
1479 Find out whether you have ISA slots on your motherboard. ISA is the
1480 name of a bus system, i.e. the way the CPU talks to the other stuff
1481 inside your box. Other bus systems are PCI, EISA, MicroChannel
1482 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
1483 newer boards don't support it. If you have ISA, say Y, otherwise N.
1489 The Extended Industry Standard Architecture (EISA) bus was
1490 developed as an open alternative to the IBM MicroChannel bus.
1492 The EISA bus provided some of the features of the IBM MicroChannel
1493 bus while maintaining backward compatibility with cards made for
1494 the older ISA bus. The EISA bus saw limited use between 1988 and
1495 1995 when it was made obsolete by the PCI bus.
1497 Say Y here if you are building a kernel for an EISA-based machine.
1501 source "drivers/eisa/Kconfig"
1504 bool "MCA support" if !(X86_VISWS || X86_VOYAGER)
1505 default y if X86_VOYAGER
1507 MicroChannel Architecture is found in some IBM PS/2 machines and
1508 laptops. It is a bus system similar to PCI or ISA. See
1509 <file:Documentation/mca.txt> (and especially the web page given
1510 there) before attempting to build an MCA bus kernel.
1512 source "drivers/mca/Kconfig"
1515 tristate "NatSemi SCx200 support"
1516 depends on !X86_VOYAGER
1518 This provides basic support for National Semiconductor's
1519 (now AMD's) Geode processors. The driver probes for the
1520 PCI-IDs of several on-chip devices, so its a good dependency
1521 for other scx200_* drivers.
1523 If compiled as a module, the driver is named scx200.
1525 config SCx200HR_TIMER
1526 tristate "NatSemi SCx200 27MHz High-Resolution Timer Support"
1527 depends on SCx200 && GENERIC_TIME
1530 This driver provides a clocksource built upon the on-chip
1531 27MHz high-resolution timer. Its also a workaround for
1532 NSC Geode SC-1100's buggy TSC, which loses time when the
1533 processor goes idle (as is done by the scheduler). The
1534 other workaround is idle=poll boot option.
1536 config GEODE_MFGPT_TIMER
1538 prompt "Geode Multi-Function General Purpose Timer (MFGPT) events"
1539 depends on MGEODE_LX && GENERIC_TIME && GENERIC_CLOCKEVENTS
1541 This driver provides a clock event source based on the MFGPT
1542 timer(s) in the CS5535 and CS5536 companion chip for the geode.
1543 MFGPTs have a better resolution and max interval than the
1544 generic PIT, and are suitable for use as high-res timers.
1550 depends on AGP_AMD64 || (X86_64 && (GART_IOMMU || (PCI && NUMA)))
1552 source "drivers/pcmcia/Kconfig"
1554 source "drivers/pci/hotplug/Kconfig"
1559 menu "Executable file formats / Emulations"
1561 source "fs/Kconfig.binfmt"
1563 config IA32_EMULATION
1564 bool "IA32 Emulation"
1566 select COMPAT_BINFMT_ELF
1568 Include code to run 32-bit programs under a 64-bit kernel. You should
1569 likely turn this on, unless you're 100% sure that you don't have any
1570 32-bit programs left.
1573 tristate "IA32 a.out support"
1574 depends on IA32_EMULATION
1576 Support old a.out binaries in the 32bit emulation.
1580 depends on IA32_EMULATION
1582 config COMPAT_FOR_U64_ALIGNMENT
1586 config SYSVIPC_COMPAT
1588 depends on X86_64 && COMPAT && SYSVIPC
1593 source "net/Kconfig"
1595 source "drivers/Kconfig"
1597 source "drivers/firmware/Kconfig"
1601 source "kernel/Kconfig.instrumentation"
1603 source "arch/x86/Kconfig.debug"
1605 source "security/Kconfig"
1607 source "crypto/Kconfig"
1609 source "arch/x86/kvm/Kconfig"
1611 source "lib/Kconfig"
projects / linux-2.6 / blob