blob: c70d8867800f94d02987317e0cc6a95a80d5c56c [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
Ingo Molnara5574cf2008-05-05 23:19:50 +020021 select HAVE_UNSTABLE_SCHED_CLOCK
Sam Ravnborgec7748b2008-02-09 10:46:40 +010022 select HAVE_IDE
Mathieu Desnoyers42d4b832008-02-02 15:10:34 -050023 select HAVE_OPROFILE
Mathieu Desnoyers3f550092008-02-02 15:10:35 -050024 select HAVE_KPROBES
Ananth N Mavinakayanahalli9edddaa2008-03-04 14:28:37 -080025 select HAVE_KRETPROBES
Randy Dunlap1a4e3f82008-02-20 09:20:08 -080026 select HAVE_KVM if ((X86_32 && !X86_VOYAGER && !X86_VISWS && !X86_NUMAQ) || X86_64)
Ingo Molnarfcbc04c2008-04-21 13:39:53 +020027 select HAVE_ARCH_KGDB if !X86_VOYAGER
Balbir Singh7d8330a2008-02-10 12:46:28 +053028
Sam Ravnborg73531902008-05-25 23:03:18 +020029config ARCH_DEFCONFIG
Sam Ravnborgb9b39bf2008-04-29 12:48:15 +020030 string
Sam Ravnborg73531902008-05-25 23:03:18 +020031 default "arch/x86/configs/i386_defconfig" if X86_32
32 default "arch/x86/configs/x86_64_defconfig" if X86_64
Sam Ravnborgb9b39bf2008-04-29 12:48:15 +020033
Sam Ravnborg8d5fffb2007-11-06 23:30:30 +010034
Nick Piggin95c354f2008-01-30 13:31:20 +010035config GENERIC_LOCKBREAK
Nick Piggin314cdbe2008-01-30 13:31:21 +010036 def_bool n
Nick Piggin95c354f2008-01-30 13:31:20 +010037
Sam Ravnborg8d5fffb2007-11-06 23:30:30 +010038config GENERIC_TIME
Harvey Harrison3c2362e2008-01-30 13:31:03 +010039 def_bool y
Sam Ravnborg8d5fffb2007-11-06 23:30:30 +010040
41config GENERIC_CMOS_UPDATE
Harvey Harrison3c2362e2008-01-30 13:31:03 +010042 def_bool y
Sam Ravnborg8d5fffb2007-11-06 23:30:30 +010043
44config CLOCKSOURCE_WATCHDOG
Harvey Harrison3c2362e2008-01-30 13:31:03 +010045 def_bool y
Sam Ravnborg8d5fffb2007-11-06 23:30:30 +010046
47config GENERIC_CLOCKEVENTS
Harvey Harrison3c2362e2008-01-30 13:31:03 +010048 def_bool y
Sam Ravnborg8d5fffb2007-11-06 23:30:30 +010049
50config GENERIC_CLOCKEVENTS_BROADCAST
Harvey Harrison3c2362e2008-01-30 13:31:03 +010051 def_bool y
Sam Ravnborg8d5fffb2007-11-06 23:30:30 +010052 depends on X86_64 || (X86_32 && X86_LOCAL_APIC)
53
54config LOCKDEP_SUPPORT
Harvey Harrison3c2362e2008-01-30 13:31:03 +010055 def_bool y
Sam Ravnborg8d5fffb2007-11-06 23:30:30 +010056
57config STACKTRACE_SUPPORT
Harvey Harrison3c2362e2008-01-30 13:31:03 +010058 def_bool y
Sam Ravnborg8d5fffb2007-11-06 23:30:30 +010059
Heiko Carstensaa7d9352008-02-01 17:45:14 +010060config HAVE_LATENCYTOP_SUPPORT
61 def_bool y
62
Christoph Lameter1f842602008-01-07 23:20:30 -080063config FAST_CMPXCHG_LOCAL
64 bool
65 default y
66
Sam Ravnborg8d5fffb2007-11-06 23:30:30 +010067config MMU
Harvey Harrison3c2362e2008-01-30 13:31:03 +010068 def_bool y
Sam Ravnborg8d5fffb2007-11-06 23:30:30 +010069
70config ZONE_DMA
Harvey Harrison3c2362e2008-01-30 13:31:03 +010071 def_bool y
Sam Ravnborg8d5fffb2007-11-06 23:30:30 +010072
Sam Ravnborg8d5fffb2007-11-06 23:30:30 +010073config SBUS
74 bool
75
76config GENERIC_ISA_DMA
Harvey Harrison3c2362e2008-01-30 13:31:03 +010077 def_bool y
Sam Ravnborg8d5fffb2007-11-06 23:30:30 +010078
79config GENERIC_IOMAP
Harvey Harrison3c2362e2008-01-30 13:31:03 +010080 def_bool y
Sam Ravnborg8d5fffb2007-11-06 23:30:30 +010081
82config GENERIC_BUG
Harvey Harrison3c2362e2008-01-30 13:31:03 +010083 def_bool y
Sam Ravnborg8d5fffb2007-11-06 23:30:30 +010084 depends on BUG
85
86config GENERIC_HWEIGHT
Harvey Harrison3c2362e2008-01-30 13:31:03 +010087 def_bool y
Sam Ravnborg8d5fffb2007-11-06 23:30:30 +010088
Florian Fainellia6082952008-01-30 13:33:35 +010089config GENERIC_GPIO
90 def_bool n
91
Sam Ravnborg8d5fffb2007-11-06 23:30:30 +010092config ARCH_MAY_HAVE_PC_FDC
Harvey Harrison3c2362e2008-01-30 13:31:03 +010093 def_bool y
Sam Ravnborg8d5fffb2007-11-06 23:30:30 +010094
Sam Ravnborg1032c0b2007-11-06 21:35:08 +010095config RWSEM_GENERIC_SPINLOCK
96 def_bool !X86_XADD
97
98config RWSEM_XCHGADD_ALGORITHM
99 def_bool X86_XADD
100
101config ARCH_HAS_ILOG2_U32
102 def_bool n
103
104config ARCH_HAS_ILOG2_U64
105 def_bool n
106
Venki Pallipadia6869cc2008-02-08 17:05:44 -0800107config ARCH_HAS_CPU_IDLE_WAIT
108 def_bool y
109
Sam Ravnborg1032c0b2007-11-06 21:35:08 +0100110config GENERIC_CALIBRATE_DELAY
111 def_bool y
112
Sam Ravnborg8d5fffb2007-11-06 23:30:30 +0100113config GENERIC_TIME_VSYSCALL
114 bool
115 default X86_64
116
venkatesh.pallipadi@intel.com9a0b8412008-01-31 17:35:06 -0800117config ARCH_HAS_CPU_RELAX
118 def_bool y
Sam Ravnborg8d5fffb2007-11-06 23:30:30 +0100119
Pekka Enberg1b27d052008-04-28 02:12:22 -0700120config ARCH_HAS_CACHE_LINE_SIZE
121 def_bool y
122
Mike Travisdd5af902008-01-30 13:33:32 +0100123config HAVE_SETUP_PER_CPU_AREA
Mike Travis23ca4bb2008-05-12 21:21:12 +0200124 def_bool X86_64_SMP || (X86_SMP && !X86_VOYAGER)
travis@sgi.comb32ef632008-01-30 13:32:51 +0100125
Mike Travis9f0e8d02008-04-04 18:11:01 -0700126config HAVE_CPUMASK_OF_CPU_MAP
127 def_bool X86_64_SMP
128
Johannes Berg801e4062007-12-08 02:12:39 +0100129config ARCH_HIBERNATION_POSSIBLE
130 def_bool y
131 depends on !SMP || !X86_VOYAGER
132
Johannes Bergf4cb5702007-12-08 02:14:00 +0100133config ARCH_SUSPEND_POSSIBLE
134 def_bool y
135 depends on !X86_VOYAGER
136
Sam Ravnborg8d5fffb2007-11-06 23:30:30 +0100137config ZONE_DMA32
138 bool
139 default X86_64
140
141config ARCH_POPULATES_NODE_MAP
142 def_bool y
143
144config AUDIT_ARCH
145 bool
146 default X86_64
147
David Howellsb0b933c2008-02-08 04:19:27 -0800148config ARCH_SUPPORTS_AOUT
149 def_bool y
150
Ingo Molnar765c68b2008-04-09 11:03:37 +0200151config ARCH_SUPPORTS_OPTIMIZED_INLINING
152 def_bool y
153
Sam Ravnborg8d5fffb2007-11-06 23:30:30 +0100154# Use the generic interrupt handling code in kernel/irq/:
155config GENERIC_HARDIRQS
156 bool
157 default y
158
159config GENERIC_IRQ_PROBE
160 bool
161 default y
162
163config GENERIC_PENDING_IRQ
164 bool
165 depends on GENERIC_HARDIRQS && SMP
166 default y
167
168config X86_SMP
169 bool
Sam Ravnborg6b0c3d42008-01-30 13:32:27 +0100170 depends on SMP && ((X86_32 && !X86_VOYAGER) || X86_64)
Sam Ravnborg8d5fffb2007-11-06 23:30:30 +0100171 default y
172
Sam Ravnborg6b0c3d42008-01-30 13:32:27 +0100173config X86_32_SMP
174 def_bool y
175 depends on X86_32 && SMP
176
177config X86_64_SMP
178 def_bool y
179 depends on X86_64 && SMP
180
Sam Ravnborg8d5fffb2007-11-06 23:30:30 +0100181config X86_HT
182 bool
Adrian Bunkee0011a2007-12-04 17:19:07 +0100183 depends on SMP
Hiroshi Shimamotob089c122008-02-27 13:16:30 -0800184 depends on (X86_32 && !(X86_VISWS || X86_VOYAGER)) || X86_64
Sam Ravnborg8d5fffb2007-11-06 23:30:30 +0100185 default y
186
187config X86_BIOS_REBOOT
188 bool
Ingo Molnar3e8f7e32008-04-28 10:46:58 +0200189 depends on !X86_VISWS && !X86_VOYAGER
Sam Ravnborg8d5fffb2007-11-06 23:30:30 +0100190 default y
191
192config X86_TRAMPOLINE
193 bool
Pavel Macheke44b7b72008-04-10 23:28:10 +0200194 depends on X86_SMP || (X86_VOYAGER && SMP) || (64BIT && ACPI_SLEEP)
Sam Ravnborg8d5fffb2007-11-06 23:30:30 +0100195 default y
196
197config KTIME_SCALAR
198 def_bool X86_32
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100199source "init/Kconfig"
Sam Ravnborg8d5fffb2007-11-06 23:30:30 +0100200
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100201menu "Processor type and features"
202
203source "kernel/time/Kconfig"
204
205config SMP
206 bool "Symmetric multi-processing support"
207 ---help---
208 This enables support for systems with more than one CPU. If you have
209 a system with only one CPU, like most personal computers, say N. If
210 you have a system with more than one CPU, say Y.
211
212 If you say N here, the kernel will run on single and multiprocessor
213 machines, but will use only one CPU of a multiprocessor machine. If
214 you say Y here, the kernel will run on many, but not all,
215 singleprocessor machines. On a singleprocessor machine, the kernel
216 will run faster if you say N here.
217
218 Note that if you say Y here and choose architecture "586" or
219 "Pentium" under "Processor family", the kernel will not work on 486
220 architectures. Similarly, multiprocessor kernels for the "PPro"
221 architecture may not work on all Pentium based boards.
222
223 People using multiprocessor machines who say Y here should also say
224 Y to "Enhanced Real Time Clock Support", below. The "Advanced Power
225 Management" code will be disabled if you say Y here.
226
Adrian Bunk03502fa2008-02-03 15:50:21 +0200227 See also <file:Documentation/i386/IO-APIC.txt>,
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100228 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
229 <http://www.tldp.org/docs.html#howto>.
230
231 If you don't know what to do here, say N.
232
Yinghai Lu6695c852008-06-19 12:13:09 -0700233config X86_FIND_SMP_CONFIG
234 def_bool y
235 depends on X86_MPPARSE || X86_VOYAGER || X86_VISWS
Yinghai Lu6695c852008-06-19 12:13:09 -0700236
237if ACPI
238config X86_MPPARSE
239 def_bool y
240 bool "Enable MPS table"
Yinghai Lubad48f42008-06-20 07:33:31 -0700241 depends on X86_LOCAL_APIC && !X86_VISWS
Yinghai Lu6695c852008-06-19 12:13:09 -0700242 help
243 For old smp systems that do not have proper acpi support. Newer systems
244 (esp with 64bit cpus) with acpi support, MADT and DSDT will override it
245endif
246
247if !ACPI
248config X86_MPPARSE
249 def_bool y
Yinghai Lubad48f42008-06-20 07:33:31 -0700250 depends on X86_LOCAL_APIC && !X86_VISWS
Yinghai Lu6695c852008-06-19 12:13:09 -0700251endif
252
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100253choice
254 prompt "Subarchitecture Type"
255 default X86_PC
256
257config X86_PC
258 bool "PC-compatible"
259 help
260 Choose this option if your computer is a standard PC or compatible.
261
262config X86_ELAN
263 bool "AMD Elan"
264 depends on X86_32
265 help
266 Select this for an AMD Elan processor.
267
268 Do not use this option for K6/Athlon/Opteron processors!
269
270 If unsure, choose "PC-compatible" instead.
271
272config X86_VOYAGER
273 bool "Voyager (NCR)"
Ingo Molnar1ac97012008-05-19 14:10:14 +0200274 depends on X86_32 && (SMP || BROKEN) && !PCI
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100275 help
276 Voyager is an MCA-based 32-way capable SMP architecture proprietary
277 to NCR Corp. Machine classes 345x/35xx/4100/51xx are Voyager-based.
278
279 *** WARNING ***
280
281 If you do not specifically know you have a Voyager based machine,
282 say N here, otherwise the kernel you build will not be bootable.
283
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100284config X86_VISWS
285 bool "SGI 320/540 (Visual Workstation)"
Ingo Molnar1ac97012008-05-19 14:10:14 +0200286 depends on X86_32 && !PCI
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100287 help
288 The SGI Visual Workstation series is an IA32-based workstation
289 based on SGI systems chips with some legacy PC hardware attached.
290
291 Say Y here to create a kernel to run on the SGI 320 or 540.
292
293 A kernel compiled for the Visual Workstation will not run on PCs
294 and vice versa. See <file:Documentation/sgi-visws.txt> for details.
295
296config X86_GENERICARCH
Yinghai Lud49c4282008-06-08 18:31:54 -0700297 bool "Generic architecture"
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100298 depends on X86_32
299 help
Yinghai Lud49c4282008-06-08 18:31:54 -0700300 This option compiles in the NUMAQ, Summit, bigsmp, ES7000, default
301 subarchitectures. It is intended for a generic binary kernel.
302 if you select them all, kernel will probe it one by one. and will
303 fallback to default.
304
305if X86_GENERICARCH
306
307config X86_NUMAQ
308 bool "NUMAQ (IBM/Sequent)"
Ingo Molnar3de352b2008-07-08 11:14:58 +0200309 depends on SMP && X86_32 && PCI && X86_MPPARSE
Yinghai Lud49c4282008-06-08 18:31:54 -0700310 select NUMA
311 help
312 This option is used for getting Linux to run on a NUMAQ (IBM/Sequent)
313 NUMA multiquad box. This changes the way that processors are
314 bootstrapped, and uses Clustered Logical APIC addressing mode instead
315 of Flat Logical. You will need a new lynxer.elf file to flash your
316 firmware with - send email to <Martin.Bligh@us.ibm.com>.
317
318config X86_SUMMIT
319 bool "Summit/EXA (IBM x440)"
320 depends on X86_32 && SMP
321 help
322 This option is needed for IBM systems that use the Summit/EXA chipset.
323 In particular, it is needed for the x440.
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100324
325config X86_ES7000
326 bool "Support for Unisys ES7000 IA32 series"
327 depends on X86_32 && SMP
328 help
329 Support for Unisys ES7000 systems. Say 'Y' here if this kernel is
330 supposed to run on an IA32-based Unisys ES7000 system.
Yinghai Lud49c4282008-06-08 18:31:54 -0700331
332config X86_BIGSMP
333 bool "Support for big SMP systems with more than 8 CPUs"
334 depends on X86_32 && SMP
335 help
336 This option is needed for the systems that have more than 8 CPUs
337 and if the system is not of any sub-arch type above.
338
339endif
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100340
Florian Fainelli5e3a77e2008-01-30 13:33:36 +0100341config X86_RDC321X
342 bool "RDC R-321x SoC"
343 depends on X86_32
344 select M486
345 select X86_REBOOTFIXUPS
346 select GENERIC_GPIO
Florian Fainelli4cf31842008-02-04 16:47:55 +0100347 select LEDS_CLASS
Florian Fainelli5e3a77e2008-01-30 13:33:36 +0100348 select LEDS_GPIO
Ingo Molnar82fd8662008-05-01 03:46:22 +0200349 select NEW_LEDS
Florian Fainelli5e3a77e2008-01-30 13:33:36 +0100350 help
351 This option is needed for RDC R-321x system-on-chip, also known
352 as R-8610-(G).
353 If you don't have one of these chips, you should say N here.
354
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100355config X86_VSMP
356 bool "Support for ScaleMP vSMP"
Glauber Costa96597fd2008-02-11 17:16:04 -0200357 select PARAVIRT
Ingo Molnar1ac97012008-05-19 14:10:14 +0200358 depends on X86_64 && !PCI
Glauber Costa96597fd2008-02-11 17:16:04 -0200359 help
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100360 Support for ScaleMP vSMP systems. Say 'Y' here if this kernel is
361 supposed to run on these EM64T-based machines. Only choose this option
362 if you have one of these machines.
363
364endchoice
365
366config SCHED_NO_NO_OMIT_FRAME_POINTER
Harvey Harrison3c2362e2008-01-30 13:31:03 +0100367 def_bool y
368 prompt "Single-depth WCHAN output"
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100369 depends on X86_32
370 help
371 Calculate simpler /proc/<PID>/wchan values. If this option
372 is disabled then wchan values will recurse back to the
373 caller function. This provides more accurate wchan values,
374 at the expense of slightly more scheduling overhead.
375
376 If in doubt, say "Y".
377
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100378menuconfig PARAVIRT_GUEST
379 bool "Paravirtualized guest support"
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100380 help
381 Say Y here to get to see options related to running Linux under
382 various hypervisors. This option alone does not add any kernel code.
383
384 If you say N, all options in this submenu will be skipped and disabled.
385
386if PARAVIRT_GUEST
387
388source "arch/x86/xen/Kconfig"
389
390config VMI
391 bool "VMI Guest support"
392 select PARAVIRT
Eduardo Pereira Habkost42d545c2008-01-30 13:33:32 +0100393 depends on X86_32
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100394 depends on !(X86_VISWS || X86_VOYAGER)
395 help
396 VMI provides a paravirtualized interface to the VMware ESX server
397 (it could be used by other hypervisors in theory too, but is not
398 at the moment), by linking the kernel to a GPL-ed ROM module
399 provided by the hypervisor.
400
Glauber de Oliveira Costa790c73f2008-02-15 17:52:48 -0200401config KVM_CLOCK
402 bool "KVM paravirtualized clock"
403 select PARAVIRT
Gerd Hoffmannf6e16d52008-06-03 16:17:32 +0200404 select PARAVIRT_CLOCK
Glauber de Oliveira Costa790c73f2008-02-15 17:52:48 -0200405 depends on !(X86_VISWS || X86_VOYAGER)
406 help
407 Turning on this option will allow you to run a paravirtualized clock
408 when running over the KVM hypervisor. Instead of relying on a PIT
409 (or probably other) emulation by the underlying device model, the host
410 provides the guest with timing infrastructure such as time of day, and
411 system time
412
Marcelo Tosatti0cf1bfd2008-02-22 12:21:36 -0500413config KVM_GUEST
414 bool "KVM Guest support"
415 select PARAVIRT
416 depends on !(X86_VISWS || X86_VOYAGER)
417 help
418 This option enables various optimizations for running under the KVM
419 hypervisor.
420
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100421source "arch/x86/lguest/Kconfig"
422
Eduardo Pereira Habkoste61bd942008-01-30 13:33:32 +0100423config PARAVIRT
424 bool "Enable paravirtualization code"
Eduardo Pereira Habkost42d545c2008-01-30 13:33:32 +0100425 depends on !(X86_VISWS || X86_VOYAGER)
Eduardo Pereira Habkoste61bd942008-01-30 13:33:32 +0100426 help
427 This changes the kernel so it can modify itself when it is run
428 under a hypervisor, potentially improving performance significantly
429 over full virtualization. However, when run without a hypervisor
430 the kernel is theoretically slower and slightly larger.
431
Gerd Hoffmann7af192c2008-06-03 16:17:29 +0200432config PARAVIRT_CLOCK
433 bool
434 default n
435
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100436endif
437
Jeremy Fitzhardinge97349132008-06-25 00:19:14 -0400438config PARAVIRT_DEBUG
439 bool "paravirt-ops debugging"
440 depends on PARAVIRT && DEBUG_KERNEL
441 help
442 Enable to debug paravirt_ops internals. Specifically, BUG if
443 a paravirt_op is missing when it is called.
444
Yinghai Lu03273182008-04-18 17:49:15 -0700445config MEMTEST
446 bool "Memtest"
Yinghai Luc64df702008-03-21 18:56:19 -0700447 depends on X86_64
448 default y
449 help
450 This option adds a kernel parameter 'memtest', which allows memtest
Yinghai Lu03273182008-04-18 17:49:15 -0700451 to be set.
452 memtest=0, mean disabled; -- default
453 memtest=1, mean do 1 test pattern;
454 ...
455 memtest=4, mean do 4 test patterns.
Yinghai Luc64df702008-03-21 18:56:19 -0700456 If you are unsure how to answer this question, answer Y.
457
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100458config X86_SUMMIT_NUMA
Harvey Harrison3c2362e2008-01-30 13:31:03 +0100459 def_bool y
Yinghai Lu0699eae2008-06-17 15:39:01 -0700460 depends on X86_32 && NUMA && X86_GENERICARCH
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100461
462config X86_CYCLONE_TIMER
Harvey Harrison3c2362e2008-01-30 13:31:03 +0100463 def_bool y
Yinghai Lu0699eae2008-06-17 15:39:01 -0700464 depends on X86_GENERICARCH
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100465
466config ES7000_CLUSTERED_APIC
Harvey Harrison3c2362e2008-01-30 13:31:03 +0100467 def_bool y
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100468 depends on SMP && X86_ES7000 && MPENTIUMIII
469
470source "arch/x86/Kconfig.cpu"
471
472config HPET_TIMER
Harvey Harrison3c2362e2008-01-30 13:31:03 +0100473 def_bool X86_64
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100474 prompt "HPET Timer Support" if X86_32
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100475 help
476 Use the IA-PC HPET (High Precision Event Timer) to manage
477 time in preference to the PIT and RTC, if a HPET is
478 present.
479 HPET is the next generation timer replacing legacy 8254s.
480 The HPET provides a stable time base on SMP
481 systems, unlike the TSC, but it is more expensive to access,
482 as it is off-chip. You can find the HPET spec at
483 <http://www.intel.com/hardwaredesign/hpetspec.htm>.
484
485 You can safely choose Y here. However, HPET will only be
486 activated if the platform and the BIOS support this feature.
487 Otherwise the 8254 will be used for timing services.
488
489 Choose N to continue using the legacy 8254 timer.
490
491config HPET_EMULATE_RTC
Harvey Harrison3c2362e2008-01-30 13:31:03 +0100492 def_bool y
Bernhard Walle9d8af782008-02-06 01:38:52 -0800493 depends on HPET_TIMER && (RTC=y || RTC=m || RTC_DRV_CMOS=m || RTC_DRV_CMOS=y)
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100494
495# Mark as embedded because too many people got it wrong.
496# The code disables itself when not needed.
Thomas Petazzoni7ae93922008-04-28 02:14:14 -0700497config DMI
498 default y
499 bool "Enable DMI scanning" if EMBEDDED
500 help
501 Enabled scanning of DMI to identify machine quirks. Say Y
502 here unless you have verified that your setup is not
503 affected by entries in the DMI blacklist. Required by PNP
504 BIOS code.
505
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100506config GART_IOMMU
507 bool "GART IOMMU support" if EMBEDDED
508 default y
509 select SWIOTLB
510 select AGP
511 depends on X86_64 && PCI
512 help
513 Support for full DMA access of devices with 32bit memory access only
514 on systems with more than 3GB. This is usually needed for USB,
515 sound, many IDE/SATA chipsets and some other devices.
516 Provides a driver for the AMD Athlon64/Opteron/Turion/Sempron GART
517 based hardware IOMMU and a software bounce buffer based IOMMU used
518 on Intel systems and as fallback.
519 The code is only active when needed (enough memory and limited
520 device) unless CONFIG_IOMMU_DEBUG or iommu=force is specified
521 too.
522
523config CALGARY_IOMMU
524 bool "IBM Calgary IOMMU support"
525 select SWIOTLB
526 depends on X86_64 && PCI && EXPERIMENTAL
527 help
528 Support for hardware IOMMUs in IBM's xSeries x366 and x460
529 systems. Needed to run systems with more than 3GB of memory
530 properly with 32-bit PCI devices that do not support DAC
531 (Double Address Cycle). Calgary also supports bus level
532 isolation, where all DMAs pass through the IOMMU. This
533 prevents them from going anywhere except their intended
534 destination. This catches hard-to-find kernel bugs and
535 mis-behaving drivers and devices that do not use the DMA-API
536 properly to set up their DMA buffers. The IOMMU can be
537 turned off at boot time with the iommu=off parameter.
538 Normally the kernel will make the right choice by itself.
539 If unsure, say Y.
540
541config CALGARY_IOMMU_ENABLED_BY_DEFAULT
Harvey Harrison3c2362e2008-01-30 13:31:03 +0100542 def_bool y
543 prompt "Should Calgary be enabled by default?"
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100544 depends on CALGARY_IOMMU
545 help
546 Should Calgary be enabled by default? if you choose 'y', Calgary
547 will be used (if it exists). If you choose 'n', Calgary will not be
548 used even if it exists. If you choose 'n' and would like to use
549 Calgary anyway, pass 'iommu=calgary' on the kernel command line.
550 If unsure, say Y.
551
Joerg Roedel2b188722008-06-26 21:27:37 +0200552config AMD_IOMMU
553 bool "AMD IOMMU support"
Ingo Molnar07c40e82008-06-27 11:31:28 +0200554 select SWIOTLB
Ingo Molnar24d2ba02008-06-27 10:37:03 +0200555 depends on X86_64 && PCI && ACPI
Joerg Roedel2b188722008-06-26 21:27:37 +0200556 help
Joerg Roedel18d22202008-07-03 19:35:06 +0200557 With this option you can enable support for AMD IOMMU hardware in
558 your system. An IOMMU is a hardware component which provides
559 remapping of DMA memory accesses from devices. With an AMD IOMMU you
560 can isolate the the DMA memory of different devices and protect the
561 system from misbehaving device drivers or hardware.
562
563 You can find out if your system has an AMD IOMMU if you look into
564 your BIOS for an option to enable it or if you have an IVRS ACPI
565 table.
Joerg Roedel2b188722008-06-26 21:27:37 +0200566
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100567# need this always selected by IOMMU for the VIA workaround
568config SWIOTLB
569 bool
570 help
571 Support for software bounce buffers used on x86-64 systems
572 which don't have a hardware IOMMU (e.g. the current generation
573 of Intel's x86-64 CPUs). Using this PCI devices which can only
574 access 32-bits of memory can be used on systems with more than
575 3 GB of memory. If unsure, say Y.
576
FUJITA Tomonoria8522502008-04-29 00:59:36 -0700577config IOMMU_HELPER
FUJITA Tomonori18b743d2008-07-10 09:50:50 +0900578 def_bool (CALGARY_IOMMU || GART_IOMMU || SWIOTLB || AMD_IOMMU)
Mike Travis1184dc22008-05-12 21:21:12 +0200579config MAXSMP
580 bool "Configure Maximum number of SMP Processors and NUMA Nodes"
581 depends on X86_64 && SMP
582 default n
583 help
584 Configure maximum number of CPUS and NUMA Nodes for this architecture.
585 If unsure, say N.
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100586
Mike Travis1184dc22008-05-12 21:21:12 +0200587if MAXSMP
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100588config NR_CPUS
Mike Travis1184dc22008-05-12 21:21:12 +0200589 int
590 default "4096"
591endif
592
593if !MAXSMP
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100594config NR_CPUS
Mike Travisc3ed6422008-05-16 10:44:39 -0700595 int "Maximum number of CPUs (2-4096)"
596 range 2 4096
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100597 depends on SMP
598 default "32" if X86_NUMAQ || X86_SUMMIT || X86_BIGSMP || X86_ES7000
599 default "8"
600 help
601 This allows you to specify the maximum number of CPUs which this
Mike Travisc3ed6422008-05-16 10:44:39 -0700602 kernel will support. The maximum supported value is 4096 and the
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100603 minimum value which makes sense is 2.
604
605 This is purely to save memory - each supported CPU adds
606 approximately eight kilobytes to the kernel image.
Mike Travis1184dc22008-05-12 21:21:12 +0200607endif
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100608
609config SCHED_SMT
610 bool "SMT (Hyperthreading) scheduler support"
Hiroshi Shimamotob089c122008-02-27 13:16:30 -0800611 depends on X86_HT
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100612 help
613 SMT scheduler support improves the CPU scheduler's decision making
614 when dealing with Intel Pentium 4 chips with HyperThreading at a
615 cost of slightly increased overhead in some places. If unsure say
616 N here.
617
618config SCHED_MC
Harvey Harrison3c2362e2008-01-30 13:31:03 +0100619 def_bool y
620 prompt "Multi-core scheduler support"
Hiroshi Shimamotob089c122008-02-27 13:16:30 -0800621 depends on X86_HT
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100622 help
623 Multi-core scheduler support improves the CPU scheduler's decision
624 making when dealing with multi-core CPU chips at a cost of slightly
625 increased overhead in some places. If unsure say N here.
626
627source "kernel/Kconfig.preempt"
628
629config X86_UP_APIC
630 bool "Local APIC support on uniprocessors"
631 depends on X86_32 && !SMP && !(X86_VISWS || X86_VOYAGER || X86_GENERICARCH)
632 help
633 A local APIC (Advanced Programmable Interrupt Controller) is an
634 integrated interrupt controller in the CPU. If you have a single-CPU
635 system which has a processor with a local APIC, you can say Y here to
636 enable and use it. If you say Y here even though your machine doesn't
637 have a local APIC, then the kernel will still run with no slowdown at
638 all. The local APIC supports CPU-generated self-interrupts (timer,
639 performance counters), and the NMI watchdog which detects hard
640 lockups.
641
642config X86_UP_IOAPIC
643 bool "IO-APIC support on uniprocessors"
644 depends on X86_UP_APIC
645 help
646 An IO-APIC (I/O Advanced Programmable Interrupt Controller) is an
647 SMP-capable replacement for PC-style interrupt controllers. Most
648 SMP systems and many recent uniprocessor systems have one.
649
650 If you have a single-CPU system with an IO-APIC, you can say Y here
651 to use it. If you say Y here even though your machine doesn't have
652 an IO-APIC, then the kernel will still run with no slowdown at all.
653
654config X86_LOCAL_APIC
Harvey Harrison3c2362e2008-01-30 13:31:03 +0100655 def_bool y
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100656 depends on X86_64 || (X86_32 && (X86_UP_APIC || ((X86_VISWS || SMP) && !X86_VOYAGER) || X86_GENERICARCH))
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100657
658config X86_IO_APIC
Harvey Harrison3c2362e2008-01-30 13:31:03 +0100659 def_bool y
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100660 depends on X86_64 || (X86_32 && (X86_UP_IOAPIC || (SMP && !(X86_VISWS || X86_VOYAGER)) || X86_GENERICARCH))
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100661
662config X86_VISWS_APIC
Harvey Harrison3c2362e2008-01-30 13:31:03 +0100663 def_bool y
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100664 depends on X86_32 && X86_VISWS
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100665
666config X86_MCE
667 bool "Machine Check Exception"
668 depends on !X86_VOYAGER
669 ---help---
670 Machine Check Exception support allows the processor to notify the
671 kernel if it detects a problem (e.g. overheating, component failure).
672 The action the kernel takes depends on the severity of the problem,
673 ranging from a warning message on the console, to halting the machine.
674 Your processor must be a Pentium or newer to support this - check the
675 flags in /proc/cpuinfo for mce. Note that some older Pentium systems
676 have a design flaw which leads to false MCE events - hence MCE is
677 disabled on all P5 processors, unless explicitly enabled with "mce"
678 as a boot argument. Similarly, if MCE is built in and creates a
679 problem on some new non-standard machine, you can boot with "nomce"
680 to disable it. MCE support simply ignores non-MCE processors like
681 the 386 and 486, so nearly everyone can say Y here.
682
683config X86_MCE_INTEL
Harvey Harrison3c2362e2008-01-30 13:31:03 +0100684 def_bool y
685 prompt "Intel MCE features"
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100686 depends on X86_64 && X86_MCE && X86_LOCAL_APIC
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100687 help
688 Additional support for intel specific MCE features such as
689 the thermal monitor.
690
691config X86_MCE_AMD
Harvey Harrison3c2362e2008-01-30 13:31:03 +0100692 def_bool y
693 prompt "AMD MCE features"
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100694 depends on X86_64 && X86_MCE && X86_LOCAL_APIC
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100695 help
696 Additional support for AMD specific MCE features such as
697 the DRAM Error Threshold.
698
699config X86_MCE_NONFATAL
700 tristate "Check for non-fatal errors on AMD Athlon/Duron / Intel Pentium 4"
701 depends on X86_32 && X86_MCE
702 help
703 Enabling this feature starts a timer that triggers every 5 seconds which
704 will look at the machine check registers to see if anything happened.
705 Non-fatal problems automatically get corrected (but still logged).
706 Disable this if you don't want to see these messages.
707 Seeing the messages this option prints out may be indicative of dying
708 or out-of-spec (ie, overclocked) hardware.
709 This option only does something on certain CPUs.
710 (AMD Athlon/Duron and Intel Pentium 4)
711
712config X86_MCE_P4THERMAL
713 bool "check for P4 thermal throttling interrupt."
714 depends on X86_32 && X86_MCE && (X86_UP_APIC || SMP) && !X86_VISWS
715 help
716 Enabling this feature will cause a message to be printed when the P4
717 enters thermal throttling.
718
719config VM86
720 bool "Enable VM86 support" if EMBEDDED
721 default y
722 depends on X86_32
723 help
724 This option is required by programs like DOSEMU to run 16-bit legacy
725 code on X86 processors. It also may be needed by software like
726 XFree86 to initialize some video cards via BIOS. Disabling this
727 option saves about 6k.
728
729config TOSHIBA
730 tristate "Toshiba Laptop support"
731 depends on X86_32
732 ---help---
733 This adds a driver to safely access the System Management Mode of
734 the CPU on Toshiba portables with a genuine Toshiba BIOS. It does
735 not work on models with a Phoenix BIOS. The System Management Mode
736 is used to set the BIOS and power saving options on Toshiba portables.
737
738 For information on utilities to make use of this driver see the
739 Toshiba Linux utilities web site at:
740 <http://www.buzzard.org.uk/toshiba/>.
741
742 Say Y if you intend to run this kernel on a Toshiba portable.
743 Say N otherwise.
744
745config I8K
746 tristate "Dell laptop support"
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100747 ---help---
748 This adds a driver to safely access the System Management Mode
749 of the CPU on the Dell Inspiron 8000. The System Management Mode
750 is used to read cpu temperature and cooling fan status and to
751 control the fans on the I8K portables.
752
753 This driver has been tested only on the Inspiron 8000 but it may
754 also work with other Dell laptops. You can force loading on other
755 models by passing the parameter `force=1' to the module. Use at
756 your own risk.
757
758 For information on utilities to make use of this driver see the
759 I8K Linux utilities web site at:
760 <http://people.debian.org/~dz/i8k/>
761
762 Say Y if you intend to run this kernel on a Dell Inspiron 8000.
763 Say N otherwise.
764
765config X86_REBOOTFIXUPS
Harvey Harrison3c2362e2008-01-30 13:31:03 +0100766 def_bool n
767 prompt "Enable X86 board specific fixups for reboot"
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100768 depends on X86_32 && X86
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100769 ---help---
770 This enables chipset and/or board specific fixups to be done
771 in order to get reboot to work correctly. This is only needed on
772 some combinations of hardware and BIOS. The symptom, for which
773 this config is intended, is when reboot ends with a stalled/hung
774 system.
775
776 Currently, the only fixup is for the Geode machines using
Florian Fainelli5e3a77e2008-01-30 13:33:36 +0100777 CS5530A and CS5536 chipsets and the RDC R-321x SoC.
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100778
779 Say Y if you want to enable the fixup. Currently, it's safe to
780 enable this option even if you don't need it.
781 Say N otherwise.
782
783config MICROCODE
784 tristate "/dev/cpu/microcode - Intel IA32 CPU microcode support"
785 select FW_LOADER
786 ---help---
787 If you say Y here, you will be able to update the microcode on
788 Intel processors in the IA32 family, e.g. Pentium Pro, Pentium II,
789 Pentium III, Pentium 4, Xeon etc. You will obviously need the
790 actual microcode binary data itself which is not shipped with the
791 Linux kernel.
792
793 For latest news and information on obtaining all the required
794 ingredients for this driver, check:
795 <http://www.urbanmyth.org/microcode/>.
796
797 To compile this driver as a module, choose M here: the
798 module will be called microcode.
799
800config MICROCODE_OLD_INTERFACE
Harvey Harrison3c2362e2008-01-30 13:31:03 +0100801 def_bool y
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100802 depends on MICROCODE
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100803
804config X86_MSR
805 tristate "/dev/cpu/*/msr - Model-specific register support"
806 help
807 This device gives privileged processes access to the x86
808 Model-Specific Registers (MSRs). It is a character device with
809 major 202 and minors 0 to 31 for /dev/cpu/0/msr to /dev/cpu/31/msr.
810 MSR accesses are directed to a specific CPU on multi-processor
811 systems.
812
813config X86_CPUID
814 tristate "/dev/cpu/*/cpuid - CPU information support"
815 help
816 This device gives processes access to the x86 CPUID instruction to
817 be executed on a specific processor. It is a character device
818 with major 203 and minors 0 to 31 for /dev/cpu/0/cpuid to
819 /dev/cpu/31/cpuid.
820
821choice
822 prompt "High Memory Support"
823 default HIGHMEM4G if !X86_NUMAQ
824 default HIGHMEM64G if X86_NUMAQ
825 depends on X86_32
826
827config NOHIGHMEM
828 bool "off"
829 depends on !X86_NUMAQ
830 ---help---
831 Linux can use up to 64 Gigabytes of physical memory on x86 systems.
832 However, the address space of 32-bit x86 processors is only 4
833 Gigabytes large. That means that, if you have a large amount of
834 physical memory, not all of it can be "permanently mapped" by the
835 kernel. The physical memory that's not permanently mapped is called
836 "high memory".
837
838 If you are compiling a kernel which will never run on a machine with
839 more than 1 Gigabyte total physical RAM, answer "off" here (default
840 choice and suitable for most users). This will result in a "3GB/1GB"
841 split: 3GB are mapped so that each process sees a 3GB virtual memory
842 space and the remaining part of the 4GB virtual memory space is used
843 by the kernel to permanently map as much physical memory as
844 possible.
845
846 If the machine has between 1 and 4 Gigabytes physical RAM, then
847 answer "4GB" here.
848
849 If more than 4 Gigabytes is used then answer "64GB" here. This
850 selection turns Intel PAE (Physical Address Extension) mode on.
851 PAE implements 3-level paging on IA32 processors. PAE is fully
852 supported by Linux, PAE mode is implemented on all recent Intel
853 processors (Pentium Pro and better). NOTE: If you say "64GB" here,
854 then the kernel will not boot on CPUs that don't support PAE!
855
856 The actual amount of total physical memory will either be
857 auto detected or can be forced by using a kernel command line option
858 such as "mem=256M". (Try "man bootparam" or see the documentation of
859 your boot loader (lilo or loadlin) about how to pass options to the
860 kernel at boot time.)
861
862 If unsure, say "off".
863
864config HIGHMEM4G
865 bool "4GB"
866 depends on !X86_NUMAQ
867 help
868 Select this if you have a 32-bit processor and between 1 and 4
869 gigabytes of physical RAM.
870
871config HIGHMEM64G
872 bool "64GB"
873 depends on !M386 && !M486
874 select X86_PAE
875 help
876 Select this if you have a 32-bit processor and more than 4
877 gigabytes of physical RAM.
878
879endchoice
880
881choice
882 depends on EXPERIMENTAL
883 prompt "Memory split" if EMBEDDED
884 default VMSPLIT_3G
885 depends on X86_32
886 help
887 Select the desired split between kernel and user memory.
888
889 If the address range available to the kernel is less than the
890 physical memory installed, the remaining memory will be available
891 as "high memory". Accessing high memory is a little more costly
892 than low memory, as it needs to be mapped into the kernel first.
893 Note that increasing the kernel address space limits the range
894 available to user programs, making the address space there
895 tighter. Selecting anything other than the default 3G/1G split
896 will also likely make your kernel incompatible with binary-only
897 kernel modules.
898
899 If you are not absolutely sure what you are doing, leave this
900 option alone!
901
902 config VMSPLIT_3G
903 bool "3G/1G user/kernel split"
904 config VMSPLIT_3G_OPT
905 depends on !X86_PAE
906 bool "3G/1G user/kernel split (for full 1G low memory)"
907 config VMSPLIT_2G
908 bool "2G/2G user/kernel split"
909 config VMSPLIT_2G_OPT
910 depends on !X86_PAE
911 bool "2G/2G user/kernel split (for full 2G low memory)"
912 config VMSPLIT_1G
913 bool "1G/3G user/kernel split"
914endchoice
915
916config PAGE_OFFSET
917 hex
918 default 0xB0000000 if VMSPLIT_3G_OPT
919 default 0x80000000 if VMSPLIT_2G
920 default 0x78000000 if VMSPLIT_2G_OPT
921 default 0x40000000 if VMSPLIT_1G
922 default 0xC0000000
923 depends on X86_32
924
925config HIGHMEM
Harvey Harrison3c2362e2008-01-30 13:31:03 +0100926 def_bool y
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100927 depends on X86_32 && (HIGHMEM64G || HIGHMEM4G)
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100928
929config X86_PAE
Harvey Harrison3c2362e2008-01-30 13:31:03 +0100930 def_bool n
931 prompt "PAE (Physical Address Extension) Support"
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100932 depends on X86_32 && !HIGHMEM4G
933 select RESOURCES_64BIT
934 help
935 PAE is required for NX support, and furthermore enables
936 larger swapspace support for non-overcommit purposes. It
937 has the cost of more pagetable lookup overhead, and also
938 consumes more pagetable space per process.
939
940# Common NUMA Features
941config NUMA
942 bool "Numa Memory Allocation and Scheduler Support (EXPERIMENTAL)"
943 depends on SMP
Yinghai Lu0699eae2008-06-17 15:39:01 -0700944 depends on X86_64 || (X86_32 && HIGHMEM64G && (X86_NUMAQ || X86_BIGSMP || X86_SUMMIT && ACPI) && EXPERIMENTAL)
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100945 default n if X86_PC
Yinghai Lu0699eae2008-06-17 15:39:01 -0700946 default y if (X86_NUMAQ || X86_SUMMIT || X86_BIGSMP)
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100947 help
948 Enable NUMA (Non Uniform Memory Access) support.
949 The kernel will try to allocate memory used by a CPU on the
950 local memory controller of the CPU and add some more
951 NUMA awareness to the kernel.
952
953 For i386 this is currently highly experimental and should be only
954 used for kernel development. It might also cause boot failures.
955 For x86_64 this is recommended on all multiprocessor Opteron systems.
956 If the system is EM64T, you should say N unless your system is
957 EM64T NUMA.
958
959comment "NUMA (Summit) requires SMP, 64GB highmem support, ACPI"
960 depends on X86_32 && X86_SUMMIT && (!HIGHMEM64G || !ACPI)
961
962config K8_NUMA
Harvey Harrison3c2362e2008-01-30 13:31:03 +0100963 def_bool y
964 prompt "Old style AMD Opteron NUMA detection"
965 depends on X86_64 && NUMA && PCI
966 help
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100967 Enable K8 NUMA node topology detection. You should say Y here if
968 you have a multi processor AMD K8 system. This uses an old
969 method to read the NUMA configuration directly from the builtin
970 Northbridge of Opteron. It is recommended to use X86_64_ACPI_NUMA
971 instead, which also takes priority if both are compiled in.
972
973config X86_64_ACPI_NUMA
Harvey Harrison3c2362e2008-01-30 13:31:03 +0100974 def_bool y
975 prompt "ACPI NUMA detection"
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100976 depends on X86_64 && NUMA && ACPI && PCI
977 select ACPI_NUMA
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100978 help
979 Enable ACPI SRAT based node topology detection.
980
Suresh Siddha6ec6e0d2008-03-25 10:14:35 -0700981# Some NUMA nodes have memory ranges that span
982# other nodes. Even though a pfn is valid and
983# between a node's start and end pfns, it may not
984# reside on that node. See memmap_init_zone()
985# for details.
986config NODES_SPAN_OTHER_NODES
987 def_bool y
988 depends on X86_64_ACPI_NUMA
989
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100990config NUMA_EMU
991 bool "NUMA emulation"
992 depends on X86_64 && NUMA
993 help
994 Enable NUMA emulation. A flat machine will be split
995 into virtual nodes when booted with "numa=fake=N", where N is the
996 number of nodes. This is only useful for debugging.
997
Mike Travis1184dc22008-05-12 21:21:12 +0200998if MAXSMP
999
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001000config NODES_SHIFT
Mike Travis1184dc22008-05-12 21:21:12 +02001001 int
1002 default "9"
1003endif
1004
1005if !MAXSMP
1006config NODES_SHIFT
1007 int "Maximum NUMA Nodes (as a power of 2)"
1008 range 1 9 if X86_64
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001009 default "6" if X86_64
1010 default "4" if X86_NUMAQ
1011 default "3"
1012 depends on NEED_MULTIPLE_NODES
Mike Travis1184dc22008-05-12 21:21:12 +02001013 help
1014 Specify the maximum number of NUMA Nodes available on the target
1015 system. Increases memory reserved to accomodate various tables.
1016endif
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001017
1018config HAVE_ARCH_BOOTMEM_NODE
Harvey Harrison3c2362e2008-01-30 13:31:03 +01001019 def_bool y
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001020 depends on X86_32 && NUMA
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001021
1022config ARCH_HAVE_MEMORY_PRESENT
Harvey Harrison3c2362e2008-01-30 13:31:03 +01001023 def_bool y
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001024 depends on X86_32 && DISCONTIGMEM
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001025
1026config NEED_NODE_MEMMAP_SIZE
Harvey Harrison3c2362e2008-01-30 13:31:03 +01001027 def_bool y
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001028 depends on X86_32 && (DISCONTIGMEM || SPARSEMEM)
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001029
1030config HAVE_ARCH_ALLOC_REMAP
Harvey Harrison3c2362e2008-01-30 13:31:03 +01001031 def_bool y
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001032 depends on X86_32 && NUMA
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001033
1034config ARCH_FLATMEM_ENABLE
1035 def_bool y
Mel Gorman409a7b82008-01-30 13:33:25 +01001036 depends on X86_32 && ARCH_SELECT_MEMORY_MODEL && X86_PC && !NUMA
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001037
1038config ARCH_DISCONTIGMEM_ENABLE
1039 def_bool y
Christoph Lameterb2632952008-01-30 13:30:47 +01001040 depends on NUMA && X86_32
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001041
1042config ARCH_DISCONTIGMEM_DEFAULT
1043 def_bool y
Christoph Lameterb2632952008-01-30 13:30:47 +01001044 depends on NUMA && X86_32
1045
1046config ARCH_SPARSEMEM_DEFAULT
1047 def_bool y
1048 depends on X86_64
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001049
1050config ARCH_SPARSEMEM_ENABLE
1051 def_bool y
Christoph Lameterb2632952008-01-30 13:30:47 +01001052 depends on X86_64 || NUMA || (EXPERIMENTAL && X86_PC)
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001053 select SPARSEMEM_STATIC if X86_32
1054 select SPARSEMEM_VMEMMAP_ENABLE if X86_64
1055
1056config ARCH_SELECT_MEMORY_MODEL
1057 def_bool y
Christoph Lameterb2632952008-01-30 13:30:47 +01001058 depends on ARCH_SPARSEMEM_ENABLE
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001059
1060config ARCH_MEMORY_PROBE
1061 def_bool X86_64
1062 depends on MEMORY_HOTPLUG
1063
1064source "mm/Kconfig"
1065
1066config HIGHPTE
1067 bool "Allocate 3rd-level pagetables from highmem"
1068 depends on X86_32 && (HIGHMEM4G || HIGHMEM64G)
1069 help
1070 The VM uses one page table entry for each page of physical memory.
1071 For systems with a lot of RAM, this can be wasteful of precious
1072 low memory. Setting this option will put user-space page table
1073 entries in high memory.
1074
1075config MATH_EMULATION
1076 bool
1077 prompt "Math emulation" if X86_32
1078 ---help---
1079 Linux can emulate a math coprocessor (used for floating point
1080 operations) if you don't have one. 486DX and Pentium processors have
1081 a math coprocessor built in, 486SX and 386 do not, unless you added
1082 a 487DX or 387, respectively. (The messages during boot time can
1083 give you some hints here ["man dmesg"].) Everyone needs either a
1084 coprocessor or this emulation.
1085
1086 If you don't have a math coprocessor, you need to say Y here; if you
1087 say Y here even though you have a coprocessor, the coprocessor will
1088 be used nevertheless. (This behavior can be changed with the kernel
1089 command line option "no387", which comes handy if your coprocessor
1090 is broken. Try "man bootparam" or see the documentation of your boot
1091 loader (lilo or loadlin) about how to pass options to the kernel at
1092 boot time.) This means that it is a good idea to say Y here if you
1093 intend to use this kernel on different machines.
1094
1095 More information about the internals of the Linux math coprocessor
1096 emulation can be found in <file:arch/x86/math-emu/README>.
1097
1098 If you are not sure, say Y; apart from resulting in a 66 KB bigger
1099 kernel, it won't hurt.
1100
1101config MTRR
1102 bool "MTRR (Memory Type Range Register) support"
1103 ---help---
1104 On Intel P6 family processors (Pentium Pro, Pentium II and later)
1105 the Memory Type Range Registers (MTRRs) may be used to control
1106 processor access to memory ranges. This is most useful if you have
1107 a video (VGA) card on a PCI or AGP bus. Enabling write-combining
1108 allows bus write transfers to be combined into a larger transfer
1109 before bursting over the PCI/AGP bus. This can increase performance
1110 of image write operations 2.5 times or more. Saying Y here creates a
1111 /proc/mtrr file which may be used to manipulate your processor's
1112 MTRRs. Typically the X server should use this.
1113
1114 This code has a reasonably generic interface so that similar
1115 control registers on other processors can be easily supported
1116 as well:
1117
1118 The Cyrix 6x86, 6x86MX and M II processors have Address Range
1119 Registers (ARRs) which provide a similar functionality to MTRRs. For
1120 these, the ARRs are used to emulate the MTRRs.
1121 The AMD K6-2 (stepping 8 and above) and K6-3 processors have two
1122 MTRRs. The Centaur C6 (WinChip) has 8 MCRs, allowing
1123 write-combining. All of these processors are supported by this code
1124 and it makes sense to say Y here if you have one of them.
1125
1126 Saying Y here also fixes a problem with buggy SMP BIOSes which only
1127 set the MTRRs for the boot CPU and not for the secondary CPUs. This
1128 can lead to all sorts of problems, so it's good to say Y here.
1129
1130 You can safely say Y even if your machine doesn't have MTRRs, you'll
1131 just add about 9 KB to your kernel.
1132
1133 See <file:Documentation/mtrr.txt> for more information.
1134
Yinghai Lu95ffa242008-04-29 03:52:33 -07001135config MTRR_SANITIZER
1136 def_bool y
1137 prompt "MTRR cleanup support"
1138 depends on MTRR
1139 help
1140 Convert MTRR layout from continuous to discrete, so some X driver
1141 could add WB entries.
1142
1143 Say N here if you see bootup problems (boot crash, boot hang,
1144 spontaneous reboots).
1145
1146 Could be disabled with disable_mtrr_cleanup. Also mtrr_chunk_size
1147 could be used to send largest mtrr entry size for continuous block
1148 to hold holes (aka. UC entries)
1149
1150 If unsure, say Y.
1151
1152config MTRR_SANITIZER_ENABLE_DEFAULT
Yinghai Luf5098d62008-04-29 20:25:58 -07001153 int "MTRR cleanup enable value (0-1)"
1154 range 0 1
1155 default "0"
Yinghai Lu95ffa242008-04-29 03:52:33 -07001156 depends on MTRR_SANITIZER
1157 help
Yinghai Luf5098d62008-04-29 20:25:58 -07001158 Enable mtrr cleanup default value
Yinghai Lu95ffa242008-04-29 03:52:33 -07001159
Yinghai Lu12031a62008-05-02 02:40:22 -07001160config MTRR_SANITIZER_SPARE_REG_NR_DEFAULT
1161 int "MTRR cleanup spare reg num (0-7)"
1162 range 0 7
1163 default "1"
1164 depends on MTRR_SANITIZER
1165 help
1166 mtrr cleanup spare entries default, it can be changed via
1167 mtrr_spare_reg_nr=
1168
venkatesh.pallipadi@intel.com2e5d9c82008-03-18 17:00:14 -07001169config X86_PAT
Ingo Molnar2a8a2712008-04-26 10:26:52 +02001170 bool
venkatesh.pallipadi@intel.com2e5d9c82008-03-18 17:00:14 -07001171 prompt "x86 PAT support"
Ingo Molnar2a8a2712008-04-26 10:26:52 +02001172 depends on MTRR
venkatesh.pallipadi@intel.com2e5d9c82008-03-18 17:00:14 -07001173 help
1174 Use PAT attributes to setup page level cache control.
Venki Pallipadi042b78e2008-03-24 14:22:35 -07001175
venkatesh.pallipadi@intel.com2e5d9c82008-03-18 17:00:14 -07001176 PATs are the modern equivalents of MTRRs and are much more
1177 flexible than MTRRs.
1178
1179 Say N here if you see bootup problems (boot crash, boot hang,
Venki Pallipadi042b78e2008-03-24 14:22:35 -07001180 spontaneous reboots) or a non-working video driver.
venkatesh.pallipadi@intel.com2e5d9c82008-03-18 17:00:14 -07001181
1182 If unsure, say Y.
1183
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001184config EFI
Harvey Harrison3c2362e2008-01-30 13:31:03 +01001185 def_bool n
Huang, Ying8b2cb7a2008-01-30 13:32:11 +01001186 prompt "EFI runtime service support"
Huang, Ying5b836832008-01-30 13:31:19 +01001187 depends on ACPI
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001188 ---help---
Huang, Ying8b2cb7a2008-01-30 13:32:11 +01001189 This enables the kernel to use EFI runtime services that are
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001190 available (such as the EFI variable services).
1191
Huang, Ying8b2cb7a2008-01-30 13:32:11 +01001192 This option is only useful on systems that have EFI firmware.
1193 In addition, you should use the latest ELILO loader available
1194 at <http://elilo.sourceforge.net> in order to take advantage
1195 of EFI runtime services. However, even with this option, the
1196 resultant kernel should continue to boot on existing non-EFI
1197 platforms.
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001198
1199config IRQBALANCE
Harvey Harrison3c2362e2008-01-30 13:31:03 +01001200 def_bool y
1201 prompt "Enable kernel irq balancing"
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001202 depends on X86_32 && SMP && X86_IO_APIC
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001203 help
1204 The default yes will allow the kernel to do irq load balancing.
1205 Saying no will keep the kernel from doing irq load balancing.
1206
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001207config SECCOMP
Harvey Harrison3c2362e2008-01-30 13:31:03 +01001208 def_bool y
1209 prompt "Enable seccomp to safely compute untrusted bytecode"
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001210 depends on PROC_FS
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001211 help
1212 This kernel feature is useful for number crunching applications
1213 that may need to compute untrusted bytecode during their
1214 execution. By using pipes or other transports made available to
1215 the process as file descriptors supporting the read/write
1216 syscalls, it's possible to isolate those applications in
1217 their own address space using seccomp. Once seccomp is
1218 enabled via /proc/<pid>/seccomp, it cannot be disabled
1219 and the task is only allowed to execute a few safe syscalls
1220 defined by each seccomp mode.
1221
1222 If unsure, say Y. Only embedded should say N here.
1223
1224config CC_STACKPROTECTOR
1225 bool "Enable -fstack-protector buffer overflow detection (EXPERIMENTAL)"
Linus Torvalds2c020a92008-02-22 08:21:38 -08001226 depends on X86_64 && EXPERIMENTAL && BROKEN
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001227 help
1228 This option turns on the -fstack-protector GCC feature. This
1229 feature puts, at the beginning of critical functions, a canary
1230 value on the stack just before the return address, and validates
1231 the value just before actually returning. Stack based buffer
1232 overflows (that need to overwrite this return address) now also
1233 overwrite the canary, which gets detected and the attack is then
1234 neutralized via a kernel panic.
1235
1236 This feature requires gcc version 4.2 or above, or a distribution
1237 gcc with the feature backported. Older versions are automatically
1238 detected and for those versions, this configuration option is ignored.
1239
1240config CC_STACKPROTECTOR_ALL
1241 bool "Use stack-protector for all functions"
1242 depends on CC_STACKPROTECTOR
1243 help
1244 Normally, GCC only inserts the canary value protection for
1245 functions that use large-ish on-stack buffers. By enabling
1246 this option, GCC will be asked to do this for ALL functions.
1247
1248source kernel/Kconfig.hz
1249
1250config KEXEC
1251 bool "kexec system call"
Ingo Molnar3e8f7e32008-04-28 10:46:58 +02001252 depends on X86_BIOS_REBOOT
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001253 help
1254 kexec is a system call that implements the ability to shutdown your
1255 current kernel, and to start another kernel. It is like a reboot
1256 but it is independent of the system firmware. And like a reboot
1257 you can start any kernel with it, not just Linux.
1258
1259 The name comes from the similarity to the exec system call.
1260
1261 It is an ongoing process to be certain the hardware in a machine
1262 is properly shutdown, so do not be surprised if this code does not
1263 initially work for you. It may help to enable device hotplugging
1264 support. As of this writing the exact hardware interface is
1265 strongly in flux, so no good recommendation can be made.
1266
1267config CRASH_DUMP
1268 bool "kernel crash dumps (EXPERIMENTAL)"
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001269 depends on X86_64 || (X86_32 && HIGHMEM)
1270 help
1271 Generate crash dump after being started by kexec.
1272 This should be normally only set in special crash dump kernels
1273 which are loaded in the main kernel with kexec-tools into
1274 a specially reserved region and then later executed after
1275 a crash by kdump/kexec. The crash dump kernel must be compiled
1276 to a memory address not used by the main kernel or BIOS using
1277 PHYSICAL_START, or it must be built as a relocatable image
1278 (CONFIG_RELOCATABLE=y).
1279 For more details see Documentation/kdump/kdump.txt
1280
1281config PHYSICAL_START
1282 hex "Physical address where the kernel is loaded" if (EMBEDDED || CRASH_DUMP)
1283 default "0x1000000" if X86_NUMAQ
1284 default "0x200000" if X86_64
1285 default "0x100000"
1286 help
1287 This gives the physical address where the kernel is loaded.
1288
1289 If kernel is a not relocatable (CONFIG_RELOCATABLE=n) then
1290 bzImage will decompress itself to above physical address and
1291 run from there. Otherwise, bzImage will run from the address where
1292 it has been loaded by the boot loader and will ignore above physical
1293 address.
1294
1295 In normal kdump cases one does not have to set/change this option
1296 as now bzImage can be compiled as a completely relocatable image
1297 (CONFIG_RELOCATABLE=y) and be used to load and run from a different
1298 address. This option is mainly useful for the folks who don't want
1299 to use a bzImage for capturing the crash dump and want to use a
1300 vmlinux instead. vmlinux is not relocatable hence a kernel needs
1301 to be specifically compiled to run from a specific memory area
1302 (normally a reserved region) and this option comes handy.
1303
1304 So if you are using bzImage for capturing the crash dump, leave
1305 the value here unchanged to 0x100000 and set CONFIG_RELOCATABLE=y.
1306 Otherwise if you plan to use vmlinux for capturing the crash dump
1307 change this value to start of the reserved region (Typically 16MB
1308 0x1000000). In other words, it can be set based on the "X" value as
1309 specified in the "crashkernel=YM@XM" command line boot parameter
1310 passed to the panic-ed kernel. Typically this parameter is set as
1311 crashkernel=64M@16M. Please take a look at
1312 Documentation/kdump/kdump.txt for more details about crash dumps.
1313
1314 Usage of bzImage for capturing the crash dump is recommended as
1315 one does not have to build two kernels. Same kernel can be used
1316 as production kernel and capture kernel. Above option should have
1317 gone away after relocatable bzImage support is introduced. But it
1318 is present because there are users out there who continue to use
1319 vmlinux for dump capture. This option should go away down the
1320 line.
1321
1322 Don't change this unless you know what you are doing.
1323
1324config RELOCATABLE
1325 bool "Build a relocatable kernel (EXPERIMENTAL)"
1326 depends on EXPERIMENTAL
1327 help
1328 This builds a kernel image that retains relocation information
1329 so it can be loaded someplace besides the default 1MB.
1330 The relocations tend to make the kernel binary about 10% larger,
1331 but are discarded at runtime.
1332
1333 One use is for the kexec on panic case where the recovery kernel
1334 must live at a different physical address than the primary
1335 kernel.
1336
1337 Note: If CONFIG_RELOCATABLE=y, then the kernel runs from the address
1338 it has been loaded at and the compile time physical address
1339 (CONFIG_PHYSICAL_START) is ignored.
1340
1341config PHYSICAL_ALIGN
1342 hex
1343 prompt "Alignment value to which kernel should be aligned" if X86_32
1344 default "0x100000" if X86_32
1345 default "0x200000" if X86_64
1346 range 0x2000 0x400000
1347 help
1348 This value puts the alignment restrictions on physical address
1349 where kernel is loaded and run from. Kernel is compiled for an
1350 address which meets above alignment restriction.
1351
1352 If bootloader loads the kernel at a non-aligned address and
1353 CONFIG_RELOCATABLE is set, kernel will move itself to nearest
1354 address aligned to above value and run from there.
1355
1356 If bootloader loads the kernel at a non-aligned address and
1357 CONFIG_RELOCATABLE is not set, kernel will ignore the run time
1358 load address and decompress itself to the address it has been
1359 compiled for and run from there. The address for which kernel is
1360 compiled already meets above alignment restrictions. Hence the
1361 end result is that kernel runs from a physical address meeting
1362 above alignment restrictions.
1363
1364 Don't change this unless you know what you are doing.
1365
1366config HOTPLUG_CPU
1367 bool "Support for suspend on SMP and hot-pluggable CPUs (EXPERIMENTAL)"
1368 depends on SMP && HOTPLUG && EXPERIMENTAL && !X86_VOYAGER
1369 ---help---
1370 Say Y here to experiment with turning CPUs off and on, and to
1371 enable suspend on SMP systems. CPUs can be controlled through
1372 /sys/devices/system/cpu.
1373 Say N if you want to disable CPU hotplug and don't need to
1374 suspend.
1375
1376config COMPAT_VDSO
Harvey Harrison3c2362e2008-01-30 13:31:03 +01001377 def_bool y
1378 prompt "Compat VDSO support"
Roland McGrathaf65d642008-01-30 13:30:43 +01001379 depends on X86_32 || IA32_EMULATION
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001380 help
Roland McGrathaf65d642008-01-30 13:30:43 +01001381 Map the 32-bit VDSO to the predictable old-style address too.
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001382 ---help---
1383 Say N here if you are running a sufficiently recent glibc
1384 version (2.3.3 or later), to remove the high-mapped
1385 VDSO mapping and to exclusively use the randomized VDSO.
1386
1387 If unsure, say Y.
1388
1389endmenu
1390
1391config ARCH_ENABLE_MEMORY_HOTPLUG
1392 def_bool y
1393 depends on X86_64 || (X86_32 && HIGHMEM)
1394
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001395config HAVE_ARCH_EARLY_PFN_TO_NID
1396 def_bool X86_64
1397 depends on NUMA
1398
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001399menu "Power management options"
1400 depends on !X86_VOYAGER
1401
1402config ARCH_HIBERNATION_HEADER
Harvey Harrison3c2362e2008-01-30 13:31:03 +01001403 def_bool y
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001404 depends on X86_64 && HIBERNATION
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001405
1406source "kernel/power/Kconfig"
1407
1408source "drivers/acpi/Kconfig"
1409
Andi Kleena6b68072008-01-30 13:32:49 +01001410config X86_APM_BOOT
1411 bool
1412 default y
1413 depends on APM || APM_MODULE
1414
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001415menuconfig APM
1416 tristate "APM (Advanced Power Management) BIOS support"
1417 depends on X86_32 && PM_SLEEP && !X86_VISWS
1418 ---help---
1419 APM is a BIOS specification for saving power using several different
1420 techniques. This is mostly useful for battery powered laptops with
1421 APM compliant BIOSes. If you say Y here, the system time will be
1422 reset after a RESUME operation, the /proc/apm device will provide
1423 battery status information, and user-space programs will receive
1424 notification of APM "events" (e.g. battery status change).
1425
1426 If you select "Y" here, you can disable actual use of the APM
1427 BIOS by passing the "apm=off" option to the kernel at boot time.
1428
1429 Note that the APM support is almost completely disabled for
1430 machines with more than one CPU.
1431
1432 In order to use APM, you will need supporting software. For location
Randy Dunlap53471122008-03-12 18:10:51 -04001433 and more information, read <file:Documentation/power/pm.txt> and the
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001434 Battery Powered Linux mini-HOWTO, available from
1435 <http://www.tldp.org/docs.html#howto>.
1436
1437 This driver does not spin down disk drives (see the hdparm(8)
1438 manpage ("man 8 hdparm") for that), and it doesn't turn off
1439 VESA-compliant "green" monitors.
1440
1441 This driver does not support the TI 4000M TravelMate and the ACER
1442 486/DX4/75 because they don't have compliant BIOSes. Many "green"
1443 desktop machines also don't have compliant BIOSes, and this driver
1444 may cause those machines to panic during the boot phase.
1445
1446 Generally, if you don't have a battery in your machine, there isn't
1447 much point in using this driver and you should say N. If you get
1448 random kernel OOPSes or reboots that don't seem to be related to
1449 anything, try disabling/enabling this option (or disabling/enabling
1450 APM in your BIOS).
1451
1452 Some other things you should try when experiencing seemingly random,
1453 "weird" problems:
1454
1455 1) make sure that you have enough swap space and that it is
1456 enabled.
1457 2) pass the "no-hlt" option to the kernel
1458 3) switch on floating point emulation in the kernel and pass
1459 the "no387" option to the kernel
1460 4) pass the "floppy=nodma" option to the kernel
1461 5) pass the "mem=4M" option to the kernel (thereby disabling
1462 all but the first 4 MB of RAM)
1463 6) make sure that the CPU is not over clocked.
1464 7) read the sig11 FAQ at <http://www.bitwizard.nl/sig11/>
1465 8) disable the cache from your BIOS settings
1466 9) install a fan for the video card or exchange video RAM
1467 10) install a better fan for the CPU
1468 11) exchange RAM chips
1469 12) exchange the motherboard.
1470
1471 To compile this driver as a module, choose M here: the
1472 module will be called apm.
1473
1474if APM
1475
1476config APM_IGNORE_USER_SUSPEND
1477 bool "Ignore USER SUSPEND"
1478 help
1479 This option will ignore USER SUSPEND requests. On machines with a
1480 compliant APM BIOS, you want to say N. However, on the NEC Versa M
1481 series notebooks, it is necessary to say Y because of a BIOS bug.
1482
1483config APM_DO_ENABLE
1484 bool "Enable PM at boot time"
1485 ---help---
1486 Enable APM features at boot time. From page 36 of the APM BIOS
1487 specification: "When disabled, the APM BIOS does not automatically
1488 power manage devices, enter the Standby State, enter the Suspend
1489 State, or take power saving steps in response to CPU Idle calls."
1490 This driver will make CPU Idle calls when Linux is idle (unless this
1491 feature is turned off -- see "Do CPU IDLE calls", below). This
1492 should always save battery power, but more complicated APM features
1493 will be dependent on your BIOS implementation. You may need to turn
1494 this option off if your computer hangs at boot time when using APM
1495 support, or if it beeps continuously instead of suspending. Turn
1496 this off if you have a NEC UltraLite Versa 33/C or a Toshiba
1497 T400CDT. This is off by default since most machines do fine without
1498 this feature.
1499
1500config APM_CPU_IDLE
1501 bool "Make CPU Idle calls when idle"
1502 help
1503 Enable calls to APM CPU Idle/CPU Busy inside the kernel's idle loop.
1504 On some machines, this can activate improved power savings, such as
1505 a slowed CPU clock rate, when the machine is idle. These idle calls
1506 are made after the idle loop has run for some length of time (e.g.,
1507 333 mS). On some machines, this will cause a hang at boot time or
1508 whenever the CPU becomes idle. (On machines with more than one CPU,
1509 this option does nothing.)
1510
1511config APM_DISPLAY_BLANK
1512 bool "Enable console blanking using APM"
1513 help
1514 Enable console blanking using the APM. Some laptops can use this to
1515 turn off the LCD backlight when the screen blanker of the Linux
1516 virtual console blanks the screen. Note that this is only used by
1517 the virtual console screen blanker, and won't turn off the backlight
1518 when using the X Window system. This also doesn't have anything to
1519 do with your VESA-compliant power-saving monitor. Further, this
1520 option doesn't work for all laptops -- it might not turn off your
1521 backlight at all, or it might print a lot of errors to the console,
1522 especially if you are using gpm.
1523
1524config APM_ALLOW_INTS
1525 bool "Allow interrupts during APM BIOS calls"
1526 help
1527 Normally we disable external interrupts while we are making calls to
1528 the APM BIOS as a measure to lessen the effects of a badly behaving
1529 BIOS implementation. The BIOS should reenable interrupts if it
1530 needs to. Unfortunately, some BIOSes do not -- especially those in
1531 many of the newer IBM Thinkpads. If you experience hangs when you
1532 suspend, try setting this to Y. Otherwise, say N.
1533
1534config APM_REAL_MODE_POWER_OFF
1535 bool "Use real mode APM BIOS call to power off"
1536 help
1537 Use real mode APM BIOS calls to switch off the computer. This is
1538 a work-around for a number of buggy BIOSes. Switch this option on if
1539 your computer crashes instead of powering off properly.
1540
1541endif # APM
1542
1543source "arch/x86/kernel/cpu/cpufreq/Kconfig"
1544
1545source "drivers/cpuidle/Kconfig"
1546
1547endmenu
1548
1549
1550menu "Bus options (PCI etc.)"
1551
1552config PCI
Ingo Molnar1ac97012008-05-19 14:10:14 +02001553 bool "PCI support"
Adrian Bunk1c858082008-01-30 13:32:32 +01001554 default y
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001555 select ARCH_SUPPORTS_MSI if (X86_LOCAL_APIC && X86_IO_APIC)
1556 help
1557 Find out whether you have a PCI motherboard. PCI is the name of a
1558 bus system, i.e. the way the CPU talks to the other stuff inside
1559 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
1560 VESA. If you have PCI, say Y, otherwise N.
1561
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001562choice
1563 prompt "PCI access mode"
1564 depends on X86_32 && PCI && !X86_VISWS
1565 default PCI_GOANY
1566 ---help---
1567 On PCI systems, the BIOS can be used to detect the PCI devices and
1568 determine their configuration. However, some old PCI motherboards
1569 have BIOS bugs and may crash if this is done. Also, some embedded
1570 PCI-based systems don't have any BIOS at all. Linux can also try to
1571 detect the PCI hardware directly without using the BIOS.
1572
1573 With this option, you can specify how Linux should detect the
1574 PCI devices. If you choose "BIOS", the BIOS will be used,
1575 if you choose "Direct", the BIOS won't be used, and if you
1576 choose "MMConfig", then PCI Express MMCONFIG will be used.
1577 If you choose "Any", the kernel will try MMCONFIG, then the
1578 direct access method and falls back to the BIOS if that doesn't
1579 work. If unsure, go with the default, which is "Any".
1580
1581config PCI_GOBIOS
1582 bool "BIOS"
1583
1584config PCI_GOMMCONFIG
1585 bool "MMConfig"
1586
1587config PCI_GODIRECT
1588 bool "Direct"
1589
Andres Salomon3ef0e1f2008-04-29 00:59:53 -07001590config PCI_GOOLPC
1591 bool "OLPC"
1592 depends on OLPC
1593
Andres Salomon2bdd1b02008-06-05 14:14:41 -07001594config PCI_GOANY
1595 bool "Any"
1596
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001597endchoice
1598
1599config PCI_BIOS
Harvey Harrison3c2362e2008-01-30 13:31:03 +01001600 def_bool y
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001601 depends on X86_32 && !X86_VISWS && PCI && (PCI_GOBIOS || PCI_GOANY)
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001602
1603# x86-64 doesn't support PCI BIOS access from long mode so always go direct.
1604config PCI_DIRECT
Harvey Harrison3c2362e2008-01-30 13:31:03 +01001605 def_bool y
Andres Salomon3ef0e1f2008-04-29 00:59:53 -07001606 depends on PCI && (X86_64 || (PCI_GODIRECT || PCI_GOANY || PCI_GOOLPC) || X86_VISWS)
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001607
1608config PCI_MMCONFIG
Harvey Harrison3c2362e2008-01-30 13:31:03 +01001609 def_bool y
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001610 depends on X86_32 && PCI && ACPI && (PCI_GOMMCONFIG || PCI_GOANY)
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001611
Andres Salomon3ef0e1f2008-04-29 00:59:53 -07001612config PCI_OLPC
Andres Salomon2bdd1b02008-06-05 14:14:41 -07001613 def_bool y
1614 depends on PCI && OLPC && (PCI_GOOLPC || PCI_GOANY)
Andres Salomon3ef0e1f2008-04-29 00:59:53 -07001615
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001616config PCI_DOMAINS
Harvey Harrison3c2362e2008-01-30 13:31:03 +01001617 def_bool y
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001618 depends on PCI
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001619
1620config PCI_MMCONFIG
1621 bool "Support mmconfig PCI config space access"
1622 depends on X86_64 && PCI && ACPI
1623
1624config DMAR
1625 bool "Support for DMA Remapping Devices (EXPERIMENTAL)"
1626 depends on X86_64 && PCI_MSI && ACPI && EXPERIMENTAL
1627 help
1628 DMA remapping (DMAR) devices support enables independent address
1629 translations for Direct Memory Access (DMA) from devices.
1630 These DMA remapping devices are reported via ACPI tables
1631 and include PCI device scope covered by these DMA
1632 remapping devices.
1633
1634config DMAR_GFX_WA
Harvey Harrison3c2362e2008-01-30 13:31:03 +01001635 def_bool y
1636 prompt "Support for Graphics workaround"
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001637 depends on DMAR
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001638 help
1639 Current Graphics drivers tend to use physical address
1640 for DMA and avoid using DMA APIs. Setting this config
1641 option permits the IOMMU driver to set a unity map for
1642 all the OS-visible memory. Hence the driver can continue
1643 to use physical addresses for DMA.
1644
1645config DMAR_FLOPPY_WA
Harvey Harrison3c2362e2008-01-30 13:31:03 +01001646 def_bool y
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001647 depends on DMAR
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001648 help
1649 Floppy disk drivers are know to bypass DMA API calls
1650 thereby failing to work when IOMMU is enabled. This
1651 workaround will setup a 1:1 mapping for the first
1652 16M to make floppy (an ISA device) work.
1653
1654source "drivers/pci/pcie/Kconfig"
1655
1656source "drivers/pci/Kconfig"
1657
1658# x86_64 have no ISA slots, but do have ISA-style DMA.
1659config ISA_DMA_API
Harvey Harrison3c2362e2008-01-30 13:31:03 +01001660 def_bool y
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001661
1662if X86_32
1663
1664config ISA
1665 bool "ISA support"
1666 depends on !(X86_VOYAGER || X86_VISWS)
1667 help
1668 Find out whether you have ISA slots on your motherboard. ISA is the
1669 name of a bus system, i.e. the way the CPU talks to the other stuff
1670 inside your box. Other bus systems are PCI, EISA, MicroChannel
1671 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
1672 newer boards don't support it. If you have ISA, say Y, otherwise N.
1673
1674config EISA
1675 bool "EISA support"
1676 depends on ISA
1677 ---help---
1678 The Extended Industry Standard Architecture (EISA) bus was
1679 developed as an open alternative to the IBM MicroChannel bus.
1680
1681 The EISA bus provided some of the features of the IBM MicroChannel
1682 bus while maintaining backward compatibility with cards made for
1683 the older ISA bus. The EISA bus saw limited use between 1988 and
1684 1995 when it was made obsolete by the PCI bus.
1685
1686 Say Y here if you are building a kernel for an EISA-based machine.
1687
1688 Otherwise, say N.
1689
1690source "drivers/eisa/Kconfig"
1691
1692config MCA
1693 bool "MCA support" if !(X86_VISWS || X86_VOYAGER)
1694 default y if X86_VOYAGER
1695 help
1696 MicroChannel Architecture is found in some IBM PS/2 machines and
1697 laptops. It is a bus system similar to PCI or ISA. See
1698 <file:Documentation/mca.txt> (and especially the web page given
1699 there) before attempting to build an MCA bus kernel.
1700
1701source "drivers/mca/Kconfig"
1702
1703config SCx200
1704 tristate "NatSemi SCx200 support"
1705 depends on !X86_VOYAGER
1706 help
1707 This provides basic support for National Semiconductor's
1708 (now AMD's) Geode processors. The driver probes for the
1709 PCI-IDs of several on-chip devices, so its a good dependency
1710 for other scx200_* drivers.
1711
1712 If compiled as a module, the driver is named scx200.
1713
1714config SCx200HR_TIMER
1715 tristate "NatSemi SCx200 27MHz High-Resolution Timer Support"
1716 depends on SCx200 && GENERIC_TIME
1717 default y
1718 help
1719 This driver provides a clocksource built upon the on-chip
1720 27MHz high-resolution timer. Its also a workaround for
1721 NSC Geode SC-1100's buggy TSC, which loses time when the
1722 processor goes idle (as is done by the scheduler). The
1723 other workaround is idle=poll boot option.
1724
1725config GEODE_MFGPT_TIMER
Harvey Harrison3c2362e2008-01-30 13:31:03 +01001726 def_bool y
1727 prompt "Geode Multi-Function General Purpose Timer (MFGPT) events"
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001728 depends on MGEODE_LX && GENERIC_TIME && GENERIC_CLOCKEVENTS
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001729 help
1730 This driver provides a clock event source based on the MFGPT
1731 timer(s) in the CS5535 and CS5536 companion chip for the geode.
1732 MFGPTs have a better resolution and max interval than the
1733 generic PIT, and are suitable for use as high-res timers.
1734
Andres Salomon3ef0e1f2008-04-29 00:59:53 -07001735config OLPC
1736 bool "One Laptop Per Child support"
1737 default n
1738 help
1739 Add support for detecting the unique features of the OLPC
1740 XO hardware.
1741
Sam Ravnborgbc0120f2007-11-06 23:10:39 +01001742endif # X86_32
1743
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001744config K8_NB
1745 def_bool y
Sam Ravnborgbc0120f2007-11-06 23:10:39 +01001746 depends on AGP_AMD64 || (X86_64 && (GART_IOMMU || (PCI && NUMA)))
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001747
1748source "drivers/pcmcia/Kconfig"
1749
1750source "drivers/pci/hotplug/Kconfig"
1751
1752endmenu
1753
1754
1755menu "Executable file formats / Emulations"
1756
1757source "fs/Kconfig.binfmt"
1758
1759config IA32_EMULATION
1760 bool "IA32 Emulation"
1761 depends on X86_64
Roland McGratha97f52e2008-01-30 13:31:55 +01001762 select COMPAT_BINFMT_ELF
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001763 help
1764 Include code to run 32-bit programs under a 64-bit kernel. You should
1765 likely turn this on, unless you're 100% sure that you don't have any
1766 32-bit programs left.
1767
1768config IA32_AOUT
1769 tristate "IA32 a.out support"
David Howellsb0b933c2008-02-08 04:19:27 -08001770 depends on IA32_EMULATION && ARCH_SUPPORTS_AOUT
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001771 help
1772 Support old a.out binaries in the 32bit emulation.
1773
1774config COMPAT
Harvey Harrison3c2362e2008-01-30 13:31:03 +01001775 def_bool y
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001776 depends on IA32_EMULATION
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001777
1778config COMPAT_FOR_U64_ALIGNMENT
1779 def_bool COMPAT
1780 depends on X86_64
1781
1782config SYSVIPC_COMPAT
Harvey Harrison3c2362e2008-01-30 13:31:03 +01001783 def_bool y
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001784 depends on X86_64 && COMPAT && SYSVIPC
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001785
1786endmenu
1787
1788
1789source "net/Kconfig"
1790
1791source "drivers/Kconfig"
1792
1793source "drivers/firmware/Kconfig"
1794
1795source "fs/Kconfig"
1796
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001797source "arch/x86/Kconfig.debug"
1798
1799source "security/Kconfig"
1800
1801source "crypto/Kconfig"
1802
Avi Kivityedf88412007-12-16 11:02:48 +02001803source "arch/x86/kvm/Kconfig"
1804
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001805source "lib/Kconfig"