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