| blob | d986769a7d9031f244337f413c8b07f7dd515a61 |
1 # x86 configuration
2 mainmenu "Linux Kernel Configuration for x86"
4 # Select 32 or 64 bit
5 config 64BIT
6 bool "64-bit kernel" if ARCH = "x86"
7 default ARCH = "x86_64"
8 ---help---
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
12 config X86_32
13 def_bool !64BIT
15 config X86_64
16 def_bool 64BIT
18 ### Arch settings
19 config X86
20 def_bool y
21 select HAVE_AOUT if X86_32
22 select HAVE_READQ
23 select HAVE_WRITEQ
24 select HAVE_UNSTABLE_SCHED_CLOCK
25 select HAVE_IDE
26 select HAVE_OPROFILE
27 select HAVE_IOREMAP_PROT
28 select HAVE_KPROBES
29 select ARCH_WANT_OPTIONAL_GPIOLIB
30 select ARCH_WANT_FRAME_POINTERS
31 select HAVE_KRETPROBES
32 select HAVE_FTRACE_MCOUNT_RECORD
33 select HAVE_DYNAMIC_FTRACE
34 select HAVE_FUNCTION_TRACER
35 select HAVE_FUNCTION_GRAPH_TRACER
36 select HAVE_FUNCTION_TRACE_MCOUNT_TEST
37 select HAVE_FTRACE_NMI_ENTER if DYNAMIC_FTRACE
38 select HAVE_FTRACE_SYSCALLS
39 select HAVE_KVM
40 select HAVE_ARCH_KGDB
41 select HAVE_ARCH_TRACEHOOK
42 select HAVE_GENERIC_DMA_COHERENT if X86_32
43 select HAVE_EFFICIENT_UNALIGNED_ACCESS
44 select USER_STACKTRACE_SUPPORT
45 select HAVE_DMA_API_DEBUG
46 select HAVE_KERNEL_GZIP
47 select HAVE_KERNEL_BZIP2
48 select HAVE_KERNEL_LZMA
50 config OUTPUT_FORMAT
51 string
52 default "elf32-i386" if X86_32
53 default "elf64-x86-64" if X86_64
55 config ARCH_DEFCONFIG
56 string
57 default "arch/x86/configs/i386_defconfig" if X86_32
58 default "arch/x86/configs/x86_64_defconfig" if X86_64
60 config GENERIC_TIME
61 def_bool y
63 config GENERIC_CMOS_UPDATE
64 def_bool y
66 config CLOCKSOURCE_WATCHDOG
67 def_bool y
69 config GENERIC_CLOCKEVENTS
70 def_bool y
72 config GENERIC_CLOCKEVENTS_BROADCAST
73 def_bool y
74 depends on X86_64 || (X86_32 && X86_LOCAL_APIC)
76 config LOCKDEP_SUPPORT
77 def_bool y
79 config STACKTRACE_SUPPORT
80 def_bool y
82 config HAVE_LATENCYTOP_SUPPORT
83 def_bool y
85 config FAST_CMPXCHG_LOCAL
86 bool
87 default y
89 config MMU
90 def_bool y
92 config ZONE_DMA
93 def_bool y
95 config SBUS
96 bool
98 config GENERIC_ISA_DMA
99 def_bool y
101 config GENERIC_IOMAP
102 def_bool y
104 config GENERIC_BUG
105 def_bool y
106 depends on BUG
107 select GENERIC_BUG_RELATIVE_POINTERS if X86_64
109 config GENERIC_BUG_RELATIVE_POINTERS
110 bool
112 config GENERIC_HWEIGHT
113 def_bool y
115 config GENERIC_GPIO
116 bool
118 config ARCH_MAY_HAVE_PC_FDC
119 def_bool y
121 config RWSEM_GENERIC_SPINLOCK
122 def_bool !X86_XADD
124 config RWSEM_XCHGADD_ALGORITHM
125 def_bool X86_XADD
127 config ARCH_HAS_CPU_IDLE_WAIT
128 def_bool y
130 config GENERIC_CALIBRATE_DELAY
131 def_bool y
133 config GENERIC_TIME_VSYSCALL
134 bool
135 default X86_64
137 config ARCH_HAS_CPU_RELAX
138 def_bool y
140 config ARCH_HAS_DEFAULT_IDLE
141 def_bool y
143 config ARCH_HAS_CACHE_LINE_SIZE
144 def_bool y
146 config HAVE_SETUP_PER_CPU_AREA
147 def_bool y
149 config HAVE_DYNAMIC_PER_CPU_AREA
150 def_bool y
152 config HAVE_CPUMASK_OF_CPU_MAP
153 def_bool X86_64_SMP
155 config ARCH_HIBERNATION_POSSIBLE
156 def_bool y
158 config ARCH_SUSPEND_POSSIBLE
159 def_bool y
161 config ZONE_DMA32
162 bool
163 default X86_64
165 config ARCH_POPULATES_NODE_MAP
166 def_bool y
168 config AUDIT_ARCH
169 bool
170 default X86_64
172 config ARCH_SUPPORTS_OPTIMIZED_INLINING
173 def_bool y
175 config ARCH_SUPPORTS_DEBUG_PAGEALLOC
176 def_bool y
178 # Use the generic interrupt handling code in kernel/irq/:
179 config GENERIC_HARDIRQS
180 bool
181 default y
183 config GENERIC_HARDIRQS_NO__DO_IRQ
184 def_bool y
186 config GENERIC_IRQ_PROBE
187 bool
188 default y
190 config GENERIC_PENDING_IRQ
191 bool
192 depends on GENERIC_HARDIRQS && SMP
193 default y
195 config USE_GENERIC_SMP_HELPERS
196 def_bool y
197 depends on SMP
199 config X86_32_SMP
200 def_bool y
201 depends on X86_32 && SMP
203 config X86_64_SMP
204 def_bool y
205 depends on X86_64 && SMP
207 config X86_HT
208 bool
209 depends on SMP
210 default y
212 config X86_TRAMPOLINE
213 bool
214 depends on SMP || (64BIT && ACPI_SLEEP)
215 default y
217 config X86_32_LAZY_GS
218 def_bool y
219 depends on X86_32 && !CC_STACKPROTECTOR
221 config KTIME_SCALAR
222 def_bool X86_32
223 source "init/Kconfig"
224 source "kernel/Kconfig.freezer"
226 menu "Processor type and features"
228 source "kernel/time/Kconfig"
230 config SMP
231 bool "Symmetric multi-processing support"
232 ---help---
233 This enables support for systems with more than one CPU. If you have
234 a system with only one CPU, like most personal computers, say N. If
235 you have a system with more than one CPU, say Y.
237 If you say N here, the kernel will run on single and multiprocessor
238 machines, but will use only one CPU of a multiprocessor machine. If
239 you say Y here, the kernel will run on many, but not all,
240 singleprocessor machines. On a singleprocessor machine, the kernel
241 will run faster if you say N here.
243 Note that if you say Y here and choose architecture "586" or
244 "Pentium" under "Processor family", the kernel will not work on 486
245 architectures. Similarly, multiprocessor kernels for the "PPro"
246 architecture may not work on all Pentium based boards.
248 People using multiprocessor machines who say Y here should also say
249 Y to "Enhanced Real Time Clock Support", below. The "Advanced Power
250 Management" code will be disabled if you say Y here.
252 See also <file:Documentation/i386/IO-APIC.txt>,
253 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
254 <http://www.tldp.org/docs.html#howto>.
256 If you don't know what to do here, say N.
258 config X86_X2APIC
259 bool "Support x2apic"
260 depends on X86_LOCAL_APIC && X86_64 && INTR_REMAP
261 ---help---
262 This enables x2apic support on CPUs that have this feature.
264 This allows 32-bit apic IDs (so it can support very large systems),
265 and accesses the local apic via MSRs not via mmio.
267 If you don't know what to do here, say N.
269 config SPARSE_IRQ
270 bool "Support sparse irq numbering"
271 depends on PCI_MSI || HT_IRQ
272 ---help---
273 This enables support for sparse irqs. This is useful for distro
274 kernels that want to define a high CONFIG_NR_CPUS value but still
275 want to have low kernel memory footprint on smaller machines.
277 ( Sparse IRQs can also be beneficial on NUMA boxes, as they spread
278 out the irq_desc[] array in a more NUMA-friendly way. )
280 If you don't know what to do here, say N.
282 config NUMA_IRQ_DESC
283 def_bool y
284 depends on SPARSE_IRQ && NUMA
286 config X86_MPPARSE
287 bool "Enable MPS table" if ACPI
288 default y
289 depends on X86_LOCAL_APIC
290 ---help---
291 For old smp systems that do not have proper acpi support. Newer systems
292 (esp with 64bit cpus) with acpi support, MADT and DSDT will override it
294 config X86_BIGSMP
295 bool "Support for big SMP systems with more than 8 CPUs"
296 depends on X86_32 && SMP
297 ---help---
298 This option is needed for the systems that have more than 8 CPUs
300 if X86_32
301 config X86_EXTENDED_PLATFORM
302 bool "Support for extended (non-PC) x86 platforms"
303 default y
304 ---help---
305 If you disable this option then the kernel will only support
306 standard PC platforms. (which covers the vast majority of
307 systems out there.)
309 If you enable this option then you'll be able to select support
310 for the following (non-PC) 32 bit x86 platforms:
311 AMD Elan
312 NUMAQ (IBM/Sequent)
313 RDC R-321x SoC
314 SGI 320/540 (Visual Workstation)
315 Summit/EXA (IBM x440)
316 Unisys ES7000 IA32 series
318 If you have one of these systems, or if you want to build a
319 generic distribution kernel, say Y here - otherwise say N.
320 endif
322 if X86_64
323 config X86_EXTENDED_PLATFORM
324 bool "Support for extended (non-PC) x86 platforms"
325 default y
326 ---help---
327 If you disable this option then the kernel will only support
328 standard PC platforms. (which covers the vast majority of
329 systems out there.)
331 If you enable this option then you'll be able to select support
332 for the following (non-PC) 64 bit x86 platforms:
333 ScaleMP vSMP
334 SGI Ultraviolet
336 If you have one of these systems, or if you want to build a
337 generic distribution kernel, say Y here - otherwise say N.
338 endif
339 # This is an alphabetically sorted list of 64 bit extended platforms
340 # Please maintain the alphabetic order if and when there are additions
342 config X86_VSMP
343 bool "ScaleMP vSMP"
344 select PARAVIRT
345 depends on X86_64 && PCI
346 depends on X86_EXTENDED_PLATFORM
347 ---help---
348 Support for ScaleMP vSMP systems. Say 'Y' here if this kernel is
349 supposed to run on these EM64T-based machines. Only choose this option
350 if you have one of these machines.
352 config X86_UV
353 bool "SGI Ultraviolet"
354 depends on X86_64
355 depends on X86_EXTENDED_PLATFORM
356 depends on NUMA
357 depends on X86_X2APIC
358 ---help---
359 This option is needed in order to support SGI Ultraviolet systems.
360 If you don't have one of these, you should say N here.
362 # Following is an alphabetically sorted list of 32 bit extended platforms
363 # Please maintain the alphabetic order if and when there are additions
365 config X86_ELAN
366 bool "AMD Elan"
367 depends on X86_32
368 depends on X86_EXTENDED_PLATFORM
369 ---help---
370 Select this for an AMD Elan processor.
372 Do not use this option for K6/Athlon/Opteron processors!
374 If unsure, choose "PC-compatible" instead.
376 config X86_RDC321X
377 bool "RDC R-321x SoC"
378 depends on X86_32
379 depends on X86_EXTENDED_PLATFORM
380 select M486
381 select X86_REBOOTFIXUPS
382 ---help---
383 This option is needed for RDC R-321x system-on-chip, also known
384 as R-8610-(G).
385 If you don't have one of these chips, you should say N here.
387 config X86_32_NON_STANDARD
388 bool "Support non-standard 32-bit SMP architectures"
389 depends on X86_32 && SMP
390 depends on X86_EXTENDED_PLATFORM
391 ---help---
392 This option compiles in the NUMAQ, Summit, bigsmp, ES7000, default
393 subarchitectures. It is intended for a generic binary kernel.
394 if you select them all, kernel will probe it one by one. and will
395 fallback to default.
397 # Alphabetically sorted list of Non standard 32 bit platforms
399 config X86_NUMAQ
400 bool "NUMAQ (IBM/Sequent)"
401 depends on X86_32_NON_STANDARD
402 select NUMA
403 select X86_MPPARSE
404 ---help---
405 This option is used for getting Linux to run on a NUMAQ (IBM/Sequent)
406 NUMA multiquad box. This changes the way that processors are
407 bootstrapped, and uses Clustered Logical APIC addressing mode instead
408 of Flat Logical. You will need a new lynxer.elf file to flash your
409 firmware with - send email to <Martin.Bligh@us.ibm.com>.
411 config X86_VISWS
412 bool "SGI 320/540 (Visual Workstation)"
413 depends on X86_32 && PCI && X86_MPPARSE && PCI_GODIRECT
414 depends on X86_32_NON_STANDARD
415 ---help---
416 The SGI Visual Workstation series is an IA32-based workstation
417 based on SGI systems chips with some legacy PC hardware attached.
419 Say Y here to create a kernel to run on the SGI 320 or 540.
421 A kernel compiled for the Visual Workstation will run on general
422 PCs as well. See <file:Documentation/sgi-visws.txt> for details.
424 config X86_SUMMIT
425 bool "Summit/EXA (IBM x440)"
426 depends on X86_32_NON_STANDARD
427 ---help---
428 This option is needed for IBM systems that use the Summit/EXA chipset.
429 In particular, it is needed for the x440.
431 config X86_ES7000
432 bool "Unisys ES7000 IA32 series"
433 depends on X86_32_NON_STANDARD && X86_BIGSMP
434 ---help---
435 Support for Unisys ES7000 systems. Say 'Y' here if this kernel is
436 supposed to run on an IA32-based Unisys ES7000 system.
438 config SCHED_OMIT_FRAME_POINTER
439 def_bool y
440 prompt "Single-depth WCHAN output"
441 depends on X86
442 ---help---
443 Calculate simpler /proc/<PID>/wchan values. If this option
444 is disabled then wchan values will recurse back to the
445 caller function. This provides more accurate wchan values,
446 at the expense of slightly more scheduling overhead.
448 If in doubt, say "Y".
450 menuconfig PARAVIRT_GUEST
451 bool "Paravirtualized guest support"
452 ---help---
453 Say Y here to get to see options related to running Linux under
454 various hypervisors. This option alone does not add any kernel code.
456 If you say N, all options in this submenu will be skipped and disabled.
458 if PARAVIRT_GUEST
460 source "arch/x86/xen/Kconfig"
462 config VMI
463 bool "VMI Guest support"
464 select PARAVIRT
465 depends on X86_32
466 ---help---
467 VMI provides a paravirtualized interface to the VMware ESX server
468 (it could be used by other hypervisors in theory too, but is not
469 at the moment), by linking the kernel to a GPL-ed ROM module
470 provided by the hypervisor.
472 config KVM_CLOCK
473 bool "KVM paravirtualized clock"
474 select PARAVIRT
475 select PARAVIRT_CLOCK
476 ---help---
477 Turning on this option will allow you to run a paravirtualized clock
478 when running over the KVM hypervisor. Instead of relying on a PIT
479 (or probably other) emulation by the underlying device model, the host
480 provides the guest with timing infrastructure such as time of day, and
481 system time
483 config KVM_GUEST
484 bool "KVM Guest support"
485 select PARAVIRT
486 ---help---
487 This option enables various optimizations for running under the KVM
488 hypervisor.
490 source "arch/x86/lguest/Kconfig"
492 config PARAVIRT
493 bool "Enable paravirtualization code"
494 ---help---
495 This changes the kernel so it can modify itself when it is run
496 under a hypervisor, potentially improving performance significantly
497 over full virtualization. However, when run without a hypervisor
498 the kernel is theoretically slower and slightly larger.
500 config PARAVIRT_SPINLOCKS
501 bool "Paravirtualization layer for spinlocks"
502 depends on PARAVIRT && SMP && EXPERIMENTAL
503 ---help---
504 Paravirtualized spinlocks allow a pvops backend to replace the
505 spinlock implementation with something virtualization-friendly
506 (for example, block the virtual CPU rather than spinning).
508 Unfortunately the downside is an up to 5% performance hit on
509 native kernels, with various workloads.
511 If you are unsure how to answer this question, answer N.
513 config PARAVIRT_CLOCK
514 bool
515 default n
517 endif
519 config PARAVIRT_DEBUG
520 bool "paravirt-ops debugging"
521 depends on PARAVIRT && DEBUG_KERNEL
522 ---help---
523 Enable to debug paravirt_ops internals. Specifically, BUG if
524 a paravirt_op is missing when it is called.
526 config MEMTEST
527 bool "Memtest"
528 ---help---
529 This option adds a kernel parameter 'memtest', which allows memtest
530 to be set.
531 memtest=0, mean disabled; -- default
532 memtest=1, mean do 1 test pattern;
533 ...
534 memtest=4, mean do 4 test patterns.
535 If you are unsure how to answer this question, answer N.
537 config X86_SUMMIT_NUMA
538 def_bool y
539 depends on X86_32 && NUMA && X86_32_NON_STANDARD
541 config X86_CYCLONE_TIMER
542 def_bool y
543 depends on X86_32_NON_STANDARD
545 source "arch/x86/Kconfig.cpu"
547 config HPET_TIMER
548 def_bool X86_64
549 prompt "HPET Timer Support" if X86_32
550 ---help---
551 Use the IA-PC HPET (High Precision Event Timer) to manage
552 time in preference to the PIT and RTC, if a HPET is
553 present.
554 HPET is the next generation timer replacing legacy 8254s.
555 The HPET provides a stable time base on SMP
556 systems, unlike the TSC, but it is more expensive to access,
557 as it is off-chip. You can find the HPET spec at
558 <http://www.intel.com/hardwaredesign/hpetspec_1.pdf>.
560 You can safely choose Y here. However, HPET will only be
561 activated if the platform and the BIOS support this feature.
562 Otherwise the 8254 will be used for timing services.
564 Choose N to continue using the legacy 8254 timer.
566 config HPET_EMULATE_RTC
567 def_bool y
568 depends on HPET_TIMER && (RTC=y || RTC=m || RTC_DRV_CMOS=m || RTC_DRV_CMOS=y)
570 # Mark as embedded because too many people got it wrong.
571 # The code disables itself when not needed.
572 config DMI
573 default y
574 bool "Enable DMI scanning" if EMBEDDED
575 ---help---
576 Enabled scanning of DMI to identify machine quirks. Say Y
577 here unless you have verified that your setup is not
578 affected by entries in the DMI blacklist. Required by PNP
579 BIOS code.
581 config GART_IOMMU
582 bool "GART IOMMU support" if EMBEDDED
583 default y
584 select SWIOTLB
585 select AGP
586 depends on X86_64 && PCI
587 ---help---
588 Support for full DMA access of devices with 32bit memory access only
589 on systems with more than 3GB. This is usually needed for USB,
590 sound, many IDE/SATA chipsets and some other devices.
591 Provides a driver for the AMD Athlon64/Opteron/Turion/Sempron GART
592 based hardware IOMMU and a software bounce buffer based IOMMU used
593 on Intel systems and as fallback.
594 The code is only active when needed (enough memory and limited
595 device) unless CONFIG_IOMMU_DEBUG or iommu=force is specified
596 too.
598 config CALGARY_IOMMU
599 bool "IBM Calgary IOMMU support"
600 select SWIOTLB
601 depends on X86_64 && PCI && EXPERIMENTAL
602 ---help---
603 Support for hardware IOMMUs in IBM's xSeries x366 and x460
604 systems. Needed to run systems with more than 3GB of memory
605 properly with 32-bit PCI devices that do not support DAC
606 (Double Address Cycle). Calgary also supports bus level
607 isolation, where all DMAs pass through the IOMMU. This
608 prevents them from going anywhere except their intended
609 destination. This catches hard-to-find kernel bugs and
610 mis-behaving drivers and devices that do not use the DMA-API
611 properly to set up their DMA buffers. The IOMMU can be
612 turned off at boot time with the iommu=off parameter.
613 Normally the kernel will make the right choice by itself.
614 If unsure, say Y.
616 config CALGARY_IOMMU_ENABLED_BY_DEFAULT
617 def_bool y
618 prompt "Should Calgary be enabled by default?"
619 depends on CALGARY_IOMMU
620 ---help---
621 Should Calgary be enabled by default? if you choose 'y', Calgary
622 will be used (if it exists). If you choose 'n', Calgary will not be
623 used even if it exists. If you choose 'n' and would like to use
624 Calgary anyway, pass 'iommu=calgary' on the kernel command line.
625 If unsure, say Y.
627 config AMD_IOMMU
628 bool "AMD IOMMU support"
629 select SWIOTLB
630 select PCI_MSI
631 depends on X86_64 && PCI && ACPI
632 ---help---
633 With this option you can enable support for AMD IOMMU hardware in
634 your system. An IOMMU is a hardware component which provides
635 remapping of DMA memory accesses from devices. With an AMD IOMMU you
636 can isolate the the DMA memory of different devices and protect the
637 system from misbehaving device drivers or hardware.
639 You can find out if your system has an AMD IOMMU if you look into
640 your BIOS for an option to enable it or if you have an IVRS ACPI
641 table.
643 config AMD_IOMMU_STATS
644 bool "Export AMD IOMMU statistics to debugfs"
645 depends on AMD_IOMMU
646 select DEBUG_FS
647 ---help---
648 This option enables code in the AMD IOMMU driver to collect various
649 statistics about whats happening in the driver and exports that
650 information to userspace via debugfs.
651 If unsure, say N.
653 # need this always selected by IOMMU for the VIA workaround
654 config SWIOTLB
655 def_bool y if X86_64
656 ---help---
657 Support for software bounce buffers used on x86-64 systems
658 which don't have a hardware IOMMU (e.g. the current generation
659 of Intel's x86-64 CPUs). Using this PCI devices which can only
660 access 32-bits of memory can be used on systems with more than
661 3 GB of memory. If unsure, say Y.
663 config IOMMU_HELPER
664 def_bool (CALGARY_IOMMU || GART_IOMMU || SWIOTLB || AMD_IOMMU)
666 config IOMMU_API
667 def_bool (AMD_IOMMU || DMAR)
669 config MAXSMP
670 bool "Configure Maximum number of SMP Processors and NUMA Nodes"
671 depends on X86_64 && SMP && DEBUG_KERNEL && EXPERIMENTAL
672 select CPUMASK_OFFSTACK
673 default n
674 ---help---
675 Configure maximum number of CPUS and NUMA Nodes for this architecture.
676 If unsure, say N.
678 config NR_CPUS
679 int "Maximum number of CPUs" if SMP && !MAXSMP
680 range 2 8 if SMP && X86_32 && !X86_BIGSMP
681 range 2 512 if SMP && !MAXSMP
682 default "1" if !SMP
683 default "4096" if MAXSMP
684 default "32" if SMP && (X86_NUMAQ || X86_SUMMIT || X86_BIGSMP || X86_ES7000)
685 default "8" if SMP
686 ---help---
687 This allows you to specify the maximum number of CPUs which this
688 kernel will support. The maximum supported value is 512 and the
689 minimum value which makes sense is 2.
691 This is purely to save memory - each supported CPU adds
692 approximately eight kilobytes to the kernel image.
694 config SCHED_SMT
695 bool "SMT (Hyperthreading) scheduler support"
696 depends on X86_HT
697 ---help---
698 SMT scheduler support improves the CPU scheduler's decision making
699 when dealing with Intel Pentium 4 chips with HyperThreading at a
700 cost of slightly increased overhead in some places. If unsure say
701 N here.
703 config SCHED_MC
704 def_bool y
705 prompt "Multi-core scheduler support"
706 depends on X86_HT
707 ---help---
708 Multi-core scheduler support improves the CPU scheduler's decision
709 making when dealing with multi-core CPU chips at a cost of slightly
710 increased overhead in some places. If unsure say N here.
712 source "kernel/Kconfig.preempt"
714 config X86_UP_APIC
715 bool "Local APIC support on uniprocessors"
716 depends on X86_32 && !SMP && !X86_32_NON_STANDARD
717 ---help---
718 A local APIC (Advanced Programmable Interrupt Controller) is an
719 integrated interrupt controller in the CPU. If you have a single-CPU
720 system which has a processor with a local APIC, you can say Y here to
721 enable and use it. If you say Y here even though your machine doesn't
722 have a local APIC, then the kernel will still run with no slowdown at
723 all. The local APIC supports CPU-generated self-interrupts (timer,
724 performance counters), and the NMI watchdog which detects hard
725 lockups.
727 config X86_UP_IOAPIC
728 bool "IO-APIC support on uniprocessors"
729 depends on X86_UP_APIC
730 ---help---
731 An IO-APIC (I/O Advanced Programmable Interrupt Controller) is an
732 SMP-capable replacement for PC-style interrupt controllers. Most
733 SMP systems and many recent uniprocessor systems have one.
735 If you have a single-CPU system with an IO-APIC, you can say Y here
736 to use it. If you say Y here even though your machine doesn't have
737 an IO-APIC, then the kernel will still run with no slowdown at all.
739 config X86_LOCAL_APIC
740 def_bool y
741 depends on X86_64 || SMP || X86_32_NON_STANDARD || X86_UP_APIC
742 select HAVE_PERF_COUNTERS if (!M386 && !M486)
744 config X86_IO_APIC
745 def_bool y
746 depends on X86_64 || SMP || X86_32_NON_STANDARD || X86_UP_APIC
748 config X86_VISWS_APIC
749 def_bool y
750 depends on X86_32 && X86_VISWS
752 config X86_REROUTE_FOR_BROKEN_BOOT_IRQS
753 bool "Reroute for broken boot IRQs"
754 default n
755 depends on X86_IO_APIC
756 ---help---
757 This option enables a workaround that fixes a source of
758 spurious interrupts. This is recommended when threaded
759 interrupt handling is used on systems where the generation of
760 superfluous "boot interrupts" cannot be disabled.
762 Some chipsets generate a legacy INTx "boot IRQ" when the IRQ
763 entry in the chipset's IO-APIC is masked (as, e.g. the RT
764 kernel does during interrupt handling). On chipsets where this
765 boot IRQ generation cannot be disabled, this workaround keeps
766 the original IRQ line masked so that only the equivalent "boot
767 IRQ" is delivered to the CPUs. The workaround also tells the
768 kernel to set up the IRQ handler on the boot IRQ line. In this
769 way only one interrupt is delivered to the kernel. Otherwise
770 the spurious second interrupt may cause the kernel to bring
771 down (vital) interrupt lines.
773 Only affects "broken" chipsets. Interrupt sharing may be
774 increased on these systems.
776 config X86_MCE
777 bool "Machine Check / overheating reporting"
778 ---help---
779 Machine Check support allows the processor to notify the
780 kernel if it detects a problem (e.g. overheating, data corruption).
781 The action the kernel takes depends on the severity of the problem,
782 ranging from warning messages to halting the machine.
784 config X86_NEW_MCE
785 depends on X86_MCE
786 bool
787 default y
789 config X86_MCE_INTEL
790 def_bool y
791 prompt "Intel MCE features"
792 depends on X86_NEW_MCE && X86_LOCAL_APIC
793 ---help---
794 Additional support for intel specific MCE features such as
795 the thermal monitor.
797 config X86_MCE_AMD
798 def_bool y
799 prompt "AMD MCE features"
800 depends on X86_NEW_MCE && X86_LOCAL_APIC
801 ---help---
802 Additional support for AMD specific MCE features such as
803 the DRAM Error Threshold.
805 config X86_ANCIENT_MCE
806 def_bool n
807 depends on X86_32 && X86_MCE
808 prompt "Support for old Pentium 5 / WinChip machine checks"
809 ---help---
810 Include support for machine check handling on old Pentium 5 or WinChip
811 systems. These typically need to be enabled explicitely on the command
812 line.
814 config X86_MCE_THRESHOLD
815 depends on X86_MCE_AMD || X86_MCE_INTEL
816 bool
817 default y
819 config X86_MCE_INJECT
820 depends on X86_NEW_MCE
821 tristate "Machine check injector support"
822 ---help---
823 Provide support for injecting machine checks for testing purposes.
824 If you don't know what a machine check is and you don't do kernel
825 QA it is safe to say n.
827 config X86_THERMAL_VECTOR
828 def_bool y
829 depends on X86_MCE_INTEL
831 config VM86
832 bool "Enable VM86 support" if EMBEDDED
833 default y
834 depends on X86_32
835 ---help---
836 This option is required by programs like DOSEMU to run 16-bit legacy
837 code on X86 processors. It also may be needed by software like
838 XFree86 to initialize some video cards via BIOS. Disabling this
839 option saves about 6k.
841 config TOSHIBA
842 tristate "Toshiba Laptop support"
843 depends on X86_32
844 ---help---
845 This adds a driver to safely access the System Management Mode of
846 the CPU on Toshiba portables with a genuine Toshiba BIOS. It does
847 not work on models with a Phoenix BIOS. The System Management Mode
848 is used to set the BIOS and power saving options on Toshiba portables.
850 For information on utilities to make use of this driver see the
851 Toshiba Linux utilities web site at:
852 <http://www.buzzard.org.uk/toshiba/>.
854 Say Y if you intend to run this kernel on a Toshiba portable.
855 Say N otherwise.
857 config I8K
858 tristate "Dell laptop support"
859 ---help---
860 This adds a driver to safely access the System Management Mode
861 of the CPU on the Dell Inspiron 8000. The System Management Mode
862 is used to read cpu temperature and cooling fan status and to
863 control the fans on the I8K portables.
865 This driver has been tested only on the Inspiron 8000 but it may
866 also work with other Dell laptops. You can force loading on other
867 models by passing the parameter `force=1' to the module. Use at
868 your own risk.
870 For information on utilities to make use of this driver see the
871 I8K Linux utilities web site at:
872 <http://people.debian.org/~dz/i8k/>
874 Say Y if you intend to run this kernel on a Dell Inspiron 8000.
875 Say N otherwise.
877 config X86_REBOOTFIXUPS
878 bool "Enable X86 board specific fixups for reboot"
879 depends on X86_32
880 ---help---
881 This enables chipset and/or board specific fixups to be done
882 in order to get reboot to work correctly. This is only needed on
883 some combinations of hardware and BIOS. The symptom, for which
884 this config is intended, is when reboot ends with a stalled/hung
885 system.
887 Currently, the only fixup is for the Geode machines using
888 CS5530A and CS5536 chipsets and the RDC R-321x SoC.
890 Say Y if you want to enable the fixup. Currently, it's safe to
891 enable this option even if you don't need it.
892 Say N otherwise.
894 config MICROCODE
895 tristate "/dev/cpu/microcode - microcode support"
896 select FW_LOADER
897 ---help---
898 If you say Y here, you will be able to update the microcode on
899 certain Intel and AMD processors. The Intel support is for the
900 IA32 family, e.g. Pentium Pro, Pentium II, Pentium III,
901 Pentium 4, Xeon etc. The AMD support is for family 0x10 and
902 0x11 processors, e.g. Opteron, Phenom and Turion 64 Ultra.
903 You will obviously need the actual microcode binary data itself
904 which is not shipped with the Linux kernel.
906 This option selects the general module only, you need to select
907 at least one vendor specific module as well.
909 To compile this driver as a module, choose M here: the
910 module will be called microcode.
912 config MICROCODE_INTEL
913 bool "Intel microcode patch loading support"
914 depends on MICROCODE
915 default MICROCODE
916 select FW_LOADER
917 ---help---
918 This options enables microcode patch loading support for Intel
919 processors.
921 For latest news and information on obtaining all the required
922 Intel ingredients for this driver, check:
923 <http://www.urbanmyth.org/microcode/>.
925 config MICROCODE_AMD
926 bool "AMD microcode patch loading support"
927 depends on MICROCODE
928 select FW_LOADER
929 ---help---
930 If you select this option, microcode patch loading support for AMD
931 processors will be enabled.
933 config MICROCODE_OLD_INTERFACE
934 def_bool y
935 depends on MICROCODE
937 config X86_MSR
938 tristate "/dev/cpu/*/msr - Model-specific register support"
939 ---help---
940 This device gives privileged processes access to the x86
941 Model-Specific Registers (MSRs). It is a character device with
942 major 202 and minors 0 to 31 for /dev/cpu/0/msr to /dev/cpu/31/msr.
943 MSR accesses are directed to a specific CPU on multi-processor
944 systems.
946 config X86_CPUID
947 tristate "/dev/cpu/*/cpuid - CPU information support"
948 ---help---
949 This device gives processes access to the x86 CPUID instruction to
950 be executed on a specific processor. It is a character device
951 with major 203 and minors 0 to 31 for /dev/cpu/0/cpuid to
952 /dev/cpu/31/cpuid.
954 config X86_CPU_DEBUG
955 tristate "/sys/kernel/debug/x86/cpu/* - CPU Debug support"
956 ---help---
957 If you select this option, this will provide various x86 CPUs
958 information through debugfs.
960 choice
961 prompt "High Memory Support"
962 default HIGHMEM4G if !X86_NUMAQ
963 default HIGHMEM64G if X86_NUMAQ
964 depends on X86_32
966 config NOHIGHMEM
967 bool "off"
968 depends on !X86_NUMAQ
969 ---help---
970 Linux can use up to 64 Gigabytes of physical memory on x86 systems.
971 However, the address space of 32-bit x86 processors is only 4
972 Gigabytes large. That means that, if you have a large amount of
973 physical memory, not all of it can be "permanently mapped" by the
974 kernel. The physical memory that's not permanently mapped is called
975 "high memory".
977 If you are compiling a kernel which will never run on a machine with
978 more than 1 Gigabyte total physical RAM, answer "off" here (default
979 choice and suitable for most users). This will result in a "3GB/1GB"
980 split: 3GB are mapped so that each process sees a 3GB virtual memory
981 space and the remaining part of the 4GB virtual memory space is used
982 by the kernel to permanently map as much physical memory as
983 possible.
985 If the machine has between 1 and 4 Gigabytes physical RAM, then
986 answer "4GB" here.
988 If more than 4 Gigabytes is used then answer "64GB" here. This
989 selection turns Intel PAE (Physical Address Extension) mode on.
990 PAE implements 3-level paging on IA32 processors. PAE is fully
991 supported by Linux, PAE mode is implemented on all recent Intel
992 processors (Pentium Pro and better). NOTE: If you say "64GB" here,
993 then the kernel will not boot on CPUs that don't support PAE!
995 The actual amount of total physical memory will either be
996 auto detected or can be forced by using a kernel command line option
997 such as "mem=256M". (Try "man bootparam" or see the documentation of
998 your boot loader (lilo or loadlin) about how to pass options to the
999 kernel at boot time.)
1001 If unsure, say "off".
1003 config HIGHMEM4G
1004 bool "4GB"
1005 depends on !X86_NUMAQ
1006 ---help---
1007 Select this if you have a 32-bit processor and between 1 and 4
1008 gigabytes of physical RAM.
1010 config HIGHMEM64G
1011 bool "64GB"
1012 depends on !M386 && !M486
1013 select X86_PAE
1014 ---help---
1015 Select this if you have a 32-bit processor and more than 4
1016 gigabytes of physical RAM.
1018 endchoice
1020 choice
1021 depends on EXPERIMENTAL
1022 prompt "Memory split" if EMBEDDED
1023 default VMSPLIT_3G
1024 depends on X86_32
1025 ---help---
1026 Select the desired split between kernel and user memory.
1028 If the address range available to the kernel is less than the
1029 physical memory installed, the remaining memory will be available
1030 as "high memory". Accessing high memory is a little more costly
1031 than low memory, as it needs to be mapped into the kernel first.
1032 Note that increasing the kernel address space limits the range
1033 available to user programs, making the address space there
1034 tighter. Selecting anything other than the default 3G/1G split
1035 will also likely make your kernel incompatible with binary-only
1036 kernel modules.
1038 If you are not absolutely sure what you are doing, leave this
1039 option alone!
1041 config VMSPLIT_3G
1042 bool "3G/1G user/kernel split"
1043 config VMSPLIT_3G_OPT
1044 depends on !X86_PAE
1045 bool "3G/1G user/kernel split (for full 1G low memory)"
1046 config VMSPLIT_2G
1047 bool "2G/2G user/kernel split"
1048 config VMSPLIT_2G_OPT
1049 depends on !X86_PAE
1050 bool "2G/2G user/kernel split (for full 2G low memory)"
1051 config VMSPLIT_1G
1052 bool "1G/3G user/kernel split"
1053 endchoice
1055 config PAGE_OFFSET
1056 hex
1057 default 0xB0000000 if VMSPLIT_3G_OPT
1058 default 0x80000000 if VMSPLIT_2G
1059 default 0x78000000 if VMSPLIT_2G_OPT
1060 default 0x40000000 if VMSPLIT_1G
1061 default 0xC0000000
1062 depends on X86_32
1064 config HIGHMEM
1065 def_bool y
1066 depends on X86_32 && (HIGHMEM64G || HIGHMEM4G)
1068 config X86_PAE
1069 bool "PAE (Physical Address Extension) Support"
1070 depends on X86_32 && !HIGHMEM4G
1071 ---help---
1072 PAE is required for NX support, and furthermore enables
1073 larger swapspace support for non-overcommit purposes. It
1074 has the cost of more pagetable lookup overhead, and also
1075 consumes more pagetable space per process.
1077 config ARCH_PHYS_ADDR_T_64BIT
1078 def_bool X86_64 || X86_PAE
1080 config DIRECT_GBPAGES
1081 bool "Enable 1GB pages for kernel pagetables" if EMBEDDED
1082 default y
1083 depends on X86_64
1084 ---help---
1085 Allow the kernel linear mapping to use 1GB pages on CPUs that
1086 support it. This can improve the kernel's performance a tiny bit by
1087 reducing TLB pressure. If in doubt, say "Y".
1089 # Common NUMA Features
1090 config NUMA
1091 bool "Numa Memory Allocation and Scheduler Support"
1092 depends on SMP
1093 depends on X86_64 || (X86_32 && HIGHMEM64G && (X86_NUMAQ || X86_BIGSMP || X86_SUMMIT && ACPI) && EXPERIMENTAL)
1094 default y if (X86_NUMAQ || X86_SUMMIT || X86_BIGSMP)
1095 ---help---
1096 Enable NUMA (Non Uniform Memory Access) support.
1098 The kernel will try to allocate memory used by a CPU on the
1099 local memory controller of the CPU and add some more
1100 NUMA awareness to the kernel.
1102 For 64-bit this is recommended if the system is Intel Core i7
1103 (or later), AMD Opteron, or EM64T NUMA.
1105 For 32-bit this is only needed on (rare) 32-bit-only platforms
1106 that support NUMA topologies, such as NUMAQ / Summit, or if you
1107 boot a 32-bit kernel on a 64-bit NUMA platform.
1109 Otherwise, you should say N.
1111 comment "NUMA (Summit) requires SMP, 64GB highmem support, ACPI"
1112 depends on X86_32 && X86_SUMMIT && (!HIGHMEM64G || !ACPI)
1114 config K8_NUMA
1115 def_bool y
1116 prompt "Old style AMD Opteron NUMA detection"
1117 depends on X86_64 && NUMA && PCI
1118 ---help---
1119 Enable K8 NUMA node topology detection. You should say Y here if
1120 you have a multi processor AMD K8 system. This uses an old
1121 method to read the NUMA configuration directly from the builtin
1122 Northbridge of Opteron. It is recommended to use X86_64_ACPI_NUMA
1123 instead, which also takes priority if both are compiled in.
1125 config X86_64_ACPI_NUMA
1126 def_bool y
1127 prompt "ACPI NUMA detection"
1128 depends on X86_64 && NUMA && ACPI && PCI
1129 select ACPI_NUMA
1130 ---help---
1131 Enable ACPI SRAT based node topology detection.
1133 # Some NUMA nodes have memory ranges that span
1134 # other nodes. Even though a pfn is valid and
1135 # between a node's start and end pfns, it may not
1136 # reside on that node. See memmap_init_zone()
1137 # for details.
1138 config NODES_SPAN_OTHER_NODES
1139 def_bool y
1140 depends on X86_64_ACPI_NUMA
1142 config NUMA_EMU
1143 bool "NUMA emulation"
1144 depends on X86_64 && NUMA
1145 ---help---
1146 Enable NUMA emulation. A flat machine will be split
1147 into virtual nodes when booted with "numa=fake=N", where N is the
1148 number of nodes. This is only useful for debugging.
1150 config NODES_SHIFT
1151 int "Maximum NUMA Nodes (as a power of 2)" if !MAXSMP
1152 range 1 9
1153 default "9" if MAXSMP
1154 default "6" if X86_64
1155 default "4" if X86_NUMAQ
1156 default "3"
1157 depends on NEED_MULTIPLE_NODES
1158 ---help---
1159 Specify the maximum number of NUMA Nodes available on the target
1160 system. Increases memory reserved to accommodate various tables.
1162 config HAVE_ARCH_BOOTMEM
1163 def_bool y
1164 depends on X86_32 && NUMA
1166 config ARCH_HAVE_MEMORY_PRESENT
1167 def_bool y
1168 depends on X86_32 && DISCONTIGMEM
1170 config NEED_NODE_MEMMAP_SIZE
1171 def_bool y
1172 depends on X86_32 && (DISCONTIGMEM || SPARSEMEM)
1174 config HAVE_ARCH_ALLOC_REMAP
1175 def_bool y
1176 depends on X86_32 && NUMA
1178 config ARCH_FLATMEM_ENABLE
1179 def_bool y
1180 depends on X86_32 && ARCH_SELECT_MEMORY_MODEL && !NUMA
1182 config ARCH_DISCONTIGMEM_ENABLE
1183 def_bool y
1184 depends on NUMA && X86_32
1186 config ARCH_DISCONTIGMEM_DEFAULT
1187 def_bool y
1188 depends on NUMA && X86_32
1190 config ARCH_SPARSEMEM_DEFAULT
1191 def_bool y
1192 depends on X86_64
1194 config ARCH_SPARSEMEM_ENABLE
1195 def_bool y
1196 depends on X86_64 || NUMA || (EXPERIMENTAL && X86_32) || X86_32_NON_STANDARD
1197 select SPARSEMEM_STATIC if X86_32
1198 select SPARSEMEM_VMEMMAP_ENABLE if X86_64
1200 config ARCH_SELECT_MEMORY_MODEL
1201 def_bool y
1202 depends on ARCH_SPARSEMEM_ENABLE
1204 config ARCH_MEMORY_PROBE
1205 def_bool X86_64
1206 depends on MEMORY_HOTPLUG
1208 source "mm/Kconfig"
1210 config HIGHPTE
1211 bool "Allocate 3rd-level pagetables from highmem"
1212 depends on X86_32 && (HIGHMEM4G || HIGHMEM64G)
1213 ---help---
1214 The VM uses one page table entry for each page of physical memory.
1215 For systems with a lot of RAM, this can be wasteful of precious
1216 low memory. Setting this option will put user-space page table
1217 entries in high memory.
1219 config X86_CHECK_BIOS_CORRUPTION
1220 bool "Check for low memory corruption"
1221 ---help---
1222 Periodically check for memory corruption in low memory, which
1223 is suspected to be caused by BIOS. Even when enabled in the
1224 configuration, it is disabled at runtime. Enable it by
1225 setting "memory_corruption_check=1" on the kernel command
1226 line. By default it scans the low 64k of memory every 60
1227 seconds; see the memory_corruption_check_size and
1228 memory_corruption_check_period parameters in
1229 Documentation/kernel-parameters.txt to adjust this.
1231 When enabled with the default parameters, this option has
1232 almost no overhead, as it reserves a relatively small amount
1233 of memory and scans it infrequently. It both detects corruption
1234 and prevents it from affecting the running system.
1236 It is, however, intended as a diagnostic tool; if repeatable
1237 BIOS-originated corruption always affects the same memory,
1238 you can use memmap= to prevent the kernel from using that
1239 memory.
1241 config X86_BOOTPARAM_MEMORY_CORRUPTION_CHECK
1242 bool "Set the default setting of memory_corruption_check"
1243 depends on X86_CHECK_BIOS_CORRUPTION
1244 default y
1245 ---help---
1246 Set whether the default state of memory_corruption_check is
1247 on or off.
1249 config X86_RESERVE_LOW_64K
1250 bool "Reserve low 64K of RAM on AMI/Phoenix BIOSen"
1251 default y
1252 ---help---
1253 Reserve the first 64K of physical RAM on BIOSes that are known
1254 to potentially corrupt that memory range. A numbers of BIOSes are
1255 known to utilize this area during suspend/resume, so it must not
1256 be used by the kernel.
1258 Set this to N if you are absolutely sure that you trust the BIOS
1259 to get all its memory reservations and usages right.
1261 If you have doubts about the BIOS (e.g. suspend/resume does not
1262 work or there's kernel crashes after certain hardware hotplug
1263 events) and it's not AMI or Phoenix, then you might want to enable
1264 X86_CHECK_BIOS_CORRUPTION=y to allow the kernel to check typical
1265 corruption patterns.
1267 Say Y if unsure.
1269 config MATH_EMULATION
1270 bool
1271 prompt "Math emulation" if X86_32
1272 ---help---
1273 Linux can emulate a math coprocessor (used for floating point
1274 operations) if you don't have one. 486DX and Pentium processors have
1275 a math coprocessor built in, 486SX and 386 do not, unless you added
1276 a 487DX or 387, respectively. (The messages during boot time can
1277 give you some hints here ["man dmesg"].) Everyone needs either a
1278 coprocessor or this emulation.
1280 If you don't have a math coprocessor, you need to say Y here; if you
1281 say Y here even though you have a coprocessor, the coprocessor will
1282 be used nevertheless. (This behavior can be changed with the kernel
1283 command line option "no387", which comes handy if your coprocessor
1284 is broken. Try "man bootparam" or see the documentation of your boot
1285 loader (lilo or loadlin) about how to pass options to the kernel at
1286 boot time.) This means that it is a good idea to say Y here if you
1287 intend to use this kernel on different machines.
1289 More information about the internals of the Linux math coprocessor
1290 emulation can be found in <file:arch/x86/math-emu/README>.
1292 If you are not sure, say Y; apart from resulting in a 66 KB bigger
1293 kernel, it won't hurt.
1295 config MTRR
1296 bool "MTRR (Memory Type Range Register) support"
1297 ---help---
1298 On Intel P6 family processors (Pentium Pro, Pentium II and later)
1299 the Memory Type Range Registers (MTRRs) may be used to control
1300 processor access to memory ranges. This is most useful if you have
1301 a video (VGA) card on a PCI or AGP bus. Enabling write-combining
1302 allows bus write transfers to be combined into a larger transfer
1303 before bursting over the PCI/AGP bus. This can increase performance
1304 of image write operations 2.5 times or more. Saying Y here creates a
1305 /proc/mtrr file which may be used to manipulate your processor's
1306 MTRRs. Typically the X server should use this.
1308 This code has a reasonably generic interface so that similar
1309 control registers on other processors can be easily supported
1310 as well:
1312 The Cyrix 6x86, 6x86MX and M II processors have Address Range
1313 Registers (ARRs) which provide a similar functionality to MTRRs. For
1314 these, the ARRs are used to emulate the MTRRs.
1315 The AMD K6-2 (stepping 8 and above) and K6-3 processors have two
1316 MTRRs. The Centaur C6 (WinChip) has 8 MCRs, allowing
1317 write-combining. All of these processors are supported by this code
1318 and it makes sense to say Y here if you have one of them.
1320 Saying Y here also fixes a problem with buggy SMP BIOSes which only
1321 set the MTRRs for the boot CPU and not for the secondary CPUs. This
1322 can lead to all sorts of problems, so it's good to say Y here.
1324 You can safely say Y even if your machine doesn't have MTRRs, you'll
1325 just add about 9 KB to your kernel.
1327 See <file:Documentation/x86/mtrr.txt> for more information.
1329 config MTRR_SANITIZER
1330 def_bool y
1331 prompt "MTRR cleanup support"
1332 depends on MTRR
1333 ---help---
1334 Convert MTRR layout from continuous to discrete, so X drivers can
1335 add writeback entries.
1337 Can be disabled with disable_mtrr_cleanup on the kernel command line.
1338 The largest mtrr entry size for a continuous block can be set with
1339 mtrr_chunk_size.
1341 If unsure, say Y.
1343 config MTRR_SANITIZER_ENABLE_DEFAULT
1344 int "MTRR cleanup enable value (0-1)"
1345 range 0 1
1346 default "0"
1347 depends on MTRR_SANITIZER
1348 ---help---
1349 Enable mtrr cleanup default value
1351 config MTRR_SANITIZER_SPARE_REG_NR_DEFAULT
1352 int "MTRR cleanup spare reg num (0-7)"
1353 range 0 7
1354 default "1"
1355 depends on MTRR_SANITIZER
1356 ---help---
1357 mtrr cleanup spare entries default, it can be changed via
1358 mtrr_spare_reg_nr=N on the kernel command line.
1360 config X86_PAT
1361 bool
1362 prompt "x86 PAT support"
1363 depends on MTRR
1364 ---help---
1365 Use PAT attributes to setup page level cache control.
1367 PATs are the modern equivalents of MTRRs and are much more
1368 flexible than MTRRs.
1370 Say N here if you see bootup problems (boot crash, boot hang,
1371 spontaneous reboots) or a non-working video driver.
1373 If unsure, say Y.
1375 config EFI
1376 bool "EFI runtime service support"
1377 depends on ACPI
1378 ---help---
1379 This enables the kernel to use EFI runtime services that are
1380 available (such as the EFI variable services).
1382 This option is only useful on systems that have EFI firmware.
1383 In addition, you should use the latest ELILO loader available
1384 at <http://elilo.sourceforge.net> in order to take advantage
1385 of EFI runtime services. However, even with this option, the
1386 resultant kernel should continue to boot on existing non-EFI
1387 platforms.
1389 config SECCOMP
1390 def_bool y
1391 prompt "Enable seccomp to safely compute untrusted bytecode"
1392 ---help---
1393 This kernel feature is useful for number crunching applications
1394 that may need to compute untrusted bytecode during their
1395 execution. By using pipes or other transports made available to
1396 the process as file descriptors supporting the read/write
1397 syscalls, it's possible to isolate those applications in
1398 their own address space using seccomp. Once seccomp is
1399 enabled via prctl(PR_SET_SECCOMP), it cannot be disabled
1400 and the task is only allowed to execute a few safe syscalls
1401 defined by each seccomp mode.
1403 If unsure, say Y. Only embedded should say N here.
1405 config CC_STACKPROTECTOR_ALL
1406 bool
1408 config CC_STACKPROTECTOR
1409 bool "Enable -fstack-protector buffer overflow detection (EXPERIMENTAL)"
1410 select CC_STACKPROTECTOR_ALL
1411 ---help---
1412 This option turns on the -fstack-protector GCC feature. This
1413 feature puts, at the beginning of functions, a canary value on
1414 the stack just before the return address, and validates
1415 the value just before actually returning. Stack based buffer
1416 overflows (that need to overwrite this return address) now also
1417 overwrite the canary, which gets detected and the attack is then
1418 neutralized via a kernel panic.
1420 This feature requires gcc version 4.2 or above, or a distribution
1421 gcc with the feature backported. Older versions are automatically
1422 detected and for those versions, this configuration option is
1423 ignored. (and a warning is printed during bootup)
1425 source kernel/Kconfig.hz
1427 config KEXEC
1428 bool "kexec system call"
1429 ---help---
1430 kexec is a system call that implements the ability to shutdown your
1431 current kernel, and to start another kernel. It is like a reboot
1432 but it is independent of the system firmware. And like a reboot
1433 you can start any kernel with it, not just Linux.
1435 The name comes from the similarity to the exec system call.
1437 It is an ongoing process to be certain the hardware in a machine
1438 is properly shutdown, so do not be surprised if this code does not
1439 initially work for you. It may help to enable device hotplugging
1440 support. As of this writing the exact hardware interface is
1441 strongly in flux, so no good recommendation can be made.
1443 config CRASH_DUMP
1444 bool "kernel crash dumps"
1445 depends on X86_64 || (X86_32 && HIGHMEM)
1446 ---help---
1447 Generate crash dump after being started by kexec.
1448 This should be normally only set in special crash dump kernels
1449 which are loaded in the main kernel with kexec-tools into
1450 a specially reserved region and then later executed after
1451 a crash by kdump/kexec. The crash dump kernel must be compiled
1452 to a memory address not used by the main kernel or BIOS using
1453 PHYSICAL_START, or it must be built as a relocatable image
1454 (CONFIG_RELOCATABLE=y).
1455 For more details see Documentation/kdump/kdump.txt
1457 config KEXEC_JUMP
1458 bool "kexec jump (EXPERIMENTAL)"
1459 depends on EXPERIMENTAL
1460 depends on KEXEC && HIBERNATION
1461 ---help---
1462 Jump between original kernel and kexeced kernel and invoke
1463 code in physical address mode via KEXEC
1465 config PHYSICAL_START
1466 hex "Physical address where the kernel is loaded" if (EMBEDDED || CRASH_DUMP)
1467 default "0x1000000"
1468 ---help---
1469 This gives the physical address where the kernel is loaded.
1471 If kernel is a not relocatable (CONFIG_RELOCATABLE=n) then
1472 bzImage will decompress itself to above physical address and
1473 run from there. Otherwise, bzImage will run from the address where
1474 it has been loaded by the boot loader and will ignore above physical
1475 address.
1477 In normal kdump cases one does not have to set/change this option
1478 as now bzImage can be compiled as a completely relocatable image
1479 (CONFIG_RELOCATABLE=y) and be used to load and run from a different
1480 address. This option is mainly useful for the folks who don't want
1481 to use a bzImage for capturing the crash dump and want to use a
1482 vmlinux instead. vmlinux is not relocatable hence a kernel needs
1483 to be specifically compiled to run from a specific memory area
1484 (normally a reserved region) and this option comes handy.
1486 So if you are using bzImage for capturing the crash dump,
1487 leave the value here unchanged to 0x1000000 and set
1488 CONFIG_RELOCATABLE=y. Otherwise if you plan to use vmlinux
1489 for capturing the crash dump change this value to start of
1490 the reserved region. In other words, it can be set based on
1491 the "X" value as specified in the "crashkernel=YM@XM"
1492 command line boot parameter passed to the panic-ed
1493 kernel. Please take a look at Documentation/kdump/kdump.txt
1494 for more details about crash dumps.
1496 Usage of bzImage for capturing the crash dump is recommended as
1497 one does not have to build two kernels. Same kernel can be used
1498 as production kernel and capture kernel. Above option should have
1499 gone away after relocatable bzImage support is introduced. But it
1500 is present because there are users out there who continue to use
1501 vmlinux for dump capture. This option should go away down the
1502 line.
1504 Don't change this unless you know what you are doing.
1506 config RELOCATABLE
1507 bool "Build a relocatable kernel"
1508 default y
1509 ---help---
1510 This builds a kernel image that retains relocation information
1511 so it can be loaded someplace besides the default 1MB.
1512 The relocations tend to make the kernel binary about 10% larger,
1513 but are discarded at runtime.
1515 One use is for the kexec on panic case where the recovery kernel
1516 must live at a different physical address than the primary
1517 kernel.
1519 Note: If CONFIG_RELOCATABLE=y, then the kernel runs from the address
1520 it has been loaded at and the compile time physical address
1521 (CONFIG_PHYSICAL_START) is ignored.
1523 # Relocation on x86-32 needs some additional build support
1524 config X86_NEED_RELOCS
1525 def_bool y
1526 depends on X86_32 && RELOCATABLE
1528 config PHYSICAL_ALIGN
1529 hex
1530 prompt "Alignment value to which kernel should be aligned" if X86_32
1531 default "0x1000000"
1532 range 0x2000 0x1000000
1533 ---help---
1534 This value puts the alignment restrictions on physical address
1535 where kernel is loaded and run from. Kernel is compiled for an
1536 address which meets above alignment restriction.
1538 If bootloader loads the kernel at a non-aligned address and
1539 CONFIG_RELOCATABLE is set, kernel will move itself to nearest
1540 address aligned to above value and run from there.
1542 If bootloader loads the kernel at a non-aligned address and
1543 CONFIG_RELOCATABLE is not set, kernel will ignore the run time
1544 load address and decompress itself to the address it has been
1545 compiled for and run from there. The address for which kernel is
1546 compiled already meets above alignment restrictions. Hence the
1547 end result is that kernel runs from a physical address meeting
1548 above alignment restrictions.
1550 Don't change this unless you know what you are doing.
1552 config HOTPLUG_CPU
1553 bool "Support for hot-pluggable CPUs"
1554 depends on SMP && HOTPLUG
1555 ---help---
1556 Say Y here to allow turning CPUs off and on. CPUs can be
1557 controlled through /sys/devices/system/cpu.
1558 ( Note: power management support will enable this option
1559 automatically on SMP systems. )
1560 Say N if you want to disable CPU hotplug.
1562 config COMPAT_VDSO
1563 def_bool y
1564 prompt "Compat VDSO support"
1565 depends on X86_32 || IA32_EMULATION
1566 ---help---
1567 Map the 32-bit VDSO to the predictable old-style address too.
1568 ---help---
1569 Say N here if you are running a sufficiently recent glibc
1570 version (2.3.3 or later), to remove the high-mapped
1571 VDSO mapping and to exclusively use the randomized VDSO.
1573 If unsure, say Y.
1575 config CMDLINE_BOOL
1576 bool "Built-in kernel command line"
1577 default n
1578 ---help---
1579 Allow for specifying boot arguments to the kernel at
1580 build time. On some systems (e.g. embedded ones), it is
1581 necessary or convenient to provide some or all of the
1582 kernel boot arguments with the kernel itself (that is,
1583 to not rely on the boot loader to provide them.)
1585 To compile command line arguments into the kernel,
1586 set this option to 'Y', then fill in the
1587 the boot arguments in CONFIG_CMDLINE.
1589 Systems with fully functional boot loaders (i.e. non-embedded)
1590 should leave this option set to 'N'.
1592 config CMDLINE
1593 string "Built-in kernel command string"
1594 depends on CMDLINE_BOOL
1595 default ""
1596 ---help---
1597 Enter arguments here that should be compiled into the kernel
1598 image and used at boot time. If the boot loader provides a
1599 command line at boot time, it is appended to this string to
1600 form the full kernel command line, when the system boots.
1602 However, you can use the CONFIG_CMDLINE_OVERRIDE option to
1603 change this behavior.
1605 In most cases, the command line (whether built-in or provided
1606 by the boot loader) should specify the device for the root
1607 file system.
1609 config CMDLINE_OVERRIDE
1610 bool "Built-in command line overrides boot loader arguments"
1611 default n
1612 depends on CMDLINE_BOOL
1613 ---help---
1614 Set this option to 'Y' to have the kernel ignore the boot loader
1615 command line, and use ONLY the built-in command line.
1617 This is used to work around broken boot loaders. This should
1618 be set to 'N' under normal conditions.
1620 endmenu
1622 config ARCH_ENABLE_MEMORY_HOTPLUG
1623 def_bool y
1624 depends on X86_64 || (X86_32 && HIGHMEM)
1626 config ARCH_ENABLE_MEMORY_HOTREMOVE
1627 def_bool y
1628 depends on MEMORY_HOTPLUG
1630 config HAVE_ARCH_EARLY_PFN_TO_NID
1631 def_bool X86_64
1632 depends on NUMA
1634 menu "Power management and ACPI options"
1636 config ARCH_HIBERNATION_HEADER
1637 def_bool y
1638 depends on X86_64 && HIBERNATION
1640 source "kernel/power/Kconfig"
1642 source "drivers/acpi/Kconfig"
1644 config X86_APM_BOOT
1645 bool
1646 default y
1647 depends on APM || APM_MODULE
1649 menuconfig APM
1650 tristate "APM (Advanced Power Management) BIOS support"
1651 depends on X86_32 && PM_SLEEP
1652 ---help---
1653 APM is a BIOS specification for saving power using several different
1654 techniques. This is mostly useful for battery powered laptops with
1655 APM compliant BIOSes. If you say Y here, the system time will be
1656 reset after a RESUME operation, the /proc/apm device will provide
1657 battery status information, and user-space programs will receive
1658 notification of APM "events" (e.g. battery status change).
1660 If you select "Y" here, you can disable actual use of the APM
1661 BIOS by passing the "apm=off" option to the kernel at boot time.
1663 Note that the APM support is almost completely disabled for
1664 machines with more than one CPU.
1666 In order to use APM, you will need supporting software. For location
1667 and more information, read <file:Documentation/power/pm.txt> and the
1668 Battery Powered Linux mini-HOWTO, available from
1669 <http://www.tldp.org/docs.html#howto>.
1671 This driver does not spin down disk drives (see the hdparm(8)
1672 manpage ("man 8 hdparm") for that), and it doesn't turn off
1673 VESA-compliant "green" monitors.
1675 This driver does not support the TI 4000M TravelMate and the ACER
1676 486/DX4/75 because they don't have compliant BIOSes. Many "green"
1677 desktop machines also don't have compliant BIOSes, and this driver
1678 may cause those machines to panic during the boot phase.
1680 Generally, if you don't have a battery in your machine, there isn't
1681 much point in using this driver and you should say N. If you get
1682 random kernel OOPSes or reboots that don't seem to be related to
1683 anything, try disabling/enabling this option (or disabling/enabling
1684 APM in your BIOS).
1686 Some other things you should try when experiencing seemingly random,
1687 "weird" problems:
1689 1) make sure that you have enough swap space and that it is
1690 enabled.
1691 2) pass the "no-hlt" option to the kernel
1692 3) switch on floating point emulation in the kernel and pass
1693 the "no387" option to the kernel
1694 4) pass the "floppy=nodma" option to the kernel
1695 5) pass the "mem=4M" option to the kernel (thereby disabling
1696 all but the first 4 MB of RAM)
1697 6) make sure that the CPU is not over clocked.
1698 7) read the sig11 FAQ at <http://www.bitwizard.nl/sig11/>
1699 8) disable the cache from your BIOS settings
1700 9) install a fan for the video card or exchange video RAM
1701 10) install a better fan for the CPU
1702 11) exchange RAM chips
1703 12) exchange the motherboard.
1705 To compile this driver as a module, choose M here: the
1706 module will be called apm.
1708 if APM
1710 config APM_IGNORE_USER_SUSPEND
1711 bool "Ignore USER SUSPEND"
1712 ---help---
1713 This option will ignore USER SUSPEND requests. On machines with a
1714 compliant APM BIOS, you want to say N. However, on the NEC Versa M
1715 series notebooks, it is necessary to say Y because of a BIOS bug.
1717 config APM_DO_ENABLE
1718 bool "Enable PM at boot time"
1719 ---help---
1720 Enable APM features at boot time. From page 36 of the APM BIOS
1721 specification: "When disabled, the APM BIOS does not automatically
1722 power manage devices, enter the Standby State, enter the Suspend
1723 State, or take power saving steps in response to CPU Idle calls."
1724 This driver will make CPU Idle calls when Linux is idle (unless this
1725 feature is turned off -- see "Do CPU IDLE calls", below). This
1726 should always save battery power, but more complicated APM features
1727 will be dependent on your BIOS implementation. You may need to turn
1728 this option off if your computer hangs at boot time when using APM
1729 support, or if it beeps continuously instead of suspending. Turn
1730 this off if you have a NEC UltraLite Versa 33/C or a Toshiba
1731 T400CDT. This is off by default since most machines do fine without
1732 this feature.
1734 config APM_CPU_IDLE
1735 bool "Make CPU Idle calls when idle"
1736 ---help---
1737 Enable calls to APM CPU Idle/CPU Busy inside the kernel's idle loop.
1738 On some machines, this can activate improved power savings, such as
1739 a slowed CPU clock rate, when the machine is idle. These idle calls
1740 are made after the idle loop has run for some length of time (e.g.,
1741 333 mS). On some machines, this will cause a hang at boot time or
1742 whenever the CPU becomes idle. (On machines with more than one CPU,
1743 this option does nothing.)
1745 config APM_DISPLAY_BLANK
1746 bool "Enable console blanking using APM"
1747 ---help---
1748 Enable console blanking using the APM. Some laptops can use this to
1749 turn off the LCD backlight when the screen blanker of the Linux
1750 virtual console blanks the screen. Note that this is only used by
1751 the virtual console screen blanker, and won't turn off the backlight
1752 when using the X Window system. This also doesn't have anything to
1753 do with your VESA-compliant power-saving monitor. Further, this
1754 option doesn't work for all laptops -- it might not turn off your
1755 backlight at all, or it might print a lot of errors to the console,
1756 especially if you are using gpm.
1758 config APM_ALLOW_INTS
1759 bool "Allow interrupts during APM BIOS calls"
1760 ---help---
1761 Normally we disable external interrupts while we are making calls to
1762 the APM BIOS as a measure to lessen the effects of a badly behaving
1763 BIOS implementation. The BIOS should reenable interrupts if it
1764 needs to. Unfortunately, some BIOSes do not -- especially those in
1765 many of the newer IBM Thinkpads. If you experience hangs when you
1766 suspend, try setting this to Y. Otherwise, say N.
1768 endif # APM
1770 source "arch/x86/kernel/cpu/cpufreq/Kconfig"
1772 source "drivers/cpuidle/Kconfig"
1774 source "drivers/idle/Kconfig"
1776 endmenu
1779 menu "Bus options (PCI etc.)"
1781 config PCI
1782 bool "PCI support"
1783 default y
1784 select ARCH_SUPPORTS_MSI if (X86_LOCAL_APIC && X86_IO_APIC)
1785 ---help---
1786 Find out whether you have a PCI motherboard. PCI is the name of a
1787 bus system, i.e. the way the CPU talks to the other stuff inside
1788 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
1789 VESA. If you have PCI, say Y, otherwise N.
1791 choice
1792 prompt "PCI access mode"
1793 depends on X86_32 && PCI
1794 default PCI_GOANY
1795 ---help---
1796 On PCI systems, the BIOS can be used to detect the PCI devices and
1797 determine their configuration. However, some old PCI motherboards
1798 have BIOS bugs and may crash if this is done. Also, some embedded
1799 PCI-based systems don't have any BIOS at all. Linux can also try to
1800 detect the PCI hardware directly without using the BIOS.
1802 With this option, you can specify how Linux should detect the
1803 PCI devices. If you choose "BIOS", the BIOS will be used,
1804 if you choose "Direct", the BIOS won't be used, and if you
1805 choose "MMConfig", then PCI Express MMCONFIG will be used.
1806 If you choose "Any", the kernel will try MMCONFIG, then the
1807 direct access method and falls back to the BIOS if that doesn't
1808 work. If unsure, go with the default, which is "Any".
1810 config PCI_GOBIOS
1811 bool "BIOS"
1813 config PCI_GOMMCONFIG
1814 bool "MMConfig"
1816 config PCI_GODIRECT
1817 bool "Direct"
1819 config PCI_GOOLPC
1820 bool "OLPC"
1821 depends on OLPC
1823 config PCI_GOANY
1824 bool "Any"
1826 endchoice
1828 config PCI_BIOS
1829 def_bool y
1830 depends on X86_32 && PCI && (PCI_GOBIOS || PCI_GOANY)
1832 # x86-64 doesn't support PCI BIOS access from long mode so always go direct.
1833 config PCI_DIRECT
1834 def_bool y
1835 depends on PCI && (X86_64 || (PCI_GODIRECT || PCI_GOANY || PCI_GOOLPC))
1837 config PCI_MMCONFIG
1838 def_bool y
1839 depends on X86_32 && PCI && ACPI && (PCI_GOMMCONFIG || PCI_GOANY)
1841 config PCI_OLPC
1842 def_bool y
1843 depends on PCI && OLPC && (PCI_GOOLPC || PCI_GOANY)
1845 config PCI_DOMAINS
1846 def_bool y
1847 depends on PCI
1849 config PCI_MMCONFIG
1850 bool "Support mmconfig PCI config space access"
1851 depends on X86_64 && PCI && ACPI
1853 config DMAR
1854 bool "Support for DMA Remapping Devices (EXPERIMENTAL)"
1855 depends on PCI_MSI && ACPI && EXPERIMENTAL
1856 help
1857 DMA remapping (DMAR) devices support enables independent address
1858 translations for Direct Memory Access (DMA) from devices.
1859 These DMA remapping devices are reported via ACPI tables
1860 and include PCI device scope covered by these DMA
1861 remapping devices.
1863 config DMAR_DEFAULT_ON
1864 def_bool y
1865 prompt "Enable DMA Remapping Devices by default"
1866 depends on DMAR
1867 help
1868 Selecting this option will enable a DMAR device at boot time if
1869 one is found. If this option is not selected, DMAR support can
1870 be enabled by passing intel_iommu=on to the kernel. It is
1871 recommended you say N here while the DMAR code remains
1872 experimental.
1874 config DMAR_GFX_WA
1875 def_bool y
1876 prompt "Support for Graphics workaround"
1877 depends on DMAR
1878 ---help---
1879 Current Graphics drivers tend to use physical address
1880 for DMA and avoid using DMA APIs. Setting this config
1881 option permits the IOMMU driver to set a unity map for
1882 all the OS-visible memory. Hence the driver can continue
1883 to use physical addresses for DMA.
1885 config DMAR_FLOPPY_WA
1886 def_bool y
1887 depends on DMAR
1888 ---help---
1889 Floppy disk drivers are know to bypass DMA API calls
1890 thereby failing to work when IOMMU is enabled. This
1891 workaround will setup a 1:1 mapping for the first
1892 16M to make floppy (an ISA device) work.
1894 config INTR_REMAP
1895 bool "Support for Interrupt Remapping (EXPERIMENTAL)"
1896 depends on X86_64 && X86_IO_APIC && PCI_MSI && ACPI && EXPERIMENTAL
1897 ---help---
1898 Supports Interrupt remapping for IO-APIC and MSI devices.
1899 To use x2apic mode in the CPU's which support x2APIC enhancements or
1900 to support platforms with CPU's having > 8 bit APIC ID, say Y.
1902 source "drivers/pci/pcie/Kconfig"
1904 source "drivers/pci/Kconfig"
1906 # x86_64 have no ISA slots, but do have ISA-style DMA.
1907 config ISA_DMA_API
1908 def_bool y
1910 if X86_32
1912 config ISA
1913 bool "ISA support"
1914 ---help---
1915 Find out whether you have ISA slots on your motherboard. ISA is the
1916 name of a bus system, i.e. the way the CPU talks to the other stuff
1917 inside your box. Other bus systems are PCI, EISA, MicroChannel
1918 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
1919 newer boards don't support it. If you have ISA, say Y, otherwise N.
1921 config EISA
1922 bool "EISA support"
1923 depends on ISA
1924 ---help---
1925 The Extended Industry Standard Architecture (EISA) bus was
1926 developed as an open alternative to the IBM MicroChannel bus.
1928 The EISA bus provided some of the features of the IBM MicroChannel
1929 bus while maintaining backward compatibility with cards made for
1930 the older ISA bus. The EISA bus saw limited use between 1988 and
1931 1995 when it was made obsolete by the PCI bus.
1933 Say Y here if you are building a kernel for an EISA-based machine.
1935 Otherwise, say N.
1937 source "drivers/eisa/Kconfig"
1939 config MCA
1940 bool "MCA support"
1941 ---help---
1942 MicroChannel Architecture is found in some IBM PS/2 machines and
1943 laptops. It is a bus system similar to PCI or ISA. See
1944 <file:Documentation/mca.txt> (and especially the web page given
1945 there) before attempting to build an MCA bus kernel.
1947 source "drivers/mca/Kconfig"
1949 config SCx200
1950 tristate "NatSemi SCx200 support"
1951 ---help---
1952 This provides basic support for National Semiconductor's
1953 (now AMD's) Geode processors. The driver probes for the
1954 PCI-IDs of several on-chip devices, so its a good dependency
1955 for other scx200_* drivers.
1957 If compiled as a module, the driver is named scx200.
1959 config SCx200HR_TIMER
1960 tristate "NatSemi SCx200 27MHz High-Resolution Timer Support"
1961 depends on SCx200 && GENERIC_TIME
1962 default y
1963 ---help---
1964 This driver provides a clocksource built upon the on-chip
1965 27MHz high-resolution timer. Its also a workaround for
1966 NSC Geode SC-1100's buggy TSC, which loses time when the
1967 processor goes idle (as is done by the scheduler). The
1968 other workaround is idle=poll boot option.
1970 config GEODE_MFGPT_TIMER
1971 def_bool y
1972 prompt "Geode Multi-Function General Purpose Timer (MFGPT) events"
1973 depends on MGEODE_LX && GENERIC_TIME && GENERIC_CLOCKEVENTS
1974 ---help---
1975 This driver provides a clock event source based on the MFGPT
1976 timer(s) in the CS5535 and CS5536 companion chip for the geode.
1977 MFGPTs have a better resolution and max interval than the
1978 generic PIT, and are suitable for use as high-res timers.
1980 config OLPC
1981 bool "One Laptop Per Child support"
1982 default n
1983 ---help---
1984 Add support for detecting the unique features of the OLPC
1985 XO hardware.
1987 endif # X86_32
1989 config K8_NB
1990 def_bool y
1991 depends on AGP_AMD64 || (X86_64 && (GART_IOMMU || (PCI && NUMA)))
1993 source "drivers/pcmcia/Kconfig"
1995 source "drivers/pci/hotplug/Kconfig"
1997 endmenu
2000 menu "Executable file formats / Emulations"
2002 source "fs/Kconfig.binfmt"
2004 config IA32_EMULATION
2005 bool "IA32 Emulation"
2006 depends on X86_64
2007 select COMPAT_BINFMT_ELF
2008 ---help---
2009 Include code to run 32-bit programs under a 64-bit kernel. You should
2010 likely turn this on, unless you're 100% sure that you don't have any
2011 32-bit programs left.
2013 config IA32_AOUT
2014 tristate "IA32 a.out support"
2015 depends on IA32_EMULATION
2016 ---help---
2017 Support old a.out binaries in the 32bit emulation.
2019 config COMPAT
2020 def_bool y
2021 depends on IA32_EMULATION
2023 config COMPAT_FOR_U64_ALIGNMENT
2024 def_bool COMPAT
2025 depends on X86_64
2027 config SYSVIPC_COMPAT
2028 def_bool y
2029 depends on COMPAT && SYSVIPC
2031 endmenu
2034 config HAVE_ATOMIC_IOMAP
2035 def_bool y
2036 depends on X86_32
2038 source "net/Kconfig"
2040 source "drivers/Kconfig"
2042 source "drivers/firmware/Kconfig"
2044 source "fs/Kconfig"
2046 source "arch/x86/Kconfig.debug"
2048 source "security/Kconfig"
2050 source "crypto/Kconfig"
2052 source "arch/x86/kvm/Kconfig"
2054 source "lib/Kconfig"