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