blob: 2e325521e5e95f992402b2b301fbf466cc851df1 [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
Glauber de Oliveira Costa4fe29a82008-03-19 14:25:23 -0300124 def_bool X86_64 || (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
233choice
234 prompt "Subarchitecture Type"
235 default X86_PC
236
237config X86_PC
238 bool "PC-compatible"
239 help
240 Choose this option if your computer is a standard PC or compatible.
241
242config X86_ELAN
243 bool "AMD Elan"
244 depends on X86_32
245 help
246 Select this for an AMD Elan processor.
247
248 Do not use this option for K6/Athlon/Opteron processors!
249
250 If unsure, choose "PC-compatible" instead.
251
252config X86_VOYAGER
253 bool "Voyager (NCR)"
Roman Zippel823c2482008-02-29 05:09:02 +0100254 depends on X86_32 && (SMP || BROKEN)
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100255 help
256 Voyager is an MCA-based 32-way capable SMP architecture proprietary
257 to NCR Corp. Machine classes 345x/35xx/4100/51xx are Voyager-based.
258
259 *** WARNING ***
260
261 If you do not specifically know you have a Voyager based machine,
262 say N here, otherwise the kernel you build will not be bootable.
263
264config X86_NUMAQ
265 bool "NUMAQ (IBM/Sequent)"
Roman Zippel823c2482008-02-29 05:09:02 +0100266 depends on SMP && X86_32
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100267 select NUMA
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100268 help
269 This option is used for getting Linux to run on a (IBM/Sequent) NUMA
270 multiquad box. This changes the way that processors are bootstrapped,
271 and uses Clustered Logical APIC addressing mode instead of Flat Logical.
272 You will need a new lynxer.elf file to flash your firmware with - send
273 email to <Martin.Bligh@us.ibm.com>.
274
275config X86_SUMMIT
276 bool "Summit/EXA (IBM x440)"
277 depends on X86_32 && SMP
278 help
279 This option is needed for IBM systems that use the Summit/EXA chipset.
280 In particular, it is needed for the x440.
281
282 If you don't have one of these computers, you should say N here.
283 If you want to build a NUMA kernel, you must select ACPI.
284
285config X86_BIGSMP
286 bool "Support for other sub-arch SMP systems with more than 8 CPUs"
287 depends on X86_32 && SMP
288 help
289 This option is needed for the systems that have more than 8 CPUs
290 and if the system is not of any sub-arch type above.
291
292 If you don't have such a system, you should say N here.
293
294config X86_VISWS
295 bool "SGI 320/540 (Visual Workstation)"
296 depends on X86_32
297 help
298 The SGI Visual Workstation series is an IA32-based workstation
299 based on SGI systems chips with some legacy PC hardware attached.
300
301 Say Y here to create a kernel to run on the SGI 320 or 540.
302
303 A kernel compiled for the Visual Workstation will not run on PCs
304 and vice versa. See <file:Documentation/sgi-visws.txt> for details.
305
306config X86_GENERICARCH
307 bool "Generic architecture (Summit, bigsmp, ES7000, default)"
308 depends on X86_32
309 help
310 This option compiles in the Summit, bigsmp, ES7000, default subarchitectures.
311 It is intended for a generic binary kernel.
312 If you want a NUMA kernel, select ACPI. We need SRAT for NUMA.
313
314config X86_ES7000
315 bool "Support for Unisys ES7000 IA32 series"
316 depends on X86_32 && SMP
317 help
318 Support for Unisys ES7000 systems. Say 'Y' here if this kernel is
319 supposed to run on an IA32-based Unisys ES7000 system.
320 Only choose this option if you have such a system, otherwise you
321 should say N here.
322
Florian Fainelli5e3a77e2008-01-30 13:33:36 +0100323config X86_RDC321X
324 bool "RDC R-321x SoC"
325 depends on X86_32
326 select M486
327 select X86_REBOOTFIXUPS
328 select GENERIC_GPIO
Florian Fainelli4cf31842008-02-04 16:47:55 +0100329 select LEDS_CLASS
Florian Fainelli5e3a77e2008-01-30 13:33:36 +0100330 select LEDS_GPIO
Ingo Molnar82fd8662008-05-01 03:46:22 +0200331 select NEW_LEDS
Florian Fainelli5e3a77e2008-01-30 13:33:36 +0100332 help
333 This option is needed for RDC R-321x system-on-chip, also known
334 as R-8610-(G).
335 If you don't have one of these chips, you should say N here.
336
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100337config X86_VSMP
338 bool "Support for ScaleMP vSMP"
Glauber Costa96597fd2008-02-11 17:16:04 -0200339 select PARAVIRT
Roman Zippel823c2482008-02-29 05:09:02 +0100340 depends on X86_64
Glauber Costa96597fd2008-02-11 17:16:04 -0200341 help
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100342 Support for ScaleMP vSMP systems. Say 'Y' here if this kernel is
343 supposed to run on these EM64T-based machines. Only choose this option
344 if you have one of these machines.
345
346endchoice
347
348config SCHED_NO_NO_OMIT_FRAME_POINTER
Harvey Harrison3c2362e2008-01-30 13:31:03 +0100349 def_bool y
350 prompt "Single-depth WCHAN output"
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100351 depends on X86_32
352 help
353 Calculate simpler /proc/<PID>/wchan values. If this option
354 is disabled then wchan values will recurse back to the
355 caller function. This provides more accurate wchan values,
356 at the expense of slightly more scheduling overhead.
357
358 If in doubt, say "Y".
359
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100360menuconfig PARAVIRT_GUEST
361 bool "Paravirtualized guest support"
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100362 help
363 Say Y here to get to see options related to running Linux under
364 various hypervisors. This option alone does not add any kernel code.
365
366 If you say N, all options in this submenu will be skipped and disabled.
367
368if PARAVIRT_GUEST
369
370source "arch/x86/xen/Kconfig"
371
372config VMI
373 bool "VMI Guest support"
374 select PARAVIRT
Eduardo Pereira Habkost42d545c2008-01-30 13:33:32 +0100375 depends on X86_32
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100376 depends on !(X86_VISWS || X86_VOYAGER)
377 help
378 VMI provides a paravirtualized interface to the VMware ESX server
379 (it could be used by other hypervisors in theory too, but is not
380 at the moment), by linking the kernel to a GPL-ed ROM module
381 provided by the hypervisor.
382
Glauber de Oliveira Costa790c73f2008-02-15 17:52:48 -0200383config KVM_CLOCK
384 bool "KVM paravirtualized clock"
385 select PARAVIRT
Gerd Hoffmannf6e16d52008-06-03 16:17:32 +0200386 select PARAVIRT_CLOCK
Glauber de Oliveira Costa790c73f2008-02-15 17:52:48 -0200387 depends on !(X86_VISWS || X86_VOYAGER)
388 help
389 Turning on this option will allow you to run a paravirtualized clock
390 when running over the KVM hypervisor. Instead of relying on a PIT
391 (or probably other) emulation by the underlying device model, the host
392 provides the guest with timing infrastructure such as time of day, and
393 system time
394
Marcelo Tosatti0cf1bfd2008-02-22 12:21:36 -0500395config KVM_GUEST
396 bool "KVM Guest support"
397 select PARAVIRT
398 depends on !(X86_VISWS || X86_VOYAGER)
399 help
400 This option enables various optimizations for running under the KVM
401 hypervisor.
402
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100403source "arch/x86/lguest/Kconfig"
404
Eduardo Pereira Habkoste61bd942008-01-30 13:33:32 +0100405config PARAVIRT
406 bool "Enable paravirtualization code"
Eduardo Pereira Habkost42d545c2008-01-30 13:33:32 +0100407 depends on !(X86_VISWS || X86_VOYAGER)
Eduardo Pereira Habkoste61bd942008-01-30 13:33:32 +0100408 help
409 This changes the kernel so it can modify itself when it is run
410 under a hypervisor, potentially improving performance significantly
411 over full virtualization. However, when run without a hypervisor
412 the kernel is theoretically slower and slightly larger.
413
Gerd Hoffmann7af192c2008-06-03 16:17:29 +0200414config PARAVIRT_CLOCK
415 bool
416 default n
417
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100418endif
419
Yinghai Luc64df702008-03-21 18:56:19 -0700420config MEMTEST_BOOTPARAM
421 bool "Memtest boot parameter"
422 depends on X86_64
423 default y
424 help
425 This option adds a kernel parameter 'memtest', which allows memtest
426 to be disabled at boot. If this option is selected, memtest
427 functionality can be disabled with memtest=0 on the kernel
428 command line. The purpose of this option is to allow a single
429 kernel image to be distributed with memtest built in, but not
430 necessarily enabled.
431
432 If you are unsure how to answer this question, answer Y.
433
434config MEMTEST_BOOTPARAM_VALUE
435 int "Memtest boot parameter default value (0-4)"
436 depends on MEMTEST_BOOTPARAM
437 range 0 4
438 default 0
439 help
440 This option sets the default value for the kernel parameter
441 'memtest', which allows memtest to be disabled at boot. If this
442 option is set to 0 (zero), the memtest kernel parameter will
443 default to 0, disabling memtest at bootup. If this option is
444 set to 4, the memtest kernel parameter will default to 4,
445 enabling memtest at bootup, and use that as pattern number.
446
447 If you are unsure how to answer this question, answer 0.
448
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100449config ACPI_SRAT
Harvey Harrison3c2362e2008-01-30 13:31:03 +0100450 def_bool y
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100451 depends on X86_32 && ACPI && NUMA && (X86_SUMMIT || X86_GENERICARCH)
452 select ACPI_NUMA
453
454config HAVE_ARCH_PARSE_SRAT
Harvey Harrison3c2362e2008-01-30 13:31:03 +0100455 def_bool y
456 depends on ACPI_SRAT
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100457
458config X86_SUMMIT_NUMA
Harvey Harrison3c2362e2008-01-30 13:31:03 +0100459 def_bool y
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100460 depends on X86_32 && NUMA && (X86_SUMMIT || X86_GENERICARCH)
461
462config X86_CYCLONE_TIMER
Harvey Harrison3c2362e2008-01-30 13:31:03 +0100463 def_bool y
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100464 depends on X86_32 && X86_SUMMIT || X86_GENERICARCH
465
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
552# need this always selected by IOMMU for the VIA workaround
553config SWIOTLB
554 bool
555 help
556 Support for software bounce buffers used on x86-64 systems
557 which don't have a hardware IOMMU (e.g. the current generation
558 of Intel's x86-64 CPUs). Using this PCI devices which can only
559 access 32-bits of memory can be used on systems with more than
560 3 GB of memory. If unsure, say Y.
561
FUJITA Tomonoria8522502008-04-29 00:59:36 -0700562config IOMMU_HELPER
563 def_bool (CALGARY_IOMMU || GART_IOMMU || SWIOTLB)
Mike Travis1184dc22008-05-12 21:21:12 +0200564config MAXSMP
565 bool "Configure Maximum number of SMP Processors and NUMA Nodes"
566 depends on X86_64 && SMP
567 default n
568 help
569 Configure maximum number of CPUS and NUMA Nodes for this architecture.
570 If unsure, say N.
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100571
Mike Travis1184dc22008-05-12 21:21:12 +0200572if MAXSMP
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100573config NR_CPUS
Mike Travis1184dc22008-05-12 21:21:12 +0200574 int
575 default "4096"
576endif
577
578if !MAXSMP
579config NR_CPUS
580 int "Maximum number of CPUs (2-4096)"
581 range 2 4096
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100582 depends on SMP
583 default "32" if X86_NUMAQ || X86_SUMMIT || X86_BIGSMP || X86_ES7000
584 default "8"
585 help
586 This allows you to specify the maximum number of CPUs which this
Mike Travis1184dc22008-05-12 21:21:12 +0200587 kernel will support. The maximum supported value is 4096 and the
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100588 minimum value which makes sense is 2.
589
590 This is purely to save memory - each supported CPU adds
591 approximately eight kilobytes to the kernel image.
Mike Travis1184dc22008-05-12 21:21:12 +0200592endif
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100593
594config SCHED_SMT
595 bool "SMT (Hyperthreading) scheduler support"
Hiroshi Shimamotob089c122008-02-27 13:16:30 -0800596 depends on X86_HT
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100597 help
598 SMT scheduler support improves the CPU scheduler's decision making
599 when dealing with Intel Pentium 4 chips with HyperThreading at a
600 cost of slightly increased overhead in some places. If unsure say
601 N here.
602
603config SCHED_MC
Harvey Harrison3c2362e2008-01-30 13:31:03 +0100604 def_bool y
605 prompt "Multi-core scheduler support"
Hiroshi Shimamotob089c122008-02-27 13:16:30 -0800606 depends on X86_HT
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100607 help
608 Multi-core scheduler support improves the CPU scheduler's decision
609 making when dealing with multi-core CPU chips at a cost of slightly
610 increased overhead in some places. If unsure say N here.
611
612source "kernel/Kconfig.preempt"
613
614config X86_UP_APIC
615 bool "Local APIC support on uniprocessors"
616 depends on X86_32 && !SMP && !(X86_VISWS || X86_VOYAGER || X86_GENERICARCH)
617 help
618 A local APIC (Advanced Programmable Interrupt Controller) is an
619 integrated interrupt controller in the CPU. If you have a single-CPU
620 system which has a processor with a local APIC, you can say Y here to
621 enable and use it. If you say Y here even though your machine doesn't
622 have a local APIC, then the kernel will still run with no slowdown at
623 all. The local APIC supports CPU-generated self-interrupts (timer,
624 performance counters), and the NMI watchdog which detects hard
625 lockups.
626
627config X86_UP_IOAPIC
628 bool "IO-APIC support on uniprocessors"
629 depends on X86_UP_APIC
630 help
631 An IO-APIC (I/O Advanced Programmable Interrupt Controller) is an
632 SMP-capable replacement for PC-style interrupt controllers. Most
633 SMP systems and many recent uniprocessor systems have one.
634
635 If you have a single-CPU system with an IO-APIC, you can say Y here
636 to use it. If you say Y here even though your machine doesn't have
637 an IO-APIC, then the kernel will still run with no slowdown at all.
638
639config X86_LOCAL_APIC
Harvey Harrison3c2362e2008-01-30 13:31:03 +0100640 def_bool y
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100641 depends on X86_64 || (X86_32 && (X86_UP_APIC || ((X86_VISWS || SMP) && !X86_VOYAGER) || X86_GENERICARCH))
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100642
643config X86_IO_APIC
Harvey Harrison3c2362e2008-01-30 13:31:03 +0100644 def_bool y
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100645 depends on X86_64 || (X86_32 && (X86_UP_IOAPIC || (SMP && !(X86_VISWS || X86_VOYAGER)) || X86_GENERICARCH))
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100646
647config X86_VISWS_APIC
Harvey Harrison3c2362e2008-01-30 13:31:03 +0100648 def_bool y
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100649 depends on X86_32 && X86_VISWS
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100650
651config X86_MCE
652 bool "Machine Check Exception"
653 depends on !X86_VOYAGER
654 ---help---
655 Machine Check Exception support allows the processor to notify the
656 kernel if it detects a problem (e.g. overheating, component failure).
657 The action the kernel takes depends on the severity of the problem,
658 ranging from a warning message on the console, to halting the machine.
659 Your processor must be a Pentium or newer to support this - check the
660 flags in /proc/cpuinfo for mce. Note that some older Pentium systems
661 have a design flaw which leads to false MCE events - hence MCE is
662 disabled on all P5 processors, unless explicitly enabled with "mce"
663 as a boot argument. Similarly, if MCE is built in and creates a
664 problem on some new non-standard machine, you can boot with "nomce"
665 to disable it. MCE support simply ignores non-MCE processors like
666 the 386 and 486, so nearly everyone can say Y here.
667
668config X86_MCE_INTEL
Harvey Harrison3c2362e2008-01-30 13:31:03 +0100669 def_bool y
670 prompt "Intel MCE features"
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100671 depends on X86_64 && X86_MCE && X86_LOCAL_APIC
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100672 help
673 Additional support for intel specific MCE features such as
674 the thermal monitor.
675
676config X86_MCE_AMD
Harvey Harrison3c2362e2008-01-30 13:31:03 +0100677 def_bool y
678 prompt "AMD MCE features"
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100679 depends on X86_64 && X86_MCE && X86_LOCAL_APIC
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100680 help
681 Additional support for AMD specific MCE features such as
682 the DRAM Error Threshold.
683
684config X86_MCE_NONFATAL
685 tristate "Check for non-fatal errors on AMD Athlon/Duron / Intel Pentium 4"
686 depends on X86_32 && X86_MCE
687 help
688 Enabling this feature starts a timer that triggers every 5 seconds which
689 will look at the machine check registers to see if anything happened.
690 Non-fatal problems automatically get corrected (but still logged).
691 Disable this if you don't want to see these messages.
692 Seeing the messages this option prints out may be indicative of dying
693 or out-of-spec (ie, overclocked) hardware.
694 This option only does something on certain CPUs.
695 (AMD Athlon/Duron and Intel Pentium 4)
696
697config X86_MCE_P4THERMAL
698 bool "check for P4 thermal throttling interrupt."
699 depends on X86_32 && X86_MCE && (X86_UP_APIC || SMP) && !X86_VISWS
700 help
701 Enabling this feature will cause a message to be printed when the P4
702 enters thermal throttling.
703
704config VM86
705 bool "Enable VM86 support" if EMBEDDED
706 default y
707 depends on X86_32
708 help
709 This option is required by programs like DOSEMU to run 16-bit legacy
710 code on X86 processors. It also may be needed by software like
711 XFree86 to initialize some video cards via BIOS. Disabling this
712 option saves about 6k.
713
714config TOSHIBA
715 tristate "Toshiba Laptop support"
716 depends on X86_32
717 ---help---
718 This adds a driver to safely access the System Management Mode of
719 the CPU on Toshiba portables with a genuine Toshiba BIOS. It does
720 not work on models with a Phoenix BIOS. The System Management Mode
721 is used to set the BIOS and power saving options on Toshiba portables.
722
723 For information on utilities to make use of this driver see the
724 Toshiba Linux utilities web site at:
725 <http://www.buzzard.org.uk/toshiba/>.
726
727 Say Y if you intend to run this kernel on a Toshiba portable.
728 Say N otherwise.
729
730config I8K
731 tristate "Dell laptop support"
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100732 ---help---
733 This adds a driver to safely access the System Management Mode
734 of the CPU on the Dell Inspiron 8000. The System Management Mode
735 is used to read cpu temperature and cooling fan status and to
736 control the fans on the I8K portables.
737
738 This driver has been tested only on the Inspiron 8000 but it may
739 also work with other Dell laptops. You can force loading on other
740 models by passing the parameter `force=1' to the module. Use at
741 your own risk.
742
743 For information on utilities to make use of this driver see the
744 I8K Linux utilities web site at:
745 <http://people.debian.org/~dz/i8k/>
746
747 Say Y if you intend to run this kernel on a Dell Inspiron 8000.
748 Say N otherwise.
749
750config X86_REBOOTFIXUPS
Harvey Harrison3c2362e2008-01-30 13:31:03 +0100751 def_bool n
752 prompt "Enable X86 board specific fixups for reboot"
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100753 depends on X86_32 && X86
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100754 ---help---
755 This enables chipset and/or board specific fixups to be done
756 in order to get reboot to work correctly. This is only needed on
757 some combinations of hardware and BIOS. The symptom, for which
758 this config is intended, is when reboot ends with a stalled/hung
759 system.
760
761 Currently, the only fixup is for the Geode machines using
Florian Fainelli5e3a77e2008-01-30 13:33:36 +0100762 CS5530A and CS5536 chipsets and the RDC R-321x SoC.
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100763
764 Say Y if you want to enable the fixup. Currently, it's safe to
765 enable this option even if you don't need it.
766 Say N otherwise.
767
768config MICROCODE
769 tristate "/dev/cpu/microcode - Intel IA32 CPU microcode support"
770 select FW_LOADER
771 ---help---
772 If you say Y here, you will be able to update the microcode on
773 Intel processors in the IA32 family, e.g. Pentium Pro, Pentium II,
774 Pentium III, Pentium 4, Xeon etc. You will obviously need the
775 actual microcode binary data itself which is not shipped with the
776 Linux kernel.
777
778 For latest news and information on obtaining all the required
779 ingredients for this driver, check:
780 <http://www.urbanmyth.org/microcode/>.
781
782 To compile this driver as a module, choose M here: the
783 module will be called microcode.
784
785config MICROCODE_OLD_INTERFACE
Harvey Harrison3c2362e2008-01-30 13:31:03 +0100786 def_bool y
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100787 depends on MICROCODE
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100788
789config X86_MSR
790 tristate "/dev/cpu/*/msr - Model-specific register support"
791 help
792 This device gives privileged processes access to the x86
793 Model-Specific Registers (MSRs). It is a character device with
794 major 202 and minors 0 to 31 for /dev/cpu/0/msr to /dev/cpu/31/msr.
795 MSR accesses are directed to a specific CPU on multi-processor
796 systems.
797
798config X86_CPUID
799 tristate "/dev/cpu/*/cpuid - CPU information support"
800 help
801 This device gives processes access to the x86 CPUID instruction to
802 be executed on a specific processor. It is a character device
803 with major 203 and minors 0 to 31 for /dev/cpu/0/cpuid to
804 /dev/cpu/31/cpuid.
805
806choice
807 prompt "High Memory Support"
808 default HIGHMEM4G if !X86_NUMAQ
809 default HIGHMEM64G if X86_NUMAQ
810 depends on X86_32
811
812config NOHIGHMEM
813 bool "off"
814 depends on !X86_NUMAQ
815 ---help---
816 Linux can use up to 64 Gigabytes of physical memory on x86 systems.
817 However, the address space of 32-bit x86 processors is only 4
818 Gigabytes large. That means that, if you have a large amount of
819 physical memory, not all of it can be "permanently mapped" by the
820 kernel. The physical memory that's not permanently mapped is called
821 "high memory".
822
823 If you are compiling a kernel which will never run on a machine with
824 more than 1 Gigabyte total physical RAM, answer "off" here (default
825 choice and suitable for most users). This will result in a "3GB/1GB"
826 split: 3GB are mapped so that each process sees a 3GB virtual memory
827 space and the remaining part of the 4GB virtual memory space is used
828 by the kernel to permanently map as much physical memory as
829 possible.
830
831 If the machine has between 1 and 4 Gigabytes physical RAM, then
832 answer "4GB" here.
833
834 If more than 4 Gigabytes is used then answer "64GB" here. This
835 selection turns Intel PAE (Physical Address Extension) mode on.
836 PAE implements 3-level paging on IA32 processors. PAE is fully
837 supported by Linux, PAE mode is implemented on all recent Intel
838 processors (Pentium Pro and better). NOTE: If you say "64GB" here,
839 then the kernel will not boot on CPUs that don't support PAE!
840
841 The actual amount of total physical memory will either be
842 auto detected or can be forced by using a kernel command line option
843 such as "mem=256M". (Try "man bootparam" or see the documentation of
844 your boot loader (lilo or loadlin) about how to pass options to the
845 kernel at boot time.)
846
847 If unsure, say "off".
848
849config HIGHMEM4G
850 bool "4GB"
851 depends on !X86_NUMAQ
852 help
853 Select this if you have a 32-bit processor and between 1 and 4
854 gigabytes of physical RAM.
855
856config HIGHMEM64G
857 bool "64GB"
858 depends on !M386 && !M486
859 select X86_PAE
860 help
861 Select this if you have a 32-bit processor and more than 4
862 gigabytes of physical RAM.
863
864endchoice
865
866choice
867 depends on EXPERIMENTAL
868 prompt "Memory split" if EMBEDDED
869 default VMSPLIT_3G
870 depends on X86_32
871 help
872 Select the desired split between kernel and user memory.
873
874 If the address range available to the kernel is less than the
875 physical memory installed, the remaining memory will be available
876 as "high memory". Accessing high memory is a little more costly
877 than low memory, as it needs to be mapped into the kernel first.
878 Note that increasing the kernel address space limits the range
879 available to user programs, making the address space there
880 tighter. Selecting anything other than the default 3G/1G split
881 will also likely make your kernel incompatible with binary-only
882 kernel modules.
883
884 If you are not absolutely sure what you are doing, leave this
885 option alone!
886
887 config VMSPLIT_3G
888 bool "3G/1G user/kernel split"
889 config VMSPLIT_3G_OPT
890 depends on !X86_PAE
891 bool "3G/1G user/kernel split (for full 1G low memory)"
892 config VMSPLIT_2G
893 bool "2G/2G user/kernel split"
894 config VMSPLIT_2G_OPT
895 depends on !X86_PAE
896 bool "2G/2G user/kernel split (for full 2G low memory)"
897 config VMSPLIT_1G
898 bool "1G/3G user/kernel split"
899endchoice
900
901config PAGE_OFFSET
902 hex
903 default 0xB0000000 if VMSPLIT_3G_OPT
904 default 0x80000000 if VMSPLIT_2G
905 default 0x78000000 if VMSPLIT_2G_OPT
906 default 0x40000000 if VMSPLIT_1G
907 default 0xC0000000
908 depends on X86_32
909
910config HIGHMEM
Harvey Harrison3c2362e2008-01-30 13:31:03 +0100911 def_bool y
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100912 depends on X86_32 && (HIGHMEM64G || HIGHMEM4G)
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100913
914config X86_PAE
Harvey Harrison3c2362e2008-01-30 13:31:03 +0100915 def_bool n
916 prompt "PAE (Physical Address Extension) Support"
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100917 depends on X86_32 && !HIGHMEM4G
918 select RESOURCES_64BIT
919 help
920 PAE is required for NX support, and furthermore enables
921 larger swapspace support for non-overcommit purposes. It
922 has the cost of more pagetable lookup overhead, and also
923 consumes more pagetable space per process.
924
925# Common NUMA Features
926config NUMA
927 bool "Numa Memory Allocation and Scheduler Support (EXPERIMENTAL)"
928 depends on SMP
929 depends on X86_64 || (X86_32 && HIGHMEM64G && (X86_NUMAQ || (X86_SUMMIT || X86_GENERICARCH) && ACPI) && EXPERIMENTAL)
930 default n if X86_PC
931 default y if (X86_NUMAQ || X86_SUMMIT)
932 help
933 Enable NUMA (Non Uniform Memory Access) support.
934 The kernel will try to allocate memory used by a CPU on the
935 local memory controller of the CPU and add some more
936 NUMA awareness to the kernel.
937
938 For i386 this is currently highly experimental and should be only
939 used for kernel development. It might also cause boot failures.
940 For x86_64 this is recommended on all multiprocessor Opteron systems.
941 If the system is EM64T, you should say N unless your system is
942 EM64T NUMA.
943
944comment "NUMA (Summit) requires SMP, 64GB highmem support, ACPI"
945 depends on X86_32 && X86_SUMMIT && (!HIGHMEM64G || !ACPI)
946
947config K8_NUMA
Harvey Harrison3c2362e2008-01-30 13:31:03 +0100948 def_bool y
949 prompt "Old style AMD Opteron NUMA detection"
950 depends on X86_64 && NUMA && PCI
951 help
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100952 Enable K8 NUMA node topology detection. You should say Y here if
953 you have a multi processor AMD K8 system. This uses an old
954 method to read the NUMA configuration directly from the builtin
955 Northbridge of Opteron. It is recommended to use X86_64_ACPI_NUMA
956 instead, which also takes priority if both are compiled in.
957
958config X86_64_ACPI_NUMA
Harvey Harrison3c2362e2008-01-30 13:31:03 +0100959 def_bool y
960 prompt "ACPI NUMA detection"
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100961 depends on X86_64 && NUMA && ACPI && PCI
962 select ACPI_NUMA
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100963 help
964 Enable ACPI SRAT based node topology detection.
965
Suresh Siddha6ec6e0d2008-03-25 10:14:35 -0700966# Some NUMA nodes have memory ranges that span
967# other nodes. Even though a pfn is valid and
968# between a node's start and end pfns, it may not
969# reside on that node. See memmap_init_zone()
970# for details.
971config NODES_SPAN_OTHER_NODES
972 def_bool y
973 depends on X86_64_ACPI_NUMA
974
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100975config NUMA_EMU
976 bool "NUMA emulation"
977 depends on X86_64 && NUMA
978 help
979 Enable NUMA emulation. A flat machine will be split
980 into virtual nodes when booted with "numa=fake=N", where N is the
981 number of nodes. This is only useful for debugging.
982
Mike Travis1184dc22008-05-12 21:21:12 +0200983if MAXSMP
984
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100985config NODES_SHIFT
Mike Travis1184dc22008-05-12 21:21:12 +0200986 int
987 default "9"
988endif
989
990if !MAXSMP
991config NODES_SHIFT
992 int "Maximum NUMA Nodes (as a power of 2)"
993 range 1 9 if X86_64
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100994 default "6" if X86_64
995 default "4" if X86_NUMAQ
996 default "3"
997 depends on NEED_MULTIPLE_NODES
Mike Travis1184dc22008-05-12 21:21:12 +0200998 help
999 Specify the maximum number of NUMA Nodes available on the target
1000 system. Increases memory reserved to accomodate various tables.
1001endif
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001002
1003config HAVE_ARCH_BOOTMEM_NODE
Harvey Harrison3c2362e2008-01-30 13:31:03 +01001004 def_bool y
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001005 depends on X86_32 && NUMA
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001006
1007config ARCH_HAVE_MEMORY_PRESENT
Harvey Harrison3c2362e2008-01-30 13:31:03 +01001008 def_bool y
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001009 depends on X86_32 && DISCONTIGMEM
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001010
1011config NEED_NODE_MEMMAP_SIZE
Harvey Harrison3c2362e2008-01-30 13:31:03 +01001012 def_bool y
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001013 depends on X86_32 && (DISCONTIGMEM || SPARSEMEM)
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001014
1015config HAVE_ARCH_ALLOC_REMAP
Harvey Harrison3c2362e2008-01-30 13:31:03 +01001016 def_bool y
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001017 depends on X86_32 && NUMA
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001018
1019config ARCH_FLATMEM_ENABLE
1020 def_bool y
Mel Gorman409a7b82008-01-30 13:33:25 +01001021 depends on X86_32 && ARCH_SELECT_MEMORY_MODEL && X86_PC && !NUMA
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001022
1023config ARCH_DISCONTIGMEM_ENABLE
1024 def_bool y
Christoph Lameterb2632952008-01-30 13:30:47 +01001025 depends on NUMA && X86_32
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001026
1027config ARCH_DISCONTIGMEM_DEFAULT
1028 def_bool y
Christoph Lameterb2632952008-01-30 13:30:47 +01001029 depends on NUMA && X86_32
1030
1031config ARCH_SPARSEMEM_DEFAULT
1032 def_bool y
1033 depends on X86_64
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001034
1035config ARCH_SPARSEMEM_ENABLE
1036 def_bool y
Christoph Lameterb2632952008-01-30 13:30:47 +01001037 depends on X86_64 || NUMA || (EXPERIMENTAL && X86_PC)
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001038 select SPARSEMEM_STATIC if X86_32
1039 select SPARSEMEM_VMEMMAP_ENABLE if X86_64
1040
1041config ARCH_SELECT_MEMORY_MODEL
1042 def_bool y
Christoph Lameterb2632952008-01-30 13:30:47 +01001043 depends on ARCH_SPARSEMEM_ENABLE
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001044
1045config ARCH_MEMORY_PROBE
1046 def_bool X86_64
1047 depends on MEMORY_HOTPLUG
1048
1049source "mm/Kconfig"
1050
1051config HIGHPTE
1052 bool "Allocate 3rd-level pagetables from highmem"
1053 depends on X86_32 && (HIGHMEM4G || HIGHMEM64G)
1054 help
1055 The VM uses one page table entry for each page of physical memory.
1056 For systems with a lot of RAM, this can be wasteful of precious
1057 low memory. Setting this option will put user-space page table
1058 entries in high memory.
1059
1060config MATH_EMULATION
1061 bool
1062 prompt "Math emulation" if X86_32
1063 ---help---
1064 Linux can emulate a math coprocessor (used for floating point
1065 operations) if you don't have one. 486DX and Pentium processors have
1066 a math coprocessor built in, 486SX and 386 do not, unless you added
1067 a 487DX or 387, respectively. (The messages during boot time can
1068 give you some hints here ["man dmesg"].) Everyone needs either a
1069 coprocessor or this emulation.
1070
1071 If you don't have a math coprocessor, you need to say Y here; if you
1072 say Y here even though you have a coprocessor, the coprocessor will
1073 be used nevertheless. (This behavior can be changed with the kernel
1074 command line option "no387", which comes handy if your coprocessor
1075 is broken. Try "man bootparam" or see the documentation of your boot
1076 loader (lilo or loadlin) about how to pass options to the kernel at
1077 boot time.) This means that it is a good idea to say Y here if you
1078 intend to use this kernel on different machines.
1079
1080 More information about the internals of the Linux math coprocessor
1081 emulation can be found in <file:arch/x86/math-emu/README>.
1082
1083 If you are not sure, say Y; apart from resulting in a 66 KB bigger
1084 kernel, it won't hurt.
1085
1086config MTRR
1087 bool "MTRR (Memory Type Range Register) support"
1088 ---help---
1089 On Intel P6 family processors (Pentium Pro, Pentium II and later)
1090 the Memory Type Range Registers (MTRRs) may be used to control
1091 processor access to memory ranges. This is most useful if you have
1092 a video (VGA) card on a PCI or AGP bus. Enabling write-combining
1093 allows bus write transfers to be combined into a larger transfer
1094 before bursting over the PCI/AGP bus. This can increase performance
1095 of image write operations 2.5 times or more. Saying Y here creates a
1096 /proc/mtrr file which may be used to manipulate your processor's
1097 MTRRs. Typically the X server should use this.
1098
1099 This code has a reasonably generic interface so that similar
1100 control registers on other processors can be easily supported
1101 as well:
1102
1103 The Cyrix 6x86, 6x86MX and M II processors have Address Range
1104 Registers (ARRs) which provide a similar functionality to MTRRs. For
1105 these, the ARRs are used to emulate the MTRRs.
1106 The AMD K6-2 (stepping 8 and above) and K6-3 processors have two
1107 MTRRs. The Centaur C6 (WinChip) has 8 MCRs, allowing
1108 write-combining. All of these processors are supported by this code
1109 and it makes sense to say Y here if you have one of them.
1110
1111 Saying Y here also fixes a problem with buggy SMP BIOSes which only
1112 set the MTRRs for the boot CPU and not for the secondary CPUs. This
1113 can lead to all sorts of problems, so it's good to say Y here.
1114
1115 You can safely say Y even if your machine doesn't have MTRRs, you'll
1116 just add about 9 KB to your kernel.
1117
1118 See <file:Documentation/mtrr.txt> for more information.
1119
venkatesh.pallipadi@intel.com2e5d9c82008-03-18 17:00:14 -07001120config X86_PAT
Ingo Molnar2a8a2712008-04-26 10:26:52 +02001121 bool
venkatesh.pallipadi@intel.com2e5d9c82008-03-18 17:00:14 -07001122 prompt "x86 PAT support"
Ingo Molnar2a8a2712008-04-26 10:26:52 +02001123 depends on MTRR
venkatesh.pallipadi@intel.com2e5d9c82008-03-18 17:00:14 -07001124 help
1125 Use PAT attributes to setup page level cache control.
Venki Pallipadi042b78e2008-03-24 14:22:35 -07001126
venkatesh.pallipadi@intel.com2e5d9c82008-03-18 17:00:14 -07001127 PATs are the modern equivalents of MTRRs and are much more
1128 flexible than MTRRs.
1129
1130 Say N here if you see bootup problems (boot crash, boot hang,
Venki Pallipadi042b78e2008-03-24 14:22:35 -07001131 spontaneous reboots) or a non-working video driver.
venkatesh.pallipadi@intel.com2e5d9c82008-03-18 17:00:14 -07001132
1133 If unsure, say Y.
1134
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001135config EFI
Harvey Harrison3c2362e2008-01-30 13:31:03 +01001136 def_bool n
Huang, Ying8b2cb7a2008-01-30 13:32:11 +01001137 prompt "EFI runtime service support"
Huang, Ying5b836832008-01-30 13:31:19 +01001138 depends on ACPI
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001139 ---help---
Huang, Ying8b2cb7a2008-01-30 13:32:11 +01001140 This enables the kernel to use EFI runtime services that are
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001141 available (such as the EFI variable services).
1142
Huang, Ying8b2cb7a2008-01-30 13:32:11 +01001143 This option is only useful on systems that have EFI firmware.
1144 In addition, you should use the latest ELILO loader available
1145 at <http://elilo.sourceforge.net> in order to take advantage
1146 of EFI runtime services. However, even with this option, the
1147 resultant kernel should continue to boot on existing non-EFI
1148 platforms.
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001149
1150config IRQBALANCE
Harvey Harrison3c2362e2008-01-30 13:31:03 +01001151 def_bool y
1152 prompt "Enable kernel irq balancing"
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001153 depends on X86_32 && SMP && X86_IO_APIC
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001154 help
1155 The default yes will allow the kernel to do irq load balancing.
1156 Saying no will keep the kernel from doing irq load balancing.
1157
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001158config SECCOMP
Harvey Harrison3c2362e2008-01-30 13:31:03 +01001159 def_bool y
1160 prompt "Enable seccomp to safely compute untrusted bytecode"
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001161 depends on PROC_FS
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001162 help
1163 This kernel feature is useful for number crunching applications
1164 that may need to compute untrusted bytecode during their
1165 execution. By using pipes or other transports made available to
1166 the process as file descriptors supporting the read/write
1167 syscalls, it's possible to isolate those applications in
1168 their own address space using seccomp. Once seccomp is
1169 enabled via /proc/<pid>/seccomp, it cannot be disabled
1170 and the task is only allowed to execute a few safe syscalls
1171 defined by each seccomp mode.
1172
1173 If unsure, say Y. Only embedded should say N here.
1174
1175config CC_STACKPROTECTOR
1176 bool "Enable -fstack-protector buffer overflow detection (EXPERIMENTAL)"
Linus Torvalds2c020a92008-02-22 08:21:38 -08001177 depends on X86_64 && EXPERIMENTAL && BROKEN
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001178 help
1179 This option turns on the -fstack-protector GCC feature. This
1180 feature puts, at the beginning of critical functions, a canary
1181 value on the stack just before the return address, and validates
1182 the value just before actually returning. Stack based buffer
1183 overflows (that need to overwrite this return address) now also
1184 overwrite the canary, which gets detected and the attack is then
1185 neutralized via a kernel panic.
1186
1187 This feature requires gcc version 4.2 or above, or a distribution
1188 gcc with the feature backported. Older versions are automatically
1189 detected and for those versions, this configuration option is ignored.
1190
1191config CC_STACKPROTECTOR_ALL
1192 bool "Use stack-protector for all functions"
1193 depends on CC_STACKPROTECTOR
1194 help
1195 Normally, GCC only inserts the canary value protection for
1196 functions that use large-ish on-stack buffers. By enabling
1197 this option, GCC will be asked to do this for ALL functions.
1198
1199source kernel/Kconfig.hz
1200
1201config KEXEC
1202 bool "kexec system call"
Ingo Molnar3e8f7e32008-04-28 10:46:58 +02001203 depends on X86_BIOS_REBOOT
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001204 help
1205 kexec is a system call that implements the ability to shutdown your
1206 current kernel, and to start another kernel. It is like a reboot
1207 but it is independent of the system firmware. And like a reboot
1208 you can start any kernel with it, not just Linux.
1209
1210 The name comes from the similarity to the exec system call.
1211
1212 It is an ongoing process to be certain the hardware in a machine
1213 is properly shutdown, so do not be surprised if this code does not
1214 initially work for you. It may help to enable device hotplugging
1215 support. As of this writing the exact hardware interface is
1216 strongly in flux, so no good recommendation can be made.
1217
1218config CRASH_DUMP
1219 bool "kernel crash dumps (EXPERIMENTAL)"
1220 depends on EXPERIMENTAL
1221 depends on X86_64 || (X86_32 && HIGHMEM)
1222 help
1223 Generate crash dump after being started by kexec.
1224 This should be normally only set in special crash dump kernels
1225 which are loaded in the main kernel with kexec-tools into
1226 a specially reserved region and then later executed after
1227 a crash by kdump/kexec. The crash dump kernel must be compiled
1228 to a memory address not used by the main kernel or BIOS using
1229 PHYSICAL_START, or it must be built as a relocatable image
1230 (CONFIG_RELOCATABLE=y).
1231 For more details see Documentation/kdump/kdump.txt
1232
1233config PHYSICAL_START
1234 hex "Physical address where the kernel is loaded" if (EMBEDDED || CRASH_DUMP)
1235 default "0x1000000" if X86_NUMAQ
1236 default "0x200000" if X86_64
1237 default "0x100000"
1238 help
1239 This gives the physical address where the kernel is loaded.
1240
1241 If kernel is a not relocatable (CONFIG_RELOCATABLE=n) then
1242 bzImage will decompress itself to above physical address and
1243 run from there. Otherwise, bzImage will run from the address where
1244 it has been loaded by the boot loader and will ignore above physical
1245 address.
1246
1247 In normal kdump cases one does not have to set/change this option
1248 as now bzImage can be compiled as a completely relocatable image
1249 (CONFIG_RELOCATABLE=y) and be used to load and run from a different
1250 address. This option is mainly useful for the folks who don't want
1251 to use a bzImage for capturing the crash dump and want to use a
1252 vmlinux instead. vmlinux is not relocatable hence a kernel needs
1253 to be specifically compiled to run from a specific memory area
1254 (normally a reserved region) and this option comes handy.
1255
1256 So if you are using bzImage for capturing the crash dump, leave
1257 the value here unchanged to 0x100000 and set CONFIG_RELOCATABLE=y.
1258 Otherwise if you plan to use vmlinux for capturing the crash dump
1259 change this value to start of the reserved region (Typically 16MB
1260 0x1000000). In other words, it can be set based on the "X" value as
1261 specified in the "crashkernel=YM@XM" command line boot parameter
1262 passed to the panic-ed kernel. Typically this parameter is set as
1263 crashkernel=64M@16M. Please take a look at
1264 Documentation/kdump/kdump.txt for more details about crash dumps.
1265
1266 Usage of bzImage for capturing the crash dump is recommended as
1267 one does not have to build two kernels. Same kernel can be used
1268 as production kernel and capture kernel. Above option should have
1269 gone away after relocatable bzImage support is introduced. But it
1270 is present because there are users out there who continue to use
1271 vmlinux for dump capture. This option should go away down the
1272 line.
1273
1274 Don't change this unless you know what you are doing.
1275
1276config RELOCATABLE
1277 bool "Build a relocatable kernel (EXPERIMENTAL)"
1278 depends on EXPERIMENTAL
1279 help
1280 This builds a kernel image that retains relocation information
1281 so it can be loaded someplace besides the default 1MB.
1282 The relocations tend to make the kernel binary about 10% larger,
1283 but are discarded at runtime.
1284
1285 One use is for the kexec on panic case where the recovery kernel
1286 must live at a different physical address than the primary
1287 kernel.
1288
1289 Note: If CONFIG_RELOCATABLE=y, then the kernel runs from the address
1290 it has been loaded at and the compile time physical address
1291 (CONFIG_PHYSICAL_START) is ignored.
1292
1293config PHYSICAL_ALIGN
1294 hex
1295 prompt "Alignment value to which kernel should be aligned" if X86_32
1296 default "0x100000" if X86_32
1297 default "0x200000" if X86_64
1298 range 0x2000 0x400000
1299 help
1300 This value puts the alignment restrictions on physical address
1301 where kernel is loaded and run from. Kernel is compiled for an
1302 address which meets above alignment restriction.
1303
1304 If bootloader loads the kernel at a non-aligned address and
1305 CONFIG_RELOCATABLE is set, kernel will move itself to nearest
1306 address aligned to above value and run from there.
1307
1308 If bootloader loads the kernel at a non-aligned address and
1309 CONFIG_RELOCATABLE is not set, kernel will ignore the run time
1310 load address and decompress itself to the address it has been
1311 compiled for and run from there. The address for which kernel is
1312 compiled already meets above alignment restrictions. Hence the
1313 end result is that kernel runs from a physical address meeting
1314 above alignment restrictions.
1315
1316 Don't change this unless you know what you are doing.
1317
1318config HOTPLUG_CPU
1319 bool "Support for suspend on SMP and hot-pluggable CPUs (EXPERIMENTAL)"
1320 depends on SMP && HOTPLUG && EXPERIMENTAL && !X86_VOYAGER
1321 ---help---
1322 Say Y here to experiment with turning CPUs off and on, and to
1323 enable suspend on SMP systems. CPUs can be controlled through
1324 /sys/devices/system/cpu.
1325 Say N if you want to disable CPU hotplug and don't need to
1326 suspend.
1327
1328config COMPAT_VDSO
Harvey Harrison3c2362e2008-01-30 13:31:03 +01001329 def_bool y
1330 prompt "Compat VDSO support"
Roland McGrathaf65d642008-01-30 13:30:43 +01001331 depends on X86_32 || IA32_EMULATION
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001332 help
Roland McGrathaf65d642008-01-30 13:30:43 +01001333 Map the 32-bit VDSO to the predictable old-style address too.
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001334 ---help---
1335 Say N here if you are running a sufficiently recent glibc
1336 version (2.3.3 or later), to remove the high-mapped
1337 VDSO mapping and to exclusively use the randomized VDSO.
1338
1339 If unsure, say Y.
1340
1341endmenu
1342
1343config ARCH_ENABLE_MEMORY_HOTPLUG
1344 def_bool y
1345 depends on X86_64 || (X86_32 && HIGHMEM)
1346
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001347config HAVE_ARCH_EARLY_PFN_TO_NID
1348 def_bool X86_64
1349 depends on NUMA
1350
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001351menu "Power management options"
1352 depends on !X86_VOYAGER
1353
1354config ARCH_HIBERNATION_HEADER
Harvey Harrison3c2362e2008-01-30 13:31:03 +01001355 def_bool y
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001356 depends on X86_64 && HIBERNATION
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001357
1358source "kernel/power/Kconfig"
1359
1360source "drivers/acpi/Kconfig"
1361
Andi Kleena6b68072008-01-30 13:32:49 +01001362config X86_APM_BOOT
1363 bool
1364 default y
1365 depends on APM || APM_MODULE
1366
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001367menuconfig APM
1368 tristate "APM (Advanced Power Management) BIOS support"
1369 depends on X86_32 && PM_SLEEP && !X86_VISWS
1370 ---help---
1371 APM is a BIOS specification for saving power using several different
1372 techniques. This is mostly useful for battery powered laptops with
1373 APM compliant BIOSes. If you say Y here, the system time will be
1374 reset after a RESUME operation, the /proc/apm device will provide
1375 battery status information, and user-space programs will receive
1376 notification of APM "events" (e.g. battery status change).
1377
1378 If you select "Y" here, you can disable actual use of the APM
1379 BIOS by passing the "apm=off" option to the kernel at boot time.
1380
1381 Note that the APM support is almost completely disabled for
1382 machines with more than one CPU.
1383
1384 In order to use APM, you will need supporting software. For location
Randy Dunlap53471122008-03-12 18:10:51 -04001385 and more information, read <file:Documentation/power/pm.txt> and the
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001386 Battery Powered Linux mini-HOWTO, available from
1387 <http://www.tldp.org/docs.html#howto>.
1388
1389 This driver does not spin down disk drives (see the hdparm(8)
1390 manpage ("man 8 hdparm") for that), and it doesn't turn off
1391 VESA-compliant "green" monitors.
1392
1393 This driver does not support the TI 4000M TravelMate and the ACER
1394 486/DX4/75 because they don't have compliant BIOSes. Many "green"
1395 desktop machines also don't have compliant BIOSes, and this driver
1396 may cause those machines to panic during the boot phase.
1397
1398 Generally, if you don't have a battery in your machine, there isn't
1399 much point in using this driver and you should say N. If you get
1400 random kernel OOPSes or reboots that don't seem to be related to
1401 anything, try disabling/enabling this option (or disabling/enabling
1402 APM in your BIOS).
1403
1404 Some other things you should try when experiencing seemingly random,
1405 "weird" problems:
1406
1407 1) make sure that you have enough swap space and that it is
1408 enabled.
1409 2) pass the "no-hlt" option to the kernel
1410 3) switch on floating point emulation in the kernel and pass
1411 the "no387" option to the kernel
1412 4) pass the "floppy=nodma" option to the kernel
1413 5) pass the "mem=4M" option to the kernel (thereby disabling
1414 all but the first 4 MB of RAM)
1415 6) make sure that the CPU is not over clocked.
1416 7) read the sig11 FAQ at <http://www.bitwizard.nl/sig11/>
1417 8) disable the cache from your BIOS settings
1418 9) install a fan for the video card or exchange video RAM
1419 10) install a better fan for the CPU
1420 11) exchange RAM chips
1421 12) exchange the motherboard.
1422
1423 To compile this driver as a module, choose M here: the
1424 module will be called apm.
1425
1426if APM
1427
1428config APM_IGNORE_USER_SUSPEND
1429 bool "Ignore USER SUSPEND"
1430 help
1431 This option will ignore USER SUSPEND requests. On machines with a
1432 compliant APM BIOS, you want to say N. However, on the NEC Versa M
1433 series notebooks, it is necessary to say Y because of a BIOS bug.
1434
1435config APM_DO_ENABLE
1436 bool "Enable PM at boot time"
1437 ---help---
1438 Enable APM features at boot time. From page 36 of the APM BIOS
1439 specification: "When disabled, the APM BIOS does not automatically
1440 power manage devices, enter the Standby State, enter the Suspend
1441 State, or take power saving steps in response to CPU Idle calls."
1442 This driver will make CPU Idle calls when Linux is idle (unless this
1443 feature is turned off -- see "Do CPU IDLE calls", below). This
1444 should always save battery power, but more complicated APM features
1445 will be dependent on your BIOS implementation. You may need to turn
1446 this option off if your computer hangs at boot time when using APM
1447 support, or if it beeps continuously instead of suspending. Turn
1448 this off if you have a NEC UltraLite Versa 33/C or a Toshiba
1449 T400CDT. This is off by default since most machines do fine without
1450 this feature.
1451
1452config APM_CPU_IDLE
1453 bool "Make CPU Idle calls when idle"
1454 help
1455 Enable calls to APM CPU Idle/CPU Busy inside the kernel's idle loop.
1456 On some machines, this can activate improved power savings, such as
1457 a slowed CPU clock rate, when the machine is idle. These idle calls
1458 are made after the idle loop has run for some length of time (e.g.,
1459 333 mS). On some machines, this will cause a hang at boot time or
1460 whenever the CPU becomes idle. (On machines with more than one CPU,
1461 this option does nothing.)
1462
1463config APM_DISPLAY_BLANK
1464 bool "Enable console blanking using APM"
1465 help
1466 Enable console blanking using the APM. Some laptops can use this to
1467 turn off the LCD backlight when the screen blanker of the Linux
1468 virtual console blanks the screen. Note that this is only used by
1469 the virtual console screen blanker, and won't turn off the backlight
1470 when using the X Window system. This also doesn't have anything to
1471 do with your VESA-compliant power-saving monitor. Further, this
1472 option doesn't work for all laptops -- it might not turn off your
1473 backlight at all, or it might print a lot of errors to the console,
1474 especially if you are using gpm.
1475
1476config APM_ALLOW_INTS
1477 bool "Allow interrupts during APM BIOS calls"
1478 help
1479 Normally we disable external interrupts while we are making calls to
1480 the APM BIOS as a measure to lessen the effects of a badly behaving
1481 BIOS implementation. The BIOS should reenable interrupts if it
1482 needs to. Unfortunately, some BIOSes do not -- especially those in
1483 many of the newer IBM Thinkpads. If you experience hangs when you
1484 suspend, try setting this to Y. Otherwise, say N.
1485
1486config APM_REAL_MODE_POWER_OFF
1487 bool "Use real mode APM BIOS call to power off"
1488 help
1489 Use real mode APM BIOS calls to switch off the computer. This is
1490 a work-around for a number of buggy BIOSes. Switch this option on if
1491 your computer crashes instead of powering off properly.
1492
1493endif # APM
1494
1495source "arch/x86/kernel/cpu/cpufreq/Kconfig"
1496
1497source "drivers/cpuidle/Kconfig"
1498
1499endmenu
1500
1501
1502menu "Bus options (PCI etc.)"
1503
1504config PCI
Roman Zippel823c2482008-02-29 05:09:02 +01001505 bool "PCI support" if !X86_VISWS && !X86_VSMP
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001506 depends on !X86_VOYAGER
Adrian Bunk1c858082008-01-30 13:32:32 +01001507 default y
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001508 select ARCH_SUPPORTS_MSI if (X86_LOCAL_APIC && X86_IO_APIC)
1509 help
1510 Find out whether you have a PCI motherboard. PCI is the name of a
1511 bus system, i.e. the way the CPU talks to the other stuff inside
1512 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
1513 VESA. If you have PCI, say Y, otherwise N.
1514
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001515choice
1516 prompt "PCI access mode"
1517 depends on X86_32 && PCI && !X86_VISWS
1518 default PCI_GOANY
1519 ---help---
1520 On PCI systems, the BIOS can be used to detect the PCI devices and
1521 determine their configuration. However, some old PCI motherboards
1522 have BIOS bugs and may crash if this is done. Also, some embedded
1523 PCI-based systems don't have any BIOS at all. Linux can also try to
1524 detect the PCI hardware directly without using the BIOS.
1525
1526 With this option, you can specify how Linux should detect the
1527 PCI devices. If you choose "BIOS", the BIOS will be used,
1528 if you choose "Direct", the BIOS won't be used, and if you
1529 choose "MMConfig", then PCI Express MMCONFIG will be used.
1530 If you choose "Any", the kernel will try MMCONFIG, then the
1531 direct access method and falls back to the BIOS if that doesn't
1532 work. If unsure, go with the default, which is "Any".
1533
1534config PCI_GOBIOS
1535 bool "BIOS"
1536
1537config PCI_GOMMCONFIG
1538 bool "MMConfig"
1539
1540config PCI_GODIRECT
1541 bool "Direct"
1542
Andres Salomon3ef0e1f2008-04-29 00:59:53 -07001543config PCI_GOOLPC
1544 bool "OLPC"
1545 depends on OLPC
1546
Andres Salomon2bdd1b02008-06-05 14:14:41 -07001547config PCI_GOANY
1548 bool "Any"
1549
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001550endchoice
1551
1552config PCI_BIOS
Harvey Harrison3c2362e2008-01-30 13:31:03 +01001553 def_bool y
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001554 depends on X86_32 && !X86_VISWS && PCI && (PCI_GOBIOS || PCI_GOANY)
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001555
1556# x86-64 doesn't support PCI BIOS access from long mode so always go direct.
1557config PCI_DIRECT
Harvey Harrison3c2362e2008-01-30 13:31:03 +01001558 def_bool y
Andres Salomon3ef0e1f2008-04-29 00:59:53 -07001559 depends on PCI && (X86_64 || (PCI_GODIRECT || PCI_GOANY || PCI_GOOLPC) || X86_VISWS)
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001560
1561config PCI_MMCONFIG
Harvey Harrison3c2362e2008-01-30 13:31:03 +01001562 def_bool y
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001563 depends on X86_32 && PCI && ACPI && (PCI_GOMMCONFIG || PCI_GOANY)
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001564
Andres Salomon3ef0e1f2008-04-29 00:59:53 -07001565config PCI_OLPC
Andres Salomon2bdd1b02008-06-05 14:14:41 -07001566 def_bool y
1567 depends on PCI && OLPC && (PCI_GOOLPC || PCI_GOANY)
Andres Salomon3ef0e1f2008-04-29 00:59:53 -07001568
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001569config PCI_DOMAINS
Harvey Harrison3c2362e2008-01-30 13:31:03 +01001570 def_bool y
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001571 depends on PCI
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001572
1573config PCI_MMCONFIG
1574 bool "Support mmconfig PCI config space access"
1575 depends on X86_64 && PCI && ACPI
1576
1577config DMAR
1578 bool "Support for DMA Remapping Devices (EXPERIMENTAL)"
1579 depends on X86_64 && PCI_MSI && ACPI && EXPERIMENTAL
1580 help
1581 DMA remapping (DMAR) devices support enables independent address
1582 translations for Direct Memory Access (DMA) from devices.
1583 These DMA remapping devices are reported via ACPI tables
1584 and include PCI device scope covered by these DMA
1585 remapping devices.
1586
1587config DMAR_GFX_WA
Harvey Harrison3c2362e2008-01-30 13:31:03 +01001588 def_bool y
1589 prompt "Support for Graphics workaround"
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001590 depends on DMAR
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001591 help
1592 Current Graphics drivers tend to use physical address
1593 for DMA and avoid using DMA APIs. Setting this config
1594 option permits the IOMMU driver to set a unity map for
1595 all the OS-visible memory. Hence the driver can continue
1596 to use physical addresses for DMA.
1597
1598config DMAR_FLOPPY_WA
Harvey Harrison3c2362e2008-01-30 13:31:03 +01001599 def_bool y
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001600 depends on DMAR
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001601 help
1602 Floppy disk drivers are know to bypass DMA API calls
1603 thereby failing to work when IOMMU is enabled. This
1604 workaround will setup a 1:1 mapping for the first
1605 16M to make floppy (an ISA device) work.
1606
1607source "drivers/pci/pcie/Kconfig"
1608
1609source "drivers/pci/Kconfig"
1610
1611# x86_64 have no ISA slots, but do have ISA-style DMA.
1612config ISA_DMA_API
Harvey Harrison3c2362e2008-01-30 13:31:03 +01001613 def_bool y
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001614
1615if X86_32
1616
1617config ISA
1618 bool "ISA support"
1619 depends on !(X86_VOYAGER || X86_VISWS)
1620 help
1621 Find out whether you have ISA slots on your motherboard. ISA is the
1622 name of a bus system, i.e. the way the CPU talks to the other stuff
1623 inside your box. Other bus systems are PCI, EISA, MicroChannel
1624 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
1625 newer boards don't support it. If you have ISA, say Y, otherwise N.
1626
1627config EISA
1628 bool "EISA support"
1629 depends on ISA
1630 ---help---
1631 The Extended Industry Standard Architecture (EISA) bus was
1632 developed as an open alternative to the IBM MicroChannel bus.
1633
1634 The EISA bus provided some of the features of the IBM MicroChannel
1635 bus while maintaining backward compatibility with cards made for
1636 the older ISA bus. The EISA bus saw limited use between 1988 and
1637 1995 when it was made obsolete by the PCI bus.
1638
1639 Say Y here if you are building a kernel for an EISA-based machine.
1640
1641 Otherwise, say N.
1642
1643source "drivers/eisa/Kconfig"
1644
1645config MCA
1646 bool "MCA support" if !(X86_VISWS || X86_VOYAGER)
1647 default y if X86_VOYAGER
1648 help
1649 MicroChannel Architecture is found in some IBM PS/2 machines and
1650 laptops. It is a bus system similar to PCI or ISA. See
1651 <file:Documentation/mca.txt> (and especially the web page given
1652 there) before attempting to build an MCA bus kernel.
1653
1654source "drivers/mca/Kconfig"
1655
1656config SCx200
1657 tristate "NatSemi SCx200 support"
1658 depends on !X86_VOYAGER
1659 help
1660 This provides basic support for National Semiconductor's
1661 (now AMD's) Geode processors. The driver probes for the
1662 PCI-IDs of several on-chip devices, so its a good dependency
1663 for other scx200_* drivers.
1664
1665 If compiled as a module, the driver is named scx200.
1666
1667config SCx200HR_TIMER
1668 tristate "NatSemi SCx200 27MHz High-Resolution Timer Support"
1669 depends on SCx200 && GENERIC_TIME
1670 default y
1671 help
1672 This driver provides a clocksource built upon the on-chip
1673 27MHz high-resolution timer. Its also a workaround for
1674 NSC Geode SC-1100's buggy TSC, which loses time when the
1675 processor goes idle (as is done by the scheduler). The
1676 other workaround is idle=poll boot option.
1677
1678config GEODE_MFGPT_TIMER
Harvey Harrison3c2362e2008-01-30 13:31:03 +01001679 def_bool y
1680 prompt "Geode Multi-Function General Purpose Timer (MFGPT) events"
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001681 depends on MGEODE_LX && GENERIC_TIME && GENERIC_CLOCKEVENTS
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001682 help
1683 This driver provides a clock event source based on the MFGPT
1684 timer(s) in the CS5535 and CS5536 companion chip for the geode.
1685 MFGPTs have a better resolution and max interval than the
1686 generic PIT, and are suitable for use as high-res timers.
1687
Andres Salomon3ef0e1f2008-04-29 00:59:53 -07001688config OLPC
1689 bool "One Laptop Per Child support"
1690 default n
1691 help
1692 Add support for detecting the unique features of the OLPC
1693 XO hardware.
1694
Sam Ravnborgbc0120f2007-11-06 23:10:39 +01001695endif # X86_32
1696
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001697config K8_NB
1698 def_bool y
Sam Ravnborgbc0120f2007-11-06 23:10:39 +01001699 depends on AGP_AMD64 || (X86_64 && (GART_IOMMU || (PCI && NUMA)))
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001700
1701source "drivers/pcmcia/Kconfig"
1702
1703source "drivers/pci/hotplug/Kconfig"
1704
1705endmenu
1706
1707
1708menu "Executable file formats / Emulations"
1709
1710source "fs/Kconfig.binfmt"
1711
1712config IA32_EMULATION
1713 bool "IA32 Emulation"
1714 depends on X86_64
Roland McGratha97f52e2008-01-30 13:31:55 +01001715 select COMPAT_BINFMT_ELF
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001716 help
1717 Include code to run 32-bit programs under a 64-bit kernel. You should
1718 likely turn this on, unless you're 100% sure that you don't have any
1719 32-bit programs left.
1720
1721config IA32_AOUT
1722 tristate "IA32 a.out support"
David Howellsb0b933c2008-02-08 04:19:27 -08001723 depends on IA32_EMULATION && ARCH_SUPPORTS_AOUT
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001724 help
1725 Support old a.out binaries in the 32bit emulation.
1726
1727config COMPAT
Harvey Harrison3c2362e2008-01-30 13:31:03 +01001728 def_bool y
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001729 depends on IA32_EMULATION
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001730
1731config COMPAT_FOR_U64_ALIGNMENT
1732 def_bool COMPAT
1733 depends on X86_64
1734
1735config SYSVIPC_COMPAT
Harvey Harrison3c2362e2008-01-30 13:31:03 +01001736 def_bool y
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001737 depends on X86_64 && COMPAT && SYSVIPC
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001738
1739endmenu
1740
1741
1742source "net/Kconfig"
1743
1744source "drivers/Kconfig"
1745
1746source "drivers/firmware/Kconfig"
1747
1748source "fs/Kconfig"
1749
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001750source "arch/x86/Kconfig.debug"
1751
1752source "security/Kconfig"
1753
1754source "crypto/Kconfig"
1755
Avi Kivityedf88412007-12-16 11:02:48 +02001756source "arch/x86/kvm/Kconfig"
1757
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001758source "lib/Kconfig"