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 SEMAPHORE_SLEEPERS
59 config FAST_CMPXCHG_LOCAL
72 config GENERIC_ISA_DMA
82 config GENERIC_HWEIGHT
88 config ARCH_MAY_HAVE_PC_FDC
94 config RWSEM_GENERIC_SPINLOCK
97 config RWSEM_XCHGADD_ALGORITHM
100 config ARCH_HAS_ILOG2_U32
103 config ARCH_HAS_ILOG2_U64
106 config ARCH_HAS_CPU_IDLE_WAIT
109 config GENERIC_CALIBRATE_DELAY
112 config GENERIC_TIME_VSYSCALL
116 config ARCH_HAS_CPU_RELAX
119 config HAVE_SETUP_PER_CPU_AREA
122 config ARCH_HIBERNATION_POSSIBLE
124 depends on !SMP || !X86_VOYAGER
126 config ARCH_SUSPEND_POSSIBLE
128 depends on !X86_VOYAGER
134 config ARCH_POPULATES_NODE_MAP
141 config ARCH_SUPPORTS_AOUT
144 # Use the generic interrupt handling code in kernel/irq/:
145 config GENERIC_HARDIRQS
149 config GENERIC_IRQ_PROBE
153 config GENERIC_PENDING_IRQ
155 depends on GENERIC_HARDIRQS && SMP
160 depends on SMP && ((X86_32 && !X86_VOYAGER) || X86_64)
165 depends on X86_32 && SMP
169 depends on X86_64 && SMP
174 depends on (X86_32 && !(X86_VISWS || X86_VOYAGER)) || (X86_64 && !MK8)
177 config X86_BIOS_REBOOT
179 depends on X86_32 && !(X86_VISWS || X86_VOYAGER)
182 config X86_TRAMPOLINE
184 depends on X86_SMP || (X86_VOYAGER && SMP)
189 source "init/Kconfig"
191 menu "Processor type and features"
193 source "kernel/time/Kconfig"
196 bool "Symmetric multi-processing support"
198 This enables support for systems with more than one CPU. If you have
199 a system with only one CPU, like most personal computers, say N. If
200 you have a system with more than one CPU, say Y.
202 If you say N here, the kernel will run on single and multiprocessor
203 machines, but will use only one CPU of a multiprocessor machine. If
204 you say Y here, the kernel will run on many, but not all,
205 singleprocessor machines. On a singleprocessor machine, the kernel
206 will run faster if you say N here.
208 Note that if you say Y here and choose architecture "586" or
209 "Pentium" under "Processor family", the kernel will not work on 486
210 architectures. Similarly, multiprocessor kernels for the "PPro"
211 architecture may not work on all Pentium based boards.
213 People using multiprocessor machines who say Y here should also say
214 Y to "Enhanced Real Time Clock Support", below. The "Advanced Power
215 Management" code will be disabled if you say Y here.
217 See also <file:Documentation/i386/IO-APIC.txt>,
218 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
219 <http://www.tldp.org/docs.html#howto>.
221 If you don't know what to do here, say N.
224 prompt "Subarchitecture Type"
230 Choose this option if your computer is a standard PC or compatible.
236 Select this for an AMD Elan processor.
238 Do not use this option for K6/Athlon/Opteron processors!
240 If unsure, choose "PC-compatible" instead.
245 select SMP if !BROKEN
247 Voyager is an MCA-based 32-way capable SMP architecture proprietary
248 to NCR Corp. Machine classes 345x/35xx/4100/51xx are Voyager-based.
252 If you do not specifically know you have a Voyager based machine,
253 say N here, otherwise the kernel you build will not be bootable.
256 bool "NUMAQ (IBM/Sequent)"
261 This option is used for getting Linux to run on a (IBM/Sequent) NUMA
262 multiquad box. This changes the way that processors are bootstrapped,
263 and uses Clustered Logical APIC addressing mode instead of Flat Logical.
264 You will need a new lynxer.elf file to flash your firmware with - send
265 email to <Martin.Bligh@us.ibm.com>.
268 bool "Summit/EXA (IBM x440)"
269 depends on X86_32 && SMP
271 This option is needed for IBM systems that use the Summit/EXA chipset.
272 In particular, it is needed for the x440.
274 If you don't have one of these computers, you should say N here.
275 If you want to build a NUMA kernel, you must select ACPI.
278 bool "Support for other sub-arch SMP systems with more than 8 CPUs"
279 depends on X86_32 && SMP
281 This option is needed for the systems that have more than 8 CPUs
282 and if the system is not of any sub-arch type above.
284 If you don't have such a system, you should say N here.
287 bool "SGI 320/540 (Visual Workstation)"
290 The SGI Visual Workstation series is an IA32-based workstation
291 based on SGI systems chips with some legacy PC hardware attached.
293 Say Y here to create a kernel to run on the SGI 320 or 540.
295 A kernel compiled for the Visual Workstation will not run on PCs
296 and vice versa. See <file:Documentation/sgi-visws.txt> for details.
298 config X86_GENERICARCH
299 bool "Generic architecture (Summit, bigsmp, ES7000, default)"
302 This option compiles in the Summit, bigsmp, ES7000, default subarchitectures.
303 It is intended for a generic binary kernel.
304 If you want a NUMA kernel, select ACPI. We need SRAT for NUMA.
307 bool "Support for Unisys ES7000 IA32 series"
308 depends on X86_32 && SMP
310 Support for Unisys ES7000 systems. Say 'Y' here if this kernel is
311 supposed to run on an IA32-based Unisys ES7000 system.
312 Only choose this option if you have such a system, otherwise you
316 bool "RDC R-321x SoC"
319 select X86_REBOOTFIXUPS
324 This option is needed for RDC R-321x system-on-chip, also known
326 If you don't have one of these chips, you should say N here.
329 bool "Support for ScaleMP vSMP"
330 depends on X86_64 && PCI
332 Support for ScaleMP vSMP systems. Say 'Y' here if this kernel is
333 supposed to run on these EM64T-based machines. Only choose this option
334 if you have one of these machines.
338 config SCHED_NO_NO_OMIT_FRAME_POINTER
340 prompt "Single-depth WCHAN output"
343 Calculate simpler /proc/<PID>/wchan values. If this option
344 is disabled then wchan values will recurse back to the
345 caller function. This provides more accurate wchan values,
346 at the expense of slightly more scheduling overhead.
348 If in doubt, say "Y".
350 menuconfig PARAVIRT_GUEST
351 bool "Paravirtualized guest support"
353 Say Y here to get to see options related to running Linux under
354 various hypervisors. This option alone does not add any kernel code.
356 If you say N, all options in this submenu will be skipped and disabled.
360 source "arch/x86/xen/Kconfig"
363 bool "VMI Guest support"
366 depends on !(X86_VISWS || X86_VOYAGER)
368 VMI provides a paravirtualized interface to the VMware ESX server
369 (it could be used by other hypervisors in theory too, but is not
370 at the moment), by linking the kernel to a GPL-ed ROM module
371 provided by the hypervisor.
373 source "arch/x86/lguest/Kconfig"
376 bool "Enable paravirtualization code"
377 depends on !(X86_VISWS || X86_VOYAGER)
379 This changes the kernel so it can modify itself when it is run
380 under a hypervisor, potentially improving performance significantly
381 over full virtualization. However, when run without a hypervisor
382 the kernel is theoretically slower and slightly larger.
388 depends on X86_32 && ACPI && NUMA && (X86_SUMMIT || X86_GENERICARCH)
391 config HAVE_ARCH_PARSE_SRAT
395 config X86_SUMMIT_NUMA
397 depends on X86_32 && NUMA && (X86_SUMMIT || X86_GENERICARCH)
399 config X86_CYCLONE_TIMER
401 depends on X86_32 && X86_SUMMIT || X86_GENERICARCH
403 config ES7000_CLUSTERED_APIC
405 depends on SMP && X86_ES7000 && MPENTIUMIII
407 source "arch/x86/Kconfig.cpu"
411 prompt "HPET Timer Support" if X86_32
413 Use the IA-PC HPET (High Precision Event Timer) to manage
414 time in preference to the PIT and RTC, if a HPET is
416 HPET is the next generation timer replacing legacy 8254s.
417 The HPET provides a stable time base on SMP
418 systems, unlike the TSC, but it is more expensive to access,
419 as it is off-chip. You can find the HPET spec at
420 <http://www.intel.com/hardwaredesign/hpetspec.htm>.
422 You can safely choose Y here. However, HPET will only be
423 activated if the platform and the BIOS support this feature.
424 Otherwise the 8254 will be used for timing services.
426 Choose N to continue using the legacy 8254 timer.
428 config HPET_EMULATE_RTC
430 depends on HPET_TIMER && (RTC=y || RTC=m || RTC_DRV_CMOS=m || RTC_DRV_CMOS=y)
432 # Mark as embedded because too many people got it wrong.
433 # The code disables itself when not needed.
435 bool "GART IOMMU support" if EMBEDDED
439 depends on X86_64 && PCI
441 Support for full DMA access of devices with 32bit memory access only
442 on systems with more than 3GB. This is usually needed for USB,
443 sound, many IDE/SATA chipsets and some other devices.
444 Provides a driver for the AMD Athlon64/Opteron/Turion/Sempron GART
445 based hardware IOMMU and a software bounce buffer based IOMMU used
446 on Intel systems and as fallback.
447 The code is only active when needed (enough memory and limited
448 device) unless CONFIG_IOMMU_DEBUG or iommu=force is specified
452 bool "IBM Calgary IOMMU support"
454 depends on X86_64 && PCI && EXPERIMENTAL
456 Support for hardware IOMMUs in IBM's xSeries x366 and x460
457 systems. Needed to run systems with more than 3GB of memory
458 properly with 32-bit PCI devices that do not support DAC
459 (Double Address Cycle). Calgary also supports bus level
460 isolation, where all DMAs pass through the IOMMU. This
461 prevents them from going anywhere except their intended
462 destination. This catches hard-to-find kernel bugs and
463 mis-behaving drivers and devices that do not use the DMA-API
464 properly to set up their DMA buffers. The IOMMU can be
465 turned off at boot time with the iommu=off parameter.
466 Normally the kernel will make the right choice by itself.
469 config CALGARY_IOMMU_ENABLED_BY_DEFAULT
471 prompt "Should Calgary be enabled by default?"
472 depends on CALGARY_IOMMU
474 Should Calgary be enabled by default? if you choose 'y', Calgary
475 will be used (if it exists). If you choose 'n', Calgary will not be
476 used even if it exists. If you choose 'n' and would like to use
477 Calgary anyway, pass 'iommu=calgary' on the kernel command line.
481 def_bool (CALGARY_IOMMU || GART_IOMMU)
483 # need this always selected by IOMMU for the VIA workaround
487 Support for software bounce buffers used on x86-64 systems
488 which don't have a hardware IOMMU (e.g. the current generation
489 of Intel's x86-64 CPUs). Using this PCI devices which can only
490 access 32-bits of memory can be used on systems with more than
491 3 GB of memory. If unsure, say Y.
495 int "Maximum number of CPUs (2-255)"
498 default "32" if X86_NUMAQ || X86_SUMMIT || X86_BIGSMP || X86_ES7000
501 This allows you to specify the maximum number of CPUs which this
502 kernel will support. The maximum supported value is 255 and the
503 minimum value which makes sense is 2.
505 This is purely to save memory - each supported CPU adds
506 approximately eight kilobytes to the kernel image.
509 bool "SMT (Hyperthreading) scheduler support"
510 depends on (X86_64 && SMP) || (X86_32 && X86_HT)
512 SMT scheduler support improves the CPU scheduler's decision making
513 when dealing with Intel Pentium 4 chips with HyperThreading at a
514 cost of slightly increased overhead in some places. If unsure say
519 prompt "Multi-core scheduler support"
520 depends on (X86_64 && SMP) || (X86_32 && X86_HT)
522 Multi-core scheduler support improves the CPU scheduler's decision
523 making when dealing with multi-core CPU chips at a cost of slightly
524 increased overhead in some places. If unsure say N here.
526 source "kernel/Kconfig.preempt"
529 bool "Local APIC support on uniprocessors"
530 depends on X86_32 && !SMP && !(X86_VISWS || X86_VOYAGER || X86_GENERICARCH)
532 A local APIC (Advanced Programmable Interrupt Controller) is an
533 integrated interrupt controller in the CPU. If you have a single-CPU
534 system which has a processor with a local APIC, you can say Y here to
535 enable and use it. If you say Y here even though your machine doesn't
536 have a local APIC, then the kernel will still run with no slowdown at
537 all. The local APIC supports CPU-generated self-interrupts (timer,
538 performance counters), and the NMI watchdog which detects hard
542 bool "IO-APIC support on uniprocessors"
543 depends on X86_UP_APIC
545 An IO-APIC (I/O Advanced Programmable Interrupt Controller) is an
546 SMP-capable replacement for PC-style interrupt controllers. Most
547 SMP systems and many recent uniprocessor systems have one.
549 If you have a single-CPU system with an IO-APIC, you can say Y here
550 to use it. If you say Y here even though your machine doesn't have
551 an IO-APIC, then the kernel will still run with no slowdown at all.
553 config X86_LOCAL_APIC
555 depends on X86_64 || (X86_32 && (X86_UP_APIC || ((X86_VISWS || SMP) && !X86_VOYAGER) || X86_GENERICARCH))
559 depends on X86_64 || (X86_32 && (X86_UP_IOAPIC || (SMP && !(X86_VISWS || X86_VOYAGER)) || X86_GENERICARCH))
561 config X86_VISWS_APIC
563 depends on X86_32 && X86_VISWS
566 bool "Machine Check Exception"
567 depends on !X86_VOYAGER
569 Machine Check Exception support allows the processor to notify the
570 kernel if it detects a problem (e.g. overheating, component failure).
571 The action the kernel takes depends on the severity of the problem,
572 ranging from a warning message on the console, to halting the machine.
573 Your processor must be a Pentium or newer to support this - check the
574 flags in /proc/cpuinfo for mce. Note that some older Pentium systems
575 have a design flaw which leads to false MCE events - hence MCE is
576 disabled on all P5 processors, unless explicitly enabled with "mce"
577 as a boot argument. Similarly, if MCE is built in and creates a
578 problem on some new non-standard machine, you can boot with "nomce"
579 to disable it. MCE support simply ignores non-MCE processors like
580 the 386 and 486, so nearly everyone can say Y here.
584 prompt "Intel MCE features"
585 depends on X86_64 && X86_MCE && X86_LOCAL_APIC
587 Additional support for intel specific MCE features such as
592 prompt "AMD MCE features"
593 depends on X86_64 && X86_MCE && X86_LOCAL_APIC
595 Additional support for AMD specific MCE features such as
596 the DRAM Error Threshold.
598 config X86_MCE_NONFATAL
599 tristate "Check for non-fatal errors on AMD Athlon/Duron / Intel Pentium 4"
600 depends on X86_32 && X86_MCE
602 Enabling this feature starts a timer that triggers every 5 seconds which
603 will look at the machine check registers to see if anything happened.
604 Non-fatal problems automatically get corrected (but still logged).
605 Disable this if you don't want to see these messages.
606 Seeing the messages this option prints out may be indicative of dying
607 or out-of-spec (ie, overclocked) hardware.
608 This option only does something on certain CPUs.
609 (AMD Athlon/Duron and Intel Pentium 4)
611 config X86_MCE_P4THERMAL
612 bool "check for P4 thermal throttling interrupt."
613 depends on X86_32 && X86_MCE && (X86_UP_APIC || SMP) && !X86_VISWS
615 Enabling this feature will cause a message to be printed when the P4
616 enters thermal throttling.
619 bool "Enable VM86 support" if EMBEDDED
623 This option is required by programs like DOSEMU to run 16-bit legacy
624 code on X86 processors. It also may be needed by software like
625 XFree86 to initialize some video cards via BIOS. Disabling this
626 option saves about 6k.
629 tristate "Toshiba Laptop support"
632 This adds a driver to safely access the System Management Mode of
633 the CPU on Toshiba portables with a genuine Toshiba BIOS. It does
634 not work on models with a Phoenix BIOS. The System Management Mode
635 is used to set the BIOS and power saving options on Toshiba portables.
637 For information on utilities to make use of this driver see the
638 Toshiba Linux utilities web site at:
639 <http://www.buzzard.org.uk/toshiba/>.
641 Say Y if you intend to run this kernel on a Toshiba portable.
645 tristate "Dell laptop support"
647 This adds a driver to safely access the System Management Mode
648 of the CPU on the Dell Inspiron 8000. The System Management Mode
649 is used to read cpu temperature and cooling fan status and to
650 control the fans on the I8K portables.
652 This driver has been tested only on the Inspiron 8000 but it may
653 also work with other Dell laptops. You can force loading on other
654 models by passing the parameter `force=1' to the module. Use at
657 For information on utilities to make use of this driver see the
658 I8K Linux utilities web site at:
659 <http://people.debian.org/~dz/i8k/>
661 Say Y if you intend to run this kernel on a Dell Inspiron 8000.
664 config X86_REBOOTFIXUPS
666 prompt "Enable X86 board specific fixups for reboot"
667 depends on X86_32 && X86
669 This enables chipset and/or board specific fixups to be done
670 in order to get reboot to work correctly. This is only needed on
671 some combinations of hardware and BIOS. The symptom, for which
672 this config is intended, is when reboot ends with a stalled/hung
675 Currently, the only fixup is for the Geode machines using
676 CS5530A and CS5536 chipsets and the RDC R-321x SoC.
678 Say Y if you want to enable the fixup. Currently, it's safe to
679 enable this option even if you don't need it.
683 tristate "/dev/cpu/microcode - Intel IA32 CPU microcode support"
686 If you say Y here, you will be able to update the microcode on
687 Intel processors in the IA32 family, e.g. Pentium Pro, Pentium II,
688 Pentium III, Pentium 4, Xeon etc. You will obviously need the
689 actual microcode binary data itself which is not shipped with the
692 For latest news and information on obtaining all the required
693 ingredients for this driver, check:
694 <http://www.urbanmyth.org/microcode/>.
696 To compile this driver as a module, choose M here: the
697 module will be called microcode.
699 config MICROCODE_OLD_INTERFACE
704 tristate "/dev/cpu/*/msr - Model-specific register support"
706 This device gives privileged processes access to the x86
707 Model-Specific Registers (MSRs). It is a character device with
708 major 202 and minors 0 to 31 for /dev/cpu/0/msr to /dev/cpu/31/msr.
709 MSR accesses are directed to a specific CPU on multi-processor
713 tristate "/dev/cpu/*/cpuid - CPU information support"
715 This device gives processes access to the x86 CPUID instruction to
716 be executed on a specific processor. It is a character device
717 with major 203 and minors 0 to 31 for /dev/cpu/0/cpuid to
721 prompt "High Memory Support"
722 default HIGHMEM4G if !X86_NUMAQ
723 default HIGHMEM64G if X86_NUMAQ
728 depends on !X86_NUMAQ
730 Linux can use up to 64 Gigabytes of physical memory on x86 systems.
731 However, the address space of 32-bit x86 processors is only 4
732 Gigabytes large. That means that, if you have a large amount of
733 physical memory, not all of it can be "permanently mapped" by the
734 kernel. The physical memory that's not permanently mapped is called
737 If you are compiling a kernel which will never run on a machine with
738 more than 1 Gigabyte total physical RAM, answer "off" here (default
739 choice and suitable for most users). This will result in a "3GB/1GB"
740 split: 3GB are mapped so that each process sees a 3GB virtual memory
741 space and the remaining part of the 4GB virtual memory space is used
742 by the kernel to permanently map as much physical memory as
745 If the machine has between 1 and 4 Gigabytes physical RAM, then
748 If more than 4 Gigabytes is used then answer "64GB" here. This
749 selection turns Intel PAE (Physical Address Extension) mode on.
750 PAE implements 3-level paging on IA32 processors. PAE is fully
751 supported by Linux, PAE mode is implemented on all recent Intel
752 processors (Pentium Pro and better). NOTE: If you say "64GB" here,
753 then the kernel will not boot on CPUs that don't support PAE!
755 The actual amount of total physical memory will either be
756 auto detected or can be forced by using a kernel command line option
757 such as "mem=256M". (Try "man bootparam" or see the documentation of
758 your boot loader (lilo or loadlin) about how to pass options to the
759 kernel at boot time.)
761 If unsure, say "off".
765 depends on !X86_NUMAQ
767 Select this if you have a 32-bit processor and between 1 and 4
768 gigabytes of physical RAM.
772 depends on !M386 && !M486
775 Select this if you have a 32-bit processor and more than 4
776 gigabytes of physical RAM.
781 depends on EXPERIMENTAL
782 prompt "Memory split" if EMBEDDED
786 Select the desired split between kernel and user memory.
788 If the address range available to the kernel is less than the
789 physical memory installed, the remaining memory will be available
790 as "high memory". Accessing high memory is a little more costly
791 than low memory, as it needs to be mapped into the kernel first.
792 Note that increasing the kernel address space limits the range
793 available to user programs, making the address space there
794 tighter. Selecting anything other than the default 3G/1G split
795 will also likely make your kernel incompatible with binary-only
798 If you are not absolutely sure what you are doing, leave this
802 bool "3G/1G user/kernel split"
803 config VMSPLIT_3G_OPT
805 bool "3G/1G user/kernel split (for full 1G low memory)"
807 bool "2G/2G user/kernel split"
808 config VMSPLIT_2G_OPT
810 bool "2G/2G user/kernel split (for full 2G low memory)"
812 bool "1G/3G user/kernel split"
817 default 0xB0000000 if VMSPLIT_3G_OPT
818 default 0x80000000 if VMSPLIT_2G
819 default 0x78000000 if VMSPLIT_2G_OPT
820 default 0x40000000 if VMSPLIT_1G
826 depends on X86_32 && (HIGHMEM64G || HIGHMEM4G)
830 prompt "PAE (Physical Address Extension) Support"
831 depends on X86_32 && !HIGHMEM4G
832 select RESOURCES_64BIT
834 PAE is required for NX support, and furthermore enables
835 larger swapspace support for non-overcommit purposes. It
836 has the cost of more pagetable lookup overhead, and also
837 consumes more pagetable space per process.
839 # Common NUMA Features
841 bool "Numa Memory Allocation and Scheduler Support (EXPERIMENTAL)"
843 depends on X86_64 || (X86_32 && HIGHMEM64G && (X86_NUMAQ || (X86_SUMMIT || X86_GENERICARCH) && ACPI) && EXPERIMENTAL)
845 default y if (X86_NUMAQ || X86_SUMMIT)
847 Enable NUMA (Non Uniform Memory Access) support.
848 The kernel will try to allocate memory used by a CPU on the
849 local memory controller of the CPU and add some more
850 NUMA awareness to the kernel.
852 For i386 this is currently highly experimental and should be only
853 used for kernel development. It might also cause boot failures.
854 For x86_64 this is recommended on all multiprocessor Opteron systems.
855 If the system is EM64T, you should say N unless your system is
858 comment "NUMA (Summit) requires SMP, 64GB highmem support, ACPI"
859 depends on X86_32 && X86_SUMMIT && (!HIGHMEM64G || !ACPI)
863 prompt "Old style AMD Opteron NUMA detection"
864 depends on X86_64 && NUMA && PCI
866 Enable K8 NUMA node topology detection. You should say Y here if
867 you have a multi processor AMD K8 system. This uses an old
868 method to read the NUMA configuration directly from the builtin
869 Northbridge of Opteron. It is recommended to use X86_64_ACPI_NUMA
870 instead, which also takes priority if both are compiled in.
872 config X86_64_ACPI_NUMA
874 prompt "ACPI NUMA detection"
875 depends on X86_64 && NUMA && ACPI && PCI
878 Enable ACPI SRAT based node topology detection.
881 bool "NUMA emulation"
882 depends on X86_64 && NUMA
884 Enable NUMA emulation. A flat machine will be split
885 into virtual nodes when booted with "numa=fake=N", where N is the
886 number of nodes. This is only useful for debugging.
891 default "6" if X86_64
892 default "4" if X86_NUMAQ
894 depends on NEED_MULTIPLE_NODES
896 config HAVE_ARCH_BOOTMEM_NODE
898 depends on X86_32 && NUMA
900 config ARCH_HAVE_MEMORY_PRESENT
902 depends on X86_32 && DISCONTIGMEM
904 config NEED_NODE_MEMMAP_SIZE
906 depends on X86_32 && (DISCONTIGMEM || SPARSEMEM)
908 config HAVE_ARCH_ALLOC_REMAP
910 depends on X86_32 && NUMA
912 config ARCH_FLATMEM_ENABLE
914 depends on X86_32 && ARCH_SELECT_MEMORY_MODEL && X86_PC && !NUMA
916 config ARCH_DISCONTIGMEM_ENABLE
918 depends on NUMA && X86_32
920 config ARCH_DISCONTIGMEM_DEFAULT
922 depends on NUMA && X86_32
924 config ARCH_SPARSEMEM_DEFAULT
928 config ARCH_SPARSEMEM_ENABLE
930 depends on X86_64 || NUMA || (EXPERIMENTAL && X86_PC)
931 select SPARSEMEM_STATIC if X86_32
932 select SPARSEMEM_VMEMMAP_ENABLE if X86_64
934 config ARCH_SELECT_MEMORY_MODEL
936 depends on ARCH_SPARSEMEM_ENABLE
938 config ARCH_MEMORY_PROBE
940 depends on MEMORY_HOTPLUG
945 bool "Allocate 3rd-level pagetables from highmem"
946 depends on X86_32 && (HIGHMEM4G || HIGHMEM64G)
948 The VM uses one page table entry for each page of physical memory.
949 For systems with a lot of RAM, this can be wasteful of precious
950 low memory. Setting this option will put user-space page table
951 entries in high memory.
953 config MATH_EMULATION
955 prompt "Math emulation" if X86_32
957 Linux can emulate a math coprocessor (used for floating point
958 operations) if you don't have one. 486DX and Pentium processors have
959 a math coprocessor built in, 486SX and 386 do not, unless you added
960 a 487DX or 387, respectively. (The messages during boot time can
961 give you some hints here ["man dmesg"].) Everyone needs either a
962 coprocessor or this emulation.
964 If you don't have a math coprocessor, you need to say Y here; if you
965 say Y here even though you have a coprocessor, the coprocessor will
966 be used nevertheless. (This behavior can be changed with the kernel
967 command line option "no387", which comes handy if your coprocessor
968 is broken. Try "man bootparam" or see the documentation of your boot
969 loader (lilo or loadlin) about how to pass options to the kernel at
970 boot time.) This means that it is a good idea to say Y here if you
971 intend to use this kernel on different machines.
973 More information about the internals of the Linux math coprocessor
974 emulation can be found in <file:arch/x86/math-emu/README>.
976 If you are not sure, say Y; apart from resulting in a 66 KB bigger
977 kernel, it won't hurt.
980 bool "MTRR (Memory Type Range Register) support"
982 On Intel P6 family processors (Pentium Pro, Pentium II and later)
983 the Memory Type Range Registers (MTRRs) may be used to control
984 processor access to memory ranges. This is most useful if you have
985 a video (VGA) card on a PCI or AGP bus. Enabling write-combining
986 allows bus write transfers to be combined into a larger transfer
987 before bursting over the PCI/AGP bus. This can increase performance
988 of image write operations 2.5 times or more. Saying Y here creates a
989 /proc/mtrr file which may be used to manipulate your processor's
990 MTRRs. Typically the X server should use this.
992 This code has a reasonably generic interface so that similar
993 control registers on other processors can be easily supported
996 The Cyrix 6x86, 6x86MX and M II processors have Address Range
997 Registers (ARRs) which provide a similar functionality to MTRRs. For
998 these, the ARRs are used to emulate the MTRRs.
999 The AMD K6-2 (stepping 8 and above) and K6-3 processors have two
1000 MTRRs. The Centaur C6 (WinChip) has 8 MCRs, allowing
1001 write-combining. All of these processors are supported by this code
1002 and it makes sense to say Y here if you have one of them.
1004 Saying Y here also fixes a problem with buggy SMP BIOSes which only
1005 set the MTRRs for the boot CPU and not for the secondary CPUs. This
1006 can lead to all sorts of problems, so it's good to say Y here.
1008 You can safely say Y even if your machine doesn't have MTRRs, you'll
1009 just add about 9 KB to your kernel.
1011 See <file:Documentation/mtrr.txt> for more information.
1015 prompt "EFI runtime service support"
1018 This enables the kernel to use EFI runtime services that are
1019 available (such as the EFI variable services).
1021 This option is only useful on systems that have EFI firmware.
1022 In addition, you should use the latest ELILO loader available
1023 at <http://elilo.sourceforge.net> in order to take advantage
1024 of EFI runtime services. However, even with this option, the
1025 resultant kernel should continue to boot on existing non-EFI
1030 prompt "Enable kernel irq balancing"
1031 depends on X86_32 && SMP && X86_IO_APIC
1033 The default yes will allow the kernel to do irq load balancing.
1034 Saying no will keep the kernel from doing irq load balancing.
1038 prompt "Enable seccomp to safely compute untrusted bytecode"
1041 This kernel feature is useful for number crunching applications
1042 that may need to compute untrusted bytecode during their
1043 execution. By using pipes or other transports made available to
1044 the process as file descriptors supporting the read/write
1045 syscalls, it's possible to isolate those applications in
1046 their own address space using seccomp. Once seccomp is
1047 enabled via /proc/<pid>/seccomp, it cannot be disabled
1048 and the task is only allowed to execute a few safe syscalls
1049 defined by each seccomp mode.
1051 If unsure, say Y. Only embedded should say N here.
1053 config CC_STACKPROTECTOR
1054 bool "Enable -fstack-protector buffer overflow detection (EXPERIMENTAL)"
1055 depends on X86_64 && EXPERIMENTAL && BROKEN
1057 This option turns on the -fstack-protector GCC feature. This
1058 feature puts, at the beginning of critical functions, a canary
1059 value on the stack just before the return address, and validates
1060 the value just before actually returning. Stack based buffer
1061 overflows (that need to overwrite this return address) now also
1062 overwrite the canary, which gets detected and the attack is then
1063 neutralized via a kernel panic.
1065 This feature requires gcc version 4.2 or above, or a distribution
1066 gcc with the feature backported. Older versions are automatically
1067 detected and for those versions, this configuration option is ignored.
1069 config CC_STACKPROTECTOR_ALL
1070 bool "Use stack-protector for all functions"
1071 depends on CC_STACKPROTECTOR
1073 Normally, GCC only inserts the canary value protection for
1074 functions that use large-ish on-stack buffers. By enabling
1075 this option, GCC will be asked to do this for ALL functions.
1077 source kernel/Kconfig.hz
1080 bool "kexec system call"
1082 kexec is a system call that implements the ability to shutdown your
1083 current kernel, and to start another kernel. It is like a reboot
1084 but it is independent of the system firmware. And like a reboot
1085 you can start any kernel with it, not just Linux.
1087 The name comes from the similarity to the exec system call.
1089 It is an ongoing process to be certain the hardware in a machine
1090 is properly shutdown, so do not be surprised if this code does not
1091 initially work for you. It may help to enable device hotplugging
1092 support. As of this writing the exact hardware interface is
1093 strongly in flux, so no good recommendation can be made.
1096 bool "kernel crash dumps (EXPERIMENTAL)"
1097 depends on EXPERIMENTAL
1098 depends on X86_64 || (X86_32 && HIGHMEM)
1100 Generate crash dump after being started by kexec.
1101 This should be normally only set in special crash dump kernels
1102 which are loaded in the main kernel with kexec-tools into
1103 a specially reserved region and then later executed after
1104 a crash by kdump/kexec. The crash dump kernel must be compiled
1105 to a memory address not used by the main kernel or BIOS using
1106 PHYSICAL_START, or it must be built as a relocatable image
1107 (CONFIG_RELOCATABLE=y).
1108 For more details see Documentation/kdump/kdump.txt
1110 config PHYSICAL_START
1111 hex "Physical address where the kernel is loaded" if (EMBEDDED || CRASH_DUMP)
1112 default "0x1000000" if X86_NUMAQ
1113 default "0x200000" if X86_64
1116 This gives the physical address where the kernel is loaded.
1118 If kernel is a not relocatable (CONFIG_RELOCATABLE=n) then
1119 bzImage will decompress itself to above physical address and
1120 run from there. Otherwise, bzImage will run from the address where
1121 it has been loaded by the boot loader and will ignore above physical
1124 In normal kdump cases one does not have to set/change this option
1125 as now bzImage can be compiled as a completely relocatable image
1126 (CONFIG_RELOCATABLE=y) and be used to load and run from a different
1127 address. This option is mainly useful for the folks who don't want
1128 to use a bzImage for capturing the crash dump and want to use a
1129 vmlinux instead. vmlinux is not relocatable hence a kernel needs
1130 to be specifically compiled to run from a specific memory area
1131 (normally a reserved region) and this option comes handy.
1133 So if you are using bzImage for capturing the crash dump, leave
1134 the value here unchanged to 0x100000 and set CONFIG_RELOCATABLE=y.
1135 Otherwise if you plan to use vmlinux for capturing the crash dump
1136 change this value to start of the reserved region (Typically 16MB
1137 0x1000000). In other words, it can be set based on the "X" value as
1138 specified in the "crashkernel=YM@XM" command line boot parameter
1139 passed to the panic-ed kernel. Typically this parameter is set as
1140 crashkernel=64M@16M. Please take a look at
1141 Documentation/kdump/kdump.txt for more details about crash dumps.
1143 Usage of bzImage for capturing the crash dump is recommended as
1144 one does not have to build two kernels. Same kernel can be used
1145 as production kernel and capture kernel. Above option should have
1146 gone away after relocatable bzImage support is introduced. But it
1147 is present because there are users out there who continue to use
1148 vmlinux for dump capture. This option should go away down the
1151 Don't change this unless you know what you are doing.
1154 bool "Build a relocatable kernel (EXPERIMENTAL)"
1155 depends on EXPERIMENTAL
1157 This builds a kernel image that retains relocation information
1158 so it can be loaded someplace besides the default 1MB.
1159 The relocations tend to make the kernel binary about 10% larger,
1160 but are discarded at runtime.
1162 One use is for the kexec on panic case where the recovery kernel
1163 must live at a different physical address than the primary
1166 Note: If CONFIG_RELOCATABLE=y, then the kernel runs from the address
1167 it has been loaded at and the compile time physical address
1168 (CONFIG_PHYSICAL_START) is ignored.
1170 config PHYSICAL_ALIGN
1172 prompt "Alignment value to which kernel should be aligned" if X86_32
1173 default "0x100000" if X86_32
1174 default "0x200000" if X86_64
1175 range 0x2000 0x400000
1177 This value puts the alignment restrictions on physical address
1178 where kernel is loaded and run from. Kernel is compiled for an
1179 address which meets above alignment restriction.
1181 If bootloader loads the kernel at a non-aligned address and
1182 CONFIG_RELOCATABLE is set, kernel will move itself to nearest
1183 address aligned to above value and run from there.
1185 If bootloader loads the kernel at a non-aligned address and
1186 CONFIG_RELOCATABLE is not set, kernel will ignore the run time
1187 load address and decompress itself to the address it has been
1188 compiled for and run from there. The address for which kernel is
1189 compiled already meets above alignment restrictions. Hence the
1190 end result is that kernel runs from a physical address meeting
1191 above alignment restrictions.
1193 Don't change this unless you know what you are doing.
1196 bool "Support for suspend on SMP and hot-pluggable CPUs (EXPERIMENTAL)"
1197 depends on SMP && HOTPLUG && EXPERIMENTAL && !X86_VOYAGER
1199 Say Y here to experiment with turning CPUs off and on, and to
1200 enable suspend on SMP systems. CPUs can be controlled through
1201 /sys/devices/system/cpu.
1202 Say N if you want to disable CPU hotplug and don't need to
1207 prompt "Compat VDSO support"
1208 depends on X86_32 || IA32_EMULATION
1210 Map the 32-bit VDSO to the predictable old-style address too.
1212 Say N here if you are running a sufficiently recent glibc
1213 version (2.3.3 or later), to remove the high-mapped
1214 VDSO mapping and to exclusively use the randomized VDSO.
1220 config ARCH_ENABLE_MEMORY_HOTPLUG
1222 depends on X86_64 || (X86_32 && HIGHMEM)
1224 config HAVE_ARCH_EARLY_PFN_TO_NID
1228 menu "Power management options"
1229 depends on !X86_VOYAGER
1231 config ARCH_HIBERNATION_HEADER
1233 depends on X86_64 && HIBERNATION
1235 source "kernel/power/Kconfig"
1237 source "drivers/acpi/Kconfig"
1242 depends on APM || APM_MODULE
1245 tristate "APM (Advanced Power Management) BIOS support"
1246 depends on X86_32 && PM_SLEEP && !X86_VISWS
1248 APM is a BIOS specification for saving power using several different
1249 techniques. This is mostly useful for battery powered laptops with
1250 APM compliant BIOSes. If you say Y here, the system time will be
1251 reset after a RESUME operation, the /proc/apm device will provide
1252 battery status information, and user-space programs will receive
1253 notification of APM "events" (e.g. battery status change).
1255 If you select "Y" here, you can disable actual use of the APM
1256 BIOS by passing the "apm=off" option to the kernel at boot time.
1258 Note that the APM support is almost completely disabled for
1259 machines with more than one CPU.
1261 In order to use APM, you will need supporting software. For location
1262 and more information, read <file:Documentation/pm.txt> and the
1263 Battery Powered Linux mini-HOWTO, available from
1264 <http://www.tldp.org/docs.html#howto>.
1266 This driver does not spin down disk drives (see the hdparm(8)
1267 manpage ("man 8 hdparm") for that), and it doesn't turn off
1268 VESA-compliant "green" monitors.
1270 This driver does not support the TI 4000M TravelMate and the ACER
1271 486/DX4/75 because they don't have compliant BIOSes. Many "green"
1272 desktop machines also don't have compliant BIOSes, and this driver
1273 may cause those machines to panic during the boot phase.
1275 Generally, if you don't have a battery in your machine, there isn't
1276 much point in using this driver and you should say N. If you get
1277 random kernel OOPSes or reboots that don't seem to be related to
1278 anything, try disabling/enabling this option (or disabling/enabling
1281 Some other things you should try when experiencing seemingly random,
1284 1) make sure that you have enough swap space and that it is
1286 2) pass the "no-hlt" option to the kernel
1287 3) switch on floating point emulation in the kernel and pass
1288 the "no387" option to the kernel
1289 4) pass the "floppy=nodma" option to the kernel
1290 5) pass the "mem=4M" option to the kernel (thereby disabling
1291 all but the first 4 MB of RAM)
1292 6) make sure that the CPU is not over clocked.
1293 7) read the sig11 FAQ at <http://www.bitwizard.nl/sig11/>
1294 8) disable the cache from your BIOS settings
1295 9) install a fan for the video card or exchange video RAM
1296 10) install a better fan for the CPU
1297 11) exchange RAM chips
1298 12) exchange the motherboard.
1300 To compile this driver as a module, choose M here: the
1301 module will be called apm.
1305 config APM_IGNORE_USER_SUSPEND
1306 bool "Ignore USER SUSPEND"
1308 This option will ignore USER SUSPEND requests. On machines with a
1309 compliant APM BIOS, you want to say N. However, on the NEC Versa M
1310 series notebooks, it is necessary to say Y because of a BIOS bug.
1312 config APM_DO_ENABLE
1313 bool "Enable PM at boot time"
1315 Enable APM features at boot time. From page 36 of the APM BIOS
1316 specification: "When disabled, the APM BIOS does not automatically
1317 power manage devices, enter the Standby State, enter the Suspend
1318 State, or take power saving steps in response to CPU Idle calls."
1319 This driver will make CPU Idle calls when Linux is idle (unless this
1320 feature is turned off -- see "Do CPU IDLE calls", below). This
1321 should always save battery power, but more complicated APM features
1322 will be dependent on your BIOS implementation. You may need to turn
1323 this option off if your computer hangs at boot time when using APM
1324 support, or if it beeps continuously instead of suspending. Turn
1325 this off if you have a NEC UltraLite Versa 33/C or a Toshiba
1326 T400CDT. This is off by default since most machines do fine without
1330 bool "Make CPU Idle calls when idle"
1332 Enable calls to APM CPU Idle/CPU Busy inside the kernel's idle loop.
1333 On some machines, this can activate improved power savings, such as
1334 a slowed CPU clock rate, when the machine is idle. These idle calls
1335 are made after the idle loop has run for some length of time (e.g.,
1336 333 mS). On some machines, this will cause a hang at boot time or
1337 whenever the CPU becomes idle. (On machines with more than one CPU,
1338 this option does nothing.)
1340 config APM_DISPLAY_BLANK
1341 bool "Enable console blanking using APM"
1343 Enable console blanking using the APM. Some laptops can use this to
1344 turn off the LCD backlight when the screen blanker of the Linux
1345 virtual console blanks the screen. Note that this is only used by
1346 the virtual console screen blanker, and won't turn off the backlight
1347 when using the X Window system. This also doesn't have anything to
1348 do with your VESA-compliant power-saving monitor. Further, this
1349 option doesn't work for all laptops -- it might not turn off your
1350 backlight at all, or it might print a lot of errors to the console,
1351 especially if you are using gpm.
1353 config APM_ALLOW_INTS
1354 bool "Allow interrupts during APM BIOS calls"
1356 Normally we disable external interrupts while we are making calls to
1357 the APM BIOS as a measure to lessen the effects of a badly behaving
1358 BIOS implementation. The BIOS should reenable interrupts if it
1359 needs to. Unfortunately, some BIOSes do not -- especially those in
1360 many of the newer IBM Thinkpads. If you experience hangs when you
1361 suspend, try setting this to Y. Otherwise, say N.
1363 config APM_REAL_MODE_POWER_OFF
1364 bool "Use real mode APM BIOS call to power off"
1366 Use real mode APM BIOS calls to switch off the computer. This is
1367 a work-around for a number of buggy BIOSes. Switch this option on if
1368 your computer crashes instead of powering off properly.
1372 source "arch/x86/kernel/cpu/cpufreq/Kconfig"
1374 source "drivers/cpuidle/Kconfig"
1379 menu "Bus options (PCI etc.)"
1382 bool "PCI support" if !X86_VISWS
1383 depends on !X86_VOYAGER
1385 select ARCH_SUPPORTS_MSI if (X86_LOCAL_APIC && X86_IO_APIC)
1387 Find out whether you have a PCI motherboard. PCI is the name of a
1388 bus system, i.e. the way the CPU talks to the other stuff inside
1389 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
1390 VESA. If you have PCI, say Y, otherwise N.
1393 prompt "PCI access mode"
1394 depends on X86_32 && PCI && !X86_VISWS
1397 On PCI systems, the BIOS can be used to detect the PCI devices and
1398 determine their configuration. However, some old PCI motherboards
1399 have BIOS bugs and may crash if this is done. Also, some embedded
1400 PCI-based systems don't have any BIOS at all. Linux can also try to
1401 detect the PCI hardware directly without using the BIOS.
1403 With this option, you can specify how Linux should detect the
1404 PCI devices. If you choose "BIOS", the BIOS will be used,
1405 if you choose "Direct", the BIOS won't be used, and if you
1406 choose "MMConfig", then PCI Express MMCONFIG will be used.
1407 If you choose "Any", the kernel will try MMCONFIG, then the
1408 direct access method and falls back to the BIOS if that doesn't
1409 work. If unsure, go with the default, which is "Any".
1414 config PCI_GOMMCONFIG
1427 depends on X86_32 && !X86_VISWS && PCI && (PCI_GOBIOS || PCI_GOANY)
1429 # x86-64 doesn't support PCI BIOS access from long mode so always go direct.
1432 depends on PCI && (X86_64 || (PCI_GODIRECT || PCI_GOANY) || X86_VISWS)
1436 depends on X86_32 && PCI && ACPI && (PCI_GOMMCONFIG || PCI_GOANY)
1443 bool "Support mmconfig PCI config space access"
1444 depends on X86_64 && PCI && ACPI
1447 bool "Support for DMA Remapping Devices (EXPERIMENTAL)"
1448 depends on X86_64 && PCI_MSI && ACPI && EXPERIMENTAL
1450 DMA remapping (DMAR) devices support enables independent address
1451 translations for Direct Memory Access (DMA) from devices.
1452 These DMA remapping devices are reported via ACPI tables
1453 and include PCI device scope covered by these DMA
1458 prompt "Support for Graphics workaround"
1461 Current Graphics drivers tend to use physical address
1462 for DMA and avoid using DMA APIs. Setting this config
1463 option permits the IOMMU driver to set a unity map for
1464 all the OS-visible memory. Hence the driver can continue
1465 to use physical addresses for DMA.
1467 config DMAR_FLOPPY_WA
1471 Floppy disk drivers are know to bypass DMA API calls
1472 thereby failing to work when IOMMU is enabled. This
1473 workaround will setup a 1:1 mapping for the first
1474 16M to make floppy (an ISA device) work.
1476 source "drivers/pci/pcie/Kconfig"
1478 source "drivers/pci/Kconfig"
1480 # x86_64 have no ISA slots, but do have ISA-style DMA.
1488 depends on !(X86_VOYAGER || X86_VISWS)
1490 Find out whether you have ISA slots on your motherboard. ISA is the
1491 name of a bus system, i.e. the way the CPU talks to the other stuff
1492 inside your box. Other bus systems are PCI, EISA, MicroChannel
1493 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
1494 newer boards don't support it. If you have ISA, say Y, otherwise N.
1500 The Extended Industry Standard Architecture (EISA) bus was
1501 developed as an open alternative to the IBM MicroChannel bus.
1503 The EISA bus provided some of the features of the IBM MicroChannel
1504 bus while maintaining backward compatibility with cards made for
1505 the older ISA bus. The EISA bus saw limited use between 1988 and
1506 1995 when it was made obsolete by the PCI bus.
1508 Say Y here if you are building a kernel for an EISA-based machine.
1512 source "drivers/eisa/Kconfig"
1515 bool "MCA support" if !(X86_VISWS || X86_VOYAGER)
1516 default y if X86_VOYAGER
1518 MicroChannel Architecture is found in some IBM PS/2 machines and
1519 laptops. It is a bus system similar to PCI or ISA. See
1520 <file:Documentation/mca.txt> (and especially the web page given
1521 there) before attempting to build an MCA bus kernel.
1523 source "drivers/mca/Kconfig"
1526 tristate "NatSemi SCx200 support"
1527 depends on !X86_VOYAGER
1529 This provides basic support for National Semiconductor's
1530 (now AMD's) Geode processors. The driver probes for the
1531 PCI-IDs of several on-chip devices, so its a good dependency
1532 for other scx200_* drivers.
1534 If compiled as a module, the driver is named scx200.
1536 config SCx200HR_TIMER
1537 tristate "NatSemi SCx200 27MHz High-Resolution Timer Support"
1538 depends on SCx200 && GENERIC_TIME
1541 This driver provides a clocksource built upon the on-chip
1542 27MHz high-resolution timer. Its also a workaround for
1543 NSC Geode SC-1100's buggy TSC, which loses time when the
1544 processor goes idle (as is done by the scheduler). The
1545 other workaround is idle=poll boot option.
1547 config GEODE_MFGPT_TIMER
1549 prompt "Geode Multi-Function General Purpose Timer (MFGPT) events"
1550 depends on MGEODE_LX && GENERIC_TIME && GENERIC_CLOCKEVENTS
1552 This driver provides a clock event source based on the MFGPT
1553 timer(s) in the CS5535 and CS5536 companion chip for the geode.
1554 MFGPTs have a better resolution and max interval than the
1555 generic PIT, and are suitable for use as high-res timers.
1561 depends on AGP_AMD64 || (X86_64 && (GART_IOMMU || (PCI && NUMA)))
1563 source "drivers/pcmcia/Kconfig"
1565 source "drivers/pci/hotplug/Kconfig"
1570 menu "Executable file formats / Emulations"
1572 source "fs/Kconfig.binfmt"
1574 config IA32_EMULATION
1575 bool "IA32 Emulation"
1577 select COMPAT_BINFMT_ELF
1579 Include code to run 32-bit programs under a 64-bit kernel. You should
1580 likely turn this on, unless you're 100% sure that you don't have any
1581 32-bit programs left.
1584 tristate "IA32 a.out support"
1585 depends on IA32_EMULATION && ARCH_SUPPORTS_AOUT
1587 Support old a.out binaries in the 32bit emulation.
1591 depends on IA32_EMULATION
1593 config COMPAT_FOR_U64_ALIGNMENT
1597 config SYSVIPC_COMPAT
1599 depends on X86_64 && COMPAT && SYSVIPC
1604 source "net/Kconfig"
1606 source "drivers/Kconfig"
1608 source "drivers/firmware/Kconfig"
1612 source "arch/x86/Kconfig.debug"
1614 source "security/Kconfig"
1616 source "crypto/Kconfig"
1618 source "arch/x86/kvm/Kconfig"
1620 source "lib/Kconfig"
projects / linux-2.6 / blob