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 ARCH_HAS_CPU_IDLE_WAIT
108 config GENERIC_CALIBRATE_DELAY
111 config GENERIC_TIME_VSYSCALL
115 config ARCH_HAS_CPU_RELAX
118 config HAVE_SETUP_PER_CPU_AREA
123 config ARCH_HIBERNATION_POSSIBLE
125 depends on !SMP || !X86_VOYAGER
127 config ARCH_SUSPEND_POSSIBLE
129 depends on !X86_VOYAGER
135 config ARCH_POPULATES_NODE_MAP
142 config ARCH_SUPPORTS_AOUT
145 # Use the generic interrupt handling code in kernel/irq/:
146 config GENERIC_HARDIRQS
150 config GENERIC_IRQ_PROBE
154 config GENERIC_PENDING_IRQ
156 depends on GENERIC_HARDIRQS && SMP
161 depends on SMP && ((X86_32 && !X86_VOYAGER) || X86_64)
166 depends on X86_32 && SMP
170 depends on X86_64 && SMP
175 depends on (X86_32 && !(X86_VISWS || X86_VOYAGER)) || (X86_64 && !MK8)
178 config X86_BIOS_REBOOT
180 depends on X86_32 && !(X86_VISWS || X86_VOYAGER)
183 config X86_TRAMPOLINE
185 depends on X86_SMP || (X86_VOYAGER && SMP)
190 source "init/Kconfig"
192 menu "Processor type and features"
194 source "kernel/time/Kconfig"
197 bool "Symmetric multi-processing support"
199 This enables support for systems with more than one CPU. If you have
200 a system with only one CPU, like most personal computers, say N. If
201 you have a system with more than one CPU, say Y.
203 If you say N here, the kernel will run on single and multiprocessor
204 machines, but will use only one CPU of a multiprocessor machine. If
205 you say Y here, the kernel will run on many, but not all,
206 singleprocessor machines. On a singleprocessor machine, the kernel
207 will run faster if you say N here.
209 Note that if you say Y here and choose architecture "586" or
210 "Pentium" under "Processor family", the kernel will not work on 486
211 architectures. Similarly, multiprocessor kernels for the "PPro"
212 architecture may not work on all Pentium based boards.
214 People using multiprocessor machines who say Y here should also say
215 Y to "Enhanced Real Time Clock Support", below. The "Advanced Power
216 Management" code will be disabled if you say Y here.
218 See also <file:Documentation/i386/IO-APIC.txt>,
219 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
220 <http://www.tldp.org/docs.html#howto>.
222 If you don't know what to do here, say N.
225 prompt "Subarchitecture Type"
231 Choose this option if your computer is a standard PC or compatible.
237 Select this for an AMD Elan processor.
239 Do not use this option for K6/Athlon/Opteron processors!
241 If unsure, choose "PC-compatible" instead.
246 select SMP if !BROKEN
248 Voyager is an MCA-based 32-way capable SMP architecture proprietary
249 to NCR Corp. Machine classes 345x/35xx/4100/51xx are Voyager-based.
253 If you do not specifically know you have a Voyager based machine,
254 say N here, otherwise the kernel you build will not be bootable.
257 bool "NUMAQ (IBM/Sequent)"
262 This option is used for getting Linux to run on a (IBM/Sequent) NUMA
263 multiquad box. This changes the way that processors are bootstrapped,
264 and uses Clustered Logical APIC addressing mode instead of Flat Logical.
265 You will need a new lynxer.elf file to flash your firmware with - send
266 email to <Martin.Bligh@us.ibm.com>.
269 bool "Summit/EXA (IBM x440)"
270 depends on X86_32 && SMP
272 This option is needed for IBM systems that use the Summit/EXA chipset.
273 In particular, it is needed for the x440.
275 If you don't have one of these computers, you should say N here.
276 If you want to build a NUMA kernel, you must select ACPI.
279 bool "Support for other sub-arch SMP systems with more than 8 CPUs"
280 depends on X86_32 && SMP
282 This option is needed for the systems that have more than 8 CPUs
283 and if the system is not of any sub-arch type above.
285 If you don't have such a system, you should say N here.
288 bool "SGI 320/540 (Visual Workstation)"
291 The SGI Visual Workstation series is an IA32-based workstation
292 based on SGI systems chips with some legacy PC hardware attached.
294 Say Y here to create a kernel to run on the SGI 320 or 540.
296 A kernel compiled for the Visual Workstation will not run on PCs
297 and vice versa. See <file:Documentation/sgi-visws.txt> for details.
299 config X86_GENERICARCH
300 bool "Generic architecture (Summit, bigsmp, ES7000, default)"
303 This option compiles in the Summit, bigsmp, ES7000, default subarchitectures.
304 It is intended for a generic binary kernel.
305 If you want a NUMA kernel, select ACPI. We need SRAT for NUMA.
308 bool "Support for Unisys ES7000 IA32 series"
309 depends on X86_32 && SMP
311 Support for Unisys ES7000 systems. Say 'Y' here if this kernel is
312 supposed to run on an IA32-based Unisys ES7000 system.
313 Only choose this option if you have such a system, otherwise you
317 bool "RDC R-321x SoC"
320 select X86_REBOOTFIXUPS
325 This option is needed for RDC R-321x system-on-chip, also known
327 If you don't have one of these chips, you should say N here.
330 bool "Support for ScaleMP vSMP"
331 depends on X86_64 && PCI
333 Support for ScaleMP vSMP systems. Say 'Y' here if this kernel is
334 supposed to run on these EM64T-based machines. Only choose this option
335 if you have one of these machines.
339 config SCHED_NO_NO_OMIT_FRAME_POINTER
341 prompt "Single-depth WCHAN output"
344 Calculate simpler /proc/<PID>/wchan values. If this option
345 is disabled then wchan values will recurse back to the
346 caller function. This provides more accurate wchan values,
347 at the expense of slightly more scheduling overhead.
349 If in doubt, say "Y".
351 menuconfig PARAVIRT_GUEST
352 bool "Paravirtualized guest support"
354 Say Y here to get to see options related to running Linux under
355 various hypervisors. This option alone does not add any kernel code.
357 If you say N, all options in this submenu will be skipped and disabled.
361 source "arch/x86/xen/Kconfig"
364 bool "VMI Guest support"
367 depends on !(X86_VISWS || X86_VOYAGER)
369 VMI provides a paravirtualized interface to the VMware ESX server
370 (it could be used by other hypervisors in theory too, but is not
371 at the moment), by linking the kernel to a GPL-ed ROM module
372 provided by the hypervisor.
374 source "arch/x86/lguest/Kconfig"
377 bool "Enable paravirtualization code"
378 depends on !(X86_VISWS || X86_VOYAGER)
380 This changes the kernel so it can modify itself when it is run
381 under a hypervisor, potentially improving performance significantly
382 over full virtualization. However, when run without a hypervisor
383 the kernel is theoretically slower and slightly larger.
389 depends on X86_32 && ACPI && NUMA && (X86_SUMMIT || X86_GENERICARCH)
392 config HAVE_ARCH_PARSE_SRAT
396 config X86_SUMMIT_NUMA
398 depends on X86_32 && NUMA && (X86_SUMMIT || X86_GENERICARCH)
400 config X86_CYCLONE_TIMER
402 depends on X86_32 && X86_SUMMIT || X86_GENERICARCH
404 config ES7000_CLUSTERED_APIC
406 depends on SMP && X86_ES7000 && MPENTIUMIII
408 source "arch/x86/Kconfig.cpu"
412 prompt "HPET Timer Support" if X86_32
414 Use the IA-PC HPET (High Precision Event Timer) to manage
415 time in preference to the PIT and RTC, if a HPET is
417 HPET is the next generation timer replacing legacy 8254s.
418 The HPET provides a stable time base on SMP
419 systems, unlike the TSC, but it is more expensive to access,
420 as it is off-chip. You can find the HPET spec at
421 <http://www.intel.com/hardwaredesign/hpetspec.htm>.
423 You can safely choose Y here. However, HPET will only be
424 activated if the platform and the BIOS support this feature.
425 Otherwise the 8254 will be used for timing services.
427 Choose N to continue using the legacy 8254 timer.
429 config HPET_EMULATE_RTC
431 depends on HPET_TIMER && (RTC=y || RTC=m || RTC_DRV_CMOS=m || RTC_DRV_CMOS=y)
433 # Mark as embedded because too many people got it wrong.
434 # The code disables itself when not needed.
436 bool "GART IOMMU support" if EMBEDDED
440 depends on X86_64 && PCI
442 Support for full DMA access of devices with 32bit memory access only
443 on systems with more than 3GB. This is usually needed for USB,
444 sound, many IDE/SATA chipsets and some other devices.
445 Provides a driver for the AMD Athlon64/Opteron/Turion/Sempron GART
446 based hardware IOMMU and a software bounce buffer based IOMMU used
447 on Intel systems and as fallback.
448 The code is only active when needed (enough memory and limited
449 device) unless CONFIG_IOMMU_DEBUG or iommu=force is specified
453 bool "IBM Calgary IOMMU support"
455 depends on X86_64 && PCI && EXPERIMENTAL
457 Support for hardware IOMMUs in IBM's xSeries x366 and x460
458 systems. Needed to run systems with more than 3GB of memory
459 properly with 32-bit PCI devices that do not support DAC
460 (Double Address Cycle). Calgary also supports bus level
461 isolation, where all DMAs pass through the IOMMU. This
462 prevents them from going anywhere except their intended
463 destination. This catches hard-to-find kernel bugs and
464 mis-behaving drivers and devices that do not use the DMA-API
465 properly to set up their DMA buffers. The IOMMU can be
466 turned off at boot time with the iommu=off parameter.
467 Normally the kernel will make the right choice by itself.
470 config CALGARY_IOMMU_ENABLED_BY_DEFAULT
472 prompt "Should Calgary be enabled by default?"
473 depends on CALGARY_IOMMU
475 Should Calgary be enabled by default? if you choose 'y', Calgary
476 will be used (if it exists). If you choose 'n', Calgary will not be
477 used even if it exists. If you choose 'n' and would like to use
478 Calgary anyway, pass 'iommu=calgary' on the kernel command line.
482 def_bool (CALGARY_IOMMU || GART_IOMMU)
484 # need this always selected by IOMMU for the VIA workaround
488 Support for software bounce buffers used on x86-64 systems
489 which don't have a hardware IOMMU (e.g. the current generation
490 of Intel's x86-64 CPUs). Using this PCI devices which can only
491 access 32-bits of memory can be used on systems with more than
492 3 GB of memory. If unsure, say Y.
496 int "Maximum number of CPUs (2-255)"
499 default "32" if X86_NUMAQ || X86_SUMMIT || X86_BIGSMP || X86_ES7000
502 This allows you to specify the maximum number of CPUs which this
503 kernel will support. The maximum supported value is 255 and the
504 minimum value which makes sense is 2.
506 This is purely to save memory - each supported CPU adds
507 approximately eight kilobytes to the kernel image.
510 bool "SMT (Hyperthreading) scheduler support"
511 depends on (X86_64 && SMP) || (X86_32 && X86_HT)
513 SMT scheduler support improves the CPU scheduler's decision making
514 when dealing with Intel Pentium 4 chips with HyperThreading at a
515 cost of slightly increased overhead in some places. If unsure say
520 prompt "Multi-core scheduler support"
521 depends on (X86_64 && SMP) || (X86_32 && X86_HT)
523 Multi-core scheduler support improves the CPU scheduler's decision
524 making when dealing with multi-core CPU chips at a cost of slightly
525 increased overhead in some places. If unsure say N here.
527 source "kernel/Kconfig.preempt"
530 bool "Local APIC support on uniprocessors"
531 depends on X86_32 && !SMP && !(X86_VISWS || X86_VOYAGER || X86_GENERICARCH)
533 A local APIC (Advanced Programmable Interrupt Controller) is an
534 integrated interrupt controller in the CPU. If you have a single-CPU
535 system which has a processor with a local APIC, you can say Y here to
536 enable and use it. If you say Y here even though your machine doesn't
537 have a local APIC, then the kernel will still run with no slowdown at
538 all. The local APIC supports CPU-generated self-interrupts (timer,
539 performance counters), and the NMI watchdog which detects hard
543 bool "IO-APIC support on uniprocessors"
544 depends on X86_UP_APIC
546 An IO-APIC (I/O Advanced Programmable Interrupt Controller) is an
547 SMP-capable replacement for PC-style interrupt controllers. Most
548 SMP systems and many recent uniprocessor systems have one.
550 If you have a single-CPU system with an IO-APIC, you can say Y here
551 to use it. If you say Y here even though your machine doesn't have
552 an IO-APIC, then the kernel will still run with no slowdown at all.
554 config X86_LOCAL_APIC
556 depends on X86_64 || (X86_32 && (X86_UP_APIC || ((X86_VISWS || SMP) && !X86_VOYAGER) || X86_GENERICARCH))
560 depends on X86_64 || (X86_32 && (X86_UP_IOAPIC || (SMP && !(X86_VISWS || X86_VOYAGER)) || X86_GENERICARCH))
562 config X86_VISWS_APIC
564 depends on X86_32 && X86_VISWS
567 bool "Machine Check Exception"
568 depends on !X86_VOYAGER
570 Machine Check Exception support allows the processor to notify the
571 kernel if it detects a problem (e.g. overheating, component failure).
572 The action the kernel takes depends on the severity of the problem,
573 ranging from a warning message on the console, to halting the machine.
574 Your processor must be a Pentium or newer to support this - check the
575 flags in /proc/cpuinfo for mce. Note that some older Pentium systems
576 have a design flaw which leads to false MCE events - hence MCE is
577 disabled on all P5 processors, unless explicitly enabled with "mce"
578 as a boot argument. Similarly, if MCE is built in and creates a
579 problem on some new non-standard machine, you can boot with "nomce"
580 to disable it. MCE support simply ignores non-MCE processors like
581 the 386 and 486, so nearly everyone can say Y here.
585 prompt "Intel MCE features"
586 depends on X86_64 && X86_MCE && X86_LOCAL_APIC
588 Additional support for intel specific MCE features such as
593 prompt "AMD MCE features"
594 depends on X86_64 && X86_MCE && X86_LOCAL_APIC
596 Additional support for AMD specific MCE features such as
597 the DRAM Error Threshold.
599 config X86_MCE_NONFATAL
600 tristate "Check for non-fatal errors on AMD Athlon/Duron / Intel Pentium 4"
601 depends on X86_32 && X86_MCE
603 Enabling this feature starts a timer that triggers every 5 seconds which
604 will look at the machine check registers to see if anything happened.
605 Non-fatal problems automatically get corrected (but still logged).
606 Disable this if you don't want to see these messages.
607 Seeing the messages this option prints out may be indicative of dying
608 or out-of-spec (ie, overclocked) hardware.
609 This option only does something on certain CPUs.
610 (AMD Athlon/Duron and Intel Pentium 4)
612 config X86_MCE_P4THERMAL
613 bool "check for P4 thermal throttling interrupt."
614 depends on X86_32 && X86_MCE && (X86_UP_APIC || SMP) && !X86_VISWS
616 Enabling this feature will cause a message to be printed when the P4
617 enters thermal throttling.
620 bool "Enable VM86 support" if EMBEDDED
624 This option is required by programs like DOSEMU to run 16-bit legacy
625 code on X86 processors. It also may be needed by software like
626 XFree86 to initialize some video cards via BIOS. Disabling this
627 option saves about 6k.
630 tristate "Toshiba Laptop support"
633 This adds a driver to safely access the System Management Mode of
634 the CPU on Toshiba portables with a genuine Toshiba BIOS. It does
635 not work on models with a Phoenix BIOS. The System Management Mode
636 is used to set the BIOS and power saving options on Toshiba portables.
638 For information on utilities to make use of this driver see the
639 Toshiba Linux utilities web site at:
640 <http://www.buzzard.org.uk/toshiba/>.
642 Say Y if you intend to run this kernel on a Toshiba portable.
646 tristate "Dell laptop support"
648 This adds a driver to safely access the System Management Mode
649 of the CPU on the Dell Inspiron 8000. The System Management Mode
650 is used to read cpu temperature and cooling fan status and to
651 control the fans on the I8K portables.
653 This driver has been tested only on the Inspiron 8000 but it may
654 also work with other Dell laptops. You can force loading on other
655 models by passing the parameter `force=1' to the module. Use at
658 For information on utilities to make use of this driver see the
659 I8K Linux utilities web site at:
660 <http://people.debian.org/~dz/i8k/>
662 Say Y if you intend to run this kernel on a Dell Inspiron 8000.
665 config X86_REBOOTFIXUPS
667 prompt "Enable X86 board specific fixups for reboot"
668 depends on X86_32 && X86
670 This enables chipset and/or board specific fixups to be done
671 in order to get reboot to work correctly. This is only needed on
672 some combinations of hardware and BIOS. The symptom, for which
673 this config is intended, is when reboot ends with a stalled/hung
676 Currently, the only fixup is for the Geode machines using
677 CS5530A and CS5536 chipsets and the RDC R-321x SoC.
679 Say Y if you want to enable the fixup. Currently, it's safe to
680 enable this option even if you don't need it.
684 tristate "/dev/cpu/microcode - Intel IA32 CPU microcode support"
687 If you say Y here, you will be able to update the microcode on
688 Intel processors in the IA32 family, e.g. Pentium Pro, Pentium II,
689 Pentium III, Pentium 4, Xeon etc. You will obviously need the
690 actual microcode binary data itself which is not shipped with the
693 For latest news and information on obtaining all the required
694 ingredients for this driver, check:
695 <http://www.urbanmyth.org/microcode/>.
697 To compile this driver as a module, choose M here: the
698 module will be called microcode.
700 config MICROCODE_OLD_INTERFACE
705 tristate "/dev/cpu/*/msr - Model-specific register support"
707 This device gives privileged processes access to the x86
708 Model-Specific Registers (MSRs). It is a character device with
709 major 202 and minors 0 to 31 for /dev/cpu/0/msr to /dev/cpu/31/msr.
710 MSR accesses are directed to a specific CPU on multi-processor
714 tristate "/dev/cpu/*/cpuid - CPU information support"
716 This device gives processes access to the x86 CPUID instruction to
717 be executed on a specific processor. It is a character device
718 with major 203 and minors 0 to 31 for /dev/cpu/0/cpuid to
722 prompt "High Memory Support"
723 default HIGHMEM4G if !X86_NUMAQ
724 default HIGHMEM64G if X86_NUMAQ
729 depends on !X86_NUMAQ
731 Linux can use up to 64 Gigabytes of physical memory on x86 systems.
732 However, the address space of 32-bit x86 processors is only 4
733 Gigabytes large. That means that, if you have a large amount of
734 physical memory, not all of it can be "permanently mapped" by the
735 kernel. The physical memory that's not permanently mapped is called
738 If you are compiling a kernel which will never run on a machine with
739 more than 1 Gigabyte total physical RAM, answer "off" here (default
740 choice and suitable for most users). This will result in a "3GB/1GB"
741 split: 3GB are mapped so that each process sees a 3GB virtual memory
742 space and the remaining part of the 4GB virtual memory space is used
743 by the kernel to permanently map as much physical memory as
746 If the machine has between 1 and 4 Gigabytes physical RAM, then
749 If more than 4 Gigabytes is used then answer "64GB" here. This
750 selection turns Intel PAE (Physical Address Extension) mode on.
751 PAE implements 3-level paging on IA32 processors. PAE is fully
752 supported by Linux, PAE mode is implemented on all recent Intel
753 processors (Pentium Pro and better). NOTE: If you say "64GB" here,
754 then the kernel will not boot on CPUs that don't support PAE!
756 The actual amount of total physical memory will either be
757 auto detected or can be forced by using a kernel command line option
758 such as "mem=256M". (Try "man bootparam" or see the documentation of
759 your boot loader (lilo or loadlin) about how to pass options to the
760 kernel at boot time.)
762 If unsure, say "off".
766 depends on !X86_NUMAQ
768 Select this if you have a 32-bit processor and between 1 and 4
769 gigabytes of physical RAM.
773 depends on !M386 && !M486
776 Select this if you have a 32-bit processor and more than 4
777 gigabytes of physical RAM.
782 depends on EXPERIMENTAL
783 prompt "Memory split" if EMBEDDED
787 Select the desired split between kernel and user memory.
789 If the address range available to the kernel is less than the
790 physical memory installed, the remaining memory will be available
791 as "high memory". Accessing high memory is a little more costly
792 than low memory, as it needs to be mapped into the kernel first.
793 Note that increasing the kernel address space limits the range
794 available to user programs, making the address space there
795 tighter. Selecting anything other than the default 3G/1G split
796 will also likely make your kernel incompatible with binary-only
799 If you are not absolutely sure what you are doing, leave this
803 bool "3G/1G user/kernel split"
804 config VMSPLIT_3G_OPT
806 bool "3G/1G user/kernel split (for full 1G low memory)"
808 bool "2G/2G user/kernel split"
809 config VMSPLIT_2G_OPT
811 bool "2G/2G user/kernel split (for full 2G low memory)"
813 bool "1G/3G user/kernel split"
818 default 0xB0000000 if VMSPLIT_3G_OPT
819 default 0x80000000 if VMSPLIT_2G
820 default 0x78000000 if VMSPLIT_2G_OPT
821 default 0x40000000 if VMSPLIT_1G
827 depends on X86_32 && (HIGHMEM64G || HIGHMEM4G)
831 prompt "PAE (Physical Address Extension) Support"
832 depends on X86_32 && !HIGHMEM4G
833 select RESOURCES_64BIT
835 PAE is required for NX support, and furthermore enables
836 larger swapspace support for non-overcommit purposes. It
837 has the cost of more pagetable lookup overhead, and also
838 consumes more pagetable space per process.
840 # Common NUMA Features
842 bool "Numa Memory Allocation and Scheduler Support (EXPERIMENTAL)"
844 depends on X86_64 || (X86_32 && HIGHMEM64G && (X86_NUMAQ || (X86_SUMMIT || X86_GENERICARCH) && ACPI) && EXPERIMENTAL)
846 default y if (X86_NUMAQ || X86_SUMMIT)
848 Enable NUMA (Non Uniform Memory Access) support.
849 The kernel will try to allocate memory used by a CPU on the
850 local memory controller of the CPU and add some more
851 NUMA awareness to the kernel.
853 For i386 this is currently highly experimental and should be only
854 used for kernel development. It might also cause boot failures.
855 For x86_64 this is recommended on all multiprocessor Opteron systems.
856 If the system is EM64T, you should say N unless your system is
859 comment "NUMA (Summit) requires SMP, 64GB highmem support, ACPI"
860 depends on X86_32 && X86_SUMMIT && (!HIGHMEM64G || !ACPI)
864 prompt "Old style AMD Opteron NUMA detection"
865 depends on X86_64 && NUMA && PCI
867 Enable K8 NUMA node topology detection. You should say Y here if
868 you have a multi processor AMD K8 system. This uses an old
869 method to read the NUMA configuration directly from the builtin
870 Northbridge of Opteron. It is recommended to use X86_64_ACPI_NUMA
871 instead, which also takes priority if both are compiled in.
873 config X86_64_ACPI_NUMA
875 prompt "ACPI NUMA detection"
876 depends on X86_64 && NUMA && ACPI && PCI
879 Enable ACPI SRAT based node topology detection.
882 bool "NUMA emulation"
883 depends on X86_64 && NUMA
885 Enable NUMA emulation. A flat machine will be split
886 into virtual nodes when booted with "numa=fake=N", where N is the
887 number of nodes. This is only useful for debugging.
892 default "6" if X86_64
893 default "4" if X86_NUMAQ
895 depends on NEED_MULTIPLE_NODES
897 config HAVE_ARCH_BOOTMEM_NODE
899 depends on X86_32 && NUMA
901 config ARCH_HAVE_MEMORY_PRESENT
903 depends on X86_32 && DISCONTIGMEM
905 config NEED_NODE_MEMMAP_SIZE
907 depends on X86_32 && (DISCONTIGMEM || SPARSEMEM)
909 config HAVE_ARCH_ALLOC_REMAP
911 depends on X86_32 && NUMA
913 config ARCH_FLATMEM_ENABLE
915 depends on X86_32 && ARCH_SELECT_MEMORY_MODEL && X86_PC && !NUMA
917 config ARCH_DISCONTIGMEM_ENABLE
919 depends on NUMA && X86_32
921 config ARCH_DISCONTIGMEM_DEFAULT
923 depends on NUMA && X86_32
925 config ARCH_SPARSEMEM_DEFAULT
929 config ARCH_SPARSEMEM_ENABLE
931 depends on X86_64 || NUMA || (EXPERIMENTAL && X86_PC)
932 select SPARSEMEM_STATIC if X86_32
933 select SPARSEMEM_VMEMMAP_ENABLE if X86_64
935 config ARCH_SELECT_MEMORY_MODEL
937 depends on ARCH_SPARSEMEM_ENABLE
939 config ARCH_MEMORY_PROBE
941 depends on MEMORY_HOTPLUG
946 bool "Allocate 3rd-level pagetables from highmem"
947 depends on X86_32 && (HIGHMEM4G || HIGHMEM64G)
949 The VM uses one page table entry for each page of physical memory.
950 For systems with a lot of RAM, this can be wasteful of precious
951 low memory. Setting this option will put user-space page table
952 entries in high memory.
954 config MATH_EMULATION
956 prompt "Math emulation" if X86_32
958 Linux can emulate a math coprocessor (used for floating point
959 operations) if you don't have one. 486DX and Pentium processors have
960 a math coprocessor built in, 486SX and 386 do not, unless you added
961 a 487DX or 387, respectively. (The messages during boot time can
962 give you some hints here ["man dmesg"].) Everyone needs either a
963 coprocessor or this emulation.
965 If you don't have a math coprocessor, you need to say Y here; if you
966 say Y here even though you have a coprocessor, the coprocessor will
967 be used nevertheless. (This behavior can be changed with the kernel
968 command line option "no387", which comes handy if your coprocessor
969 is broken. Try "man bootparam" or see the documentation of your boot
970 loader (lilo or loadlin) about how to pass options to the kernel at
971 boot time.) This means that it is a good idea to say Y here if you
972 intend to use this kernel on different machines.
974 More information about the internals of the Linux math coprocessor
975 emulation can be found in <file:arch/x86/math-emu/README>.
977 If you are not sure, say Y; apart from resulting in a 66 KB bigger
978 kernel, it won't hurt.
981 bool "MTRR (Memory Type Range Register) support"
983 On Intel P6 family processors (Pentium Pro, Pentium II and later)
984 the Memory Type Range Registers (MTRRs) may be used to control
985 processor access to memory ranges. This is most useful if you have
986 a video (VGA) card on a PCI or AGP bus. Enabling write-combining
987 allows bus write transfers to be combined into a larger transfer
988 before bursting over the PCI/AGP bus. This can increase performance
989 of image write operations 2.5 times or more. Saying Y here creates a
990 /proc/mtrr file which may be used to manipulate your processor's
991 MTRRs. Typically the X server should use this.
993 This code has a reasonably generic interface so that similar
994 control registers on other processors can be easily supported
997 The Cyrix 6x86, 6x86MX and M II processors have Address Range
998 Registers (ARRs) which provide a similar functionality to MTRRs. For
999 these, the ARRs are used to emulate the MTRRs.
1000 The AMD K6-2 (stepping 8 and above) and K6-3 processors have two
1001 MTRRs. The Centaur C6 (WinChip) has 8 MCRs, allowing
1002 write-combining. All of these processors are supported by this code
1003 and it makes sense to say Y here if you have one of them.
1005 Saying Y here also fixes a problem with buggy SMP BIOSes which only
1006 set the MTRRs for the boot CPU and not for the secondary CPUs. This
1007 can lead to all sorts of problems, so it's good to say Y here.
1009 You can safely say Y even if your machine doesn't have MTRRs, you'll
1010 just add about 9 KB to your kernel.
1012 See <file:Documentation/mtrr.txt> for more information.
1016 prompt "EFI runtime service support"
1019 This enables the kernel to use EFI runtime services that are
1020 available (such as the EFI variable services).
1022 This option is only useful on systems that have EFI firmware.
1023 In addition, you should use the latest ELILO loader available
1024 at <http://elilo.sourceforge.net> in order to take advantage
1025 of EFI runtime services. However, even with this option, the
1026 resultant kernel should continue to boot on existing non-EFI
1031 prompt "Enable kernel irq balancing"
1032 depends on X86_32 && SMP && X86_IO_APIC
1034 The default yes will allow the kernel to do irq load balancing.
1035 Saying no will keep the kernel from doing irq load balancing.
1039 prompt "Enable seccomp to safely compute untrusted bytecode"
1042 This kernel feature is useful for number crunching applications
1043 that may need to compute untrusted bytecode during their
1044 execution. By using pipes or other transports made available to
1045 the process as file descriptors supporting the read/write
1046 syscalls, it's possible to isolate those applications in
1047 their own address space using seccomp. Once seccomp is
1048 enabled via /proc/<pid>/seccomp, it cannot be disabled
1049 and the task is only allowed to execute a few safe syscalls
1050 defined by each seccomp mode.
1052 If unsure, say Y. Only embedded should say N here.
1054 config CC_STACKPROTECTOR
1055 bool "Enable -fstack-protector buffer overflow detection (EXPERIMENTAL)"
1056 depends on X86_64 && EXPERIMENTAL
1058 This option turns on the -fstack-protector GCC feature. This
1059 feature puts, at the beginning of critical functions, a canary
1060 value on the stack just before the return address, and validates
1061 the value just before actually returning. Stack based buffer
1062 overflows (that need to overwrite this return address) now also
1063 overwrite the canary, which gets detected and the attack is then
1064 neutralized via a kernel panic.
1066 This feature requires gcc version 4.2 or above, or a distribution
1067 gcc with the feature backported. Older versions are automatically
1068 detected and for those versions, this configuration option is ignored.
1070 config CC_STACKPROTECTOR_ALL
1071 bool "Use stack-protector for all functions"
1072 depends on CC_STACKPROTECTOR
1074 Normally, GCC only inserts the canary value protection for
1075 functions that use large-ish on-stack buffers. By enabling
1076 this option, GCC will be asked to do this for ALL functions.
1078 source kernel/Kconfig.hz
1081 bool "kexec system call"
1083 kexec is a system call that implements the ability to shutdown your
1084 current kernel, and to start another kernel. It is like a reboot
1085 but it is independent of the system firmware. And like a reboot
1086 you can start any kernel with it, not just Linux.
1088 The name comes from the similarity to the exec system call.
1090 It is an ongoing process to be certain the hardware in a machine
1091 is properly shutdown, so do not be surprised if this code does not
1092 initially work for you. It may help to enable device hotplugging
1093 support. As of this writing the exact hardware interface is
1094 strongly in flux, so no good recommendation can be made.
1097 bool "kernel crash dumps (EXPERIMENTAL)"
1098 depends on EXPERIMENTAL
1099 depends on X86_64 || (X86_32 && HIGHMEM)
1101 Generate crash dump after being started by kexec.
1102 This should be normally only set in special crash dump kernels
1103 which are loaded in the main kernel with kexec-tools into
1104 a specially reserved region and then later executed after
1105 a crash by kdump/kexec. The crash dump kernel must be compiled
1106 to a memory address not used by the main kernel or BIOS using
1107 PHYSICAL_START, or it must be built as a relocatable image
1108 (CONFIG_RELOCATABLE=y).
1109 For more details see Documentation/kdump/kdump.txt
1111 config PHYSICAL_START
1112 hex "Physical address where the kernel is loaded" if (EMBEDDED || CRASH_DUMP)
1113 default "0x1000000" if X86_NUMAQ
1114 default "0x200000" if X86_64
1117 This gives the physical address where the kernel is loaded.
1119 If kernel is a not relocatable (CONFIG_RELOCATABLE=n) then
1120 bzImage will decompress itself to above physical address and
1121 run from there. Otherwise, bzImage will run from the address where
1122 it has been loaded by the boot loader and will ignore above physical
1125 In normal kdump cases one does not have to set/change this option
1126 as now bzImage can be compiled as a completely relocatable image
1127 (CONFIG_RELOCATABLE=y) and be used to load and run from a different
1128 address. This option is mainly useful for the folks who don't want
1129 to use a bzImage for capturing the crash dump and want to use a
1130 vmlinux instead. vmlinux is not relocatable hence a kernel needs
1131 to be specifically compiled to run from a specific memory area
1132 (normally a reserved region) and this option comes handy.
1134 So if you are using bzImage for capturing the crash dump, leave
1135 the value here unchanged to 0x100000 and set CONFIG_RELOCATABLE=y.
1136 Otherwise if you plan to use vmlinux for capturing the crash dump
1137 change this value to start of the reserved region (Typically 16MB
1138 0x1000000). In other words, it can be set based on the "X" value as
1139 specified in the "crashkernel=YM@XM" command line boot parameter
1140 passed to the panic-ed kernel. Typically this parameter is set as
1141 crashkernel=64M@16M. Please take a look at
1142 Documentation/kdump/kdump.txt for more details about crash dumps.
1144 Usage of bzImage for capturing the crash dump is recommended as
1145 one does not have to build two kernels. Same kernel can be used
1146 as production kernel and capture kernel. Above option should have
1147 gone away after relocatable bzImage support is introduced. But it
1148 is present because there are users out there who continue to use
1149 vmlinux for dump capture. This option should go away down the
1152 Don't change this unless you know what you are doing.
1155 bool "Build a relocatable kernel (EXPERIMENTAL)"
1156 depends on EXPERIMENTAL
1158 This builds a kernel image that retains relocation information
1159 so it can be loaded someplace besides the default 1MB.
1160 The relocations tend to make the kernel binary about 10% larger,
1161 but are discarded at runtime.
1163 One use is for the kexec on panic case where the recovery kernel
1164 must live at a different physical address than the primary
1167 Note: If CONFIG_RELOCATABLE=y, then the kernel runs from the address
1168 it has been loaded at and the compile time physical address
1169 (CONFIG_PHYSICAL_START) is ignored.
1171 config PHYSICAL_ALIGN
1173 prompt "Alignment value to which kernel should be aligned" if X86_32
1174 default "0x100000" if X86_32
1175 default "0x200000" if X86_64
1176 range 0x2000 0x400000
1178 This value puts the alignment restrictions on physical address
1179 where kernel is loaded and run from. Kernel is compiled for an
1180 address which meets above alignment restriction.
1182 If bootloader loads the kernel at a non-aligned address and
1183 CONFIG_RELOCATABLE is set, kernel will move itself to nearest
1184 address aligned to above value and run from there.
1186 If bootloader loads the kernel at a non-aligned address and
1187 CONFIG_RELOCATABLE is not set, kernel will ignore the run time
1188 load address and decompress itself to the address it has been
1189 compiled for and run from there. The address for which kernel is
1190 compiled already meets above alignment restrictions. Hence the
1191 end result is that kernel runs from a physical address meeting
1192 above alignment restrictions.
1194 Don't change this unless you know what you are doing.
1197 bool "Support for suspend on SMP and hot-pluggable CPUs (EXPERIMENTAL)"
1198 depends on SMP && HOTPLUG && EXPERIMENTAL && !X86_VOYAGER
1200 Say Y here to experiment with turning CPUs off and on, and to
1201 enable suspend on SMP systems. CPUs can be controlled through
1202 /sys/devices/system/cpu.
1203 Say N if you want to disable CPU hotplug and don't need to
1208 prompt "Compat VDSO support"
1209 depends on X86_32 || IA32_EMULATION
1211 Map the 32-bit VDSO to the predictable old-style address too.
1213 Say N here if you are running a sufficiently recent glibc
1214 version (2.3.3 or later), to remove the high-mapped
1215 VDSO mapping and to exclusively use the randomized VDSO.
1221 config ARCH_ENABLE_MEMORY_HOTPLUG
1223 depends on X86_64 || (X86_32 && HIGHMEM)
1225 config HAVE_ARCH_EARLY_PFN_TO_NID
1229 menu "Power management options"
1230 depends on !X86_VOYAGER
1232 config ARCH_HIBERNATION_HEADER
1234 depends on X86_64 && HIBERNATION
1236 source "kernel/power/Kconfig"
1238 source "drivers/acpi/Kconfig"
1243 depends on APM || APM_MODULE
1246 tristate "APM (Advanced Power Management) BIOS support"
1247 depends on X86_32 && PM_SLEEP && !X86_VISWS
1249 APM is a BIOS specification for saving power using several different
1250 techniques. This is mostly useful for battery powered laptops with
1251 APM compliant BIOSes. If you say Y here, the system time will be
1252 reset after a RESUME operation, the /proc/apm device will provide
1253 battery status information, and user-space programs will receive
1254 notification of APM "events" (e.g. battery status change).
1256 If you select "Y" here, you can disable actual use of the APM
1257 BIOS by passing the "apm=off" option to the kernel at boot time.
1259 Note that the APM support is almost completely disabled for
1260 machines with more than one CPU.
1262 In order to use APM, you will need supporting software. For location
1263 and more information, read <file:Documentation/pm.txt> and the
1264 Battery Powered Linux mini-HOWTO, available from
1265 <http://www.tldp.org/docs.html#howto>.
1267 This driver does not spin down disk drives (see the hdparm(8)
1268 manpage ("man 8 hdparm") for that), and it doesn't turn off
1269 VESA-compliant "green" monitors.
1271 This driver does not support the TI 4000M TravelMate and the ACER
1272 486/DX4/75 because they don't have compliant BIOSes. Many "green"
1273 desktop machines also don't have compliant BIOSes, and this driver
1274 may cause those machines to panic during the boot phase.
1276 Generally, if you don't have a battery in your machine, there isn't
1277 much point in using this driver and you should say N. If you get
1278 random kernel OOPSes or reboots that don't seem to be related to
1279 anything, try disabling/enabling this option (or disabling/enabling
1282 Some other things you should try when experiencing seemingly random,
1285 1) make sure that you have enough swap space and that it is
1287 2) pass the "no-hlt" option to the kernel
1288 3) switch on floating point emulation in the kernel and pass
1289 the "no387" option to the kernel
1290 4) pass the "floppy=nodma" option to the kernel
1291 5) pass the "mem=4M" option to the kernel (thereby disabling
1292 all but the first 4 MB of RAM)
1293 6) make sure that the CPU is not over clocked.
1294 7) read the sig11 FAQ at <http://www.bitwizard.nl/sig11/>
1295 8) disable the cache from your BIOS settings
1296 9) install a fan for the video card or exchange video RAM
1297 10) install a better fan for the CPU
1298 11) exchange RAM chips
1299 12) exchange the motherboard.
1301 To compile this driver as a module, choose M here: the
1302 module will be called apm.
1306 config APM_IGNORE_USER_SUSPEND
1307 bool "Ignore USER SUSPEND"
1309 This option will ignore USER SUSPEND requests. On machines with a
1310 compliant APM BIOS, you want to say N. However, on the NEC Versa M
1311 series notebooks, it is necessary to say Y because of a BIOS bug.
1313 config APM_DO_ENABLE
1314 bool "Enable PM at boot time"
1316 Enable APM features at boot time. From page 36 of the APM BIOS
1317 specification: "When disabled, the APM BIOS does not automatically
1318 power manage devices, enter the Standby State, enter the Suspend
1319 State, or take power saving steps in response to CPU Idle calls."
1320 This driver will make CPU Idle calls when Linux is idle (unless this
1321 feature is turned off -- see "Do CPU IDLE calls", below). This
1322 should always save battery power, but more complicated APM features
1323 will be dependent on your BIOS implementation. You may need to turn
1324 this option off if your computer hangs at boot time when using APM
1325 support, or if it beeps continuously instead of suspending. Turn
1326 this off if you have a NEC UltraLite Versa 33/C or a Toshiba
1327 T400CDT. This is off by default since most machines do fine without
1331 bool "Make CPU Idle calls when idle"
1333 Enable calls to APM CPU Idle/CPU Busy inside the kernel's idle loop.
1334 On some machines, this can activate improved power savings, such as
1335 a slowed CPU clock rate, when the machine is idle. These idle calls
1336 are made after the idle loop has run for some length of time (e.g.,
1337 333 mS). On some machines, this will cause a hang at boot time or
1338 whenever the CPU becomes idle. (On machines with more than one CPU,
1339 this option does nothing.)
1341 config APM_DISPLAY_BLANK
1342 bool "Enable console blanking using APM"
1344 Enable console blanking using the APM. Some laptops can use this to
1345 turn off the LCD backlight when the screen blanker of the Linux
1346 virtual console blanks the screen. Note that this is only used by
1347 the virtual console screen blanker, and won't turn off the backlight
1348 when using the X Window system. This also doesn't have anything to
1349 do with your VESA-compliant power-saving monitor. Further, this
1350 option doesn't work for all laptops -- it might not turn off your
1351 backlight at all, or it might print a lot of errors to the console,
1352 especially if you are using gpm.
1354 config APM_ALLOW_INTS
1355 bool "Allow interrupts during APM BIOS calls"
1357 Normally we disable external interrupts while we are making calls to
1358 the APM BIOS as a measure to lessen the effects of a badly behaving
1359 BIOS implementation. The BIOS should reenable interrupts if it
1360 needs to. Unfortunately, some BIOSes do not -- especially those in
1361 many of the newer IBM Thinkpads. If you experience hangs when you
1362 suspend, try setting this to Y. Otherwise, say N.
1364 config APM_REAL_MODE_POWER_OFF
1365 bool "Use real mode APM BIOS call to power off"
1367 Use real mode APM BIOS calls to switch off the computer. This is
1368 a work-around for a number of buggy BIOSes. Switch this option on if
1369 your computer crashes instead of powering off properly.
1373 source "arch/x86/kernel/cpu/cpufreq/Kconfig"
1375 source "drivers/cpuidle/Kconfig"
1380 menu "Bus options (PCI etc.)"
1383 bool "PCI support" if !X86_VISWS
1384 depends on !X86_VOYAGER
1386 select ARCH_SUPPORTS_MSI if (X86_LOCAL_APIC && X86_IO_APIC)
1388 Find out whether you have a PCI motherboard. PCI is the name of a
1389 bus system, i.e. the way the CPU talks to the other stuff inside
1390 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
1391 VESA. If you have PCI, say Y, otherwise N.
1394 prompt "PCI access mode"
1395 depends on X86_32 && PCI && !X86_VISWS
1398 On PCI systems, the BIOS can be used to detect the PCI devices and
1399 determine their configuration. However, some old PCI motherboards
1400 have BIOS bugs and may crash if this is done. Also, some embedded
1401 PCI-based systems don't have any BIOS at all. Linux can also try to
1402 detect the PCI hardware directly without using the BIOS.
1404 With this option, you can specify how Linux should detect the
1405 PCI devices. If you choose "BIOS", the BIOS will be used,
1406 if you choose "Direct", the BIOS won't be used, and if you
1407 choose "MMConfig", then PCI Express MMCONFIG will be used.
1408 If you choose "Any", the kernel will try MMCONFIG, then the
1409 direct access method and falls back to the BIOS if that doesn't
1410 work. If unsure, go with the default, which is "Any".
1415 config PCI_GOMMCONFIG
1428 depends on X86_32 && !X86_VISWS && PCI && (PCI_GOBIOS || PCI_GOANY)
1430 # x86-64 doesn't support PCI BIOS access from long mode so always go direct.
1433 depends on PCI && (X86_64 || (PCI_GODIRECT || PCI_GOANY) || X86_VISWS)
1437 depends on X86_32 && PCI && ACPI && (PCI_GOMMCONFIG || PCI_GOANY)
1444 bool "Support mmconfig PCI config space access"
1445 depends on X86_64 && PCI && ACPI
1448 bool "Support for DMA Remapping Devices (EXPERIMENTAL)"
1449 depends on X86_64 && PCI_MSI && ACPI && EXPERIMENTAL
1451 DMA remapping (DMAR) devices support enables independent address
1452 translations for Direct Memory Access (DMA) from devices.
1453 These DMA remapping devices are reported via ACPI tables
1454 and include PCI device scope covered by these DMA
1459 prompt "Support for Graphics workaround"
1462 Current Graphics drivers tend to use physical address
1463 for DMA and avoid using DMA APIs. Setting this config
1464 option permits the IOMMU driver to set a unity map for
1465 all the OS-visible memory. Hence the driver can continue
1466 to use physical addresses for DMA.
1468 config DMAR_FLOPPY_WA
1472 Floppy disk drivers are know to bypass DMA API calls
1473 thereby failing to work when IOMMU is enabled. This
1474 workaround will setup a 1:1 mapping for the first
1475 16M to make floppy (an ISA device) work.
1477 source "drivers/pci/pcie/Kconfig"
1479 source "drivers/pci/Kconfig"
1481 # x86_64 have no ISA slots, but do have ISA-style DMA.
1489 depends on !(X86_VOYAGER || X86_VISWS)
1491 Find out whether you have ISA slots on your motherboard. ISA is the
1492 name of a bus system, i.e. the way the CPU talks to the other stuff
1493 inside your box. Other bus systems are PCI, EISA, MicroChannel
1494 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
1495 newer boards don't support it. If you have ISA, say Y, otherwise N.
1501 The Extended Industry Standard Architecture (EISA) bus was
1502 developed as an open alternative to the IBM MicroChannel bus.
1504 The EISA bus provided some of the features of the IBM MicroChannel
1505 bus while maintaining backward compatibility with cards made for
1506 the older ISA bus. The EISA bus saw limited use between 1988 and
1507 1995 when it was made obsolete by the PCI bus.
1509 Say Y here if you are building a kernel for an EISA-based machine.
1513 source "drivers/eisa/Kconfig"
1516 bool "MCA support" if !(X86_VISWS || X86_VOYAGER)
1517 default y if X86_VOYAGER
1519 MicroChannel Architecture is found in some IBM PS/2 machines and
1520 laptops. It is a bus system similar to PCI or ISA. See
1521 <file:Documentation/mca.txt> (and especially the web page given
1522 there) before attempting to build an MCA bus kernel.
1524 source "drivers/mca/Kconfig"
1527 tristate "NatSemi SCx200 support"
1528 depends on !X86_VOYAGER
1530 This provides basic support for National Semiconductor's
1531 (now AMD's) Geode processors. The driver probes for the
1532 PCI-IDs of several on-chip devices, so its a good dependency
1533 for other scx200_* drivers.
1535 If compiled as a module, the driver is named scx200.
1537 config SCx200HR_TIMER
1538 tristate "NatSemi SCx200 27MHz High-Resolution Timer Support"
1539 depends on SCx200 && GENERIC_TIME
1542 This driver provides a clocksource built upon the on-chip
1543 27MHz high-resolution timer. Its also a workaround for
1544 NSC Geode SC-1100's buggy TSC, which loses time when the
1545 processor goes idle (as is done by the scheduler). The
1546 other workaround is idle=poll boot option.
1548 config GEODE_MFGPT_TIMER
1550 prompt "Geode Multi-Function General Purpose Timer (MFGPT) events"
1551 depends on MGEODE_LX && GENERIC_TIME && GENERIC_CLOCKEVENTS
1553 This driver provides a clock event source based on the MFGPT
1554 timer(s) in the CS5535 and CS5536 companion chip for the geode.
1555 MFGPTs have a better resolution and max interval than the
1556 generic PIT, and are suitable for use as high-res timers.
1562 depends on AGP_AMD64 || (X86_64 && (GART_IOMMU || (PCI && NUMA)))
1564 source "drivers/pcmcia/Kconfig"
1566 source "drivers/pci/hotplug/Kconfig"
1571 menu "Executable file formats / Emulations"
1573 source "fs/Kconfig.binfmt"
1575 config IA32_EMULATION
1576 bool "IA32 Emulation"
1578 select COMPAT_BINFMT_ELF
1580 Include code to run 32-bit programs under a 64-bit kernel. You should
1581 likely turn this on, unless you're 100% sure that you don't have any
1582 32-bit programs left.
1585 tristate "IA32 a.out support"
1586 depends on IA32_EMULATION && ARCH_SUPPORTS_AOUT
1588 Support old a.out binaries in the 32bit emulation.
1592 depends on IA32_EMULATION
1594 config COMPAT_FOR_U64_ALIGNMENT
1598 config SYSVIPC_COMPAT
1600 depends on X86_64 && COMPAT && SYSVIPC
1605 source "net/Kconfig"
1607 source "drivers/Kconfig"
1609 source "drivers/firmware/Kconfig"
1613 source "arch/x86/Kconfig.debug"
1615 source "security/Kconfig"
1617 source "crypto/Kconfig"
1619 source "arch/x86/kvm/Kconfig"
1621 source "lib/Kconfig"
projects / linux-2.6 / blob