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
55 config FAST_CMPXCHG_LOCAL
71 config GENERIC_ISA_DMA
81 config GENERIC_HWEIGHT
87 config ARCH_MAY_HAVE_PC_FDC
93 config RWSEM_GENERIC_SPINLOCK
96 config RWSEM_XCHGADD_ALGORITHM
99 config ARCH_HAS_ILOG2_U32
102 config ARCH_HAS_ILOG2_U64
105 config GENERIC_CALIBRATE_DELAY
108 config GENERIC_TIME_VSYSCALL
112 config ARCH_HAS_CPU_RELAX
115 config HAVE_SETUP_PER_CPU_AREA
120 config ARCH_HIBERNATION_POSSIBLE
122 depends on !SMP || !X86_VOYAGER
124 config ARCH_SUSPEND_POSSIBLE
126 depends on !X86_VOYAGER
132 config ARCH_POPULATES_NODE_MAP
139 config ARCH_SUPPORTS_AOUT
142 # Use the generic interrupt handling code in kernel/irq/:
143 config GENERIC_HARDIRQS
147 config GENERIC_IRQ_PROBE
151 config GENERIC_PENDING_IRQ
153 depends on GENERIC_HARDIRQS && SMP
158 depends on SMP && ((X86_32 && !X86_VOYAGER) || X86_64)
163 depends on X86_32 && SMP
167 depends on X86_64 && SMP
172 depends on (X86_32 && !(X86_VISWS || X86_VOYAGER)) || (X86_64 && !MK8)
175 config X86_BIOS_REBOOT
177 depends on X86_32 && !(X86_VISWS || X86_VOYAGER)
180 config X86_TRAMPOLINE
182 depends on X86_SMP || (X86_VOYAGER && SMP)
187 source "init/Kconfig"
189 menu "Processor type and features"
191 source "kernel/time/Kconfig"
194 bool "Symmetric multi-processing support"
196 This enables support for systems with more than one CPU. If you have
197 a system with only one CPU, like most personal computers, say N. If
198 you have a system with more than one CPU, say Y.
200 If you say N here, the kernel will run on single and multiprocessor
201 machines, but will use only one CPU of a multiprocessor machine. If
202 you say Y here, the kernel will run on many, but not all,
203 singleprocessor machines. On a singleprocessor machine, the kernel
204 will run faster if you say N here.
206 Note that if you say Y here and choose architecture "586" or
207 "Pentium" under "Processor family", the kernel will not work on 486
208 architectures. Similarly, multiprocessor kernels for the "PPro"
209 architecture may not work on all Pentium based boards.
211 People using multiprocessor machines who say Y here should also say
212 Y to "Enhanced Real Time Clock Support", below. The "Advanced Power
213 Management" code will be disabled if you say Y here.
215 See also <file:Documentation/i386/IO-APIC.txt>,
216 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
217 <http://www.tldp.org/docs.html#howto>.
219 If you don't know what to do here, say N.
222 prompt "Subarchitecture Type"
228 Choose this option if your computer is a standard PC or compatible.
234 Select this for an AMD Elan processor.
236 Do not use this option for K6/Athlon/Opteron processors!
238 If unsure, choose "PC-compatible" instead.
243 select SMP if !BROKEN
245 Voyager is an MCA-based 32-way capable SMP architecture proprietary
246 to NCR Corp. Machine classes 345x/35xx/4100/51xx are Voyager-based.
250 If you do not specifically know you have a Voyager based machine,
251 say N here, otherwise the kernel you build will not be bootable.
254 bool "NUMAQ (IBM/Sequent)"
259 This option is used for getting Linux to run on a (IBM/Sequent) NUMA
260 multiquad box. This changes the way that processors are bootstrapped,
261 and uses Clustered Logical APIC addressing mode instead of Flat Logical.
262 You will need a new lynxer.elf file to flash your firmware with - send
263 email to <Martin.Bligh@us.ibm.com>.
266 bool "Summit/EXA (IBM x440)"
267 depends on X86_32 && SMP
269 This option is needed for IBM systems that use the Summit/EXA chipset.
270 In particular, it is needed for the x440.
272 If you don't have one of these computers, you should say N here.
273 If you want to build a NUMA kernel, you must select ACPI.
276 bool "Support for other sub-arch SMP systems with more than 8 CPUs"
277 depends on X86_32 && SMP
279 This option is needed for the systems that have more than 8 CPUs
280 and if the system is not of any sub-arch type above.
282 If you don't have such a system, you should say N here.
285 bool "SGI 320/540 (Visual Workstation)"
288 The SGI Visual Workstation series is an IA32-based workstation
289 based on SGI systems chips with some legacy PC hardware attached.
291 Say Y here to create a kernel to run on the SGI 320 or 540.
293 A kernel compiled for the Visual Workstation will not run on PCs
294 and vice versa. See <file:Documentation/sgi-visws.txt> for details.
296 config X86_GENERICARCH
297 bool "Generic architecture (Summit, bigsmp, ES7000, default)"
300 This option compiles in the Summit, bigsmp, ES7000, default subarchitectures.
301 It is intended for a generic binary kernel.
302 If you want a NUMA kernel, select ACPI. We need SRAT for NUMA.
305 bool "Support for Unisys ES7000 IA32 series"
306 depends on X86_32 && SMP
308 Support for Unisys ES7000 systems. Say 'Y' here if this kernel is
309 supposed to run on an IA32-based Unisys ES7000 system.
310 Only choose this option if you have such a system, otherwise you
314 bool "RDC R-321x SoC"
317 select X86_REBOOTFIXUPS
322 This option is needed for RDC R-321x system-on-chip, also known
324 If you don't have one of these chips, you should say N here.
327 bool "Support for ScaleMP vSMP"
328 depends on X86_64 && PCI
330 Support for ScaleMP vSMP systems. Say 'Y' here if this kernel is
331 supposed to run on these EM64T-based machines. Only choose this option
332 if you have one of these machines.
336 config SCHED_NO_NO_OMIT_FRAME_POINTER
338 prompt "Single-depth WCHAN output"
341 Calculate simpler /proc/<PID>/wchan values. If this option
342 is disabled then wchan values will recurse back to the
343 caller function. This provides more accurate wchan values,
344 at the expense of slightly more scheduling overhead.
346 If in doubt, say "Y".
348 menuconfig PARAVIRT_GUEST
349 bool "Paravirtualized guest support"
351 Say Y here to get to see options related to running Linux under
352 various hypervisors. This option alone does not add any kernel code.
354 If you say N, all options in this submenu will be skipped and disabled.
358 source "arch/x86/xen/Kconfig"
361 bool "VMI Guest support"
364 depends on !(X86_VISWS || X86_VOYAGER)
366 VMI provides a paravirtualized interface to the VMware ESX server
367 (it could be used by other hypervisors in theory too, but is not
368 at the moment), by linking the kernel to a GPL-ed ROM module
369 provided by the hypervisor.
371 source "arch/x86/lguest/Kconfig"
374 bool "Enable paravirtualization code"
375 depends on !(X86_VISWS || X86_VOYAGER)
377 This changes the kernel so it can modify itself when it is run
378 under a hypervisor, potentially improving performance significantly
379 over full virtualization. However, when run without a hypervisor
380 the kernel is theoretically slower and slightly larger.
386 depends on X86_32 && ACPI && NUMA && (X86_SUMMIT || X86_GENERICARCH)
389 config HAVE_ARCH_PARSE_SRAT
393 config X86_SUMMIT_NUMA
395 depends on X86_32 && NUMA && (X86_SUMMIT || X86_GENERICARCH)
397 config X86_CYCLONE_TIMER
399 depends on X86_32 && X86_SUMMIT || X86_GENERICARCH
401 config ES7000_CLUSTERED_APIC
403 depends on SMP && X86_ES7000 && MPENTIUMIII
405 source "arch/x86/Kconfig.cpu"
409 prompt "HPET Timer Support" if X86_32
411 Use the IA-PC HPET (High Precision Event Timer) to manage
412 time in preference to the PIT and RTC, if a HPET is
414 HPET is the next generation timer replacing legacy 8254s.
415 The HPET provides a stable time base on SMP
416 systems, unlike the TSC, but it is more expensive to access,
417 as it is off-chip. You can find the HPET spec at
418 <http://www.intel.com/hardwaredesign/hpetspec.htm>.
420 You can safely choose Y here. However, HPET will only be
421 activated if the platform and the BIOS support this feature.
422 Otherwise the 8254 will be used for timing services.
424 Choose N to continue using the legacy 8254 timer.
426 config HPET_EMULATE_RTC
428 depends on HPET_TIMER && (RTC=y || RTC=m || RTC_DRV_CMOS=m || RTC_DRV_CMOS=y)
430 # Mark as embedded because too many people got it wrong.
431 # The code disables itself when not needed.
433 bool "GART IOMMU support" if EMBEDDED
437 depends on X86_64 && PCI
439 Support for full DMA access of devices with 32bit memory access only
440 on systems with more than 3GB. This is usually needed for USB,
441 sound, many IDE/SATA chipsets and some other devices.
442 Provides a driver for the AMD Athlon64/Opteron/Turion/Sempron GART
443 based hardware IOMMU and a software bounce buffer based IOMMU used
444 on Intel systems and as fallback.
445 The code is only active when needed (enough memory and limited
446 device) unless CONFIG_IOMMU_DEBUG or iommu=force is specified
450 bool "IBM Calgary IOMMU support"
452 depends on X86_64 && PCI && EXPERIMENTAL
454 Support for hardware IOMMUs in IBM's xSeries x366 and x460
455 systems. Needed to run systems with more than 3GB of memory
456 properly with 32-bit PCI devices that do not support DAC
457 (Double Address Cycle). Calgary also supports bus level
458 isolation, where all DMAs pass through the IOMMU. This
459 prevents them from going anywhere except their intended
460 destination. This catches hard-to-find kernel bugs and
461 mis-behaving drivers and devices that do not use the DMA-API
462 properly to set up their DMA buffers. The IOMMU can be
463 turned off at boot time with the iommu=off parameter.
464 Normally the kernel will make the right choice by itself.
467 config CALGARY_IOMMU_ENABLED_BY_DEFAULT
469 prompt "Should Calgary be enabled by default?"
470 depends on CALGARY_IOMMU
472 Should Calgary be enabled by default? if you choose 'y', Calgary
473 will be used (if it exists). If you choose 'n', Calgary will not be
474 used even if it exists. If you choose 'n' and would like to use
475 Calgary anyway, pass 'iommu=calgary' on the kernel command line.
479 def_bool (CALGARY_IOMMU || GART_IOMMU)
481 # need this always selected by IOMMU for the VIA workaround
485 Support for software bounce buffers used on x86-64 systems
486 which don't have a hardware IOMMU (e.g. the current generation
487 of Intel's x86-64 CPUs). Using this PCI devices which can only
488 access 32-bits of memory can be used on systems with more than
489 3 GB of memory. If unsure, say Y.
493 int "Maximum number of CPUs (2-255)"
496 default "32" if X86_NUMAQ || X86_SUMMIT || X86_BIGSMP || X86_ES7000
499 This allows you to specify the maximum number of CPUs which this
500 kernel will support. The maximum supported value is 255 and the
501 minimum value which makes sense is 2.
503 This is purely to save memory - each supported CPU adds
504 approximately eight kilobytes to the kernel image.
507 bool "SMT (Hyperthreading) scheduler support"
508 depends on (X86_64 && SMP) || (X86_32 && X86_HT)
510 SMT scheduler support improves the CPU scheduler's decision making
511 when dealing with Intel Pentium 4 chips with HyperThreading at a
512 cost of slightly increased overhead in some places. If unsure say
517 prompt "Multi-core scheduler support"
518 depends on (X86_64 && SMP) || (X86_32 && X86_HT)
520 Multi-core scheduler support improves the CPU scheduler's decision
521 making when dealing with multi-core CPU chips at a cost of slightly
522 increased overhead in some places. If unsure say N here.
524 source "kernel/Kconfig.preempt"
527 bool "Local APIC support on uniprocessors"
528 depends on X86_32 && !SMP && !(X86_VISWS || X86_VOYAGER || X86_GENERICARCH)
530 A local APIC (Advanced Programmable Interrupt Controller) is an
531 integrated interrupt controller in the CPU. If you have a single-CPU
532 system which has a processor with a local APIC, you can say Y here to
533 enable and use it. If you say Y here even though your machine doesn't
534 have a local APIC, then the kernel will still run with no slowdown at
535 all. The local APIC supports CPU-generated self-interrupts (timer,
536 performance counters), and the NMI watchdog which detects hard
540 bool "IO-APIC support on uniprocessors"
541 depends on X86_UP_APIC
543 An IO-APIC (I/O Advanced Programmable Interrupt Controller) is an
544 SMP-capable replacement for PC-style interrupt controllers. Most
545 SMP systems and many recent uniprocessor systems have one.
547 If you have a single-CPU system with an IO-APIC, you can say Y here
548 to use it. If you say Y here even though your machine doesn't have
549 an IO-APIC, then the kernel will still run with no slowdown at all.
551 config X86_LOCAL_APIC
553 depends on X86_64 || (X86_32 && (X86_UP_APIC || ((X86_VISWS || SMP) && !X86_VOYAGER) || X86_GENERICARCH))
557 depends on X86_64 || (X86_32 && (X86_UP_IOAPIC || (SMP && !(X86_VISWS || X86_VOYAGER)) || X86_GENERICARCH))
559 config X86_VISWS_APIC
561 depends on X86_32 && X86_VISWS
564 bool "Machine Check Exception"
565 depends on !X86_VOYAGER
567 Machine Check Exception support allows the processor to notify the
568 kernel if it detects a problem (e.g. overheating, component failure).
569 The action the kernel takes depends on the severity of the problem,
570 ranging from a warning message on the console, to halting the machine.
571 Your processor must be a Pentium or newer to support this - check the
572 flags in /proc/cpuinfo for mce. Note that some older Pentium systems
573 have a design flaw which leads to false MCE events - hence MCE is
574 disabled on all P5 processors, unless explicitly enabled with "mce"
575 as a boot argument. Similarly, if MCE is built in and creates a
576 problem on some new non-standard machine, you can boot with "nomce"
577 to disable it. MCE support simply ignores non-MCE processors like
578 the 386 and 486, so nearly everyone can say Y here.
582 prompt "Intel MCE features"
583 depends on X86_64 && X86_MCE && X86_LOCAL_APIC
585 Additional support for intel specific MCE features such as
590 prompt "AMD MCE features"
591 depends on X86_64 && X86_MCE && X86_LOCAL_APIC
593 Additional support for AMD specific MCE features such as
594 the DRAM Error Threshold.
596 config X86_MCE_NONFATAL
597 tristate "Check for non-fatal errors on AMD Athlon/Duron / Intel Pentium 4"
598 depends on X86_32 && X86_MCE
600 Enabling this feature starts a timer that triggers every 5 seconds which
601 will look at the machine check registers to see if anything happened.
602 Non-fatal problems automatically get corrected (but still logged).
603 Disable this if you don't want to see these messages.
604 Seeing the messages this option prints out may be indicative of dying
605 or out-of-spec (ie, overclocked) hardware.
606 This option only does something on certain CPUs.
607 (AMD Athlon/Duron and Intel Pentium 4)
609 config X86_MCE_P4THERMAL
610 bool "check for P4 thermal throttling interrupt."
611 depends on X86_32 && X86_MCE && (X86_UP_APIC || SMP) && !X86_VISWS
613 Enabling this feature will cause a message to be printed when the P4
614 enters thermal throttling.
617 bool "Enable VM86 support" if EMBEDDED
621 This option is required by programs like DOSEMU to run 16-bit legacy
622 code on X86 processors. It also may be needed by software like
623 XFree86 to initialize some video cards via BIOS. Disabling this
624 option saves about 6k.
627 tristate "Toshiba Laptop support"
630 This adds a driver to safely access the System Management Mode of
631 the CPU on Toshiba portables with a genuine Toshiba BIOS. It does
632 not work on models with a Phoenix BIOS. The System Management Mode
633 is used to set the BIOS and power saving options on Toshiba portables.
635 For information on utilities to make use of this driver see the
636 Toshiba Linux utilities web site at:
637 <http://www.buzzard.org.uk/toshiba/>.
639 Say Y if you intend to run this kernel on a Toshiba portable.
643 tristate "Dell laptop support"
645 This adds a driver to safely access the System Management Mode
646 of the CPU on the Dell Inspiron 8000. The System Management Mode
647 is used to read cpu temperature and cooling fan status and to
648 control the fans on the I8K portables.
650 This driver has been tested only on the Inspiron 8000 but it may
651 also work with other Dell laptops. You can force loading on other
652 models by passing the parameter `force=1' to the module. Use at
655 For information on utilities to make use of this driver see the
656 I8K Linux utilities web site at:
657 <http://people.debian.org/~dz/i8k/>
659 Say Y if you intend to run this kernel on a Dell Inspiron 8000.
662 config X86_REBOOTFIXUPS
664 prompt "Enable X86 board specific fixups for reboot"
665 depends on X86_32 && X86
667 This enables chipset and/or board specific fixups to be done
668 in order to get reboot to work correctly. This is only needed on
669 some combinations of hardware and BIOS. The symptom, for which
670 this config is intended, is when reboot ends with a stalled/hung
673 Currently, the only fixup is for the Geode machines using
674 CS5530A and CS5536 chipsets and the RDC R-321x SoC.
676 Say Y if you want to enable the fixup. Currently, it's safe to
677 enable this option even if you don't need it.
681 tristate "/dev/cpu/microcode - Intel IA32 CPU microcode support"
684 If you say Y here, you will be able to update the microcode on
685 Intel processors in the IA32 family, e.g. Pentium Pro, Pentium II,
686 Pentium III, Pentium 4, Xeon etc. You will obviously need the
687 actual microcode binary data itself which is not shipped with the
690 For latest news and information on obtaining all the required
691 ingredients for this driver, check:
692 <http://www.urbanmyth.org/microcode/>.
694 To compile this driver as a module, choose M here: the
695 module will be called microcode.
697 config MICROCODE_OLD_INTERFACE
702 tristate "/dev/cpu/*/msr - Model-specific register support"
704 This device gives privileged processes access to the x86
705 Model-Specific Registers (MSRs). It is a character device with
706 major 202 and minors 0 to 31 for /dev/cpu/0/msr to /dev/cpu/31/msr.
707 MSR accesses are directed to a specific CPU on multi-processor
711 tristate "/dev/cpu/*/cpuid - CPU information support"
713 This device gives processes access to the x86 CPUID instruction to
714 be executed on a specific processor. It is a character device
715 with major 203 and minors 0 to 31 for /dev/cpu/0/cpuid to
719 prompt "High Memory Support"
720 default HIGHMEM4G if !X86_NUMAQ
721 default HIGHMEM64G if X86_NUMAQ
726 depends on !X86_NUMAQ
728 Linux can use up to 64 Gigabytes of physical memory on x86 systems.
729 However, the address space of 32-bit x86 processors is only 4
730 Gigabytes large. That means that, if you have a large amount of
731 physical memory, not all of it can be "permanently mapped" by the
732 kernel. The physical memory that's not permanently mapped is called
735 If you are compiling a kernel which will never run on a machine with
736 more than 1 Gigabyte total physical RAM, answer "off" here (default
737 choice and suitable for most users). This will result in a "3GB/1GB"
738 split: 3GB are mapped so that each process sees a 3GB virtual memory
739 space and the remaining part of the 4GB virtual memory space is used
740 by the kernel to permanently map as much physical memory as
743 If the machine has between 1 and 4 Gigabytes physical RAM, then
746 If more than 4 Gigabytes is used then answer "64GB" here. This
747 selection turns Intel PAE (Physical Address Extension) mode on.
748 PAE implements 3-level paging on IA32 processors. PAE is fully
749 supported by Linux, PAE mode is implemented on all recent Intel
750 processors (Pentium Pro and better). NOTE: If you say "64GB" here,
751 then the kernel will not boot on CPUs that don't support PAE!
753 The actual amount of total physical memory will either be
754 auto detected or can be forced by using a kernel command line option
755 such as "mem=256M". (Try "man bootparam" or see the documentation of
756 your boot loader (lilo or loadlin) about how to pass options to the
757 kernel at boot time.)
759 If unsure, say "off".
763 depends on !X86_NUMAQ
765 Select this if you have a 32-bit processor and between 1 and 4
766 gigabytes of physical RAM.
770 depends on !M386 && !M486
773 Select this if you have a 32-bit processor and more than 4
774 gigabytes of physical RAM.
779 depends on EXPERIMENTAL
780 prompt "Memory split" if EMBEDDED
784 Select the desired split between kernel and user memory.
786 If the address range available to the kernel is less than the
787 physical memory installed, the remaining memory will be available
788 as "high memory". Accessing high memory is a little more costly
789 than low memory, as it needs to be mapped into the kernel first.
790 Note that increasing the kernel address space limits the range
791 available to user programs, making the address space there
792 tighter. Selecting anything other than the default 3G/1G split
793 will also likely make your kernel incompatible with binary-only
796 If you are not absolutely sure what you are doing, leave this
800 bool "3G/1G user/kernel split"
801 config VMSPLIT_3G_OPT
803 bool "3G/1G user/kernel split (for full 1G low memory)"
805 bool "2G/2G user/kernel split"
806 config VMSPLIT_2G_OPT
808 bool "2G/2G user/kernel split (for full 2G low memory)"
810 bool "1G/3G user/kernel split"
815 default 0xB0000000 if VMSPLIT_3G_OPT
816 default 0x80000000 if VMSPLIT_2G
817 default 0x78000000 if VMSPLIT_2G_OPT
818 default 0x40000000 if VMSPLIT_1G
824 depends on X86_32 && (HIGHMEM64G || HIGHMEM4G)
828 prompt "PAE (Physical Address Extension) Support"
829 depends on X86_32 && !HIGHMEM4G
830 select RESOURCES_64BIT
832 PAE is required for NX support, and furthermore enables
833 larger swapspace support for non-overcommit purposes. It
834 has the cost of more pagetable lookup overhead, and also
835 consumes more pagetable space per process.
837 # Common NUMA Features
839 bool "Numa Memory Allocation and Scheduler Support (EXPERIMENTAL)"
841 depends on X86_64 || (X86_32 && HIGHMEM64G && (X86_NUMAQ || (X86_SUMMIT || X86_GENERICARCH) && ACPI) && EXPERIMENTAL)
843 default y if (X86_NUMAQ || X86_SUMMIT)
845 Enable NUMA (Non Uniform Memory Access) support.
846 The kernel will try to allocate memory used by a CPU on the
847 local memory controller of the CPU and add some more
848 NUMA awareness to the kernel.
850 For i386 this is currently highly experimental and should be only
851 used for kernel development. It might also cause boot failures.
852 For x86_64 this is recommended on all multiprocessor Opteron systems.
853 If the system is EM64T, you should say N unless your system is
856 comment "NUMA (Summit) requires SMP, 64GB highmem support, ACPI"
857 depends on X86_32 && X86_SUMMIT && (!HIGHMEM64G || !ACPI)
861 prompt "Old style AMD Opteron NUMA detection"
862 depends on X86_64 && NUMA && PCI
864 Enable K8 NUMA node topology detection. You should say Y here if
865 you have a multi processor AMD K8 system. This uses an old
866 method to read the NUMA configuration directly from the builtin
867 Northbridge of Opteron. It is recommended to use X86_64_ACPI_NUMA
868 instead, which also takes priority if both are compiled in.
870 config X86_64_ACPI_NUMA
872 prompt "ACPI NUMA detection"
873 depends on X86_64 && NUMA && ACPI && PCI
876 Enable ACPI SRAT based node topology detection.
879 bool "NUMA emulation"
880 depends on X86_64 && NUMA
882 Enable NUMA emulation. A flat machine will be split
883 into virtual nodes when booted with "numa=fake=N", where N is the
884 number of nodes. This is only useful for debugging.
889 default "6" if X86_64
890 default "4" if X86_NUMAQ
892 depends on NEED_MULTIPLE_NODES
894 config HAVE_ARCH_BOOTMEM_NODE
896 depends on X86_32 && NUMA
898 config ARCH_HAVE_MEMORY_PRESENT
900 depends on X86_32 && DISCONTIGMEM
902 config NEED_NODE_MEMMAP_SIZE
904 depends on X86_32 && (DISCONTIGMEM || SPARSEMEM)
906 config HAVE_ARCH_ALLOC_REMAP
908 depends on X86_32 && NUMA
910 config ARCH_FLATMEM_ENABLE
912 depends on X86_32 && ARCH_SELECT_MEMORY_MODEL && X86_PC && !NUMA
914 config ARCH_DISCONTIGMEM_ENABLE
916 depends on NUMA && X86_32
918 config ARCH_DISCONTIGMEM_DEFAULT
920 depends on NUMA && X86_32
922 config ARCH_SPARSEMEM_DEFAULT
926 config ARCH_SPARSEMEM_ENABLE
928 depends on X86_64 || NUMA || (EXPERIMENTAL && X86_PC)
929 select SPARSEMEM_STATIC if X86_32
930 select SPARSEMEM_VMEMMAP_ENABLE if X86_64
932 config ARCH_SELECT_MEMORY_MODEL
934 depends on ARCH_SPARSEMEM_ENABLE
936 config ARCH_MEMORY_PROBE
938 depends on MEMORY_HOTPLUG
943 bool "Allocate 3rd-level pagetables from highmem"
944 depends on X86_32 && (HIGHMEM4G || HIGHMEM64G)
946 The VM uses one page table entry for each page of physical memory.
947 For systems with a lot of RAM, this can be wasteful of precious
948 low memory. Setting this option will put user-space page table
949 entries in high memory.
951 config MATH_EMULATION
953 prompt "Math emulation" if X86_32
955 Linux can emulate a math coprocessor (used for floating point
956 operations) if you don't have one. 486DX and Pentium processors have
957 a math coprocessor built in, 486SX and 386 do not, unless you added
958 a 487DX or 387, respectively. (The messages during boot time can
959 give you some hints here ["man dmesg"].) Everyone needs either a
960 coprocessor or this emulation.
962 If you don't have a math coprocessor, you need to say Y here; if you
963 say Y here even though you have a coprocessor, the coprocessor will
964 be used nevertheless. (This behavior can be changed with the kernel
965 command line option "no387", which comes handy if your coprocessor
966 is broken. Try "man bootparam" or see the documentation of your boot
967 loader (lilo or loadlin) about how to pass options to the kernel at
968 boot time.) This means that it is a good idea to say Y here if you
969 intend to use this kernel on different machines.
971 More information about the internals of the Linux math coprocessor
972 emulation can be found in <file:arch/x86/math-emu/README>.
974 If you are not sure, say Y; apart from resulting in a 66 KB bigger
975 kernel, it won't hurt.
978 bool "MTRR (Memory Type Range Register) support"
980 On Intel P6 family processors (Pentium Pro, Pentium II and later)
981 the Memory Type Range Registers (MTRRs) may be used to control
982 processor access to memory ranges. This is most useful if you have
983 a video (VGA) card on a PCI or AGP bus. Enabling write-combining
984 allows bus write transfers to be combined into a larger transfer
985 before bursting over the PCI/AGP bus. This can increase performance
986 of image write operations 2.5 times or more. Saying Y here creates a
987 /proc/mtrr file which may be used to manipulate your processor's
988 MTRRs. Typically the X server should use this.
990 This code has a reasonably generic interface so that similar
991 control registers on other processors can be easily supported
994 The Cyrix 6x86, 6x86MX and M II processors have Address Range
995 Registers (ARRs) which provide a similar functionality to MTRRs. For
996 these, the ARRs are used to emulate the MTRRs.
997 The AMD K6-2 (stepping 8 and above) and K6-3 processors have two
998 MTRRs. The Centaur C6 (WinChip) has 8 MCRs, allowing
999 write-combining. All of these processors are supported by this code
1000 and it makes sense to say Y here if you have one of them.
1002 Saying Y here also fixes a problem with buggy SMP BIOSes which only
1003 set the MTRRs for the boot CPU and not for the secondary CPUs. This
1004 can lead to all sorts of problems, so it's good to say Y here.
1006 You can safely say Y even if your machine doesn't have MTRRs, you'll
1007 just add about 9 KB to your kernel.
1009 See <file:Documentation/mtrr.txt> for more information.
1013 prompt "EFI runtime service support"
1016 This enables the kernel to use EFI runtime services that are
1017 available (such as the EFI variable services).
1019 This option is only useful on systems that have EFI firmware.
1020 In addition, you should use the latest ELILO loader available
1021 at <http://elilo.sourceforge.net> in order to take advantage
1022 of EFI runtime services. However, even with this option, the
1023 resultant kernel should continue to boot on existing non-EFI
1028 prompt "Enable kernel irq balancing"
1029 depends on X86_32 && SMP && X86_IO_APIC
1031 The default yes will allow the kernel to do irq load balancing.
1032 Saying no will keep the kernel from doing irq load balancing.
1036 prompt "Enable seccomp to safely compute untrusted bytecode"
1039 This kernel feature is useful for number crunching applications
1040 that may need to compute untrusted bytecode during their
1041 execution. By using pipes or other transports made available to
1042 the process as file descriptors supporting the read/write
1043 syscalls, it's possible to isolate those applications in
1044 their own address space using seccomp. Once seccomp is
1045 enabled via /proc/<pid>/seccomp, it cannot be disabled
1046 and the task is only allowed to execute a few safe syscalls
1047 defined by each seccomp mode.
1049 If unsure, say Y. Only embedded should say N here.
1051 config CC_STACKPROTECTOR
1052 bool "Enable -fstack-protector buffer overflow detection (EXPERIMENTAL)"
1053 depends on X86_64 && EXPERIMENTAL
1055 This option turns on the -fstack-protector GCC feature. This
1056 feature puts, at the beginning of critical functions, a canary
1057 value on the stack just before the return address, and validates
1058 the value just before actually returning. Stack based buffer
1059 overflows (that need to overwrite this return address) now also
1060 overwrite the canary, which gets detected and the attack is then
1061 neutralized via a kernel panic.
1063 This feature requires gcc version 4.2 or above, or a distribution
1064 gcc with the feature backported. Older versions are automatically
1065 detected and for those versions, this configuration option is ignored.
1067 config CC_STACKPROTECTOR_ALL
1068 bool "Use stack-protector for all functions"
1069 depends on CC_STACKPROTECTOR
1071 Normally, GCC only inserts the canary value protection for
1072 functions that use large-ish on-stack buffers. By enabling
1073 this option, GCC will be asked to do this for ALL functions.
1075 source kernel/Kconfig.hz
1078 bool "kexec system call"
1080 kexec is a system call that implements the ability to shutdown your
1081 current kernel, and to start another kernel. It is like a reboot
1082 but it is independent of the system firmware. And like a reboot
1083 you can start any kernel with it, not just Linux.
1085 The name comes from the similarity to the exec system call.
1087 It is an ongoing process to be certain the hardware in a machine
1088 is properly shutdown, so do not be surprised if this code does not
1089 initially work for you. It may help to enable device hotplugging
1090 support. As of this writing the exact hardware interface is
1091 strongly in flux, so no good recommendation can be made.
1094 bool "kernel crash dumps (EXPERIMENTAL)"
1095 depends on EXPERIMENTAL
1096 depends on X86_64 || (X86_32 && HIGHMEM)
1098 Generate crash dump after being started by kexec.
1099 This should be normally only set in special crash dump kernels
1100 which are loaded in the main kernel with kexec-tools into
1101 a specially reserved region and then later executed after
1102 a crash by kdump/kexec. The crash dump kernel must be compiled
1103 to a memory address not used by the main kernel or BIOS using
1104 PHYSICAL_START, or it must be built as a relocatable image
1105 (CONFIG_RELOCATABLE=y).
1106 For more details see Documentation/kdump/kdump.txt
1108 config PHYSICAL_START
1109 hex "Physical address where the kernel is loaded" if (EMBEDDED || CRASH_DUMP)
1110 default "0x1000000" if X86_NUMAQ
1111 default "0x200000" if X86_64
1114 This gives the physical address where the kernel is loaded.
1116 If kernel is a not relocatable (CONFIG_RELOCATABLE=n) then
1117 bzImage will decompress itself to above physical address and
1118 run from there. Otherwise, bzImage will run from the address where
1119 it has been loaded by the boot loader and will ignore above physical
1122 In normal kdump cases one does not have to set/change this option
1123 as now bzImage can be compiled as a completely relocatable image
1124 (CONFIG_RELOCATABLE=y) and be used to load and run from a different
1125 address. This option is mainly useful for the folks who don't want
1126 to use a bzImage for capturing the crash dump and want to use a
1127 vmlinux instead. vmlinux is not relocatable hence a kernel needs
1128 to be specifically compiled to run from a specific memory area
1129 (normally a reserved region) and this option comes handy.
1131 So if you are using bzImage for capturing the crash dump, leave
1132 the value here unchanged to 0x100000 and set CONFIG_RELOCATABLE=y.
1133 Otherwise if you plan to use vmlinux for capturing the crash dump
1134 change this value to start of the reserved region (Typically 16MB
1135 0x1000000). In other words, it can be set based on the "X" value as
1136 specified in the "crashkernel=YM@XM" command line boot parameter
1137 passed to the panic-ed kernel. Typically this parameter is set as
1138 crashkernel=64M@16M. Please take a look at
1139 Documentation/kdump/kdump.txt for more details about crash dumps.
1141 Usage of bzImage for capturing the crash dump is recommended as
1142 one does not have to build two kernels. Same kernel can be used
1143 as production kernel and capture kernel. Above option should have
1144 gone away after relocatable bzImage support is introduced. But it
1145 is present because there are users out there who continue to use
1146 vmlinux for dump capture. This option should go away down the
1149 Don't change this unless you know what you are doing.
1152 bool "Build a relocatable kernel (EXPERIMENTAL)"
1153 depends on EXPERIMENTAL
1155 This builds a kernel image that retains relocation information
1156 so it can be loaded someplace besides the default 1MB.
1157 The relocations tend to make the kernel binary about 10% larger,
1158 but are discarded at runtime.
1160 One use is for the kexec on panic case where the recovery kernel
1161 must live at a different physical address than the primary
1164 Note: If CONFIG_RELOCATABLE=y, then the kernel runs from the address
1165 it has been loaded at and the compile time physical address
1166 (CONFIG_PHYSICAL_START) is ignored.
1168 config PHYSICAL_ALIGN
1170 prompt "Alignment value to which kernel should be aligned" if X86_32
1171 default "0x100000" if X86_32
1172 default "0x200000" if X86_64
1173 range 0x2000 0x400000
1175 This value puts the alignment restrictions on physical address
1176 where kernel is loaded and run from. Kernel is compiled for an
1177 address which meets above alignment restriction.
1179 If bootloader loads the kernel at a non-aligned address and
1180 CONFIG_RELOCATABLE is set, kernel will move itself to nearest
1181 address aligned to above value and run from there.
1183 If bootloader loads the kernel at a non-aligned address and
1184 CONFIG_RELOCATABLE is not set, kernel will ignore the run time
1185 load address and decompress itself to the address it has been
1186 compiled for and run from there. The address for which kernel is
1187 compiled already meets above alignment restrictions. Hence the
1188 end result is that kernel runs from a physical address meeting
1189 above alignment restrictions.
1191 Don't change this unless you know what you are doing.
1194 bool "Support for suspend on SMP and hot-pluggable CPUs (EXPERIMENTAL)"
1195 depends on SMP && HOTPLUG && EXPERIMENTAL && !X86_VOYAGER
1197 Say Y here to experiment with turning CPUs off and on, and to
1198 enable suspend on SMP systems. CPUs can be controlled through
1199 /sys/devices/system/cpu.
1200 Say N if you want to disable CPU hotplug and don't need to
1205 prompt "Compat VDSO support"
1206 depends on X86_32 || IA32_EMULATION
1208 Map the 32-bit VDSO to the predictable old-style address too.
1210 Say N here if you are running a sufficiently recent glibc
1211 version (2.3.3 or later), to remove the high-mapped
1212 VDSO mapping and to exclusively use the randomized VDSO.
1218 config ARCH_ENABLE_MEMORY_HOTPLUG
1220 depends on X86_64 || (X86_32 && HIGHMEM)
1222 config HAVE_ARCH_EARLY_PFN_TO_NID
1226 menu "Power management options"
1227 depends on !X86_VOYAGER
1229 config ARCH_HIBERNATION_HEADER
1231 depends on X86_64 && HIBERNATION
1233 source "kernel/power/Kconfig"
1235 source "drivers/acpi/Kconfig"
1240 depends on APM || APM_MODULE
1243 tristate "APM (Advanced Power Management) BIOS support"
1244 depends on X86_32 && PM_SLEEP && !X86_VISWS
1246 APM is a BIOS specification for saving power using several different
1247 techniques. This is mostly useful for battery powered laptops with
1248 APM compliant BIOSes. If you say Y here, the system time will be
1249 reset after a RESUME operation, the /proc/apm device will provide
1250 battery status information, and user-space programs will receive
1251 notification of APM "events" (e.g. battery status change).
1253 If you select "Y" here, you can disable actual use of the APM
1254 BIOS by passing the "apm=off" option to the kernel at boot time.
1256 Note that the APM support is almost completely disabled for
1257 machines with more than one CPU.
1259 In order to use APM, you will need supporting software. For location
1260 and more information, read <file:Documentation/pm.txt> and the
1261 Battery Powered Linux mini-HOWTO, available from
1262 <http://www.tldp.org/docs.html#howto>.
1264 This driver does not spin down disk drives (see the hdparm(8)
1265 manpage ("man 8 hdparm") for that), and it doesn't turn off
1266 VESA-compliant "green" monitors.
1268 This driver does not support the TI 4000M TravelMate and the ACER
1269 486/DX4/75 because they don't have compliant BIOSes. Many "green"
1270 desktop machines also don't have compliant BIOSes, and this driver
1271 may cause those machines to panic during the boot phase.
1273 Generally, if you don't have a battery in your machine, there isn't
1274 much point in using this driver and you should say N. If you get
1275 random kernel OOPSes or reboots that don't seem to be related to
1276 anything, try disabling/enabling this option (or disabling/enabling
1279 Some other things you should try when experiencing seemingly random,
1282 1) make sure that you have enough swap space and that it is
1284 2) pass the "no-hlt" option to the kernel
1285 3) switch on floating point emulation in the kernel and pass
1286 the "no387" option to the kernel
1287 4) pass the "floppy=nodma" option to the kernel
1288 5) pass the "mem=4M" option to the kernel (thereby disabling
1289 all but the first 4 MB of RAM)
1290 6) make sure that the CPU is not over clocked.
1291 7) read the sig11 FAQ at <http://www.bitwizard.nl/sig11/>
1292 8) disable the cache from your BIOS settings
1293 9) install a fan for the video card or exchange video RAM
1294 10) install a better fan for the CPU
1295 11) exchange RAM chips
1296 12) exchange the motherboard.
1298 To compile this driver as a module, choose M here: the
1299 module will be called apm.
1303 config APM_IGNORE_USER_SUSPEND
1304 bool "Ignore USER SUSPEND"
1306 This option will ignore USER SUSPEND requests. On machines with a
1307 compliant APM BIOS, you want to say N. However, on the NEC Versa M
1308 series notebooks, it is necessary to say Y because of a BIOS bug.
1310 config APM_DO_ENABLE
1311 bool "Enable PM at boot time"
1313 Enable APM features at boot time. From page 36 of the APM BIOS
1314 specification: "When disabled, the APM BIOS does not automatically
1315 power manage devices, enter the Standby State, enter the Suspend
1316 State, or take power saving steps in response to CPU Idle calls."
1317 This driver will make CPU Idle calls when Linux is idle (unless this
1318 feature is turned off -- see "Do CPU IDLE calls", below). This
1319 should always save battery power, but more complicated APM features
1320 will be dependent on your BIOS implementation. You may need to turn
1321 this option off if your computer hangs at boot time when using APM
1322 support, or if it beeps continuously instead of suspending. Turn
1323 this off if you have a NEC UltraLite Versa 33/C or a Toshiba
1324 T400CDT. This is off by default since most machines do fine without
1328 bool "Make CPU Idle calls when idle"
1330 Enable calls to APM CPU Idle/CPU Busy inside the kernel's idle loop.
1331 On some machines, this can activate improved power savings, such as
1332 a slowed CPU clock rate, when the machine is idle. These idle calls
1333 are made after the idle loop has run for some length of time (e.g.,
1334 333 mS). On some machines, this will cause a hang at boot time or
1335 whenever the CPU becomes idle. (On machines with more than one CPU,
1336 this option does nothing.)
1338 config APM_DISPLAY_BLANK
1339 bool "Enable console blanking using APM"
1341 Enable console blanking using the APM. Some laptops can use this to
1342 turn off the LCD backlight when the screen blanker of the Linux
1343 virtual console blanks the screen. Note that this is only used by
1344 the virtual console screen blanker, and won't turn off the backlight
1345 when using the X Window system. This also doesn't have anything to
1346 do with your VESA-compliant power-saving monitor. Further, this
1347 option doesn't work for all laptops -- it might not turn off your
1348 backlight at all, or it might print a lot of errors to the console,
1349 especially if you are using gpm.
1351 config APM_ALLOW_INTS
1352 bool "Allow interrupts during APM BIOS calls"
1354 Normally we disable external interrupts while we are making calls to
1355 the APM BIOS as a measure to lessen the effects of a badly behaving
1356 BIOS implementation. The BIOS should reenable interrupts if it
1357 needs to. Unfortunately, some BIOSes do not -- especially those in
1358 many of the newer IBM Thinkpads. If you experience hangs when you
1359 suspend, try setting this to Y. Otherwise, say N.
1361 config APM_REAL_MODE_POWER_OFF
1362 bool "Use real mode APM BIOS call to power off"
1364 Use real mode APM BIOS calls to switch off the computer. This is
1365 a work-around for a number of buggy BIOSes. Switch this option on if
1366 your computer crashes instead of powering off properly.
1370 source "arch/x86/kernel/cpu/cpufreq/Kconfig"
1372 source "drivers/cpuidle/Kconfig"
1377 menu "Bus options (PCI etc.)"
1380 bool "PCI support" if !X86_VISWS
1381 depends on !X86_VOYAGER
1383 select ARCH_SUPPORTS_MSI if (X86_LOCAL_APIC && X86_IO_APIC)
1385 Find out whether you have a PCI motherboard. PCI is the name of a
1386 bus system, i.e. the way the CPU talks to the other stuff inside
1387 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
1388 VESA. If you have PCI, say Y, otherwise N.
1391 prompt "PCI access mode"
1392 depends on X86_32 && PCI && !X86_VISWS
1395 On PCI systems, the BIOS can be used to detect the PCI devices and
1396 determine their configuration. However, some old PCI motherboards
1397 have BIOS bugs and may crash if this is done. Also, some embedded
1398 PCI-based systems don't have any BIOS at all. Linux can also try to
1399 detect the PCI hardware directly without using the BIOS.
1401 With this option, you can specify how Linux should detect the
1402 PCI devices. If you choose "BIOS", the BIOS will be used,
1403 if you choose "Direct", the BIOS won't be used, and if you
1404 choose "MMConfig", then PCI Express MMCONFIG will be used.
1405 If you choose "Any", the kernel will try MMCONFIG, then the
1406 direct access method and falls back to the BIOS if that doesn't
1407 work. If unsure, go with the default, which is "Any".
1412 config PCI_GOMMCONFIG
1425 depends on X86_32 && !X86_VISWS && PCI && (PCI_GOBIOS || PCI_GOANY)
1427 # x86-64 doesn't support PCI BIOS access from long mode so always go direct.
1430 depends on PCI && (X86_64 || (PCI_GODIRECT || PCI_GOANY) || X86_VISWS)
1434 depends on X86_32 && PCI && ACPI && (PCI_GOMMCONFIG || PCI_GOANY)
1441 bool "Support mmconfig PCI config space access"
1442 depends on X86_64 && PCI && ACPI
1445 bool "Support for DMA Remapping Devices (EXPERIMENTAL)"
1446 depends on X86_64 && PCI_MSI && ACPI && EXPERIMENTAL
1448 DMA remapping (DMAR) devices support enables independent address
1449 translations for Direct Memory Access (DMA) from devices.
1450 These DMA remapping devices are reported via ACPI tables
1451 and include PCI device scope covered by these DMA
1456 prompt "Support for Graphics workaround"
1459 Current Graphics drivers tend to use physical address
1460 for DMA and avoid using DMA APIs. Setting this config
1461 option permits the IOMMU driver to set a unity map for
1462 all the OS-visible memory. Hence the driver can continue
1463 to use physical addresses for DMA.
1465 config DMAR_FLOPPY_WA
1469 Floppy disk drivers are know to bypass DMA API calls
1470 thereby failing to work when IOMMU is enabled. This
1471 workaround will setup a 1:1 mapping for the first
1472 16M to make floppy (an ISA device) work.
1474 source "drivers/pci/pcie/Kconfig"
1476 source "drivers/pci/Kconfig"
1478 # x86_64 have no ISA slots, but do have ISA-style DMA.
1486 depends on !(X86_VOYAGER || X86_VISWS)
1488 Find out whether you have ISA slots on your motherboard. ISA is the
1489 name of a bus system, i.e. the way the CPU talks to the other stuff
1490 inside your box. Other bus systems are PCI, EISA, MicroChannel
1491 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
1492 newer boards don't support it. If you have ISA, say Y, otherwise N.
1498 The Extended Industry Standard Architecture (EISA) bus was
1499 developed as an open alternative to the IBM MicroChannel bus.
1501 The EISA bus provided some of the features of the IBM MicroChannel
1502 bus while maintaining backward compatibility with cards made for
1503 the older ISA bus. The EISA bus saw limited use between 1988 and
1504 1995 when it was made obsolete by the PCI bus.
1506 Say Y here if you are building a kernel for an EISA-based machine.
1510 source "drivers/eisa/Kconfig"
1513 bool "MCA support" if !(X86_VISWS || X86_VOYAGER)
1514 default y if X86_VOYAGER
1516 MicroChannel Architecture is found in some IBM PS/2 machines and
1517 laptops. It is a bus system similar to PCI or ISA. See
1518 <file:Documentation/mca.txt> (and especially the web page given
1519 there) before attempting to build an MCA bus kernel.
1521 source "drivers/mca/Kconfig"
1524 tristate "NatSemi SCx200 support"
1525 depends on !X86_VOYAGER
1527 This provides basic support for National Semiconductor's
1528 (now AMD's) Geode processors. The driver probes for the
1529 PCI-IDs of several on-chip devices, so its a good dependency
1530 for other scx200_* drivers.
1532 If compiled as a module, the driver is named scx200.
1534 config SCx200HR_TIMER
1535 tristate "NatSemi SCx200 27MHz High-Resolution Timer Support"
1536 depends on SCx200 && GENERIC_TIME
1539 This driver provides a clocksource built upon the on-chip
1540 27MHz high-resolution timer. Its also a workaround for
1541 NSC Geode SC-1100's buggy TSC, which loses time when the
1542 processor goes idle (as is done by the scheduler). The
1543 other workaround is idle=poll boot option.
1545 config GEODE_MFGPT_TIMER
1547 prompt "Geode Multi-Function General Purpose Timer (MFGPT) events"
1548 depends on MGEODE_LX && GENERIC_TIME && GENERIC_CLOCKEVENTS
1550 This driver provides a clock event source based on the MFGPT
1551 timer(s) in the CS5535 and CS5536 companion chip for the geode.
1552 MFGPTs have a better resolution and max interval than the
1553 generic PIT, and are suitable for use as high-res timers.
1559 depends on AGP_AMD64 || (X86_64 && (GART_IOMMU || (PCI && NUMA)))
1561 source "drivers/pcmcia/Kconfig"
1563 source "drivers/pci/hotplug/Kconfig"
1568 menu "Executable file formats / Emulations"
1570 source "fs/Kconfig.binfmt"
1572 config IA32_EMULATION
1573 bool "IA32 Emulation"
1575 select COMPAT_BINFMT_ELF
1577 Include code to run 32-bit programs under a 64-bit kernel. You should
1578 likely turn this on, unless you're 100% sure that you don't have any
1579 32-bit programs left.
1582 tristate "IA32 a.out support"
1583 depends on IA32_EMULATION && ARCH_SUPPORTS_AOUT
1585 Support old a.out binaries in the 32bit emulation.
1589 depends on IA32_EMULATION
1591 config COMPAT_FOR_U64_ALIGNMENT
1595 config SYSVIPC_COMPAT
1597 depends on X86_64 && COMPAT && SYSVIPC
1602 source "net/Kconfig"
1604 source "drivers/Kconfig"
1606 source "drivers/firmware/Kconfig"
1610 source "arch/x86/Kconfig.debug"
1612 source "security/Kconfig"
1614 source "crypto/Kconfig"
1616 source "arch/x86/kvm/Kconfig"
1618 source "lib/Kconfig"
projects / linux-2.6-omap-h63xx.git / blob