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