blob: afaf2cb7c1ac4e0b700a8ec2df0489fb3bdde2c2 [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
David Woodhousee17c6d52008-06-17 12:19:34 +010021 select HAVE_AOUT if X86_32
Hitoshi Mitake2c5643b2008-11-30 17:16:04 +090022 select HAVE_READQ
23 select HAVE_WRITEQ
Ingo Molnara5574cf2008-05-05 23:19:50 +020024 select HAVE_UNSTABLE_SCHED_CLOCK
Sam Ravnborgec7748b2008-02-09 10:46:40 +010025 select HAVE_IDE
Mathieu Desnoyers42d4b832008-02-02 15:10:34 -050026 select HAVE_OPROFILE
Rik van Riel28b2ee22008-07-23 21:27:05 -070027 select HAVE_IOREMAP_PROT
Mathieu Desnoyers3f550092008-02-02 15:10:35 -050028 select HAVE_KPROBES
Ingo Molnar1f972762008-07-26 13:52:50 +020029 select ARCH_WANT_OPTIONAL_GPIOLIB
Ingo Molnarda4276b2009-01-07 11:05:10 +010030 select ARCH_WANT_FRAME_POINTERS
Ananth N Mavinakayanahalli9edddaa2008-03-04 14:28:37 -080031 select HAVE_KRETPROBES
Steven Rostedte4b2b882008-08-14 15:45:11 -040032 select HAVE_FTRACE_MCOUNT_RECORD
Steven Rostedt677aa9f2008-05-17 00:01:36 -040033 select HAVE_DYNAMIC_FTRACE
Steven Rostedt606576c2008-10-06 19:06:12 -040034 select HAVE_FUNCTION_TRACER
Frederic Weisbecker48d68b22008-12-02 00:20:39 +010035 select HAVE_FUNCTION_GRAPH_TRACER
Steven Rostedt60a7ecf2008-11-05 16:05:44 -050036 select HAVE_FUNCTION_TRACE_MCOUNT_TEST
Ingo Molnare0ec9482009-01-27 17:01:14 +010037 select HAVE_KVM
Ingo Molnar49793b02009-01-27 17:02:29 +010038 select HAVE_ARCH_KGDB
Roland McGrath99bbc4b2008-04-20 14:35:12 -070039 select HAVE_ARCH_TRACEHOOK
Dmitry Baryshkov323ec002008-06-29 14:19:31 +040040 select HAVE_GENERIC_DMA_COHERENT if X86_32
Johannes Berg58340a02008-07-25 01:45:33 -070041 select HAVE_EFFICIENT_UNALIGNED_ACCESS
Török Edwin8d264872008-11-23 12:39:08 +020042 select USER_STACKTRACE_SUPPORT
Balbir Singh7d8330a2008-02-10 12:46:28 +053043
Sam Ravnborg73531902008-05-25 23:03:18 +020044config ARCH_DEFCONFIG
Sam Ravnborgb9b39bf2008-04-29 12:48:15 +020045 string
Sam Ravnborg73531902008-05-25 23:03:18 +020046 default "arch/x86/configs/i386_defconfig" if X86_32
47 default "arch/x86/configs/x86_64_defconfig" if X86_64
Sam Ravnborgb9b39bf2008-04-29 12:48:15 +020048
Sam Ravnborg8d5fffb2007-11-06 23:30:30 +010049config GENERIC_TIME
Harvey Harrison3c2362e2008-01-30 13:31:03 +010050 def_bool y
Sam Ravnborg8d5fffb2007-11-06 23:30:30 +010051
52config GENERIC_CMOS_UPDATE
Harvey Harrison3c2362e2008-01-30 13:31:03 +010053 def_bool y
Sam Ravnborg8d5fffb2007-11-06 23:30:30 +010054
55config CLOCKSOURCE_WATCHDOG
Harvey Harrison3c2362e2008-01-30 13:31:03 +010056 def_bool y
Sam Ravnborg8d5fffb2007-11-06 23:30:30 +010057
58config GENERIC_CLOCKEVENTS
Harvey Harrison3c2362e2008-01-30 13:31:03 +010059 def_bool y
Sam Ravnborg8d5fffb2007-11-06 23:30:30 +010060
61config GENERIC_CLOCKEVENTS_BROADCAST
Harvey Harrison3c2362e2008-01-30 13:31:03 +010062 def_bool y
Sam Ravnborg8d5fffb2007-11-06 23:30:30 +010063 depends on X86_64 || (X86_32 && X86_LOCAL_APIC)
64
65config LOCKDEP_SUPPORT
Harvey Harrison3c2362e2008-01-30 13:31:03 +010066 def_bool y
Sam Ravnborg8d5fffb2007-11-06 23:30:30 +010067
68config STACKTRACE_SUPPORT
Harvey Harrison3c2362e2008-01-30 13:31:03 +010069 def_bool y
Sam Ravnborg8d5fffb2007-11-06 23:30:30 +010070
Heiko Carstensaa7d9352008-02-01 17:45:14 +010071config HAVE_LATENCYTOP_SUPPORT
72 def_bool y
73
Christoph Lameter1f842602008-01-07 23:20:30 -080074config FAST_CMPXCHG_LOCAL
75 bool
76 default y
77
Sam Ravnborg8d5fffb2007-11-06 23:30:30 +010078config MMU
Harvey Harrison3c2362e2008-01-30 13:31:03 +010079 def_bool y
Sam Ravnborg8d5fffb2007-11-06 23:30:30 +010080
81config ZONE_DMA
Harvey Harrison3c2362e2008-01-30 13:31:03 +010082 def_bool y
Sam Ravnborg8d5fffb2007-11-06 23:30:30 +010083
Sam Ravnborg8d5fffb2007-11-06 23:30:30 +010084config SBUS
85 bool
86
87config GENERIC_ISA_DMA
Harvey Harrison3c2362e2008-01-30 13:31:03 +010088 def_bool y
Sam Ravnborg8d5fffb2007-11-06 23:30:30 +010089
90config GENERIC_IOMAP
Harvey Harrison3c2362e2008-01-30 13:31:03 +010091 def_bool y
Sam Ravnborg8d5fffb2007-11-06 23:30:30 +010092
93config GENERIC_BUG
Harvey Harrison3c2362e2008-01-30 13:31:03 +010094 def_bool y
Sam Ravnborg8d5fffb2007-11-06 23:30:30 +010095 depends on BUG
Jan Beulichb93a5312008-12-16 11:40:27 +000096 select GENERIC_BUG_RELATIVE_POINTERS if X86_64
97
98config GENERIC_BUG_RELATIVE_POINTERS
99 bool
Sam Ravnborg8d5fffb2007-11-06 23:30:30 +0100100
101config GENERIC_HWEIGHT
Harvey Harrison3c2362e2008-01-30 13:31:03 +0100102 def_bool y
Sam Ravnborg8d5fffb2007-11-06 23:30:30 +0100103
Florian Fainellia6082952008-01-30 13:33:35 +0100104config GENERIC_GPIO
Jan Beulich9ba16082008-10-15 22:01:38 -0700105 bool
Florian Fainellia6082952008-01-30 13:33:35 +0100106
Sam Ravnborg8d5fffb2007-11-06 23:30:30 +0100107config ARCH_MAY_HAVE_PC_FDC
Harvey Harrison3c2362e2008-01-30 13:31:03 +0100108 def_bool y
Sam Ravnborg8d5fffb2007-11-06 23:30:30 +0100109
Sam Ravnborg1032c0b2007-11-06 21:35:08 +0100110config RWSEM_GENERIC_SPINLOCK
111 def_bool !X86_XADD
112
113config RWSEM_XCHGADD_ALGORITHM
114 def_bool X86_XADD
115
Venki Pallipadia6869cc2008-02-08 17:05:44 -0800116config ARCH_HAS_CPU_IDLE_WAIT
117 def_bool y
118
Sam Ravnborg1032c0b2007-11-06 21:35:08 +0100119config GENERIC_CALIBRATE_DELAY
120 def_bool y
121
Sam Ravnborg8d5fffb2007-11-06 23:30:30 +0100122config GENERIC_TIME_VSYSCALL
123 bool
124 default X86_64
125
venkatesh.pallipadi@intel.com9a0b8412008-01-31 17:35:06 -0800126config ARCH_HAS_CPU_RELAX
127 def_bool y
Sam Ravnborg8d5fffb2007-11-06 23:30:30 +0100128
Venkatesh Pallipadi89cedfe2008-10-16 19:00:08 -0400129config ARCH_HAS_DEFAULT_IDLE
130 def_bool y
131
Pekka Enberg1b27d052008-04-28 02:12:22 -0700132config ARCH_HAS_CACHE_LINE_SIZE
133 def_bool y
134
Mike Travisdd5af902008-01-30 13:33:32 +0100135config HAVE_SETUP_PER_CPU_AREA
Brian Gerst89c9c4c2009-01-27 12:56:48 +0900136 def_bool y
travis@sgi.comb32ef632008-01-30 13:32:51 +0100137
Mike Travis9f0e8d02008-04-04 18:11:01 -0700138config HAVE_CPUMASK_OF_CPU_MAP
139 def_bool X86_64_SMP
140
Johannes Berg801e4062007-12-08 02:12:39 +0100141config ARCH_HIBERNATION_POSSIBLE
142 def_bool y
Ingo Molnaraced3ce2009-01-27 17:03:24 +0100143 depends on !SMP
Johannes Berg801e4062007-12-08 02:12:39 +0100144
Johannes Bergf4cb5702007-12-08 02:14:00 +0100145config ARCH_SUSPEND_POSSIBLE
146 def_bool y
Johannes Bergf4cb5702007-12-08 02:14:00 +0100147
Sam Ravnborg8d5fffb2007-11-06 23:30:30 +0100148config ZONE_DMA32
149 bool
150 default X86_64
151
152config ARCH_POPULATES_NODE_MAP
153 def_bool y
154
155config AUDIT_ARCH
156 bool
157 default X86_64
158
Ingo Molnar765c68b2008-04-09 11:03:37 +0200159config ARCH_SUPPORTS_OPTIMIZED_INLINING
160 def_bool y
161
Sam Ravnborg8d5fffb2007-11-06 23:30:30 +0100162# Use the generic interrupt handling code in kernel/irq/:
163config GENERIC_HARDIRQS
164 bool
165 default y
166
167config GENERIC_IRQ_PROBE
168 bool
169 default y
170
171config GENERIC_PENDING_IRQ
172 bool
173 depends on GENERIC_HARDIRQS && SMP
174 default y
175
James Bottomley6cd10f82008-11-09 11:53:14 -0600176config USE_GENERIC_SMP_HELPERS
177 def_bool y
178 depends on SMP
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
Sam Ravnborg8d5fffb2007-11-06 23:30:30 +0100191 default y
192
Sam Ravnborg8d5fffb2007-11-06 23:30:30 +0100193config X86_TRAMPOLINE
194 bool
Ingo Molnar3e5095d2009-01-27 17:07:08 +0100195 depends on SMP || (64BIT && ACPI_SLEEP)
Sam Ravnborg8d5fffb2007-11-06 23:30:30 +0100196 default y
197
198config KTIME_SCALAR
199 def_bool X86_32
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100200source "init/Kconfig"
Matt Helsleydc52ddc2008-10-18 20:27:21 -0700201source "kernel/Kconfig.freezer"
Sam Ravnborg8d5fffb2007-11-06 23:30:30 +0100202
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100203menu "Processor type and features"
204
205source "kernel/time/Kconfig"
206
207config SMP
208 bool "Symmetric multi-processing support"
209 ---help---
210 This enables support for systems with more than one CPU. If you have
211 a system with only one CPU, like most personal computers, say N. If
212 you have a system with more than one CPU, say Y.
213
214 If you say N here, the kernel will run on single and multiprocessor
215 machines, but will use only one CPU of a multiprocessor machine. If
216 you say Y here, the kernel will run on many, but not all,
217 singleprocessor machines. On a singleprocessor machine, the kernel
218 will run faster if you say N here.
219
220 Note that if you say Y here and choose architecture "586" or
221 "Pentium" under "Processor family", the kernel will not work on 486
222 architectures. Similarly, multiprocessor kernels for the "PPro"
223 architecture may not work on all Pentium based boards.
224
225 People using multiprocessor machines who say Y here should also say
226 Y to "Enhanced Real Time Clock Support", below. The "Advanced Power
227 Management" code will be disabled if you say Y here.
228
Adrian Bunk03502fa2008-02-03 15:50:21 +0200229 See also <file:Documentation/i386/IO-APIC.txt>,
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100230 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
231 <http://www.tldp.org/docs.html#howto>.
232
233 If you don't know what to do here, say N.
234
Yinghai Lu0b8f1ef2008-12-05 18:58:31 -0800235config SPARSE_IRQ
236 bool "Support sparse irq numbering"
Yinghai Lu17483a12008-12-12 13:14:18 -0800237 depends on PCI_MSI || HT_IRQ
Yinghai Lu0b8f1ef2008-12-05 18:58:31 -0800238 help
Ingo Molnar973656f2008-12-25 16:26:47 +0100239 This enables support for sparse irqs. This is useful for distro
240 kernels that want to define a high CONFIG_NR_CPUS value but still
241 want to have low kernel memory footprint on smaller machines.
Yinghai Lu0b8f1ef2008-12-05 18:58:31 -0800242
Ingo Molnar973656f2008-12-25 16:26:47 +0100243 ( Sparse IRQs can also be beneficial on NUMA boxes, as they spread
244 out the irq_desc[] array in a more NUMA-friendly way. )
245
246 If you don't know what to do here, say N.
Yinghai Lu0b8f1ef2008-12-05 18:58:31 -0800247
Yinghai Lu48a1b102008-12-11 00:15:01 -0800248config NUMA_MIGRATE_IRQ_DESC
249 bool "Move irq desc when changing irq smp_affinity"
Yinghai Lub9098952008-12-19 13:48:34 -0800250 depends on SPARSE_IRQ && NUMA
Yinghai Lu48a1b102008-12-11 00:15:01 -0800251 default n
252 help
253 This enables moving irq_desc to cpu/node that irq will use handled.
254
255 If you don't know what to do here, say N.
256
Yinghai Lu6695c852008-06-19 12:13:09 -0700257config X86_MPPARSE
Jan Beulich7a527682008-10-30 10:38:24 +0000258 bool "Enable MPS table" if ACPI
259 default y
Ingo Molnar5ab74722008-07-10 14:42:03 +0200260 depends on X86_LOCAL_APIC
Yinghai Lu6695c852008-06-19 12:13:09 -0700261 help
262 For old smp systems that do not have proper acpi support. Newer systems
263 (esp with 64bit cpus) with acpi support, MADT and DSDT will override it
Yinghai Lu6695c852008-06-19 12:13:09 -0700264
Ingo Molnar06ac8342009-01-27 18:11:43 +0100265config X86_NON_STANDARD
266 bool "Support for non-standard x86 platforms"
267 help
268 If you disable this option then the kernel will only support
269 standard PC platforms. (which covers the vast majority of
270 systems out there.)
271
272 If you enable this option then you'll be able to select a number
273 of less common non-PC x86 platforms: VisWS, RDC321, SGI/UV.
274
275 If you have one of these systems, or if you want to build a
276 generic distribution kernel, say Y here - otherwise say N.
277
Ingo Molnar1b84e1c2008-07-10 15:55:27 +0200278config X86_VISWS
279 bool "SGI 320/540 (Visual Workstation)"
Ingo Molnar36619a82009-01-27 17:33:34 +0100280 depends on X86_32 && PCI && X86_MPPARSE && PCI_GODIRECT
Ingo Molnar06ac8342009-01-27 18:11:43 +0100281 depends on X86_NON_STANDARD
Ingo Molnar1b84e1c2008-07-10 15:55:27 +0200282 help
283 The SGI Visual Workstation series is an IA32-based workstation
284 based on SGI systems chips with some legacy PC hardware attached.
285
286 Say Y here to create a kernel to run on the SGI 320 or 540.
287
288 A kernel compiled for the Visual Workstation will run on general
289 PCs as well. See <file:Documentation/sgi-visws.txt> for details.
290
Ingo Molnar1f972762008-07-26 13:52:50 +0200291config X86_RDC321X
292 bool "RDC R-321x SoC"
293 depends on X86_32
Ingo Molnar06ac8342009-01-27 18:11:43 +0100294 depends on X86_NON_STANDARD
Ingo Molnar1f972762008-07-26 13:52:50 +0200295 select M486
296 select X86_REBOOTFIXUPS
297 help
298 This option is needed for RDC R-321x system-on-chip, also known
299 as R-8610-(G).
300 If you don't have one of these chips, you should say N here.
301
Nick Piggin03b48632009-01-20 04:36:04 +0100302config X86_UV
303 bool "SGI Ultraviolet"
304 depends on X86_64
Ingo Molnar06ac8342009-01-27 18:11:43 +0100305 depends on X86_NON_STANDARD
Nick Piggin03b48632009-01-20 04:36:04 +0100306 help
307 This option is needed in order to support SGI Ultraviolet systems.
308 If you don't have one of these, you should say N here.
309
Ingo Molnar6a485652009-01-27 18:29:13 +0100310config X86_VSMP
311 bool "Support for ScaleMP vSMP"
312 select PARAVIRT
313 depends on X86_64 && PCI
314 depends on X86_NON_STANDARD
315 help
316 Support for ScaleMP vSMP systems. Say 'Y' here if this kernel is
317 supposed to run on these EM64T-based machines. Only choose this option
318 if you have one of these machines.
319
Ingo Molnar9e111f32009-01-27 18:18:25 +0100320config X86_ELAN
321 bool "AMD Elan"
322 depends on X86_32
323 depends on X86_NON_STANDARD
324 help
325 Select this for an AMD Elan processor.
326
327 Do not use this option for K6/Athlon/Opteron processors!
328
329 If unsure, choose "PC-compatible" instead.
330
Ingo Molnare0c7ae32009-01-27 18:43:09 +0100331config X86_32_NON_STANDARD
Ingo Molnar9c398012009-01-27 18:24:57 +0100332 bool "Support non-standard 32-bit SMP architectures"
333 depends on X86_32 && SMP
334 depends on X86_NON_STANDARD
335 help
336 This option compiles in the NUMAQ, Summit, bigsmp, ES7000, default
337 subarchitectures. It is intended for a generic binary kernel.
338 if you select them all, kernel will probe it one by one. and will
339 fallback to default.
340
Ingo Molnar3769e7b2009-01-27 18:46:23 +0100341config X86_BIGSMP
342 bool "Support for big SMP systems with more than 8 CPUs"
343 depends on X86_32_NON_STANDARD
344 help
345 This option is needed for the systems that have more than 8 CPUs
346 and if the system is not of any sub-arch type above.
347
Ingo Molnar9c398012009-01-27 18:24:57 +0100348config X86_NUMAQ
349 bool "NUMAQ (IBM/Sequent)"
Ingo Molnare0c7ae32009-01-27 18:43:09 +0100350 depends on X86_32_NON_STANDARD
Ingo Molnar9c398012009-01-27 18:24:57 +0100351 select NUMA
352 select X86_MPPARSE
353 help
354 This option is used for getting Linux to run on a NUMAQ (IBM/Sequent)
355 NUMA multiquad box. This changes the way that processors are
356 bootstrapped, and uses Clustered Logical APIC addressing mode instead
357 of Flat Logical. You will need a new lynxer.elf file to flash your
358 firmware with - send email to <Martin.Bligh@us.ibm.com>.
359
360config X86_SUMMIT
361 bool "Summit/EXA (IBM x440)"
Ingo Molnare0c7ae32009-01-27 18:43:09 +0100362 depends on X86_32_NON_STANDARD
Ingo Molnar9c398012009-01-27 18:24:57 +0100363 help
364 This option is needed for IBM systems that use the Summit/EXA chipset.
365 In particular, it is needed for the x440.
366
367config X86_ES7000
368 bool "Support for Unisys ES7000 IA32 series"
Ingo Molnare0c7ae32009-01-27 18:43:09 +0100369 depends on X86_32_NON_STANDARD
Ingo Molnar9c398012009-01-27 18:24:57 +0100370 help
371 Support for Unisys ES7000 systems. Say 'Y' here if this kernel is
372 supposed to run on an IA32-based Unisys ES7000 system.
373
Ingo Molnar3769e7b2009-01-27 18:46:23 +0100374config X86_VOYAGER
375 bool "Voyager (NCR)"
376 depends on SMP && !PCI && BROKEN
Ingo Molnare0c7ae32009-01-27 18:43:09 +0100377 depends on X86_32_NON_STANDARD
Ingo Molnar9c398012009-01-27 18:24:57 +0100378 help
Ingo Molnar3769e7b2009-01-27 18:46:23 +0100379 Voyager is an MCA-based 32-way capable SMP architecture proprietary
380 to NCR Corp. Machine classes 345x/35xx/4100/51xx are Voyager-based.
381
382 *** WARNING ***
383
384 If you do not specifically know you have a Voyager based machine,
385 say N here, otherwise the kernel you build will not be bootable.
Ingo Molnar9c398012009-01-27 18:24:57 +0100386
Ingo Molnarae1e9132008-11-11 09:05:16 +0100387config SCHED_OMIT_FRAME_POINTER
Harvey Harrison3c2362e2008-01-30 13:31:03 +0100388 def_bool y
389 prompt "Single-depth WCHAN output"
Ken Chena87d0912008-11-06 11:10:49 -0800390 depends on X86
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100391 help
392 Calculate simpler /proc/<PID>/wchan values. If this option
393 is disabled then wchan values will recurse back to the
394 caller function. This provides more accurate wchan values,
395 at the expense of slightly more scheduling overhead.
396
397 If in doubt, say "Y".
398
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100399menuconfig PARAVIRT_GUEST
400 bool "Paravirtualized guest support"
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100401 help
402 Say Y here to get to see options related to running Linux under
403 various hypervisors. This option alone does not add any kernel code.
404
405 If you say N, all options in this submenu will be skipped and disabled.
406
407if PARAVIRT_GUEST
408
409source "arch/x86/xen/Kconfig"
410
411config VMI
412 bool "VMI Guest support"
413 select PARAVIRT
Eduardo Pereira Habkost42d545c2008-01-30 13:33:32 +0100414 depends on X86_32
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100415 help
416 VMI provides a paravirtualized interface to the VMware ESX server
417 (it could be used by other hypervisors in theory too, but is not
418 at the moment), by linking the kernel to a GPL-ed ROM module
419 provided by the hypervisor.
420
Glauber de Oliveira Costa790c73f2008-02-15 17:52:48 -0200421config KVM_CLOCK
422 bool "KVM paravirtualized clock"
423 select PARAVIRT
Gerd Hoffmannf6e16d52008-06-03 16:17:32 +0200424 select PARAVIRT_CLOCK
Glauber de Oliveira Costa790c73f2008-02-15 17:52:48 -0200425 help
426 Turning on this option will allow you to run a paravirtualized clock
427 when running over the KVM hypervisor. Instead of relying on a PIT
428 (or probably other) emulation by the underlying device model, the host
429 provides the guest with timing infrastructure such as time of day, and
430 system time
431
Marcelo Tosatti0cf1bfd2008-02-22 12:21:36 -0500432config KVM_GUEST
433 bool "KVM Guest support"
434 select PARAVIRT
Marcelo Tosatti0cf1bfd2008-02-22 12:21:36 -0500435 help
436 This option enables various optimizations for running under the KVM
437 hypervisor.
438
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100439source "arch/x86/lguest/Kconfig"
440
Eduardo Pereira Habkoste61bd942008-01-30 13:33:32 +0100441config PARAVIRT
442 bool "Enable paravirtualization code"
Eduardo Pereira Habkoste61bd942008-01-30 13:33:32 +0100443 help
444 This changes the kernel so it can modify itself when it is run
445 under a hypervisor, potentially improving performance significantly
446 over full virtualization. However, when run without a hypervisor
447 the kernel is theoretically slower and slightly larger.
448
Gerd Hoffmann7af192c2008-06-03 16:17:29 +0200449config PARAVIRT_CLOCK
450 bool
451 default n
452
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100453endif
454
Jeremy Fitzhardinge97349132008-06-25 00:19:14 -0400455config PARAVIRT_DEBUG
456 bool "paravirt-ops debugging"
457 depends on PARAVIRT && DEBUG_KERNEL
458 help
459 Enable to debug paravirt_ops internals. Specifically, BUG if
460 a paravirt_op is missing when it is called.
461
Yinghai Lu03273182008-04-18 17:49:15 -0700462config MEMTEST
463 bool "Memtest"
Yinghai Luc64df702008-03-21 18:56:19 -0700464 help
465 This option adds a kernel parameter 'memtest', which allows memtest
Yinghai Lu03273182008-04-18 17:49:15 -0700466 to be set.
467 memtest=0, mean disabled; -- default
468 memtest=1, mean do 1 test pattern;
469 ...
470 memtest=4, mean do 4 test patterns.
Thomas Gleixneraba37282008-07-15 14:48:48 +0200471 If you are unsure how to answer this question, answer N.
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100472
473config X86_SUMMIT_NUMA
Harvey Harrison3c2362e2008-01-30 13:31:03 +0100474 def_bool y
Ingo Molnare0c7ae32009-01-27 18:43:09 +0100475 depends on X86_32 && NUMA && X86_32_NON_STANDARD
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100476
477config X86_CYCLONE_TIMER
Harvey Harrison3c2362e2008-01-30 13:31:03 +0100478 def_bool y
Ingo Molnare0c7ae32009-01-27 18:43:09 +0100479 depends on X86_32_NON_STANDARD
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100480
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100481source "arch/x86/Kconfig.cpu"
482
483config HPET_TIMER
Harvey Harrison3c2362e2008-01-30 13:31:03 +0100484 def_bool X86_64
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100485 prompt "HPET Timer Support" if X86_32
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100486 help
487 Use the IA-PC HPET (High Precision Event Timer) to manage
488 time in preference to the PIT and RTC, if a HPET is
489 present.
490 HPET is the next generation timer replacing legacy 8254s.
491 The HPET provides a stable time base on SMP
492 systems, unlike the TSC, but it is more expensive to access,
493 as it is off-chip. You can find the HPET spec at
Denis V. Luneve45f2c02008-11-24 11:28:36 +0300494 <http://www.intel.com/hardwaredesign/hpetspec_1.pdf>.
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100495
496 You can safely choose Y here. However, HPET will only be
497 activated if the platform and the BIOS support this feature.
498 Otherwise the 8254 will be used for timing services.
499
500 Choose N to continue using the legacy 8254 timer.
501
502config HPET_EMULATE_RTC
Harvey Harrison3c2362e2008-01-30 13:31:03 +0100503 def_bool y
Bernhard Walle9d8af782008-02-06 01:38:52 -0800504 depends on HPET_TIMER && (RTC=y || RTC=m || RTC_DRV_CMOS=m || RTC_DRV_CMOS=y)
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100505
506# Mark as embedded because too many people got it wrong.
507# The code disables itself when not needed.
Thomas Petazzoni7ae93922008-04-28 02:14:14 -0700508config DMI
509 default y
510 bool "Enable DMI scanning" if EMBEDDED
511 help
512 Enabled scanning of DMI to identify machine quirks. Say Y
513 here unless you have verified that your setup is not
514 affected by entries in the DMI blacklist. Required by PNP
515 BIOS code.
516
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100517config GART_IOMMU
518 bool "GART IOMMU support" if EMBEDDED
519 default y
520 select SWIOTLB
521 select AGP
522 depends on X86_64 && PCI
523 help
524 Support for full DMA access of devices with 32bit memory access only
525 on systems with more than 3GB. This is usually needed for USB,
526 sound, many IDE/SATA chipsets and some other devices.
527 Provides a driver for the AMD Athlon64/Opteron/Turion/Sempron GART
528 based hardware IOMMU and a software bounce buffer based IOMMU used
529 on Intel systems and as fallback.
530 The code is only active when needed (enough memory and limited
531 device) unless CONFIG_IOMMU_DEBUG or iommu=force is specified
532 too.
533
534config CALGARY_IOMMU
535 bool "IBM Calgary IOMMU support"
536 select SWIOTLB
537 depends on X86_64 && PCI && EXPERIMENTAL
538 help
539 Support for hardware IOMMUs in IBM's xSeries x366 and x460
540 systems. Needed to run systems with more than 3GB of memory
541 properly with 32-bit PCI devices that do not support DAC
542 (Double Address Cycle). Calgary also supports bus level
543 isolation, where all DMAs pass through the IOMMU. This
544 prevents them from going anywhere except their intended
545 destination. This catches hard-to-find kernel bugs and
546 mis-behaving drivers and devices that do not use the DMA-API
547 properly to set up their DMA buffers. The IOMMU can be
548 turned off at boot time with the iommu=off parameter.
549 Normally the kernel will make the right choice by itself.
550 If unsure, say Y.
551
552config CALGARY_IOMMU_ENABLED_BY_DEFAULT
Harvey Harrison3c2362e2008-01-30 13:31:03 +0100553 def_bool y
554 prompt "Should Calgary be enabled by default?"
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100555 depends on CALGARY_IOMMU
556 help
557 Should Calgary be enabled by default? if you choose 'y', Calgary
558 will be used (if it exists). If you choose 'n', Calgary will not be
559 used even if it exists. If you choose 'n' and would like to use
560 Calgary anyway, pass 'iommu=calgary' on the kernel command line.
561 If unsure, say Y.
562
Joerg Roedel2b188722008-06-26 21:27:37 +0200563config AMD_IOMMU
564 bool "AMD IOMMU support"
Ingo Molnar07c40e82008-06-27 11:31:28 +0200565 select SWIOTLB
Joerg Roedela80dc3e2008-09-11 16:51:41 +0200566 select PCI_MSI
Ingo Molnar24d2ba02008-06-27 10:37:03 +0200567 depends on X86_64 && PCI && ACPI
Joerg Roedel2b188722008-06-26 21:27:37 +0200568 help
Joerg Roedel18d22202008-07-03 19:35:06 +0200569 With this option you can enable support for AMD IOMMU hardware in
570 your system. An IOMMU is a hardware component which provides
571 remapping of DMA memory accesses from devices. With an AMD IOMMU you
572 can isolate the the DMA memory of different devices and protect the
573 system from misbehaving device drivers or hardware.
574
575 You can find out if your system has an AMD IOMMU if you look into
576 your BIOS for an option to enable it or if you have an IVRS ACPI
577 table.
Joerg Roedel2b188722008-06-26 21:27:37 +0200578
Joerg Roedel2e117602008-12-11 19:00:12 +0100579config AMD_IOMMU_STATS
580 bool "Export AMD IOMMU statistics to debugfs"
581 depends on AMD_IOMMU
582 select DEBUG_FS
583 help
584 This option enables code in the AMD IOMMU driver to collect various
585 statistics about whats happening in the driver and exports that
586 information to userspace via debugfs.
587 If unsure, say N.
588
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100589# need this always selected by IOMMU for the VIA workaround
590config SWIOTLB
Joerg Roedela1afd012008-11-18 12:44:21 +0100591 def_bool y if X86_64
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100592 help
593 Support for software bounce buffers used on x86-64 systems
594 which don't have a hardware IOMMU (e.g. the current generation
595 of Intel's x86-64 CPUs). Using this PCI devices which can only
596 access 32-bits of memory can be used on systems with more than
597 3 GB of memory. If unsure, say Y.
598
FUJITA Tomonoria8522502008-04-29 00:59:36 -0700599config IOMMU_HELPER
FUJITA Tomonori18b743d2008-07-10 09:50:50 +0900600 def_bool (CALGARY_IOMMU || GART_IOMMU || SWIOTLB || AMD_IOMMU)
Linus Torvaldsd25e26b2008-08-25 14:15:38 -0700601
Joerg Roedel1aaf1182008-11-26 17:25:13 +0100602config IOMMU_API
603 def_bool (AMD_IOMMU || DMAR)
604
Mike Travis1184dc22008-05-12 21:21:12 +0200605config MAXSMP
606 bool "Configure Maximum number of SMP Processors and NUMA Nodes"
Mike Travis36f51012008-12-16 17:33:51 -0800607 depends on X86_64 && SMP && DEBUG_KERNEL && EXPERIMENTAL
608 select CPUMASK_OFFSTACK
Mike Travis1184dc22008-05-12 21:21:12 +0200609 default n
610 help
611 Configure maximum number of CPUS and NUMA Nodes for this architecture.
612 If unsure, say N.
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100613
614config NR_CPUS
Mike Travis36f51012008-12-16 17:33:51 -0800615 int "Maximum number of CPUs" if SMP && !MAXSMP
616 range 2 512 if SMP && !MAXSMP
Mike Travis78637a972008-12-16 17:34:00 -0800617 default "1" if !SMP
Linus Torvaldsd25e26b2008-08-25 14:15:38 -0700618 default "4096" if MAXSMP
Mike Travis78637a972008-12-16 17:34:00 -0800619 default "32" if SMP && (X86_NUMAQ || X86_SUMMIT || X86_BIGSMP || X86_ES7000)
620 default "8" if SMP
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100621 help
622 This allows you to specify the maximum number of CPUs which this
Linus Torvaldsd25e26b2008-08-25 14:15:38 -0700623 kernel will support. The maximum supported value is 512 and the
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100624 minimum value which makes sense is 2.
625
626 This is purely to save memory - each supported CPU adds
627 approximately eight kilobytes to the kernel image.
628
629config SCHED_SMT
630 bool "SMT (Hyperthreading) scheduler support"
Hiroshi Shimamotob089c122008-02-27 13:16:30 -0800631 depends on X86_HT
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100632 help
633 SMT scheduler support improves the CPU scheduler's decision making
634 when dealing with Intel Pentium 4 chips with HyperThreading at a
635 cost of slightly increased overhead in some places. If unsure say
636 N here.
637
638config SCHED_MC
Harvey Harrison3c2362e2008-01-30 13:31:03 +0100639 def_bool y
640 prompt "Multi-core scheduler support"
Hiroshi Shimamotob089c122008-02-27 13:16:30 -0800641 depends on X86_HT
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100642 help
643 Multi-core scheduler support improves the CPU scheduler's decision
644 making when dealing with multi-core CPU chips at a cost of slightly
645 increased overhead in some places. If unsure say N here.
646
647source "kernel/Kconfig.preempt"
648
649config X86_UP_APIC
650 bool "Local APIC support on uniprocessors"
Ingo Molnare0c7ae32009-01-27 18:43:09 +0100651 depends on X86_32 && !SMP && !X86_32_NON_STANDARD
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100652 help
653 A local APIC (Advanced Programmable Interrupt Controller) is an
654 integrated interrupt controller in the CPU. If you have a single-CPU
655 system which has a processor with a local APIC, you can say Y here to
656 enable and use it. If you say Y here even though your machine doesn't
657 have a local APIC, then the kernel will still run with no slowdown at
658 all. The local APIC supports CPU-generated self-interrupts (timer,
659 performance counters), and the NMI watchdog which detects hard
660 lockups.
661
662config X86_UP_IOAPIC
663 bool "IO-APIC support on uniprocessors"
664 depends on X86_UP_APIC
665 help
666 An IO-APIC (I/O Advanced Programmable Interrupt Controller) is an
667 SMP-capable replacement for PC-style interrupt controllers. Most
668 SMP systems and many recent uniprocessor systems have one.
669
670 If you have a single-CPU system with an IO-APIC, you can say Y here
671 to use it. If you say Y here even though your machine doesn't have
672 an IO-APIC, then the kernel will still run with no slowdown at all.
673
674config X86_LOCAL_APIC
Harvey Harrison3c2362e2008-01-30 13:31:03 +0100675 def_bool y
Ingo Molnare0c7ae32009-01-27 18:43:09 +0100676 depends on X86_64 || SMP || X86_32_NON_STANDARD || X86_UP_APIC
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100677
678config X86_IO_APIC
Harvey Harrison3c2362e2008-01-30 13:31:03 +0100679 def_bool y
Ingo Molnare0c7ae32009-01-27 18:43:09 +0100680 depends on X86_64 || SMP || X86_32_NON_STANDARD || X86_UP_APIC
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100681
682config X86_VISWS_APIC
Harvey Harrison3c2362e2008-01-30 13:31:03 +0100683 def_bool y
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100684 depends on X86_32 && X86_VISWS
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100685
Stefan Assmann41b9eb22008-07-15 13:48:55 +0200686config X86_REROUTE_FOR_BROKEN_BOOT_IRQS
687 bool "Reroute for broken boot IRQs"
688 default n
689 depends on X86_IO_APIC
690 help
691 This option enables a workaround that fixes a source of
692 spurious interrupts. This is recommended when threaded
693 interrupt handling is used on systems where the generation of
694 superfluous "boot interrupts" cannot be disabled.
695
696 Some chipsets generate a legacy INTx "boot IRQ" when the IRQ
697 entry in the chipset's IO-APIC is masked (as, e.g. the RT
698 kernel does during interrupt handling). On chipsets where this
699 boot IRQ generation cannot be disabled, this workaround keeps
700 the original IRQ line masked so that only the equivalent "boot
701 IRQ" is delivered to the CPUs. The workaround also tells the
702 kernel to set up the IRQ handler on the boot IRQ line. In this
703 way only one interrupt is delivered to the kernel. Otherwise
704 the spurious second interrupt may cause the kernel to bring
705 down (vital) interrupt lines.
706
707 Only affects "broken" chipsets. Interrupt sharing may be
708 increased on these systems.
709
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100710config X86_MCE
711 bool "Machine Check Exception"
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100712 ---help---
713 Machine Check Exception support allows the processor to notify the
714 kernel if it detects a problem (e.g. overheating, component failure).
715 The action the kernel takes depends on the severity of the problem,
716 ranging from a warning message on the console, to halting the machine.
717 Your processor must be a Pentium or newer to support this - check the
718 flags in /proc/cpuinfo for mce. Note that some older Pentium systems
719 have a design flaw which leads to false MCE events - hence MCE is
720 disabled on all P5 processors, unless explicitly enabled with "mce"
721 as a boot argument. Similarly, if MCE is built in and creates a
722 problem on some new non-standard machine, you can boot with "nomce"
723 to disable it. MCE support simply ignores non-MCE processors like
724 the 386 and 486, so nearly everyone can say Y here.
725
726config X86_MCE_INTEL
Harvey Harrison3c2362e2008-01-30 13:31:03 +0100727 def_bool y
728 prompt "Intel MCE features"
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100729 depends on X86_64 && X86_MCE && X86_LOCAL_APIC
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100730 help
731 Additional support for intel specific MCE features such as
732 the thermal monitor.
733
734config X86_MCE_AMD
Harvey Harrison3c2362e2008-01-30 13:31:03 +0100735 def_bool y
736 prompt "AMD MCE features"
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100737 depends on X86_64 && X86_MCE && X86_LOCAL_APIC
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100738 help
739 Additional support for AMD specific MCE features such as
740 the DRAM Error Threshold.
741
742config X86_MCE_NONFATAL
743 tristate "Check for non-fatal errors on AMD Athlon/Duron / Intel Pentium 4"
744 depends on X86_32 && X86_MCE
745 help
746 Enabling this feature starts a timer that triggers every 5 seconds which
747 will look at the machine check registers to see if anything happened.
748 Non-fatal problems automatically get corrected (but still logged).
749 Disable this if you don't want to see these messages.
750 Seeing the messages this option prints out may be indicative of dying
751 or out-of-spec (ie, overclocked) hardware.
752 This option only does something on certain CPUs.
753 (AMD Athlon/Duron and Intel Pentium 4)
754
755config X86_MCE_P4THERMAL
756 bool "check for P4 thermal throttling interrupt."
Ingo Molnarefefa6f2008-07-10 16:09:50 +0200757 depends on X86_32 && X86_MCE && (X86_UP_APIC || SMP)
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100758 help
759 Enabling this feature will cause a message to be printed when the P4
760 enters thermal throttling.
761
762config VM86
763 bool "Enable VM86 support" if EMBEDDED
764 default y
765 depends on X86_32
766 help
767 This option is required by programs like DOSEMU to run 16-bit legacy
768 code on X86 processors. It also may be needed by software like
769 XFree86 to initialize some video cards via BIOS. Disabling this
770 option saves about 6k.
771
772config TOSHIBA
773 tristate "Toshiba Laptop support"
774 depends on X86_32
775 ---help---
776 This adds a driver to safely access the System Management Mode of
777 the CPU on Toshiba portables with a genuine Toshiba BIOS. It does
778 not work on models with a Phoenix BIOS. The System Management Mode
779 is used to set the BIOS and power saving options on Toshiba portables.
780
781 For information on utilities to make use of this driver see the
782 Toshiba Linux utilities web site at:
783 <http://www.buzzard.org.uk/toshiba/>.
784
785 Say Y if you intend to run this kernel on a Toshiba portable.
786 Say N otherwise.
787
788config I8K
789 tristate "Dell laptop support"
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100790 ---help---
791 This adds a driver to safely access the System Management Mode
792 of the CPU on the Dell Inspiron 8000. The System Management Mode
793 is used to read cpu temperature and cooling fan status and to
794 control the fans on the I8K portables.
795
796 This driver has been tested only on the Inspiron 8000 but it may
797 also work with other Dell laptops. You can force loading on other
798 models by passing the parameter `force=1' to the module. Use at
799 your own risk.
800
801 For information on utilities to make use of this driver see the
802 I8K Linux utilities web site at:
803 <http://people.debian.org/~dz/i8k/>
804
805 Say Y if you intend to run this kernel on a Dell Inspiron 8000.
806 Say N otherwise.
807
808config X86_REBOOTFIXUPS
Jan Beulich9ba16082008-10-15 22:01:38 -0700809 bool "Enable X86 board specific fixups for reboot"
810 depends on X86_32
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100811 ---help---
812 This enables chipset and/or board specific fixups to be done
813 in order to get reboot to work correctly. This is only needed on
814 some combinations of hardware and BIOS. The symptom, for which
815 this config is intended, is when reboot ends with a stalled/hung
816 system.
817
818 Currently, the only fixup is for the Geode machines using
Florian Fainelli5e3a77e2008-01-30 13:33:36 +0100819 CS5530A and CS5536 chipsets and the RDC R-321x SoC.
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100820
821 Say Y if you want to enable the fixup. Currently, it's safe to
822 enable this option even if you don't need it.
823 Say N otherwise.
824
825config MICROCODE
Peter Oruba8d86f392008-07-28 18:44:21 +0200826 tristate "/dev/cpu/microcode - microcode support"
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100827 select FW_LOADER
828 ---help---
829 If you say Y here, you will be able to update the microcode on
Peter Oruba80cc9f12008-07-28 18:44:22 +0200830 certain Intel and AMD processors. The Intel support is for the
831 IA32 family, e.g. Pentium Pro, Pentium II, Pentium III,
832 Pentium 4, Xeon etc. The AMD support is for family 0x10 and
833 0x11 processors, e.g. Opteron, Phenom and Turion 64 Ultra.
834 You will obviously need the actual microcode binary data itself
835 which is not shipped with the Linux kernel.
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100836
Peter Oruba8d86f392008-07-28 18:44:21 +0200837 This option selects the general module only, you need to select
838 at least one vendor specific module as well.
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100839
840 To compile this driver as a module, choose M here: the
841 module will be called microcode.
842
Peter Oruba8d86f392008-07-28 18:44:21 +0200843config MICROCODE_INTEL
Dmitry Adamushko18dbc912008-09-23 12:08:44 +0200844 bool "Intel microcode patch loading support"
Peter Oruba8d86f392008-07-28 18:44:21 +0200845 depends on MICROCODE
846 default MICROCODE
847 select FW_LOADER
848 --help---
849 This options enables microcode patch loading support for Intel
850 processors.
851
852 For latest news and information on obtaining all the required
853 Intel ingredients for this driver, check:
854 <http://www.urbanmyth.org/microcode/>.
855
Peter Oruba80cc9f12008-07-28 18:44:22 +0200856config MICROCODE_AMD
Dmitry Adamushko18dbc912008-09-23 12:08:44 +0200857 bool "AMD microcode patch loading support"
Peter Oruba80cc9f12008-07-28 18:44:22 +0200858 depends on MICROCODE
859 select FW_LOADER
860 --help---
861 If you select this option, microcode patch loading support for AMD
862 processors will be enabled.
863
Peter Oruba8d86f392008-07-28 18:44:21 +0200864 config MICROCODE_OLD_INTERFACE
Harvey Harrison3c2362e2008-01-30 13:31:03 +0100865 def_bool y
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100866 depends on MICROCODE
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100867
868config X86_MSR
869 tristate "/dev/cpu/*/msr - Model-specific register support"
870 help
871 This device gives privileged processes access to the x86
872 Model-Specific Registers (MSRs). It is a character device with
873 major 202 and minors 0 to 31 for /dev/cpu/0/msr to /dev/cpu/31/msr.
874 MSR accesses are directed to a specific CPU on multi-processor
875 systems.
876
877config X86_CPUID
878 tristate "/dev/cpu/*/cpuid - CPU information support"
879 help
880 This device gives processes access to the x86 CPUID instruction to
881 be executed on a specific processor. It is a character device
882 with major 203 and minors 0 to 31 for /dev/cpu/0/cpuid to
883 /dev/cpu/31/cpuid.
884
885choice
886 prompt "High Memory Support"
887 default HIGHMEM4G if !X86_NUMAQ
888 default HIGHMEM64G if X86_NUMAQ
889 depends on X86_32
890
891config NOHIGHMEM
892 bool "off"
893 depends on !X86_NUMAQ
894 ---help---
895 Linux can use up to 64 Gigabytes of physical memory on x86 systems.
896 However, the address space of 32-bit x86 processors is only 4
897 Gigabytes large. That means that, if you have a large amount of
898 physical memory, not all of it can be "permanently mapped" by the
899 kernel. The physical memory that's not permanently mapped is called
900 "high memory".
901
902 If you are compiling a kernel which will never run on a machine with
903 more than 1 Gigabyte total physical RAM, answer "off" here (default
904 choice and suitable for most users). This will result in a "3GB/1GB"
905 split: 3GB are mapped so that each process sees a 3GB virtual memory
906 space and the remaining part of the 4GB virtual memory space is used
907 by the kernel to permanently map as much physical memory as
908 possible.
909
910 If the machine has between 1 and 4 Gigabytes physical RAM, then
911 answer "4GB" here.
912
913 If more than 4 Gigabytes is used then answer "64GB" here. This
914 selection turns Intel PAE (Physical Address Extension) mode on.
915 PAE implements 3-level paging on IA32 processors. PAE is fully
916 supported by Linux, PAE mode is implemented on all recent Intel
917 processors (Pentium Pro and better). NOTE: If you say "64GB" here,
918 then the kernel will not boot on CPUs that don't support PAE!
919
920 The actual amount of total physical memory will either be
921 auto detected or can be forced by using a kernel command line option
922 such as "mem=256M". (Try "man bootparam" or see the documentation of
923 your boot loader (lilo or loadlin) about how to pass options to the
924 kernel at boot time.)
925
926 If unsure, say "off".
927
928config HIGHMEM4G
929 bool "4GB"
930 depends on !X86_NUMAQ
931 help
932 Select this if you have a 32-bit processor and between 1 and 4
933 gigabytes of physical RAM.
934
935config HIGHMEM64G
936 bool "64GB"
937 depends on !M386 && !M486
938 select X86_PAE
939 help
940 Select this if you have a 32-bit processor and more than 4
941 gigabytes of physical RAM.
942
943endchoice
944
945choice
946 depends on EXPERIMENTAL
947 prompt "Memory split" if EMBEDDED
948 default VMSPLIT_3G
949 depends on X86_32
950 help
951 Select the desired split between kernel and user memory.
952
953 If the address range available to the kernel is less than the
954 physical memory installed, the remaining memory will be available
955 as "high memory". Accessing high memory is a little more costly
956 than low memory, as it needs to be mapped into the kernel first.
957 Note that increasing the kernel address space limits the range
958 available to user programs, making the address space there
959 tighter. Selecting anything other than the default 3G/1G split
960 will also likely make your kernel incompatible with binary-only
961 kernel modules.
962
963 If you are not absolutely sure what you are doing, leave this
964 option alone!
965
966 config VMSPLIT_3G
967 bool "3G/1G user/kernel split"
968 config VMSPLIT_3G_OPT
969 depends on !X86_PAE
970 bool "3G/1G user/kernel split (for full 1G low memory)"
971 config VMSPLIT_2G
972 bool "2G/2G user/kernel split"
973 config VMSPLIT_2G_OPT
974 depends on !X86_PAE
975 bool "2G/2G user/kernel split (for full 2G low memory)"
976 config VMSPLIT_1G
977 bool "1G/3G user/kernel split"
978endchoice
979
980config PAGE_OFFSET
981 hex
982 default 0xB0000000 if VMSPLIT_3G_OPT
983 default 0x80000000 if VMSPLIT_2G
984 default 0x78000000 if VMSPLIT_2G_OPT
985 default 0x40000000 if VMSPLIT_1G
986 default 0xC0000000
987 depends on X86_32
988
989config HIGHMEM
Harvey Harrison3c2362e2008-01-30 13:31:03 +0100990 def_bool y
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100991 depends on X86_32 && (HIGHMEM64G || HIGHMEM4G)
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100992
993config X86_PAE
Jan Beulich9ba16082008-10-15 22:01:38 -0700994 bool "PAE (Physical Address Extension) Support"
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100995 depends on X86_32 && !HIGHMEM4G
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100996 help
997 PAE is required for NX support, and furthermore enables
998 larger swapspace support for non-overcommit purposes. It
999 has the cost of more pagetable lookup overhead, and also
1000 consumes more pagetable space per process.
1001
Jeremy Fitzhardinge600715d2008-09-11 01:31:45 -07001002config ARCH_PHYS_ADDR_T_64BIT
1003 def_bool X86_64 || X86_PAE
1004
Nick Piggin9e899812008-10-22 12:33:16 +02001005config DIRECT_GBPAGES
1006 bool "Enable 1GB pages for kernel pagetables" if EMBEDDED
1007 default y
1008 depends on X86_64
1009 help
1010 Allow the kernel linear mapping to use 1GB pages on CPUs that
1011 support it. This can improve the kernel's performance a tiny bit by
1012 reducing TLB pressure. If in doubt, say "Y".
1013
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001014# Common NUMA Features
1015config NUMA
KOSAKI Motohirofd51b2d2008-11-05 02:27:19 +09001016 bool "Numa Memory Allocation and Scheduler Support"
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001017 depends on SMP
Yinghai Lu0699eae2008-06-17 15:39:01 -07001018 depends on X86_64 || (X86_32 && HIGHMEM64G && (X86_NUMAQ || X86_BIGSMP || X86_SUMMIT && ACPI) && EXPERIMENTAL)
Yinghai Lu0699eae2008-06-17 15:39:01 -07001019 default y if (X86_NUMAQ || X86_SUMMIT || X86_BIGSMP)
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001020 help
1021 Enable NUMA (Non Uniform Memory Access) support.
KOSAKI Motohirofd51b2d2008-11-05 02:27:19 +09001022
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001023 The kernel will try to allocate memory used by a CPU on the
1024 local memory controller of the CPU and add some more
1025 NUMA awareness to the kernel.
1026
Ingo Molnarc280ea52008-11-08 13:29:45 +01001027 For 64-bit this is recommended if the system is Intel Core i7
KOSAKI Motohirofd51b2d2008-11-05 02:27:19 +09001028 (or later), AMD Opteron, or EM64T NUMA.
1029
1030 For 32-bit this is only needed on (rare) 32-bit-only platforms
1031 that support NUMA topologies, such as NUMAQ / Summit, or if you
1032 boot a 32-bit kernel on a 64-bit NUMA platform.
1033
1034 Otherwise, you should say N.
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001035
1036comment "NUMA (Summit) requires SMP, 64GB highmem support, ACPI"
1037 depends on X86_32 && X86_SUMMIT && (!HIGHMEM64G || !ACPI)
1038
1039config K8_NUMA
Harvey Harrison3c2362e2008-01-30 13:31:03 +01001040 def_bool y
1041 prompt "Old style AMD Opteron NUMA detection"
1042 depends on X86_64 && NUMA && PCI
1043 help
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001044 Enable K8 NUMA node topology detection. You should say Y here if
1045 you have a multi processor AMD K8 system. This uses an old
1046 method to read the NUMA configuration directly from the builtin
1047 Northbridge of Opteron. It is recommended to use X86_64_ACPI_NUMA
1048 instead, which also takes priority if both are compiled in.
1049
1050config X86_64_ACPI_NUMA
Harvey Harrison3c2362e2008-01-30 13:31:03 +01001051 def_bool y
1052 prompt "ACPI NUMA detection"
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001053 depends on X86_64 && NUMA && ACPI && PCI
1054 select ACPI_NUMA
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001055 help
1056 Enable ACPI SRAT based node topology detection.
1057
Suresh Siddha6ec6e0d2008-03-25 10:14:35 -07001058# Some NUMA nodes have memory ranges that span
1059# other nodes. Even though a pfn is valid and
1060# between a node's start and end pfns, it may not
1061# reside on that node. See memmap_init_zone()
1062# for details.
1063config NODES_SPAN_OTHER_NODES
1064 def_bool y
1065 depends on X86_64_ACPI_NUMA
1066
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001067config NUMA_EMU
1068 bool "NUMA emulation"
1069 depends on X86_64 && NUMA
1070 help
1071 Enable NUMA emulation. A flat machine will be split
1072 into virtual nodes when booted with "numa=fake=N", where N is the
1073 number of nodes. This is only useful for debugging.
1074
1075config NODES_SHIFT
Linus Torvaldsd25e26b2008-08-25 14:15:38 -07001076 int "Maximum NUMA Nodes (as a power of 2)" if !MAXSMP
Mike Travis1184dc22008-05-12 21:21:12 +02001077 range 1 9 if X86_64
Linus Torvaldsd25e26b2008-08-25 14:15:38 -07001078 default "9" if MAXSMP
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001079 default "6" if X86_64
1080 default "4" if X86_NUMAQ
1081 default "3"
1082 depends on NEED_MULTIPLE_NODES
Mike Travis1184dc22008-05-12 21:21:12 +02001083 help
1084 Specify the maximum number of NUMA Nodes available on the target
1085 system. Increases memory reserved to accomodate various tables.
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001086
1087config HAVE_ARCH_BOOTMEM_NODE
Harvey Harrison3c2362e2008-01-30 13:31:03 +01001088 def_bool y
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001089 depends on X86_32 && NUMA
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001090
1091config ARCH_HAVE_MEMORY_PRESENT
Harvey Harrison3c2362e2008-01-30 13:31:03 +01001092 def_bool y
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001093 depends on X86_32 && DISCONTIGMEM
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001094
1095config NEED_NODE_MEMMAP_SIZE
Harvey Harrison3c2362e2008-01-30 13:31:03 +01001096 def_bool y
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001097 depends on X86_32 && (DISCONTIGMEM || SPARSEMEM)
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001098
1099config HAVE_ARCH_ALLOC_REMAP
Harvey Harrison3c2362e2008-01-30 13:31:03 +01001100 def_bool y
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001101 depends on X86_32 && NUMA
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001102
1103config ARCH_FLATMEM_ENABLE
1104 def_bool y
Jeff Chua99809962008-08-06 19:09:53 +08001105 depends on X86_32 && ARCH_SELECT_MEMORY_MODEL && !NUMA
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001106
1107config ARCH_DISCONTIGMEM_ENABLE
1108 def_bool y
Christoph Lameterb2632952008-01-30 13:30:47 +01001109 depends on NUMA && X86_32
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001110
1111config ARCH_DISCONTIGMEM_DEFAULT
1112 def_bool y
Christoph Lameterb2632952008-01-30 13:30:47 +01001113 depends on NUMA && X86_32
1114
1115config ARCH_SPARSEMEM_DEFAULT
1116 def_bool y
1117 depends on X86_64
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001118
1119config ARCH_SPARSEMEM_ENABLE
1120 def_bool y
Yinghai Lu4272ebf2009-01-29 15:14:46 -08001121 depends on X86_64 || NUMA || (EXPERIMENTAL && X86_32) || X86_32_NON_STANDARD
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001122 select SPARSEMEM_STATIC if X86_32
1123 select SPARSEMEM_VMEMMAP_ENABLE if X86_64
1124
1125config ARCH_SELECT_MEMORY_MODEL
1126 def_bool y
Christoph Lameterb2632952008-01-30 13:30:47 +01001127 depends on ARCH_SPARSEMEM_ENABLE
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001128
1129config ARCH_MEMORY_PROBE
1130 def_bool X86_64
1131 depends on MEMORY_HOTPLUG
1132
1133source "mm/Kconfig"
1134
1135config HIGHPTE
1136 bool "Allocate 3rd-level pagetables from highmem"
1137 depends on X86_32 && (HIGHMEM4G || HIGHMEM64G)
1138 help
1139 The VM uses one page table entry for each page of physical memory.
1140 For systems with a lot of RAM, this can be wasteful of precious
1141 low memory. Setting this option will put user-space page table
1142 entries in high memory.
1143
Jeremy Fitzhardinge9f077872008-09-07 01:51:34 -07001144config X86_CHECK_BIOS_CORRUPTION
1145 bool "Check for low memory corruption"
Jeremy Fitzhardinge9f077872008-09-07 01:51:34 -07001146 help
1147 Periodically check for memory corruption in low memory, which
1148 is suspected to be caused by BIOS. Even when enabled in the
1149 configuration, it is disabled at runtime. Enable it by
1150 setting "memory_corruption_check=1" on the kernel command
1151 line. By default it scans the low 64k of memory every 60
1152 seconds; see the memory_corruption_check_size and
1153 memory_corruption_check_period parameters in
1154 Documentation/kernel-parameters.txt to adjust this.
1155
1156 When enabled with the default parameters, this option has
1157 almost no overhead, as it reserves a relatively small amount
1158 of memory and scans it infrequently. It both detects corruption
1159 and prevents it from affecting the running system.
1160
1161 It is, however, intended as a diagnostic tool; if repeatable
1162 BIOS-originated corruption always affects the same memory,
1163 you can use memmap= to prevent the kernel from using that
1164 memory.
1165
Jeremy Fitzhardingec885df52008-09-07 02:37:32 -07001166config X86_BOOTPARAM_MEMORY_CORRUPTION_CHECK
1167 bool "Set the default setting of memory_corruption_check"
1168 depends on X86_CHECK_BIOS_CORRUPTION
1169 default y
1170 help
1171 Set whether the default state of memory_corruption_check is
1172 on or off.
1173
Ingo Molnarfc381512008-09-16 10:07:34 +02001174config X86_RESERVE_LOW_64K
1175 bool "Reserve low 64K of RAM on AMI/Phoenix BIOSen"
1176 default y
1177 help
1178 Reserve the first 64K of physical RAM on BIOSes that are known
1179 to potentially corrupt that memory range. A numbers of BIOSes are
1180 known to utilize this area during suspend/resume, so it must not
1181 be used by the kernel.
1182
1183 Set this to N if you are absolutely sure that you trust the BIOS
1184 to get all its memory reservations and usages right.
1185
1186 If you have doubts about the BIOS (e.g. suspend/resume does not
1187 work or there's kernel crashes after certain hardware hotplug
1188 events) and it's not AMI or Phoenix, then you might want to enable
1189 X86_CHECK_BIOS_CORRUPTION=y to allow the kernel to check typical
1190 corruption patterns.
1191
1192 Say Y if unsure.
1193
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001194config MATH_EMULATION
1195 bool
1196 prompt "Math emulation" if X86_32
1197 ---help---
1198 Linux can emulate a math coprocessor (used for floating point
1199 operations) if you don't have one. 486DX and Pentium processors have
1200 a math coprocessor built in, 486SX and 386 do not, unless you added
1201 a 487DX or 387, respectively. (The messages during boot time can
1202 give you some hints here ["man dmesg"].) Everyone needs either a
1203 coprocessor or this emulation.
1204
1205 If you don't have a math coprocessor, you need to say Y here; if you
1206 say Y here even though you have a coprocessor, the coprocessor will
1207 be used nevertheless. (This behavior can be changed with the kernel
1208 command line option "no387", which comes handy if your coprocessor
1209 is broken. Try "man bootparam" or see the documentation of your boot
1210 loader (lilo or loadlin) about how to pass options to the kernel at
1211 boot time.) This means that it is a good idea to say Y here if you
1212 intend to use this kernel on different machines.
1213
1214 More information about the internals of the Linux math coprocessor
1215 emulation can be found in <file:arch/x86/math-emu/README>.
1216
1217 If you are not sure, say Y; apart from resulting in a 66 KB bigger
1218 kernel, it won't hurt.
1219
1220config MTRR
1221 bool "MTRR (Memory Type Range Register) support"
1222 ---help---
1223 On Intel P6 family processors (Pentium Pro, Pentium II and later)
1224 the Memory Type Range Registers (MTRRs) may be used to control
1225 processor access to memory ranges. This is most useful if you have
1226 a video (VGA) card on a PCI or AGP bus. Enabling write-combining
1227 allows bus write transfers to be combined into a larger transfer
1228 before bursting over the PCI/AGP bus. This can increase performance
1229 of image write operations 2.5 times or more. Saying Y here creates a
1230 /proc/mtrr file which may be used to manipulate your processor's
1231 MTRRs. Typically the X server should use this.
1232
1233 This code has a reasonably generic interface so that similar
1234 control registers on other processors can be easily supported
1235 as well:
1236
1237 The Cyrix 6x86, 6x86MX and M II processors have Address Range
1238 Registers (ARRs) which provide a similar functionality to MTRRs. For
1239 these, the ARRs are used to emulate the MTRRs.
1240 The AMD K6-2 (stepping 8 and above) and K6-3 processors have two
1241 MTRRs. The Centaur C6 (WinChip) has 8 MCRs, allowing
1242 write-combining. All of these processors are supported by this code
1243 and it makes sense to say Y here if you have one of them.
1244
1245 Saying Y here also fixes a problem with buggy SMP BIOSes which only
1246 set the MTRRs for the boot CPU and not for the secondary CPUs. This
1247 can lead to all sorts of problems, so it's good to say Y here.
1248
1249 You can safely say Y even if your machine doesn't have MTRRs, you'll
1250 just add about 9 KB to your kernel.
1251
Randy Dunlap7225e752008-07-26 17:54:22 -07001252 See <file:Documentation/x86/mtrr.txt> for more information.
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001253
Yinghai Lu95ffa242008-04-29 03:52:33 -07001254config MTRR_SANITIZER
Yinghai Lu2ffb3502008-09-30 16:29:40 -07001255 def_bool y
Yinghai Lu95ffa242008-04-29 03:52:33 -07001256 prompt "MTRR cleanup support"
1257 depends on MTRR
1258 help
Thomas Gleixneraba37282008-07-15 14:48:48 +02001259 Convert MTRR layout from continuous to discrete, so X drivers can
1260 add writeback entries.
Yinghai Lu95ffa242008-04-29 03:52:33 -07001261
Thomas Gleixneraba37282008-07-15 14:48:48 +02001262 Can be disabled with disable_mtrr_cleanup on the kernel command line.
1263 The largest mtrr entry size for a continous block can be set with
1264 mtrr_chunk_size.
Yinghai Lu95ffa242008-04-29 03:52:33 -07001265
Yinghai Lu2ffb3502008-09-30 16:29:40 -07001266 If unsure, say Y.
Yinghai Lu95ffa242008-04-29 03:52:33 -07001267
1268config MTRR_SANITIZER_ENABLE_DEFAULT
Yinghai Luf5098d62008-04-29 20:25:58 -07001269 int "MTRR cleanup enable value (0-1)"
1270 range 0 1
1271 default "0"
Yinghai Lu95ffa242008-04-29 03:52:33 -07001272 depends on MTRR_SANITIZER
1273 help
Yinghai Luf5098d62008-04-29 20:25:58 -07001274 Enable mtrr cleanup default value
Yinghai Lu95ffa242008-04-29 03:52:33 -07001275
Yinghai Lu12031a62008-05-02 02:40:22 -07001276config MTRR_SANITIZER_SPARE_REG_NR_DEFAULT
1277 int "MTRR cleanup spare reg num (0-7)"
1278 range 0 7
1279 default "1"
1280 depends on MTRR_SANITIZER
1281 help
1282 mtrr cleanup spare entries default, it can be changed via
Thomas Gleixneraba37282008-07-15 14:48:48 +02001283 mtrr_spare_reg_nr=N on the kernel command line.
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001284
venkatesh.pallipadi@intel.com2e5d9c82008-03-18 17:00:14 -07001285config X86_PAT
Ingo Molnar2a8a2712008-04-26 10:26:52 +02001286 bool
venkatesh.pallipadi@intel.com2e5d9c82008-03-18 17:00:14 -07001287 prompt "x86 PAT support"
Ingo Molnar2a8a2712008-04-26 10:26:52 +02001288 depends on MTRR
venkatesh.pallipadi@intel.com2e5d9c82008-03-18 17:00:14 -07001289 help
1290 Use PAT attributes to setup page level cache control.
Venki Pallipadi042b78e2008-03-24 14:22:35 -07001291
venkatesh.pallipadi@intel.com2e5d9c82008-03-18 17:00:14 -07001292 PATs are the modern equivalents of MTRRs and are much more
1293 flexible than MTRRs.
1294
1295 Say N here if you see bootup problems (boot crash, boot hang,
Venki Pallipadi042b78e2008-03-24 14:22:35 -07001296 spontaneous reboots) or a non-working video driver.
venkatesh.pallipadi@intel.com2e5d9c82008-03-18 17:00:14 -07001297
1298 If unsure, say Y.
1299
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001300config EFI
Jan Beulich9ba16082008-10-15 22:01:38 -07001301 bool "EFI runtime service support"
Huang, Ying5b836832008-01-30 13:31:19 +01001302 depends on ACPI
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001303 ---help---
Huang, Ying8b2cb7a2008-01-30 13:32:11 +01001304 This enables the kernel to use EFI runtime services that are
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001305 available (such as the EFI variable services).
1306
Huang, Ying8b2cb7a2008-01-30 13:32:11 +01001307 This option is only useful on systems that have EFI firmware.
1308 In addition, you should use the latest ELILO loader available
1309 at <http://elilo.sourceforge.net> in order to take advantage
1310 of EFI runtime services. However, even with this option, the
1311 resultant kernel should continue to boot on existing non-EFI
1312 platforms.
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001313
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001314config SECCOMP
Harvey Harrison3c2362e2008-01-30 13:31:03 +01001315 def_bool y
1316 prompt "Enable seccomp to safely compute untrusted bytecode"
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001317 help
1318 This kernel feature is useful for number crunching applications
1319 that may need to compute untrusted bytecode during their
1320 execution. By using pipes or other transports made available to
1321 the process as file descriptors supporting the read/write
1322 syscalls, it's possible to isolate those applications in
1323 their own address space using seccomp. Once seccomp is
Alexey Dobriyan9c0bbee2008-09-09 11:01:31 +04001324 enabled via prctl(PR_SET_SECCOMP), it cannot be disabled
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001325 and the task is only allowed to execute a few safe syscalls
1326 defined by each seccomp mode.
1327
1328 If unsure, say Y. Only embedded should say N here.
1329
Ingo Molnar113c5412008-02-14 10:36:03 +01001330config CC_STACKPROTECTOR_ALL
1331 bool
1332
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001333config CC_STACKPROTECTOR
1334 bool "Enable -fstack-protector buffer overflow detection (EXPERIMENTAL)"
Ingo Molnar72370f22008-02-13 16:15:34 +01001335 depends on X86_64
Ingo Molnar113c5412008-02-14 10:36:03 +01001336 select CC_STACKPROTECTOR_ALL
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001337 help
Ingo Molnar113c5412008-02-14 10:36:03 +01001338 This option turns on the -fstack-protector GCC feature. This
1339 feature puts, at the beginning of functions, a canary value on
1340 the stack just before the return address, and validates
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001341 the value just before actually returning. Stack based buffer
1342 overflows (that need to overwrite this return address) now also
1343 overwrite the canary, which gets detected and the attack is then
1344 neutralized via a kernel panic.
1345
1346 This feature requires gcc version 4.2 or above, or a distribution
1347 gcc with the feature backported. Older versions are automatically
Ingo Molnar113c5412008-02-14 10:36:03 +01001348 detected and for those versions, this configuration option is
1349 ignored. (and a warning is printed during bootup)
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001350
1351source kernel/Kconfig.hz
1352
1353config KEXEC
1354 bool "kexec system call"
1355 help
1356 kexec is a system call that implements the ability to shutdown your
1357 current kernel, and to start another kernel. It is like a reboot
1358 but it is independent of the system firmware. And like a reboot
1359 you can start any kernel with it, not just Linux.
1360
1361 The name comes from the similarity to the exec system call.
1362
1363 It is an ongoing process to be certain the hardware in a machine
1364 is properly shutdown, so do not be surprised if this code does not
1365 initially work for you. It may help to enable device hotplugging
1366 support. As of this writing the exact hardware interface is
1367 strongly in flux, so no good recommendation can be made.
1368
1369config CRASH_DUMP
Pavel Machek04b69442008-08-14 17:16:50 +02001370 bool "kernel crash dumps"
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001371 depends on X86_64 || (X86_32 && HIGHMEM)
1372 help
1373 Generate crash dump after being started by kexec.
1374 This should be normally only set in special crash dump kernels
1375 which are loaded in the main kernel with kexec-tools into
1376 a specially reserved region and then later executed after
1377 a crash by kdump/kexec. The crash dump kernel must be compiled
1378 to a memory address not used by the main kernel or BIOS using
1379 PHYSICAL_START, or it must be built as a relocatable image
1380 (CONFIG_RELOCATABLE=y).
1381 For more details see Documentation/kdump/kdump.txt
1382
Huang Ying3ab83522008-07-25 19:45:07 -07001383config KEXEC_JUMP
1384 bool "kexec jump (EXPERIMENTAL)"
1385 depends on EXPERIMENTAL
Huang Ying89081d12008-07-25 19:45:10 -07001386 depends on KEXEC && HIBERNATION && X86_32
Huang Ying3ab83522008-07-25 19:45:07 -07001387 help
Huang Ying89081d12008-07-25 19:45:10 -07001388 Jump between original kernel and kexeced kernel and invoke
1389 code in physical address mode via KEXEC
Huang Ying3ab83522008-07-25 19:45:07 -07001390
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001391config PHYSICAL_START
1392 hex "Physical address where the kernel is loaded" if (EMBEDDED || CRASH_DUMP)
1393 default "0x1000000" if X86_NUMAQ
1394 default "0x200000" if X86_64
1395 default "0x100000"
1396 help
1397 This gives the physical address where the kernel is loaded.
1398
1399 If kernel is a not relocatable (CONFIG_RELOCATABLE=n) then
1400 bzImage will decompress itself to above physical address and
1401 run from there. Otherwise, bzImage will run from the address where
1402 it has been loaded by the boot loader and will ignore above physical
1403 address.
1404
1405 In normal kdump cases one does not have to set/change this option
1406 as now bzImage can be compiled as a completely relocatable image
1407 (CONFIG_RELOCATABLE=y) and be used to load and run from a different
1408 address. This option is mainly useful for the folks who don't want
1409 to use a bzImage for capturing the crash dump and want to use a
1410 vmlinux instead. vmlinux is not relocatable hence a kernel needs
1411 to be specifically compiled to run from a specific memory area
1412 (normally a reserved region) and this option comes handy.
1413
1414 So if you are using bzImage for capturing the crash dump, leave
1415 the value here unchanged to 0x100000 and set CONFIG_RELOCATABLE=y.
1416 Otherwise if you plan to use vmlinux for capturing the crash dump
1417 change this value to start of the reserved region (Typically 16MB
1418 0x1000000). In other words, it can be set based on the "X" value as
1419 specified in the "crashkernel=YM@XM" command line boot parameter
1420 passed to the panic-ed kernel. Typically this parameter is set as
1421 crashkernel=64M@16M. Please take a look at
1422 Documentation/kdump/kdump.txt for more details about crash dumps.
1423
1424 Usage of bzImage for capturing the crash dump is recommended as
1425 one does not have to build two kernels. Same kernel can be used
1426 as production kernel and capture kernel. Above option should have
1427 gone away after relocatable bzImage support is introduced. But it
1428 is present because there are users out there who continue to use
1429 vmlinux for dump capture. This option should go away down the
1430 line.
1431
1432 Don't change this unless you know what you are doing.
1433
1434config RELOCATABLE
1435 bool "Build a relocatable kernel (EXPERIMENTAL)"
1436 depends on EXPERIMENTAL
1437 help
1438 This builds a kernel image that retains relocation information
1439 so it can be loaded someplace besides the default 1MB.
1440 The relocations tend to make the kernel binary about 10% larger,
1441 but are discarded at runtime.
1442
1443 One use is for the kexec on panic case where the recovery kernel
1444 must live at a different physical address than the primary
1445 kernel.
1446
1447 Note: If CONFIG_RELOCATABLE=y, then the kernel runs from the address
1448 it has been loaded at and the compile time physical address
1449 (CONFIG_PHYSICAL_START) is ignored.
1450
1451config PHYSICAL_ALIGN
1452 hex
1453 prompt "Alignment value to which kernel should be aligned" if X86_32
1454 default "0x100000" if X86_32
1455 default "0x200000" if X86_64
1456 range 0x2000 0x400000
1457 help
1458 This value puts the alignment restrictions on physical address
1459 where kernel is loaded and run from. Kernel is compiled for an
1460 address which meets above alignment restriction.
1461
1462 If bootloader loads the kernel at a non-aligned address and
1463 CONFIG_RELOCATABLE is set, kernel will move itself to nearest
1464 address aligned to above value and run from there.
1465
1466 If bootloader loads the kernel at a non-aligned address and
1467 CONFIG_RELOCATABLE is not set, kernel will ignore the run time
1468 load address and decompress itself to the address it has been
1469 compiled for and run from there. The address for which kernel is
1470 compiled already meets above alignment restrictions. Hence the
1471 end result is that kernel runs from a physical address meeting
1472 above alignment restrictions.
1473
1474 Don't change this unless you know what you are doing.
1475
1476config HOTPLUG_CPU
Dimitri Sivanich7c13e6a2008-08-11 10:46:46 -05001477 bool "Support for hot-pluggable CPUs"
Ingo Molnar4b19ed912009-01-27 17:47:24 +01001478 depends on SMP && HOTPLUG
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001479 ---help---
Dimitri Sivanich7c13e6a2008-08-11 10:46:46 -05001480 Say Y here to allow turning CPUs off and on. CPUs can be
1481 controlled through /sys/devices/system/cpu.
1482 ( Note: power management support will enable this option
1483 automatically on SMP systems. )
1484 Say N if you want to disable CPU hotplug.
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001485
1486config COMPAT_VDSO
Harvey Harrison3c2362e2008-01-30 13:31:03 +01001487 def_bool y
1488 prompt "Compat VDSO support"
Roland McGrathaf65d642008-01-30 13:30:43 +01001489 depends on X86_32 || IA32_EMULATION
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001490 help
Roland McGrathaf65d642008-01-30 13:30:43 +01001491 Map the 32-bit VDSO to the predictable old-style address too.
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001492 ---help---
1493 Say N here if you are running a sufficiently recent glibc
1494 version (2.3.3 or later), to remove the high-mapped
1495 VDSO mapping and to exclusively use the randomized VDSO.
1496
1497 If unsure, say Y.
1498
Tim Bird516cbf32008-08-12 12:52:36 -07001499config CMDLINE_BOOL
1500 bool "Built-in kernel command line"
1501 default n
1502 help
1503 Allow for specifying boot arguments to the kernel at
1504 build time. On some systems (e.g. embedded ones), it is
1505 necessary or convenient to provide some or all of the
1506 kernel boot arguments with the kernel itself (that is,
1507 to not rely on the boot loader to provide them.)
1508
1509 To compile command line arguments into the kernel,
1510 set this option to 'Y', then fill in the
1511 the boot arguments in CONFIG_CMDLINE.
1512
1513 Systems with fully functional boot loaders (i.e. non-embedded)
1514 should leave this option set to 'N'.
1515
1516config CMDLINE
1517 string "Built-in kernel command string"
1518 depends on CMDLINE_BOOL
1519 default ""
1520 help
1521 Enter arguments here that should be compiled into the kernel
1522 image and used at boot time. If the boot loader provides a
1523 command line at boot time, it is appended to this string to
1524 form the full kernel command line, when the system boots.
1525
1526 However, you can use the CONFIG_CMDLINE_OVERRIDE option to
1527 change this behavior.
1528
1529 In most cases, the command line (whether built-in or provided
1530 by the boot loader) should specify the device for the root
1531 file system.
1532
1533config CMDLINE_OVERRIDE
1534 bool "Built-in command line overrides boot loader arguments"
1535 default n
1536 depends on CMDLINE_BOOL
1537 help
1538 Set this option to 'Y' to have the kernel ignore the boot loader
1539 command line, and use ONLY the built-in command line.
1540
1541 This is used to work around broken boot loaders. This should
1542 be set to 'N' under normal conditions.
1543
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001544endmenu
1545
1546config ARCH_ENABLE_MEMORY_HOTPLUG
1547 def_bool y
1548 depends on X86_64 || (X86_32 && HIGHMEM)
1549
Gary Hade35551052008-10-31 10:52:03 -07001550config ARCH_ENABLE_MEMORY_HOTREMOVE
1551 def_bool y
1552 depends on MEMORY_HOTPLUG
1553
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001554config HAVE_ARCH_EARLY_PFN_TO_NID
1555 def_bool X86_64
1556 depends on NUMA
1557
Bjorn Helgaasda85f862008-11-05 13:37:27 -06001558menu "Power management and ACPI options"
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001559
1560config ARCH_HIBERNATION_HEADER
Harvey Harrison3c2362e2008-01-30 13:31:03 +01001561 def_bool y
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001562 depends on X86_64 && HIBERNATION
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001563
1564source "kernel/power/Kconfig"
1565
1566source "drivers/acpi/Kconfig"
1567
Andi Kleena6b68072008-01-30 13:32:49 +01001568config X86_APM_BOOT
1569 bool
1570 default y
1571 depends on APM || APM_MODULE
1572
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001573menuconfig APM
1574 tristate "APM (Advanced Power Management) BIOS support"
Ingo Molnarefefa6f2008-07-10 16:09:50 +02001575 depends on X86_32 && PM_SLEEP
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001576 ---help---
1577 APM is a BIOS specification for saving power using several different
1578 techniques. This is mostly useful for battery powered laptops with
1579 APM compliant BIOSes. If you say Y here, the system time will be
1580 reset after a RESUME operation, the /proc/apm device will provide
1581 battery status information, and user-space programs will receive
1582 notification of APM "events" (e.g. battery status change).
1583
1584 If you select "Y" here, you can disable actual use of the APM
1585 BIOS by passing the "apm=off" option to the kernel at boot time.
1586
1587 Note that the APM support is almost completely disabled for
1588 machines with more than one CPU.
1589
1590 In order to use APM, you will need supporting software. For location
Randy Dunlap53471122008-03-12 18:10:51 -04001591 and more information, read <file:Documentation/power/pm.txt> and the
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001592 Battery Powered Linux mini-HOWTO, available from
1593 <http://www.tldp.org/docs.html#howto>.
1594
1595 This driver does not spin down disk drives (see the hdparm(8)
1596 manpage ("man 8 hdparm") for that), and it doesn't turn off
1597 VESA-compliant "green" monitors.
1598
1599 This driver does not support the TI 4000M TravelMate and the ACER
1600 486/DX4/75 because they don't have compliant BIOSes. Many "green"
1601 desktop machines also don't have compliant BIOSes, and this driver
1602 may cause those machines to panic during the boot phase.
1603
1604 Generally, if you don't have a battery in your machine, there isn't
1605 much point in using this driver and you should say N. If you get
1606 random kernel OOPSes or reboots that don't seem to be related to
1607 anything, try disabling/enabling this option (or disabling/enabling
1608 APM in your BIOS).
1609
1610 Some other things you should try when experiencing seemingly random,
1611 "weird" problems:
1612
1613 1) make sure that you have enough swap space and that it is
1614 enabled.
1615 2) pass the "no-hlt" option to the kernel
1616 3) switch on floating point emulation in the kernel and pass
1617 the "no387" option to the kernel
1618 4) pass the "floppy=nodma" option to the kernel
1619 5) pass the "mem=4M" option to the kernel (thereby disabling
1620 all but the first 4 MB of RAM)
1621 6) make sure that the CPU is not over clocked.
1622 7) read the sig11 FAQ at <http://www.bitwizard.nl/sig11/>
1623 8) disable the cache from your BIOS settings
1624 9) install a fan for the video card or exchange video RAM
1625 10) install a better fan for the CPU
1626 11) exchange RAM chips
1627 12) exchange the motherboard.
1628
1629 To compile this driver as a module, choose M here: the
1630 module will be called apm.
1631
1632if APM
1633
1634config APM_IGNORE_USER_SUSPEND
1635 bool "Ignore USER SUSPEND"
1636 help
1637 This option will ignore USER SUSPEND requests. On machines with a
1638 compliant APM BIOS, you want to say N. However, on the NEC Versa M
1639 series notebooks, it is necessary to say Y because of a BIOS bug.
1640
1641config APM_DO_ENABLE
1642 bool "Enable PM at boot time"
1643 ---help---
1644 Enable APM features at boot time. From page 36 of the APM BIOS
1645 specification: "When disabled, the APM BIOS does not automatically
1646 power manage devices, enter the Standby State, enter the Suspend
1647 State, or take power saving steps in response to CPU Idle calls."
1648 This driver will make CPU Idle calls when Linux is idle (unless this
1649 feature is turned off -- see "Do CPU IDLE calls", below). This
1650 should always save battery power, but more complicated APM features
1651 will be dependent on your BIOS implementation. You may need to turn
1652 this option off if your computer hangs at boot time when using APM
1653 support, or if it beeps continuously instead of suspending. Turn
1654 this off if you have a NEC UltraLite Versa 33/C or a Toshiba
1655 T400CDT. This is off by default since most machines do fine without
1656 this feature.
1657
1658config APM_CPU_IDLE
1659 bool "Make CPU Idle calls when idle"
1660 help
1661 Enable calls to APM CPU Idle/CPU Busy inside the kernel's idle loop.
1662 On some machines, this can activate improved power savings, such as
1663 a slowed CPU clock rate, when the machine is idle. These idle calls
1664 are made after the idle loop has run for some length of time (e.g.,
1665 333 mS). On some machines, this will cause a hang at boot time or
1666 whenever the CPU becomes idle. (On machines with more than one CPU,
1667 this option does nothing.)
1668
1669config APM_DISPLAY_BLANK
1670 bool "Enable console blanking using APM"
1671 help
1672 Enable console blanking using the APM. Some laptops can use this to
1673 turn off the LCD backlight when the screen blanker of the Linux
1674 virtual console blanks the screen. Note that this is only used by
1675 the virtual console screen blanker, and won't turn off the backlight
1676 when using the X Window system. This also doesn't have anything to
1677 do with your VESA-compliant power-saving monitor. Further, this
1678 option doesn't work for all laptops -- it might not turn off your
1679 backlight at all, or it might print a lot of errors to the console,
1680 especially if you are using gpm.
1681
1682config APM_ALLOW_INTS
1683 bool "Allow interrupts during APM BIOS calls"
1684 help
1685 Normally we disable external interrupts while we are making calls to
1686 the APM BIOS as a measure to lessen the effects of a badly behaving
1687 BIOS implementation. The BIOS should reenable interrupts if it
1688 needs to. Unfortunately, some BIOSes do not -- especially those in
1689 many of the newer IBM Thinkpads. If you experience hangs when you
1690 suspend, try setting this to Y. Otherwise, say N.
1691
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001692endif # APM
1693
1694source "arch/x86/kernel/cpu/cpufreq/Kconfig"
1695
1696source "drivers/cpuidle/Kconfig"
1697
Andy Henroid27471fd2008-10-09 11:45:22 -07001698source "drivers/idle/Kconfig"
1699
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001700endmenu
1701
1702
1703menu "Bus options (PCI etc.)"
1704
1705config PCI
Ingo Molnar1ac97012008-05-19 14:10:14 +02001706 bool "PCI support"
Adrian Bunk1c858082008-01-30 13:32:32 +01001707 default y
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001708 select ARCH_SUPPORTS_MSI if (X86_LOCAL_APIC && X86_IO_APIC)
1709 help
1710 Find out whether you have a PCI motherboard. PCI is the name of a
1711 bus system, i.e. the way the CPU talks to the other stuff inside
1712 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
1713 VESA. If you have PCI, say Y, otherwise N.
1714
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001715choice
1716 prompt "PCI access mode"
Ingo Molnarefefa6f2008-07-10 16:09:50 +02001717 depends on X86_32 && PCI
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001718 default PCI_GOANY
1719 ---help---
1720 On PCI systems, the BIOS can be used to detect the PCI devices and
1721 determine their configuration. However, some old PCI motherboards
1722 have BIOS bugs and may crash if this is done. Also, some embedded
1723 PCI-based systems don't have any BIOS at all. Linux can also try to
1724 detect the PCI hardware directly without using the BIOS.
1725
1726 With this option, you can specify how Linux should detect the
1727 PCI devices. If you choose "BIOS", the BIOS will be used,
1728 if you choose "Direct", the BIOS won't be used, and if you
1729 choose "MMConfig", then PCI Express MMCONFIG will be used.
1730 If you choose "Any", the kernel will try MMCONFIG, then the
1731 direct access method and falls back to the BIOS if that doesn't
1732 work. If unsure, go with the default, which is "Any".
1733
1734config PCI_GOBIOS
1735 bool "BIOS"
1736
1737config PCI_GOMMCONFIG
1738 bool "MMConfig"
1739
1740config PCI_GODIRECT
1741 bool "Direct"
1742
Andres Salomon3ef0e1f2008-04-29 00:59:53 -07001743config PCI_GOOLPC
1744 bool "OLPC"
1745 depends on OLPC
1746
Andres Salomon2bdd1b02008-06-05 14:14:41 -07001747config PCI_GOANY
1748 bool "Any"
1749
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001750endchoice
1751
1752config PCI_BIOS
Harvey Harrison3c2362e2008-01-30 13:31:03 +01001753 def_bool y
Ingo Molnarefefa6f2008-07-10 16:09:50 +02001754 depends on X86_32 && PCI && (PCI_GOBIOS || PCI_GOANY)
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001755
1756# x86-64 doesn't support PCI BIOS access from long mode so always go direct.
1757config PCI_DIRECT
Harvey Harrison3c2362e2008-01-30 13:31:03 +01001758 def_bool y
Ingo Molnarefefa6f2008-07-10 16:09:50 +02001759 depends on PCI && (X86_64 || (PCI_GODIRECT || PCI_GOANY || PCI_GOOLPC))
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001760
1761config PCI_MMCONFIG
Harvey Harrison3c2362e2008-01-30 13:31:03 +01001762 def_bool y
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001763 depends on X86_32 && PCI && ACPI && (PCI_GOMMCONFIG || PCI_GOANY)
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001764
Andres Salomon3ef0e1f2008-04-29 00:59:53 -07001765config PCI_OLPC
Andres Salomon2bdd1b02008-06-05 14:14:41 -07001766 def_bool y
1767 depends on PCI && OLPC && (PCI_GOOLPC || PCI_GOANY)
Andres Salomon3ef0e1f2008-04-29 00:59:53 -07001768
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001769config PCI_DOMAINS
Harvey Harrison3c2362e2008-01-30 13:31:03 +01001770 def_bool y
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001771 depends on PCI
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001772
1773config PCI_MMCONFIG
1774 bool "Support mmconfig PCI config space access"
1775 depends on X86_64 && PCI && ACPI
1776
1777config DMAR
1778 bool "Support for DMA Remapping Devices (EXPERIMENTAL)"
1779 depends on X86_64 && PCI_MSI && ACPI && EXPERIMENTAL
1780 help
1781 DMA remapping (DMAR) devices support enables independent address
1782 translations for Direct Memory Access (DMA) from devices.
1783 These DMA remapping devices are reported via ACPI tables
1784 and include PCI device scope covered by these DMA
1785 remapping devices.
1786
1787config DMAR_GFX_WA
Harvey Harrison3c2362e2008-01-30 13:31:03 +01001788 def_bool y
1789 prompt "Support for Graphics workaround"
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001790 depends on DMAR
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001791 help
1792 Current Graphics drivers tend to use physical address
1793 for DMA and avoid using DMA APIs. Setting this config
1794 option permits the IOMMU driver to set a unity map for
1795 all the OS-visible memory. Hence the driver can continue
1796 to use physical addresses for DMA.
1797
1798config DMAR_FLOPPY_WA
Harvey Harrison3c2362e2008-01-30 13:31:03 +01001799 def_bool y
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001800 depends on DMAR
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001801 help
1802 Floppy disk drivers are know to bypass DMA API calls
1803 thereby failing to work when IOMMU is enabled. This
1804 workaround will setup a 1:1 mapping for the first
1805 16M to make floppy (an ISA device) work.
1806
Suresh Siddha9fa8c482008-07-10 11:17:00 -07001807config INTR_REMAP
1808 bool "Support for Interrupt Remapping (EXPERIMENTAL)"
1809 depends on X86_64 && X86_IO_APIC && PCI_MSI && ACPI && EXPERIMENTAL
1810 help
1811 Supports Interrupt remapping for IO-APIC and MSI devices.
1812 To use x2apic mode in the CPU's which support x2APIC enhancements or
1813 to support platforms with CPU's having > 8 bit APIC ID, say Y.
1814
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001815source "drivers/pci/pcie/Kconfig"
1816
1817source "drivers/pci/Kconfig"
1818
1819# x86_64 have no ISA slots, but do have ISA-style DMA.
1820config ISA_DMA_API
Harvey Harrison3c2362e2008-01-30 13:31:03 +01001821 def_bool y
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001822
1823if X86_32
1824
1825config ISA
1826 bool "ISA support"
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001827 help
1828 Find out whether you have ISA slots on your motherboard. ISA is the
1829 name of a bus system, i.e. the way the CPU talks to the other stuff
1830 inside your box. Other bus systems are PCI, EISA, MicroChannel
1831 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
1832 newer boards don't support it. If you have ISA, say Y, otherwise N.
1833
1834config EISA
1835 bool "EISA support"
1836 depends on ISA
1837 ---help---
1838 The Extended Industry Standard Architecture (EISA) bus was
1839 developed as an open alternative to the IBM MicroChannel bus.
1840
1841 The EISA bus provided some of the features of the IBM MicroChannel
1842 bus while maintaining backward compatibility with cards made for
1843 the older ISA bus. The EISA bus saw limited use between 1988 and
1844 1995 when it was made obsolete by the PCI bus.
1845
1846 Say Y here if you are building a kernel for an EISA-based machine.
1847
1848 Otherwise, say N.
1849
1850source "drivers/eisa/Kconfig"
1851
1852config MCA
Ingo Molnar72ee6eb2009-01-27 16:57:49 +01001853 bool "MCA support"
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001854 help
1855 MicroChannel Architecture is found in some IBM PS/2 machines and
1856 laptops. It is a bus system similar to PCI or ISA. See
1857 <file:Documentation/mca.txt> (and especially the web page given
1858 there) before attempting to build an MCA bus kernel.
1859
1860source "drivers/mca/Kconfig"
1861
1862config SCx200
1863 tristate "NatSemi SCx200 support"
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001864 help
1865 This provides basic support for National Semiconductor's
1866 (now AMD's) Geode processors. The driver probes for the
1867 PCI-IDs of several on-chip devices, so its a good dependency
1868 for other scx200_* drivers.
1869
1870 If compiled as a module, the driver is named scx200.
1871
1872config SCx200HR_TIMER
1873 tristate "NatSemi SCx200 27MHz High-Resolution Timer Support"
1874 depends on SCx200 && GENERIC_TIME
1875 default y
1876 help
1877 This driver provides a clocksource built upon the on-chip
1878 27MHz high-resolution timer. Its also a workaround for
1879 NSC Geode SC-1100's buggy TSC, which loses time when the
1880 processor goes idle (as is done by the scheduler). The
1881 other workaround is idle=poll boot option.
1882
1883config GEODE_MFGPT_TIMER
Harvey Harrison3c2362e2008-01-30 13:31:03 +01001884 def_bool y
1885 prompt "Geode Multi-Function General Purpose Timer (MFGPT) events"
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001886 depends on MGEODE_LX && GENERIC_TIME && GENERIC_CLOCKEVENTS
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001887 help
1888 This driver provides a clock event source based on the MFGPT
1889 timer(s) in the CS5535 and CS5536 companion chip for the geode.
1890 MFGPTs have a better resolution and max interval than the
1891 generic PIT, and are suitable for use as high-res timers.
1892
Andres Salomon3ef0e1f2008-04-29 00:59:53 -07001893config OLPC
1894 bool "One Laptop Per Child support"
1895 default n
1896 help
1897 Add support for detecting the unique features of the OLPC
1898 XO hardware.
1899
Sam Ravnborgbc0120f2007-11-06 23:10:39 +01001900endif # X86_32
1901
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001902config K8_NB
1903 def_bool y
Sam Ravnborgbc0120f2007-11-06 23:10:39 +01001904 depends on AGP_AMD64 || (X86_64 && (GART_IOMMU || (PCI && NUMA)))
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001905
1906source "drivers/pcmcia/Kconfig"
1907
1908source "drivers/pci/hotplug/Kconfig"
1909
1910endmenu
1911
1912
1913menu "Executable file formats / Emulations"
1914
1915source "fs/Kconfig.binfmt"
1916
1917config IA32_EMULATION
1918 bool "IA32 Emulation"
1919 depends on X86_64
Roland McGratha97f52e2008-01-30 13:31:55 +01001920 select COMPAT_BINFMT_ELF
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001921 help
1922 Include code to run 32-bit programs under a 64-bit kernel. You should
1923 likely turn this on, unless you're 100% sure that you don't have any
1924 32-bit programs left.
1925
1926config IA32_AOUT
1927 tristate "IA32 a.out support"
David Woodhouse6b213e12008-06-16 12:39:13 +01001928 depends on IA32_EMULATION
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001929 help
1930 Support old a.out binaries in the 32bit emulation.
1931
1932config COMPAT
Harvey Harrison3c2362e2008-01-30 13:31:03 +01001933 def_bool y
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001934 depends on IA32_EMULATION
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001935
1936config COMPAT_FOR_U64_ALIGNMENT
1937 def_bool COMPAT
1938 depends on X86_64
1939
1940config SYSVIPC_COMPAT
Harvey Harrison3c2362e2008-01-30 13:31:03 +01001941 def_bool y
Alexey Dobriyanb8992192008-09-14 13:44:41 +04001942 depends on COMPAT && SYSVIPC
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001943
1944endmenu
1945
1946
Keith Packarde5beae12008-11-03 18:21:45 +01001947config HAVE_ATOMIC_IOMAP
1948 def_bool y
1949 depends on X86_32
1950
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001951source "net/Kconfig"
1952
1953source "drivers/Kconfig"
1954
1955source "drivers/firmware/Kconfig"
1956
1957source "fs/Kconfig"
1958
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001959source "arch/x86/Kconfig.debug"
1960
1961source "security/Kconfig"
1962
1963source "crypto/Kconfig"
1964
Avi Kivityedf88412007-12-16 11:02:48 +02001965source "arch/x86/kvm/Kconfig"
1966
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001967source "lib/Kconfig"