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 select HAVE_KRETPROBES
25 select HAVE_KVM if ((X86_32 && !X86_VOYAGER && !X86_VISWS && !X86_NUMAQ) || X86_64)
28 config GENERIC_LOCKBREAK
34 config GENERIC_CMOS_UPDATE
37 config CLOCKSOURCE_WATCHDOG
40 config GENERIC_CLOCKEVENTS
43 config GENERIC_CLOCKEVENTS_BROADCAST
45 depends on X86_64 || (X86_32 && X86_LOCAL_APIC)
47 config LOCKDEP_SUPPORT
50 config STACKTRACE_SUPPORT
53 config HAVE_LATENCYTOP_SUPPORT
56 config FAST_CMPXCHG_LOCAL
69 config GENERIC_ISA_DMA
79 config GENERIC_HWEIGHT
85 config ARCH_MAY_HAVE_PC_FDC
91 config RWSEM_GENERIC_SPINLOCK
94 config RWSEM_XCHGADD_ALGORITHM
97 config ARCH_HAS_ILOG2_U32
100 config ARCH_HAS_ILOG2_U64
103 config ARCH_HAS_CPU_IDLE_WAIT
106 config GENERIC_CALIBRATE_DELAY
109 config GENERIC_TIME_VSYSCALL
113 config ARCH_HAS_CPU_RELAX
116 config HAVE_SETUP_PER_CPU_AREA
119 config ARCH_HIBERNATION_POSSIBLE
121 depends on !SMP || !X86_VOYAGER
123 config ARCH_SUSPEND_POSSIBLE
125 depends on !X86_VOYAGER
131 config ARCH_POPULATES_NODE_MAP
138 config ARCH_SUPPORTS_AOUT
141 # Use the generic interrupt handling code in kernel/irq/:
142 config GENERIC_HARDIRQS
146 config GENERIC_IRQ_PROBE
150 config GENERIC_PENDING_IRQ
152 depends on GENERIC_HARDIRQS && SMP
157 depends on SMP && ((X86_32 && !X86_VOYAGER) || X86_64)
162 depends on X86_32 && SMP
166 depends on X86_64 && SMP
171 depends on (X86_32 && !(X86_VISWS || X86_VOYAGER)) || (X86_64 && !MK8)
174 config X86_BIOS_REBOOT
176 depends on X86_32 && !(X86_VISWS || X86_VOYAGER)
179 config X86_TRAMPOLINE
181 depends on X86_SMP || (X86_VOYAGER && SMP)
186 source "init/Kconfig"
188 menu "Processor type and features"
190 source "kernel/time/Kconfig"
193 bool "Symmetric multi-processing support"
195 This enables support for systems with more than one CPU. If you have
196 a system with only one CPU, like most personal computers, say N. If
197 you have a system with more than one CPU, say Y.
199 If you say N here, the kernel will run on single and multiprocessor
200 machines, but will use only one CPU of a multiprocessor machine. If
201 you say Y here, the kernel will run on many, but not all,
202 singleprocessor machines. On a singleprocessor machine, the kernel
203 will run faster if you say N here.
205 Note that if you say Y here and choose architecture "586" or
206 "Pentium" under "Processor family", the kernel will not work on 486
207 architectures. Similarly, multiprocessor kernels for the "PPro"
208 architecture may not work on all Pentium based boards.
210 People using multiprocessor machines who say Y here should also say
211 Y to "Enhanced Real Time Clock Support", below. The "Advanced Power
212 Management" code will be disabled if you say Y here.
214 See also <file:Documentation/i386/IO-APIC.txt>,
215 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
216 <http://www.tldp.org/docs.html#howto>.
218 If you don't know what to do here, say N.
221 prompt "Subarchitecture Type"
227 Choose this option if your computer is a standard PC or compatible.
233 Select this for an AMD Elan processor.
235 Do not use this option for K6/Athlon/Opteron processors!
237 If unsure, choose "PC-compatible" instead.
242 select SMP if !BROKEN
244 Voyager is an MCA-based 32-way capable SMP architecture proprietary
245 to NCR Corp. Machine classes 345x/35xx/4100/51xx are Voyager-based.
249 If you do not specifically know you have a Voyager based machine,
250 say N here, otherwise the kernel you build will not be bootable.
253 bool "NUMAQ (IBM/Sequent)"
258 This option is used for getting Linux to run on a (IBM/Sequent) NUMA
259 multiquad box. This changes the way that processors are bootstrapped,
260 and uses Clustered Logical APIC addressing mode instead of Flat Logical.
261 You will need a new lynxer.elf file to flash your firmware with - send
262 email to <Martin.Bligh@us.ibm.com>.
265 bool "Summit/EXA (IBM x440)"
266 depends on X86_32 && SMP
268 This option is needed for IBM systems that use the Summit/EXA chipset.
269 In particular, it is needed for the x440.
271 If you don't have one of these computers, you should say N here.
272 If you want to build a NUMA kernel, you must select ACPI.
275 bool "Support for other sub-arch SMP systems with more than 8 CPUs"
276 depends on X86_32 && SMP
278 This option is needed for the systems that have more than 8 CPUs
279 and if the system is not of any sub-arch type above.
281 If you don't have such a system, you should say N here.
284 bool "SGI 320/540 (Visual Workstation)"
287 The SGI Visual Workstation series is an IA32-based workstation
288 based on SGI systems chips with some legacy PC hardware attached.
290 Say Y here to create a kernel to run on the SGI 320 or 540.
292 A kernel compiled for the Visual Workstation will not run on PCs
293 and vice versa. See <file:Documentation/sgi-visws.txt> for details.
295 config X86_GENERICARCH
296 bool "Generic architecture (Summit, bigsmp, ES7000, default)"
299 This option compiles in the Summit, bigsmp, ES7000, default subarchitectures.
300 It is intended for a generic binary kernel.
301 If you want a NUMA kernel, select ACPI. We need SRAT for NUMA.
304 bool "Support for Unisys ES7000 IA32 series"
305 depends on X86_32 && SMP
307 Support for Unisys ES7000 systems. Say 'Y' here if this kernel is
308 supposed to run on an IA32-based Unisys ES7000 system.
309 Only choose this option if you have such a system, otherwise you
313 bool "RDC R-321x SoC"
316 select X86_REBOOTFIXUPS
321 This option is needed for RDC R-321x system-on-chip, also known
323 If you don't have one of these chips, you should say N here.
326 bool "Support for ScaleMP vSMP"
327 depends on X86_64 && PCI
329 Support for ScaleMP vSMP systems. Say 'Y' here if this kernel is
330 supposed to run on these EM64T-based machines. Only choose this option
331 if you have one of these machines.
335 config SCHED_NO_NO_OMIT_FRAME_POINTER
337 prompt "Single-depth WCHAN output"
340 Calculate simpler /proc/<PID>/wchan values. If this option
341 is disabled then wchan values will recurse back to the
342 caller function. This provides more accurate wchan values,
343 at the expense of slightly more scheduling overhead.
345 If in doubt, say "Y".
347 menuconfig PARAVIRT_GUEST
348 bool "Paravirtualized guest support"
350 Say Y here to get to see options related to running Linux under
351 various hypervisors. This option alone does not add any kernel code.
353 If you say N, all options in this submenu will be skipped and disabled.
357 source "arch/x86/xen/Kconfig"
360 bool "VMI Guest support"
363 depends on !(X86_VISWS || X86_VOYAGER)
365 VMI provides a paravirtualized interface to the VMware ESX server
366 (it could be used by other hypervisors in theory too, but is not
367 at the moment), by linking the kernel to a GPL-ed ROM module
368 provided by the hypervisor.
370 source "arch/x86/lguest/Kconfig"
373 bool "Enable paravirtualization code"
374 depends on !(X86_VISWS || X86_VOYAGER)
376 This changes the kernel so it can modify itself when it is run
377 under a hypervisor, potentially improving performance significantly
378 over full virtualization. However, when run without a hypervisor
379 the kernel is theoretically slower and slightly larger.
385 depends on X86_32 && ACPI && NUMA && (X86_SUMMIT || X86_GENERICARCH)
388 config HAVE_ARCH_PARSE_SRAT
392 config X86_SUMMIT_NUMA
394 depends on X86_32 && NUMA && (X86_SUMMIT || X86_GENERICARCH)
396 config X86_CYCLONE_TIMER
398 depends on X86_32 && X86_SUMMIT || X86_GENERICARCH
400 config ES7000_CLUSTERED_APIC
402 depends on SMP && X86_ES7000 && MPENTIUMIII
404 source "arch/x86/Kconfig.cpu"
408 prompt "HPET Timer Support" if X86_32
410 Use the IA-PC HPET (High Precision Event Timer) to manage
411 time in preference to the PIT and RTC, if a HPET is
413 HPET is the next generation timer replacing legacy 8254s.
414 The HPET provides a stable time base on SMP
415 systems, unlike the TSC, but it is more expensive to access,
416 as it is off-chip. You can find the HPET spec at
417 <http://www.intel.com/hardwaredesign/hpetspec.htm>.
419 You can safely choose Y here. However, HPET will only be
420 activated if the platform and the BIOS support this feature.
421 Otherwise the 8254 will be used for timing services.
423 Choose N to continue using the legacy 8254 timer.
425 config HPET_EMULATE_RTC
427 depends on HPET_TIMER && (RTC=y || RTC=m || RTC_DRV_CMOS=m || RTC_DRV_CMOS=y)
429 # Mark as embedded because too many people got it wrong.
430 # The code disables itself when not needed.
432 bool "GART IOMMU support" if EMBEDDED
436 depends on X86_64 && PCI
438 Support for full DMA access of devices with 32bit memory access only
439 on systems with more than 3GB. This is usually needed for USB,
440 sound, many IDE/SATA chipsets and some other devices.
441 Provides a driver for the AMD Athlon64/Opteron/Turion/Sempron GART
442 based hardware IOMMU and a software bounce buffer based IOMMU used
443 on Intel systems and as fallback.
444 The code is only active when needed (enough memory and limited
445 device) unless CONFIG_IOMMU_DEBUG or iommu=force is specified
449 bool "IBM Calgary IOMMU support"
451 depends on X86_64 && PCI && EXPERIMENTAL
453 Support for hardware IOMMUs in IBM's xSeries x366 and x460
454 systems. Needed to run systems with more than 3GB of memory
455 properly with 32-bit PCI devices that do not support DAC
456 (Double Address Cycle). Calgary also supports bus level
457 isolation, where all DMAs pass through the IOMMU. This
458 prevents them from going anywhere except their intended
459 destination. This catches hard-to-find kernel bugs and
460 mis-behaving drivers and devices that do not use the DMA-API
461 properly to set up their DMA buffers. The IOMMU can be
462 turned off at boot time with the iommu=off parameter.
463 Normally the kernel will make the right choice by itself.
466 config CALGARY_IOMMU_ENABLED_BY_DEFAULT
468 prompt "Should Calgary be enabled by default?"
469 depends on CALGARY_IOMMU
471 Should Calgary be enabled by default? if you choose 'y', Calgary
472 will be used (if it exists). If you choose 'n', Calgary will not be
473 used even if it exists. If you choose 'n' and would like to use
474 Calgary anyway, pass 'iommu=calgary' on the kernel command line.
478 def_bool (CALGARY_IOMMU || GART_IOMMU)
480 # need this always selected by IOMMU for the VIA workaround
484 Support for software bounce buffers used on x86-64 systems
485 which don't have a hardware IOMMU (e.g. the current generation
486 of Intel's x86-64 CPUs). Using this PCI devices which can only
487 access 32-bits of memory can be used on systems with more than
488 3 GB of memory. If unsure, say Y.
492 int "Maximum number of CPUs (2-255)"
495 default "32" if X86_NUMAQ || X86_SUMMIT || X86_BIGSMP || X86_ES7000
498 This allows you to specify the maximum number of CPUs which this
499 kernel will support. The maximum supported value is 255 and the
500 minimum value which makes sense is 2.
502 This is purely to save memory - each supported CPU adds
503 approximately eight kilobytes to the kernel image.
506 bool "SMT (Hyperthreading) scheduler support"
507 depends on (X86_64 && SMP) || (X86_32 && X86_HT)
509 SMT scheduler support improves the CPU scheduler's decision making
510 when dealing with Intel Pentium 4 chips with HyperThreading at a
511 cost of slightly increased overhead in some places. If unsure say
516 prompt "Multi-core scheduler support"
517 depends on (X86_64 && SMP) || (X86_32 && X86_HT)
519 Multi-core scheduler support improves the CPU scheduler's decision
520 making when dealing with multi-core CPU chips at a cost of slightly
521 increased overhead in some places. If unsure say N here.
523 source "kernel/Kconfig.preempt"
526 bool "Local APIC support on uniprocessors"
527 depends on X86_32 && !SMP && !(X86_VISWS || X86_VOYAGER || X86_GENERICARCH)
529 A local APIC (Advanced Programmable Interrupt Controller) is an
530 integrated interrupt controller in the CPU. If you have a single-CPU
531 system which has a processor with a local APIC, you can say Y here to
532 enable and use it. If you say Y here even though your machine doesn't
533 have a local APIC, then the kernel will still run with no slowdown at
534 all. The local APIC supports CPU-generated self-interrupts (timer,
535 performance counters), and the NMI watchdog which detects hard
539 bool "IO-APIC support on uniprocessors"
540 depends on X86_UP_APIC
542 An IO-APIC (I/O Advanced Programmable Interrupt Controller) is an
543 SMP-capable replacement for PC-style interrupt controllers. Most
544 SMP systems and many recent uniprocessor systems have one.
546 If you have a single-CPU system with an IO-APIC, you can say Y here
547 to use it. If you say Y here even though your machine doesn't have
548 an IO-APIC, then the kernel will still run with no slowdown at all.
550 config X86_LOCAL_APIC
552 depends on X86_64 || (X86_32 && (X86_UP_APIC || ((X86_VISWS || SMP) && !X86_VOYAGER) || X86_GENERICARCH))
556 depends on X86_64 || (X86_32 && (X86_UP_IOAPIC || (SMP && !(X86_VISWS || X86_VOYAGER)) || X86_GENERICARCH))
558 config X86_VISWS_APIC
560 depends on X86_32 && X86_VISWS
563 bool "Machine Check Exception"
564 depends on !X86_VOYAGER
566 Machine Check Exception support allows the processor to notify the
567 kernel if it detects a problem (e.g. overheating, component failure).
568 The action the kernel takes depends on the severity of the problem,
569 ranging from a warning message on the console, to halting the machine.
570 Your processor must be a Pentium or newer to support this - check the
571 flags in /proc/cpuinfo for mce. Note that some older Pentium systems
572 have a design flaw which leads to false MCE events - hence MCE is
573 disabled on all P5 processors, unless explicitly enabled with "mce"
574 as a boot argument. Similarly, if MCE is built in and creates a
575 problem on some new non-standard machine, you can boot with "nomce"
576 to disable it. MCE support simply ignores non-MCE processors like
577 the 386 and 486, so nearly everyone can say Y here.
581 prompt "Intel MCE features"
582 depends on X86_64 && X86_MCE && X86_LOCAL_APIC
584 Additional support for intel specific MCE features such as
589 prompt "AMD MCE features"
590 depends on X86_64 && X86_MCE && X86_LOCAL_APIC
592 Additional support for AMD specific MCE features such as
593 the DRAM Error Threshold.
595 config X86_MCE_NONFATAL
596 tristate "Check for non-fatal errors on AMD Athlon/Duron / Intel Pentium 4"
597 depends on X86_32 && X86_MCE
599 Enabling this feature starts a timer that triggers every 5 seconds which
600 will look at the machine check registers to see if anything happened.
601 Non-fatal problems automatically get corrected (but still logged).
602 Disable this if you don't want to see these messages.
603 Seeing the messages this option prints out may be indicative of dying
604 or out-of-spec (ie, overclocked) hardware.
605 This option only does something on certain CPUs.
606 (AMD Athlon/Duron and Intel Pentium 4)
608 config X86_MCE_P4THERMAL
609 bool "check for P4 thermal throttling interrupt."
610 depends on X86_32 && X86_MCE && (X86_UP_APIC || SMP) && !X86_VISWS
612 Enabling this feature will cause a message to be printed when the P4
613 enters thermal throttling.
616 bool "Enable VM86 support" if EMBEDDED
620 This option is required by programs like DOSEMU to run 16-bit legacy
621 code on X86 processors. It also may be needed by software like
622 XFree86 to initialize some video cards via BIOS. Disabling this
623 option saves about 6k.
626 tristate "Toshiba Laptop support"
629 This adds a driver to safely access the System Management Mode of
630 the CPU on Toshiba portables with a genuine Toshiba BIOS. It does
631 not work on models with a Phoenix BIOS. The System Management Mode
632 is used to set the BIOS and power saving options on Toshiba portables.
634 For information on utilities to make use of this driver see the
635 Toshiba Linux utilities web site at:
636 <http://www.buzzard.org.uk/toshiba/>.
638 Say Y if you intend to run this kernel on a Toshiba portable.
642 tristate "Dell laptop support"
644 This adds a driver to safely access the System Management Mode
645 of the CPU on the Dell Inspiron 8000. The System Management Mode
646 is used to read cpu temperature and cooling fan status and to
647 control the fans on the I8K portables.
649 This driver has been tested only on the Inspiron 8000 but it may
650 also work with other Dell laptops. You can force loading on other
651 models by passing the parameter `force=1' to the module. Use at
654 For information on utilities to make use of this driver see the
655 I8K Linux utilities web site at:
656 <http://people.debian.org/~dz/i8k/>
658 Say Y if you intend to run this kernel on a Dell Inspiron 8000.
661 config X86_REBOOTFIXUPS
663 prompt "Enable X86 board specific fixups for reboot"
664 depends on X86_32 && X86
666 This enables chipset and/or board specific fixups to be done
667 in order to get reboot to work correctly. This is only needed on
668 some combinations of hardware and BIOS. The symptom, for which
669 this config is intended, is when reboot ends with a stalled/hung
672 Currently, the only fixup is for the Geode machines using
673 CS5530A and CS5536 chipsets and the RDC R-321x SoC.
675 Say Y if you want to enable the fixup. Currently, it's safe to
676 enable this option even if you don't need it.
680 tristate "/dev/cpu/microcode - Intel IA32 CPU microcode support"
683 If you say Y here, you will be able to update the microcode on
684 Intel processors in the IA32 family, e.g. Pentium Pro, Pentium II,
685 Pentium III, Pentium 4, Xeon etc. You will obviously need the
686 actual microcode binary data itself which is not shipped with the
689 For latest news and information on obtaining all the required
690 ingredients for this driver, check:
691 <http://www.urbanmyth.org/microcode/>.
693 To compile this driver as a module, choose M here: the
694 module will be called microcode.
696 config MICROCODE_OLD_INTERFACE
701 tristate "/dev/cpu/*/msr - Model-specific register support"
703 This device gives privileged processes access to the x86
704 Model-Specific Registers (MSRs). It is a character device with
705 major 202 and minors 0 to 31 for /dev/cpu/0/msr to /dev/cpu/31/msr.
706 MSR accesses are directed to a specific CPU on multi-processor
710 tristate "/dev/cpu/*/cpuid - CPU information support"
712 This device gives processes access to the x86 CPUID instruction to
713 be executed on a specific processor. It is a character device
714 with major 203 and minors 0 to 31 for /dev/cpu/0/cpuid to
718 prompt "High Memory Support"
719 default HIGHMEM4G if !X86_NUMAQ
720 default HIGHMEM64G if X86_NUMAQ
725 depends on !X86_NUMAQ
727 Linux can use up to 64 Gigabytes of physical memory on x86 systems.
728 However, the address space of 32-bit x86 processors is only 4
729 Gigabytes large. That means that, if you have a large amount of
730 physical memory, not all of it can be "permanently mapped" by the
731 kernel. The physical memory that's not permanently mapped is called
734 If you are compiling a kernel which will never run on a machine with
735 more than 1 Gigabyte total physical RAM, answer "off" here (default
736 choice and suitable for most users). This will result in a "3GB/1GB"
737 split: 3GB are mapped so that each process sees a 3GB virtual memory
738 space and the remaining part of the 4GB virtual memory space is used
739 by the kernel to permanently map as much physical memory as
742 If the machine has between 1 and 4 Gigabytes physical RAM, then
745 If more than 4 Gigabytes is used then answer "64GB" here. This
746 selection turns Intel PAE (Physical Address Extension) mode on.
747 PAE implements 3-level paging on IA32 processors. PAE is fully
748 supported by Linux, PAE mode is implemented on all recent Intel
749 processors (Pentium Pro and better). NOTE: If you say "64GB" here,
750 then the kernel will not boot on CPUs that don't support PAE!
752 The actual amount of total physical memory will either be
753 auto detected or can be forced by using a kernel command line option
754 such as "mem=256M". (Try "man bootparam" or see the documentation of
755 your boot loader (lilo or loadlin) about how to pass options to the
756 kernel at boot time.)
758 If unsure, say "off".
762 depends on !X86_NUMAQ
764 Select this if you have a 32-bit processor and between 1 and 4
765 gigabytes of physical RAM.
769 depends on !M386 && !M486
772 Select this if you have a 32-bit processor and more than 4
773 gigabytes of physical RAM.
778 depends on EXPERIMENTAL
779 prompt "Memory split" if EMBEDDED
783 Select the desired split between kernel and user memory.
785 If the address range available to the kernel is less than the
786 physical memory installed, the remaining memory will be available
787 as "high memory". Accessing high memory is a little more costly
788 than low memory, as it needs to be mapped into the kernel first.
789 Note that increasing the kernel address space limits the range
790 available to user programs, making the address space there
791 tighter. Selecting anything other than the default 3G/1G split
792 will also likely make your kernel incompatible with binary-only
795 If you are not absolutely sure what you are doing, leave this
799 bool "3G/1G user/kernel split"
800 config VMSPLIT_3G_OPT
802 bool "3G/1G user/kernel split (for full 1G low memory)"
804 bool "2G/2G user/kernel split"
805 config VMSPLIT_2G_OPT
807 bool "2G/2G user/kernel split (for full 2G low memory)"
809 bool "1G/3G user/kernel split"
814 default 0xB0000000 if VMSPLIT_3G_OPT
815 default 0x80000000 if VMSPLIT_2G
816 default 0x78000000 if VMSPLIT_2G_OPT
817 default 0x40000000 if VMSPLIT_1G
823 depends on X86_32 && (HIGHMEM64G || HIGHMEM4G)
827 prompt "PAE (Physical Address Extension) Support"
828 depends on X86_32 && !HIGHMEM4G
829 select RESOURCES_64BIT
831 PAE is required for NX support, and furthermore enables
832 larger swapspace support for non-overcommit purposes. It
833 has the cost of more pagetable lookup overhead, and also
834 consumes more pagetable space per process.
836 # Common NUMA Features
838 bool "Numa Memory Allocation and Scheduler Support (EXPERIMENTAL)"
840 depends on X86_64 || (X86_32 && HIGHMEM64G && (X86_NUMAQ || (X86_SUMMIT || X86_GENERICARCH) && ACPI) && EXPERIMENTAL)
842 default y if (X86_NUMAQ || X86_SUMMIT)
844 Enable NUMA (Non Uniform Memory Access) support.
845 The kernel will try to allocate memory used by a CPU on the
846 local memory controller of the CPU and add some more
847 NUMA awareness to the kernel.
849 For i386 this is currently highly experimental and should be only
850 used for kernel development. It might also cause boot failures.
851 For x86_64 this is recommended on all multiprocessor Opteron systems.
852 If the system is EM64T, you should say N unless your system is
855 comment "NUMA (Summit) requires SMP, 64GB highmem support, ACPI"
856 depends on X86_32 && X86_SUMMIT && (!HIGHMEM64G || !ACPI)
860 prompt "Old style AMD Opteron NUMA detection"
861 depends on X86_64 && NUMA && PCI
863 Enable K8 NUMA node topology detection. You should say Y here if
864 you have a multi processor AMD K8 system. This uses an old
865 method to read the NUMA configuration directly from the builtin
866 Northbridge of Opteron. It is recommended to use X86_64_ACPI_NUMA
867 instead, which also takes priority if both are compiled in.
869 config X86_64_ACPI_NUMA
871 prompt "ACPI NUMA detection"
872 depends on X86_64 && NUMA && ACPI && PCI
875 Enable ACPI SRAT based node topology detection.
878 bool "NUMA emulation"
879 depends on X86_64 && NUMA
881 Enable NUMA emulation. A flat machine will be split
882 into virtual nodes when booted with "numa=fake=N", where N is the
883 number of nodes. This is only useful for debugging.
888 default "6" if X86_64
889 default "4" if X86_NUMAQ
891 depends on NEED_MULTIPLE_NODES
893 config HAVE_ARCH_BOOTMEM_NODE
895 depends on X86_32 && NUMA
897 config ARCH_HAVE_MEMORY_PRESENT
899 depends on X86_32 && DISCONTIGMEM
901 config NEED_NODE_MEMMAP_SIZE
903 depends on X86_32 && (DISCONTIGMEM || SPARSEMEM)
905 config HAVE_ARCH_ALLOC_REMAP
907 depends on X86_32 && NUMA
909 config ARCH_FLATMEM_ENABLE
911 depends on X86_32 && ARCH_SELECT_MEMORY_MODEL && X86_PC && !NUMA
913 config ARCH_DISCONTIGMEM_ENABLE
915 depends on NUMA && X86_32
917 config ARCH_DISCONTIGMEM_DEFAULT
919 depends on NUMA && X86_32
921 config ARCH_SPARSEMEM_DEFAULT
925 config ARCH_SPARSEMEM_ENABLE
927 depends on X86_64 || NUMA || (EXPERIMENTAL && X86_PC)
928 select SPARSEMEM_STATIC if X86_32
929 select SPARSEMEM_VMEMMAP_ENABLE if X86_64
931 config ARCH_SELECT_MEMORY_MODEL
933 depends on ARCH_SPARSEMEM_ENABLE
935 config ARCH_MEMORY_PROBE
937 depends on MEMORY_HOTPLUG
942 bool "Allocate 3rd-level pagetables from highmem"
943 depends on X86_32 && (HIGHMEM4G || HIGHMEM64G)
945 The VM uses one page table entry for each page of physical memory.
946 For systems with a lot of RAM, this can be wasteful of precious
947 low memory. Setting this option will put user-space page table
948 entries in high memory.
950 config MATH_EMULATION
952 prompt "Math emulation" if X86_32
954 Linux can emulate a math coprocessor (used for floating point
955 operations) if you don't have one. 486DX and Pentium processors have
956 a math coprocessor built in, 486SX and 386 do not, unless you added
957 a 487DX or 387, respectively. (The messages during boot time can
958 give you some hints here ["man dmesg"].) Everyone needs either a
959 coprocessor or this emulation.
961 If you don't have a math coprocessor, you need to say Y here; if you
962 say Y here even though you have a coprocessor, the coprocessor will
963 be used nevertheless. (This behavior can be changed with the kernel
964 command line option "no387", which comes handy if your coprocessor
965 is broken. Try "man bootparam" or see the documentation of your boot
966 loader (lilo or loadlin) about how to pass options to the kernel at
967 boot time.) This means that it is a good idea to say Y here if you
968 intend to use this kernel on different machines.
970 More information about the internals of the Linux math coprocessor
971 emulation can be found in <file:arch/x86/math-emu/README>.
973 If you are not sure, say Y; apart from resulting in a 66 KB bigger
974 kernel, it won't hurt.
977 bool "MTRR (Memory Type Range Register) support"
979 On Intel P6 family processors (Pentium Pro, Pentium II and later)
980 the Memory Type Range Registers (MTRRs) may be used to control
981 processor access to memory ranges. This is most useful if you have
982 a video (VGA) card on a PCI or AGP bus. Enabling write-combining
983 allows bus write transfers to be combined into a larger transfer
984 before bursting over the PCI/AGP bus. This can increase performance
985 of image write operations 2.5 times or more. Saying Y here creates a
986 /proc/mtrr file which may be used to manipulate your processor's
987 MTRRs. Typically the X server should use this.
989 This code has a reasonably generic interface so that similar
990 control registers on other processors can be easily supported
993 The Cyrix 6x86, 6x86MX and M II processors have Address Range
994 Registers (ARRs) which provide a similar functionality to MTRRs. For
995 these, the ARRs are used to emulate the MTRRs.
996 The AMD K6-2 (stepping 8 and above) and K6-3 processors have two
997 MTRRs. The Centaur C6 (WinChip) has 8 MCRs, allowing
998 write-combining. All of these processors are supported by this code
999 and it makes sense to say Y here if you have one of them.
1001 Saying Y here also fixes a problem with buggy SMP BIOSes which only
1002 set the MTRRs for the boot CPU and not for the secondary CPUs. This
1003 can lead to all sorts of problems, so it's good to say Y here.
1005 You can safely say Y even if your machine doesn't have MTRRs, you'll
1006 just add about 9 KB to your kernel.
1008 See <file:Documentation/mtrr.txt> for more information.
1012 prompt "EFI runtime service support"
1015 This enables the kernel to use EFI runtime services that are
1016 available (such as the EFI variable services).
1018 This option is only useful on systems that have EFI firmware.
1019 In addition, you should use the latest ELILO loader available
1020 at <http://elilo.sourceforge.net> in order to take advantage
1021 of EFI runtime services. However, even with this option, the
1022 resultant kernel should continue to boot on existing non-EFI
1027 prompt "Enable kernel irq balancing"
1028 depends on X86_32 && SMP && X86_IO_APIC
1030 The default yes will allow the kernel to do irq load balancing.
1031 Saying no will keep the kernel from doing irq load balancing.
1035 prompt "Enable seccomp to safely compute untrusted bytecode"
1038 This kernel feature is useful for number crunching applications
1039 that may need to compute untrusted bytecode during their
1040 execution. By using pipes or other transports made available to
1041 the process as file descriptors supporting the read/write
1042 syscalls, it's possible to isolate those applications in
1043 their own address space using seccomp. Once seccomp is
1044 enabled via /proc/<pid>/seccomp, it cannot be disabled
1045 and the task is only allowed to execute a few safe syscalls
1046 defined by each seccomp mode.
1048 If unsure, say Y. Only embedded should say N here.
1050 config CC_STACKPROTECTOR
1051 bool "Enable -fstack-protector buffer overflow detection (EXPERIMENTAL)"
1052 depends on X86_64 && EXPERIMENTAL && BROKEN
1054 This option turns on the -fstack-protector GCC feature. This
1055 feature puts, at the beginning of critical functions, a canary
1056 value on the stack just before the return address, and validates
1057 the value just before actually returning. Stack based buffer
1058 overflows (that need to overwrite this return address) now also
1059 overwrite the canary, which gets detected and the attack is then
1060 neutralized via a kernel panic.
1062 This feature requires gcc version 4.2 or above, or a distribution
1063 gcc with the feature backported. Older versions are automatically
1064 detected and for those versions, this configuration option is ignored.
1066 config CC_STACKPROTECTOR_ALL
1067 bool "Use stack-protector for all functions"
1068 depends on CC_STACKPROTECTOR
1070 Normally, GCC only inserts the canary value protection for
1071 functions that use large-ish on-stack buffers. By enabling
1072 this option, GCC will be asked to do this for ALL functions.
1074 source kernel/Kconfig.hz
1077 bool "kexec system call"
1079 kexec is a system call that implements the ability to shutdown your
1080 current kernel, and to start another kernel. It is like a reboot
1081 but it is independent of the system firmware. And like a reboot
1082 you can start any kernel with it, not just Linux.
1084 The name comes from the similarity to the exec system call.
1086 It is an ongoing process to be certain the hardware in a machine
1087 is properly shutdown, so do not be surprised if this code does not
1088 initially work for you. It may help to enable device hotplugging
1089 support. As of this writing the exact hardware interface is
1090 strongly in flux, so no good recommendation can be made.
1093 bool "kernel crash dumps (EXPERIMENTAL)"
1094 depends on EXPERIMENTAL
1095 depends on X86_64 || (X86_32 && HIGHMEM)
1097 Generate crash dump after being started by kexec.
1098 This should be normally only set in special crash dump kernels
1099 which are loaded in the main kernel with kexec-tools into
1100 a specially reserved region and then later executed after
1101 a crash by kdump/kexec. The crash dump kernel must be compiled
1102 to a memory address not used by the main kernel or BIOS using
1103 PHYSICAL_START, or it must be built as a relocatable image
1104 (CONFIG_RELOCATABLE=y).
1105 For more details see Documentation/kdump/kdump.txt
1107 config PHYSICAL_START
1108 hex "Physical address where the kernel is loaded" if (EMBEDDED || CRASH_DUMP)
1109 default "0x1000000" if X86_NUMAQ
1110 default "0x200000" if X86_64
1113 This gives the physical address where the kernel is loaded.
1115 If kernel is a not relocatable (CONFIG_RELOCATABLE=n) then
1116 bzImage will decompress itself to above physical address and
1117 run from there. Otherwise, bzImage will run from the address where
1118 it has been loaded by the boot loader and will ignore above physical
1121 In normal kdump cases one does not have to set/change this option
1122 as now bzImage can be compiled as a completely relocatable image
1123 (CONFIG_RELOCATABLE=y) and be used to load and run from a different
1124 address. This option is mainly useful for the folks who don't want
1125 to use a bzImage for capturing the crash dump and want to use a
1126 vmlinux instead. vmlinux is not relocatable hence a kernel needs
1127 to be specifically compiled to run from a specific memory area
1128 (normally a reserved region) and this option comes handy.
1130 So if you are using bzImage for capturing the crash dump, leave
1131 the value here unchanged to 0x100000 and set CONFIG_RELOCATABLE=y.
1132 Otherwise if you plan to use vmlinux for capturing the crash dump
1133 change this value to start of the reserved region (Typically 16MB
1134 0x1000000). In other words, it can be set based on the "X" value as
1135 specified in the "crashkernel=YM@XM" command line boot parameter
1136 passed to the panic-ed kernel. Typically this parameter is set as
1137 crashkernel=64M@16M. Please take a look at
1138 Documentation/kdump/kdump.txt for more details about crash dumps.
1140 Usage of bzImage for capturing the crash dump is recommended as
1141 one does not have to build two kernels. Same kernel can be used
1142 as production kernel and capture kernel. Above option should have
1143 gone away after relocatable bzImage support is introduced. But it
1144 is present because there are users out there who continue to use
1145 vmlinux for dump capture. This option should go away down the
1148 Don't change this unless you know what you are doing.
1151 bool "Build a relocatable kernel (EXPERIMENTAL)"
1152 depends on EXPERIMENTAL
1154 This builds a kernel image that retains relocation information
1155 so it can be loaded someplace besides the default 1MB.
1156 The relocations tend to make the kernel binary about 10% larger,
1157 but are discarded at runtime.
1159 One use is for the kexec on panic case where the recovery kernel
1160 must live at a different physical address than the primary
1163 Note: If CONFIG_RELOCATABLE=y, then the kernel runs from the address
1164 it has been loaded at and the compile time physical address
1165 (CONFIG_PHYSICAL_START) is ignored.
1167 config PHYSICAL_ALIGN
1169 prompt "Alignment value to which kernel should be aligned" if X86_32
1170 default "0x100000" if X86_32
1171 default "0x200000" if X86_64
1172 range 0x2000 0x400000
1174 This value puts the alignment restrictions on physical address
1175 where kernel is loaded and run from. Kernel is compiled for an
1176 address which meets above alignment restriction.
1178 If bootloader loads the kernel at a non-aligned address and
1179 CONFIG_RELOCATABLE is set, kernel will move itself to nearest
1180 address aligned to above value and run from there.
1182 If bootloader loads the kernel at a non-aligned address and
1183 CONFIG_RELOCATABLE is not set, kernel will ignore the run time
1184 load address and decompress itself to the address it has been
1185 compiled for and run from there. The address for which kernel is
1186 compiled already meets above alignment restrictions. Hence the
1187 end result is that kernel runs from a physical address meeting
1188 above alignment restrictions.
1190 Don't change this unless you know what you are doing.
1193 bool "Support for suspend on SMP and hot-pluggable CPUs (EXPERIMENTAL)"
1194 depends on SMP && HOTPLUG && EXPERIMENTAL && !X86_VOYAGER
1196 Say Y here to experiment with turning CPUs off and on, and to
1197 enable suspend on SMP systems. CPUs can be controlled through
1198 /sys/devices/system/cpu.
1199 Say N if you want to disable CPU hotplug and don't need to
1204 prompt "Compat VDSO support"
1205 depends on X86_32 || IA32_EMULATION
1207 Map the 32-bit VDSO to the predictable old-style address too.
1209 Say N here if you are running a sufficiently recent glibc
1210 version (2.3.3 or later), to remove the high-mapped
1211 VDSO mapping and to exclusively use the randomized VDSO.
1217 config ARCH_ENABLE_MEMORY_HOTPLUG
1219 depends on X86_64 || (X86_32 && HIGHMEM)
1221 config HAVE_ARCH_EARLY_PFN_TO_NID
1225 menu "Power management options"
1226 depends on !X86_VOYAGER
1228 config ARCH_HIBERNATION_HEADER
1230 depends on X86_64 && HIBERNATION
1232 source "kernel/power/Kconfig"
1234 source "drivers/acpi/Kconfig"
1239 depends on APM || APM_MODULE
1242 tristate "APM (Advanced Power Management) BIOS support"
1243 depends on X86_32 && PM_SLEEP && !X86_VISWS
1245 APM is a BIOS specification for saving power using several different
1246 techniques. This is mostly useful for battery powered laptops with
1247 APM compliant BIOSes. If you say Y here, the system time will be
1248 reset after a RESUME operation, the /proc/apm device will provide
1249 battery status information, and user-space programs will receive
1250 notification of APM "events" (e.g. battery status change).
1252 If you select "Y" here, you can disable actual use of the APM
1253 BIOS by passing the "apm=off" option to the kernel at boot time.
1255 Note that the APM support is almost completely disabled for
1256 machines with more than one CPU.
1258 In order to use APM, you will need supporting software. For location
1259 and more information, read <file:Documentation/power/pm.txt> and the
1260 Battery Powered Linux mini-HOWTO, available from
1261 <http://www.tldp.org/docs.html#howto>.
1263 This driver does not spin down disk drives (see the hdparm(8)
1264 manpage ("man 8 hdparm") for that), and it doesn't turn off
1265 VESA-compliant "green" monitors.
1267 This driver does not support the TI 4000M TravelMate and the ACER
1268 486/DX4/75 because they don't have compliant BIOSes. Many "green"
1269 desktop machines also don't have compliant BIOSes, and this driver
1270 may cause those machines to panic during the boot phase.
1272 Generally, if you don't have a battery in your machine, there isn't
1273 much point in using this driver and you should say N. If you get
1274 random kernel OOPSes or reboots that don't seem to be related to
1275 anything, try disabling/enabling this option (or disabling/enabling
1278 Some other things you should try when experiencing seemingly random,
1281 1) make sure that you have enough swap space and that it is
1283 2) pass the "no-hlt" option to the kernel
1284 3) switch on floating point emulation in the kernel and pass
1285 the "no387" option to the kernel
1286 4) pass the "floppy=nodma" option to the kernel
1287 5) pass the "mem=4M" option to the kernel (thereby disabling
1288 all but the first 4 MB of RAM)
1289 6) make sure that the CPU is not over clocked.
1290 7) read the sig11 FAQ at <http://www.bitwizard.nl/sig11/>
1291 8) disable the cache from your BIOS settings
1292 9) install a fan for the video card or exchange video RAM
1293 10) install a better fan for the CPU
1294 11) exchange RAM chips
1295 12) exchange the motherboard.
1297 To compile this driver as a module, choose M here: the
1298 module will be called apm.
1302 config APM_IGNORE_USER_SUSPEND
1303 bool "Ignore USER SUSPEND"
1305 This option will ignore USER SUSPEND requests. On machines with a
1306 compliant APM BIOS, you want to say N. However, on the NEC Versa M
1307 series notebooks, it is necessary to say Y because of a BIOS bug.
1309 config APM_DO_ENABLE
1310 bool "Enable PM at boot time"
1312 Enable APM features at boot time. From page 36 of the APM BIOS
1313 specification: "When disabled, the APM BIOS does not automatically
1314 power manage devices, enter the Standby State, enter the Suspend
1315 State, or take power saving steps in response to CPU Idle calls."
1316 This driver will make CPU Idle calls when Linux is idle (unless this
1317 feature is turned off -- see "Do CPU IDLE calls", below). This
1318 should always save battery power, but more complicated APM features
1319 will be dependent on your BIOS implementation. You may need to turn
1320 this option off if your computer hangs at boot time when using APM
1321 support, or if it beeps continuously instead of suspending. Turn
1322 this off if you have a NEC UltraLite Versa 33/C or a Toshiba
1323 T400CDT. This is off by default since most machines do fine without
1327 bool "Make CPU Idle calls when idle"
1329 Enable calls to APM CPU Idle/CPU Busy inside the kernel's idle loop.
1330 On some machines, this can activate improved power savings, such as
1331 a slowed CPU clock rate, when the machine is idle. These idle calls
1332 are made after the idle loop has run for some length of time (e.g.,
1333 333 mS). On some machines, this will cause a hang at boot time or
1334 whenever the CPU becomes idle. (On machines with more than one CPU,
1335 this option does nothing.)
1337 config APM_DISPLAY_BLANK
1338 bool "Enable console blanking using APM"
1340 Enable console blanking using the APM. Some laptops can use this to
1341 turn off the LCD backlight when the screen blanker of the Linux
1342 virtual console blanks the screen. Note that this is only used by
1343 the virtual console screen blanker, and won't turn off the backlight
1344 when using the X Window system. This also doesn't have anything to
1345 do with your VESA-compliant power-saving monitor. Further, this
1346 option doesn't work for all laptops -- it might not turn off your
1347 backlight at all, or it might print a lot of errors to the console,
1348 especially if you are using gpm.
1350 config APM_ALLOW_INTS
1351 bool "Allow interrupts during APM BIOS calls"
1353 Normally we disable external interrupts while we are making calls to
1354 the APM BIOS as a measure to lessen the effects of a badly behaving
1355 BIOS implementation. The BIOS should reenable interrupts if it
1356 needs to. Unfortunately, some BIOSes do not -- especially those in
1357 many of the newer IBM Thinkpads. If you experience hangs when you
1358 suspend, try setting this to Y. Otherwise, say N.
1360 config APM_REAL_MODE_POWER_OFF
1361 bool "Use real mode APM BIOS call to power off"
1363 Use real mode APM BIOS calls to switch off the computer. This is
1364 a work-around for a number of buggy BIOSes. Switch this option on if
1365 your computer crashes instead of powering off properly.
1369 source "arch/x86/kernel/cpu/cpufreq/Kconfig"
1371 source "drivers/cpuidle/Kconfig"
1376 menu "Bus options (PCI etc.)"
1379 bool "PCI support" if !X86_VISWS
1380 depends on !X86_VOYAGER
1382 select ARCH_SUPPORTS_MSI if (X86_LOCAL_APIC && X86_IO_APIC)
1384 Find out whether you have a PCI motherboard. PCI is the name of a
1385 bus system, i.e. the way the CPU talks to the other stuff inside
1386 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
1387 VESA. If you have PCI, say Y, otherwise N.
1390 prompt "PCI access mode"
1391 depends on X86_32 && PCI && !X86_VISWS
1394 On PCI systems, the BIOS can be used to detect the PCI devices and
1395 determine their configuration. However, some old PCI motherboards
1396 have BIOS bugs and may crash if this is done. Also, some embedded
1397 PCI-based systems don't have any BIOS at all. Linux can also try to
1398 detect the PCI hardware directly without using the BIOS.
1400 With this option, you can specify how Linux should detect the
1401 PCI devices. If you choose "BIOS", the BIOS will be used,
1402 if you choose "Direct", the BIOS won't be used, and if you
1403 choose "MMConfig", then PCI Express MMCONFIG will be used.
1404 If you choose "Any", the kernel will try MMCONFIG, then the
1405 direct access method and falls back to the BIOS if that doesn't
1406 work. If unsure, go with the default, which is "Any".
1411 config PCI_GOMMCONFIG
1424 depends on X86_32 && !X86_VISWS && PCI && (PCI_GOBIOS || PCI_GOANY)
1426 # x86-64 doesn't support PCI BIOS access from long mode so always go direct.
1429 depends on PCI && (X86_64 || (PCI_GODIRECT || PCI_GOANY) || X86_VISWS)
1433 depends on X86_32 && PCI && ACPI && (PCI_GOMMCONFIG || PCI_GOANY)
1440 bool "Support mmconfig PCI config space access"
1441 depends on X86_64 && PCI && ACPI
1444 bool "Support for DMA Remapping Devices (EXPERIMENTAL)"
1445 depends on X86_64 && PCI_MSI && ACPI && EXPERIMENTAL
1447 DMA remapping (DMAR) devices support enables independent address
1448 translations for Direct Memory Access (DMA) from devices.
1449 These DMA remapping devices are reported via ACPI tables
1450 and include PCI device scope covered by these DMA
1455 prompt "Support for Graphics workaround"
1458 Current Graphics drivers tend to use physical address
1459 for DMA and avoid using DMA APIs. Setting this config
1460 option permits the IOMMU driver to set a unity map for
1461 all the OS-visible memory. Hence the driver can continue
1462 to use physical addresses for DMA.
1464 config DMAR_FLOPPY_WA
1468 Floppy disk drivers are know to bypass DMA API calls
1469 thereby failing to work when IOMMU is enabled. This
1470 workaround will setup a 1:1 mapping for the first
1471 16M to make floppy (an ISA device) work.
1473 source "drivers/pci/pcie/Kconfig"
1475 source "drivers/pci/Kconfig"
1477 # x86_64 have no ISA slots, but do have ISA-style DMA.
1485 depends on !(X86_VOYAGER || X86_VISWS)
1487 Find out whether you have ISA slots on your motherboard. ISA is the
1488 name of a bus system, i.e. the way the CPU talks to the other stuff
1489 inside your box. Other bus systems are PCI, EISA, MicroChannel
1490 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
1491 newer boards don't support it. If you have ISA, say Y, otherwise N.
1497 The Extended Industry Standard Architecture (EISA) bus was
1498 developed as an open alternative to the IBM MicroChannel bus.
1500 The EISA bus provided some of the features of the IBM MicroChannel
1501 bus while maintaining backward compatibility with cards made for
1502 the older ISA bus. The EISA bus saw limited use between 1988 and
1503 1995 when it was made obsolete by the PCI bus.
1505 Say Y here if you are building a kernel for an EISA-based machine.
1509 source "drivers/eisa/Kconfig"
1512 bool "MCA support" if !(X86_VISWS || X86_VOYAGER)
1513 default y if X86_VOYAGER
1515 MicroChannel Architecture is found in some IBM PS/2 machines and
1516 laptops. It is a bus system similar to PCI or ISA. See
1517 <file:Documentation/mca.txt> (and especially the web page given
1518 there) before attempting to build an MCA bus kernel.
1520 source "drivers/mca/Kconfig"
1523 tristate "NatSemi SCx200 support"
1524 depends on !X86_VOYAGER
1526 This provides basic support for National Semiconductor's
1527 (now AMD's) Geode processors. The driver probes for the
1528 PCI-IDs of several on-chip devices, so its a good dependency
1529 for other scx200_* drivers.
1531 If compiled as a module, the driver is named scx200.
1533 config SCx200HR_TIMER
1534 tristate "NatSemi SCx200 27MHz High-Resolution Timer Support"
1535 depends on SCx200 && GENERIC_TIME
1538 This driver provides a clocksource built upon the on-chip
1539 27MHz high-resolution timer. Its also a workaround for
1540 NSC Geode SC-1100's buggy TSC, which loses time when the
1541 processor goes idle (as is done by the scheduler). The
1542 other workaround is idle=poll boot option.
1544 config GEODE_MFGPT_TIMER
1546 prompt "Geode Multi-Function General Purpose Timer (MFGPT) events"
1547 depends on MGEODE_LX && GENERIC_TIME && GENERIC_CLOCKEVENTS
1549 This driver provides a clock event source based on the MFGPT
1550 timer(s) in the CS5535 and CS5536 companion chip for the geode.
1551 MFGPTs have a better resolution and max interval than the
1552 generic PIT, and are suitable for use as high-res timers.
1558 depends on AGP_AMD64 || (X86_64 && (GART_IOMMU || (PCI && NUMA)))
1560 source "drivers/pcmcia/Kconfig"
1562 source "drivers/pci/hotplug/Kconfig"
1567 menu "Executable file formats / Emulations"
1569 source "fs/Kconfig.binfmt"
1571 config IA32_EMULATION
1572 bool "IA32 Emulation"
1574 select COMPAT_BINFMT_ELF
1576 Include code to run 32-bit programs under a 64-bit kernel. You should
1577 likely turn this on, unless you're 100% sure that you don't have any
1578 32-bit programs left.
1581 tristate "IA32 a.out support"
1582 depends on IA32_EMULATION && ARCH_SUPPORTS_AOUT
1584 Support old a.out binaries in the 32bit emulation.
1588 depends on IA32_EMULATION
1590 config COMPAT_FOR_U64_ALIGNMENT
1594 config SYSVIPC_COMPAT
1596 depends on X86_64 && COMPAT && SYSVIPC
1601 source "net/Kconfig"
1603 source "drivers/Kconfig"
1605 source "drivers/firmware/Kconfig"
1609 source "arch/x86/Kconfig.debug"
1611 source "security/Kconfig"
1613 source "crypto/Kconfig"
1615 source "arch/x86/kvm/Kconfig"
1617 source "lib/Kconfig"
projects / linux-2.6 / blob