2 mainmenu "Linux Kernel Configuration for x86"
6 bool "64-bit kernel" if ARCH = "x86"
7 default ARCH = "x86_64"
9 Say yes to build a 64-bit kernel - formerly known as x86_64
10 Say no to build a 32-bit kernel - formerly known as i386
24 config GENERIC_LOCKBREAK
30 config GENERIC_CMOS_UPDATE
33 config CLOCKSOURCE_WATCHDOG
36 config GENERIC_CLOCKEVENTS
39 config GENERIC_CLOCKEVENTS_BROADCAST
41 depends on X86_64 || (X86_32 && X86_LOCAL_APIC)
43 config LOCKDEP_SUPPORT
46 config STACKTRACE_SUPPORT
49 config HAVE_LATENCYTOP_SUPPORT
52 config SEMAPHORE_SLEEPERS
67 config GENERIC_ISA_DMA
77 config GENERIC_HWEIGHT
83 config ARCH_MAY_HAVE_PC_FDC
89 config RWSEM_GENERIC_SPINLOCK
92 config RWSEM_XCHGADD_ALGORITHM
95 config ARCH_HAS_ILOG2_U32
98 config ARCH_HAS_ILOG2_U64
101 config GENERIC_CALIBRATE_DELAY
104 config GENERIC_TIME_VSYSCALL
108 config ARCH_HAS_CPU_RELAX
111 config HAVE_SETUP_PER_CPU_AREA
116 config ARCH_HIBERNATION_POSSIBLE
118 depends on !SMP || !X86_VOYAGER
120 config ARCH_SUSPEND_POSSIBLE
122 depends on !X86_VOYAGER
128 config ARCH_POPULATES_NODE_MAP
135 # Use the generic interrupt handling code in kernel/irq/:
136 config GENERIC_HARDIRQS
140 config GENERIC_IRQ_PROBE
144 config GENERIC_PENDING_IRQ
146 depends on GENERIC_HARDIRQS && SMP
151 depends on SMP && ((X86_32 && !X86_VOYAGER) || X86_64)
156 depends on X86_32 && SMP
160 depends on X86_64 && SMP
165 depends on (X86_32 && !(X86_VISWS || X86_VOYAGER)) || (X86_64 && !MK8)
168 config X86_BIOS_REBOOT
170 depends on X86_32 && !(X86_VISWS || X86_VOYAGER)
173 config X86_TRAMPOLINE
175 depends on X86_SMP || (X86_VOYAGER && SMP)
180 source "init/Kconfig"
182 menu "Processor type and features"
184 source "kernel/time/Kconfig"
187 bool "Symmetric multi-processing support"
189 This enables support for systems with more than one CPU. If you have
190 a system with only one CPU, like most personal computers, say N. If
191 you have a system with more than one CPU, say Y.
193 If you say N here, the kernel will run on single and multiprocessor
194 machines, but will use only one CPU of a multiprocessor machine. If
195 you say Y here, the kernel will run on many, but not all,
196 singleprocessor machines. On a singleprocessor machine, the kernel
197 will run faster if you say N here.
199 Note that if you say Y here and choose architecture "586" or
200 "Pentium" under "Processor family", the kernel will not work on 486
201 architectures. Similarly, multiprocessor kernels for the "PPro"
202 architecture may not work on all Pentium based boards.
204 People using multiprocessor machines who say Y here should also say
205 Y to "Enhanced Real Time Clock Support", below. The "Advanced Power
206 Management" code will be disabled if you say Y here.
208 See also <file:Documentation/i386/IO-APIC.txt>,
209 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
210 <http://www.tldp.org/docs.html#howto>.
212 If you don't know what to do here, say N.
215 prompt "Subarchitecture Type"
221 Choose this option if your computer is a standard PC or compatible.
227 Select this for an AMD Elan processor.
229 Do not use this option for K6/Athlon/Opteron processors!
231 If unsure, choose "PC-compatible" instead.
236 select SMP if !BROKEN
238 Voyager is an MCA-based 32-way capable SMP architecture proprietary
239 to NCR Corp. Machine classes 345x/35xx/4100/51xx are Voyager-based.
243 If you do not specifically know you have a Voyager based machine,
244 say N here, otherwise the kernel you build will not be bootable.
247 bool "NUMAQ (IBM/Sequent)"
252 This option is used for getting Linux to run on a (IBM/Sequent) NUMA
253 multiquad box. This changes the way that processors are bootstrapped,
254 and uses Clustered Logical APIC addressing mode instead of Flat Logical.
255 You will need a new lynxer.elf file to flash your firmware with - send
256 email to <Martin.Bligh@us.ibm.com>.
259 bool "Summit/EXA (IBM x440)"
260 depends on X86_32 && SMP
262 This option is needed for IBM systems that use the Summit/EXA chipset.
263 In particular, it is needed for the x440.
265 If you don't have one of these computers, you should say N here.
266 If you want to build a NUMA kernel, you must select ACPI.
269 bool "Support for other sub-arch SMP systems with more than 8 CPUs"
270 depends on X86_32 && SMP
272 This option is needed for the systems that have more than 8 CPUs
273 and if the system is not of any sub-arch type above.
275 If you don't have such a system, you should say N here.
278 bool "SGI 320/540 (Visual Workstation)"
281 The SGI Visual Workstation series is an IA32-based workstation
282 based on SGI systems chips with some legacy PC hardware attached.
284 Say Y here to create a kernel to run on the SGI 320 or 540.
286 A kernel compiled for the Visual Workstation will not run on PCs
287 and vice versa. See <file:Documentation/sgi-visws.txt> for details.
289 config X86_GENERICARCH
290 bool "Generic architecture (Summit, bigsmp, ES7000, default)"
293 This option compiles in the Summit, bigsmp, ES7000, default subarchitectures.
294 It is intended for a generic binary kernel.
295 If you want a NUMA kernel, select ACPI. We need SRAT for NUMA.
298 bool "Support for Unisys ES7000 IA32 series"
299 depends on X86_32 && SMP
301 Support for Unisys ES7000 systems. Say 'Y' here if this kernel is
302 supposed to run on an IA32-based Unisys ES7000 system.
303 Only choose this option if you have such a system, otherwise you
307 bool "RDC R-321x SoC"
310 select X86_REBOOTFIXUPS
315 This option is needed for RDC R-321x system-on-chip, also known
317 If you don't have one of these chips, you should say N here.
320 bool "Support for ScaleMP vSMP"
321 depends on X86_64 && PCI
323 Support for ScaleMP vSMP systems. Say 'Y' here if this kernel is
324 supposed to run on these EM64T-based machines. Only choose this option
325 if you have one of these machines.
329 config SCHED_NO_NO_OMIT_FRAME_POINTER
331 prompt "Single-depth WCHAN output"
334 Calculate simpler /proc/<PID>/wchan values. If this option
335 is disabled then wchan values will recurse back to the
336 caller function. This provides more accurate wchan values,
337 at the expense of slightly more scheduling overhead.
339 If in doubt, say "Y".
341 menuconfig PARAVIRT_GUEST
342 bool "Paravirtualized guest support"
344 Say Y here to get to see options related to running Linux under
345 various hypervisors. This option alone does not add any kernel code.
347 If you say N, all options in this submenu will be skipped and disabled.
351 source "arch/x86/xen/Kconfig"
354 bool "VMI Guest support"
357 depends on !(X86_VISWS || X86_VOYAGER)
359 VMI provides a paravirtualized interface to the VMware ESX server
360 (it could be used by other hypervisors in theory too, but is not
361 at the moment), by linking the kernel to a GPL-ed ROM module
362 provided by the hypervisor.
364 source "arch/x86/lguest/Kconfig"
367 bool "Enable paravirtualization code"
368 depends on !(X86_VISWS || X86_VOYAGER)
370 This changes the kernel so it can modify itself when it is run
371 under a hypervisor, potentially improving performance significantly
372 over full virtualization. However, when run without a hypervisor
373 the kernel is theoretically slower and slightly larger.
379 depends on X86_32 && ACPI && NUMA && (X86_SUMMIT || X86_GENERICARCH)
382 config HAVE_ARCH_PARSE_SRAT
386 config X86_SUMMIT_NUMA
388 depends on X86_32 && NUMA && (X86_SUMMIT || X86_GENERICARCH)
390 config X86_CYCLONE_TIMER
392 depends on X86_32 && X86_SUMMIT || X86_GENERICARCH
394 config ES7000_CLUSTERED_APIC
396 depends on SMP && X86_ES7000 && MPENTIUMIII
398 source "arch/x86/Kconfig.cpu"
402 prompt "HPET Timer Support" if X86_32
404 Use the IA-PC HPET (High Precision Event Timer) to manage
405 time in preference to the PIT and RTC, if a HPET is
407 HPET is the next generation timer replacing legacy 8254s.
408 The HPET provides a stable time base on SMP
409 systems, unlike the TSC, but it is more expensive to access,
410 as it is off-chip. You can find the HPET spec at
411 <http://www.intel.com/hardwaredesign/hpetspec.htm>.
413 You can safely choose Y here. However, HPET will only be
414 activated if the platform and the BIOS support this feature.
415 Otherwise the 8254 will be used for timing services.
417 Choose N to continue using the legacy 8254 timer.
419 config HPET_EMULATE_RTC
421 depends on HPET_TIMER && (RTC=y || RTC=m || RTC_DRV_CMOS=m || RTC_DRV_CMOS=y)
423 # Mark as embedded because too many people got it wrong.
424 # The code disables itself when not needed.
426 bool "GART IOMMU support" if EMBEDDED
430 depends on X86_64 && PCI
432 Support for full DMA access of devices with 32bit memory access only
433 on systems with more than 3GB. This is usually needed for USB,
434 sound, many IDE/SATA chipsets and some other devices.
435 Provides a driver for the AMD Athlon64/Opteron/Turion/Sempron GART
436 based hardware IOMMU and a software bounce buffer based IOMMU used
437 on Intel systems and as fallback.
438 The code is only active when needed (enough memory and limited
439 device) unless CONFIG_IOMMU_DEBUG or iommu=force is specified
443 bool "IBM Calgary IOMMU support"
445 depends on X86_64 && PCI && EXPERIMENTAL
447 Support for hardware IOMMUs in IBM's xSeries x366 and x460
448 systems. Needed to run systems with more than 3GB of memory
449 properly with 32-bit PCI devices that do not support DAC
450 (Double Address Cycle). Calgary also supports bus level
451 isolation, where all DMAs pass through the IOMMU. This
452 prevents them from going anywhere except their intended
453 destination. This catches hard-to-find kernel bugs and
454 mis-behaving drivers and devices that do not use the DMA-API
455 properly to set up their DMA buffers. The IOMMU can be
456 turned off at boot time with the iommu=off parameter.
457 Normally the kernel will make the right choice by itself.
460 config CALGARY_IOMMU_ENABLED_BY_DEFAULT
462 prompt "Should Calgary be enabled by default?"
463 depends on CALGARY_IOMMU
465 Should Calgary be enabled by default? if you choose 'y', Calgary
466 will be used (if it exists). If you choose 'n', Calgary will not be
467 used even if it exists. If you choose 'n' and would like to use
468 Calgary anyway, pass 'iommu=calgary' on the kernel command line.
472 def_bool (CALGARY_IOMMU || GART_IOMMU)
474 # need this always selected by IOMMU for the VIA workaround
478 Support for software bounce buffers used on x86-64 systems
479 which don't have a hardware IOMMU (e.g. the current generation
480 of Intel's x86-64 CPUs). Using this PCI devices which can only
481 access 32-bits of memory can be used on systems with more than
482 3 GB of memory. If unsure, say Y.
486 int "Maximum number of CPUs (2-255)"
489 default "32" if X86_NUMAQ || X86_SUMMIT || X86_BIGSMP || X86_ES7000
492 This allows you to specify the maximum number of CPUs which this
493 kernel will support. The maximum supported value is 255 and the
494 minimum value which makes sense is 2.
496 This is purely to save memory - each supported CPU adds
497 approximately eight kilobytes to the kernel image.
500 bool "SMT (Hyperthreading) scheduler support"
501 depends on (X86_64 && SMP) || (X86_32 && X86_HT)
503 SMT scheduler support improves the CPU scheduler's decision making
504 when dealing with Intel Pentium 4 chips with HyperThreading at a
505 cost of slightly increased overhead in some places. If unsure say
510 prompt "Multi-core scheduler support"
511 depends on (X86_64 && SMP) || (X86_32 && X86_HT)
513 Multi-core scheduler support improves the CPU scheduler's decision
514 making when dealing with multi-core CPU chips at a cost of slightly
515 increased overhead in some places. If unsure say N here.
517 source "kernel/Kconfig.preempt"
520 bool "Local APIC support on uniprocessors"
521 depends on X86_32 && !SMP && !(X86_VISWS || X86_VOYAGER || X86_GENERICARCH)
523 A local APIC (Advanced Programmable Interrupt Controller) is an
524 integrated interrupt controller in the CPU. If you have a single-CPU
525 system which has a processor with a local APIC, you can say Y here to
526 enable and use it. If you say Y here even though your machine doesn't
527 have a local APIC, then the kernel will still run with no slowdown at
528 all. The local APIC supports CPU-generated self-interrupts (timer,
529 performance counters), and the NMI watchdog which detects hard
533 bool "IO-APIC support on uniprocessors"
534 depends on X86_UP_APIC
536 An IO-APIC (I/O Advanced Programmable Interrupt Controller) is an
537 SMP-capable replacement for PC-style interrupt controllers. Most
538 SMP systems and many recent uniprocessor systems have one.
540 If you have a single-CPU system with an IO-APIC, you can say Y here
541 to use it. If you say Y here even though your machine doesn't have
542 an IO-APIC, then the kernel will still run with no slowdown at all.
544 config X86_LOCAL_APIC
546 depends on X86_64 || (X86_32 && (X86_UP_APIC || ((X86_VISWS || SMP) && !X86_VOYAGER) || X86_GENERICARCH))
550 depends on X86_64 || (X86_32 && (X86_UP_IOAPIC || (SMP && !(X86_VISWS || X86_VOYAGER)) || X86_GENERICARCH))
552 config X86_VISWS_APIC
554 depends on X86_32 && X86_VISWS
557 bool "Machine Check Exception"
558 depends on !X86_VOYAGER
560 Machine Check Exception support allows the processor to notify the
561 kernel if it detects a problem (e.g. overheating, component failure).
562 The action the kernel takes depends on the severity of the problem,
563 ranging from a warning message on the console, to halting the machine.
564 Your processor must be a Pentium or newer to support this - check the
565 flags in /proc/cpuinfo for mce. Note that some older Pentium systems
566 have a design flaw which leads to false MCE events - hence MCE is
567 disabled on all P5 processors, unless explicitly enabled with "mce"
568 as a boot argument. Similarly, if MCE is built in and creates a
569 problem on some new non-standard machine, you can boot with "nomce"
570 to disable it. MCE support simply ignores non-MCE processors like
571 the 386 and 486, so nearly everyone can say Y here.
575 prompt "Intel MCE features"
576 depends on X86_64 && X86_MCE && X86_LOCAL_APIC
578 Additional support for intel specific MCE features such as
583 prompt "AMD MCE features"
584 depends on X86_64 && X86_MCE && X86_LOCAL_APIC
586 Additional support for AMD specific MCE features such as
587 the DRAM Error Threshold.
589 config X86_MCE_NONFATAL
590 tristate "Check for non-fatal errors on AMD Athlon/Duron / Intel Pentium 4"
591 depends on X86_32 && X86_MCE
593 Enabling this feature starts a timer that triggers every 5 seconds which
594 will look at the machine check registers to see if anything happened.
595 Non-fatal problems automatically get corrected (but still logged).
596 Disable this if you don't want to see these messages.
597 Seeing the messages this option prints out may be indicative of dying
598 or out-of-spec (ie, overclocked) hardware.
599 This option only does something on certain CPUs.
600 (AMD Athlon/Duron and Intel Pentium 4)
602 config X86_MCE_P4THERMAL
603 bool "check for P4 thermal throttling interrupt."
604 depends on X86_32 && X86_MCE && (X86_UP_APIC || SMP) && !X86_VISWS
606 Enabling this feature will cause a message to be printed when the P4
607 enters thermal throttling.
610 bool "Enable VM86 support" if EMBEDDED
614 This option is required by programs like DOSEMU to run 16-bit legacy
615 code on X86 processors. It also may be needed by software like
616 XFree86 to initialize some video cards via BIOS. Disabling this
617 option saves about 6k.
620 tristate "Toshiba Laptop support"
623 This adds a driver to safely access the System Management Mode of
624 the CPU on Toshiba portables with a genuine Toshiba BIOS. It does
625 not work on models with a Phoenix BIOS. The System Management Mode
626 is used to set the BIOS and power saving options on Toshiba portables.
628 For information on utilities to make use of this driver see the
629 Toshiba Linux utilities web site at:
630 <http://www.buzzard.org.uk/toshiba/>.
632 Say Y if you intend to run this kernel on a Toshiba portable.
636 tristate "Dell laptop support"
639 This adds a driver to safely access the System Management Mode
640 of the CPU on the Dell Inspiron 8000. The System Management Mode
641 is used to read cpu temperature and cooling fan status and to
642 control the fans on the I8K portables.
644 This driver has been tested only on the Inspiron 8000 but it may
645 also work with other Dell laptops. You can force loading on other
646 models by passing the parameter `force=1' to the module. Use at
649 For information on utilities to make use of this driver see the
650 I8K Linux utilities web site at:
651 <http://people.debian.org/~dz/i8k/>
653 Say Y if you intend to run this kernel on a Dell Inspiron 8000.
656 config X86_REBOOTFIXUPS
658 prompt "Enable X86 board specific fixups for reboot"
659 depends on X86_32 && X86
661 This enables chipset and/or board specific fixups to be done
662 in order to get reboot to work correctly. This is only needed on
663 some combinations of hardware and BIOS. The symptom, for which
664 this config is intended, is when reboot ends with a stalled/hung
667 Currently, the only fixup is for the Geode machines using
668 CS5530A and CS5536 chipsets and the RDC R-321x SoC.
670 Say Y if you want to enable the fixup. Currently, it's safe to
671 enable this option even if you don't need it.
675 tristate "/dev/cpu/microcode - Intel IA32 CPU microcode support"
678 If you say Y here, you will be able to update the microcode on
679 Intel processors in the IA32 family, e.g. Pentium Pro, Pentium II,
680 Pentium III, Pentium 4, Xeon etc. You will obviously need the
681 actual microcode binary data itself which is not shipped with the
684 For latest news and information on obtaining all the required
685 ingredients for this driver, check:
686 <http://www.urbanmyth.org/microcode/>.
688 To compile this driver as a module, choose M here: the
689 module will be called microcode.
691 config MICROCODE_OLD_INTERFACE
696 tristate "/dev/cpu/*/msr - Model-specific register support"
698 This device gives privileged processes access to the x86
699 Model-Specific Registers (MSRs). It is a character device with
700 major 202 and minors 0 to 31 for /dev/cpu/0/msr to /dev/cpu/31/msr.
701 MSR accesses are directed to a specific CPU on multi-processor
705 tristate "/dev/cpu/*/cpuid - CPU information support"
707 This device gives processes access to the x86 CPUID instruction to
708 be executed on a specific processor. It is a character device
709 with major 203 and minors 0 to 31 for /dev/cpu/0/cpuid to
713 prompt "High Memory Support"
714 default HIGHMEM4G if !X86_NUMAQ
715 default HIGHMEM64G if X86_NUMAQ
720 depends on !X86_NUMAQ
722 Linux can use up to 64 Gigabytes of physical memory on x86 systems.
723 However, the address space of 32-bit x86 processors is only 4
724 Gigabytes large. That means that, if you have a large amount of
725 physical memory, not all of it can be "permanently mapped" by the
726 kernel. The physical memory that's not permanently mapped is called
729 If you are compiling a kernel which will never run on a machine with
730 more than 1 Gigabyte total physical RAM, answer "off" here (default
731 choice and suitable for most users). This will result in a "3GB/1GB"
732 split: 3GB are mapped so that each process sees a 3GB virtual memory
733 space and the remaining part of the 4GB virtual memory space is used
734 by the kernel to permanently map as much physical memory as
737 If the machine has between 1 and 4 Gigabytes physical RAM, then
740 If more than 4 Gigabytes is used then answer "64GB" here. This
741 selection turns Intel PAE (Physical Address Extension) mode on.
742 PAE implements 3-level paging on IA32 processors. PAE is fully
743 supported by Linux, PAE mode is implemented on all recent Intel
744 processors (Pentium Pro and better). NOTE: If you say "64GB" here,
745 then the kernel will not boot on CPUs that don't support PAE!
747 The actual amount of total physical memory will either be
748 auto detected or can be forced by using a kernel command line option
749 such as "mem=256M". (Try "man bootparam" or see the documentation of
750 your boot loader (lilo or loadlin) about how to pass options to the
751 kernel at boot time.)
753 If unsure, say "off".
757 depends on !X86_NUMAQ
759 Select this if you have a 32-bit processor and between 1 and 4
760 gigabytes of physical RAM.
764 depends on !M386 && !M486
767 Select this if you have a 32-bit processor and more than 4
768 gigabytes of physical RAM.
773 depends on EXPERIMENTAL
774 prompt "Memory split" if EMBEDDED
778 Select the desired split between kernel and user memory.
780 If the address range available to the kernel is less than the
781 physical memory installed, the remaining memory will be available
782 as "high memory". Accessing high memory is a little more costly
783 than low memory, as it needs to be mapped into the kernel first.
784 Note that increasing the kernel address space limits the range
785 available to user programs, making the address space there
786 tighter. Selecting anything other than the default 3G/1G split
787 will also likely make your kernel incompatible with binary-only
790 If you are not absolutely sure what you are doing, leave this
794 bool "3G/1G user/kernel split"
795 config VMSPLIT_3G_OPT
797 bool "3G/1G user/kernel split (for full 1G low memory)"
799 bool "2G/2G user/kernel split"
800 config VMSPLIT_2G_OPT
802 bool "2G/2G user/kernel split (for full 2G low memory)"
804 bool "1G/3G user/kernel split"
809 default 0xB0000000 if VMSPLIT_3G_OPT
810 default 0x80000000 if VMSPLIT_2G
811 default 0x78000000 if VMSPLIT_2G_OPT
812 default 0x40000000 if VMSPLIT_1G
818 depends on X86_32 && (HIGHMEM64G || HIGHMEM4G)
822 prompt "PAE (Physical Address Extension) Support"
823 depends on X86_32 && !HIGHMEM4G
824 select RESOURCES_64BIT
826 PAE is required for NX support, and furthermore enables
827 larger swapspace support for non-overcommit purposes. It
828 has the cost of more pagetable lookup overhead, and also
829 consumes more pagetable space per process.
831 # Common NUMA Features
833 bool "Numa Memory Allocation and Scheduler Support (EXPERIMENTAL)"
835 depends on X86_64 || (X86_32 && HIGHMEM64G && (X86_NUMAQ || (X86_SUMMIT || X86_GENERICARCH) && ACPI) && EXPERIMENTAL)
837 default y if (X86_NUMAQ || X86_SUMMIT)
839 Enable NUMA (Non Uniform Memory Access) support.
840 The kernel will try to allocate memory used by a CPU on the
841 local memory controller of the CPU and add some more
842 NUMA awareness to the kernel.
844 For i386 this is currently highly experimental and should be only
845 used for kernel development. It might also cause boot failures.
846 For x86_64 this is recommended on all multiprocessor Opteron systems.
847 If the system is EM64T, you should say N unless your system is
850 comment "NUMA (Summit) requires SMP, 64GB highmem support, ACPI"
851 depends on X86_32 && X86_SUMMIT && (!HIGHMEM64G || !ACPI)
855 prompt "Old style AMD Opteron NUMA detection"
856 depends on X86_64 && NUMA && PCI
858 Enable K8 NUMA node topology detection. You should say Y here if
859 you have a multi processor AMD K8 system. This uses an old
860 method to read the NUMA configuration directly from the builtin
861 Northbridge of Opteron. It is recommended to use X86_64_ACPI_NUMA
862 instead, which also takes priority if both are compiled in.
864 config X86_64_ACPI_NUMA
866 prompt "ACPI NUMA detection"
867 depends on X86_64 && NUMA && ACPI && PCI
870 Enable ACPI SRAT based node topology detection.
873 bool "NUMA emulation"
874 depends on X86_64 && NUMA
876 Enable NUMA emulation. A flat machine will be split
877 into virtual nodes when booted with "numa=fake=N", where N is the
878 number of nodes. This is only useful for debugging.
883 default "6" if X86_64
884 default "4" if X86_NUMAQ
886 depends on NEED_MULTIPLE_NODES
888 config HAVE_ARCH_BOOTMEM_NODE
890 depends on X86_32 && NUMA
892 config ARCH_HAVE_MEMORY_PRESENT
894 depends on X86_32 && DISCONTIGMEM
896 config NEED_NODE_MEMMAP_SIZE
898 depends on X86_32 && (DISCONTIGMEM || SPARSEMEM)
900 config HAVE_ARCH_ALLOC_REMAP
902 depends on X86_32 && NUMA
904 config ARCH_FLATMEM_ENABLE
906 depends on X86_32 && ARCH_SELECT_MEMORY_MODEL && X86_PC && !NUMA
908 config ARCH_DISCONTIGMEM_ENABLE
910 depends on NUMA && X86_32
912 config ARCH_DISCONTIGMEM_DEFAULT
914 depends on NUMA && X86_32
916 config ARCH_SPARSEMEM_DEFAULT
920 config ARCH_SPARSEMEM_ENABLE
922 depends on X86_64 || NUMA || (EXPERIMENTAL && X86_PC)
923 select SPARSEMEM_STATIC if X86_32
924 select SPARSEMEM_VMEMMAP_ENABLE if X86_64
926 config ARCH_SELECT_MEMORY_MODEL
928 depends on ARCH_SPARSEMEM_ENABLE
930 config ARCH_MEMORY_PROBE
932 depends on MEMORY_HOTPLUG
937 bool "Allocate 3rd-level pagetables from highmem"
938 depends on X86_32 && (HIGHMEM4G || HIGHMEM64G)
940 The VM uses one page table entry for each page of physical memory.
941 For systems with a lot of RAM, this can be wasteful of precious
942 low memory. Setting this option will put user-space page table
943 entries in high memory.
945 config MATH_EMULATION
947 prompt "Math emulation" if X86_32
949 Linux can emulate a math coprocessor (used for floating point
950 operations) if you don't have one. 486DX and Pentium processors have
951 a math coprocessor built in, 486SX and 386 do not, unless you added
952 a 487DX or 387, respectively. (The messages during boot time can
953 give you some hints here ["man dmesg"].) Everyone needs either a
954 coprocessor or this emulation.
956 If you don't have a math coprocessor, you need to say Y here; if you
957 say Y here even though you have a coprocessor, the coprocessor will
958 be used nevertheless. (This behavior can be changed with the kernel
959 command line option "no387", which comes handy if your coprocessor
960 is broken. Try "man bootparam" or see the documentation of your boot
961 loader (lilo or loadlin) about how to pass options to the kernel at
962 boot time.) This means that it is a good idea to say Y here if you
963 intend to use this kernel on different machines.
965 More information about the internals of the Linux math coprocessor
966 emulation can be found in <file:arch/x86/math-emu/README>.
968 If you are not sure, say Y; apart from resulting in a 66 KB bigger
969 kernel, it won't hurt.
972 bool "MTRR (Memory Type Range Register) support"
974 On Intel P6 family processors (Pentium Pro, Pentium II and later)
975 the Memory Type Range Registers (MTRRs) may be used to control
976 processor access to memory ranges. This is most useful if you have
977 a video (VGA) card on a PCI or AGP bus. Enabling write-combining
978 allows bus write transfers to be combined into a larger transfer
979 before bursting over the PCI/AGP bus. This can increase performance
980 of image write operations 2.5 times or more. Saying Y here creates a
981 /proc/mtrr file which may be used to manipulate your processor's
982 MTRRs. Typically the X server should use this.
984 This code has a reasonably generic interface so that similar
985 control registers on other processors can be easily supported
988 The Cyrix 6x86, 6x86MX and M II processors have Address Range
989 Registers (ARRs) which provide a similar functionality to MTRRs. For
990 these, the ARRs are used to emulate the MTRRs.
991 The AMD K6-2 (stepping 8 and above) and K6-3 processors have two
992 MTRRs. The Centaur C6 (WinChip) has 8 MCRs, allowing
993 write-combining. All of these processors are supported by this code
994 and it makes sense to say Y here if you have one of them.
996 Saying Y here also fixes a problem with buggy SMP BIOSes which only
997 set the MTRRs for the boot CPU and not for the secondary CPUs. This
998 can lead to all sorts of problems, so it's good to say Y here.
1000 You can safely say Y even if your machine doesn't have MTRRs, you'll
1001 just add about 9 KB to your kernel.
1003 See <file:Documentation/mtrr.txt> for more information.
1007 prompt "EFI runtime service support"
1010 This enables the kernel to use EFI runtime services that are
1011 available (such as the EFI variable services).
1013 This option is only useful on systems that have EFI firmware.
1014 In addition, you should use the latest ELILO loader available
1015 at <http://elilo.sourceforge.net> in order to take advantage
1016 of EFI runtime services. However, even with this option, the
1017 resultant kernel should continue to boot on existing non-EFI
1022 prompt "Enable kernel irq balancing"
1023 depends on X86_32 && SMP && X86_IO_APIC
1025 The default yes will allow the kernel to do irq load balancing.
1026 Saying no will keep the kernel from doing irq load balancing.
1030 prompt "Enable seccomp to safely compute untrusted bytecode"
1033 This kernel feature is useful for number crunching applications
1034 that may need to compute untrusted bytecode during their
1035 execution. By using pipes or other transports made available to
1036 the process as file descriptors supporting the read/write
1037 syscalls, it's possible to isolate those applications in
1038 their own address space using seccomp. Once seccomp is
1039 enabled via /proc/<pid>/seccomp, it cannot be disabled
1040 and the task is only allowed to execute a few safe syscalls
1041 defined by each seccomp mode.
1043 If unsure, say Y. Only embedded should say N here.
1045 config CC_STACKPROTECTOR
1046 bool "Enable -fstack-protector buffer overflow detection (EXPERIMENTAL)"
1047 depends on X86_64 && EXPERIMENTAL
1049 This option turns on the -fstack-protector GCC feature. This
1050 feature puts, at the beginning of critical functions, a canary
1051 value on the stack just before the return address, and validates
1052 the value just before actually returning. Stack based buffer
1053 overflows (that need to overwrite this return address) now also
1054 overwrite the canary, which gets detected and the attack is then
1055 neutralized via a kernel panic.
1057 This feature requires gcc version 4.2 or above, or a distribution
1058 gcc with the feature backported. Older versions are automatically
1059 detected and for those versions, this configuration option is ignored.
1061 config CC_STACKPROTECTOR_ALL
1062 bool "Use stack-protector for all functions"
1063 depends on CC_STACKPROTECTOR
1065 Normally, GCC only inserts the canary value protection for
1066 functions that use large-ish on-stack buffers. By enabling
1067 this option, GCC will be asked to do this for ALL functions.
1069 source kernel/Kconfig.hz
1072 bool "kexec system call"
1074 kexec is a system call that implements the ability to shutdown your
1075 current kernel, and to start another kernel. It is like a reboot
1076 but it is independent of the system firmware. And like a reboot
1077 you can start any kernel with it, not just Linux.
1079 The name comes from the similarity to the exec system call.
1081 It is an ongoing process to be certain the hardware in a machine
1082 is properly shutdown, so do not be surprised if this code does not
1083 initially work for you. It may help to enable device hotplugging
1084 support. As of this writing the exact hardware interface is
1085 strongly in flux, so no good recommendation can be made.
1088 bool "kernel crash dumps (EXPERIMENTAL)"
1089 depends on EXPERIMENTAL
1090 depends on X86_64 || (X86_32 && HIGHMEM)
1092 Generate crash dump after being started by kexec.
1093 This should be normally only set in special crash dump kernels
1094 which are loaded in the main kernel with kexec-tools into
1095 a specially reserved region and then later executed after
1096 a crash by kdump/kexec. The crash dump kernel must be compiled
1097 to a memory address not used by the main kernel or BIOS using
1098 PHYSICAL_START, or it must be built as a relocatable image
1099 (CONFIG_RELOCATABLE=y).
1100 For more details see Documentation/kdump/kdump.txt
1102 config PHYSICAL_START
1103 hex "Physical address where the kernel is loaded" if (EMBEDDED || CRASH_DUMP)
1104 default "0x1000000" if X86_NUMAQ
1105 default "0x200000" if X86_64
1108 This gives the physical address where the kernel is loaded.
1110 If kernel is a not relocatable (CONFIG_RELOCATABLE=n) then
1111 bzImage will decompress itself to above physical address and
1112 run from there. Otherwise, bzImage will run from the address where
1113 it has been loaded by the boot loader and will ignore above physical
1116 In normal kdump cases one does not have to set/change this option
1117 as now bzImage can be compiled as a completely relocatable image
1118 (CONFIG_RELOCATABLE=y) and be used to load and run from a different
1119 address. This option is mainly useful for the folks who don't want
1120 to use a bzImage for capturing the crash dump and want to use a
1121 vmlinux instead. vmlinux is not relocatable hence a kernel needs
1122 to be specifically compiled to run from a specific memory area
1123 (normally a reserved region) and this option comes handy.
1125 So if you are using bzImage for capturing the crash dump, leave
1126 the value here unchanged to 0x100000 and set CONFIG_RELOCATABLE=y.
1127 Otherwise if you plan to use vmlinux for capturing the crash dump
1128 change this value to start of the reserved region (Typically 16MB
1129 0x1000000). In other words, it can be set based on the "X" value as
1130 specified in the "crashkernel=YM@XM" command line boot parameter
1131 passed to the panic-ed kernel. Typically this parameter is set as
1132 crashkernel=64M@16M. Please take a look at
1133 Documentation/kdump/kdump.txt for more details about crash dumps.
1135 Usage of bzImage for capturing the crash dump is recommended as
1136 one does not have to build two kernels. Same kernel can be used
1137 as production kernel and capture kernel. Above option should have
1138 gone away after relocatable bzImage support is introduced. But it
1139 is present because there are users out there who continue to use
1140 vmlinux for dump capture. This option should go away down the
1143 Don't change this unless you know what you are doing.
1146 bool "Build a relocatable kernel (EXPERIMENTAL)"
1147 depends on EXPERIMENTAL
1149 This builds a kernel image that retains relocation information
1150 so it can be loaded someplace besides the default 1MB.
1151 The relocations tend to make the kernel binary about 10% larger,
1152 but are discarded at runtime.
1154 One use is for the kexec on panic case where the recovery kernel
1155 must live at a different physical address than the primary
1158 Note: If CONFIG_RELOCATABLE=y, then the kernel runs from the address
1159 it has been loaded at and the compile time physical address
1160 (CONFIG_PHYSICAL_START) is ignored.
1162 config PHYSICAL_ALIGN
1164 prompt "Alignment value to which kernel should be aligned" if X86_32
1165 default "0x100000" if X86_32
1166 default "0x200000" if X86_64
1167 range 0x2000 0x400000
1169 This value puts the alignment restrictions on physical address
1170 where kernel is loaded and run from. Kernel is compiled for an
1171 address which meets above alignment restriction.
1173 If bootloader loads the kernel at a non-aligned address and
1174 CONFIG_RELOCATABLE is set, kernel will move itself to nearest
1175 address aligned to above value and run from there.
1177 If bootloader loads the kernel at a non-aligned address and
1178 CONFIG_RELOCATABLE is not set, kernel will ignore the run time
1179 load address and decompress itself to the address it has been
1180 compiled for and run from there. The address for which kernel is
1181 compiled already meets above alignment restrictions. Hence the
1182 end result is that kernel runs from a physical address meeting
1183 above alignment restrictions.
1185 Don't change this unless you know what you are doing.
1188 bool "Support for suspend on SMP and hot-pluggable CPUs (EXPERIMENTAL)"
1189 depends on SMP && HOTPLUG && EXPERIMENTAL && !X86_VOYAGER
1191 Say Y here to experiment with turning CPUs off and on, and to
1192 enable suspend on SMP systems. CPUs can be controlled through
1193 /sys/devices/system/cpu.
1194 Say N if you want to disable CPU hotplug and don't need to
1199 prompt "Compat VDSO support"
1200 depends on X86_32 || IA32_EMULATION
1202 Map the 32-bit VDSO to the predictable old-style address too.
1204 Say N here if you are running a sufficiently recent glibc
1205 version (2.3.3 or later), to remove the high-mapped
1206 VDSO mapping and to exclusively use the randomized VDSO.
1212 config ARCH_ENABLE_MEMORY_HOTPLUG
1214 depends on X86_64 || (X86_32 && HIGHMEM)
1216 config HAVE_ARCH_EARLY_PFN_TO_NID
1220 menu "Power management options"
1221 depends on !X86_VOYAGER
1223 config ARCH_HIBERNATION_HEADER
1225 depends on X86_64 && HIBERNATION
1227 source "kernel/power/Kconfig"
1229 source "drivers/acpi/Kconfig"
1234 depends on APM || APM_MODULE
1237 tristate "APM (Advanced Power Management) BIOS support"
1238 depends on X86_32 && PM_SLEEP && !X86_VISWS
1240 APM is a BIOS specification for saving power using several different
1241 techniques. This is mostly useful for battery powered laptops with
1242 APM compliant BIOSes. If you say Y here, the system time will be
1243 reset after a RESUME operation, the /proc/apm device will provide
1244 battery status information, and user-space programs will receive
1245 notification of APM "events" (e.g. battery status change).
1247 If you select "Y" here, you can disable actual use of the APM
1248 BIOS by passing the "apm=off" option to the kernel at boot time.
1250 Note that the APM support is almost completely disabled for
1251 machines with more than one CPU.
1253 In order to use APM, you will need supporting software. For location
1254 and more information, read <file:Documentation/pm.txt> and the
1255 Battery Powered Linux mini-HOWTO, available from
1256 <http://www.tldp.org/docs.html#howto>.
1258 This driver does not spin down disk drives (see the hdparm(8)
1259 manpage ("man 8 hdparm") for that), and it doesn't turn off
1260 VESA-compliant "green" monitors.
1262 This driver does not support the TI 4000M TravelMate and the ACER
1263 486/DX4/75 because they don't have compliant BIOSes. Many "green"
1264 desktop machines also don't have compliant BIOSes, and this driver
1265 may cause those machines to panic during the boot phase.
1267 Generally, if you don't have a battery in your machine, there isn't
1268 much point in using this driver and you should say N. If you get
1269 random kernel OOPSes or reboots that don't seem to be related to
1270 anything, try disabling/enabling this option (or disabling/enabling
1273 Some other things you should try when experiencing seemingly random,
1276 1) make sure that you have enough swap space and that it is
1278 2) pass the "no-hlt" option to the kernel
1279 3) switch on floating point emulation in the kernel and pass
1280 the "no387" option to the kernel
1281 4) pass the "floppy=nodma" option to the kernel
1282 5) pass the "mem=4M" option to the kernel (thereby disabling
1283 all but the first 4 MB of RAM)
1284 6) make sure that the CPU is not over clocked.
1285 7) read the sig11 FAQ at <http://www.bitwizard.nl/sig11/>
1286 8) disable the cache from your BIOS settings
1287 9) install a fan for the video card or exchange video RAM
1288 10) install a better fan for the CPU
1289 11) exchange RAM chips
1290 12) exchange the motherboard.
1292 To compile this driver as a module, choose M here: the
1293 module will be called apm.
1297 config APM_IGNORE_USER_SUSPEND
1298 bool "Ignore USER SUSPEND"
1300 This option will ignore USER SUSPEND requests. On machines with a
1301 compliant APM BIOS, you want to say N. However, on the NEC Versa M
1302 series notebooks, it is necessary to say Y because of a BIOS bug.
1304 config APM_DO_ENABLE
1305 bool "Enable PM at boot time"
1307 Enable APM features at boot time. From page 36 of the APM BIOS
1308 specification: "When disabled, the APM BIOS does not automatically
1309 power manage devices, enter the Standby State, enter the Suspend
1310 State, or take power saving steps in response to CPU Idle calls."
1311 This driver will make CPU Idle calls when Linux is idle (unless this
1312 feature is turned off -- see "Do CPU IDLE calls", below). This
1313 should always save battery power, but more complicated APM features
1314 will be dependent on your BIOS implementation. You may need to turn
1315 this option off if your computer hangs at boot time when using APM
1316 support, or if it beeps continuously instead of suspending. Turn
1317 this off if you have a NEC UltraLite Versa 33/C or a Toshiba
1318 T400CDT. This is off by default since most machines do fine without
1322 bool "Make CPU Idle calls when idle"
1324 Enable calls to APM CPU Idle/CPU Busy inside the kernel's idle loop.
1325 On some machines, this can activate improved power savings, such as
1326 a slowed CPU clock rate, when the machine is idle. These idle calls
1327 are made after the idle loop has run for some length of time (e.g.,
1328 333 mS). On some machines, this will cause a hang at boot time or
1329 whenever the CPU becomes idle. (On machines with more than one CPU,
1330 this option does nothing.)
1332 config APM_DISPLAY_BLANK
1333 bool "Enable console blanking using APM"
1335 Enable console blanking using the APM. Some laptops can use this to
1336 turn off the LCD backlight when the screen blanker of the Linux
1337 virtual console blanks the screen. Note that this is only used by
1338 the virtual console screen blanker, and won't turn off the backlight
1339 when using the X Window system. This also doesn't have anything to
1340 do with your VESA-compliant power-saving monitor. Further, this
1341 option doesn't work for all laptops -- it might not turn off your
1342 backlight at all, or it might print a lot of errors to the console,
1343 especially if you are using gpm.
1345 config APM_ALLOW_INTS
1346 bool "Allow interrupts during APM BIOS calls"
1348 Normally we disable external interrupts while we are making calls to
1349 the APM BIOS as a measure to lessen the effects of a badly behaving
1350 BIOS implementation. The BIOS should reenable interrupts if it
1351 needs to. Unfortunately, some BIOSes do not -- especially those in
1352 many of the newer IBM Thinkpads. If you experience hangs when you
1353 suspend, try setting this to Y. Otherwise, say N.
1355 config APM_REAL_MODE_POWER_OFF
1356 bool "Use real mode APM BIOS call to power off"
1358 Use real mode APM BIOS calls to switch off the computer. This is
1359 a work-around for a number of buggy BIOSes. Switch this option on if
1360 your computer crashes instead of powering off properly.
1364 source "arch/x86/kernel/cpu/cpufreq/Kconfig"
1366 source "drivers/cpuidle/Kconfig"
1371 menu "Bus options (PCI etc.)"
1374 bool "PCI support" if !X86_VISWS
1375 depends on !X86_VOYAGER
1377 select ARCH_SUPPORTS_MSI if (X86_LOCAL_APIC && X86_IO_APIC)
1379 Find out whether you have a PCI motherboard. PCI is the name of a
1380 bus system, i.e. the way the CPU talks to the other stuff inside
1381 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
1382 VESA. If you have PCI, say Y, otherwise N.
1385 prompt "PCI access mode"
1386 depends on X86_32 && PCI && !X86_VISWS
1389 On PCI systems, the BIOS can be used to detect the PCI devices and
1390 determine their configuration. However, some old PCI motherboards
1391 have BIOS bugs and may crash if this is done. Also, some embedded
1392 PCI-based systems don't have any BIOS at all. Linux can also try to
1393 detect the PCI hardware directly without using the BIOS.
1395 With this option, you can specify how Linux should detect the
1396 PCI devices. If you choose "BIOS", the BIOS will be used,
1397 if you choose "Direct", the BIOS won't be used, and if you
1398 choose "MMConfig", then PCI Express MMCONFIG will be used.
1399 If you choose "Any", the kernel will try MMCONFIG, then the
1400 direct access method and falls back to the BIOS if that doesn't
1401 work. If unsure, go with the default, which is "Any".
1406 config PCI_GOMMCONFIG
1419 depends on X86_32 && !X86_VISWS && PCI && (PCI_GOBIOS || PCI_GOANY)
1421 # x86-64 doesn't support PCI BIOS access from long mode so always go direct.
1424 depends on PCI && (X86_64 || (PCI_GODIRECT || PCI_GOANY) || X86_VISWS)
1428 depends on X86_32 && PCI && ACPI && (PCI_GOMMCONFIG || PCI_GOANY)
1435 bool "Support mmconfig PCI config space access"
1436 depends on X86_64 && PCI && ACPI
1439 bool "Support for DMA Remapping Devices (EXPERIMENTAL)"
1440 depends on X86_64 && PCI_MSI && ACPI && EXPERIMENTAL
1442 DMA remapping (DMAR) devices support enables independent address
1443 translations for Direct Memory Access (DMA) from devices.
1444 These DMA remapping devices are reported via ACPI tables
1445 and include PCI device scope covered by these DMA
1450 prompt "Support for Graphics workaround"
1453 Current Graphics drivers tend to use physical address
1454 for DMA and avoid using DMA APIs. Setting this config
1455 option permits the IOMMU driver to set a unity map for
1456 all the OS-visible memory. Hence the driver can continue
1457 to use physical addresses for DMA.
1459 config DMAR_FLOPPY_WA
1463 Floppy disk drivers are know to bypass DMA API calls
1464 thereby failing to work when IOMMU is enabled. This
1465 workaround will setup a 1:1 mapping for the first
1466 16M to make floppy (an ISA device) work.
1468 source "drivers/pci/pcie/Kconfig"
1470 source "drivers/pci/Kconfig"
1472 # x86_64 have no ISA slots, but do have ISA-style DMA.
1480 depends on !(X86_VOYAGER || X86_VISWS)
1482 Find out whether you have ISA slots on your motherboard. ISA is the
1483 name of a bus system, i.e. the way the CPU talks to the other stuff
1484 inside your box. Other bus systems are PCI, EISA, MicroChannel
1485 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
1486 newer boards don't support it. If you have ISA, say Y, otherwise N.
1492 The Extended Industry Standard Architecture (EISA) bus was
1493 developed as an open alternative to the IBM MicroChannel bus.
1495 The EISA bus provided some of the features of the IBM MicroChannel
1496 bus while maintaining backward compatibility with cards made for
1497 the older ISA bus. The EISA bus saw limited use between 1988 and
1498 1995 when it was made obsolete by the PCI bus.
1500 Say Y here if you are building a kernel for an EISA-based machine.
1504 source "drivers/eisa/Kconfig"
1507 bool "MCA support" if !(X86_VISWS || X86_VOYAGER)
1508 default y if X86_VOYAGER
1510 MicroChannel Architecture is found in some IBM PS/2 machines and
1511 laptops. It is a bus system similar to PCI or ISA. See
1512 <file:Documentation/mca.txt> (and especially the web page given
1513 there) before attempting to build an MCA bus kernel.
1515 source "drivers/mca/Kconfig"
1518 tristate "NatSemi SCx200 support"
1519 depends on !X86_VOYAGER
1521 This provides basic support for National Semiconductor's
1522 (now AMD's) Geode processors. The driver probes for the
1523 PCI-IDs of several on-chip devices, so its a good dependency
1524 for other scx200_* drivers.
1526 If compiled as a module, the driver is named scx200.
1528 config SCx200HR_TIMER
1529 tristate "NatSemi SCx200 27MHz High-Resolution Timer Support"
1530 depends on SCx200 && GENERIC_TIME
1533 This driver provides a clocksource built upon the on-chip
1534 27MHz high-resolution timer. Its also a workaround for
1535 NSC Geode SC-1100's buggy TSC, which loses time when the
1536 processor goes idle (as is done by the scheduler). The
1537 other workaround is idle=poll boot option.
1539 config GEODE_MFGPT_TIMER
1541 prompt "Geode Multi-Function General Purpose Timer (MFGPT) events"
1542 depends on MGEODE_LX && GENERIC_TIME && GENERIC_CLOCKEVENTS
1544 This driver provides a clock event source based on the MFGPT
1545 timer(s) in the CS5535 and CS5536 companion chip for the geode.
1546 MFGPTs have a better resolution and max interval than the
1547 generic PIT, and are suitable for use as high-res timers.
1553 depends on AGP_AMD64 || (X86_64 && (GART_IOMMU || (PCI && NUMA)))
1555 source "drivers/pcmcia/Kconfig"
1557 source "drivers/pci/hotplug/Kconfig"
1562 menu "Executable file formats / Emulations"
1564 source "fs/Kconfig.binfmt"
1566 config IA32_EMULATION
1567 bool "IA32 Emulation"
1569 select COMPAT_BINFMT_ELF
1571 Include code to run 32-bit programs under a 64-bit kernel. You should
1572 likely turn this on, unless you're 100% sure that you don't have any
1573 32-bit programs left.
1576 tristate "IA32 a.out support"
1577 depends on IA32_EMULATION
1579 Support old a.out binaries in the 32bit emulation.
1583 depends on IA32_EMULATION
1585 config COMPAT_FOR_U64_ALIGNMENT
1589 config SYSVIPC_COMPAT
1591 depends on X86_64 && COMPAT && SYSVIPC
1596 source "net/Kconfig"
1598 source "drivers/Kconfig"
1600 source "drivers/firmware/Kconfig"
1604 source "arch/x86/Kconfig.debug"
1606 source "security/Kconfig"
1608 source "crypto/Kconfig"
1610 source "arch/x86/kvm/Kconfig"
1612 source "lib/Kconfig"
git.openpandora.org / pandora-kernel.git / blob