| blob | 2492c7f27e8768486489550f44026b2d7eac69a6 |
1 # Select 32 or 64 bit
2 config 64BIT
3 bool "64-bit kernel" if ARCH = "x86"
4 default ARCH = "x86_64"
5 ---help---
6 Say yes to build a 64-bit kernel - formerly known as x86_64
7 Say no to build a 32-bit kernel - formerly known as i386
9 config X86_32
10 def_bool !64BIT
11 select CLKSRC_I8253
13 config X86_64
14 def_bool 64BIT
16 ### Arch settings
17 config X86
18 def_bool y
19 select HAVE_AOUT if X86_32
20 select HAVE_UNSTABLE_SCHED_CLOCK
21 select HAVE_IDE
22 select HAVE_OPROFILE
23 select HAVE_PCSPKR_PLATFORM
24 select HAVE_PERF_EVENTS
25 select HAVE_IRQ_WORK
26 select HAVE_IOREMAP_PROT
27 select HAVE_KPROBES
28 select HAVE_MEMBLOCK
29 select HAVE_MEMBLOCK_NODE_MAP
30 select ARCH_DISCARD_MEMBLOCK
31 select ARCH_WANT_OPTIONAL_GPIOLIB
32 select ARCH_WANT_FRAME_POINTERS
33 select HAVE_DMA_ATTRS
34 select HAVE_KRETPROBES
35 select HAVE_OPTPROBES
36 select HAVE_FTRACE_MCOUNT_RECORD
37 select HAVE_C_RECORDMCOUNT
38 select HAVE_DYNAMIC_FTRACE
39 select HAVE_FUNCTION_TRACER
40 select HAVE_FUNCTION_GRAPH_TRACER
41 select HAVE_FUNCTION_GRAPH_FP_TEST
42 select HAVE_FUNCTION_TRACE_MCOUNT_TEST
43 select HAVE_FTRACE_NMI_ENTER if DYNAMIC_FTRACE
44 select HAVE_SYSCALL_TRACEPOINTS
45 select HAVE_KVM
46 select HAVE_ARCH_KGDB
47 select HAVE_ARCH_TRACEHOOK
48 select HAVE_GENERIC_DMA_COHERENT if X86_32
49 select HAVE_EFFICIENT_UNALIGNED_ACCESS
50 select USER_STACKTRACE_SUPPORT
51 select HAVE_REGS_AND_STACK_ACCESS_API
52 select HAVE_DMA_API_DEBUG
53 select HAVE_KERNEL_GZIP
54 select HAVE_KERNEL_BZIP2
55 select HAVE_KERNEL_LZMA
56 select HAVE_KERNEL_XZ
57 select HAVE_KERNEL_LZO
58 select HAVE_HW_BREAKPOINT
59 select HAVE_MIXED_BREAKPOINTS_REGS
60 select PERF_EVENTS
61 select HAVE_PERF_EVENTS_NMI
62 select ANON_INODES
63 select HAVE_ALIGNED_STRUCT_PAGE if SLUB && !M386
64 select HAVE_CMPXCHG_LOCAL if !M386
65 select HAVE_CMPXCHG_DOUBLE
66 select HAVE_ARCH_KMEMCHECK
67 select HAVE_USER_RETURN_NOTIFIER
68 select ARCH_BINFMT_ELF_RANDOMIZE_PIE
69 select HAVE_ARCH_JUMP_LABEL
70 select HAVE_TEXT_POKE_SMP
71 select HAVE_GENERIC_HARDIRQS
72 select HAVE_SPARSE_IRQ
73 select SPARSE_IRQ
74 select GENERIC_FIND_FIRST_BIT
75 select GENERIC_IRQ_PROBE
76 select GENERIC_PENDING_IRQ if SMP
77 select GENERIC_IRQ_SHOW
78 select GENERIC_CLOCKEVENTS_MIN_ADJUST
79 select IRQ_FORCED_THREADING
80 select USE_GENERIC_SMP_HELPERS if SMP
81 select HAVE_BPF_JIT if (X86_64 && NET)
82 select CLKEVT_I8253
83 select ARCH_HAVE_NMI_SAFE_CMPXCHG
84 select GENERIC_IOMAP
86 config INSTRUCTION_DECODER
87 def_bool (KPROBES || PERF_EVENTS)
89 config OUTPUT_FORMAT
90 string
91 default "elf32-i386" if X86_32
92 default "elf64-x86-64" if X86_64
94 config ARCH_DEFCONFIG
95 string
96 default "arch/x86/configs/i386_defconfig" if X86_32
97 default "arch/x86/configs/x86_64_defconfig" if X86_64
99 config GENERIC_CMOS_UPDATE
100 def_bool y
102 config CLOCKSOURCE_WATCHDOG
103 def_bool y
105 config GENERIC_CLOCKEVENTS
106 def_bool y
108 config ARCH_CLOCKSOURCE_DATA
109 def_bool y
110 depends on X86_64
112 config GENERIC_CLOCKEVENTS_BROADCAST
113 def_bool y
114 depends on X86_64 || (X86_32 && X86_LOCAL_APIC)
116 config LOCKDEP_SUPPORT
117 def_bool y
119 config STACKTRACE_SUPPORT
120 def_bool y
122 config HAVE_LATENCYTOP_SUPPORT
123 def_bool y
125 config MMU
126 def_bool y
128 config SBUS
129 bool
131 config NEED_DMA_MAP_STATE
132 def_bool (X86_64 || INTEL_IOMMU || DMA_API_DEBUG)
134 config NEED_SG_DMA_LENGTH
135 def_bool y
137 config GENERIC_ISA_DMA
138 def_bool ISA_DMA_API
140 config GENERIC_BUG
141 def_bool y
142 depends on BUG
143 select GENERIC_BUG_RELATIVE_POINTERS if X86_64
145 config GENERIC_BUG_RELATIVE_POINTERS
146 bool
148 config GENERIC_HWEIGHT
149 def_bool y
151 config GENERIC_GPIO
152 bool
154 config ARCH_MAY_HAVE_PC_FDC
155 def_bool ISA_DMA_API
157 config RWSEM_GENERIC_SPINLOCK
158 def_bool !X86_XADD
160 config RWSEM_XCHGADD_ALGORITHM
161 def_bool X86_XADD
163 config ARCH_HAS_CPU_IDLE_WAIT
164 def_bool y
166 config GENERIC_CALIBRATE_DELAY
167 def_bool y
169 config GENERIC_TIME_VSYSCALL
170 bool
171 default X86_64
173 config ARCH_HAS_CPU_RELAX
174 def_bool y
176 config ARCH_HAS_DEFAULT_IDLE
177 def_bool y
179 config ARCH_HAS_CACHE_LINE_SIZE
180 def_bool y
182 config HAVE_SETUP_PER_CPU_AREA
183 def_bool y
185 config NEED_PER_CPU_EMBED_FIRST_CHUNK
186 def_bool y
188 config NEED_PER_CPU_PAGE_FIRST_CHUNK
189 def_bool y
191 config ARCH_HIBERNATION_POSSIBLE
192 def_bool y
194 config ARCH_SUSPEND_POSSIBLE
195 def_bool y
197 config ZONE_DMA32
198 bool
199 default X86_64
201 config AUDIT_ARCH
202 bool
203 default X86_64
205 config ARCH_SUPPORTS_OPTIMIZED_INLINING
206 def_bool y
208 config ARCH_SUPPORTS_DEBUG_PAGEALLOC
209 def_bool y
211 config HAVE_INTEL_TXT
212 def_bool y
213 depends on EXPERIMENTAL && INTEL_IOMMU && ACPI
215 config X86_32_SMP
216 def_bool y
217 depends on X86_32 && SMP
219 config X86_64_SMP
220 def_bool y
221 depends on X86_64 && SMP
223 config X86_HT
224 def_bool y
225 depends on SMP
227 config X86_32_LAZY_GS
228 def_bool y
229 depends on X86_32 && !CC_STACKPROTECTOR
231 config ARCH_HWEIGHT_CFLAGS
232 string
233 default "-fcall-saved-ecx -fcall-saved-edx" if X86_32
234 default "-fcall-saved-rdi -fcall-saved-rsi -fcall-saved-rdx -fcall-saved-rcx -fcall-saved-r8 -fcall-saved-r9 -fcall-saved-r10 -fcall-saved-r11" if X86_64
236 config KTIME_SCALAR
237 def_bool X86_32
239 config ARCH_CPU_PROBE_RELEASE
240 def_bool y
241 depends on HOTPLUG_CPU
243 source "init/Kconfig"
244 source "kernel/Kconfig.freezer"
246 menu "Processor type and features"
248 config ZONE_DMA
249 bool "DMA memory allocation support" if EXPERT
250 default y
251 help
252 DMA memory allocation support allows devices with less than 32-bit
253 addressing to allocate within the first 16MB of address space.
254 Disable if no such devices will be used.
256 If unsure, say Y.
258 source "kernel/time/Kconfig"
260 config SMP
261 bool "Symmetric multi-processing support"
262 ---help---
263 This enables support for systems with more than one CPU. If you have
264 a system with only one CPU, like most personal computers, say N. If
265 you have a system with more than one CPU, say Y.
267 If you say N here, the kernel will run on single and multiprocessor
268 machines, but will use only one CPU of a multiprocessor machine. If
269 you say Y here, the kernel will run on many, but not all,
270 singleprocessor machines. On a singleprocessor machine, the kernel
271 will run faster if you say N here.
273 Note that if you say Y here and choose architecture "586" or
274 "Pentium" under "Processor family", the kernel will not work on 486
275 architectures. Similarly, multiprocessor kernels for the "PPro"
276 architecture may not work on all Pentium based boards.
278 People using multiprocessor machines who say Y here should also say
279 Y to "Enhanced Real Time Clock Support", below. The "Advanced Power
280 Management" code will be disabled if you say Y here.
282 See also <file:Documentation/x86/i386/IO-APIC.txt>,
283 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
284 <http://www.tldp.org/docs.html#howto>.
286 If you don't know what to do here, say N.
288 config X86_X2APIC
289 bool "Support x2apic"
290 depends on X86_LOCAL_APIC && X86_64 && IRQ_REMAP
291 ---help---
292 This enables x2apic support on CPUs that have this feature.
294 This allows 32-bit apic IDs (so it can support very large systems),
295 and accesses the local apic via MSRs not via mmio.
297 If you don't know what to do here, say N.
299 config X86_MPPARSE
300 bool "Enable MPS table" if ACPI
301 default y
302 depends on X86_LOCAL_APIC
303 ---help---
304 For old smp systems that do not have proper acpi support. Newer systems
305 (esp with 64bit cpus) with acpi support, MADT and DSDT will override it
307 config X86_BIGSMP
308 bool "Support for big SMP systems with more than 8 CPUs"
309 depends on X86_32 && SMP
310 ---help---
311 This option is needed for the systems that have more than 8 CPUs
313 if X86_32
314 config X86_EXTENDED_PLATFORM
315 bool "Support for extended (non-PC) x86 platforms"
316 default y
317 ---help---
318 If you disable this option then the kernel will only support
319 standard PC platforms. (which covers the vast majority of
320 systems out there.)
322 If you enable this option then you'll be able to select support
323 for the following (non-PC) 32 bit x86 platforms:
324 AMD Elan
325 NUMAQ (IBM/Sequent)
326 RDC R-321x SoC
327 SGI 320/540 (Visual Workstation)
328 Summit/EXA (IBM x440)
329 Unisys ES7000 IA32 series
330 Moorestown MID devices
332 If you have one of these systems, or if you want to build a
333 generic distribution kernel, say Y here - otherwise say N.
334 endif
336 if X86_64
337 config X86_EXTENDED_PLATFORM
338 bool "Support for extended (non-PC) x86 platforms"
339 default y
340 ---help---
341 If you disable this option then the kernel will only support
342 standard PC platforms. (which covers the vast majority of
343 systems out there.)
345 If you enable this option then you'll be able to select support
346 for the following (non-PC) 64 bit x86 platforms:
347 Numascale NumaChip
348 ScaleMP vSMP
349 SGI Ultraviolet
351 If you have one of these systems, or if you want to build a
352 generic distribution kernel, say Y here - otherwise say N.
353 endif
354 # This is an alphabetically sorted list of 64 bit extended platforms
355 # Please maintain the alphabetic order if and when there are additions
356 config X86_NUMACHIP
357 bool "Numascale NumaChip"
358 depends on X86_64
359 depends on X86_EXTENDED_PLATFORM
360 depends on NUMA
361 depends on SMP
362 depends on X86_X2APIC
363 ---help---
364 Adds support for Numascale NumaChip large-SMP systems. Needed to
365 enable more than ~168 cores.
366 If you don't have one of these, you should say N here.
368 config X86_VSMP
369 bool "ScaleMP vSMP"
370 select PARAVIRT_GUEST
371 select PARAVIRT
372 depends on X86_64 && PCI
373 depends on X86_EXTENDED_PLATFORM
374 ---help---
375 Support for ScaleMP vSMP systems. Say 'Y' here if this kernel is
376 supposed to run on these EM64T-based machines. Only choose this option
377 if you have one of these machines.
379 config X86_UV
380 bool "SGI Ultraviolet"
381 depends on X86_64
382 depends on X86_EXTENDED_PLATFORM
383 depends on NUMA
384 depends on X86_X2APIC
385 ---help---
386 This option is needed in order to support SGI Ultraviolet systems.
387 If you don't have one of these, you should say N here.
389 # Following is an alphabetically sorted list of 32 bit extended platforms
390 # Please maintain the alphabetic order if and when there are additions
392 config X86_INTEL_CE
393 bool "CE4100 TV platform"
394 depends on PCI
395 depends on PCI_GODIRECT
396 depends on X86_32
397 depends on X86_EXTENDED_PLATFORM
398 select X86_REBOOTFIXUPS
399 select OF
400 select OF_EARLY_FLATTREE
401 ---help---
402 Select for the Intel CE media processor (CE4100) SOC.
403 This option compiles in support for the CE4100 SOC for settop
404 boxes and media devices.
406 config X86_WANT_INTEL_MID
407 bool "Intel MID platform support"
408 depends on X86_32
409 depends on X86_EXTENDED_PLATFORM
410 ---help---
411 Select to build a kernel capable of supporting Intel MID platform
412 systems which do not have the PCI legacy interfaces (Moorestown,
413 Medfield). If you are building for a PC class system say N here.
415 if X86_WANT_INTEL_MID
417 config X86_INTEL_MID
418 bool
420 config X86_MRST
421 bool "Moorestown MID platform"
422 depends on PCI
423 depends on PCI_GOANY
424 depends on X86_IO_APIC
425 select X86_INTEL_MID
426 select SFI
427 select DW_APB_TIMER
428 select APB_TIMER
429 select I2C
430 select SPI
431 select INTEL_SCU_IPC
432 select X86_PLATFORM_DEVICES
433 ---help---
434 Moorestown is Intel's Low Power Intel Architecture (LPIA) based Moblin
435 Internet Device(MID) platform. Moorestown consists of two chips:
436 Lincroft (CPU core, graphics, and memory controller) and Langwell IOH.
437 Unlike standard x86 PCs, Moorestown does not have many legacy devices
438 nor standard legacy replacement devices/features. e.g. Moorestown does
439 not contain i8259, i8254, HPET, legacy BIOS, most of the io ports.
441 config X86_MDFLD
442 bool "Medfield MID platform"
443 depends on PCI
444 depends on PCI_GOANY
445 depends on X86_IO_APIC
446 select X86_INTEL_MID
447 select SFI
448 select DW_APB_TIMER
449 select APB_TIMER
450 select I2C
451 select SPI
452 select INTEL_SCU_IPC
453 select X86_PLATFORM_DEVICES
454 ---help---
455 Medfield is Intel's Low Power Intel Architecture (LPIA) based Moblin
456 Internet Device(MID) platform.
457 Unlike standard x86 PCs, Medfield does not have many legacy devices
458 nor standard legacy replacement devices/features. e.g. Medfield does
459 not contain i8259, i8254, HPET, legacy BIOS, most of the io ports.
461 endif
463 config X86_RDC321X
464 bool "RDC R-321x SoC"
465 depends on X86_32
466 depends on X86_EXTENDED_PLATFORM
467 select M486
468 select X86_REBOOTFIXUPS
469 ---help---
470 This option is needed for RDC R-321x system-on-chip, also known
471 as R-8610-(G).
472 If you don't have one of these chips, you should say N here.
474 config X86_32_NON_STANDARD
475 bool "Support non-standard 32-bit SMP architectures"
476 depends on X86_32 && SMP
477 depends on X86_EXTENDED_PLATFORM
478 ---help---
479 This option compiles in the NUMAQ, Summit, bigsmp, ES7000, default
480 subarchitectures. It is intended for a generic binary kernel.
481 if you select them all, kernel will probe it one by one. and will
482 fallback to default.
484 # Alphabetically sorted list of Non standard 32 bit platforms
486 config X86_NUMAQ
487 bool "NUMAQ (IBM/Sequent)"
488 depends on X86_32_NON_STANDARD
489 depends on PCI
490 select NUMA
491 select X86_MPPARSE
492 ---help---
493 This option is used for getting Linux to run on a NUMAQ (IBM/Sequent)
494 NUMA multiquad box. This changes the way that processors are
495 bootstrapped, and uses Clustered Logical APIC addressing mode instead
496 of Flat Logical. You will need a new lynxer.elf file to flash your
497 firmware with - send email to <Martin.Bligh@us.ibm.com>.
499 config X86_SUPPORTS_MEMORY_FAILURE
500 def_bool y
501 # MCE code calls memory_failure():
502 depends on X86_MCE
503 # On 32-bit this adds too big of NODES_SHIFT and we run out of page flags:
504 depends on !X86_NUMAQ
505 # On 32-bit SPARSEMEM adds too big of SECTIONS_WIDTH:
506 depends on X86_64 || !SPARSEMEM
507 select ARCH_SUPPORTS_MEMORY_FAILURE
509 config X86_VISWS
510 bool "SGI 320/540 (Visual Workstation)"
511 depends on X86_32 && PCI && X86_MPPARSE && PCI_GODIRECT
512 depends on X86_32_NON_STANDARD
513 ---help---
514 The SGI Visual Workstation series is an IA32-based workstation
515 based on SGI systems chips with some legacy PC hardware attached.
517 Say Y here to create a kernel to run on the SGI 320 or 540.
519 A kernel compiled for the Visual Workstation will run on general
520 PCs as well. See <file:Documentation/sgi-visws.txt> for details.
522 config X86_SUMMIT
523 bool "Summit/EXA (IBM x440)"
524 depends on X86_32_NON_STANDARD
525 ---help---
526 This option is needed for IBM systems that use the Summit/EXA chipset.
527 In particular, it is needed for the x440.
529 config X86_ES7000
530 bool "Unisys ES7000 IA32 series"
531 depends on X86_32_NON_STANDARD && X86_BIGSMP
532 ---help---
533 Support for Unisys ES7000 systems. Say 'Y' here if this kernel is
534 supposed to run on an IA32-based Unisys ES7000 system.
536 config X86_32_IRIS
537 tristate "Eurobraille/Iris poweroff module"
538 depends on X86_32
539 ---help---
540 The Iris machines from EuroBraille do not have APM or ACPI support
541 to shut themselves down properly. A special I/O sequence is
542 needed to do so, which is what this module does at
543 kernel shutdown.
545 This is only for Iris machines from EuroBraille.
547 If unused, say N.
549 config SCHED_OMIT_FRAME_POINTER
550 def_bool y
551 prompt "Single-depth WCHAN output"
552 depends on X86
553 ---help---
554 Calculate simpler /proc/<PID>/wchan values. If this option
555 is disabled then wchan values will recurse back to the
556 caller function. This provides more accurate wchan values,
557 at the expense of slightly more scheduling overhead.
559 If in doubt, say "Y".
561 menuconfig PARAVIRT_GUEST
562 bool "Paravirtualized guest support"
563 ---help---
564 Say Y here to get to see options related to running Linux under
565 various hypervisors. This option alone does not add any kernel code.
567 If you say N, all options in this submenu will be skipped and disabled.
569 if PARAVIRT_GUEST
571 config PARAVIRT_TIME_ACCOUNTING
572 bool "Paravirtual steal time accounting"
573 select PARAVIRT
574 default n
575 ---help---
576 Select this option to enable fine granularity task steal time
577 accounting. Time spent executing other tasks in parallel with
578 the current vCPU is discounted from the vCPU power. To account for
579 that, there can be a small performance impact.
581 If in doubt, say N here.
583 source "arch/x86/xen/Kconfig"
585 config KVM_CLOCK
586 bool "KVM paravirtualized clock"
587 select PARAVIRT
588 select PARAVIRT_CLOCK
589 ---help---
590 Turning on this option will allow you to run a paravirtualized clock
591 when running over the KVM hypervisor. Instead of relying on a PIT
592 (or probably other) emulation by the underlying device model, the host
593 provides the guest with timing infrastructure such as time of day, and
594 system time
596 config KVM_GUEST
597 bool "KVM Guest support"
598 select PARAVIRT
599 ---help---
600 This option enables various optimizations for running under the KVM
601 hypervisor.
603 source "arch/x86/lguest/Kconfig"
605 config PARAVIRT
606 bool "Enable paravirtualization code"
607 ---help---
608 This changes the kernel so it can modify itself when it is run
609 under a hypervisor, potentially improving performance significantly
610 over full virtualization. However, when run without a hypervisor
611 the kernel is theoretically slower and slightly larger.
613 config PARAVIRT_SPINLOCKS
614 bool "Paravirtualization layer for spinlocks"
615 depends on PARAVIRT && SMP && EXPERIMENTAL
616 ---help---
617 Paravirtualized spinlocks allow a pvops backend to replace the
618 spinlock implementation with something virtualization-friendly
619 (for example, block the virtual CPU rather than spinning).
621 Unfortunately the downside is an up to 5% performance hit on
622 native kernels, with various workloads.
624 If you are unsure how to answer this question, answer N.
626 config PARAVIRT_CLOCK
627 bool
629 endif
631 config PARAVIRT_DEBUG
632 bool "paravirt-ops debugging"
633 depends on PARAVIRT && DEBUG_KERNEL
634 ---help---
635 Enable to debug paravirt_ops internals. Specifically, BUG if
636 a paravirt_op is missing when it is called.
638 config NO_BOOTMEM
639 def_bool y
641 config MEMTEST
642 bool "Memtest"
643 ---help---
644 This option adds a kernel parameter 'memtest', which allows memtest
645 to be set.
646 memtest=0, mean disabled; -- default
647 memtest=1, mean do 1 test pattern;
648 ...
649 memtest=4, mean do 4 test patterns.
650 If you are unsure how to answer this question, answer N.
652 config X86_SUMMIT_NUMA
653 def_bool y
654 depends on X86_32 && NUMA && X86_32_NON_STANDARD
656 config X86_CYCLONE_TIMER
657 def_bool y
658 depends on X86_SUMMIT
660 source "arch/x86/Kconfig.cpu"
662 config HPET_TIMER
663 def_bool X86_64
664 prompt "HPET Timer Support" if X86_32
665 ---help---
666 Use the IA-PC HPET (High Precision Event Timer) to manage
667 time in preference to the PIT and RTC, if a HPET is
668 present.
669 HPET is the next generation timer replacing legacy 8254s.
670 The HPET provides a stable time base on SMP
671 systems, unlike the TSC, but it is more expensive to access,
672 as it is off-chip. You can find the HPET spec at
673 <http://www.intel.com/hardwaredesign/hpetspec_1.pdf>.
675 You can safely choose Y here. However, HPET will only be
676 activated if the platform and the BIOS support this feature.
677 Otherwise the 8254 will be used for timing services.
679 Choose N to continue using the legacy 8254 timer.
681 config HPET_EMULATE_RTC
682 def_bool y
683 depends on HPET_TIMER && (RTC=y || RTC=m || RTC_DRV_CMOS=m || RTC_DRV_CMOS=y)
685 config APB_TIMER
686 def_bool y if X86_INTEL_MID
687 prompt "Intel MID APB Timer Support" if X86_INTEL_MID
688 select DW_APB_TIMER
689 depends on X86_INTEL_MID && SFI
690 help
691 APB timer is the replacement for 8254, HPET on X86 MID platforms.
692 The APBT provides a stable time base on SMP
693 systems, unlike the TSC, but it is more expensive to access,
694 as it is off-chip. APB timers are always running regardless of CPU
695 C states, they are used as per CPU clockevent device when possible.
697 # Mark as expert because too many people got it wrong.
698 # The code disables itself when not needed.
699 config DMI
700 default y
701 bool "Enable DMI scanning" if EXPERT
702 ---help---
703 Enabled scanning of DMI to identify machine quirks. Say Y
704 here unless you have verified that your setup is not
705 affected by entries in the DMI blacklist. Required by PNP
706 BIOS code.
708 config GART_IOMMU
709 bool "GART IOMMU support" if EXPERT
710 default y
711 select SWIOTLB
712 depends on X86_64 && PCI && AMD_NB
713 ---help---
714 Support for full DMA access of devices with 32bit memory access only
715 on systems with more than 3GB. This is usually needed for USB,
716 sound, many IDE/SATA chipsets and some other devices.
717 Provides a driver for the AMD Athlon64/Opteron/Turion/Sempron GART
718 based hardware IOMMU and a software bounce buffer based IOMMU used
719 on Intel systems and as fallback.
720 The code is only active when needed (enough memory and limited
721 device) unless CONFIG_IOMMU_DEBUG or iommu=force is specified
722 too.
724 config CALGARY_IOMMU
725 bool "IBM Calgary IOMMU support"
726 select SWIOTLB
727 depends on X86_64 && PCI && EXPERIMENTAL
728 ---help---
729 Support for hardware IOMMUs in IBM's xSeries x366 and x460
730 systems. Needed to run systems with more than 3GB of memory
731 properly with 32-bit PCI devices that do not support DAC
732 (Double Address Cycle). Calgary also supports bus level
733 isolation, where all DMAs pass through the IOMMU. This
734 prevents them from going anywhere except their intended
735 destination. This catches hard-to-find kernel bugs and
736 mis-behaving drivers and devices that do not use the DMA-API
737 properly to set up their DMA buffers. The IOMMU can be
738 turned off at boot time with the iommu=off parameter.
739 Normally the kernel will make the right choice by itself.
740 If unsure, say Y.
742 config CALGARY_IOMMU_ENABLED_BY_DEFAULT
743 def_bool y
744 prompt "Should Calgary be enabled by default?"
745 depends on CALGARY_IOMMU
746 ---help---
747 Should Calgary be enabled by default? if you choose 'y', Calgary
748 will be used (if it exists). If you choose 'n', Calgary will not be
749 used even if it exists. If you choose 'n' and would like to use
750 Calgary anyway, pass 'iommu=calgary' on the kernel command line.
751 If unsure, say Y.
753 # need this always selected by IOMMU for the VIA workaround
754 config SWIOTLB
755 def_bool y if X86_64
756 ---help---
757 Support for software bounce buffers used on x86-64 systems
758 which don't have a hardware IOMMU (e.g. the current generation
759 of Intel's x86-64 CPUs). Using this PCI devices which can only
760 access 32-bits of memory can be used on systems with more than
761 3 GB of memory. If unsure, say Y.
763 config IOMMU_HELPER
764 def_bool (CALGARY_IOMMU || GART_IOMMU || SWIOTLB || AMD_IOMMU)
766 config MAXSMP
767 bool "Enable Maximum number of SMP Processors and NUMA Nodes"
768 depends on X86_64 && SMP && DEBUG_KERNEL && EXPERIMENTAL
769 select CPUMASK_OFFSTACK
770 ---help---
771 Enable maximum number of CPUS and NUMA Nodes for this architecture.
772 If unsure, say N.
774 config NR_CPUS
775 int "Maximum number of CPUs" if SMP && !MAXSMP
776 range 2 8 if SMP && X86_32 && !X86_BIGSMP
777 range 2 512 if SMP && !MAXSMP
778 default "1" if !SMP
779 default "4096" if MAXSMP
780 default "32" if SMP && (X86_NUMAQ || X86_SUMMIT || X86_BIGSMP || X86_ES7000)
781 default "8" if SMP
782 ---help---
783 This allows you to specify the maximum number of CPUs which this
784 kernel will support. The maximum supported value is 512 and the
785 minimum value which makes sense is 2.
787 This is purely to save memory - each supported CPU adds
788 approximately eight kilobytes to the kernel image.
790 config SCHED_SMT
791 bool "SMT (Hyperthreading) scheduler support"
792 depends on X86_HT
793 ---help---
794 SMT scheduler support improves the CPU scheduler's decision making
795 when dealing with Intel Pentium 4 chips with HyperThreading at a
796 cost of slightly increased overhead in some places. If unsure say
797 N here.
799 config SCHED_MC
800 def_bool y
801 prompt "Multi-core scheduler support"
802 depends on X86_HT
803 ---help---
804 Multi-core scheduler support improves the CPU scheduler's decision
805 making when dealing with multi-core CPU chips at a cost of slightly
806 increased overhead in some places. If unsure say N here.
808 config IRQ_TIME_ACCOUNTING
809 def_bool y
811 source "kernel/Kconfig.preempt"
813 config X86_UP_APIC
814 bool "Local APIC support on uniprocessors"
815 depends on X86_32 && !SMP && !X86_32_NON_STANDARD
816 ---help---
817 A local APIC (Advanced Programmable Interrupt Controller) is an
818 integrated interrupt controller in the CPU. If you have a single-CPU
819 system which has a processor with a local APIC, you can say Y here to
820 enable and use it. If you say Y here even though your machine doesn't
821 have a local APIC, then the kernel will still run with no slowdown at
822 all. The local APIC supports CPU-generated self-interrupts (timer,
823 performance counters), and the NMI watchdog which detects hard
824 lockups.
826 config X86_UP_IOAPIC
827 bool "IO-APIC support on uniprocessors"
828 depends on X86_UP_APIC
829 ---help---
830 An IO-APIC (I/O Advanced Programmable Interrupt Controller) is an
831 SMP-capable replacement for PC-style interrupt controllers. Most
832 SMP systems and many recent uniprocessor systems have one.
834 If you have a single-CPU system with an IO-APIC, you can say Y here
835 to use it. If you say Y here even though your machine doesn't have
836 an IO-APIC, then the kernel will still run with no slowdown at all.
838 config X86_LOCAL_APIC
839 def_bool y
840 depends on X86_64 || SMP || X86_32_NON_STANDARD || X86_UP_APIC
842 config X86_IO_APIC
843 def_bool y
844 depends on X86_64 || SMP || X86_32_NON_STANDARD || X86_UP_IOAPIC
846 config X86_VISWS_APIC
847 def_bool y
848 depends on X86_32 && X86_VISWS
850 config X86_REROUTE_FOR_BROKEN_BOOT_IRQS
851 bool "Reroute for broken boot IRQs"
852 depends on X86_IO_APIC
853 ---help---
854 This option enables a workaround that fixes a source of
855 spurious interrupts. This is recommended when threaded
856 interrupt handling is used on systems where the generation of
857 superfluous "boot interrupts" cannot be disabled.
859 Some chipsets generate a legacy INTx "boot IRQ" when the IRQ
860 entry in the chipset's IO-APIC is masked (as, e.g. the RT
861 kernel does during interrupt handling). On chipsets where this
862 boot IRQ generation cannot be disabled, this workaround keeps
863 the original IRQ line masked so that only the equivalent "boot
864 IRQ" is delivered to the CPUs. The workaround also tells the
865 kernel to set up the IRQ handler on the boot IRQ line. In this
866 way only one interrupt is delivered to the kernel. Otherwise
867 the spurious second interrupt may cause the kernel to bring
868 down (vital) interrupt lines.
870 Only affects "broken" chipsets. Interrupt sharing may be
871 increased on these systems.
873 config X86_MCE
874 bool "Machine Check / overheating reporting"
875 ---help---
876 Machine Check support allows the processor to notify the
877 kernel if it detects a problem (e.g. overheating, data corruption).
878 The action the kernel takes depends on the severity of the problem,
879 ranging from warning messages to halting the machine.
881 config X86_MCE_INTEL
882 def_bool y
883 prompt "Intel MCE features"
884 depends on X86_MCE && X86_LOCAL_APIC
885 ---help---
886 Additional support for intel specific MCE features such as
887 the thermal monitor.
889 config X86_MCE_AMD
890 def_bool y
891 prompt "AMD MCE features"
892 depends on X86_MCE && X86_LOCAL_APIC
893 ---help---
894 Additional support for AMD specific MCE features such as
895 the DRAM Error Threshold.
897 config X86_ANCIENT_MCE
898 bool "Support for old Pentium 5 / WinChip machine checks"
899 depends on X86_32 && X86_MCE
900 ---help---
901 Include support for machine check handling on old Pentium 5 or WinChip
902 systems. These typically need to be enabled explicitely on the command
903 line.
905 config X86_MCE_THRESHOLD
906 depends on X86_MCE_AMD || X86_MCE_INTEL
907 def_bool y
909 config X86_MCE_INJECT
910 depends on X86_MCE
911 tristate "Machine check injector support"
912 ---help---
913 Provide support for injecting machine checks for testing purposes.
914 If you don't know what a machine check is and you don't do kernel
915 QA it is safe to say n.
917 config X86_THERMAL_VECTOR
918 def_bool y
919 depends on X86_MCE_INTEL
921 config VM86
922 bool "Enable VM86 support" if EXPERT
923 default y
924 depends on X86_32
925 ---help---
926 This option is required by programs like DOSEMU to run 16-bit legacy
927 code on X86 processors. It also may be needed by software like
928 XFree86 to initialize some video cards via BIOS. Disabling this
929 option saves about 6k.
931 config TOSHIBA
932 tristate "Toshiba Laptop support"
933 depends on X86_32
934 ---help---
935 This adds a driver to safely access the System Management Mode of
936 the CPU on Toshiba portables with a genuine Toshiba BIOS. It does
937 not work on models with a Phoenix BIOS. The System Management Mode
938 is used to set the BIOS and power saving options on Toshiba portables.
940 For information on utilities to make use of this driver see the
941 Toshiba Linux utilities web site at:
942 <http://www.buzzard.org.uk/toshiba/>.
944 Say Y if you intend to run this kernel on a Toshiba portable.
945 Say N otherwise.
947 config I8K
948 tristate "Dell laptop support"
949 select HWMON
950 ---help---
951 This adds a driver to safely access the System Management Mode
952 of the CPU on the Dell Inspiron 8000. The System Management Mode
953 is used to read cpu temperature and cooling fan status and to
954 control the fans on the I8K portables.
956 This driver has been tested only on the Inspiron 8000 but it may
957 also work with other Dell laptops. You can force loading on other
958 models by passing the parameter `force=1' to the module. Use at
959 your own risk.
961 For information on utilities to make use of this driver see the
962 I8K Linux utilities web site at:
963 <http://people.debian.org/~dz/i8k/>
965 Say Y if you intend to run this kernel on a Dell Inspiron 8000.
966 Say N otherwise.
968 config X86_REBOOTFIXUPS
969 bool "Enable X86 board specific fixups for reboot"
970 depends on X86_32
971 ---help---
972 This enables chipset and/or board specific fixups to be done
973 in order to get reboot to work correctly. This is only needed on
974 some combinations of hardware and BIOS. The symptom, for which
975 this config is intended, is when reboot ends with a stalled/hung
976 system.
978 Currently, the only fixup is for the Geode machines using
979 CS5530A and CS5536 chipsets and the RDC R-321x SoC.
981 Say Y if you want to enable the fixup. Currently, it's safe to
982 enable this option even if you don't need it.
983 Say N otherwise.
985 config MICROCODE
986 tristate "/dev/cpu/microcode - microcode support"
987 select FW_LOADER
988 ---help---
989 If you say Y here, you will be able to update the microcode on
990 certain Intel and AMD processors. The Intel support is for the
991 IA32 family, e.g. Pentium Pro, Pentium II, Pentium III,
992 Pentium 4, Xeon etc. The AMD support is for family 0x10 and
993 0x11 processors, e.g. Opteron, Phenom and Turion 64 Ultra.
994 You will obviously need the actual microcode binary data itself
995 which is not shipped with the Linux kernel.
997 This option selects the general module only, you need to select
998 at least one vendor specific module as well.
1000 To compile this driver as a module, choose M here: the
1001 module will be called microcode.
1003 config MICROCODE_INTEL
1004 bool "Intel microcode patch loading support"
1005 depends on MICROCODE
1006 default MICROCODE
1007 select FW_LOADER
1008 ---help---
1009 This options enables microcode patch loading support for Intel
1010 processors.
1012 For latest news and information on obtaining all the required
1013 Intel ingredients for this driver, check:
1014 <http://www.urbanmyth.org/microcode/>.
1016 config MICROCODE_AMD
1017 bool "AMD microcode patch loading support"
1018 depends on MICROCODE
1019 select FW_LOADER
1020 ---help---
1021 If you select this option, microcode patch loading support for AMD
1022 processors will be enabled.
1024 config MICROCODE_OLD_INTERFACE
1025 def_bool y
1026 depends on MICROCODE
1028 config X86_MSR
1029 tristate "/dev/cpu/*/msr - Model-specific register support"
1030 ---help---
1031 This device gives privileged processes access to the x86
1032 Model-Specific Registers (MSRs). It is a character device with
1033 major 202 and minors 0 to 31 for /dev/cpu/0/msr to /dev/cpu/31/msr.
1034 MSR accesses are directed to a specific CPU on multi-processor
1035 systems.
1037 config X86_CPUID
1038 tristate "/dev/cpu/*/cpuid - CPU information support"
1039 ---help---
1040 This device gives processes access to the x86 CPUID instruction to
1041 be executed on a specific processor. It is a character device
1042 with major 203 and minors 0 to 31 for /dev/cpu/0/cpuid to
1043 /dev/cpu/31/cpuid.
1045 choice
1046 prompt "High Memory Support"
1047 default HIGHMEM64G if X86_NUMAQ
1048 default HIGHMEM4G
1049 depends on X86_32
1051 config NOHIGHMEM
1052 bool "off"
1053 depends on !X86_NUMAQ
1054 ---help---
1055 Linux can use up to 64 Gigabytes of physical memory on x86 systems.
1056 However, the address space of 32-bit x86 processors is only 4
1057 Gigabytes large. That means that, if you have a large amount of
1058 physical memory, not all of it can be "permanently mapped" by the
1059 kernel. The physical memory that's not permanently mapped is called
1060 "high memory".
1062 If you are compiling a kernel which will never run on a machine with
1063 more than 1 Gigabyte total physical RAM, answer "off" here (default
1064 choice and suitable for most users). This will result in a "3GB/1GB"
1065 split: 3GB are mapped so that each process sees a 3GB virtual memory
1066 space and the remaining part of the 4GB virtual memory space is used
1067 by the kernel to permanently map as much physical memory as
1068 possible.
1070 If the machine has between 1 and 4 Gigabytes physical RAM, then
1071 answer "4GB" here.
1073 If more than 4 Gigabytes is used then answer "64GB" here. This
1074 selection turns Intel PAE (Physical Address Extension) mode on.
1075 PAE implements 3-level paging on IA32 processors. PAE is fully
1076 supported by Linux, PAE mode is implemented on all recent Intel
1077 processors (Pentium Pro and better). NOTE: If you say "64GB" here,
1078 then the kernel will not boot on CPUs that don't support PAE!
1080 The actual amount of total physical memory will either be
1081 auto detected or can be forced by using a kernel command line option
1082 such as "mem=256M". (Try "man bootparam" or see the documentation of
1083 your boot loader (lilo or loadlin) about how to pass options to the
1084 kernel at boot time.)
1086 If unsure, say "off".
1088 config HIGHMEM4G
1089 bool "4GB"
1090 depends on !X86_NUMAQ
1091 ---help---
1092 Select this if you have a 32-bit processor and between 1 and 4
1093 gigabytes of physical RAM.
1095 config HIGHMEM64G
1096 bool "64GB"
1097 depends on !M386 && !M486
1098 select X86_PAE
1099 ---help---
1100 Select this if you have a 32-bit processor and more than 4
1101 gigabytes of physical RAM.
1103 endchoice
1105 choice
1106 depends on EXPERIMENTAL
1107 prompt "Memory split" if EXPERT
1108 default VMSPLIT_3G
1109 depends on X86_32
1110 ---help---
1111 Select the desired split between kernel and user memory.
1113 If the address range available to the kernel is less than the
1114 physical memory installed, the remaining memory will be available
1115 as "high memory". Accessing high memory is a little more costly
1116 than low memory, as it needs to be mapped into the kernel first.
1117 Note that increasing the kernel address space limits the range
1118 available to user programs, making the address space there
1119 tighter. Selecting anything other than the default 3G/1G split
1120 will also likely make your kernel incompatible with binary-only
1121 kernel modules.
1123 If you are not absolutely sure what you are doing, leave this
1124 option alone!
1126 config VMSPLIT_3G
1127 bool "3G/1G user/kernel split"
1128 config VMSPLIT_3G_OPT
1129 depends on !X86_PAE
1130 bool "3G/1G user/kernel split (for full 1G low memory)"
1131 config VMSPLIT_2G
1132 bool "2G/2G user/kernel split"
1133 config VMSPLIT_2G_OPT
1134 depends on !X86_PAE
1135 bool "2G/2G user/kernel split (for full 2G low memory)"
1136 config VMSPLIT_1G
1137 bool "1G/3G user/kernel split"
1138 endchoice
1140 config PAGE_OFFSET
1141 hex
1142 default 0xB0000000 if VMSPLIT_3G_OPT
1143 default 0x80000000 if VMSPLIT_2G
1144 default 0x78000000 if VMSPLIT_2G_OPT
1145 default 0x40000000 if VMSPLIT_1G
1146 default 0xC0000000
1147 depends on X86_32
1149 config HIGHMEM
1150 def_bool y
1151 depends on X86_32 && (HIGHMEM64G || HIGHMEM4G)
1153 config X86_PAE
1154 bool "PAE (Physical Address Extension) Support"
1155 depends on X86_32 && !HIGHMEM4G
1156 ---help---
1157 PAE is required for NX support, and furthermore enables
1158 larger swapspace support for non-overcommit purposes. It
1159 has the cost of more pagetable lookup overhead, and also
1160 consumes more pagetable space per process.
1162 config ARCH_PHYS_ADDR_T_64BIT
1163 def_bool X86_64 || X86_PAE
1165 config ARCH_DMA_ADDR_T_64BIT
1166 def_bool X86_64 || HIGHMEM64G
1168 config DIRECT_GBPAGES
1169 bool "Enable 1GB pages for kernel pagetables" if EXPERT
1170 default y
1171 depends on X86_64
1172 ---help---
1173 Allow the kernel linear mapping to use 1GB pages on CPUs that
1174 support it. This can improve the kernel's performance a tiny bit by
1175 reducing TLB pressure. If in doubt, say "Y".
1177 # Common NUMA Features
1178 config NUMA
1179 bool "Numa Memory Allocation and Scheduler Support"
1180 depends on SMP
1181 depends on X86_64 || (X86_32 && HIGHMEM64G && (X86_NUMAQ || X86_BIGSMP || X86_SUMMIT && ACPI) && EXPERIMENTAL)
1182 default y if (X86_NUMAQ || X86_SUMMIT || X86_BIGSMP)
1183 ---help---
1184 Enable NUMA (Non Uniform Memory Access) support.
1186 The kernel will try to allocate memory used by a CPU on the
1187 local memory controller of the CPU and add some more
1188 NUMA awareness to the kernel.
1190 For 64-bit this is recommended if the system is Intel Core i7
1191 (or later), AMD Opteron, or EM64T NUMA.
1193 For 32-bit this is only needed on (rare) 32-bit-only platforms
1194 that support NUMA topologies, such as NUMAQ / Summit, or if you
1195 boot a 32-bit kernel on a 64-bit NUMA platform.
1197 Otherwise, you should say N.
1199 comment "NUMA (Summit) requires SMP, 64GB highmem support, ACPI"
1200 depends on X86_32 && X86_SUMMIT && (!HIGHMEM64G || !ACPI)
1202 config AMD_NUMA
1203 def_bool y
1204 prompt "Old style AMD Opteron NUMA detection"
1205 depends on X86_64 && NUMA && PCI
1206 ---help---
1207 Enable AMD NUMA node topology detection. You should say Y here if
1208 you have a multi processor AMD system. This uses an old method to
1209 read the NUMA configuration directly from the builtin Northbridge
1210 of Opteron. It is recommended to use X86_64_ACPI_NUMA instead,
1211 which also takes priority if both are compiled in.
1213 config X86_64_ACPI_NUMA
1214 def_bool y
1215 prompt "ACPI NUMA detection"
1216 depends on X86_64 && NUMA && ACPI && PCI
1217 select ACPI_NUMA
1218 ---help---
1219 Enable ACPI SRAT based node topology detection.
1221 # Some NUMA nodes have memory ranges that span
1222 # other nodes. Even though a pfn is valid and
1223 # between a node's start and end pfns, it may not
1224 # reside on that node. See memmap_init_zone()
1225 # for details.
1226 config NODES_SPAN_OTHER_NODES
1227 def_bool y
1228 depends on X86_64_ACPI_NUMA
1230 config NUMA_EMU
1231 bool "NUMA emulation"
1232 depends on NUMA
1233 ---help---
1234 Enable NUMA emulation. A flat machine will be split
1235 into virtual nodes when booted with "numa=fake=N", where N is the
1236 number of nodes. This is only useful for debugging.
1238 config NODES_SHIFT
1239 int "Maximum NUMA Nodes (as a power of 2)" if !MAXSMP
1240 range 1 10
1241 default "10" if MAXSMP
1242 default "6" if X86_64
1243 default "4" if X86_NUMAQ
1244 default "3"
1245 depends on NEED_MULTIPLE_NODES
1246 ---help---
1247 Specify the maximum number of NUMA Nodes available on the target
1248 system. Increases memory reserved to accommodate various tables.
1250 config HAVE_ARCH_BOOTMEM
1251 def_bool y
1252 depends on X86_32 && NUMA
1254 config HAVE_ARCH_ALLOC_REMAP
1255 def_bool y
1256 depends on X86_32 && NUMA
1258 config ARCH_HAVE_MEMORY_PRESENT
1259 def_bool y
1260 depends on X86_32 && DISCONTIGMEM
1262 config NEED_NODE_MEMMAP_SIZE
1263 def_bool y
1264 depends on X86_32 && (DISCONTIGMEM || SPARSEMEM)
1266 config ARCH_FLATMEM_ENABLE
1267 def_bool y
1268 depends on X86_32 && !NUMA
1270 config ARCH_DISCONTIGMEM_ENABLE
1271 def_bool y
1272 depends on NUMA && X86_32
1274 config ARCH_DISCONTIGMEM_DEFAULT
1275 def_bool y
1276 depends on NUMA && X86_32
1278 config ARCH_SPARSEMEM_ENABLE
1279 def_bool y
1280 depends on X86_64 || NUMA || (EXPERIMENTAL && X86_32) || X86_32_NON_STANDARD
1281 select SPARSEMEM_STATIC if X86_32
1282 select SPARSEMEM_VMEMMAP_ENABLE if X86_64
1284 config ARCH_SPARSEMEM_DEFAULT
1285 def_bool y
1286 depends on X86_64
1288 config ARCH_SELECT_MEMORY_MODEL
1289 def_bool y
1290 depends on ARCH_SPARSEMEM_ENABLE
1292 config ARCH_MEMORY_PROBE
1293 def_bool X86_64
1294 depends on MEMORY_HOTPLUG
1296 config ARCH_PROC_KCORE_TEXT
1297 def_bool y
1298 depends on X86_64 && PROC_KCORE
1300 config ILLEGAL_POINTER_VALUE
1301 hex
1302 default 0 if X86_32
1303 default 0xdead000000000000 if X86_64
1305 source "mm/Kconfig"
1307 config HIGHPTE
1308 bool "Allocate 3rd-level pagetables from highmem"
1309 depends on HIGHMEM
1310 ---help---
1311 The VM uses one page table entry for each page of physical memory.
1312 For systems with a lot of RAM, this can be wasteful of precious
1313 low memory. Setting this option will put user-space page table
1314 entries in high memory.
1316 config X86_CHECK_BIOS_CORRUPTION
1317 bool "Check for low memory corruption"
1318 ---help---
1319 Periodically check for memory corruption in low memory, which
1320 is suspected to be caused by BIOS. Even when enabled in the
1321 configuration, it is disabled at runtime. Enable it by
1322 setting "memory_corruption_check=1" on the kernel command
1323 line. By default it scans the low 64k of memory every 60
1324 seconds; see the memory_corruption_check_size and
1325 memory_corruption_check_period parameters in
1326 Documentation/kernel-parameters.txt to adjust this.
1328 When enabled with the default parameters, this option has
1329 almost no overhead, as it reserves a relatively small amount
1330 of memory and scans it infrequently. It both detects corruption
1331 and prevents it from affecting the running system.
1333 It is, however, intended as a diagnostic tool; if repeatable
1334 BIOS-originated corruption always affects the same memory,
1335 you can use memmap= to prevent the kernel from using that
1336 memory.
1338 config X86_BOOTPARAM_MEMORY_CORRUPTION_CHECK
1339 bool "Set the default setting of memory_corruption_check"
1340 depends on X86_CHECK_BIOS_CORRUPTION
1341 default y
1342 ---help---
1343 Set whether the default state of memory_corruption_check is
1344 on or off.
1346 config X86_RESERVE_LOW
1347 int "Amount of low memory, in kilobytes, to reserve for the BIOS"
1348 default 64
1349 range 4 640
1350 ---help---
1351 Specify the amount of low memory to reserve for the BIOS.
1353 The first page contains BIOS data structures that the kernel
1354 must not use, so that page must always be reserved.
1356 By default we reserve the first 64K of physical RAM, as a
1357 number of BIOSes are known to corrupt that memory range
1358 during events such as suspend/resume or monitor cable
1359 insertion, so it must not be used by the kernel.
1361 You can set this to 4 if you are absolutely sure that you
1362 trust the BIOS to get all its memory reservations and usages
1363 right. If you know your BIOS have problems beyond the
1364 default 64K area, you can set this to 640 to avoid using the
1365 entire low memory range.
1367 If you have doubts about the BIOS (e.g. suspend/resume does
1368 not work or there's kernel crashes after certain hardware
1369 hotplug events) then you might want to enable
1370 X86_CHECK_BIOS_CORRUPTION=y to allow the kernel to check
1371 typical corruption patterns.
1373 Leave this to the default value of 64 if you are unsure.
1375 config MATH_EMULATION
1376 bool
1377 prompt "Math emulation" if X86_32
1378 ---help---
1379 Linux can emulate a math coprocessor (used for floating point
1380 operations) if you don't have one. 486DX and Pentium processors have
1381 a math coprocessor built in, 486SX and 386 do not, unless you added
1382 a 487DX or 387, respectively. (The messages during boot time can
1383 give you some hints here ["man dmesg"].) Everyone needs either a
1384 coprocessor or this emulation.
1386 If you don't have a math coprocessor, you need to say Y here; if you
1387 say Y here even though you have a coprocessor, the coprocessor will
1388 be used nevertheless. (This behavior can be changed with the kernel
1389 command line option "no387", which comes handy if your coprocessor
1390 is broken. Try "man bootparam" or see the documentation of your boot
1391 loader (lilo or loadlin) about how to pass options to the kernel at
1392 boot time.) This means that it is a good idea to say Y here if you
1393 intend to use this kernel on different machines.
1395 More information about the internals of the Linux math coprocessor
1396 emulation can be found in <file:arch/x86/math-emu/README>.
1398 If you are not sure, say Y; apart from resulting in a 66 KB bigger
1399 kernel, it won't hurt.
1401 config MTRR
1402 def_bool y
1403 prompt "MTRR (Memory Type Range Register) support" if EXPERT
1404 ---help---
1405 On Intel P6 family processors (Pentium Pro, Pentium II and later)
1406 the Memory Type Range Registers (MTRRs) may be used to control
1407 processor access to memory ranges. This is most useful if you have
1408 a video (VGA) card on a PCI or AGP bus. Enabling write-combining
1409 allows bus write transfers to be combined into a larger transfer
1410 before bursting over the PCI/AGP bus. This can increase performance
1411 of image write operations 2.5 times or more. Saying Y here creates a
1412 /proc/mtrr file which may be used to manipulate your processor's
1413 MTRRs. Typically the X server should use this.
1415 This code has a reasonably generic interface so that similar
1416 control registers on other processors can be easily supported
1417 as well:
1419 The Cyrix 6x86, 6x86MX and M II processors have Address Range
1420 Registers (ARRs) which provide a similar functionality to MTRRs. For
1421 these, the ARRs are used to emulate the MTRRs.
1422 The AMD K6-2 (stepping 8 and above) and K6-3 processors have two
1423 MTRRs. The Centaur C6 (WinChip) has 8 MCRs, allowing
1424 write-combining. All of these processors are supported by this code
1425 and it makes sense to say Y here if you have one of them.
1427 Saying Y here also fixes a problem with buggy SMP BIOSes which only
1428 set the MTRRs for the boot CPU and not for the secondary CPUs. This
1429 can lead to all sorts of problems, so it's good to say Y here.
1431 You can safely say Y even if your machine doesn't have MTRRs, you'll
1432 just add about 9 KB to your kernel.
1434 See <file:Documentation/x86/mtrr.txt> for more information.
1436 config MTRR_SANITIZER
1437 def_bool y
1438 prompt "MTRR cleanup support"
1439 depends on MTRR
1440 ---help---
1441 Convert MTRR layout from continuous to discrete, so X drivers can
1442 add writeback entries.
1444 Can be disabled with disable_mtrr_cleanup on the kernel command line.
1445 The largest mtrr entry size for a continuous block can be set with
1446 mtrr_chunk_size.
1448 If unsure, say Y.
1450 config MTRR_SANITIZER_ENABLE_DEFAULT
1451 int "MTRR cleanup enable value (0-1)"
1452 range 0 1
1453 default "0"
1454 depends on MTRR_SANITIZER
1455 ---help---
1456 Enable mtrr cleanup default value
1458 config MTRR_SANITIZER_SPARE_REG_NR_DEFAULT
1459 int "MTRR cleanup spare reg num (0-7)"
1460 range 0 7
1461 default "1"
1462 depends on MTRR_SANITIZER
1463 ---help---
1464 mtrr cleanup spare entries default, it can be changed via
1465 mtrr_spare_reg_nr=N on the kernel command line.
1467 config X86_PAT
1468 def_bool y
1469 prompt "x86 PAT support" if EXPERT
1470 depends on MTRR
1471 ---help---
1472 Use PAT attributes to setup page level cache control.
1474 PATs are the modern equivalents of MTRRs and are much more
1475 flexible than MTRRs.
1477 Say N here if you see bootup problems (boot crash, boot hang,
1478 spontaneous reboots) or a non-working video driver.
1480 If unsure, say Y.
1482 config ARCH_USES_PG_UNCACHED
1483 def_bool y
1484 depends on X86_PAT
1486 config ARCH_RANDOM
1487 def_bool y
1488 prompt "x86 architectural random number generator" if EXPERT
1489 ---help---
1490 Enable the x86 architectural RDRAND instruction
1491 (Intel Bull Mountain technology) to generate random numbers.
1492 If supported, this is a high bandwidth, cryptographically
1493 secure hardware random number generator.
1495 config EFI
1496 bool "EFI runtime service support"
1497 depends on ACPI
1498 ---help---
1499 This enables the kernel to use EFI runtime services that are
1500 available (such as the EFI variable services).
1502 This option is only useful on systems that have EFI firmware.
1503 In addition, you should use the latest ELILO loader available
1504 at <http://elilo.sourceforge.net> in order to take advantage
1505 of EFI runtime services. However, even with this option, the
1506 resultant kernel should continue to boot on existing non-EFI
1507 platforms.
1509 config EFI_STUB
1510 bool "EFI stub support"
1511 depends on EFI
1512 ---help---
1513 This kernel feature allows a bzImage to be loaded directly
1514 by EFI firmware without the use of a bootloader.
1516 config SECCOMP
1517 def_bool y
1518 prompt "Enable seccomp to safely compute untrusted bytecode"
1519 ---help---
1520 This kernel feature is useful for number crunching applications
1521 that may need to compute untrusted bytecode during their
1522 execution. By using pipes or other transports made available to
1523 the process as file descriptors supporting the read/write
1524 syscalls, it's possible to isolate those applications in
1525 their own address space using seccomp. Once seccomp is
1526 enabled via prctl(PR_SET_SECCOMP), it cannot be disabled
1527 and the task is only allowed to execute a few safe syscalls
1528 defined by each seccomp mode.
1530 If unsure, say Y. Only embedded should say N here.
1532 config CC_STACKPROTECTOR
1533 bool "Enable -fstack-protector buffer overflow detection (EXPERIMENTAL)"
1534 ---help---
1535 This option turns on the -fstack-protector GCC feature. This
1536 feature puts, at the beginning of functions, a canary value on
1537 the stack just before the return address, and validates
1538 the value just before actually returning. Stack based buffer
1539 overflows (that need to overwrite this return address) now also
1540 overwrite the canary, which gets detected and the attack is then
1541 neutralized via a kernel panic.
1543 This feature requires gcc version 4.2 or above, or a distribution
1544 gcc with the feature backported. Older versions are automatically
1545 detected and for those versions, this configuration option is
1546 ignored. (and a warning is printed during bootup)
1548 source kernel/Kconfig.hz
1550 config KEXEC
1551 bool "kexec system call"
1552 ---help---
1553 kexec is a system call that implements the ability to shutdown your
1554 current kernel, and to start another kernel. It is like a reboot
1555 but it is independent of the system firmware. And like a reboot
1556 you can start any kernel with it, not just Linux.
1558 The name comes from the similarity to the exec system call.
1560 It is an ongoing process to be certain the hardware in a machine
1561 is properly shutdown, so do not be surprised if this code does not
1562 initially work for you. It may help to enable device hotplugging
1563 support. As of this writing the exact hardware interface is
1564 strongly in flux, so no good recommendation can be made.
1566 config CRASH_DUMP
1567 bool "kernel crash dumps"
1568 depends on X86_64 || (X86_32 && HIGHMEM)
1569 ---help---
1570 Generate crash dump after being started by kexec.
1571 This should be normally only set in special crash dump kernels
1572 which are loaded in the main kernel with kexec-tools into
1573 a specially reserved region and then later executed after
1574 a crash by kdump/kexec. The crash dump kernel must be compiled
1575 to a memory address not used by the main kernel or BIOS using
1576 PHYSICAL_START, or it must be built as a relocatable image
1577 (CONFIG_RELOCATABLE=y).
1578 For more details see Documentation/kdump/kdump.txt
1580 config KEXEC_JUMP
1581 bool "kexec jump (EXPERIMENTAL)"
1582 depends on EXPERIMENTAL
1583 depends on KEXEC && HIBERNATION
1584 ---help---
1585 Jump between original kernel and kexeced kernel and invoke
1586 code in physical address mode via KEXEC
1588 config PHYSICAL_START
1589 hex "Physical address where the kernel is loaded" if (EXPERT || CRASH_DUMP)
1590 default "0x1000000"
1591 ---help---
1592 This gives the physical address where the kernel is loaded.
1594 If kernel is a not relocatable (CONFIG_RELOCATABLE=n) then
1595 bzImage will decompress itself to above physical address and
1596 run from there. Otherwise, bzImage will run from the address where
1597 it has been loaded by the boot loader and will ignore above physical
1598 address.
1600 In normal kdump cases one does not have to set/change this option
1601 as now bzImage can be compiled as a completely relocatable image
1602 (CONFIG_RELOCATABLE=y) and be used to load and run from a different
1603 address. This option is mainly useful for the folks who don't want
1604 to use a bzImage for capturing the crash dump and want to use a
1605 vmlinux instead. vmlinux is not relocatable hence a kernel needs
1606 to be specifically compiled to run from a specific memory area
1607 (normally a reserved region) and this option comes handy.
1609 So if you are using bzImage for capturing the crash dump,
1610 leave the value here unchanged to 0x1000000 and set
1611 CONFIG_RELOCATABLE=y. Otherwise if you plan to use vmlinux
1612 for capturing the crash dump change this value to start of
1613 the reserved region. In other words, it can be set based on
1614 the "X" value as specified in the "crashkernel=YM@XM"
1615 command line boot parameter passed to the panic-ed
1616 kernel. Please take a look at Documentation/kdump/kdump.txt
1617 for more details about crash dumps.
1619 Usage of bzImage for capturing the crash dump is recommended as
1620 one does not have to build two kernels. Same kernel can be used
1621 as production kernel and capture kernel. Above option should have
1622 gone away after relocatable bzImage support is introduced. But it
1623 is present because there are users out there who continue to use
1624 vmlinux for dump capture. This option should go away down the
1625 line.
1627 Don't change this unless you know what you are doing.
1629 config RELOCATABLE
1630 bool "Build a relocatable kernel"
1631 default y
1632 ---help---
1633 This builds a kernel image that retains relocation information
1634 so it can be loaded someplace besides the default 1MB.
1635 The relocations tend to make the kernel binary about 10% larger,
1636 but are discarded at runtime.
1638 One use is for the kexec on panic case where the recovery kernel
1639 must live at a different physical address than the primary
1640 kernel.
1642 Note: If CONFIG_RELOCATABLE=y, then the kernel runs from the address
1643 it has been loaded at and the compile time physical address
1644 (CONFIG_PHYSICAL_START) is ignored.
1646 # Relocation on x86-32 needs some additional build support
1647 config X86_NEED_RELOCS
1648 def_bool y
1649 depends on X86_32 && RELOCATABLE
1651 config PHYSICAL_ALIGN
1652 hex "Alignment value to which kernel should be aligned" if X86_32
1653 default "0x1000000"
1654 range 0x2000 0x1000000
1655 ---help---
1656 This value puts the alignment restrictions on physical address
1657 where kernel is loaded and run from. Kernel is compiled for an
1658 address which meets above alignment restriction.
1660 If bootloader loads the kernel at a non-aligned address and
1661 CONFIG_RELOCATABLE is set, kernel will move itself to nearest
1662 address aligned to above value and run from there.
1664 If bootloader loads the kernel at a non-aligned address and
1665 CONFIG_RELOCATABLE is not set, kernel will ignore the run time
1666 load address and decompress itself to the address it has been
1667 compiled for and run from there. The address for which kernel is
1668 compiled already meets above alignment restrictions. Hence the
1669 end result is that kernel runs from a physical address meeting
1670 above alignment restrictions.
1672 Don't change this unless you know what you are doing.
1674 config HOTPLUG_CPU
1675 bool "Support for hot-pluggable CPUs"
1676 depends on SMP && HOTPLUG
1677 ---help---
1678 Say Y here to allow turning CPUs off and on. CPUs can be
1679 controlled through /sys/devices/system/cpu.
1680 ( Note: power management support will enable this option
1681 automatically on SMP systems. )
1682 Say N if you want to disable CPU hotplug.
1684 config COMPAT_VDSO
1685 def_bool y
1686 prompt "Compat VDSO support"
1687 depends on X86_32 || IA32_EMULATION
1688 ---help---
1689 Map the 32-bit VDSO to the predictable old-style address too.
1691 Say N here if you are running a sufficiently recent glibc
1692 version (2.3.3 or later), to remove the high-mapped
1693 VDSO mapping and to exclusively use the randomized VDSO.
1695 If unsure, say Y.
1697 config CMDLINE_BOOL
1698 bool "Built-in kernel command line"
1699 ---help---
1700 Allow for specifying boot arguments to the kernel at
1701 build time. On some systems (e.g. embedded ones), it is
1702 necessary or convenient to provide some or all of the
1703 kernel boot arguments with the kernel itself (that is,
1704 to not rely on the boot loader to provide them.)
1706 To compile command line arguments into the kernel,
1707 set this option to 'Y', then fill in the
1708 the boot arguments in CONFIG_CMDLINE.
1710 Systems with fully functional boot loaders (i.e. non-embedded)
1711 should leave this option set to 'N'.
1713 config CMDLINE
1714 string "Built-in kernel command string"
1715 depends on CMDLINE_BOOL
1716 default ""
1717 ---help---
1718 Enter arguments here that should be compiled into the kernel
1719 image and used at boot time. If the boot loader provides a
1720 command line at boot time, it is appended to this string to
1721 form the full kernel command line, when the system boots.
1723 However, you can use the CONFIG_CMDLINE_OVERRIDE option to
1724 change this behavior.
1726 In most cases, the command line (whether built-in or provided
1727 by the boot loader) should specify the device for the root
1728 file system.
1730 config CMDLINE_OVERRIDE
1731 bool "Built-in command line overrides boot loader arguments"
1732 depends on CMDLINE_BOOL
1733 ---help---
1734 Set this option to 'Y' to have the kernel ignore the boot loader
1735 command line, and use ONLY the built-in command line.
1737 This is used to work around broken boot loaders. This should
1738 be set to 'N' under normal conditions.
1740 endmenu
1742 config ARCH_ENABLE_MEMORY_HOTPLUG
1743 def_bool y
1744 depends on X86_64 || (X86_32 && HIGHMEM)
1746 config ARCH_ENABLE_MEMORY_HOTREMOVE
1747 def_bool y
1748 depends on MEMORY_HOTPLUG
1750 config USE_PERCPU_NUMA_NODE_ID
1751 def_bool y
1752 depends on NUMA
1754 menu "Power management and ACPI options"
1756 config ARCH_HIBERNATION_HEADER
1757 def_bool y
1758 depends on X86_64 && HIBERNATION
1760 source "kernel/power/Kconfig"
1762 source "drivers/acpi/Kconfig"
1764 source "drivers/sfi/Kconfig"
1766 config X86_APM_BOOT
1767 def_bool y
1768 depends on APM
1770 menuconfig APM
1771 tristate "APM (Advanced Power Management) BIOS support"
1772 depends on X86_32 && PM_SLEEP
1773 ---help---
1774 APM is a BIOS specification for saving power using several different
1775 techniques. This is mostly useful for battery powered laptops with
1776 APM compliant BIOSes. If you say Y here, the system time will be
1777 reset after a RESUME operation, the /proc/apm device will provide
1778 battery status information, and user-space programs will receive
1779 notification of APM "events" (e.g. battery status change).
1781 If you select "Y" here, you can disable actual use of the APM
1782 BIOS by passing the "apm=off" option to the kernel at boot time.
1784 Note that the APM support is almost completely disabled for
1785 machines with more than one CPU.
1787 In order to use APM, you will need supporting software. For location
1788 and more information, read <file:Documentation/power/apm-acpi.txt>
1789 and the Battery Powered Linux mini-HOWTO, available from
1790 <http://www.tldp.org/docs.html#howto>.
1792 This driver does not spin down disk drives (see the hdparm(8)
1793 manpage ("man 8 hdparm") for that), and it doesn't turn off
1794 VESA-compliant "green" monitors.
1796 This driver does not support the TI 4000M TravelMate and the ACER
1797 486/DX4/75 because they don't have compliant BIOSes. Many "green"
1798 desktop machines also don't have compliant BIOSes, and this driver
1799 may cause those machines to panic during the boot phase.
1801 Generally, if you don't have a battery in your machine, there isn't
1802 much point in using this driver and you should say N. If you get
1803 random kernel OOPSes or reboots that don't seem to be related to
1804 anything, try disabling/enabling this option (or disabling/enabling
1805 APM in your BIOS).
1807 Some other things you should try when experiencing seemingly random,
1808 "weird" problems:
1810 1) make sure that you have enough swap space and that it is
1811 enabled.
1812 2) pass the "no-hlt" option to the kernel
1813 3) switch on floating point emulation in the kernel and pass
1814 the "no387" option to the kernel
1815 4) pass the "floppy=nodma" option to the kernel
1816 5) pass the "mem=4M" option to the kernel (thereby disabling
1817 all but the first 4 MB of RAM)
1818 6) make sure that the CPU is not over clocked.
1819 7) read the sig11 FAQ at <http://www.bitwizard.nl/sig11/>
1820 8) disable the cache from your BIOS settings
1821 9) install a fan for the video card or exchange video RAM
1822 10) install a better fan for the CPU
1823 11) exchange RAM chips
1824 12) exchange the motherboard.
1826 To compile this driver as a module, choose M here: the
1827 module will be called apm.
1829 if APM
1831 config APM_IGNORE_USER_SUSPEND
1832 bool "Ignore USER SUSPEND"
1833 ---help---
1834 This option will ignore USER SUSPEND requests. On machines with a
1835 compliant APM BIOS, you want to say N. However, on the NEC Versa M
1836 series notebooks, it is necessary to say Y because of a BIOS bug.
1838 config APM_DO_ENABLE
1839 bool "Enable PM at boot time"
1840 ---help---
1841 Enable APM features at boot time. From page 36 of the APM BIOS
1842 specification: "When disabled, the APM BIOS does not automatically
1843 power manage devices, enter the Standby State, enter the Suspend
1844 State, or take power saving steps in response to CPU Idle calls."
1845 This driver will make CPU Idle calls when Linux is idle (unless this
1846 feature is turned off -- see "Do CPU IDLE calls", below). This
1847 should always save battery power, but more complicated APM features
1848 will be dependent on your BIOS implementation. You may need to turn
1849 this option off if your computer hangs at boot time when using APM
1850 support, or if it beeps continuously instead of suspending. Turn
1851 this off if you have a NEC UltraLite Versa 33/C or a Toshiba
1852 T400CDT. This is off by default since most machines do fine without
1853 this feature.
1855 config APM_CPU_IDLE
1856 bool "Make CPU Idle calls when idle"
1857 ---help---
1858 Enable calls to APM CPU Idle/CPU Busy inside the kernel's idle loop.
1859 On some machines, this can activate improved power savings, such as
1860 a slowed CPU clock rate, when the machine is idle. These idle calls
1861 are made after the idle loop has run for some length of time (e.g.,
1862 333 mS). On some machines, this will cause a hang at boot time or
1863 whenever the CPU becomes idle. (On machines with more than one CPU,
1864 this option does nothing.)
1866 config APM_DISPLAY_BLANK
1867 bool "Enable console blanking using APM"
1868 ---help---
1869 Enable console blanking using the APM. Some laptops can use this to
1870 turn off the LCD backlight when the screen blanker of the Linux
1871 virtual console blanks the screen. Note that this is only used by
1872 the virtual console screen blanker, and won't turn off the backlight
1873 when using the X Window system. This also doesn't have anything to
1874 do with your VESA-compliant power-saving monitor. Further, this
1875 option doesn't work for all laptops -- it might not turn off your
1876 backlight at all, or it might print a lot of errors to the console,
1877 especially if you are using gpm.
1879 config APM_ALLOW_INTS
1880 bool "Allow interrupts during APM BIOS calls"
1881 ---help---
1882 Normally we disable external interrupts while we are making calls to
1883 the APM BIOS as a measure to lessen the effects of a badly behaving
1884 BIOS implementation. The BIOS should reenable interrupts if it
1885 needs to. Unfortunately, some BIOSes do not -- especially those in
1886 many of the newer IBM Thinkpads. If you experience hangs when you
1887 suspend, try setting this to Y. Otherwise, say N.
1889 endif # APM
1891 source "drivers/cpufreq/Kconfig"
1893 source "drivers/cpuidle/Kconfig"
1895 source "drivers/idle/Kconfig"
1897 endmenu
1900 menu "Bus options (PCI etc.)"
1902 config PCI
1903 bool "PCI support"
1904 default y
1905 select ARCH_SUPPORTS_MSI if (X86_LOCAL_APIC && X86_IO_APIC)
1906 ---help---
1907 Find out whether you have a PCI motherboard. PCI is the name of a
1908 bus system, i.e. the way the CPU talks to the other stuff inside
1909 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
1910 VESA. If you have PCI, say Y, otherwise N.
1912 choice
1913 prompt "PCI access mode"
1914 depends on X86_32 && PCI
1915 default PCI_GOANY
1916 ---help---
1917 On PCI systems, the BIOS can be used to detect the PCI devices and
1918 determine their configuration. However, some old PCI motherboards
1919 have BIOS bugs and may crash if this is done. Also, some embedded
1920 PCI-based systems don't have any BIOS at all. Linux can also try to
1921 detect the PCI hardware directly without using the BIOS.
1923 With this option, you can specify how Linux should detect the
1924 PCI devices. If you choose "BIOS", the BIOS will be used,
1925 if you choose "Direct", the BIOS won't be used, and if you
1926 choose "MMConfig", then PCI Express MMCONFIG will be used.
1927 If you choose "Any", the kernel will try MMCONFIG, then the
1928 direct access method and falls back to the BIOS if that doesn't
1929 work. If unsure, go with the default, which is "Any".
1931 config PCI_GOBIOS
1932 bool "BIOS"
1934 config PCI_GOMMCONFIG
1935 bool "MMConfig"
1937 config PCI_GODIRECT
1938 bool "Direct"
1940 config PCI_GOOLPC
1941 bool "OLPC XO-1"
1942 depends on OLPC
1944 config PCI_GOANY
1945 bool "Any"
1947 endchoice
1949 config PCI_BIOS
1950 def_bool y
1951 depends on X86_32 && PCI && (PCI_GOBIOS || PCI_GOANY)
1953 # x86-64 doesn't support PCI BIOS access from long mode so always go direct.
1954 config PCI_DIRECT
1955 def_bool y
1956 depends on PCI && (X86_64 || (PCI_GODIRECT || PCI_GOANY || PCI_GOOLPC || PCI_GOMMCONFIG))
1958 config PCI_MMCONFIG
1959 def_bool y
1960 depends on X86_32 && PCI && (ACPI || SFI) && (PCI_GOMMCONFIG || PCI_GOANY)
1962 config PCI_OLPC
1963 def_bool y
1964 depends on PCI && OLPC && (PCI_GOOLPC || PCI_GOANY)
1966 config PCI_XEN
1967 def_bool y
1968 depends on PCI && XEN
1969 select SWIOTLB_XEN
1971 config PCI_DOMAINS
1972 def_bool y
1973 depends on PCI
1975 config PCI_MMCONFIG
1976 bool "Support mmconfig PCI config space access"
1977 depends on X86_64 && PCI && ACPI
1979 config PCI_CNB20LE_QUIRK
1980 bool "Read CNB20LE Host Bridge Windows" if EXPERT
1981 default n
1982 depends on PCI && EXPERIMENTAL
1983 help
1984 Read the PCI windows out of the CNB20LE host bridge. This allows
1985 PCI hotplug to work on systems with the CNB20LE chipset which do
1986 not have ACPI.
1988 There's no public spec for this chipset, and this functionality
1989 is known to be incomplete.
1991 You should say N unless you know you need this.
1993 source "drivers/pci/pcie/Kconfig"
1995 source "drivers/pci/Kconfig"
1997 # x86_64 have no ISA slots, but can have ISA-style DMA.
1998 config ISA_DMA_API
1999 bool "ISA-style DMA support" if (X86_64 && EXPERT)
2000 default y
2001 help
2002 Enables ISA-style DMA support for devices requiring such controllers.
2003 If unsure, say Y.
2005 if X86_32
2007 config ISA
2008 bool "ISA support"
2009 ---help---
2010 Find out whether you have ISA slots on your motherboard. ISA is the
2011 name of a bus system, i.e. the way the CPU talks to the other stuff
2012 inside your box. Other bus systems are PCI, EISA, MicroChannel
2013 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
2014 newer boards don't support it. If you have ISA, say Y, otherwise N.
2016 config EISA
2017 bool "EISA support"
2018 depends on ISA
2019 ---help---
2020 The Extended Industry Standard Architecture (EISA) bus was
2021 developed as an open alternative to the IBM MicroChannel bus.
2023 The EISA bus provided some of the features of the IBM MicroChannel
2024 bus while maintaining backward compatibility with cards made for
2025 the older ISA bus. The EISA bus saw limited use between 1988 and
2026 1995 when it was made obsolete by the PCI bus.
2028 Say Y here if you are building a kernel for an EISA-based machine.
2030 Otherwise, say N.
2032 source "drivers/eisa/Kconfig"
2034 config MCA
2035 bool "MCA support"
2036 ---help---
2037 MicroChannel Architecture is found in some IBM PS/2 machines and
2038 laptops. It is a bus system similar to PCI or ISA. See
2039 <file:Documentation/mca.txt> (and especially the web page given
2040 there) before attempting to build an MCA bus kernel.
2042 source "drivers/mca/Kconfig"
2044 config SCx200
2045 tristate "NatSemi SCx200 support"
2046 ---help---
2047 This provides basic support for National Semiconductor's
2048 (now AMD's) Geode processors. The driver probes for the
2049 PCI-IDs of several on-chip devices, so its a good dependency
2050 for other scx200_* drivers.
2052 If compiled as a module, the driver is named scx200.
2054 config SCx200HR_TIMER
2055 tristate "NatSemi SCx200 27MHz High-Resolution Timer Support"
2056 depends on SCx200
2057 default y
2058 ---help---
2059 This driver provides a clocksource built upon the on-chip
2060 27MHz high-resolution timer. Its also a workaround for
2061 NSC Geode SC-1100's buggy TSC, which loses time when the
2062 processor goes idle (as is done by the scheduler). The
2063 other workaround is idle=poll boot option.
2065 config OLPC
2066 bool "One Laptop Per Child support"
2067 depends on !X86_PAE
2068 select GPIOLIB
2069 select OF
2070 select OF_PROMTREE
2071 ---help---
2072 Add support for detecting the unique features of the OLPC
2073 XO hardware.
2075 config OLPC_XO1_PM
2076 bool "OLPC XO-1 Power Management"
2077 depends on OLPC && MFD_CS5535 && PM_SLEEP
2078 select MFD_CORE
2079 ---help---
2080 Add support for poweroff and suspend of the OLPC XO-1 laptop.
2082 config OLPC_XO1_RTC
2083 bool "OLPC XO-1 Real Time Clock"
2084 depends on OLPC_XO1_PM && RTC_DRV_CMOS
2085 ---help---
2086 Add support for the XO-1 real time clock, which can be used as a
2087 programmable wakeup source.
2089 config OLPC_XO1_SCI
2090 bool "OLPC XO-1 SCI extras"
2091 depends on OLPC && OLPC_XO1_PM
2092 select POWER_SUPPLY
2093 select GPIO_CS5535
2094 select MFD_CORE
2095 ---help---
2096 Add support for SCI-based features of the OLPC XO-1 laptop:
2097 - EC-driven system wakeups
2098 - Power button
2099 - Ebook switch
2100 - Lid switch
2101 - AC adapter status updates
2102 - Battery status updates
2104 config OLPC_XO15_SCI
2105 bool "OLPC XO-1.5 SCI extras"
2106 depends on OLPC && ACPI
2107 select POWER_SUPPLY
2108 ---help---
2109 Add support for SCI-based features of the OLPC XO-1.5 laptop:
2110 - EC-driven system wakeups
2111 - AC adapter status updates
2112 - Battery status updates
2114 config ALIX
2115 bool "PCEngines ALIX System Support (LED setup)"
2116 select GPIOLIB
2117 ---help---
2118 This option enables system support for the PCEngines ALIX.
2119 At present this just sets up LEDs for GPIO control on
2120 ALIX2/3/6 boards. However, other system specific setup should
2121 get added here.
2123 Note: You must still enable the drivers for GPIO and LED support
2124 (GPIO_CS5535 & LEDS_GPIO) to actually use the LEDs
2126 Note: You have to set alix.force=1 for boards with Award BIOS.
2128 endif # X86_32
2130 config AMD_NB
2131 def_bool y
2132 depends on CPU_SUP_AMD && PCI
2134 source "drivers/pcmcia/Kconfig"
2136 source "drivers/pci/hotplug/Kconfig"
2138 config RAPIDIO
2139 bool "RapidIO support"
2140 depends on PCI
2141 default n
2142 help
2143 If you say Y here, the kernel will include drivers and
2144 infrastructure code to support RapidIO interconnect devices.
2146 source "drivers/rapidio/Kconfig"
2148 endmenu
2151 menu "Executable file formats / Emulations"
2153 source "fs/Kconfig.binfmt"
2155 config IA32_EMULATION
2156 bool "IA32 Emulation"
2157 depends on X86_64
2158 select COMPAT_BINFMT_ELF
2159 ---help---
2160 Include code to run 32-bit programs under a 64-bit kernel. You should
2161 likely turn this on, unless you're 100% sure that you don't have any
2162 32-bit programs left.
2164 config IA32_AOUT
2165 tristate "IA32 a.out support"
2166 depends on IA32_EMULATION
2167 ---help---
2168 Support old a.out binaries in the 32bit emulation.
2170 config COMPAT
2171 def_bool y
2172 depends on IA32_EMULATION
2174 config COMPAT_FOR_U64_ALIGNMENT
2175 def_bool COMPAT
2176 depends on X86_64
2178 config SYSVIPC_COMPAT
2179 def_bool y
2180 depends on COMPAT && SYSVIPC
2182 config KEYS_COMPAT
2183 bool
2184 depends on COMPAT && KEYS
2185 default y
2187 endmenu
2190 config HAVE_ATOMIC_IOMAP
2191 def_bool y
2192 depends on X86_32
2194 config HAVE_TEXT_POKE_SMP
2195 bool
2196 select STOP_MACHINE if SMP
2198 source "net/Kconfig"
2200 source "drivers/Kconfig"
2202 source "drivers/firmware/Kconfig"
2204 source "fs/Kconfig"
2206 source "arch/x86/Kconfig.debug"
2208 source "security/Kconfig"
2210 source "crypto/Kconfig"
2212 source "arch/x86/kvm/Kconfig"
2214 source "lib/Kconfig"