| blob | 8d1fc0a6f6fa8eef34b4034ffa342d07506290c2 |
1 # x86 configuration
2 mainmenu "Linux Kernel Configuration for x86"
4 # Select 32 or 64 bit
5 config 64BIT
6 bool "64-bit kernel" if ARCH = "x86"
7 default ARCH = "x86_64"
8 help
9 Say yes to build a 64-bit kernel - formerly known as x86_64
10 Say no to build a 32-bit kernel - formerly known as i386
12 config X86_32
13 def_bool !64BIT
15 config X86_64
16 def_bool 64BIT
18 ### Arch settings
19 config X86
20 def_bool y
21 select HAVE_IDE
22 select HAVE_OPROFILE
23 select HAVE_KPROBES
24 <<<<<<< HEAD:arch/x86/Kconfig
25 select HAVE_KVM
26 =======
27 select HAVE_KRETPROBES
28 select HAVE_KVM if ((X86_32 && !X86_VOYAGER && !X86_VISWS && !X86_NUMAQ) || X86_64)
29 >>>>>>> 264e3e889d86e552b4191d69bb60f4f3b383135a:arch/x86/Kconfig
32 config GENERIC_LOCKBREAK
33 def_bool n
35 config GENERIC_TIME
36 def_bool y
38 config GENERIC_CMOS_UPDATE
39 def_bool y
41 config CLOCKSOURCE_WATCHDOG
42 def_bool y
44 config GENERIC_CLOCKEVENTS
45 def_bool y
47 config GENERIC_CLOCKEVENTS_BROADCAST
48 def_bool y
49 depends on X86_64 || (X86_32 && X86_LOCAL_APIC)
51 config LOCKDEP_SUPPORT
52 def_bool y
54 config STACKTRACE_SUPPORT
55 def_bool y
57 config HAVE_LATENCYTOP_SUPPORT
58 def_bool y
60 config SEMAPHORE_SLEEPERS
61 def_bool y
63 config FAST_CMPXCHG_LOCAL
64 bool
65 default y
67 config MMU
68 def_bool y
70 config ZONE_DMA
71 def_bool y
73 <<<<<<< HEAD:arch/x86/Kconfig
74 config QUICKLIST
75 def_bool X86_32
77 =======
78 >>>>>>> 264e3e889d86e552b4191d69bb60f4f3b383135a:arch/x86/Kconfig
79 config SBUS
80 bool
82 config GENERIC_ISA_DMA
83 def_bool y
85 config GENERIC_IOMAP
86 def_bool y
88 config GENERIC_BUG
89 def_bool y
90 depends on BUG
92 config GENERIC_HWEIGHT
93 def_bool y
95 config GENERIC_GPIO
96 def_bool n
98 config ARCH_MAY_HAVE_PC_FDC
99 def_bool y
101 config DMI
102 def_bool y
104 config RWSEM_GENERIC_SPINLOCK
105 def_bool !X86_XADD
107 config RWSEM_XCHGADD_ALGORITHM
108 def_bool X86_XADD
110 config ARCH_HAS_ILOG2_U32
111 def_bool n
113 config ARCH_HAS_ILOG2_U64
114 def_bool n
116 config ARCH_HAS_CPU_IDLE_WAIT
117 def_bool y
119 config GENERIC_CALIBRATE_DELAY
120 def_bool y
122 config GENERIC_TIME_VSYSCALL
123 bool
124 default X86_64
126 config ARCH_HAS_CPU_RELAX
127 def_bool y
129 config HAVE_SETUP_PER_CPU_AREA
130 def_bool X86_64
132 config ARCH_HIBERNATION_POSSIBLE
133 def_bool y
134 depends on !SMP || !X86_VOYAGER
136 config ARCH_SUSPEND_POSSIBLE
137 def_bool y
138 depends on !X86_VOYAGER
140 config ZONE_DMA32
141 bool
142 default X86_64
144 config ARCH_POPULATES_NODE_MAP
145 def_bool y
147 config AUDIT_ARCH
148 bool
149 default X86_64
151 config ARCH_SUPPORTS_AOUT
152 def_bool y
154 # Use the generic interrupt handling code in kernel/irq/:
155 config GENERIC_HARDIRQS
156 bool
157 default y
159 config GENERIC_IRQ_PROBE
160 bool
161 default y
163 config GENERIC_PENDING_IRQ
164 bool
165 depends on GENERIC_HARDIRQS && SMP
166 default y
168 config X86_SMP
169 bool
170 depends on SMP && ((X86_32 && !X86_VOYAGER) || X86_64)
171 default y
173 config X86_32_SMP
174 def_bool y
175 depends on X86_32 && SMP
177 config X86_64_SMP
178 def_bool y
179 depends on X86_64 && SMP
181 config X86_HT
182 bool
183 depends on SMP
184 depends on (X86_32 && !(X86_VISWS || X86_VOYAGER)) || (X86_64 && !MK8)
185 default y
187 config X86_BIOS_REBOOT
188 bool
189 depends on X86_32 && !(X86_VISWS || X86_VOYAGER)
190 default y
192 config X86_TRAMPOLINE
193 bool
194 depends on X86_SMP || (X86_VOYAGER && SMP)
195 default y
197 config KTIME_SCALAR
198 def_bool X86_32
199 source "init/Kconfig"
201 menu "Processor type and features"
203 source "kernel/time/Kconfig"
205 config SMP
206 bool "Symmetric multi-processing support"
207 ---help---
208 This enables support for systems with more than one CPU. If you have
209 a system with only one CPU, like most personal computers, say N. If
210 you have a system with more than one CPU, say Y.
212 If you say N here, the kernel will run on single and multiprocessor
213 machines, but will use only one CPU of a multiprocessor machine. If
214 you say Y here, the kernel will run on many, but not all,
215 singleprocessor machines. On a singleprocessor machine, the kernel
216 will run faster if you say N here.
218 Note that if you say Y here and choose architecture "586" or
219 "Pentium" under "Processor family", the kernel will not work on 486
220 architectures. Similarly, multiprocessor kernels for the "PPro"
221 architecture may not work on all Pentium based boards.
223 People using multiprocessor machines who say Y here should also say
224 Y to "Enhanced Real Time Clock Support", below. The "Advanced Power
225 Management" code will be disabled if you say Y here.
227 See also <file:Documentation/i386/IO-APIC.txt>,
228 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
229 <http://www.tldp.org/docs.html#howto>.
231 If you don't know what to do here, say N.
233 choice
234 prompt "Subarchitecture Type"
235 default X86_PC
237 config X86_PC
238 bool "PC-compatible"
239 help
240 Choose this option if your computer is a standard PC or compatible.
242 config X86_ELAN
243 bool "AMD Elan"
244 depends on X86_32
245 help
246 Select this for an AMD Elan processor.
248 Do not use this option for K6/Athlon/Opteron processors!
250 If unsure, choose "PC-compatible" instead.
252 config X86_VOYAGER
253 bool "Voyager (NCR)"
254 depends on X86_32
255 select SMP if !BROKEN
256 help
257 Voyager is an MCA-based 32-way capable SMP architecture proprietary
258 to NCR Corp. Machine classes 345x/35xx/4100/51xx are Voyager-based.
260 *** WARNING ***
262 If you do not specifically know you have a Voyager based machine,
263 say N here, otherwise the kernel you build will not be bootable.
265 config X86_NUMAQ
266 bool "NUMAQ (IBM/Sequent)"
267 select SMP
268 select NUMA
269 depends on X86_32
270 help
271 This option is used for getting Linux to run on a (IBM/Sequent) NUMA
272 multiquad box. This changes the way that processors are bootstrapped,
273 and uses Clustered Logical APIC addressing mode instead of Flat Logical.
274 You will need a new lynxer.elf file to flash your firmware with - send
275 email to <Martin.Bligh@us.ibm.com>.
277 config X86_SUMMIT
278 bool "Summit/EXA (IBM x440)"
279 depends on X86_32 && SMP
280 help
281 This option is needed for IBM systems that use the Summit/EXA chipset.
282 In particular, it is needed for the x440.
284 If you don't have one of these computers, you should say N here.
285 If you want to build a NUMA kernel, you must select ACPI.
287 config X86_BIGSMP
288 bool "Support for other sub-arch SMP systems with more than 8 CPUs"
289 depends on X86_32 && SMP
290 help
291 This option is needed for the systems that have more than 8 CPUs
292 and if the system is not of any sub-arch type above.
294 If you don't have such a system, you should say N here.
296 config X86_VISWS
297 bool "SGI 320/540 (Visual Workstation)"
298 depends on X86_32
299 help
300 The SGI Visual Workstation series is an IA32-based workstation
301 based on SGI systems chips with some legacy PC hardware attached.
303 Say Y here to create a kernel to run on the SGI 320 or 540.
305 A kernel compiled for the Visual Workstation will not run on PCs
306 and vice versa. See <file:Documentation/sgi-visws.txt> for details.
308 config X86_GENERICARCH
309 bool "Generic architecture (Summit, bigsmp, ES7000, default)"
310 depends on X86_32
311 help
312 This option compiles in the Summit, bigsmp, ES7000, default subarchitectures.
313 It is intended for a generic binary kernel.
314 If you want a NUMA kernel, select ACPI. We need SRAT for NUMA.
316 config X86_ES7000
317 bool "Support for Unisys ES7000 IA32 series"
318 depends on X86_32 && SMP
319 help
320 Support for Unisys ES7000 systems. Say 'Y' here if this kernel is
321 supposed to run on an IA32-based Unisys ES7000 system.
322 Only choose this option if you have such a system, otherwise you
323 should say N here.
325 config X86_RDC321X
326 bool "RDC R-321x SoC"
327 depends on X86_32
328 select M486
329 select X86_REBOOTFIXUPS
330 select GENERIC_GPIO
331 select LEDS_CLASS
332 select LEDS_GPIO
333 help
334 This option is needed for RDC R-321x system-on-chip, also known
335 as R-8610-(G).
336 If you don't have one of these chips, you should say N here.
338 config X86_VSMP
339 bool "Support for ScaleMP vSMP"
340 depends on X86_64 && PCI
341 help
342 Support for ScaleMP vSMP systems. Say 'Y' here if this kernel is
343 supposed to run on these EM64T-based machines. Only choose this option
344 if you have one of these machines.
346 endchoice
348 config SCHED_NO_NO_OMIT_FRAME_POINTER
349 def_bool y
350 prompt "Single-depth WCHAN output"
351 depends on X86_32
352 help
353 Calculate simpler /proc/<PID>/wchan values. If this option
354 is disabled then wchan values will recurse back to the
355 caller function. This provides more accurate wchan values,
356 at the expense of slightly more scheduling overhead.
358 If in doubt, say "Y".
360 menuconfig PARAVIRT_GUEST
361 bool "Paravirtualized guest support"
362 help
363 Say Y here to get to see options related to running Linux under
364 various hypervisors. This option alone does not add any kernel code.
366 If you say N, all options in this submenu will be skipped and disabled.
368 if PARAVIRT_GUEST
370 source "arch/x86/xen/Kconfig"
372 config VMI
373 bool "VMI Guest support"
374 select PARAVIRT
375 depends on X86_32
376 depends on !(X86_VISWS || X86_VOYAGER)
377 help
378 VMI provides a paravirtualized interface to the VMware ESX server
379 (it could be used by other hypervisors in theory too, but is not
380 at the moment), by linking the kernel to a GPL-ed ROM module
381 provided by the hypervisor.
383 source "arch/x86/lguest/Kconfig"
385 config PARAVIRT
386 bool "Enable paravirtualization code"
387 depends on !(X86_VISWS || X86_VOYAGER)
388 help
389 This changes the kernel so it can modify itself when it is run
390 under a hypervisor, potentially improving performance significantly
391 over full virtualization. However, when run without a hypervisor
392 the kernel is theoretically slower and slightly larger.
394 endif
396 config ACPI_SRAT
397 def_bool y
398 depends on X86_32 && ACPI && NUMA && (X86_SUMMIT || X86_GENERICARCH)
399 select ACPI_NUMA
401 config HAVE_ARCH_PARSE_SRAT
402 def_bool y
403 depends on ACPI_SRAT
405 config X86_SUMMIT_NUMA
406 def_bool y
407 depends on X86_32 && NUMA && (X86_SUMMIT || X86_GENERICARCH)
409 config X86_CYCLONE_TIMER
410 def_bool y
411 depends on X86_32 && X86_SUMMIT || X86_GENERICARCH
413 config ES7000_CLUSTERED_APIC
414 def_bool y
415 depends on SMP && X86_ES7000 && MPENTIUMIII
417 source "arch/x86/Kconfig.cpu"
419 config HPET_TIMER
420 def_bool X86_64
421 prompt "HPET Timer Support" if X86_32
422 help
423 Use the IA-PC HPET (High Precision Event Timer) to manage
424 time in preference to the PIT and RTC, if a HPET is
425 present.
426 HPET is the next generation timer replacing legacy 8254s.
427 The HPET provides a stable time base on SMP
428 systems, unlike the TSC, but it is more expensive to access,
429 as it is off-chip. You can find the HPET spec at
430 <http://www.intel.com/hardwaredesign/hpetspec.htm>.
432 You can safely choose Y here. However, HPET will only be
433 activated if the platform and the BIOS support this feature.
434 Otherwise the 8254 will be used for timing services.
436 Choose N to continue using the legacy 8254 timer.
438 config HPET_EMULATE_RTC
439 def_bool y
440 depends on HPET_TIMER && (RTC=y || RTC=m || RTC_DRV_CMOS=m || RTC_DRV_CMOS=y)
442 # Mark as embedded because too many people got it wrong.
443 # The code disables itself when not needed.
444 config GART_IOMMU
445 bool "GART IOMMU support" if EMBEDDED
446 default y
447 select SWIOTLB
448 select AGP
449 depends on X86_64 && PCI
450 help
451 Support for full DMA access of devices with 32bit memory access only
452 on systems with more than 3GB. This is usually needed for USB,
453 sound, many IDE/SATA chipsets and some other devices.
454 Provides a driver for the AMD Athlon64/Opteron/Turion/Sempron GART
455 based hardware IOMMU and a software bounce buffer based IOMMU used
456 on Intel systems and as fallback.
457 The code is only active when needed (enough memory and limited
458 device) unless CONFIG_IOMMU_DEBUG or iommu=force is specified
459 too.
461 config CALGARY_IOMMU
462 bool "IBM Calgary IOMMU support"
463 select SWIOTLB
464 depends on X86_64 && PCI && EXPERIMENTAL
465 help
466 Support for hardware IOMMUs in IBM's xSeries x366 and x460
467 systems. Needed to run systems with more than 3GB of memory
468 properly with 32-bit PCI devices that do not support DAC
469 (Double Address Cycle). Calgary also supports bus level
470 isolation, where all DMAs pass through the IOMMU. This
471 prevents them from going anywhere except their intended
472 destination. This catches hard-to-find kernel bugs and
473 mis-behaving drivers and devices that do not use the DMA-API
474 properly to set up their DMA buffers. The IOMMU can be
475 turned off at boot time with the iommu=off parameter.
476 Normally the kernel will make the right choice by itself.
477 If unsure, say Y.
479 config CALGARY_IOMMU_ENABLED_BY_DEFAULT
480 def_bool y
481 prompt "Should Calgary be enabled by default?"
482 depends on CALGARY_IOMMU
483 help
484 Should Calgary be enabled by default? if you choose 'y', Calgary
485 will be used (if it exists). If you choose 'n', Calgary will not be
486 used even if it exists. If you choose 'n' and would like to use
487 Calgary anyway, pass 'iommu=calgary' on the kernel command line.
488 If unsure, say Y.
490 config IOMMU_HELPER
491 def_bool (CALGARY_IOMMU || GART_IOMMU)
493 # need this always selected by IOMMU for the VIA workaround
494 config SWIOTLB
495 bool
496 help
497 Support for software bounce buffers used on x86-64 systems
498 which don't have a hardware IOMMU (e.g. the current generation
499 of Intel's x86-64 CPUs). Using this PCI devices which can only
500 access 32-bits of memory can be used on systems with more than
501 3 GB of memory. If unsure, say Y.
504 config NR_CPUS
505 int "Maximum number of CPUs (2-255)"
506 range 2 255
507 depends on SMP
508 default "32" if X86_NUMAQ || X86_SUMMIT || X86_BIGSMP || X86_ES7000
509 default "8"
510 help
511 This allows you to specify the maximum number of CPUs which this
512 kernel will support. The maximum supported value is 255 and the
513 minimum value which makes sense is 2.
515 This is purely to save memory - each supported CPU adds
516 approximately eight kilobytes to the kernel image.
518 config SCHED_SMT
519 bool "SMT (Hyperthreading) scheduler support"
520 depends on (X86_64 && SMP) || (X86_32 && X86_HT)
521 help
522 SMT scheduler support improves the CPU scheduler's decision making
523 when dealing with Intel Pentium 4 chips with HyperThreading at a
524 cost of slightly increased overhead in some places. If unsure say
525 N here.
527 config SCHED_MC
528 def_bool y
529 prompt "Multi-core scheduler support"
530 depends on (X86_64 && SMP) || (X86_32 && X86_HT)
531 help
532 Multi-core scheduler support improves the CPU scheduler's decision
533 making when dealing with multi-core CPU chips at a cost of slightly
534 increased overhead in some places. If unsure say N here.
536 source "kernel/Kconfig.preempt"
538 config X86_UP_APIC
539 bool "Local APIC support on uniprocessors"
540 depends on X86_32 && !SMP && !(X86_VISWS || X86_VOYAGER || X86_GENERICARCH)
541 help
542 A local APIC (Advanced Programmable Interrupt Controller) is an
543 integrated interrupt controller in the CPU. If you have a single-CPU
544 system which has a processor with a local APIC, you can say Y here to
545 enable and use it. If you say Y here even though your machine doesn't
546 have a local APIC, then the kernel will still run with no slowdown at
547 all. The local APIC supports CPU-generated self-interrupts (timer,
548 performance counters), and the NMI watchdog which detects hard
549 lockups.
551 config X86_UP_IOAPIC
552 bool "IO-APIC support on uniprocessors"
553 depends on X86_UP_APIC
554 help
555 An IO-APIC (I/O Advanced Programmable Interrupt Controller) is an
556 SMP-capable replacement for PC-style interrupt controllers. Most
557 SMP systems and many recent uniprocessor systems have one.
559 If you have a single-CPU system with an IO-APIC, you can say Y here
560 to use it. If you say Y here even though your machine doesn't have
561 an IO-APIC, then the kernel will still run with no slowdown at all.
563 config X86_LOCAL_APIC
564 def_bool y
565 depends on X86_64 || (X86_32 && (X86_UP_APIC || ((X86_VISWS || SMP) && !X86_VOYAGER) || X86_GENERICARCH))
567 config X86_IO_APIC
568 def_bool y
569 depends on X86_64 || (X86_32 && (X86_UP_IOAPIC || (SMP && !(X86_VISWS || X86_VOYAGER)) || X86_GENERICARCH))
571 config X86_VISWS_APIC
572 def_bool y
573 depends on X86_32 && X86_VISWS
575 config X86_MCE
576 bool "Machine Check Exception"
577 depends on !X86_VOYAGER
578 ---help---
579 Machine Check Exception support allows the processor to notify the
580 kernel if it detects a problem (e.g. overheating, component failure).
581 The action the kernel takes depends on the severity of the problem,
582 ranging from a warning message on the console, to halting the machine.
583 Your processor must be a Pentium or newer to support this - check the
584 flags in /proc/cpuinfo for mce. Note that some older Pentium systems
585 have a design flaw which leads to false MCE events - hence MCE is
586 disabled on all P5 processors, unless explicitly enabled with "mce"
587 as a boot argument. Similarly, if MCE is built in and creates a
588 problem on some new non-standard machine, you can boot with "nomce"
589 to disable it. MCE support simply ignores non-MCE processors like
590 the 386 and 486, so nearly everyone can say Y here.
592 config X86_MCE_INTEL
593 def_bool y
594 prompt "Intel MCE features"
595 depends on X86_64 && X86_MCE && X86_LOCAL_APIC
596 help
597 Additional support for intel specific MCE features such as
598 the thermal monitor.
600 config X86_MCE_AMD
601 def_bool y
602 prompt "AMD MCE features"
603 depends on X86_64 && X86_MCE && X86_LOCAL_APIC
604 help
605 Additional support for AMD specific MCE features such as
606 the DRAM Error Threshold.
608 config X86_MCE_NONFATAL
609 tristate "Check for non-fatal errors on AMD Athlon/Duron / Intel Pentium 4"
610 depends on X86_32 && X86_MCE
611 help
612 Enabling this feature starts a timer that triggers every 5 seconds which
613 will look at the machine check registers to see if anything happened.
614 Non-fatal problems automatically get corrected (but still logged).
615 Disable this if you don't want to see these messages.
616 Seeing the messages this option prints out may be indicative of dying
617 or out-of-spec (ie, overclocked) hardware.
618 This option only does something on certain CPUs.
619 (AMD Athlon/Duron and Intel Pentium 4)
621 config X86_MCE_P4THERMAL
622 bool "check for P4 thermal throttling interrupt."
623 depends on X86_32 && X86_MCE && (X86_UP_APIC || SMP) && !X86_VISWS
624 help
625 Enabling this feature will cause a message to be printed when the P4
626 enters thermal throttling.
628 config VM86
629 bool "Enable VM86 support" if EMBEDDED
630 default y
631 depends on X86_32
632 help
633 This option is required by programs like DOSEMU to run 16-bit legacy
634 code on X86 processors. It also may be needed by software like
635 XFree86 to initialize some video cards via BIOS. Disabling this
636 option saves about 6k.
638 config TOSHIBA
639 tristate "Toshiba Laptop support"
640 depends on X86_32
641 ---help---
642 This adds a driver to safely access the System Management Mode of
643 the CPU on Toshiba portables with a genuine Toshiba BIOS. It does
644 not work on models with a Phoenix BIOS. The System Management Mode
645 is used to set the BIOS and power saving options on Toshiba portables.
647 For information on utilities to make use of this driver see the
648 Toshiba Linux utilities web site at:
649 <http://www.buzzard.org.uk/toshiba/>.
651 Say Y if you intend to run this kernel on a Toshiba portable.
652 Say N otherwise.
654 config I8K
655 tristate "Dell laptop support"
656 ---help---
657 This adds a driver to safely access the System Management Mode
658 of the CPU on the Dell Inspiron 8000. The System Management Mode
659 is used to read cpu temperature and cooling fan status and to
660 control the fans on the I8K portables.
662 This driver has been tested only on the Inspiron 8000 but it may
663 also work with other Dell laptops. You can force loading on other
664 models by passing the parameter `force=1' to the module. Use at
665 your own risk.
667 For information on utilities to make use of this driver see the
668 I8K Linux utilities web site at:
669 <http://people.debian.org/~dz/i8k/>
671 Say Y if you intend to run this kernel on a Dell Inspiron 8000.
672 Say N otherwise.
674 config X86_REBOOTFIXUPS
675 def_bool n
676 prompt "Enable X86 board specific fixups for reboot"
677 depends on X86_32 && X86
678 ---help---
679 This enables chipset and/or board specific fixups to be done
680 in order to get reboot to work correctly. This is only needed on
681 some combinations of hardware and BIOS. The symptom, for which
682 this config is intended, is when reboot ends with a stalled/hung
683 system.
685 Currently, the only fixup is for the Geode machines using
686 CS5530A and CS5536 chipsets and the RDC R-321x SoC.
688 Say Y if you want to enable the fixup. Currently, it's safe to
689 enable this option even if you don't need it.
690 Say N otherwise.
692 config MICROCODE
693 tristate "/dev/cpu/microcode - Intel IA32 CPU microcode support"
694 select FW_LOADER
695 ---help---
696 If you say Y here, you will be able to update the microcode on
697 Intel processors in the IA32 family, e.g. Pentium Pro, Pentium II,
698 Pentium III, Pentium 4, Xeon etc. You will obviously need the
699 actual microcode binary data itself which is not shipped with the
700 Linux kernel.
702 For latest news and information on obtaining all the required
703 ingredients for this driver, check:
704 <http://www.urbanmyth.org/microcode/>.
706 To compile this driver as a module, choose M here: the
707 module will be called microcode.
709 config MICROCODE_OLD_INTERFACE
710 def_bool y
711 depends on MICROCODE
713 config X86_MSR
714 tristate "/dev/cpu/*/msr - Model-specific register support"
715 help
716 This device gives privileged processes access to the x86
717 Model-Specific Registers (MSRs). It is a character device with
718 major 202 and minors 0 to 31 for /dev/cpu/0/msr to /dev/cpu/31/msr.
719 MSR accesses are directed to a specific CPU on multi-processor
720 systems.
722 config X86_CPUID
723 tristate "/dev/cpu/*/cpuid - CPU information support"
724 help
725 This device gives processes access to the x86 CPUID instruction to
726 be executed on a specific processor. It is a character device
727 with major 203 and minors 0 to 31 for /dev/cpu/0/cpuid to
728 /dev/cpu/31/cpuid.
730 choice
731 prompt "High Memory Support"
732 default HIGHMEM4G if !X86_NUMAQ
733 default HIGHMEM64G if X86_NUMAQ
734 depends on X86_32
736 config NOHIGHMEM
737 bool "off"
738 depends on !X86_NUMAQ
739 ---help---
740 Linux can use up to 64 Gigabytes of physical memory on x86 systems.
741 However, the address space of 32-bit x86 processors is only 4
742 Gigabytes large. That means that, if you have a large amount of
743 physical memory, not all of it can be "permanently mapped" by the
744 kernel. The physical memory that's not permanently mapped is called
745 "high memory".
747 If you are compiling a kernel which will never run on a machine with
748 more than 1 Gigabyte total physical RAM, answer "off" here (default
749 choice and suitable for most users). This will result in a "3GB/1GB"
750 split: 3GB are mapped so that each process sees a 3GB virtual memory
751 space and the remaining part of the 4GB virtual memory space is used
752 by the kernel to permanently map as much physical memory as
753 possible.
755 If the machine has between 1 and 4 Gigabytes physical RAM, then
756 answer "4GB" here.
758 If more than 4 Gigabytes is used then answer "64GB" here. This
759 selection turns Intel PAE (Physical Address Extension) mode on.
760 PAE implements 3-level paging on IA32 processors. PAE is fully
761 supported by Linux, PAE mode is implemented on all recent Intel
762 processors (Pentium Pro and better). NOTE: If you say "64GB" here,
763 then the kernel will not boot on CPUs that don't support PAE!
765 The actual amount of total physical memory will either be
766 auto detected or can be forced by using a kernel command line option
767 such as "mem=256M". (Try "man bootparam" or see the documentation of
768 your boot loader (lilo or loadlin) about how to pass options to the
769 kernel at boot time.)
771 If unsure, say "off".
773 config HIGHMEM4G
774 bool "4GB"
775 depends on !X86_NUMAQ
776 help
777 Select this if you have a 32-bit processor and between 1 and 4
778 gigabytes of physical RAM.
780 config HIGHMEM64G
781 bool "64GB"
782 depends on !M386 && !M486
783 select X86_PAE
784 help
785 Select this if you have a 32-bit processor and more than 4
786 gigabytes of physical RAM.
788 endchoice
790 choice
791 depends on EXPERIMENTAL
792 prompt "Memory split" if EMBEDDED
793 default VMSPLIT_3G
794 depends on X86_32
795 help
796 Select the desired split between kernel and user memory.
798 If the address range available to the kernel is less than the
799 physical memory installed, the remaining memory will be available
800 as "high memory". Accessing high memory is a little more costly
801 than low memory, as it needs to be mapped into the kernel first.
802 Note that increasing the kernel address space limits the range
803 available to user programs, making the address space there
804 tighter. Selecting anything other than the default 3G/1G split
805 will also likely make your kernel incompatible with binary-only
806 kernel modules.
808 If you are not absolutely sure what you are doing, leave this
809 option alone!
811 config VMSPLIT_3G
812 bool "3G/1G user/kernel split"
813 config VMSPLIT_3G_OPT
814 depends on !X86_PAE
815 bool "3G/1G user/kernel split (for full 1G low memory)"
816 config VMSPLIT_2G
817 bool "2G/2G user/kernel split"
818 config VMSPLIT_2G_OPT
819 depends on !X86_PAE
820 bool "2G/2G user/kernel split (for full 2G low memory)"
821 config VMSPLIT_1G
822 bool "1G/3G user/kernel split"
823 endchoice
825 config PAGE_OFFSET
826 hex
827 default 0xB0000000 if VMSPLIT_3G_OPT
828 default 0x80000000 if VMSPLIT_2G
829 default 0x78000000 if VMSPLIT_2G_OPT
830 default 0x40000000 if VMSPLIT_1G
831 default 0xC0000000
832 depends on X86_32
834 config HIGHMEM
835 def_bool y
836 depends on X86_32 && (HIGHMEM64G || HIGHMEM4G)
838 config X86_PAE
839 def_bool n
840 prompt "PAE (Physical Address Extension) Support"
841 depends on X86_32 && !HIGHMEM4G
842 select RESOURCES_64BIT
843 help
844 PAE is required for NX support, and furthermore enables
845 larger swapspace support for non-overcommit purposes. It
846 has the cost of more pagetable lookup overhead, and also
847 consumes more pagetable space per process.
849 # Common NUMA Features
850 config NUMA
851 bool "Numa Memory Allocation and Scheduler Support (EXPERIMENTAL)"
852 depends on SMP
853 depends on X86_64 || (X86_32 && HIGHMEM64G && (X86_NUMAQ || (X86_SUMMIT || X86_GENERICARCH) && ACPI) && EXPERIMENTAL)
854 default n if X86_PC
855 default y if (X86_NUMAQ || X86_SUMMIT)
856 help
857 Enable NUMA (Non Uniform Memory Access) support.
858 The kernel will try to allocate memory used by a CPU on the
859 local memory controller of the CPU and add some more
860 NUMA awareness to the kernel.
862 For i386 this is currently highly experimental and should be only
863 used for kernel development. It might also cause boot failures.
864 For x86_64 this is recommended on all multiprocessor Opteron systems.
865 If the system is EM64T, you should say N unless your system is
866 EM64T NUMA.
868 comment "NUMA (Summit) requires SMP, 64GB highmem support, ACPI"
869 depends on X86_32 && X86_SUMMIT && (!HIGHMEM64G || !ACPI)
871 config K8_NUMA
872 def_bool y
873 prompt "Old style AMD Opteron NUMA detection"
874 depends on X86_64 && NUMA && PCI
875 help
876 Enable K8 NUMA node topology detection. You should say Y here if
877 you have a multi processor AMD K8 system. This uses an old
878 method to read the NUMA configuration directly from the builtin
879 Northbridge of Opteron. It is recommended to use X86_64_ACPI_NUMA
880 instead, which also takes priority if both are compiled in.
882 config X86_64_ACPI_NUMA
883 def_bool y
884 prompt "ACPI NUMA detection"
885 depends on X86_64 && NUMA && ACPI && PCI
886 select ACPI_NUMA
887 help
888 Enable ACPI SRAT based node topology detection.
890 config NUMA_EMU
891 bool "NUMA emulation"
892 depends on X86_64 && NUMA
893 help
894 Enable NUMA emulation. A flat machine will be split
895 into virtual nodes when booted with "numa=fake=N", where N is the
896 number of nodes. This is only useful for debugging.
898 config NODES_SHIFT
899 int
900 range 1 15 if X86_64
901 default "6" if X86_64
902 default "4" if X86_NUMAQ
903 default "3"
904 depends on NEED_MULTIPLE_NODES
906 config HAVE_ARCH_BOOTMEM_NODE
907 def_bool y
908 depends on X86_32 && NUMA
910 config ARCH_HAVE_MEMORY_PRESENT
911 def_bool y
912 depends on X86_32 && DISCONTIGMEM
914 config NEED_NODE_MEMMAP_SIZE
915 def_bool y
916 depends on X86_32 && (DISCONTIGMEM || SPARSEMEM)
918 config HAVE_ARCH_ALLOC_REMAP
919 def_bool y
920 depends on X86_32 && NUMA
922 config ARCH_FLATMEM_ENABLE
923 def_bool y
924 depends on X86_32 && ARCH_SELECT_MEMORY_MODEL && X86_PC && !NUMA
926 config ARCH_DISCONTIGMEM_ENABLE
927 def_bool y
928 depends on NUMA && X86_32
930 config ARCH_DISCONTIGMEM_DEFAULT
931 def_bool y
932 depends on NUMA && X86_32
934 config ARCH_SPARSEMEM_DEFAULT
935 def_bool y
936 depends on X86_64
938 config ARCH_SPARSEMEM_ENABLE
939 def_bool y
940 depends on X86_64 || NUMA || (EXPERIMENTAL && X86_PC)
941 select SPARSEMEM_STATIC if X86_32
942 select SPARSEMEM_VMEMMAP_ENABLE if X86_64
944 config ARCH_SELECT_MEMORY_MODEL
945 def_bool y
946 depends on ARCH_SPARSEMEM_ENABLE
948 config ARCH_MEMORY_PROBE
949 def_bool X86_64
950 depends on MEMORY_HOTPLUG
952 source "mm/Kconfig"
954 config HIGHPTE
955 bool "Allocate 3rd-level pagetables from highmem"
956 depends on X86_32 && (HIGHMEM4G || HIGHMEM64G)
957 help
958 The VM uses one page table entry for each page of physical memory.
959 For systems with a lot of RAM, this can be wasteful of precious
960 low memory. Setting this option will put user-space page table
961 entries in high memory.
963 config MATH_EMULATION
964 bool
965 prompt "Math emulation" if X86_32
966 ---help---
967 Linux can emulate a math coprocessor (used for floating point
968 operations) if you don't have one. 486DX and Pentium processors have
969 a math coprocessor built in, 486SX and 386 do not, unless you added
970 a 487DX or 387, respectively. (The messages during boot time can
971 give you some hints here ["man dmesg"].) Everyone needs either a
972 coprocessor or this emulation.
974 If you don't have a math coprocessor, you need to say Y here; if you
975 say Y here even though you have a coprocessor, the coprocessor will
976 be used nevertheless. (This behavior can be changed with the kernel
977 command line option "no387", which comes handy if your coprocessor
978 is broken. Try "man bootparam" or see the documentation of your boot
979 loader (lilo or loadlin) about how to pass options to the kernel at
980 boot time.) This means that it is a good idea to say Y here if you
981 intend to use this kernel on different machines.
983 More information about the internals of the Linux math coprocessor
984 emulation can be found in <file:arch/x86/math-emu/README>.
986 If you are not sure, say Y; apart from resulting in a 66 KB bigger
987 kernel, it won't hurt.
989 config MTRR
990 bool "MTRR (Memory Type Range Register) support"
991 ---help---
992 On Intel P6 family processors (Pentium Pro, Pentium II and later)
993 the Memory Type Range Registers (MTRRs) may be used to control
994 processor access to memory ranges. This is most useful if you have
995 a video (VGA) card on a PCI or AGP bus. Enabling write-combining
996 allows bus write transfers to be combined into a larger transfer
997 before bursting over the PCI/AGP bus. This can increase performance
998 of image write operations 2.5 times or more. Saying Y here creates a
999 /proc/mtrr file which may be used to manipulate your processor's
1000 MTRRs. Typically the X server should use this.
1002 This code has a reasonably generic interface so that similar
1003 control registers on other processors can be easily supported
1004 as well:
1006 The Cyrix 6x86, 6x86MX and M II processors have Address Range
1007 Registers (ARRs) which provide a similar functionality to MTRRs. For
1008 these, the ARRs are used to emulate the MTRRs.
1009 The AMD K6-2 (stepping 8 and above) and K6-3 processors have two
1010 MTRRs. The Centaur C6 (WinChip) has 8 MCRs, allowing
1011 write-combining. All of these processors are supported by this code
1012 and it makes sense to say Y here if you have one of them.
1014 Saying Y here also fixes a problem with buggy SMP BIOSes which only
1015 set the MTRRs for the boot CPU and not for the secondary CPUs. This
1016 can lead to all sorts of problems, so it's good to say Y here.
1018 You can safely say Y even if your machine doesn't have MTRRs, you'll
1019 just add about 9 KB to your kernel.
1021 See <file:Documentation/mtrr.txt> for more information.
1023 config EFI
1024 def_bool n
1025 prompt "EFI runtime service support"
1026 depends on ACPI
1027 ---help---
1028 This enables the kernel to use EFI runtime services that are
1029 available (such as the EFI variable services).
1031 This option is only useful on systems that have EFI firmware.
1032 In addition, you should use the latest ELILO loader available
1033 at <http://elilo.sourceforge.net> in order to take advantage
1034 of EFI runtime services. However, even with this option, the
1035 resultant kernel should continue to boot on existing non-EFI
1036 platforms.
1038 config IRQBALANCE
1039 def_bool y
1040 prompt "Enable kernel irq balancing"
1041 depends on X86_32 && SMP && X86_IO_APIC
1042 help
1043 The default yes will allow the kernel to do irq load balancing.
1044 Saying no will keep the kernel from doing irq load balancing.
1046 config SECCOMP
1047 def_bool y
1048 prompt "Enable seccomp to safely compute untrusted bytecode"
1049 depends on PROC_FS
1050 help
1051 This kernel feature is useful for number crunching applications
1052 that may need to compute untrusted bytecode during their
1053 execution. By using pipes or other transports made available to
1054 the process as file descriptors supporting the read/write
1055 syscalls, it's possible to isolate those applications in
1056 their own address space using seccomp. Once seccomp is
1057 enabled via /proc/<pid>/seccomp, it cannot be disabled
1058 and the task is only allowed to execute a few safe syscalls
1059 defined by each seccomp mode.
1061 If unsure, say Y. Only embedded should say N here.
1063 config CC_STACKPROTECTOR
1064 bool "Enable -fstack-protector buffer overflow detection (EXPERIMENTAL)"
1065 <<<<<<< HEAD:arch/x86/Kconfig
1066 depends on X86_64 && EXPERIMENTAL
1067 =======
1068 depends on X86_64 && EXPERIMENTAL && BROKEN
1069 >>>>>>> 264e3e889d86e552b4191d69bb60f4f3b383135a:arch/x86/Kconfig
1070 help
1071 This option turns on the -fstack-protector GCC feature. This
1072 feature puts, at the beginning of critical functions, a canary
1073 value on the stack just before the return address, and validates
1074 the value just before actually returning. Stack based buffer
1075 overflows (that need to overwrite this return address) now also
1076 overwrite the canary, which gets detected and the attack is then
1077 neutralized via a kernel panic.
1079 This feature requires gcc version 4.2 or above, or a distribution
1080 gcc with the feature backported. Older versions are automatically
1081 detected and for those versions, this configuration option is ignored.
1083 config CC_STACKPROTECTOR_ALL
1084 bool "Use stack-protector for all functions"
1085 depends on CC_STACKPROTECTOR
1086 help
1087 Normally, GCC only inserts the canary value protection for
1088 functions that use large-ish on-stack buffers. By enabling
1089 this option, GCC will be asked to do this for ALL functions.
1091 source kernel/Kconfig.hz
1093 config KEXEC
1094 bool "kexec system call"
1095 help
1096 kexec is a system call that implements the ability to shutdown your
1097 current kernel, and to start another kernel. It is like a reboot
1098 but it is independent of the system firmware. And like a reboot
1099 you can start any kernel with it, not just Linux.
1101 The name comes from the similarity to the exec system call.
1103 It is an ongoing process to be certain the hardware in a machine
1104 is properly shutdown, so do not be surprised if this code does not
1105 initially work for you. It may help to enable device hotplugging
1106 support. As of this writing the exact hardware interface is
1107 strongly in flux, so no good recommendation can be made.
1109 config CRASH_DUMP
1110 bool "kernel crash dumps (EXPERIMENTAL)"
1111 depends on EXPERIMENTAL
1112 depends on X86_64 || (X86_32 && HIGHMEM)
1113 help
1114 Generate crash dump after being started by kexec.
1115 This should be normally only set in special crash dump kernels
1116 which are loaded in the main kernel with kexec-tools into
1117 a specially reserved region and then later executed after
1118 a crash by kdump/kexec. The crash dump kernel must be compiled
1119 to a memory address not used by the main kernel or BIOS using
1120 PHYSICAL_START, or it must be built as a relocatable image
1121 (CONFIG_RELOCATABLE=y).
1122 For more details see Documentation/kdump/kdump.txt
1124 config PHYSICAL_START
1125 hex "Physical address where the kernel is loaded" if (EMBEDDED || CRASH_DUMP)
1126 default "0x1000000" if X86_NUMAQ
1127 default "0x200000" if X86_64
1128 default "0x100000"
1129 help
1130 This gives the physical address where the kernel is loaded.
1132 If kernel is a not relocatable (CONFIG_RELOCATABLE=n) then
1133 bzImage will decompress itself to above physical address and
1134 run from there. Otherwise, bzImage will run from the address where
1135 it has been loaded by the boot loader and will ignore above physical
1136 address.
1138 In normal kdump cases one does not have to set/change this option
1139 as now bzImage can be compiled as a completely relocatable image
1140 (CONFIG_RELOCATABLE=y) and be used to load and run from a different
1141 address. This option is mainly useful for the folks who don't want
1142 to use a bzImage for capturing the crash dump and want to use a
1143 vmlinux instead. vmlinux is not relocatable hence a kernel needs
1144 to be specifically compiled to run from a specific memory area
1145 (normally a reserved region) and this option comes handy.
1147 So if you are using bzImage for capturing the crash dump, leave
1148 the value here unchanged to 0x100000 and set CONFIG_RELOCATABLE=y.
1149 Otherwise if you plan to use vmlinux for capturing the crash dump
1150 change this value to start of the reserved region (Typically 16MB
1151 0x1000000). In other words, it can be set based on the "X" value as
1152 specified in the "crashkernel=YM@XM" command line boot parameter
1153 passed to the panic-ed kernel. Typically this parameter is set as
1154 crashkernel=64M@16M. Please take a look at
1155 Documentation/kdump/kdump.txt for more details about crash dumps.
1157 Usage of bzImage for capturing the crash dump is recommended as
1158 one does not have to build two kernels. Same kernel can be used
1159 as production kernel and capture kernel. Above option should have
1160 gone away after relocatable bzImage support is introduced. But it
1161 is present because there are users out there who continue to use
1162 vmlinux for dump capture. This option should go away down the
1163 line.
1165 Don't change this unless you know what you are doing.
1167 config RELOCATABLE
1168 bool "Build a relocatable kernel (EXPERIMENTAL)"
1169 depends on EXPERIMENTAL
1170 help
1171 This builds a kernel image that retains relocation information
1172 so it can be loaded someplace besides the default 1MB.
1173 The relocations tend to make the kernel binary about 10% larger,
1174 but are discarded at runtime.
1176 One use is for the kexec on panic case where the recovery kernel
1177 must live at a different physical address than the primary
1178 kernel.
1180 Note: If CONFIG_RELOCATABLE=y, then the kernel runs from the address
1181 it has been loaded at and the compile time physical address
1182 (CONFIG_PHYSICAL_START) is ignored.
1184 config PHYSICAL_ALIGN
1185 hex
1186 prompt "Alignment value to which kernel should be aligned" if X86_32
1187 default "0x100000" if X86_32
1188 default "0x200000" if X86_64
1189 range 0x2000 0x400000
1190 help
1191 This value puts the alignment restrictions on physical address
1192 where kernel is loaded and run from. Kernel is compiled for an
1193 address which meets above alignment restriction.
1195 If bootloader loads the kernel at a non-aligned address and
1196 CONFIG_RELOCATABLE is set, kernel will move itself to nearest
1197 address aligned to above value and run from there.
1199 If bootloader loads the kernel at a non-aligned address and
1200 CONFIG_RELOCATABLE is not set, kernel will ignore the run time
1201 load address and decompress itself to the address it has been
1202 compiled for and run from there. The address for which kernel is
1203 compiled already meets above alignment restrictions. Hence the
1204 end result is that kernel runs from a physical address meeting
1205 above alignment restrictions.
1207 Don't change this unless you know what you are doing.
1209 config HOTPLUG_CPU
1210 bool "Support for suspend on SMP and hot-pluggable CPUs (EXPERIMENTAL)"
1211 depends on SMP && HOTPLUG && EXPERIMENTAL && !X86_VOYAGER
1212 ---help---
1213 Say Y here to experiment with turning CPUs off and on, and to
1214 enable suspend on SMP systems. CPUs can be controlled through
1215 /sys/devices/system/cpu.
1216 Say N if you want to disable CPU hotplug and don't need to
1217 suspend.
1219 config COMPAT_VDSO
1220 def_bool y
1221 prompt "Compat VDSO support"
1222 depends on X86_32 || IA32_EMULATION
1223 help
1224 Map the 32-bit VDSO to the predictable old-style address too.
1225 ---help---
1226 Say N here if you are running a sufficiently recent glibc
1227 version (2.3.3 or later), to remove the high-mapped
1228 VDSO mapping and to exclusively use the randomized VDSO.
1230 If unsure, say Y.
1232 endmenu
1234 config ARCH_ENABLE_MEMORY_HOTPLUG
1235 def_bool y
1236 depends on X86_64 || (X86_32 && HIGHMEM)
1238 config HAVE_ARCH_EARLY_PFN_TO_NID
1239 def_bool X86_64
1240 depends on NUMA
1242 menu "Power management options"
1243 depends on !X86_VOYAGER
1245 config ARCH_HIBERNATION_HEADER
1246 def_bool y
1247 depends on X86_64 && HIBERNATION
1249 source "kernel/power/Kconfig"
1251 source "drivers/acpi/Kconfig"
1253 config X86_APM_BOOT
1254 bool
1255 default y
1256 depends on APM || APM_MODULE
1258 menuconfig APM
1259 tristate "APM (Advanced Power Management) BIOS support"
1260 depends on X86_32 && PM_SLEEP && !X86_VISWS
1261 ---help---
1262 APM is a BIOS specification for saving power using several different
1263 techniques. This is mostly useful for battery powered laptops with
1264 APM compliant BIOSes. If you say Y here, the system time will be
1265 reset after a RESUME operation, the /proc/apm device will provide
1266 battery status information, and user-space programs will receive
1267 notification of APM "events" (e.g. battery status change).
1269 If you select "Y" here, you can disable actual use of the APM
1270 BIOS by passing the "apm=off" option to the kernel at boot time.
1272 Note that the APM support is almost completely disabled for
1273 machines with more than one CPU.
1275 In order to use APM, you will need supporting software. For location
1276 <<<<<<< HEAD:arch/x86/Kconfig
1277 and more information, read <file:Documentation/pm.txt> and the
1278 =======
1279 and more information, read <file:Documentation/power/pm.txt> and the
1280 >>>>>>> 264e3e889d86e552b4191d69bb60f4f3b383135a:arch/x86/Kconfig
1281 Battery Powered Linux mini-HOWTO, available from
1282 <http://www.tldp.org/docs.html#howto>.
1284 This driver does not spin down disk drives (see the hdparm(8)
1285 manpage ("man 8 hdparm") for that), and it doesn't turn off
1286 VESA-compliant "green" monitors.
1288 This driver does not support the TI 4000M TravelMate and the ACER
1289 486/DX4/75 because they don't have compliant BIOSes. Many "green"
1290 desktop machines also don't have compliant BIOSes, and this driver
1291 may cause those machines to panic during the boot phase.
1293 Generally, if you don't have a battery in your machine, there isn't
1294 much point in using this driver and you should say N. If you get
1295 random kernel OOPSes or reboots that don't seem to be related to
1296 anything, try disabling/enabling this option (or disabling/enabling
1297 APM in your BIOS).
1299 Some other things you should try when experiencing seemingly random,
1300 "weird" problems:
1302 1) make sure that you have enough swap space and that it is
1303 enabled.
1304 2) pass the "no-hlt" option to the kernel
1305 3) switch on floating point emulation in the kernel and pass
1306 the "no387" option to the kernel
1307 4) pass the "floppy=nodma" option to the kernel
1308 5) pass the "mem=4M" option to the kernel (thereby disabling
1309 all but the first 4 MB of RAM)
1310 6) make sure that the CPU is not over clocked.
1311 7) read the sig11 FAQ at <http://www.bitwizard.nl/sig11/>
1312 8) disable the cache from your BIOS settings
1313 9) install a fan for the video card or exchange video RAM
1314 10) install a better fan for the CPU
1315 11) exchange RAM chips
1316 12) exchange the motherboard.
1318 To compile this driver as a module, choose M here: the
1319 module will be called apm.
1321 if APM
1323 config APM_IGNORE_USER_SUSPEND
1324 bool "Ignore USER SUSPEND"
1325 help
1326 This option will ignore USER SUSPEND requests. On machines with a
1327 compliant APM BIOS, you want to say N. However, on the NEC Versa M
1328 series notebooks, it is necessary to say Y because of a BIOS bug.
1330 config APM_DO_ENABLE
1331 bool "Enable PM at boot time"
1332 ---help---
1333 Enable APM features at boot time. From page 36 of the APM BIOS
1334 specification: "When disabled, the APM BIOS does not automatically
1335 power manage devices, enter the Standby State, enter the Suspend
1336 State, or take power saving steps in response to CPU Idle calls."
1337 This driver will make CPU Idle calls when Linux is idle (unless this
1338 feature is turned off -- see "Do CPU IDLE calls", below). This
1339 should always save battery power, but more complicated APM features
1340 will be dependent on your BIOS implementation. You may need to turn
1341 this option off if your computer hangs at boot time when using APM
1342 support, or if it beeps continuously instead of suspending. Turn
1343 this off if you have a NEC UltraLite Versa 33/C or a Toshiba
1344 T400CDT. This is off by default since most machines do fine without
1345 this feature.
1347 config APM_CPU_IDLE
1348 bool "Make CPU Idle calls when idle"
1349 help
1350 Enable calls to APM CPU Idle/CPU Busy inside the kernel's idle loop.
1351 On some machines, this can activate improved power savings, such as
1352 a slowed CPU clock rate, when the machine is idle. These idle calls
1353 are made after the idle loop has run for some length of time (e.g.,
1354 333 mS). On some machines, this will cause a hang at boot time or
1355 whenever the CPU becomes idle. (On machines with more than one CPU,
1356 this option does nothing.)
1358 config APM_DISPLAY_BLANK
1359 bool "Enable console blanking using APM"
1360 help
1361 Enable console blanking using the APM. Some laptops can use this to
1362 turn off the LCD backlight when the screen blanker of the Linux
1363 virtual console blanks the screen. Note that this is only used by
1364 the virtual console screen blanker, and won't turn off the backlight
1365 when using the X Window system. This also doesn't have anything to
1366 do with your VESA-compliant power-saving monitor. Further, this
1367 option doesn't work for all laptops -- it might not turn off your
1368 backlight at all, or it might print a lot of errors to the console,
1369 especially if you are using gpm.
1371 config APM_ALLOW_INTS
1372 bool "Allow interrupts during APM BIOS calls"
1373 help
1374 Normally we disable external interrupts while we are making calls to
1375 the APM BIOS as a measure to lessen the effects of a badly behaving
1376 BIOS implementation. The BIOS should reenable interrupts if it
1377 needs to. Unfortunately, some BIOSes do not -- especially those in
1378 many of the newer IBM Thinkpads. If you experience hangs when you
1379 suspend, try setting this to Y. Otherwise, say N.
1381 config APM_REAL_MODE_POWER_OFF
1382 bool "Use real mode APM BIOS call to power off"
1383 help
1384 Use real mode APM BIOS calls to switch off the computer. This is
1385 a work-around for a number of buggy BIOSes. Switch this option on if
1386 your computer crashes instead of powering off properly.
1388 endif # APM
1390 source "arch/x86/kernel/cpu/cpufreq/Kconfig"
1392 source "drivers/cpuidle/Kconfig"
1394 endmenu
1397 menu "Bus options (PCI etc.)"
1399 config PCI
1400 bool "PCI support" if !X86_VISWS
1401 depends on !X86_VOYAGER
1402 default y
1403 select ARCH_SUPPORTS_MSI if (X86_LOCAL_APIC && X86_IO_APIC)
1404 help
1405 Find out whether you have a PCI motherboard. PCI is the name of a
1406 bus system, i.e. the way the CPU talks to the other stuff inside
1407 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
1408 VESA. If you have PCI, say Y, otherwise N.
1410 choice
1411 prompt "PCI access mode"
1412 depends on X86_32 && PCI && !X86_VISWS
1413 default PCI_GOANY
1414 ---help---
1415 On PCI systems, the BIOS can be used to detect the PCI devices and
1416 determine their configuration. However, some old PCI motherboards
1417 have BIOS bugs and may crash if this is done. Also, some embedded
1418 PCI-based systems don't have any BIOS at all. Linux can also try to
1419 detect the PCI hardware directly without using the BIOS.
1421 With this option, you can specify how Linux should detect the
1422 PCI devices. If you choose "BIOS", the BIOS will be used,
1423 if you choose "Direct", the BIOS won't be used, and if you
1424 choose "MMConfig", then PCI Express MMCONFIG will be used.
1425 If you choose "Any", the kernel will try MMCONFIG, then the
1426 direct access method and falls back to the BIOS if that doesn't
1427 work. If unsure, go with the default, which is "Any".
1429 config PCI_GOBIOS
1430 bool "BIOS"
1432 config PCI_GOMMCONFIG
1433 bool "MMConfig"
1435 config PCI_GODIRECT
1436 bool "Direct"
1438 config PCI_GOANY
1439 bool "Any"
1441 endchoice
1443 config PCI_BIOS
1444 def_bool y
1445 depends on X86_32 && !X86_VISWS && PCI && (PCI_GOBIOS || PCI_GOANY)
1447 # x86-64 doesn't support PCI BIOS access from long mode so always go direct.
1448 config PCI_DIRECT
1449 def_bool y
1450 depends on PCI && (X86_64 || (PCI_GODIRECT || PCI_GOANY) || X86_VISWS)
1452 config PCI_MMCONFIG
1453 def_bool y
1454 depends on X86_32 && PCI && ACPI && (PCI_GOMMCONFIG || PCI_GOANY)
1456 config PCI_DOMAINS
1457 def_bool y
1458 depends on PCI
1460 config PCI_MMCONFIG
1461 bool "Support mmconfig PCI config space access"
1462 depends on X86_64 && PCI && ACPI
1464 config DMAR
1465 bool "Support for DMA Remapping Devices (EXPERIMENTAL)"
1466 depends on X86_64 && PCI_MSI && ACPI && EXPERIMENTAL
1467 help
1468 DMA remapping (DMAR) devices support enables independent address
1469 translations for Direct Memory Access (DMA) from devices.
1470 These DMA remapping devices are reported via ACPI tables
1471 and include PCI device scope covered by these DMA
1472 remapping devices.
1474 config DMAR_GFX_WA
1475 def_bool y
1476 prompt "Support for Graphics workaround"
1477 depends on DMAR
1478 help
1479 Current Graphics drivers tend to use physical address
1480 for DMA and avoid using DMA APIs. Setting this config
1481 option permits the IOMMU driver to set a unity map for
1482 all the OS-visible memory. Hence the driver can continue
1483 to use physical addresses for DMA.
1485 config DMAR_FLOPPY_WA
1486 def_bool y
1487 depends on DMAR
1488 help
1489 Floppy disk drivers are know to bypass DMA API calls
1490 thereby failing to work when IOMMU is enabled. This
1491 workaround will setup a 1:1 mapping for the first
1492 16M to make floppy (an ISA device) work.
1494 source "drivers/pci/pcie/Kconfig"
1496 source "drivers/pci/Kconfig"
1498 # x86_64 have no ISA slots, but do have ISA-style DMA.
1499 config ISA_DMA_API
1500 def_bool y
1502 if X86_32
1504 config ISA
1505 bool "ISA support"
1506 depends on !(X86_VOYAGER || X86_VISWS)
1507 help
1508 Find out whether you have ISA slots on your motherboard. ISA is the
1509 name of a bus system, i.e. the way the CPU talks to the other stuff
1510 inside your box. Other bus systems are PCI, EISA, MicroChannel
1511 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
1512 newer boards don't support it. If you have ISA, say Y, otherwise N.
1514 config EISA
1515 bool "EISA support"
1516 depends on ISA
1517 ---help---
1518 The Extended Industry Standard Architecture (EISA) bus was
1519 developed as an open alternative to the IBM MicroChannel bus.
1521 The EISA bus provided some of the features of the IBM MicroChannel
1522 bus while maintaining backward compatibility with cards made for
1523 the older ISA bus. The EISA bus saw limited use between 1988 and
1524 1995 when it was made obsolete by the PCI bus.
1526 Say Y here if you are building a kernel for an EISA-based machine.
1528 Otherwise, say N.
1530 source "drivers/eisa/Kconfig"
1532 config MCA
1533 bool "MCA support" if !(X86_VISWS || X86_VOYAGER)
1534 default y if X86_VOYAGER
1535 help
1536 MicroChannel Architecture is found in some IBM PS/2 machines and
1537 laptops. It is a bus system similar to PCI or ISA. See
1538 <file:Documentation/mca.txt> (and especially the web page given
1539 there) before attempting to build an MCA bus kernel.
1541 source "drivers/mca/Kconfig"
1543 config SCx200
1544 tristate "NatSemi SCx200 support"
1545 depends on !X86_VOYAGER
1546 help
1547 This provides basic support for National Semiconductor's
1548 (now AMD's) Geode processors. The driver probes for the
1549 PCI-IDs of several on-chip devices, so its a good dependency
1550 for other scx200_* drivers.
1552 If compiled as a module, the driver is named scx200.
1554 config SCx200HR_TIMER
1555 tristate "NatSemi SCx200 27MHz High-Resolution Timer Support"
1556 depends on SCx200 && GENERIC_TIME
1557 default y
1558 help
1559 This driver provides a clocksource built upon the on-chip
1560 27MHz high-resolution timer. Its also a workaround for
1561 NSC Geode SC-1100's buggy TSC, which loses time when the
1562 processor goes idle (as is done by the scheduler). The
1563 other workaround is idle=poll boot option.
1565 config GEODE_MFGPT_TIMER
1566 def_bool y
1567 prompt "Geode Multi-Function General Purpose Timer (MFGPT) events"
1568 depends on MGEODE_LX && GENERIC_TIME && GENERIC_CLOCKEVENTS
1569 help
1570 This driver provides a clock event source based on the MFGPT
1571 timer(s) in the CS5535 and CS5536 companion chip for the geode.
1572 MFGPTs have a better resolution and max interval than the
1573 generic PIT, and are suitable for use as high-res timers.
1575 endif # X86_32
1577 config K8_NB
1578 def_bool y
1579 depends on AGP_AMD64 || (X86_64 && (GART_IOMMU || (PCI && NUMA)))
1581 source "drivers/pcmcia/Kconfig"
1583 source "drivers/pci/hotplug/Kconfig"
1585 endmenu
1588 menu "Executable file formats / Emulations"
1590 source "fs/Kconfig.binfmt"
1592 config IA32_EMULATION
1593 bool "IA32 Emulation"
1594 depends on X86_64
1595 select COMPAT_BINFMT_ELF
1596 help
1597 Include code to run 32-bit programs under a 64-bit kernel. You should
1598 likely turn this on, unless you're 100% sure that you don't have any
1599 32-bit programs left.
1601 config IA32_AOUT
1602 tristate "IA32 a.out support"
1603 depends on IA32_EMULATION && ARCH_SUPPORTS_AOUT
1604 help
1605 Support old a.out binaries in the 32bit emulation.
1607 config COMPAT
1608 def_bool y
1609 depends on IA32_EMULATION
1611 config COMPAT_FOR_U64_ALIGNMENT
1612 def_bool COMPAT
1613 depends on X86_64
1615 config SYSVIPC_COMPAT
1616 def_bool y
1617 depends on X86_64 && COMPAT && SYSVIPC
1619 endmenu
1622 source "net/Kconfig"
1624 source "drivers/Kconfig"
1626 source "drivers/firmware/Kconfig"
1628 source "fs/Kconfig"
1630 source "arch/x86/Kconfig.debug"
1632 source "security/Kconfig"
1634 source "crypto/Kconfig"
1636 source "arch/x86/kvm/Kconfig"
1638 source "lib/Kconfig"