| blob | 6339aa496c4f9c09fcd650ff541ad586fae65c6f |
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 ARCH_HAS_CPU_AUTOPROBE
183 def_bool y
185 config HAVE_SETUP_PER_CPU_AREA
186 def_bool y
188 config NEED_PER_CPU_EMBED_FIRST_CHUNK
189 def_bool y
191 config NEED_PER_CPU_PAGE_FIRST_CHUNK
192 def_bool y
194 config ARCH_HIBERNATION_POSSIBLE
195 def_bool y
197 config ARCH_SUSPEND_POSSIBLE
198 def_bool y
200 config ZONE_DMA32
201 bool
202 default X86_64
204 config AUDIT_ARCH
205 bool
206 default X86_64
208 config ARCH_SUPPORTS_OPTIMIZED_INLINING
209 def_bool y
211 config ARCH_SUPPORTS_DEBUG_PAGEALLOC
212 def_bool y
214 config HAVE_INTEL_TXT
215 def_bool y
216 depends on EXPERIMENTAL && INTEL_IOMMU && ACPI
218 config X86_32_SMP
219 def_bool y
220 depends on X86_32 && SMP
222 config X86_64_SMP
223 def_bool y
224 depends on X86_64 && SMP
226 config X86_HT
227 def_bool y
228 depends on SMP
230 config X86_32_LAZY_GS
231 def_bool y
232 depends on X86_32 && !CC_STACKPROTECTOR
234 config ARCH_HWEIGHT_CFLAGS
235 string
236 default "-fcall-saved-ecx -fcall-saved-edx" if X86_32
237 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
239 config KTIME_SCALAR
240 def_bool X86_32
242 config ARCH_CPU_PROBE_RELEASE
243 def_bool y
244 depends on HOTPLUG_CPU
246 source "init/Kconfig"
247 source "kernel/Kconfig.freezer"
249 menu "Processor type and features"
251 config ZONE_DMA
252 bool "DMA memory allocation support" if EXPERT
253 default y
254 help
255 DMA memory allocation support allows devices with less than 32-bit
256 addressing to allocate within the first 16MB of address space.
257 Disable if no such devices will be used.
259 If unsure, say Y.
261 source "kernel/time/Kconfig"
263 config SMP
264 bool "Symmetric multi-processing support"
265 ---help---
266 This enables support for systems with more than one CPU. If you have
267 a system with only one CPU, like most personal computers, say N. If
268 you have a system with more than one CPU, say Y.
270 If you say N here, the kernel will run on single and multiprocessor
271 machines, but will use only one CPU of a multiprocessor machine. If
272 you say Y here, the kernel will run on many, but not all,
273 singleprocessor machines. On a singleprocessor machine, the kernel
274 will run faster if you say N here.
276 Note that if you say Y here and choose architecture "586" or
277 "Pentium" under "Processor family", the kernel will not work on 486
278 architectures. Similarly, multiprocessor kernels for the "PPro"
279 architecture may not work on all Pentium based boards.
281 People using multiprocessor machines who say Y here should also say
282 Y to "Enhanced Real Time Clock Support", below. The "Advanced Power
283 Management" code will be disabled if you say Y here.
285 See also <file:Documentation/x86/i386/IO-APIC.txt>,
286 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
287 <http://www.tldp.org/docs.html#howto>.
289 If you don't know what to do here, say N.
291 config X86_X2APIC
292 bool "Support x2apic"
293 depends on X86_LOCAL_APIC && X86_64 && IRQ_REMAP
294 ---help---
295 This enables x2apic support on CPUs that have this feature.
297 This allows 32-bit apic IDs (so it can support very large systems),
298 and accesses the local apic via MSRs not via mmio.
300 If you don't know what to do here, say N.
302 config X86_MPPARSE
303 bool "Enable MPS table" if ACPI
304 default y
305 depends on X86_LOCAL_APIC
306 ---help---
307 For old smp systems that do not have proper acpi support. Newer systems
308 (esp with 64bit cpus) with acpi support, MADT and DSDT will override it
310 config X86_BIGSMP
311 bool "Support for big SMP systems with more than 8 CPUs"
312 depends on X86_32 && SMP
313 ---help---
314 This option is needed for the systems that have more than 8 CPUs
316 if X86_32
317 config X86_EXTENDED_PLATFORM
318 bool "Support for extended (non-PC) x86 platforms"
319 default y
320 ---help---
321 If you disable this option then the kernel will only support
322 standard PC platforms. (which covers the vast majority of
323 systems out there.)
325 If you enable this option then you'll be able to select support
326 for the following (non-PC) 32 bit x86 platforms:
327 AMD Elan
328 NUMAQ (IBM/Sequent)
329 RDC R-321x SoC
330 SGI 320/540 (Visual Workstation)
331 Summit/EXA (IBM x440)
332 Unisys ES7000 IA32 series
333 Moorestown MID devices
335 If you have one of these systems, or if you want to build a
336 generic distribution kernel, say Y here - otherwise say N.
337 endif
339 if X86_64
340 config X86_EXTENDED_PLATFORM
341 bool "Support for extended (non-PC) x86 platforms"
342 default y
343 ---help---
344 If you disable this option then the kernel will only support
345 standard PC platforms. (which covers the vast majority of
346 systems out there.)
348 If you enable this option then you'll be able to select support
349 for the following (non-PC) 64 bit x86 platforms:
350 Numascale NumaChip
351 ScaleMP vSMP
352 SGI Ultraviolet
354 If you have one of these systems, or if you want to build a
355 generic distribution kernel, say Y here - otherwise say N.
356 endif
357 # This is an alphabetically sorted list of 64 bit extended platforms
358 # Please maintain the alphabetic order if and when there are additions
359 config X86_NUMACHIP
360 bool "Numascale NumaChip"
361 depends on X86_64
362 depends on X86_EXTENDED_PLATFORM
363 depends on NUMA
364 depends on SMP
365 depends on X86_X2APIC
366 ---help---
367 Adds support for Numascale NumaChip large-SMP systems. Needed to
368 enable more than ~168 cores.
369 If you don't have one of these, you should say N here.
371 config X86_VSMP
372 bool "ScaleMP vSMP"
373 select PARAVIRT_GUEST
374 select PARAVIRT
375 depends on X86_64 && PCI
376 depends on X86_EXTENDED_PLATFORM
377 ---help---
378 Support for ScaleMP vSMP systems. Say 'Y' here if this kernel is
379 supposed to run on these EM64T-based machines. Only choose this option
380 if you have one of these machines.
382 config X86_UV
383 bool "SGI Ultraviolet"
384 depends on X86_64
385 depends on X86_EXTENDED_PLATFORM
386 depends on NUMA
387 depends on X86_X2APIC
388 ---help---
389 This option is needed in order to support SGI Ultraviolet systems.
390 If you don't have one of these, you should say N here.
392 # Following is an alphabetically sorted list of 32 bit extended platforms
393 # Please maintain the alphabetic order if and when there are additions
395 config X86_INTEL_CE
396 bool "CE4100 TV platform"
397 depends on PCI
398 depends on PCI_GODIRECT
399 depends on X86_32
400 depends on X86_EXTENDED_PLATFORM
401 select X86_REBOOTFIXUPS
402 select OF
403 select OF_EARLY_FLATTREE
404 ---help---
405 Select for the Intel CE media processor (CE4100) SOC.
406 This option compiles in support for the CE4100 SOC for settop
407 boxes and media devices.
409 config X86_WANT_INTEL_MID
410 bool "Intel MID platform support"
411 depends on X86_32
412 depends on X86_EXTENDED_PLATFORM
413 ---help---
414 Select to build a kernel capable of supporting Intel MID platform
415 systems which do not have the PCI legacy interfaces (Moorestown,
416 Medfield). If you are building for a PC class system say N here.
418 if X86_WANT_INTEL_MID
420 config X86_INTEL_MID
421 bool
423 config X86_MRST
424 bool "Moorestown MID platform"
425 depends on PCI
426 depends on PCI_GOANY
427 depends on X86_IO_APIC
428 select X86_INTEL_MID
429 select SFI
430 select DW_APB_TIMER
431 select APB_TIMER
432 select I2C
433 select SPI
434 select INTEL_SCU_IPC
435 select X86_PLATFORM_DEVICES
436 ---help---
437 Moorestown is Intel's Low Power Intel Architecture (LPIA) based Moblin
438 Internet Device(MID) platform. Moorestown consists of two chips:
439 Lincroft (CPU core, graphics, and memory controller) and Langwell IOH.
440 Unlike standard x86 PCs, Moorestown does not have many legacy devices
441 nor standard legacy replacement devices/features. e.g. Moorestown does
442 not contain i8259, i8254, HPET, legacy BIOS, most of the io ports.
444 config X86_MDFLD
445 bool "Medfield MID platform"
446 depends on PCI
447 depends on PCI_GOANY
448 depends on X86_IO_APIC
449 select X86_INTEL_MID
450 select SFI
451 select DW_APB_TIMER
452 select APB_TIMER
453 select I2C
454 select SPI
455 select INTEL_SCU_IPC
456 select X86_PLATFORM_DEVICES
457 ---help---
458 Medfield is Intel's Low Power Intel Architecture (LPIA) based Moblin
459 Internet Device(MID) platform.
460 Unlike standard x86 PCs, Medfield does not have many legacy devices
461 nor standard legacy replacement devices/features. e.g. Medfield does
462 not contain i8259, i8254, HPET, legacy BIOS, most of the io ports.
464 endif
466 config X86_RDC321X
467 bool "RDC R-321x SoC"
468 depends on X86_32
469 depends on X86_EXTENDED_PLATFORM
470 select M486
471 select X86_REBOOTFIXUPS
472 ---help---
473 This option is needed for RDC R-321x system-on-chip, also known
474 as R-8610-(G).
475 If you don't have one of these chips, you should say N here.
477 config X86_32_NON_STANDARD
478 bool "Support non-standard 32-bit SMP architectures"
479 depends on X86_32 && SMP
480 depends on X86_EXTENDED_PLATFORM
481 ---help---
482 This option compiles in the NUMAQ, Summit, bigsmp, ES7000, default
483 subarchitectures. It is intended for a generic binary kernel.
484 if you select them all, kernel will probe it one by one. and will
485 fallback to default.
487 # Alphabetically sorted list of Non standard 32 bit platforms
489 config X86_NUMAQ
490 bool "NUMAQ (IBM/Sequent)"
491 depends on X86_32_NON_STANDARD
492 depends on PCI
493 select NUMA
494 select X86_MPPARSE
495 ---help---
496 This option is used for getting Linux to run on a NUMAQ (IBM/Sequent)
497 NUMA multiquad box. This changes the way that processors are
498 bootstrapped, and uses Clustered Logical APIC addressing mode instead
499 of Flat Logical. You will need a new lynxer.elf file to flash your
500 firmware with - send email to <Martin.Bligh@us.ibm.com>.
502 config X86_SUPPORTS_MEMORY_FAILURE
503 def_bool y
504 # MCE code calls memory_failure():
505 depends on X86_MCE
506 # On 32-bit this adds too big of NODES_SHIFT and we run out of page flags:
507 depends on !X86_NUMAQ
508 # On 32-bit SPARSEMEM adds too big of SECTIONS_WIDTH:
509 depends on X86_64 || !SPARSEMEM
510 select ARCH_SUPPORTS_MEMORY_FAILURE
512 config X86_VISWS
513 bool "SGI 320/540 (Visual Workstation)"
514 depends on X86_32 && PCI && X86_MPPARSE && PCI_GODIRECT
515 depends on X86_32_NON_STANDARD
516 ---help---
517 The SGI Visual Workstation series is an IA32-based workstation
518 based on SGI systems chips with some legacy PC hardware attached.
520 Say Y here to create a kernel to run on the SGI 320 or 540.
522 A kernel compiled for the Visual Workstation will run on general
523 PCs as well. See <file:Documentation/sgi-visws.txt> for details.
525 config X86_SUMMIT
526 bool "Summit/EXA (IBM x440)"
527 depends on X86_32_NON_STANDARD
528 ---help---
529 This option is needed for IBM systems that use the Summit/EXA chipset.
530 In particular, it is needed for the x440.
532 config X86_ES7000
533 bool "Unisys ES7000 IA32 series"
534 depends on X86_32_NON_STANDARD && X86_BIGSMP
535 ---help---
536 Support for Unisys ES7000 systems. Say 'Y' here if this kernel is
537 supposed to run on an IA32-based Unisys ES7000 system.
539 config X86_32_IRIS
540 tristate "Eurobraille/Iris poweroff module"
541 depends on X86_32
542 ---help---
543 The Iris machines from EuroBraille do not have APM or ACPI support
544 to shut themselves down properly. A special I/O sequence is
545 needed to do so, which is what this module does at
546 kernel shutdown.
548 This is only for Iris machines from EuroBraille.
550 If unused, say N.
552 config SCHED_OMIT_FRAME_POINTER
553 def_bool y
554 prompt "Single-depth WCHAN output"
555 depends on X86
556 ---help---
557 Calculate simpler /proc/<PID>/wchan values. If this option
558 is disabled then wchan values will recurse back to the
559 caller function. This provides more accurate wchan values,
560 at the expense of slightly more scheduling overhead.
562 If in doubt, say "Y".
564 menuconfig PARAVIRT_GUEST
565 bool "Paravirtualized guest support"
566 ---help---
567 Say Y here to get to see options related to running Linux under
568 various hypervisors. This option alone does not add any kernel code.
570 If you say N, all options in this submenu will be skipped and disabled.
572 if PARAVIRT_GUEST
574 config PARAVIRT_TIME_ACCOUNTING
575 bool "Paravirtual steal time accounting"
576 select PARAVIRT
577 default n
578 ---help---
579 Select this option to enable fine granularity task steal time
580 accounting. Time spent executing other tasks in parallel with
581 the current vCPU is discounted from the vCPU power. To account for
582 that, there can be a small performance impact.
584 If in doubt, say N here.
586 source "arch/x86/xen/Kconfig"
588 config KVM_CLOCK
589 bool "KVM paravirtualized clock"
590 select PARAVIRT
591 select PARAVIRT_CLOCK
592 ---help---
593 Turning on this option will allow you to run a paravirtualized clock
594 when running over the KVM hypervisor. Instead of relying on a PIT
595 (or probably other) emulation by the underlying device model, the host
596 provides the guest with timing infrastructure such as time of day, and
597 system time
599 config KVM_GUEST
600 bool "KVM Guest support"
601 select PARAVIRT
602 ---help---
603 This option enables various optimizations for running under the KVM
604 hypervisor.
606 source "arch/x86/lguest/Kconfig"
608 config PARAVIRT
609 bool "Enable paravirtualization code"
610 ---help---
611 This changes the kernel so it can modify itself when it is run
612 under a hypervisor, potentially improving performance significantly
613 over full virtualization. However, when run without a hypervisor
614 the kernel is theoretically slower and slightly larger.
616 config PARAVIRT_SPINLOCKS
617 bool "Paravirtualization layer for spinlocks"
618 depends on PARAVIRT && SMP && EXPERIMENTAL
619 ---help---
620 Paravirtualized spinlocks allow a pvops backend to replace the
621 spinlock implementation with something virtualization-friendly
622 (for example, block the virtual CPU rather than spinning).
624 Unfortunately the downside is an up to 5% performance hit on
625 native kernels, with various workloads.
627 If you are unsure how to answer this question, answer N.
629 config PARAVIRT_CLOCK
630 bool
632 endif
634 config PARAVIRT_DEBUG
635 bool "paravirt-ops debugging"
636 depends on PARAVIRT && DEBUG_KERNEL
637 ---help---
638 Enable to debug paravirt_ops internals. Specifically, BUG if
639 a paravirt_op is missing when it is called.
641 config NO_BOOTMEM
642 def_bool y
644 config MEMTEST
645 bool "Memtest"
646 ---help---
647 This option adds a kernel parameter 'memtest', which allows memtest
648 to be set.
649 memtest=0, mean disabled; -- default
650 memtest=1, mean do 1 test pattern;
651 ...
652 memtest=4, mean do 4 test patterns.
653 If you are unsure how to answer this question, answer N.
655 config X86_SUMMIT_NUMA
656 def_bool y
657 depends on X86_32 && NUMA && X86_32_NON_STANDARD
659 config X86_CYCLONE_TIMER
660 def_bool y
661 depends on X86_SUMMIT
663 source "arch/x86/Kconfig.cpu"
665 config HPET_TIMER
666 def_bool X86_64
667 prompt "HPET Timer Support" if X86_32
668 ---help---
669 Use the IA-PC HPET (High Precision Event Timer) to manage
670 time in preference to the PIT and RTC, if a HPET is
671 present.
672 HPET is the next generation timer replacing legacy 8254s.
673 The HPET provides a stable time base on SMP
674 systems, unlike the TSC, but it is more expensive to access,
675 as it is off-chip. You can find the HPET spec at
676 <http://www.intel.com/hardwaredesign/hpetspec_1.pdf>.
678 You can safely choose Y here. However, HPET will only be
679 activated if the platform and the BIOS support this feature.
680 Otherwise the 8254 will be used for timing services.
682 Choose N to continue using the legacy 8254 timer.
684 config HPET_EMULATE_RTC
685 def_bool y
686 depends on HPET_TIMER && (RTC=y || RTC=m || RTC_DRV_CMOS=m || RTC_DRV_CMOS=y)
688 config APB_TIMER
689 def_bool y if X86_INTEL_MID
690 prompt "Intel MID APB Timer Support" if X86_INTEL_MID
691 select DW_APB_TIMER
692 depends on X86_INTEL_MID && SFI
693 help
694 APB timer is the replacement for 8254, HPET on X86 MID platforms.
695 The APBT provides a stable time base on SMP
696 systems, unlike the TSC, but it is more expensive to access,
697 as it is off-chip. APB timers are always running regardless of CPU
698 C states, they are used as per CPU clockevent device when possible.
700 # Mark as expert because too many people got it wrong.
701 # The code disables itself when not needed.
702 config DMI
703 default y
704 bool "Enable DMI scanning" if EXPERT
705 ---help---
706 Enabled scanning of DMI to identify machine quirks. Say Y
707 here unless you have verified that your setup is not
708 affected by entries in the DMI blacklist. Required by PNP
709 BIOS code.
711 config GART_IOMMU
712 bool "GART IOMMU support" if EXPERT
713 default y
714 select SWIOTLB
715 depends on X86_64 && PCI && AMD_NB
716 ---help---
717 Support for full DMA access of devices with 32bit memory access only
718 on systems with more than 3GB. This is usually needed for USB,
719 sound, many IDE/SATA chipsets and some other devices.
720 Provides a driver for the AMD Athlon64/Opteron/Turion/Sempron GART
721 based hardware IOMMU and a software bounce buffer based IOMMU used
722 on Intel systems and as fallback.
723 The code is only active when needed (enough memory and limited
724 device) unless CONFIG_IOMMU_DEBUG or iommu=force is specified
725 too.
727 config CALGARY_IOMMU
728 bool "IBM Calgary IOMMU support"
729 select SWIOTLB
730 depends on X86_64 && PCI && EXPERIMENTAL
731 ---help---
732 Support for hardware IOMMUs in IBM's xSeries x366 and x460
733 systems. Needed to run systems with more than 3GB of memory
734 properly with 32-bit PCI devices that do not support DAC
735 (Double Address Cycle). Calgary also supports bus level
736 isolation, where all DMAs pass through the IOMMU. This
737 prevents them from going anywhere except their intended
738 destination. This catches hard-to-find kernel bugs and
739 mis-behaving drivers and devices that do not use the DMA-API
740 properly to set up their DMA buffers. The IOMMU can be
741 turned off at boot time with the iommu=off parameter.
742 Normally the kernel will make the right choice by itself.
743 If unsure, say Y.
745 config CALGARY_IOMMU_ENABLED_BY_DEFAULT
746 def_bool y
747 prompt "Should Calgary be enabled by default?"
748 depends on CALGARY_IOMMU
749 ---help---
750 Should Calgary be enabled by default? if you choose 'y', Calgary
751 will be used (if it exists). If you choose 'n', Calgary will not be
752 used even if it exists. If you choose 'n' and would like to use
753 Calgary anyway, pass 'iommu=calgary' on the kernel command line.
754 If unsure, say Y.
756 # need this always selected by IOMMU for the VIA workaround
757 config SWIOTLB
758 def_bool y if X86_64
759 ---help---
760 Support for software bounce buffers used on x86-64 systems
761 which don't have a hardware IOMMU (e.g. the current generation
762 of Intel's x86-64 CPUs). Using this PCI devices which can only
763 access 32-bits of memory can be used on systems with more than
764 3 GB of memory. If unsure, say Y.
766 config IOMMU_HELPER
767 def_bool (CALGARY_IOMMU || GART_IOMMU || SWIOTLB || AMD_IOMMU)
769 config MAXSMP
770 bool "Enable Maximum number of SMP Processors and NUMA Nodes"
771 depends on X86_64 && SMP && DEBUG_KERNEL && EXPERIMENTAL
772 select CPUMASK_OFFSTACK
773 ---help---
774 Enable maximum number of CPUS and NUMA Nodes for this architecture.
775 If unsure, say N.
777 config NR_CPUS
778 int "Maximum number of CPUs" if SMP && !MAXSMP
779 range 2 8 if SMP && X86_32 && !X86_BIGSMP
780 range 2 512 if SMP && !MAXSMP
781 default "1" if !SMP
782 default "4096" if MAXSMP
783 default "32" if SMP && (X86_NUMAQ || X86_SUMMIT || X86_BIGSMP || X86_ES7000)
784 default "8" if SMP
785 ---help---
786 This allows you to specify the maximum number of CPUs which this
787 kernel will support. The maximum supported value is 512 and the
788 minimum value which makes sense is 2.
790 This is purely to save memory - each supported CPU adds
791 approximately eight kilobytes to the kernel image.
793 config SCHED_SMT
794 bool "SMT (Hyperthreading) scheduler support"
795 depends on X86_HT
796 ---help---
797 SMT scheduler support improves the CPU scheduler's decision making
798 when dealing with Intel Pentium 4 chips with HyperThreading at a
799 cost of slightly increased overhead in some places. If unsure say
800 N here.
802 config SCHED_MC
803 def_bool y
804 prompt "Multi-core scheduler support"
805 depends on X86_HT
806 ---help---
807 Multi-core scheduler support improves the CPU scheduler's decision
808 making when dealing with multi-core CPU chips at a cost of slightly
809 increased overhead in some places. If unsure say N here.
811 config IRQ_TIME_ACCOUNTING
812 bool "Fine granularity task level IRQ time accounting"
813 default n
814 ---help---
815 Select this option to enable fine granularity task irq time
816 accounting. This is done by reading a timestamp on each
817 transitions between softirq and hardirq state, so there can be a
818 small performance impact.
820 If in doubt, say N here.
822 source "kernel/Kconfig.preempt"
824 config X86_UP_APIC
825 bool "Local APIC support on uniprocessors"
826 depends on X86_32 && !SMP && !X86_32_NON_STANDARD
827 ---help---
828 A local APIC (Advanced Programmable Interrupt Controller) is an
829 integrated interrupt controller in the CPU. If you have a single-CPU
830 system which has a processor with a local APIC, you can say Y here to
831 enable and use it. If you say Y here even though your machine doesn't
832 have a local APIC, then the kernel will still run with no slowdown at
833 all. The local APIC supports CPU-generated self-interrupts (timer,
834 performance counters), and the NMI watchdog which detects hard
835 lockups.
837 config X86_UP_IOAPIC
838 bool "IO-APIC support on uniprocessors"
839 depends on X86_UP_APIC
840 ---help---
841 An IO-APIC (I/O Advanced Programmable Interrupt Controller) is an
842 SMP-capable replacement for PC-style interrupt controllers. Most
843 SMP systems and many recent uniprocessor systems have one.
845 If you have a single-CPU system with an IO-APIC, you can say Y here
846 to use it. If you say Y here even though your machine doesn't have
847 an IO-APIC, then the kernel will still run with no slowdown at all.
849 config X86_LOCAL_APIC
850 def_bool y
851 depends on X86_64 || SMP || X86_32_NON_STANDARD || X86_UP_APIC
853 config X86_IO_APIC
854 def_bool y
855 depends on X86_64 || SMP || X86_32_NON_STANDARD || X86_UP_IOAPIC
857 config X86_VISWS_APIC
858 def_bool y
859 depends on X86_32 && X86_VISWS
861 config X86_REROUTE_FOR_BROKEN_BOOT_IRQS
862 bool "Reroute for broken boot IRQs"
863 depends on X86_IO_APIC
864 ---help---
865 This option enables a workaround that fixes a source of
866 spurious interrupts. This is recommended when threaded
867 interrupt handling is used on systems where the generation of
868 superfluous "boot interrupts" cannot be disabled.
870 Some chipsets generate a legacy INTx "boot IRQ" when the IRQ
871 entry in the chipset's IO-APIC is masked (as, e.g. the RT
872 kernel does during interrupt handling). On chipsets where this
873 boot IRQ generation cannot be disabled, this workaround keeps
874 the original IRQ line masked so that only the equivalent "boot
875 IRQ" is delivered to the CPUs. The workaround also tells the
876 kernel to set up the IRQ handler on the boot IRQ line. In this
877 way only one interrupt is delivered to the kernel. Otherwise
878 the spurious second interrupt may cause the kernel to bring
879 down (vital) interrupt lines.
881 Only affects "broken" chipsets. Interrupt sharing may be
882 increased on these systems.
884 config X86_MCE
885 bool "Machine Check / overheating reporting"
886 ---help---
887 Machine Check support allows the processor to notify the
888 kernel if it detects a problem (e.g. overheating, data corruption).
889 The action the kernel takes depends on the severity of the problem,
890 ranging from warning messages to halting the machine.
892 config X86_MCE_INTEL
893 def_bool y
894 prompt "Intel MCE features"
895 depends on X86_MCE && X86_LOCAL_APIC
896 ---help---
897 Additional support for intel specific MCE features such as
898 the thermal monitor.
900 config X86_MCE_AMD
901 def_bool y
902 prompt "AMD MCE features"
903 depends on X86_MCE && X86_LOCAL_APIC
904 ---help---
905 Additional support for AMD specific MCE features such as
906 the DRAM Error Threshold.
908 config X86_ANCIENT_MCE
909 bool "Support for old Pentium 5 / WinChip machine checks"
910 depends on X86_32 && X86_MCE
911 ---help---
912 Include support for machine check handling on old Pentium 5 or WinChip
913 systems. These typically need to be enabled explicitely on the command
914 line.
916 config X86_MCE_THRESHOLD
917 depends on X86_MCE_AMD || X86_MCE_INTEL
918 def_bool y
920 config X86_MCE_INJECT
921 depends on X86_MCE
922 tristate "Machine check injector support"
923 ---help---
924 Provide support for injecting machine checks for testing purposes.
925 If you don't know what a machine check is and you don't do kernel
926 QA it is safe to say n.
928 config X86_THERMAL_VECTOR
929 def_bool y
930 depends on X86_MCE_INTEL
932 config VM86
933 bool "Enable VM86 support" if EXPERT
934 default y
935 depends on X86_32
936 ---help---
937 This option is required by programs like DOSEMU to run 16-bit legacy
938 code on X86 processors. It also may be needed by software like
939 XFree86 to initialize some video cards via BIOS. Disabling this
940 option saves about 6k.
942 config TOSHIBA
943 tristate "Toshiba Laptop support"
944 depends on X86_32
945 ---help---
946 This adds a driver to safely access the System Management Mode of
947 the CPU on Toshiba portables with a genuine Toshiba BIOS. It does
948 not work on models with a Phoenix BIOS. The System Management Mode
949 is used to set the BIOS and power saving options on Toshiba portables.
951 For information on utilities to make use of this driver see the
952 Toshiba Linux utilities web site at:
953 <http://www.buzzard.org.uk/toshiba/>.
955 Say Y if you intend to run this kernel on a Toshiba portable.
956 Say N otherwise.
958 config I8K
959 tristate "Dell laptop support"
960 select HWMON
961 ---help---
962 This adds a driver to safely access the System Management Mode
963 of the CPU on the Dell Inspiron 8000. The System Management Mode
964 is used to read cpu temperature and cooling fan status and to
965 control the fans on the I8K portables.
967 This driver has been tested only on the Inspiron 8000 but it may
968 also work with other Dell laptops. You can force loading on other
969 models by passing the parameter `force=1' to the module. Use at
970 your own risk.
972 For information on utilities to make use of this driver see the
973 I8K Linux utilities web site at:
974 <http://people.debian.org/~dz/i8k/>
976 Say Y if you intend to run this kernel on a Dell Inspiron 8000.
977 Say N otherwise.
979 config X86_REBOOTFIXUPS
980 bool "Enable X86 board specific fixups for reboot"
981 depends on X86_32
982 ---help---
983 This enables chipset and/or board specific fixups to be done
984 in order to get reboot to work correctly. This is only needed on
985 some combinations of hardware and BIOS. The symptom, for which
986 this config is intended, is when reboot ends with a stalled/hung
987 system.
989 Currently, the only fixup is for the Geode machines using
990 CS5530A and CS5536 chipsets and the RDC R-321x SoC.
992 Say Y if you want to enable the fixup. Currently, it's safe to
993 enable this option even if you don't need it.
994 Say N otherwise.
996 config MICROCODE
997 tristate "/dev/cpu/microcode - microcode support"
998 select FW_LOADER
999 ---help---
1000 If you say Y here, you will be able to update the microcode on
1001 certain Intel and AMD processors. The Intel support is for the
1002 IA32 family, e.g. Pentium Pro, Pentium II, Pentium III,
1003 Pentium 4, Xeon etc. The AMD support is for family 0x10 and
1004 0x11 processors, e.g. Opteron, Phenom and Turion 64 Ultra.
1005 You will obviously need the actual microcode binary data itself
1006 which is not shipped with the Linux kernel.
1008 This option selects the general module only, you need to select
1009 at least one vendor specific module as well.
1011 To compile this driver as a module, choose M here: the
1012 module will be called microcode.
1014 config MICROCODE_INTEL
1015 bool "Intel microcode patch loading support"
1016 depends on MICROCODE
1017 default MICROCODE
1018 select FW_LOADER
1019 ---help---
1020 This options enables microcode patch loading support for Intel
1021 processors.
1023 For latest news and information on obtaining all the required
1024 Intel ingredients for this driver, check:
1025 <http://www.urbanmyth.org/microcode/>.
1027 config MICROCODE_AMD
1028 bool "AMD microcode patch loading support"
1029 depends on MICROCODE
1030 select FW_LOADER
1031 ---help---
1032 If you select this option, microcode patch loading support for AMD
1033 processors will be enabled.
1035 config MICROCODE_OLD_INTERFACE
1036 def_bool y
1037 depends on MICROCODE
1039 config X86_MSR
1040 tristate "/dev/cpu/*/msr - Model-specific register support"
1041 ---help---
1042 This device gives privileged processes access to the x86
1043 Model-Specific Registers (MSRs). It is a character device with
1044 major 202 and minors 0 to 31 for /dev/cpu/0/msr to /dev/cpu/31/msr.
1045 MSR accesses are directed to a specific CPU on multi-processor
1046 systems.
1048 config X86_CPUID
1049 tristate "/dev/cpu/*/cpuid - CPU information support"
1050 ---help---
1051 This device gives processes access to the x86 CPUID instruction to
1052 be executed on a specific processor. It is a character device
1053 with major 203 and minors 0 to 31 for /dev/cpu/0/cpuid to
1054 /dev/cpu/31/cpuid.
1056 choice
1057 prompt "High Memory Support"
1058 default HIGHMEM64G if X86_NUMAQ
1059 default HIGHMEM4G
1060 depends on X86_32
1062 config NOHIGHMEM
1063 bool "off"
1064 depends on !X86_NUMAQ
1065 ---help---
1066 Linux can use up to 64 Gigabytes of physical memory on x86 systems.
1067 However, the address space of 32-bit x86 processors is only 4
1068 Gigabytes large. That means that, if you have a large amount of
1069 physical memory, not all of it can be "permanently mapped" by the
1070 kernel. The physical memory that's not permanently mapped is called
1071 "high memory".
1073 If you are compiling a kernel which will never run on a machine with
1074 more than 1 Gigabyte total physical RAM, answer "off" here (default
1075 choice and suitable for most users). This will result in a "3GB/1GB"
1076 split: 3GB are mapped so that each process sees a 3GB virtual memory
1077 space and the remaining part of the 4GB virtual memory space is used
1078 by the kernel to permanently map as much physical memory as
1079 possible.
1081 If the machine has between 1 and 4 Gigabytes physical RAM, then
1082 answer "4GB" here.
1084 If more than 4 Gigabytes is used then answer "64GB" here. This
1085 selection turns Intel PAE (Physical Address Extension) mode on.
1086 PAE implements 3-level paging on IA32 processors. PAE is fully
1087 supported by Linux, PAE mode is implemented on all recent Intel
1088 processors (Pentium Pro and better). NOTE: If you say "64GB" here,
1089 then the kernel will not boot on CPUs that don't support PAE!
1091 The actual amount of total physical memory will either be
1092 auto detected or can be forced by using a kernel command line option
1093 such as "mem=256M". (Try "man bootparam" or see the documentation of
1094 your boot loader (lilo or loadlin) about how to pass options to the
1095 kernel at boot time.)
1097 If unsure, say "off".
1099 config HIGHMEM4G
1100 bool "4GB"
1101 depends on !X86_NUMAQ
1102 ---help---
1103 Select this if you have a 32-bit processor and between 1 and 4
1104 gigabytes of physical RAM.
1106 config HIGHMEM64G
1107 bool "64GB"
1108 depends on !M386 && !M486
1109 select X86_PAE
1110 ---help---
1111 Select this if you have a 32-bit processor and more than 4
1112 gigabytes of physical RAM.
1114 endchoice
1116 choice
1117 depends on EXPERIMENTAL
1118 prompt "Memory split" if EXPERT
1119 default VMSPLIT_3G
1120 depends on X86_32
1121 ---help---
1122 Select the desired split between kernel and user memory.
1124 If the address range available to the kernel is less than the
1125 physical memory installed, the remaining memory will be available
1126 as "high memory". Accessing high memory is a little more costly
1127 than low memory, as it needs to be mapped into the kernel first.
1128 Note that increasing the kernel address space limits the range
1129 available to user programs, making the address space there
1130 tighter. Selecting anything other than the default 3G/1G split
1131 will also likely make your kernel incompatible with binary-only
1132 kernel modules.
1134 If you are not absolutely sure what you are doing, leave this
1135 option alone!
1137 config VMSPLIT_3G
1138 bool "3G/1G user/kernel split"
1139 config VMSPLIT_3G_OPT
1140 depends on !X86_PAE
1141 bool "3G/1G user/kernel split (for full 1G low memory)"
1142 config VMSPLIT_2G
1143 bool "2G/2G user/kernel split"
1144 config VMSPLIT_2G_OPT
1145 depends on !X86_PAE
1146 bool "2G/2G user/kernel split (for full 2G low memory)"
1147 config VMSPLIT_1G
1148 bool "1G/3G user/kernel split"
1149 endchoice
1151 config PAGE_OFFSET
1152 hex
1153 default 0xB0000000 if VMSPLIT_3G_OPT
1154 default 0x80000000 if VMSPLIT_2G
1155 default 0x78000000 if VMSPLIT_2G_OPT
1156 default 0x40000000 if VMSPLIT_1G
1157 default 0xC0000000
1158 depends on X86_32
1160 config HIGHMEM
1161 def_bool y
1162 depends on X86_32 && (HIGHMEM64G || HIGHMEM4G)
1164 config X86_PAE
1165 bool "PAE (Physical Address Extension) Support"
1166 depends on X86_32 && !HIGHMEM4G
1167 ---help---
1168 PAE is required for NX support, and furthermore enables
1169 larger swapspace support for non-overcommit purposes. It
1170 has the cost of more pagetable lookup overhead, and also
1171 consumes more pagetable space per process.
1173 config ARCH_PHYS_ADDR_T_64BIT
1174 def_bool X86_64 || X86_PAE
1176 config ARCH_DMA_ADDR_T_64BIT
1177 def_bool X86_64 || HIGHMEM64G
1179 config DIRECT_GBPAGES
1180 bool "Enable 1GB pages for kernel pagetables" if EXPERT
1181 default y
1182 depends on X86_64
1183 ---help---
1184 Allow the kernel linear mapping to use 1GB pages on CPUs that
1185 support it. This can improve the kernel's performance a tiny bit by
1186 reducing TLB pressure. If in doubt, say "Y".
1188 # Common NUMA Features
1189 config NUMA
1190 bool "Numa Memory Allocation and Scheduler Support"
1191 depends on SMP
1192 depends on X86_64 || (X86_32 && HIGHMEM64G && (X86_NUMAQ || X86_BIGSMP || X86_SUMMIT && ACPI) && EXPERIMENTAL)
1193 default y if (X86_NUMAQ || X86_SUMMIT || X86_BIGSMP)
1194 ---help---
1195 Enable NUMA (Non Uniform Memory Access) support.
1197 The kernel will try to allocate memory used by a CPU on the
1198 local memory controller of the CPU and add some more
1199 NUMA awareness to the kernel.
1201 For 64-bit this is recommended if the system is Intel Core i7
1202 (or later), AMD Opteron, or EM64T NUMA.
1204 For 32-bit this is only needed on (rare) 32-bit-only platforms
1205 that support NUMA topologies, such as NUMAQ / Summit, or if you
1206 boot a 32-bit kernel on a 64-bit NUMA platform.
1208 Otherwise, you should say N.
1210 comment "NUMA (Summit) requires SMP, 64GB highmem support, ACPI"
1211 depends on X86_32 && X86_SUMMIT && (!HIGHMEM64G || !ACPI)
1213 config AMD_NUMA
1214 def_bool y
1215 prompt "Old style AMD Opteron NUMA detection"
1216 depends on X86_64 && NUMA && PCI
1217 ---help---
1218 Enable AMD NUMA node topology detection. You should say Y here if
1219 you have a multi processor AMD system. This uses an old method to
1220 read the NUMA configuration directly from the builtin Northbridge
1221 of Opteron. It is recommended to use X86_64_ACPI_NUMA instead,
1222 which also takes priority if both are compiled in.
1224 config X86_64_ACPI_NUMA
1225 def_bool y
1226 prompt "ACPI NUMA detection"
1227 depends on X86_64 && NUMA && ACPI && PCI
1228 select ACPI_NUMA
1229 ---help---
1230 Enable ACPI SRAT based node topology detection.
1232 # Some NUMA nodes have memory ranges that span
1233 # other nodes. Even though a pfn is valid and
1234 # between a node's start and end pfns, it may not
1235 # reside on that node. See memmap_init_zone()
1236 # for details.
1237 config NODES_SPAN_OTHER_NODES
1238 def_bool y
1239 depends on X86_64_ACPI_NUMA
1241 config NUMA_EMU
1242 bool "NUMA emulation"
1243 depends on NUMA
1244 ---help---
1245 Enable NUMA emulation. A flat machine will be split
1246 into virtual nodes when booted with "numa=fake=N", where N is the
1247 number of nodes. This is only useful for debugging.
1249 config NODES_SHIFT
1250 int "Maximum NUMA Nodes (as a power of 2)" if !MAXSMP
1251 range 1 10
1252 default "10" if MAXSMP
1253 default "6" if X86_64
1254 default "4" if X86_NUMAQ
1255 default "3"
1256 depends on NEED_MULTIPLE_NODES
1257 ---help---
1258 Specify the maximum number of NUMA Nodes available on the target
1259 system. Increases memory reserved to accommodate various tables.
1261 config HAVE_ARCH_BOOTMEM
1262 def_bool y
1263 depends on X86_32 && NUMA
1265 config HAVE_ARCH_ALLOC_REMAP
1266 def_bool y
1267 depends on X86_32 && NUMA
1269 config ARCH_HAVE_MEMORY_PRESENT
1270 def_bool y
1271 depends on X86_32 && DISCONTIGMEM
1273 config NEED_NODE_MEMMAP_SIZE
1274 def_bool y
1275 depends on X86_32 && (DISCONTIGMEM || SPARSEMEM)
1277 config ARCH_FLATMEM_ENABLE
1278 def_bool y
1279 depends on X86_32 && !NUMA
1281 config ARCH_DISCONTIGMEM_ENABLE
1282 def_bool y
1283 depends on NUMA && X86_32
1285 config ARCH_DISCONTIGMEM_DEFAULT
1286 def_bool y
1287 depends on NUMA && X86_32
1289 config ARCH_SPARSEMEM_ENABLE
1290 def_bool y
1291 depends on X86_64 || NUMA || (EXPERIMENTAL && X86_32) || X86_32_NON_STANDARD
1292 select SPARSEMEM_STATIC if X86_32
1293 select SPARSEMEM_VMEMMAP_ENABLE if X86_64
1295 config ARCH_SPARSEMEM_DEFAULT
1296 def_bool y
1297 depends on X86_64
1299 config ARCH_SELECT_MEMORY_MODEL
1300 def_bool y
1301 depends on ARCH_SPARSEMEM_ENABLE
1303 config ARCH_MEMORY_PROBE
1304 def_bool X86_64
1305 depends on MEMORY_HOTPLUG
1307 config ARCH_PROC_KCORE_TEXT
1308 def_bool y
1309 depends on X86_64 && PROC_KCORE
1311 config ILLEGAL_POINTER_VALUE
1312 hex
1313 default 0 if X86_32
1314 default 0xdead000000000000 if X86_64
1316 source "mm/Kconfig"
1318 config HIGHPTE
1319 bool "Allocate 3rd-level pagetables from highmem"
1320 depends on HIGHMEM
1321 ---help---
1322 The VM uses one page table entry for each page of physical memory.
1323 For systems with a lot of RAM, this can be wasteful of precious
1324 low memory. Setting this option will put user-space page table
1325 entries in high memory.
1327 config X86_CHECK_BIOS_CORRUPTION
1328 bool "Check for low memory corruption"
1329 ---help---
1330 Periodically check for memory corruption in low memory, which
1331 is suspected to be caused by BIOS. Even when enabled in the
1332 configuration, it is disabled at runtime. Enable it by
1333 setting "memory_corruption_check=1" on the kernel command
1334 line. By default it scans the low 64k of memory every 60
1335 seconds; see the memory_corruption_check_size and
1336 memory_corruption_check_period parameters in
1337 Documentation/kernel-parameters.txt to adjust this.
1339 When enabled with the default parameters, this option has
1340 almost no overhead, as it reserves a relatively small amount
1341 of memory and scans it infrequently. It both detects corruption
1342 and prevents it from affecting the running system.
1344 It is, however, intended as a diagnostic tool; if repeatable
1345 BIOS-originated corruption always affects the same memory,
1346 you can use memmap= to prevent the kernel from using that
1347 memory.
1349 config X86_BOOTPARAM_MEMORY_CORRUPTION_CHECK
1350 bool "Set the default setting of memory_corruption_check"
1351 depends on X86_CHECK_BIOS_CORRUPTION
1352 default y
1353 ---help---
1354 Set whether the default state of memory_corruption_check is
1355 on or off.
1357 config X86_RESERVE_LOW
1358 int "Amount of low memory, in kilobytes, to reserve for the BIOS"
1359 default 64
1360 range 4 640
1361 ---help---
1362 Specify the amount of low memory to reserve for the BIOS.
1364 The first page contains BIOS data structures that the kernel
1365 must not use, so that page must always be reserved.
1367 By default we reserve the first 64K of physical RAM, as a
1368 number of BIOSes are known to corrupt that memory range
1369 during events such as suspend/resume or monitor cable
1370 insertion, so it must not be used by the kernel.
1372 You can set this to 4 if you are absolutely sure that you
1373 trust the BIOS to get all its memory reservations and usages
1374 right. If you know your BIOS have problems beyond the
1375 default 64K area, you can set this to 640 to avoid using the
1376 entire low memory range.
1378 If you have doubts about the BIOS (e.g. suspend/resume does
1379 not work or there's kernel crashes after certain hardware
1380 hotplug events) then you might want to enable
1381 X86_CHECK_BIOS_CORRUPTION=y to allow the kernel to check
1382 typical corruption patterns.
1384 Leave this to the default value of 64 if you are unsure.
1386 config MATH_EMULATION
1387 bool
1388 prompt "Math emulation" if X86_32
1389 ---help---
1390 Linux can emulate a math coprocessor (used for floating point
1391 operations) if you don't have one. 486DX and Pentium processors have
1392 a math coprocessor built in, 486SX and 386 do not, unless you added
1393 a 487DX or 387, respectively. (The messages during boot time can
1394 give you some hints here ["man dmesg"].) Everyone needs either a
1395 coprocessor or this emulation.
1397 If you don't have a math coprocessor, you need to say Y here; if you
1398 say Y here even though you have a coprocessor, the coprocessor will
1399 be used nevertheless. (This behavior can be changed with the kernel
1400 command line option "no387", which comes handy if your coprocessor
1401 is broken. Try "man bootparam" or see the documentation of your boot
1402 loader (lilo or loadlin) about how to pass options to the kernel at
1403 boot time.) This means that it is a good idea to say Y here if you
1404 intend to use this kernel on different machines.
1406 More information about the internals of the Linux math coprocessor
1407 emulation can be found in <file:arch/x86/math-emu/README>.
1409 If you are not sure, say Y; apart from resulting in a 66 KB bigger
1410 kernel, it won't hurt.
1412 config MTRR
1413 def_bool y
1414 prompt "MTRR (Memory Type Range Register) support" if EXPERT
1415 ---help---
1416 On Intel P6 family processors (Pentium Pro, Pentium II and later)
1417 the Memory Type Range Registers (MTRRs) may be used to control
1418 processor access to memory ranges. This is most useful if you have
1419 a video (VGA) card on a PCI or AGP bus. Enabling write-combining
1420 allows bus write transfers to be combined into a larger transfer
1421 before bursting over the PCI/AGP bus. This can increase performance
1422 of image write operations 2.5 times or more. Saying Y here creates a
1423 /proc/mtrr file which may be used to manipulate your processor's
1424 MTRRs. Typically the X server should use this.
1426 This code has a reasonably generic interface so that similar
1427 control registers on other processors can be easily supported
1428 as well:
1430 The Cyrix 6x86, 6x86MX and M II processors have Address Range
1431 Registers (ARRs) which provide a similar functionality to MTRRs. For
1432 these, the ARRs are used to emulate the MTRRs.
1433 The AMD K6-2 (stepping 8 and above) and K6-3 processors have two
1434 MTRRs. The Centaur C6 (WinChip) has 8 MCRs, allowing
1435 write-combining. All of these processors are supported by this code
1436 and it makes sense to say Y here if you have one of them.
1438 Saying Y here also fixes a problem with buggy SMP BIOSes which only
1439 set the MTRRs for the boot CPU and not for the secondary CPUs. This
1440 can lead to all sorts of problems, so it's good to say Y here.
1442 You can safely say Y even if your machine doesn't have MTRRs, you'll
1443 just add about 9 KB to your kernel.
1445 See <file:Documentation/x86/mtrr.txt> for more information.
1447 config MTRR_SANITIZER
1448 def_bool y
1449 prompt "MTRR cleanup support"
1450 depends on MTRR
1451 ---help---
1452 Convert MTRR layout from continuous to discrete, so X drivers can
1453 add writeback entries.
1455 Can be disabled with disable_mtrr_cleanup on the kernel command line.
1456 The largest mtrr entry size for a continuous block can be set with
1457 mtrr_chunk_size.
1459 If unsure, say Y.
1461 config MTRR_SANITIZER_ENABLE_DEFAULT
1462 int "MTRR cleanup enable value (0-1)"
1463 range 0 1
1464 default "0"
1465 depends on MTRR_SANITIZER
1466 ---help---
1467 Enable mtrr cleanup default value
1469 config MTRR_SANITIZER_SPARE_REG_NR_DEFAULT
1470 int "MTRR cleanup spare reg num (0-7)"
1471 range 0 7
1472 default "1"
1473 depends on MTRR_SANITIZER
1474 ---help---
1475 mtrr cleanup spare entries default, it can be changed via
1476 mtrr_spare_reg_nr=N on the kernel command line.
1478 config X86_PAT
1479 def_bool y
1480 prompt "x86 PAT support" if EXPERT
1481 depends on MTRR
1482 ---help---
1483 Use PAT attributes to setup page level cache control.
1485 PATs are the modern equivalents of MTRRs and are much more
1486 flexible than MTRRs.
1488 Say N here if you see bootup problems (boot crash, boot hang,
1489 spontaneous reboots) or a non-working video driver.
1491 If unsure, say Y.
1493 config ARCH_USES_PG_UNCACHED
1494 def_bool y
1495 depends on X86_PAT
1497 config ARCH_RANDOM
1498 def_bool y
1499 prompt "x86 architectural random number generator" if EXPERT
1500 ---help---
1501 Enable the x86 architectural RDRAND instruction
1502 (Intel Bull Mountain technology) to generate random numbers.
1503 If supported, this is a high bandwidth, cryptographically
1504 secure hardware random number generator.
1506 config EFI
1507 bool "EFI runtime service support"
1508 depends on ACPI
1509 ---help---
1510 This enables the kernel to use EFI runtime services that are
1511 available (such as the EFI variable services).
1513 This option is only useful on systems that have EFI firmware.
1514 In addition, you should use the latest ELILO loader available
1515 at <http://elilo.sourceforge.net> in order to take advantage
1516 of EFI runtime services. However, even with this option, the
1517 resultant kernel should continue to boot on existing non-EFI
1518 platforms.
1520 config EFI_STUB
1521 bool "EFI stub support"
1522 depends on EFI
1523 ---help---
1524 This kernel feature allows a bzImage to be loaded directly
1525 by EFI firmware without the use of a bootloader.
1527 config SECCOMP
1528 def_bool y
1529 prompt "Enable seccomp to safely compute untrusted bytecode"
1530 ---help---
1531 This kernel feature is useful for number crunching applications
1532 that may need to compute untrusted bytecode during their
1533 execution. By using pipes or other transports made available to
1534 the process as file descriptors supporting the read/write
1535 syscalls, it's possible to isolate those applications in
1536 their own address space using seccomp. Once seccomp is
1537 enabled via prctl(PR_SET_SECCOMP), it cannot be disabled
1538 and the task is only allowed to execute a few safe syscalls
1539 defined by each seccomp mode.
1541 If unsure, say Y. Only embedded should say N here.
1543 config CC_STACKPROTECTOR
1544 bool "Enable -fstack-protector buffer overflow detection (EXPERIMENTAL)"
1545 ---help---
1546 This option turns on the -fstack-protector GCC feature. This
1547 feature puts, at the beginning of functions, a canary value on
1548 the stack just before the return address, and validates
1549 the value just before actually returning. Stack based buffer
1550 overflows (that need to overwrite this return address) now also
1551 overwrite the canary, which gets detected and the attack is then
1552 neutralized via a kernel panic.
1554 This feature requires gcc version 4.2 or above, or a distribution
1555 gcc with the feature backported. Older versions are automatically
1556 detected and for those versions, this configuration option is
1557 ignored. (and a warning is printed during bootup)
1559 source kernel/Kconfig.hz
1561 config KEXEC
1562 bool "kexec system call"
1563 ---help---
1564 kexec is a system call that implements the ability to shutdown your
1565 current kernel, and to start another kernel. It is like a reboot
1566 but it is independent of the system firmware. And like a reboot
1567 you can start any kernel with it, not just Linux.
1569 The name comes from the similarity to the exec system call.
1571 It is an ongoing process to be certain the hardware in a machine
1572 is properly shutdown, so do not be surprised if this code does not
1573 initially work for you. It may help to enable device hotplugging
1574 support. As of this writing the exact hardware interface is
1575 strongly in flux, so no good recommendation can be made.
1577 config CRASH_DUMP
1578 bool "kernel crash dumps"
1579 depends on X86_64 || (X86_32 && HIGHMEM)
1580 ---help---
1581 Generate crash dump after being started by kexec.
1582 This should be normally only set in special crash dump kernels
1583 which are loaded in the main kernel with kexec-tools into
1584 a specially reserved region and then later executed after
1585 a crash by kdump/kexec. The crash dump kernel must be compiled
1586 to a memory address not used by the main kernel or BIOS using
1587 PHYSICAL_START, or it must be built as a relocatable image
1588 (CONFIG_RELOCATABLE=y).
1589 For more details see Documentation/kdump/kdump.txt
1591 config KEXEC_JUMP
1592 bool "kexec jump (EXPERIMENTAL)"
1593 depends on EXPERIMENTAL
1594 depends on KEXEC && HIBERNATION
1595 ---help---
1596 Jump between original kernel and kexeced kernel and invoke
1597 code in physical address mode via KEXEC
1599 config PHYSICAL_START
1600 hex "Physical address where the kernel is loaded" if (EXPERT || CRASH_DUMP)
1601 default "0x1000000"
1602 ---help---
1603 This gives the physical address where the kernel is loaded.
1605 If kernel is a not relocatable (CONFIG_RELOCATABLE=n) then
1606 bzImage will decompress itself to above physical address and
1607 run from there. Otherwise, bzImage will run from the address where
1608 it has been loaded by the boot loader and will ignore above physical
1609 address.
1611 In normal kdump cases one does not have to set/change this option
1612 as now bzImage can be compiled as a completely relocatable image
1613 (CONFIG_RELOCATABLE=y) and be used to load and run from a different
1614 address. This option is mainly useful for the folks who don't want
1615 to use a bzImage for capturing the crash dump and want to use a
1616 vmlinux instead. vmlinux is not relocatable hence a kernel needs
1617 to be specifically compiled to run from a specific memory area
1618 (normally a reserved region) and this option comes handy.
1620 So if you are using bzImage for capturing the crash dump,
1621 leave the value here unchanged to 0x1000000 and set
1622 CONFIG_RELOCATABLE=y. Otherwise if you plan to use vmlinux
1623 for capturing the crash dump change this value to start of
1624 the reserved region. In other words, it can be set based on
1625 the "X" value as specified in the "crashkernel=YM@XM"
1626 command line boot parameter passed to the panic-ed
1627 kernel. Please take a look at Documentation/kdump/kdump.txt
1628 for more details about crash dumps.
1630 Usage of bzImage for capturing the crash dump is recommended as
1631 one does not have to build two kernels. Same kernel can be used
1632 as production kernel and capture kernel. Above option should have
1633 gone away after relocatable bzImage support is introduced. But it
1634 is present because there are users out there who continue to use
1635 vmlinux for dump capture. This option should go away down the
1636 line.
1638 Don't change this unless you know what you are doing.
1640 config RELOCATABLE
1641 bool "Build a relocatable kernel"
1642 default y
1643 ---help---
1644 This builds a kernel image that retains relocation information
1645 so it can be loaded someplace besides the default 1MB.
1646 The relocations tend to make the kernel binary about 10% larger,
1647 but are discarded at runtime.
1649 One use is for the kexec on panic case where the recovery kernel
1650 must live at a different physical address than the primary
1651 kernel.
1653 Note: If CONFIG_RELOCATABLE=y, then the kernel runs from the address
1654 it has been loaded at and the compile time physical address
1655 (CONFIG_PHYSICAL_START) is ignored.
1657 # Relocation on x86-32 needs some additional build support
1658 config X86_NEED_RELOCS
1659 def_bool y
1660 depends on X86_32 && RELOCATABLE
1662 config PHYSICAL_ALIGN
1663 hex "Alignment value to which kernel should be aligned" if X86_32
1664 default "0x1000000"
1665 range 0x2000 0x1000000
1666 ---help---
1667 This value puts the alignment restrictions on physical address
1668 where kernel is loaded and run from. Kernel is compiled for an
1669 address which meets above alignment restriction.
1671 If bootloader loads the kernel at a non-aligned address and
1672 CONFIG_RELOCATABLE is set, kernel will move itself to nearest
1673 address aligned to above value and run from there.
1675 If bootloader loads the kernel at a non-aligned address and
1676 CONFIG_RELOCATABLE is not set, kernel will ignore the run time
1677 load address and decompress itself to the address it has been
1678 compiled for and run from there. The address for which kernel is
1679 compiled already meets above alignment restrictions. Hence the
1680 end result is that kernel runs from a physical address meeting
1681 above alignment restrictions.
1683 Don't change this unless you know what you are doing.
1685 config HOTPLUG_CPU
1686 bool "Support for hot-pluggable CPUs"
1687 depends on SMP && HOTPLUG
1688 ---help---
1689 Say Y here to allow turning CPUs off and on. CPUs can be
1690 controlled through /sys/devices/system/cpu.
1691 ( Note: power management support will enable this option
1692 automatically on SMP systems. )
1693 Say N if you want to disable CPU hotplug.
1695 config COMPAT_VDSO
1696 def_bool y
1697 prompt "Compat VDSO support"
1698 depends on X86_32 || IA32_EMULATION
1699 ---help---
1700 Map the 32-bit VDSO to the predictable old-style address too.
1702 Say N here if you are running a sufficiently recent glibc
1703 version (2.3.3 or later), to remove the high-mapped
1704 VDSO mapping and to exclusively use the randomized VDSO.
1706 If unsure, say Y.
1708 config CMDLINE_BOOL
1709 bool "Built-in kernel command line"
1710 ---help---
1711 Allow for specifying boot arguments to the kernel at
1712 build time. On some systems (e.g. embedded ones), it is
1713 necessary or convenient to provide some or all of the
1714 kernel boot arguments with the kernel itself (that is,
1715 to not rely on the boot loader to provide them.)
1717 To compile command line arguments into the kernel,
1718 set this option to 'Y', then fill in the
1719 the boot arguments in CONFIG_CMDLINE.
1721 Systems with fully functional boot loaders (i.e. non-embedded)
1722 should leave this option set to 'N'.
1724 config CMDLINE
1725 string "Built-in kernel command string"
1726 depends on CMDLINE_BOOL
1727 default ""
1728 ---help---
1729 Enter arguments here that should be compiled into the kernel
1730 image and used at boot time. If the boot loader provides a
1731 command line at boot time, it is appended to this string to
1732 form the full kernel command line, when the system boots.
1734 However, you can use the CONFIG_CMDLINE_OVERRIDE option to
1735 change this behavior.
1737 In most cases, the command line (whether built-in or provided
1738 by the boot loader) should specify the device for the root
1739 file system.
1741 config CMDLINE_OVERRIDE
1742 bool "Built-in command line overrides boot loader arguments"
1743 depends on CMDLINE_BOOL
1744 ---help---
1745 Set this option to 'Y' to have the kernel ignore the boot loader
1746 command line, and use ONLY the built-in command line.
1748 This is used to work around broken boot loaders. This should
1749 be set to 'N' under normal conditions.
1751 endmenu
1753 config ARCH_ENABLE_MEMORY_HOTPLUG
1754 def_bool y
1755 depends on X86_64 || (X86_32 && HIGHMEM)
1757 config ARCH_ENABLE_MEMORY_HOTREMOVE
1758 def_bool y
1759 depends on MEMORY_HOTPLUG
1761 config USE_PERCPU_NUMA_NODE_ID
1762 def_bool y
1763 depends on NUMA
1765 menu "Power management and ACPI options"
1767 config ARCH_HIBERNATION_HEADER
1768 def_bool y
1769 depends on X86_64 && HIBERNATION
1771 source "kernel/power/Kconfig"
1773 source "drivers/acpi/Kconfig"
1775 source "drivers/sfi/Kconfig"
1777 config X86_APM_BOOT
1778 def_bool y
1779 depends on APM
1781 menuconfig APM
1782 tristate "APM (Advanced Power Management) BIOS support"
1783 depends on X86_32 && PM_SLEEP
1784 ---help---
1785 APM is a BIOS specification for saving power using several different
1786 techniques. This is mostly useful for battery powered laptops with
1787 APM compliant BIOSes. If you say Y here, the system time will be
1788 reset after a RESUME operation, the /proc/apm device will provide
1789 battery status information, and user-space programs will receive
1790 notification of APM "events" (e.g. battery status change).
1792 If you select "Y" here, you can disable actual use of the APM
1793 BIOS by passing the "apm=off" option to the kernel at boot time.
1795 Note that the APM support is almost completely disabled for
1796 machines with more than one CPU.
1798 In order to use APM, you will need supporting software. For location
1799 and more information, read <file:Documentation/power/apm-acpi.txt>
1800 and the Battery Powered Linux mini-HOWTO, available from
1801 <http://www.tldp.org/docs.html#howto>.
1803 This driver does not spin down disk drives (see the hdparm(8)
1804 manpage ("man 8 hdparm") for that), and it doesn't turn off
1805 VESA-compliant "green" monitors.
1807 This driver does not support the TI 4000M TravelMate and the ACER
1808 486/DX4/75 because they don't have compliant BIOSes. Many "green"
1809 desktop machines also don't have compliant BIOSes, and this driver
1810 may cause those machines to panic during the boot phase.
1812 Generally, if you don't have a battery in your machine, there isn't
1813 much point in using this driver and you should say N. If you get
1814 random kernel OOPSes or reboots that don't seem to be related to
1815 anything, try disabling/enabling this option (or disabling/enabling
1816 APM in your BIOS).
1818 Some other things you should try when experiencing seemingly random,
1819 "weird" problems:
1821 1) make sure that you have enough swap space and that it is
1822 enabled.
1823 2) pass the "no-hlt" option to the kernel
1824 3) switch on floating point emulation in the kernel and pass
1825 the "no387" option to the kernel
1826 4) pass the "floppy=nodma" option to the kernel
1827 5) pass the "mem=4M" option to the kernel (thereby disabling
1828 all but the first 4 MB of RAM)
1829 6) make sure that the CPU is not over clocked.
1830 7) read the sig11 FAQ at <http://www.bitwizard.nl/sig11/>
1831 8) disable the cache from your BIOS settings
1832 9) install a fan for the video card or exchange video RAM
1833 10) install a better fan for the CPU
1834 11) exchange RAM chips
1835 12) exchange the motherboard.
1837 To compile this driver as a module, choose M here: the
1838 module will be called apm.
1840 if APM
1842 config APM_IGNORE_USER_SUSPEND
1843 bool "Ignore USER SUSPEND"
1844 ---help---
1845 This option will ignore USER SUSPEND requests. On machines with a
1846 compliant APM BIOS, you want to say N. However, on the NEC Versa M
1847 series notebooks, it is necessary to say Y because of a BIOS bug.
1849 config APM_DO_ENABLE
1850 bool "Enable PM at boot time"
1851 ---help---
1852 Enable APM features at boot time. From page 36 of the APM BIOS
1853 specification: "When disabled, the APM BIOS does not automatically
1854 power manage devices, enter the Standby State, enter the Suspend
1855 State, or take power saving steps in response to CPU Idle calls."
1856 This driver will make CPU Idle calls when Linux is idle (unless this
1857 feature is turned off -- see "Do CPU IDLE calls", below). This
1858 should always save battery power, but more complicated APM features
1859 will be dependent on your BIOS implementation. You may need to turn
1860 this option off if your computer hangs at boot time when using APM
1861 support, or if it beeps continuously instead of suspending. Turn
1862 this off if you have a NEC UltraLite Versa 33/C or a Toshiba
1863 T400CDT. This is off by default since most machines do fine without
1864 this feature.
1866 config APM_CPU_IDLE
1867 bool "Make CPU Idle calls when idle"
1868 ---help---
1869 Enable calls to APM CPU Idle/CPU Busy inside the kernel's idle loop.
1870 On some machines, this can activate improved power savings, such as
1871 a slowed CPU clock rate, when the machine is idle. These idle calls
1872 are made after the idle loop has run for some length of time (e.g.,
1873 333 mS). On some machines, this will cause a hang at boot time or
1874 whenever the CPU becomes idle. (On machines with more than one CPU,
1875 this option does nothing.)
1877 config APM_DISPLAY_BLANK
1878 bool "Enable console blanking using APM"
1879 ---help---
1880 Enable console blanking using the APM. Some laptops can use this to
1881 turn off the LCD backlight when the screen blanker of the Linux
1882 virtual console blanks the screen. Note that this is only used by
1883 the virtual console screen blanker, and won't turn off the backlight
1884 when using the X Window system. This also doesn't have anything to
1885 do with your VESA-compliant power-saving monitor. Further, this
1886 option doesn't work for all laptops -- it might not turn off your
1887 backlight at all, or it might print a lot of errors to the console,
1888 especially if you are using gpm.
1890 config APM_ALLOW_INTS
1891 bool "Allow interrupts during APM BIOS calls"
1892 ---help---
1893 Normally we disable external interrupts while we are making calls to
1894 the APM BIOS as a measure to lessen the effects of a badly behaving
1895 BIOS implementation. The BIOS should reenable interrupts if it
1896 needs to. Unfortunately, some BIOSes do not -- especially those in
1897 many of the newer IBM Thinkpads. If you experience hangs when you
1898 suspend, try setting this to Y. Otherwise, say N.
1900 endif # APM
1902 source "drivers/cpufreq/Kconfig"
1904 source "drivers/cpuidle/Kconfig"
1906 source "drivers/idle/Kconfig"
1908 endmenu
1911 menu "Bus options (PCI etc.)"
1913 config PCI
1914 bool "PCI support"
1915 default y
1916 select ARCH_SUPPORTS_MSI if (X86_LOCAL_APIC && X86_IO_APIC)
1917 ---help---
1918 Find out whether you have a PCI motherboard. PCI is the name of a
1919 bus system, i.e. the way the CPU talks to the other stuff inside
1920 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
1921 VESA. If you have PCI, say Y, otherwise N.
1923 choice
1924 prompt "PCI access mode"
1925 depends on X86_32 && PCI
1926 default PCI_GOANY
1927 ---help---
1928 On PCI systems, the BIOS can be used to detect the PCI devices and
1929 determine their configuration. However, some old PCI motherboards
1930 have BIOS bugs and may crash if this is done. Also, some embedded
1931 PCI-based systems don't have any BIOS at all. Linux can also try to
1932 detect the PCI hardware directly without using the BIOS.
1934 With this option, you can specify how Linux should detect the
1935 PCI devices. If you choose "BIOS", the BIOS will be used,
1936 if you choose "Direct", the BIOS won't be used, and if you
1937 choose "MMConfig", then PCI Express MMCONFIG will be used.
1938 If you choose "Any", the kernel will try MMCONFIG, then the
1939 direct access method and falls back to the BIOS if that doesn't
1940 work. If unsure, go with the default, which is "Any".
1942 config PCI_GOBIOS
1943 bool "BIOS"
1945 config PCI_GOMMCONFIG
1946 bool "MMConfig"
1948 config PCI_GODIRECT
1949 bool "Direct"
1951 config PCI_GOOLPC
1952 bool "OLPC XO-1"
1953 depends on OLPC
1955 config PCI_GOANY
1956 bool "Any"
1958 endchoice
1960 config PCI_BIOS
1961 def_bool y
1962 depends on X86_32 && PCI && (PCI_GOBIOS || PCI_GOANY)
1964 # x86-64 doesn't support PCI BIOS access from long mode so always go direct.
1965 config PCI_DIRECT
1966 def_bool y
1967 depends on PCI && (X86_64 || (PCI_GODIRECT || PCI_GOANY || PCI_GOOLPC || PCI_GOMMCONFIG))
1969 config PCI_MMCONFIG
1970 def_bool y
1971 depends on X86_32 && PCI && (ACPI || SFI) && (PCI_GOMMCONFIG || PCI_GOANY)
1973 config PCI_OLPC
1974 def_bool y
1975 depends on PCI && OLPC && (PCI_GOOLPC || PCI_GOANY)
1977 config PCI_XEN
1978 def_bool y
1979 depends on PCI && XEN
1980 select SWIOTLB_XEN
1982 config PCI_DOMAINS
1983 def_bool y
1984 depends on PCI
1986 config PCI_MMCONFIG
1987 bool "Support mmconfig PCI config space access"
1988 depends on X86_64 && PCI && ACPI
1990 config PCI_CNB20LE_QUIRK
1991 bool "Read CNB20LE Host Bridge Windows" if EXPERT
1992 default n
1993 depends on PCI && EXPERIMENTAL
1994 help
1995 Read the PCI windows out of the CNB20LE host bridge. This allows
1996 PCI hotplug to work on systems with the CNB20LE chipset which do
1997 not have ACPI.
1999 There's no public spec for this chipset, and this functionality
2000 is known to be incomplete.
2002 You should say N unless you know you need this.
2004 source "drivers/pci/pcie/Kconfig"
2006 source "drivers/pci/Kconfig"
2008 # x86_64 have no ISA slots, but can have ISA-style DMA.
2009 config ISA_DMA_API
2010 bool "ISA-style DMA support" if (X86_64 && EXPERT)
2011 default y
2012 help
2013 Enables ISA-style DMA support for devices requiring such controllers.
2014 If unsure, say Y.
2016 if X86_32
2018 config ISA
2019 bool "ISA support"
2020 ---help---
2021 Find out whether you have ISA slots on your motherboard. ISA is the
2022 name of a bus system, i.e. the way the CPU talks to the other stuff
2023 inside your box. Other bus systems are PCI, EISA, MicroChannel
2024 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
2025 newer boards don't support it. If you have ISA, say Y, otherwise N.
2027 config EISA
2028 bool "EISA support"
2029 depends on ISA
2030 ---help---
2031 The Extended Industry Standard Architecture (EISA) bus was
2032 developed as an open alternative to the IBM MicroChannel bus.
2034 The EISA bus provided some of the features of the IBM MicroChannel
2035 bus while maintaining backward compatibility with cards made for
2036 the older ISA bus. The EISA bus saw limited use between 1988 and
2037 1995 when it was made obsolete by the PCI bus.
2039 Say Y here if you are building a kernel for an EISA-based machine.
2041 Otherwise, say N.
2043 source "drivers/eisa/Kconfig"
2045 config MCA
2046 bool "MCA support"
2047 ---help---
2048 MicroChannel Architecture is found in some IBM PS/2 machines and
2049 laptops. It is a bus system similar to PCI or ISA. See
2050 <file:Documentation/mca.txt> (and especially the web page given
2051 there) before attempting to build an MCA bus kernel.
2053 source "drivers/mca/Kconfig"
2055 config SCx200
2056 tristate "NatSemi SCx200 support"
2057 ---help---
2058 This provides basic support for National Semiconductor's
2059 (now AMD's) Geode processors. The driver probes for the
2060 PCI-IDs of several on-chip devices, so its a good dependency
2061 for other scx200_* drivers.
2063 If compiled as a module, the driver is named scx200.
2065 config SCx200HR_TIMER
2066 tristate "NatSemi SCx200 27MHz High-Resolution Timer Support"
2067 depends on SCx200
2068 default y
2069 ---help---
2070 This driver provides a clocksource built upon the on-chip
2071 27MHz high-resolution timer. Its also a workaround for
2072 NSC Geode SC-1100's buggy TSC, which loses time when the
2073 processor goes idle (as is done by the scheduler). The
2074 other workaround is idle=poll boot option.
2076 config OLPC
2077 bool "One Laptop Per Child support"
2078 depends on !X86_PAE
2079 select GPIOLIB
2080 select OF
2081 select OF_PROMTREE
2082 ---help---
2083 Add support for detecting the unique features of the OLPC
2084 XO hardware.
2086 config OLPC_XO1_PM
2087 bool "OLPC XO-1 Power Management"
2088 depends on OLPC && MFD_CS5535 && PM_SLEEP
2089 select MFD_CORE
2090 ---help---
2091 Add support for poweroff and suspend of the OLPC XO-1 laptop.
2093 config OLPC_XO1_RTC
2094 bool "OLPC XO-1 Real Time Clock"
2095 depends on OLPC_XO1_PM && RTC_DRV_CMOS
2096 ---help---
2097 Add support for the XO-1 real time clock, which can be used as a
2098 programmable wakeup source.
2100 config OLPC_XO1_SCI
2101 bool "OLPC XO-1 SCI extras"
2102 depends on OLPC && OLPC_XO1_PM
2103 select POWER_SUPPLY
2104 select GPIO_CS5535
2105 select MFD_CORE
2106 ---help---
2107 Add support for SCI-based features of the OLPC XO-1 laptop:
2108 - EC-driven system wakeups
2109 - Power button
2110 - Ebook switch
2111 - Lid switch
2112 - AC adapter status updates
2113 - Battery status updates
2115 config OLPC_XO15_SCI
2116 bool "OLPC XO-1.5 SCI extras"
2117 depends on OLPC && ACPI
2118 select POWER_SUPPLY
2119 ---help---
2120 Add support for SCI-based features of the OLPC XO-1.5 laptop:
2121 - EC-driven system wakeups
2122 - AC adapter status updates
2123 - Battery status updates
2125 config ALIX
2126 bool "PCEngines ALIX System Support (LED setup)"
2127 select GPIOLIB
2128 ---help---
2129 This option enables system support for the PCEngines ALIX.
2130 At present this just sets up LEDs for GPIO control on
2131 ALIX2/3/6 boards. However, other system specific setup should
2132 get added here.
2134 Note: You must still enable the drivers for GPIO and LED support
2135 (GPIO_CS5535 & LEDS_GPIO) to actually use the LEDs
2137 Note: You have to set alix.force=1 for boards with Award BIOS.
2139 endif # X86_32
2141 config AMD_NB
2142 def_bool y
2143 depends on CPU_SUP_AMD && PCI
2145 source "drivers/pcmcia/Kconfig"
2147 source "drivers/pci/hotplug/Kconfig"
2149 config RAPIDIO
2150 bool "RapidIO support"
2151 depends on PCI
2152 default n
2153 help
2154 If you say Y here, the kernel will include drivers and
2155 infrastructure code to support RapidIO interconnect devices.
2157 source "drivers/rapidio/Kconfig"
2159 endmenu
2162 menu "Executable file formats / Emulations"
2164 source "fs/Kconfig.binfmt"
2166 config IA32_EMULATION
2167 bool "IA32 Emulation"
2168 depends on X86_64
2169 select COMPAT_BINFMT_ELF
2170 ---help---
2171 Include code to run 32-bit programs under a 64-bit kernel. You should
2172 likely turn this on, unless you're 100% sure that you don't have any
2173 32-bit programs left.
2175 config IA32_AOUT
2176 tristate "IA32 a.out support"
2177 depends on IA32_EMULATION
2178 ---help---
2179 Support old a.out binaries in the 32bit emulation.
2181 config COMPAT
2182 def_bool y
2183 depends on IA32_EMULATION
2185 config COMPAT_FOR_U64_ALIGNMENT
2186 def_bool COMPAT
2187 depends on X86_64
2189 config SYSVIPC_COMPAT
2190 def_bool y
2191 depends on COMPAT && SYSVIPC
2193 config KEYS_COMPAT
2194 bool
2195 depends on COMPAT && KEYS
2196 default y
2198 endmenu
2201 config HAVE_ATOMIC_IOMAP
2202 def_bool y
2203 depends on X86_32
2205 config HAVE_TEXT_POKE_SMP
2206 bool
2207 select STOP_MACHINE if SMP
2209 source "net/Kconfig"
2211 source "drivers/Kconfig"
2213 source "drivers/firmware/Kconfig"
2215 source "fs/Kconfig"
2217 source "arch/x86/Kconfig.debug"
2219 source "security/Kconfig"
2221 source "crypto/Kconfig"
2223 source "arch/x86/kvm/Kconfig"
2225 source "lib/Kconfig"