ia64/linux-2.6.18-xen.hg

view arch/i386/Kconfig @ 647:a5bb490065f6

Fix the build after public header sync.
Signed-off-by: Keir Fraser <keir.fraser@citrix.com>
author Keir Fraser <keir.fraser@citrix.com>
date Wed Aug 13 14:01:49 2008 +0100 (2008-08-13)
parents 099864f50909
children
line source
1 #
2 # For a description of the syntax of this configuration file,
3 # see Documentation/kbuild/kconfig-language.txt.
4 #
6 mainmenu "Linux Kernel Configuration"
8 config X86_32
9 bool
10 default y
11 help
12 This is Linux's home port. Linux was originally native to the Intel
13 386, and runs on all the later x86 processors including the Intel
14 486, 586, Pentiums, and various instruction-set-compatible chips by
15 AMD, Cyrix, and others.
17 config GENERIC_TIME
18 bool
19 depends on !X86_XEN
20 default y
22 config LOCKDEP_SUPPORT
23 bool
24 default y
26 config STACKTRACE_SUPPORT
27 bool
28 default y
30 config SEMAPHORE_SLEEPERS
31 bool
32 default y
34 config X86
35 bool
36 default y
38 config MMU
39 bool
40 default y
42 config SBUS
43 bool
45 config GENERIC_ISA_DMA
46 bool
47 default y
49 config GENERIC_IOMAP
50 bool
51 default y
53 config GENERIC_HWEIGHT
54 bool
55 default y
57 config ARCH_MAY_HAVE_PC_FDC
58 bool
59 default y
61 config DMI
62 bool
63 default y
65 source "init/Kconfig"
67 menu "Processor type and features"
69 config SMP
70 bool "Symmetric multi-processing support"
71 ---help---
72 This enables support for systems with more than one CPU. If you have
73 a system with only one CPU, like most personal computers, say N. If
74 you have a system with more than one CPU, say Y.
76 If you say N here, the kernel will run on single and multiprocessor
77 machines, but will use only one CPU of a multiprocessor machine. If
78 you say Y here, the kernel will run on many, but not all,
79 singleprocessor machines. On a singleprocessor machine, the kernel
80 will run faster if you say N here.
82 Note that if you say Y here and choose architecture "586" or
83 "Pentium" under "Processor family", the kernel will not work on 486
84 architectures. Similarly, multiprocessor kernels for the "PPro"
85 architecture may not work on all Pentium based boards.
87 People using multiprocessor machines who say Y here should also say
88 Y to "Enhanced Real Time Clock Support", below. The "Advanced Power
89 Management" code will be disabled if you say Y here.
91 See also the <file:Documentation/smp.txt>,
92 <file:Documentation/i386/IO-APIC.txt>,
93 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
94 <http://www.tldp.org/docs.html#howto>.
96 If you don't know what to do here, say N.
98 choice
99 prompt "Subarchitecture Type"
100 default X86_PC
102 config X86_PC
103 bool "PC-compatible"
104 help
105 Choose this option if your computer is a standard PC or compatible.
107 config X86_XEN
108 bool "Xen-compatible"
109 select XEN
110 select X86_PAE
111 select X86_UP_APIC if !SMP && XEN_PRIVILEGED_GUEST
112 select X86_UP_IOAPIC if !SMP && XEN_PRIVILEGED_GUEST
113 select SWIOTLB
114 help
115 Choose this option if you plan to run this kernel on top of the
116 Xen Hypervisor.
118 config X86_ELAN
119 bool "AMD Elan"
120 help
121 Select this for an AMD Elan processor.
123 Do not use this option for K6/Athlon/Opteron processors!
125 If unsure, choose "PC-compatible" instead.
127 config X86_VOYAGER
128 bool "Voyager (NCR)"
129 help
130 Voyager is an MCA-based 32-way capable SMP architecture proprietary
131 to NCR Corp. Machine classes 345x/35xx/4100/51xx are Voyager-based.
133 *** WARNING ***
135 If you do not specifically know you have a Voyager based machine,
136 say N here, otherwise the kernel you build will not be bootable.
138 config X86_NUMAQ
139 bool "NUMAQ (IBM/Sequent)"
140 select SMP
141 select NUMA
142 help
143 This option is used for getting Linux to run on a (IBM/Sequent) NUMA
144 multiquad box. This changes the way that processors are bootstrapped,
145 and uses Clustered Logical APIC addressing mode instead of Flat Logical.
146 You will need a new lynxer.elf file to flash your firmware with - send
147 email to <Martin.Bligh@us.ibm.com>.
149 config X86_SUMMIT
150 bool "Summit/EXA (IBM x440)"
151 depends on SMP
152 help
153 This option is needed for IBM systems that use the Summit/EXA chipset.
154 In particular, it is needed for the x440.
156 If you don't have one of these computers, you should say N here.
157 If you want to build a NUMA kernel, you must select ACPI.
159 config X86_BIGSMP
160 bool "Support for other sub-arch SMP systems with more than 8 CPUs"
161 depends on SMP
162 help
163 This option is needed for the systems that have more than 8 CPUs
164 and if the system is not of any sub-arch type above.
166 If you don't have such a system, you should say N here.
168 config X86_VISWS
169 bool "SGI 320/540 (Visual Workstation)"
170 help
171 The SGI Visual Workstation series is an IA32-based workstation
172 based on SGI systems chips with some legacy PC hardware attached.
174 Say Y here to create a kernel to run on the SGI 320 or 540.
176 A kernel compiled for the Visual Workstation will not run on PCs
177 and vice versa. See <file:Documentation/sgi-visws.txt> for details.
179 config X86_GENERICARCH
180 bool "Generic architecture (Summit, bigsmp, ES7000, default)"
181 depends on SMP
182 help
183 This option compiles in the Summit, bigsmp, ES7000, default subarchitectures.
184 It is intended for a generic binary kernel.
185 If you want a NUMA kernel, select ACPI. We need SRAT for NUMA.
187 config X86_ES7000
188 bool "Support for Unisys ES7000 IA32 series"
189 depends on SMP
190 help
191 Support for Unisys ES7000 systems. Say 'Y' here if this kernel is
192 supposed to run on an IA32-based Unisys ES7000 system.
193 Only choose this option if you have such a system, otherwise you
194 should say N here.
196 endchoice
198 config ACPI_SRAT
199 bool
200 default y
201 depends on ACPI && NUMA && (X86_SUMMIT || X86_GENERICARCH)
202 select ACPI_NUMA
204 config HAVE_ARCH_PARSE_SRAT
205 bool
206 default y
207 depends on ACPI_SRAT
209 config X86_SUMMIT_NUMA
210 bool
211 default y
212 depends on NUMA && (X86_SUMMIT || X86_GENERICARCH)
214 config X86_CYCLONE_TIMER
215 bool
216 default y
217 depends on X86_SUMMIT || X86_GENERICARCH
219 config ES7000_CLUSTERED_APIC
220 bool
221 default y
222 depends on SMP && X86_ES7000 && MPENTIUMIII
224 source "arch/i386/Kconfig.cpu"
226 config HPET_TIMER
227 bool "HPET Timer Support"
228 depends on !X86_XEN
229 help
230 This enables the use of the HPET for the kernel's internal timer.
231 HPET is the next generation timer replacing legacy 8254s.
232 You can safely choose Y here. However, HPET will only be
233 activated if the platform and the BIOS support this feature.
234 Otherwise the 8254 will be used for timing services.
236 Choose N to continue using the legacy 8254 timer.
238 config HPET_EMULATE_RTC
239 bool
240 depends on HPET_TIMER && RTC=y
241 default y
243 config NR_CPUS
244 int "Maximum number of CPUs (2-255)"
245 range 2 255
246 depends on SMP
247 default "32" if X86_NUMAQ || X86_SUMMIT || X86_BIGSMP || X86_ES7000
248 default "8"
249 help
250 This allows you to specify the maximum number of CPUs which this
251 kernel will support. The maximum supported value is 255 and the
252 minimum value which makes sense is 2.
254 This is purely to save memory - each supported CPU adds
255 approximately eight kilobytes to the kernel image.
257 config SCHED_SMT
258 bool "SMT (Hyperthreading) scheduler support"
259 depends on X86_HT
260 help
261 SMT scheduler support improves the CPU scheduler's decision making
262 when dealing with Intel Pentium 4 chips with HyperThreading at a
263 cost of slightly increased overhead in some places. If unsure say
264 N here.
266 config SCHED_MC
267 bool "Multi-core scheduler support"
268 depends on X86_HT
269 default y
270 help
271 Multi-core scheduler support improves the CPU scheduler's decision
272 making when dealing with multi-core CPU chips at a cost of slightly
273 increased overhead in some places. If unsure say N here.
275 source "kernel/Kconfig.preempt"
277 config X86_UP_APIC
278 bool "Local APIC support on uniprocessors"
279 depends on !SMP && !(X86_VISWS || X86_VOYAGER || XEN_UNPRIVILEGED_GUEST)
280 help
281 A local APIC (Advanced Programmable Interrupt Controller) is an
282 integrated interrupt controller in the CPU. If you have a single-CPU
283 system which has a processor with a local APIC, you can say Y here to
284 enable and use it. If you say Y here even though your machine doesn't
285 have a local APIC, then the kernel will still run with no slowdown at
286 all. The local APIC supports CPU-generated self-interrupts (timer,
287 performance counters), and the NMI watchdog which detects hard
288 lockups.
290 config X86_UP_IOAPIC
291 bool "IO-APIC support on uniprocessors"
292 depends on X86_UP_APIC
293 help
294 An IO-APIC (I/O Advanced Programmable Interrupt Controller) is an
295 SMP-capable replacement for PC-style interrupt controllers. Most
296 SMP systems and many recent uniprocessor systems have one.
298 If you have a single-CPU system with an IO-APIC, you can say Y here
299 to use it. If you say Y here even though your machine doesn't have
300 an IO-APIC, then the kernel will still run with no slowdown at all.
302 config X86_LOCAL_APIC
303 bool
304 depends on X86_UP_APIC || ((X86_VISWS || SMP) && !(X86_VOYAGER || XEN_UNPRIVILEGED_GUEST))
305 default y
307 config X86_IO_APIC
308 bool
309 depends on X86_UP_IOAPIC || (SMP && !(X86_VISWS || X86_VOYAGER || XEN_UNPRIVILEGED_GUEST))
310 default y
312 config X86_VISWS_APIC
313 bool
314 depends on X86_VISWS
315 default y
317 config X86_MCE
318 bool "Machine Check Exception"
319 depends on !(X86_VOYAGER || X86_XEN)
320 ---help---
321 Machine Check Exception support allows the processor to notify the
322 kernel if it detects a problem (e.g. overheating, component failure).
323 The action the kernel takes depends on the severity of the problem,
324 ranging from a warning message on the console, to halting the machine.
325 Your processor must be a Pentium or newer to support this - check the
326 flags in /proc/cpuinfo for mce. Note that some older Pentium systems
327 have a design flaw which leads to false MCE events - hence MCE is
328 disabled on all P5 processors, unless explicitly enabled with "mce"
329 as a boot argument. Similarly, if MCE is built in and creates a
330 problem on some new non-standard machine, you can boot with "nomce"
331 to disable it. MCE support simply ignores non-MCE processors like
332 the 386 and 486, so nearly everyone can say Y here.
334 config X86_MCE_NONFATAL
335 tristate "Check for non-fatal errors on AMD Athlon/Duron / Intel Pentium 4"
336 depends on X86_MCE
337 help
338 Enabling this feature starts a timer that triggers every 5 seconds which
339 will look at the machine check registers to see if anything happened.
340 Non-fatal problems automatically get corrected (but still logged).
341 Disable this if you don't want to see these messages.
342 Seeing the messages this option prints out may be indicative of dying hardware,
343 or out-of-spec (ie, overclocked) hardware.
344 This option only does something on certain CPUs.
345 (AMD Athlon/Duron and Intel Pentium 4)
347 config X86_MCE_P4THERMAL
348 bool "check for P4 thermal throttling interrupt."
349 depends on X86_MCE && (X86_UP_APIC || SMP) && !X86_VISWS
350 help
351 Enabling this feature will cause a message to be printed when the P4
352 enters thermal throttling.
354 config VM86
355 default y
356 bool "Enable VM86 support" if EMBEDDED
357 help
358 This option is required by programs like DOSEMU to run 16-bit legacy
359 code on X86 processors. It also may be needed by software like
360 XFree86 to initialize some video cards via BIOS. Disabling this
361 option saves about 6k.
363 config TOSHIBA
364 tristate "Toshiba Laptop support"
365 ---help---
366 This adds a driver to safely access the System Management Mode of
367 the CPU on Toshiba portables with a genuine Toshiba BIOS. It does
368 not work on models with a Phoenix BIOS. The System Management Mode
369 is used to set the BIOS and power saving options on Toshiba portables.
371 For information on utilities to make use of this driver see the
372 Toshiba Linux utilities web site at:
373 <http://www.buzzard.org.uk/toshiba/>.
375 Say Y if you intend to run this kernel on a Toshiba portable.
376 Say N otherwise.
378 config I8K
379 tristate "Dell laptop support"
380 ---help---
381 This adds a driver to safely access the System Management Mode
382 of the CPU on the Dell Inspiron 8000. The System Management Mode
383 is used to read cpu temperature and cooling fan status and to
384 control the fans on the I8K portables.
386 This driver has been tested only on the Inspiron 8000 but it may
387 also work with other Dell laptops. You can force loading on other
388 models by passing the parameter `force=1' to the module. Use at
389 your own risk.
391 For information on utilities to make use of this driver see the
392 I8K Linux utilities web site at:
393 <http://people.debian.org/~dz/i8k/>
395 Say Y if you intend to run this kernel on a Dell Inspiron 8000.
396 Say N otherwise.
398 config X86_REBOOTFIXUPS
399 bool "Enable X86 board specific fixups for reboot"
400 depends on !X86_XEN
401 default n
402 ---help---
403 This enables chipset and/or board specific fixups to be done
404 in order to get reboot to work correctly. This is only needed on
405 some combinations of hardware and BIOS. The symptom, for which
406 this config is intended, is when reboot ends with a stalled/hung
407 system.
409 Currently, the only fixup is for the Geode GX1/CS5530A/TROM2.1.
410 combination.
412 Say Y if you want to enable the fixup. Currently, it's safe to
413 enable this option even if you don't need it.
414 Say N otherwise.
416 config MICROCODE
417 tristate "/dev/cpu/microcode - Intel IA32 CPU microcode support"
418 depends on !XEN_UNPRIVILEGED_GUEST
419 ---help---
420 If you say Y here and also to "/dev file system support" in the
421 'File systems' section, you will be able to update the microcode on
422 Intel processors in the IA32 family, e.g. Pentium Pro, Pentium II,
423 Pentium III, Pentium 4, Xeon etc. You will obviously need the
424 actual microcode binary data itself which is not shipped with the
425 Linux kernel.
427 For latest news and information on obtaining all the required
428 ingredients for this driver, check:
429 <http://www.urbanmyth.org/microcode/>.
431 To compile this driver as a module, choose M here: the
432 module will be called microcode.
434 config X86_MSR
435 tristate "/dev/cpu/*/msr - Model-specific register support"
436 help
437 This device gives privileged processes access to the x86
438 Model-Specific Registers (MSRs). It is a character device with
439 major 202 and minors 0 to 31 for /dev/cpu/0/msr to /dev/cpu/31/msr.
440 MSR accesses are directed to a specific CPU on multi-processor
441 systems.
443 config X86_CPUID
444 tristate "/dev/cpu/*/cpuid - CPU information support"
445 help
446 This device gives processes access to the x86 CPUID instruction to
447 be executed on a specific processor. It is a character device
448 with major 203 and minors 0 to 31 for /dev/cpu/0/cpuid to
449 /dev/cpu/31/cpuid.
451 config SWIOTLB
452 bool
453 default n
455 source "drivers/firmware/Kconfig"
457 choice
458 prompt "High Memory Support"
459 default NOHIGHMEM
461 config NOHIGHMEM
462 bool "off"
463 depends on !X86_NUMAQ
464 ---help---
465 Linux can use up to 64 Gigabytes of physical memory on x86 systems.
466 However, the address space of 32-bit x86 processors is only 4
467 Gigabytes large. That means that, if you have a large amount of
468 physical memory, not all of it can be "permanently mapped" by the
469 kernel. The physical memory that's not permanently mapped is called
470 "high memory".
472 If you are compiling a kernel which will never run on a machine with
473 more than 1 Gigabyte total physical RAM, answer "off" here (default
474 choice and suitable for most users). This will result in a "3GB/1GB"
475 split: 3GB are mapped so that each process sees a 3GB virtual memory
476 space and the remaining part of the 4GB virtual memory space is used
477 by the kernel to permanently map as much physical memory as
478 possible.
480 If the machine has between 1 and 4 Gigabytes physical RAM, then
481 answer "4GB" here.
483 If more than 4 Gigabytes is used then answer "64GB" here. This
484 selection turns Intel PAE (Physical Address Extension) mode on.
485 PAE implements 3-level paging on IA32 processors. PAE is fully
486 supported by Linux, PAE mode is implemented on all recent Intel
487 processors (Pentium Pro and better). NOTE: If you say "64GB" here,
488 then the kernel will not boot on CPUs that don't support PAE!
490 The actual amount of total physical memory will either be
491 auto detected or can be forced by using a kernel command line option
492 such as "mem=256M". (Try "man bootparam" or see the documentation of
493 your boot loader (lilo or loadlin) about how to pass options to the
494 kernel at boot time.)
496 If unsure, say "off".
498 config HIGHMEM4G
499 bool "4GB"
500 depends on !X86_NUMAQ
501 help
502 Select this if you have a 32-bit processor and between 1 and 4
503 gigabytes of physical RAM.
505 config HIGHMEM64G
506 bool "64GB"
507 depends on X86_CMPXCHG64
508 help
509 Select this if you have a 32-bit processor and more than 4
510 gigabytes of physical RAM.
512 endchoice
514 choice
515 depends on EXPERIMENTAL && !X86_PAE
516 prompt "Memory split" if EMBEDDED
517 default VMSPLIT_3G
518 help
519 Select the desired split between kernel and user memory.
521 If the address range available to the kernel is less than the
522 physical memory installed, the remaining memory will be available
523 as "high memory". Accessing high memory is a little more costly
524 than low memory, as it needs to be mapped into the kernel first.
525 Note that increasing the kernel address space limits the range
526 available to user programs, making the address space there
527 tighter. Selecting anything other than the default 3G/1G split
528 will also likely make your kernel incompatible with binary-only
529 kernel modules.
531 If you are not absolutely sure what you are doing, leave this
532 option alone!
534 config VMSPLIT_3G
535 bool "3G/1G user/kernel split"
536 config VMSPLIT_3G_OPT
537 bool "3G/1G user/kernel split (for full 1G low memory)"
538 config VMSPLIT_2G
539 bool "2G/2G user/kernel split"
540 config VMSPLIT_1G
541 bool "1G/3G user/kernel split"
542 endchoice
544 config PAGE_OFFSET
545 hex
546 default 0xB0000000 if VMSPLIT_3G_OPT
547 default 0x78000000 if VMSPLIT_2G
548 default 0x40000000 if VMSPLIT_1G
549 default 0xC0000000
551 config HIGHMEM
552 bool
553 depends on HIGHMEM64G || HIGHMEM4G
554 default y
556 config X86_PAE
557 bool
558 depends on HIGHMEM64G
559 default y
560 select RESOURCES_64BIT
562 # Common NUMA Features
563 config NUMA
564 bool "Numa Memory Allocation and Scheduler Support"
565 depends on SMP && HIGHMEM64G && (X86_NUMAQ || (X86_SUMMIT || X86_GENERICARCH) && ACPI)
566 default n if X86_PC
567 default y if (X86_NUMAQ || X86_SUMMIT)
569 comment "NUMA (Summit) requires SMP, 64GB highmem support, ACPI"
570 depends on X86_SUMMIT && (!HIGHMEM64G || !ACPI)
572 config NODES_SHIFT
573 int
574 default "4" if X86_NUMAQ
575 default "3"
576 depends on NEED_MULTIPLE_NODES
578 config HAVE_ARCH_BOOTMEM_NODE
579 bool
580 depends on NUMA
581 default y
583 config ARCH_HAVE_MEMORY_PRESENT
584 bool
585 depends on DISCONTIGMEM
586 default y
588 config NEED_NODE_MEMMAP_SIZE
589 bool
590 depends on DISCONTIGMEM || SPARSEMEM
591 default y
593 config HAVE_ARCH_ALLOC_REMAP
594 bool
595 depends on NUMA
596 default y
598 config ARCH_FLATMEM_ENABLE
599 def_bool y
600 depends on (ARCH_SELECT_MEMORY_MODEL && X86_PC)
602 config ARCH_DISCONTIGMEM_ENABLE
603 def_bool y
604 depends on NUMA
606 config ARCH_DISCONTIGMEM_DEFAULT
607 def_bool y
608 depends on NUMA
610 config ARCH_SPARSEMEM_ENABLE
611 def_bool y
612 depends on (NUMA || (X86_PC && EXPERIMENTAL))
613 select SPARSEMEM_STATIC
615 config ARCH_SELECT_MEMORY_MODEL
616 def_bool y
617 depends on ARCH_SPARSEMEM_ENABLE
619 source "mm/Kconfig"
621 config HAVE_ARCH_EARLY_PFN_TO_NID
622 bool
623 default y
624 depends on NUMA
626 config HIGHPTE
627 bool "Allocate 3rd-level pagetables from highmem"
628 depends on HIGHMEM4G || HIGHMEM64G
629 help
630 The VM uses one page table entry for each page of physical memory.
631 For systems with a lot of RAM, this can be wasteful of precious
632 low memory. Setting this option will put user-space page table
633 entries in high memory.
635 config MATH_EMULATION
636 bool "Math emulation"
637 depends on !X86_XEN
638 ---help---
639 Linux can emulate a math coprocessor (used for floating point
640 operations) if you don't have one. 486DX and Pentium processors have
641 a math coprocessor built in, 486SX and 386 do not, unless you added
642 a 487DX or 387, respectively. (The messages during boot time can
643 give you some hints here ["man dmesg"].) Everyone needs either a
644 coprocessor or this emulation.
646 If you don't have a math coprocessor, you need to say Y here; if you
647 say Y here even though you have a coprocessor, the coprocessor will
648 be used nevertheless. (This behavior can be changed with the kernel
649 command line option "no387", which comes handy if your coprocessor
650 is broken. Try "man bootparam" or see the documentation of your boot
651 loader (lilo or loadlin) about how to pass options to the kernel at
652 boot time.) This means that it is a good idea to say Y here if you
653 intend to use this kernel on different machines.
655 More information about the internals of the Linux math coprocessor
656 emulation can be found in <file:arch/i386/math-emu/README>.
658 If you are not sure, say Y; apart from resulting in a 66 KB bigger
659 kernel, it won't hurt.
661 config MTRR
662 bool "MTRR (Memory Type Range Register) support"
663 depends on !XEN_UNPRIVILEGED_GUEST
664 ---help---
665 On Intel P6 family processors (Pentium Pro, Pentium II and later)
666 the Memory Type Range Registers (MTRRs) may be used to control
667 processor access to memory ranges. This is most useful if you have
668 a video (VGA) card on a PCI or AGP bus. Enabling write-combining
669 allows bus write transfers to be combined into a larger transfer
670 before bursting over the PCI/AGP bus. This can increase performance
671 of image write operations 2.5 times or more. Saying Y here creates a
672 /proc/mtrr file which may be used to manipulate your processor's
673 MTRRs. Typically the X server should use this.
675 This code has a reasonably generic interface so that similar
676 control registers on other processors can be easily supported
677 as well:
679 The Cyrix 6x86, 6x86MX and M II processors have Address Range
680 Registers (ARRs) which provide a similar functionality to MTRRs. For
681 these, the ARRs are used to emulate the MTRRs.
682 The AMD K6-2 (stepping 8 and above) and K6-3 processors have two
683 MTRRs. The Centaur C6 (WinChip) has 8 MCRs, allowing
684 write-combining. All of these processors are supported by this code
685 and it makes sense to say Y here if you have one of them.
687 Saying Y here also fixes a problem with buggy SMP BIOSes which only
688 set the MTRRs for the boot CPU and not for the secondary CPUs. This
689 can lead to all sorts of problems, so it's good to say Y here.
691 You can safely say Y even if your machine doesn't have MTRRs, you'll
692 just add about 9 KB to your kernel.
694 See <file:Documentation/mtrr.txt> for more information.
696 config EFI
697 bool "Boot from EFI support"
698 depends on ACPI && !X86_XEN
699 default n
700 ---help---
701 This enables the the kernel to boot on EFI platforms using
702 system configuration information passed to it from the firmware.
703 This also enables the kernel to use any EFI runtime services that are
704 available (such as the EFI variable services).
706 This option is only useful on systems that have EFI firmware
707 and will result in a kernel image that is ~8k larger. In addition,
708 you must use the latest ELILO loader available at
709 <http://elilo.sourceforge.net> in order to take advantage of
710 kernel initialization using EFI information (neither GRUB nor LILO know
711 anything about EFI). However, even with this option, the resultant
712 kernel should continue to boot on existing non-EFI platforms.
714 config IRQBALANCE
715 bool "Enable kernel irq balancing"
716 depends on SMP && X86_IO_APIC && !X86_XEN
717 default y
718 help
719 The default yes will allow the kernel to do irq load balancing.
720 Saying no will keep the kernel from doing irq load balancing.
722 # turning this on wastes a bunch of space.
723 # Summit needs it only when NUMA is on
724 config BOOT_IOREMAP
725 bool
726 depends on (((X86_SUMMIT || X86_GENERICARCH) && NUMA) || (X86 && EFI))
727 default y
729 config REGPARM
730 bool "Use register arguments"
731 default y
732 help
733 Compile the kernel with -mregparm=3. This instructs gcc to use
734 a more efficient function call ABI which passes the first three
735 arguments of a function call via registers, which results in denser
736 and faster code.
738 If this option is disabled, then the default ABI of passing
739 arguments via the stack is used.
741 If unsure, say Y.
743 config SECCOMP
744 bool "Enable seccomp to safely compute untrusted bytecode"
745 depends on PROC_FS
746 default y
747 help
748 This kernel feature is useful for number crunching applications
749 that may need to compute untrusted bytecode during their
750 execution. By using pipes or other transports made available to
751 the process as file descriptors supporting the read/write
752 syscalls, it's possible to isolate those applications in
753 their own address space using seccomp. Once seccomp is
754 enabled via /proc/<pid>/seccomp, it cannot be disabled
755 and the task is only allowed to execute a few safe syscalls
756 defined by each seccomp mode.
758 If unsure, say Y. Only embedded should say N here.
760 source kernel/Kconfig.hz
762 config KEXEC
763 bool "kexec system call (EXPERIMENTAL)"
764 depends on EXPERIMENTAL && !XEN_UNPRIVILEGED_GUEST
765 help
766 kexec is a system call that implements the ability to shutdown your
767 current kernel, and to start another kernel. It is like a reboot
768 but it is independent of the system firmware. And like a reboot
769 you can start any kernel with it, not just Linux.
771 The name comes from the similarity to the exec system call.
773 It is an ongoing process to be certain the hardware in a machine
774 is properly shutdown, so do not be surprised if this code does not
775 initially work for you. It may help to enable device hotplugging
776 support. As of this writing the exact hardware interface is
777 strongly in flux, so no good recommendation can be made.
779 config CRASH_DUMP
780 bool "kernel crash dumps (EXPERIMENTAL)"
781 depends on EXPERIMENTAL
782 depends on HIGHMEM
783 depends on !XEN
784 help
785 Generate crash dump after being started by kexec.
787 config PHYSICAL_START
788 hex "Physical address where the kernel is loaded" if (EMBEDDED || CRASH_DUMP)
790 default "0x1000000" if CRASH_DUMP
791 default "0x100000"
792 help
793 This gives the physical address where the kernel is loaded. Normally
794 for regular kernels this value is 0x100000 (1MB). But in the case
795 of kexec on panic the fail safe kernel needs to run at a different
796 address than the panic-ed kernel. This option is used to set the load
797 address for kernels used to capture crash dump on being kexec'ed
798 after panic. The default value for crash dump kernels is
799 0x1000000 (16MB). This can also be set based on the "X" value as
800 specified in the "crashkernel=YM@XM" command line boot parameter
801 passed to the panic-ed kernel. Typically this parameter is set as
802 crashkernel=64M@16M. Please take a look at
803 Documentation/kdump/kdump.txt for more details about crash dumps.
805 Don't change this unless you know what you are doing.
807 config HOTPLUG_CPU
808 bool "Support for hot-pluggable CPUs (EXPERIMENTAL)"
809 depends on SMP && HOTPLUG && EXPERIMENTAL && !X86_VOYAGER
810 ---help---
811 Say Y here to experiment with turning CPUs off and on, and to
812 enable suspend on SMP systems. CPUs can be controlled through
813 /sys/devices/system/cpu.
815 config COMPAT_VDSO
816 bool "Compat VDSO support"
817 depends on !X86_XEN
818 default y
819 help
820 Map the VDSO to the predictable old-style address too.
821 ---help---
822 Say N here if you are running a sufficiently recent glibc
823 version (2.3.3 or later), to remove the high-mapped
824 VDSO mapping and to exclusively use the randomized VDSO.
826 If unsure, say Y.
828 endmenu
830 config ARCH_ENABLE_MEMORY_HOTPLUG
831 def_bool y
832 depends on HIGHMEM
834 menu "Power management options (ACPI, APM)"
835 depends on !(X86_VOYAGER || XEN_UNPRIVILEGED_GUEST)
837 source "kernel/power/Kconfig"
839 source "drivers/acpi/Kconfig"
841 menu "APM (Advanced Power Management) BIOS Support"
842 depends on PM && !(X86_VISWS || X86_XEN)
844 config APM
845 tristate "APM (Advanced Power Management) BIOS support"
846 depends on PM && PM_LEGACY
847 ---help---
848 APM is a BIOS specification for saving power using several different
849 techniques. This is mostly useful for battery powered laptops with
850 APM compliant BIOSes. If you say Y here, the system time will be
851 reset after a RESUME operation, the /proc/apm device will provide
852 battery status information, and user-space programs will receive
853 notification of APM "events" (e.g. battery status change).
855 If you select "Y" here, you can disable actual use of the APM
856 BIOS by passing the "apm=off" option to the kernel at boot time.
858 Note that the APM support is almost completely disabled for
859 machines with more than one CPU.
861 In order to use APM, you will need supporting software. For location
862 and more information, read <file:Documentation/pm.txt> and the
863 Battery Powered Linux mini-HOWTO, available from
864 <http://www.tldp.org/docs.html#howto>.
866 This driver does not spin down disk drives (see the hdparm(8)
867 manpage ("man 8 hdparm") for that), and it doesn't turn off
868 VESA-compliant "green" monitors.
870 This driver does not support the TI 4000M TravelMate and the ACER
871 486/DX4/75 because they don't have compliant BIOSes. Many "green"
872 desktop machines also don't have compliant BIOSes, and this driver
873 may cause those machines to panic during the boot phase.
875 Generally, if you don't have a battery in your machine, there isn't
876 much point in using this driver and you should say N. If you get
877 random kernel OOPSes or reboots that don't seem to be related to
878 anything, try disabling/enabling this option (or disabling/enabling
879 APM in your BIOS).
881 Some other things you should try when experiencing seemingly random,
882 "weird" problems:
884 1) make sure that you have enough swap space and that it is
885 enabled.
886 2) pass the "no-hlt" option to the kernel
887 3) switch on floating point emulation in the kernel and pass
888 the "no387" option to the kernel
889 4) pass the "floppy=nodma" option to the kernel
890 5) pass the "mem=4M" option to the kernel (thereby disabling
891 all but the first 4 MB of RAM)
892 6) make sure that the CPU is not over clocked.
893 7) read the sig11 FAQ at <http://www.bitwizard.nl/sig11/>
894 8) disable the cache from your BIOS settings
895 9) install a fan for the video card or exchange video RAM
896 10) install a better fan for the CPU
897 11) exchange RAM chips
898 12) exchange the motherboard.
900 To compile this driver as a module, choose M here: the
901 module will be called apm.
903 config APM_IGNORE_USER_SUSPEND
904 bool "Ignore USER SUSPEND"
905 depends on APM
906 help
907 This option will ignore USER SUSPEND requests. On machines with a
908 compliant APM BIOS, you want to say N. However, on the NEC Versa M
909 series notebooks, it is necessary to say Y because of a BIOS bug.
911 config APM_DO_ENABLE
912 bool "Enable PM at boot time"
913 depends on APM
914 ---help---
915 Enable APM features at boot time. From page 36 of the APM BIOS
916 specification: "When disabled, the APM BIOS does not automatically
917 power manage devices, enter the Standby State, enter the Suspend
918 State, or take power saving steps in response to CPU Idle calls."
919 This driver will make CPU Idle calls when Linux is idle (unless this
920 feature is turned off -- see "Do CPU IDLE calls", below). This
921 should always save battery power, but more complicated APM features
922 will be dependent on your BIOS implementation. You may need to turn
923 this option off if your computer hangs at boot time when using APM
924 support, or if it beeps continuously instead of suspending. Turn
925 this off if you have a NEC UltraLite Versa 33/C or a Toshiba
926 T400CDT. This is off by default since most machines do fine without
927 this feature.
929 config APM_CPU_IDLE
930 bool "Make CPU Idle calls when idle"
931 depends on APM
932 help
933 Enable calls to APM CPU Idle/CPU Busy inside the kernel's idle loop.
934 On some machines, this can activate improved power savings, such as
935 a slowed CPU clock rate, when the machine is idle. These idle calls
936 are made after the idle loop has run for some length of time (e.g.,
937 333 mS). On some machines, this will cause a hang at boot time or
938 whenever the CPU becomes idle. (On machines with more than one CPU,
939 this option does nothing.)
941 config APM_DISPLAY_BLANK
942 bool "Enable console blanking using APM"
943 depends on APM
944 help
945 Enable console blanking using the APM. Some laptops can use this to
946 turn off the LCD backlight when the screen blanker of the Linux
947 virtual console blanks the screen. Note that this is only used by
948 the virtual console screen blanker, and won't turn off the backlight
949 when using the X Window system. This also doesn't have anything to
950 do with your VESA-compliant power-saving monitor. Further, this
951 option doesn't work for all laptops -- it might not turn off your
952 backlight at all, or it might print a lot of errors to the console,
953 especially if you are using gpm.
955 config APM_RTC_IS_GMT
956 bool "RTC stores time in GMT"
957 depends on APM
958 help
959 Say Y here if your RTC (Real Time Clock a.k.a. hardware clock)
960 stores the time in GMT (Greenwich Mean Time). Say N if your RTC
961 stores localtime.
963 It is in fact recommended to store GMT in your RTC, because then you
964 don't have to worry about daylight savings time changes. The only
965 reason not to use GMT in your RTC is if you also run a broken OS
966 that doesn't understand GMT.
968 config APM_ALLOW_INTS
969 bool "Allow interrupts during APM BIOS calls"
970 depends on APM
971 help
972 Normally we disable external interrupts while we are making calls to
973 the APM BIOS as a measure to lessen the effects of a badly behaving
974 BIOS implementation. The BIOS should reenable interrupts if it
975 needs to. Unfortunately, some BIOSes do not -- especially those in
976 many of the newer IBM Thinkpads. If you experience hangs when you
977 suspend, try setting this to Y. Otherwise, say N.
979 config APM_REAL_MODE_POWER_OFF
980 bool "Use real mode APM BIOS call to power off"
981 depends on APM
982 help
983 Use real mode APM BIOS calls to switch off the computer. This is
984 a work-around for a number of buggy BIOSes. Switch this option on if
985 your computer crashes instead of powering off properly.
987 endmenu
989 source "arch/i386/kernel/cpu/cpufreq/Kconfig"
991 endmenu
993 menu "Bus options (PCI, PCMCIA, EISA, MCA, ISA)"
995 config PCI
996 bool "PCI support" if !X86_VISWS
997 depends on !X86_VOYAGER
998 default y if X86_VISWS
999 help
1000 Find out whether you have a PCI motherboard. PCI is the name of a
1001 bus system, i.e. the way the CPU talks to the other stuff inside
1002 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
1003 VESA. If you have PCI, say Y, otherwise N.
1005 The PCI-HOWTO, available from
1006 <http://www.tldp.org/docs.html#howto>, contains valuable
1007 information about which PCI hardware does work under Linux and which
1008 doesn't.
1010 choice
1011 prompt "PCI access mode"
1012 depends on PCI && !X86_VISWS
1013 default PCI_GOANY
1014 ---help---
1015 On PCI systems, the BIOS can be used to detect the PCI devices and
1016 determine their configuration. However, some old PCI motherboards
1017 have BIOS bugs and may crash if this is done. Also, some embedded
1018 PCI-based systems don't have any BIOS at all. Linux can also try to
1019 detect the PCI hardware directly without using the BIOS.
1021 With this option, you can specify how Linux should detect the
1022 PCI devices. If you choose "BIOS", the BIOS will be used,
1023 if you choose "Direct", the BIOS won't be used, and if you
1024 choose "MMConfig", then PCI Express MMCONFIG will be used.
1025 If you choose "Any", the kernel will try MMCONFIG, then the
1026 direct access method and falls back to the BIOS if that doesn't
1027 work. If unsure, go with the default, which is "Any".
1029 config PCI_GOBIOS
1030 bool "BIOS"
1031 depends on !X86_XEN
1033 config PCI_GOMMCONFIG
1034 bool "MMConfig"
1036 config PCI_GODIRECT
1037 bool "Direct"
1039 config PCI_GOXEN_FE
1040 bool "Xen PCI Frontend"
1041 depends on X86_XEN
1042 help
1043 The PCI device frontend driver allows the kernel to import arbitrary
1044 PCI devices from a PCI backend to support PCI driver domains.
1046 config PCI_GOANY
1047 bool "Any"
1049 endchoice
1051 config PCI_BIOS
1052 bool
1053 depends on !(X86_VISWS || X86_XEN) && PCI && (PCI_GOBIOS || PCI_GOANY)
1054 default y
1056 config PCI_DIRECT
1057 bool
1058 depends on PCI && ((PCI_GODIRECT || PCI_GOANY) || X86_VISWS)
1059 default y
1061 config PCI_MMCONFIG
1062 bool
1063 depends on PCI && ACPI && (PCI_GOMMCONFIG || PCI_GOANY)
1064 default y
1066 config XEN_PCIDEV_FRONTEND
1067 bool
1068 depends on PCI && X86_XEN && (PCI_GOXEN_FE || PCI_GOANY)
1069 select HOTPLUG
1070 default y
1072 config XEN_PCIDEV_FE_DEBUG
1073 bool "Xen PCI Frontend Debugging"
1074 depends on XEN_PCIDEV_FRONTEND
1075 default n
1076 help
1077 Enables some debug statements within the PCI Frontend.
1079 source "drivers/pci/pcie/Kconfig"
1081 source "drivers/pci/Kconfig"
1083 config ISA_DMA_API
1084 bool
1085 default y
1087 config ISA
1088 bool "ISA support"
1089 depends on !(X86_VOYAGER || X86_VISWS || X86_XEN)
1090 help
1091 Find out whether you have ISA slots on your motherboard. ISA is the
1092 name of a bus system, i.e. the way the CPU talks to the other stuff
1093 inside your box. Other bus systems are PCI, EISA, MicroChannel
1094 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
1095 newer boards don't support it. If you have ISA, say Y, otherwise N.
1097 config EISA
1098 bool "EISA support"
1099 depends on ISA
1100 ---help---
1101 The Extended Industry Standard Architecture (EISA) bus was
1102 developed as an open alternative to the IBM MicroChannel bus.
1104 The EISA bus provided some of the features of the IBM MicroChannel
1105 bus while maintaining backward compatibility with cards made for
1106 the older ISA bus. The EISA bus saw limited use between 1988 and
1107 1995 when it was made obsolete by the PCI bus.
1109 Say Y here if you are building a kernel for an EISA-based machine.
1111 Otherwise, say N.
1113 source "drivers/eisa/Kconfig"
1115 config MCA
1116 bool "MCA support" if !(X86_VISWS || X86_VOYAGER || X86_XEN)
1117 default y if X86_VOYAGER
1118 help
1119 MicroChannel Architecture is found in some IBM PS/2 machines and
1120 laptops. It is a bus system similar to PCI or ISA. See
1121 <file:Documentation/mca.txt> (and especially the web page given
1122 there) before attempting to build an MCA bus kernel.
1124 source "drivers/mca/Kconfig"
1126 config SCx200
1127 tristate "NatSemi SCx200 support"
1128 depends on !X86_VOYAGER
1129 help
1130 This provides basic support for National Semiconductor's
1131 (now AMD's) Geode processors. The driver probes for the
1132 PCI-IDs of several on-chip devices, so its a good dependency
1133 for other scx200_* drivers.
1135 If compiled as a module, the driver is named scx200.
1137 config SCx200HR_TIMER
1138 tristate "NatSemi SCx200 27MHz High-Resolution Timer Support"
1139 depends on SCx200 && GENERIC_TIME
1140 default y
1141 help
1142 This driver provides a clocksource built upon the on-chip
1143 27MHz high-resolution timer. Its also a workaround for
1144 NSC Geode SC-1100's buggy TSC, which loses time when the
1145 processor goes idle (as is done by the scheduler). The
1146 other workaround is idle=poll boot option.
1148 config K8_NB
1149 def_bool y
1150 depends on AGP_AMD64
1152 source "drivers/pcmcia/Kconfig"
1154 source "drivers/pci/hotplug/Kconfig"
1156 endmenu
1158 menu "Executable file formats"
1160 source "fs/Kconfig.binfmt"
1162 endmenu
1164 source "net/Kconfig"
1166 source "drivers/Kconfig"
1168 source "fs/Kconfig"
1170 menu "Instrumentation Support"
1171 depends on EXPERIMENTAL
1173 source "arch/i386/oprofile/Kconfig"
1175 config KPROBES
1176 bool "Kprobes (EXPERIMENTAL)"
1177 depends on EXPERIMENTAL && MODULES
1178 help
1179 Kprobes allows you to trap at almost any kernel address and
1180 execute a callback function. register_kprobe() establishes
1181 a probepoint and specifies the callback. Kprobes is useful
1182 for kernel debugging, non-intrusive instrumentation and testing.
1183 If in doubt, say "N".
1184 endmenu
1186 source "arch/i386/Kconfig.debug"
1188 source "security/Kconfig"
1190 source "crypto/Kconfig"
1192 source "drivers/xen/Kconfig"
1194 source "lib/Kconfig"
1197 # Use the generic interrupt handling code in kernel/irq/:
1199 config GENERIC_HARDIRQS
1200 bool
1201 default y
1203 config GENERIC_IRQ_PROBE
1204 bool
1205 default y
1207 config GENERIC_PENDING_IRQ
1208 bool
1209 depends on GENERIC_HARDIRQS && SMP
1210 default y
1212 config X86_SMP
1213 bool
1214 depends on SMP && !X86_VOYAGER
1215 default y
1217 config X86_HT
1218 bool
1219 depends on SMP && !(X86_VISWS || X86_VOYAGER || X86_XEN)
1220 default y
1222 config X86_BIOS_REBOOT
1223 bool
1224 depends on !(X86_VISWS || X86_VOYAGER)
1225 default y
1227 config X86_TRAMPOLINE
1228 bool
1229 depends on X86_SMP || (X86_VOYAGER && SMP)
1230 depends on !XEN
1231 default y
1233 config X86_NO_TSS
1234 bool
1235 depends on X86_XEN
1236 default y
1238 config X86_NO_IDT
1239 bool
1240 depends on X86_XEN
1241 default y
1243 config KTIME_SCALAR
1244 bool
1245 default y