blob: c1c5ccd1937f56b7be18c604fe3718e622241b66 [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"
Ingo Molnar8f9ca472009-02-05 16:21:53 +01008 ---help---
Sam Ravnborgdaa93fa2007-11-12 20:54:30 +01009 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
Steven Rostedt9a5fd902009-02-06 01:14:26 -050037 select HAVE_FTRACE_NMI_ENTER if DYNAMIC_FTRACE
Frederic Weisbecker1b3fa2c2009-03-07 05:53:00 +010038 select HAVE_FTRACE_SYSCALLS
Ingo Molnare0ec9482009-01-27 17:01:14 +010039 select HAVE_KVM
Ingo Molnar49793b02009-01-27 17:02:29 +010040 select HAVE_ARCH_KGDB
Roland McGrath99bbc4b2008-04-20 14:35:12 -070041 select HAVE_ARCH_TRACEHOOK
Dmitry Baryshkov323ec002008-06-29 14:19:31 +040042 select HAVE_GENERIC_DMA_COHERENT if X86_32
Johannes Berg58340a02008-07-25 01:45:33 -070043 select HAVE_EFFICIENT_UNALIGNED_ACCESS
Török Edwin8d264872008-11-23 12:39:08 +020044 select USER_STACKTRACE_SUPPORT
Joerg Roedel2118d0c2009-01-09 15:13:15 +010045 select HAVE_DMA_API_DEBUG
H. Peter Anvin2e9f3bd2009-01-04 15:41:25 -080046 select HAVE_KERNEL_GZIP
47 select HAVE_KERNEL_BZIP2
48 select HAVE_KERNEL_LZMA
Balbir Singh7d8330a2008-02-10 12:46:28 +053049
Sam Ravnborg73531902008-05-25 23:03:18 +020050config ARCH_DEFCONFIG
Sam Ravnborgb9b39bf2008-04-29 12:48:15 +020051 string
Sam Ravnborg73531902008-05-25 23:03:18 +020052 default "arch/x86/configs/i386_defconfig" if X86_32
53 default "arch/x86/configs/x86_64_defconfig" if X86_64
Sam Ravnborgb9b39bf2008-04-29 12:48:15 +020054
Sam Ravnborg8d5fffb2007-11-06 23:30:30 +010055config GENERIC_TIME
Harvey Harrison3c2362e2008-01-30 13:31:03 +010056 def_bool y
Sam Ravnborg8d5fffb2007-11-06 23:30:30 +010057
58config GENERIC_CMOS_UPDATE
Harvey Harrison3c2362e2008-01-30 13:31:03 +010059 def_bool y
Sam Ravnborg8d5fffb2007-11-06 23:30:30 +010060
61config CLOCKSOURCE_WATCHDOG
Harvey Harrison3c2362e2008-01-30 13:31:03 +010062 def_bool y
Sam Ravnborg8d5fffb2007-11-06 23:30:30 +010063
64config GENERIC_CLOCKEVENTS
Harvey Harrison3c2362e2008-01-30 13:31:03 +010065 def_bool y
Sam Ravnborg8d5fffb2007-11-06 23:30:30 +010066
67config GENERIC_CLOCKEVENTS_BROADCAST
Harvey Harrison3c2362e2008-01-30 13:31:03 +010068 def_bool y
Sam Ravnborg8d5fffb2007-11-06 23:30:30 +010069 depends on X86_64 || (X86_32 && X86_LOCAL_APIC)
70
71config LOCKDEP_SUPPORT
Harvey Harrison3c2362e2008-01-30 13:31:03 +010072 def_bool y
Sam Ravnborg8d5fffb2007-11-06 23:30:30 +010073
74config STACKTRACE_SUPPORT
Harvey Harrison3c2362e2008-01-30 13:31:03 +010075 def_bool y
Sam Ravnborg8d5fffb2007-11-06 23:30:30 +010076
Heiko Carstensaa7d9352008-02-01 17:45:14 +010077config HAVE_LATENCYTOP_SUPPORT
78 def_bool y
79
Christoph Lameter1f842602008-01-07 23:20:30 -080080config FAST_CMPXCHG_LOCAL
81 bool
82 default y
83
Sam Ravnborg8d5fffb2007-11-06 23:30:30 +010084config MMU
Harvey Harrison3c2362e2008-01-30 13:31:03 +010085 def_bool y
Sam Ravnborg8d5fffb2007-11-06 23:30:30 +010086
87config ZONE_DMA
Harvey Harrison3c2362e2008-01-30 13:31:03 +010088 def_bool y
Sam Ravnborg8d5fffb2007-11-06 23:30:30 +010089
Sam Ravnborg8d5fffb2007-11-06 23:30:30 +010090config SBUS
91 bool
92
93config GENERIC_ISA_DMA
Harvey Harrison3c2362e2008-01-30 13:31:03 +010094 def_bool y
Sam Ravnborg8d5fffb2007-11-06 23:30:30 +010095
96config GENERIC_IOMAP
Harvey Harrison3c2362e2008-01-30 13:31:03 +010097 def_bool y
Sam Ravnborg8d5fffb2007-11-06 23:30:30 +010098
99config GENERIC_BUG
Harvey Harrison3c2362e2008-01-30 13:31:03 +0100100 def_bool y
Sam Ravnborg8d5fffb2007-11-06 23:30:30 +0100101 depends on BUG
Jan Beulichb93a5312008-12-16 11:40:27 +0000102 select GENERIC_BUG_RELATIVE_POINTERS if X86_64
103
104config GENERIC_BUG_RELATIVE_POINTERS
105 bool
Sam Ravnborg8d5fffb2007-11-06 23:30:30 +0100106
107config GENERIC_HWEIGHT
Harvey Harrison3c2362e2008-01-30 13:31:03 +0100108 def_bool y
Sam Ravnborg8d5fffb2007-11-06 23:30:30 +0100109
Florian Fainellia6082952008-01-30 13:33:35 +0100110config GENERIC_GPIO
Jan Beulich9ba16082008-10-15 22:01:38 -0700111 bool
Florian Fainellia6082952008-01-30 13:33:35 +0100112
Sam Ravnborg8d5fffb2007-11-06 23:30:30 +0100113config ARCH_MAY_HAVE_PC_FDC
Harvey Harrison3c2362e2008-01-30 13:31:03 +0100114 def_bool y
Sam Ravnborg8d5fffb2007-11-06 23:30:30 +0100115
Sam Ravnborg1032c0b2007-11-06 21:35:08 +0100116config RWSEM_GENERIC_SPINLOCK
117 def_bool !X86_XADD
118
119config RWSEM_XCHGADD_ALGORITHM
120 def_bool X86_XADD
121
Venki Pallipadia6869cc2008-02-08 17:05:44 -0800122config ARCH_HAS_CPU_IDLE_WAIT
123 def_bool y
124
Sam Ravnborg1032c0b2007-11-06 21:35:08 +0100125config GENERIC_CALIBRATE_DELAY
126 def_bool y
127
Sam Ravnborg8d5fffb2007-11-06 23:30:30 +0100128config GENERIC_TIME_VSYSCALL
129 bool
130 default X86_64
131
venkatesh.pallipadi@intel.com9a0b8412008-01-31 17:35:06 -0800132config ARCH_HAS_CPU_RELAX
133 def_bool y
Sam Ravnborg8d5fffb2007-11-06 23:30:30 +0100134
Venkatesh Pallipadi89cedfe2008-10-16 19:00:08 -0400135config ARCH_HAS_DEFAULT_IDLE
136 def_bool y
137
Pekka Enberg1b27d052008-04-28 02:12:22 -0700138config ARCH_HAS_CACHE_LINE_SIZE
139 def_bool y
140
Mike Travisdd5af902008-01-30 13:33:32 +0100141config HAVE_SETUP_PER_CPU_AREA
Brian Gerst89c9c4c2009-01-27 12:56:48 +0900142 def_bool y
travis@sgi.comb32ef632008-01-30 13:32:51 +0100143
Tejun Heo11124412009-02-20 16:29:09 +0900144config HAVE_DYNAMIC_PER_CPU_AREA
145 def_bool y
146
Mike Travis9f0e8d02008-04-04 18:11:01 -0700147config HAVE_CPUMASK_OF_CPU_MAP
148 def_bool X86_64_SMP
149
Johannes Berg801e4062007-12-08 02:12:39 +0100150config ARCH_HIBERNATION_POSSIBLE
151 def_bool y
Johannes Berg801e4062007-12-08 02:12:39 +0100152
Johannes Bergf4cb5702007-12-08 02:14:00 +0100153config ARCH_SUSPEND_POSSIBLE
154 def_bool y
Johannes Bergf4cb5702007-12-08 02:14:00 +0100155
Sam Ravnborg8d5fffb2007-11-06 23:30:30 +0100156config ZONE_DMA32
157 bool
158 default X86_64
159
160config ARCH_POPULATES_NODE_MAP
161 def_bool y
162
163config AUDIT_ARCH
164 bool
165 default X86_64
166
Ingo Molnar765c68b2008-04-09 11:03:37 +0200167config ARCH_SUPPORTS_OPTIMIZED_INLINING
168 def_bool y
169
Akinobu Mita6a11f752009-03-31 15:23:17 -0700170config ARCH_SUPPORTS_DEBUG_PAGEALLOC
171 def_bool y
172
Sam Ravnborg8d5fffb2007-11-06 23:30:30 +0100173# Use the generic interrupt handling code in kernel/irq/:
174config GENERIC_HARDIRQS
175 bool
176 default y
177
Thomas Gleixnerf9a36fa2009-03-13 16:37:48 +0100178config GENERIC_HARDIRQS_NO__DO_IRQ
179 def_bool y
180
Sam Ravnborg8d5fffb2007-11-06 23:30:30 +0100181config GENERIC_IRQ_PROBE
182 bool
183 default y
184
185config GENERIC_PENDING_IRQ
186 bool
187 depends on GENERIC_HARDIRQS && SMP
188 default y
189
James Bottomley6cd10f82008-11-09 11:53:14 -0600190config USE_GENERIC_SMP_HELPERS
191 def_bool y
192 depends on SMP
193
Sam Ravnborg6b0c3d42008-01-30 13:32:27 +0100194config X86_32_SMP
195 def_bool y
196 depends on X86_32 && SMP
197
198config X86_64_SMP
199 def_bool y
200 depends on X86_64 && SMP
201
Sam Ravnborg8d5fffb2007-11-06 23:30:30 +0100202config X86_HT
203 bool
Adrian Bunkee0011a2007-12-04 17:19:07 +0100204 depends on SMP
Sam Ravnborg8d5fffb2007-11-06 23:30:30 +0100205 default y
206
Sam Ravnborg8d5fffb2007-11-06 23:30:30 +0100207config X86_TRAMPOLINE
208 bool
Ingo Molnar3e5095d2009-01-27 17:07:08 +0100209 depends on SMP || (64BIT && ACPI_SLEEP)
Sam Ravnborg8d5fffb2007-11-06 23:30:30 +0100210 default y
211
Tejun Heoccbeed32009-02-09 22:17:40 +0900212config X86_32_LAZY_GS
213 def_bool y
Tejun Heo60a53172009-02-09 22:17:40 +0900214 depends on X86_32 && !CC_STACKPROTECTOR
Tejun Heoccbeed32009-02-09 22:17:40 +0900215
Sam Ravnborg8d5fffb2007-11-06 23:30:30 +0100216config KTIME_SCALAR
217 def_bool X86_32
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100218source "init/Kconfig"
Matt Helsleydc52ddc2008-10-18 20:27:21 -0700219source "kernel/Kconfig.freezer"
Sam Ravnborg8d5fffb2007-11-06 23:30:30 +0100220
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100221menu "Processor type and features"
222
223source "kernel/time/Kconfig"
224
225config SMP
226 bool "Symmetric multi-processing support"
227 ---help---
228 This enables support for systems with more than one CPU. If you have
229 a system with only one CPU, like most personal computers, say N. If
230 you have a system with more than one CPU, say Y.
231
232 If you say N here, the kernel will run on single and multiprocessor
233 machines, but will use only one CPU of a multiprocessor machine. If
234 you say Y here, the kernel will run on many, but not all,
235 singleprocessor machines. On a singleprocessor machine, the kernel
236 will run faster if you say N here.
237
238 Note that if you say Y here and choose architecture "586" or
239 "Pentium" under "Processor family", the kernel will not work on 486
240 architectures. Similarly, multiprocessor kernels for the "PPro"
241 architecture may not work on all Pentium based boards.
242
243 People using multiprocessor machines who say Y here should also say
244 Y to "Enhanced Real Time Clock Support", below. The "Advanced Power
245 Management" code will be disabled if you say Y here.
246
Adrian Bunk03502fa2008-02-03 15:50:21 +0200247 See also <file:Documentation/i386/IO-APIC.txt>,
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100248 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
249 <http://www.tldp.org/docs.html#howto>.
250
251 If you don't know what to do here, say N.
252
Yinghai Lu06cd9a72009-02-16 17:29:58 -0800253config X86_X2APIC
254 bool "Support x2apic"
David Woodhousef7d7f862009-04-06 23:04:40 -0700255 depends on X86_LOCAL_APIC && X86_64 && INTR_REMAP
Yinghai Lu06cd9a72009-02-16 17:29:58 -0800256 ---help---
257 This enables x2apic support on CPUs that have this feature.
258
259 This allows 32-bit apic IDs (so it can support very large systems),
260 and accesses the local apic via MSRs not via mmio.
261
Yinghai Lu06cd9a72009-02-16 17:29:58 -0800262 If you don't know what to do here, say N.
263
Yinghai Lu0b8f1ef2008-12-05 18:58:31 -0800264config SPARSE_IRQ
265 bool "Support sparse irq numbering"
Yinghai Lu17483a12008-12-12 13:14:18 -0800266 depends on PCI_MSI || HT_IRQ
Ingo Molnar8f9ca472009-02-05 16:21:53 +0100267 ---help---
Ingo Molnar973656f2008-12-25 16:26:47 +0100268 This enables support for sparse irqs. This is useful for distro
269 kernels that want to define a high CONFIG_NR_CPUS value but still
270 want to have low kernel memory footprint on smaller machines.
Yinghai Lu0b8f1ef2008-12-05 18:58:31 -0800271
Ingo Molnar973656f2008-12-25 16:26:47 +0100272 ( Sparse IRQs can also be beneficial on NUMA boxes, as they spread
273 out the irq_desc[] array in a more NUMA-friendly way. )
274
275 If you don't know what to do here, say N.
Yinghai Lu0b8f1ef2008-12-05 18:58:31 -0800276
Yinghai Lu48a1b102008-12-11 00:15:01 -0800277config NUMA_MIGRATE_IRQ_DESC
278 bool "Move irq desc when changing irq smp_affinity"
Yinghai Lub9098952008-12-19 13:48:34 -0800279 depends on SPARSE_IRQ && NUMA
Yinghai Luca713c22009-04-15 18:39:13 -0700280 depends on BROKEN
Yinghai Lu48a1b102008-12-11 00:15:01 -0800281 default n
Ingo Molnar8f9ca472009-02-05 16:21:53 +0100282 ---help---
Yinghai Lu48a1b102008-12-11 00:15:01 -0800283 This enables moving irq_desc to cpu/node that irq will use handled.
284
285 If you don't know what to do here, say N.
286
Yinghai Lu6695c852008-06-19 12:13:09 -0700287config X86_MPPARSE
Jan Beulich7a527682008-10-30 10:38:24 +0000288 bool "Enable MPS table" if ACPI
289 default y
Ingo Molnar5ab74722008-07-10 14:42:03 +0200290 depends on X86_LOCAL_APIC
Ingo Molnar8f9ca472009-02-05 16:21:53 +0100291 ---help---
Yinghai Lu6695c852008-06-19 12:13:09 -0700292 For old smp systems that do not have proper acpi support. Newer systems
293 (esp with 64bit cpus) with acpi support, MADT and DSDT will override it
Yinghai Lu6695c852008-06-19 12:13:09 -0700294
Yinghai Lu26f7ef12009-01-29 14:19:22 -0800295config X86_BIGSMP
296 bool "Support for big SMP systems with more than 8 CPUs"
297 depends on X86_32 && SMP
Ingo Molnar8f9ca472009-02-05 16:21:53 +0100298 ---help---
Yinghai Lu26f7ef12009-01-29 14:19:22 -0800299 This option is needed for the systems that have more than 8 CPUs
300
Ravikiran G Thirumalai84250912009-02-20 16:59:11 -0800301if X86_32
Ravikiran G Thirumalaic5c606d2009-02-09 18:18:14 -0800302config X86_EXTENDED_PLATFORM
303 bool "Support for extended (non-PC) x86 platforms"
304 default y
Ingo Molnar8f9ca472009-02-05 16:21:53 +0100305 ---help---
Ingo Molnar06ac8342009-01-27 18:11:43 +0100306 If you disable this option then the kernel will only support
307 standard PC platforms. (which covers the vast majority of
308 systems out there.)
309
Ravikiran G Thirumalai84250912009-02-20 16:59:11 -0800310 If you enable this option then you'll be able to select support
311 for the following (non-PC) 32 bit x86 platforms:
312 AMD Elan
313 NUMAQ (IBM/Sequent)
314 RDC R-321x SoC
315 SGI 320/540 (Visual Workstation)
316 Summit/EXA (IBM x440)
317 Unisys ES7000 IA32 series
Ingo Molnar06ac8342009-01-27 18:11:43 +0100318
319 If you have one of these systems, or if you want to build a
320 generic distribution kernel, say Y here - otherwise say N.
Ravikiran G Thirumalai84250912009-02-20 16:59:11 -0800321endif
Ingo Molnar06ac8342009-01-27 18:11:43 +0100322
Ravikiran G Thirumalai84250912009-02-20 16:59:11 -0800323if X86_64
324config X86_EXTENDED_PLATFORM
325 bool "Support for extended (non-PC) x86 platforms"
326 default y
327 ---help---
328 If you disable this option then the kernel will only support
329 standard PC platforms. (which covers the vast majority of
330 systems out there.)
331
332 If you enable this option then you'll be able to select support
333 for the following (non-PC) 64 bit x86 platforms:
334 ScaleMP vSMP
335 SGI Ultraviolet
336
337 If you have one of these systems, or if you want to build a
338 generic distribution kernel, say Y here - otherwise say N.
339endif
Ravikiran G Thirumalaic5c606d2009-02-09 18:18:14 -0800340# This is an alphabetically sorted list of 64 bit extended platforms
341# Please maintain the alphabetic order if and when there are additions
Nick Piggin03b48632009-01-20 04:36:04 +0100342
Ingo Molnar6a485652009-01-27 18:29:13 +0100343config X86_VSMP
Ravikiran G Thirumalaic5c606d2009-02-09 18:18:14 -0800344 bool "ScaleMP vSMP"
Ingo Molnar6a485652009-01-27 18:29:13 +0100345 select PARAVIRT
346 depends on X86_64 && PCI
Ravikiran G Thirumalaic5c606d2009-02-09 18:18:14 -0800347 depends on X86_EXTENDED_PLATFORM
Ingo Molnar8f9ca472009-02-05 16:21:53 +0100348 ---help---
Ingo Molnar6a485652009-01-27 18:29:13 +0100349 Support for ScaleMP vSMP systems. Say 'Y' here if this kernel is
350 supposed to run on these EM64T-based machines. Only choose this option
351 if you have one of these machines.
352
Ravikiran G Thirumalaic5c606d2009-02-09 18:18:14 -0800353config X86_UV
354 bool "SGI Ultraviolet"
355 depends on X86_64
356 depends on X86_EXTENDED_PLATFORM
Jack Steiner54c28d22009-04-03 15:39:42 -0500357 depends on NUMA
Ingo Molnar7d01d322009-02-17 12:33:20 +0100358 select X86_X2APIC
Ravikiran G Thirumalaic5c606d2009-02-09 18:18:14 -0800359 ---help---
360 This option is needed in order to support SGI Ultraviolet systems.
361 If you don't have one of these, you should say N here.
362
363# Following is an alphabetically sorted list of 32 bit extended platforms
364# Please maintain the alphabetic order if and when there are additions
365
Ingo Molnar9e111f32009-01-27 18:18:25 +0100366config X86_ELAN
367 bool "AMD Elan"
368 depends on X86_32
Ravikiran G Thirumalaic5c606d2009-02-09 18:18:14 -0800369 depends on X86_EXTENDED_PLATFORM
Ingo Molnar8f9ca472009-02-05 16:21:53 +0100370 ---help---
Ingo Molnar9e111f32009-01-27 18:18:25 +0100371 Select this for an AMD Elan processor.
372
373 Do not use this option for K6/Athlon/Opteron processors!
374
375 If unsure, choose "PC-compatible" instead.
376
Ravikiran G Thirumalaic5c606d2009-02-09 18:18:14 -0800377config X86_RDC321X
378 bool "RDC R-321x SoC"
379 depends on X86_32
380 depends on X86_EXTENDED_PLATFORM
381 select M486
382 select X86_REBOOTFIXUPS
383 ---help---
384 This option is needed for RDC R-321x system-on-chip, also known
385 as R-8610-(G).
386 If you don't have one of these chips, you should say N here.
387
Ingo Molnare0c7ae32009-01-27 18:43:09 +0100388config X86_32_NON_STANDARD
Ingo Molnar9c398012009-01-27 18:24:57 +0100389 bool "Support non-standard 32-bit SMP architectures"
390 depends on X86_32 && SMP
Ravikiran G Thirumalaic5c606d2009-02-09 18:18:14 -0800391 depends on X86_EXTENDED_PLATFORM
Ingo Molnar8f9ca472009-02-05 16:21:53 +0100392 ---help---
393 This option compiles in the NUMAQ, Summit, bigsmp, ES7000, default
Ingo Molnar9c398012009-01-27 18:24:57 +0100394 subarchitectures. It is intended for a generic binary kernel.
395 if you select them all, kernel will probe it one by one. and will
396 fallback to default.
397
Ravikiran G Thirumalaic5c606d2009-02-09 18:18:14 -0800398# Alphabetically sorted list of Non standard 32 bit platforms
399
Ingo Molnar9c398012009-01-27 18:24:57 +0100400config X86_NUMAQ
401 bool "NUMAQ (IBM/Sequent)"
Ingo Molnare0c7ae32009-01-27 18:43:09 +0100402 depends on X86_32_NON_STANDARD
Ingo Molnar9c398012009-01-27 18:24:57 +0100403 select NUMA
404 select X86_MPPARSE
Ingo Molnar8f9ca472009-02-05 16:21:53 +0100405 ---help---
Ingo Molnar9c398012009-01-27 18:24:57 +0100406 This option is used for getting Linux to run on a NUMAQ (IBM/Sequent)
407 NUMA multiquad box. This changes the way that processors are
408 bootstrapped, and uses Clustered Logical APIC addressing mode instead
409 of Flat Logical. You will need a new lynxer.elf file to flash your
410 firmware with - send email to <Martin.Bligh@us.ibm.com>.
411
Ravikiran G Thirumalaic5c606d2009-02-09 18:18:14 -0800412config X86_VISWS
413 bool "SGI 320/540 (Visual Workstation)"
414 depends on X86_32 && PCI && X86_MPPARSE && PCI_GODIRECT
415 depends on X86_32_NON_STANDARD
416 ---help---
417 The SGI Visual Workstation series is an IA32-based workstation
418 based on SGI systems chips with some legacy PC hardware attached.
419
420 Say Y here to create a kernel to run on the SGI 320 or 540.
421
422 A kernel compiled for the Visual Workstation will run on general
423 PCs as well. See <file:Documentation/sgi-visws.txt> for details.
424
Ingo Molnar9c398012009-01-27 18:24:57 +0100425config X86_SUMMIT
426 bool "Summit/EXA (IBM x440)"
Ingo Molnare0c7ae32009-01-27 18:43:09 +0100427 depends on X86_32_NON_STANDARD
Ingo Molnar8f9ca472009-02-05 16:21:53 +0100428 ---help---
Ingo Molnar9c398012009-01-27 18:24:57 +0100429 This option is needed for IBM systems that use the Summit/EXA chipset.
430 In particular, it is needed for the x440.
431
432config X86_ES7000
Ravikiran G Thirumalaic5c606d2009-02-09 18:18:14 -0800433 bool "Unisys ES7000 IA32 series"
Yinghai Lu26f7ef12009-01-29 14:19:22 -0800434 depends on X86_32_NON_STANDARD && X86_BIGSMP
Ingo Molnar8f9ca472009-02-05 16:21:53 +0100435 ---help---
Ingo Molnar9c398012009-01-27 18:24:57 +0100436 Support for Unisys ES7000 systems. Say 'Y' here if this kernel is
437 supposed to run on an IA32-based Unisys ES7000 system.
438
Ingo Molnarae1e9132008-11-11 09:05:16 +0100439config SCHED_OMIT_FRAME_POINTER
Harvey Harrison3c2362e2008-01-30 13:31:03 +0100440 def_bool y
441 prompt "Single-depth WCHAN output"
Ken Chena87d0912008-11-06 11:10:49 -0800442 depends on X86
Ingo Molnar8f9ca472009-02-05 16:21:53 +0100443 ---help---
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100444 Calculate simpler /proc/<PID>/wchan values. If this option
445 is disabled then wchan values will recurse back to the
446 caller function. This provides more accurate wchan values,
447 at the expense of slightly more scheduling overhead.
448
449 If in doubt, say "Y".
450
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100451menuconfig PARAVIRT_GUEST
452 bool "Paravirtualized guest support"
Ingo Molnar8f9ca472009-02-05 16:21:53 +0100453 ---help---
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100454 Say Y here to get to see options related to running Linux under
455 various hypervisors. This option alone does not add any kernel code.
456
457 If you say N, all options in this submenu will be skipped and disabled.
458
459if PARAVIRT_GUEST
460
461source "arch/x86/xen/Kconfig"
462
463config VMI
464 bool "VMI Guest support"
465 select PARAVIRT
Eduardo Pereira Habkost42d545c2008-01-30 13:33:32 +0100466 depends on X86_32
Ingo Molnar8f9ca472009-02-05 16:21:53 +0100467 ---help---
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100468 VMI provides a paravirtualized interface to the VMware ESX server
469 (it could be used by other hypervisors in theory too, but is not
470 at the moment), by linking the kernel to a GPL-ed ROM module
471 provided by the hypervisor.
472
Glauber de Oliveira Costa790c73f2008-02-15 17:52:48 -0200473config KVM_CLOCK
474 bool "KVM paravirtualized clock"
475 select PARAVIRT
Gerd Hoffmannf6e16d52008-06-03 16:17:32 +0200476 select PARAVIRT_CLOCK
Ingo Molnar8f9ca472009-02-05 16:21:53 +0100477 ---help---
Glauber de Oliveira Costa790c73f2008-02-15 17:52:48 -0200478 Turning on this option will allow you to run a paravirtualized clock
479 when running over the KVM hypervisor. Instead of relying on a PIT
480 (or probably other) emulation by the underlying device model, the host
481 provides the guest with timing infrastructure such as time of day, and
482 system time
483
Marcelo Tosatti0cf1bfd2008-02-22 12:21:36 -0500484config KVM_GUEST
485 bool "KVM Guest support"
486 select PARAVIRT
Ingo Molnar8f9ca472009-02-05 16:21:53 +0100487 ---help---
488 This option enables various optimizations for running under the KVM
489 hypervisor.
Marcelo Tosatti0cf1bfd2008-02-22 12:21:36 -0500490
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100491source "arch/x86/lguest/Kconfig"
492
Eduardo Pereira Habkoste61bd942008-01-30 13:33:32 +0100493config PARAVIRT
494 bool "Enable paravirtualization code"
Ingo Molnar8f9ca472009-02-05 16:21:53 +0100495 ---help---
Eduardo Pereira Habkoste61bd942008-01-30 13:33:32 +0100496 This changes the kernel so it can modify itself when it is run
497 under a hypervisor, potentially improving performance significantly
498 over full virtualization. However, when run without a hypervisor
499 the kernel is theoretically slower and slightly larger.
500
Jeremy Fitzhardingeb4ecc122009-05-13 17:16:55 -0700501config PARAVIRT_SPINLOCKS
502 bool "Paravirtualization layer for spinlocks"
503 depends on PARAVIRT && SMP && EXPERIMENTAL
504 ---help---
505 Paravirtualized spinlocks allow a pvops backend to replace the
506 spinlock implementation with something virtualization-friendly
507 (for example, block the virtual CPU rather than spinning).
508
509 Unfortunately the downside is an up to 5% performance hit on
510 native kernels, with various workloads.
511
512 If you are unsure how to answer this question, answer N.
513
Gerd Hoffmann7af192c2008-06-03 16:17:29 +0200514config PARAVIRT_CLOCK
515 bool
516 default n
517
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100518endif
519
Jeremy Fitzhardinge97349132008-06-25 00:19:14 -0400520config PARAVIRT_DEBUG
Ingo Molnar8f9ca472009-02-05 16:21:53 +0100521 bool "paravirt-ops debugging"
522 depends on PARAVIRT && DEBUG_KERNEL
523 ---help---
524 Enable to debug paravirt_ops internals. Specifically, BUG if
525 a paravirt_op is missing when it is called.
Jeremy Fitzhardinge97349132008-06-25 00:19:14 -0400526
Yinghai Lu03273182008-04-18 17:49:15 -0700527config MEMTEST
528 bool "Memtest"
Ingo Molnar8f9ca472009-02-05 16:21:53 +0100529 ---help---
Yinghai Luc64df702008-03-21 18:56:19 -0700530 This option adds a kernel parameter 'memtest', which allows memtest
Yinghai Lu03273182008-04-18 17:49:15 -0700531 to be set.
Ingo Molnar8f9ca472009-02-05 16:21:53 +0100532 memtest=0, mean disabled; -- default
533 memtest=1, mean do 1 test pattern;
534 ...
535 memtest=4, mean do 4 test patterns.
Thomas Gleixneraba37282008-07-15 14:48:48 +0200536 If you are unsure how to answer this question, answer N.
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100537
538config X86_SUMMIT_NUMA
Harvey Harrison3c2362e2008-01-30 13:31:03 +0100539 def_bool y
Ingo Molnare0c7ae32009-01-27 18:43:09 +0100540 depends on X86_32 && NUMA && X86_32_NON_STANDARD
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100541
542config X86_CYCLONE_TIMER
Harvey Harrison3c2362e2008-01-30 13:31:03 +0100543 def_bool y
Ingo Molnare0c7ae32009-01-27 18:43:09 +0100544 depends on X86_32_NON_STANDARD
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100545
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100546source "arch/x86/Kconfig.cpu"
547
548config HPET_TIMER
Harvey Harrison3c2362e2008-01-30 13:31:03 +0100549 def_bool X86_64
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100550 prompt "HPET Timer Support" if X86_32
Ingo Molnar8f9ca472009-02-05 16:21:53 +0100551 ---help---
552 Use the IA-PC HPET (High Precision Event Timer) to manage
553 time in preference to the PIT and RTC, if a HPET is
554 present.
555 HPET is the next generation timer replacing legacy 8254s.
556 The HPET provides a stable time base on SMP
557 systems, unlike the TSC, but it is more expensive to access,
558 as it is off-chip. You can find the HPET spec at
559 <http://www.intel.com/hardwaredesign/hpetspec_1.pdf>.
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100560
Ingo Molnar8f9ca472009-02-05 16:21:53 +0100561 You can safely choose Y here. However, HPET will only be
562 activated if the platform and the BIOS support this feature.
563 Otherwise the 8254 will be used for timing services.
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100564
Ingo Molnar8f9ca472009-02-05 16:21:53 +0100565 Choose N to continue using the legacy 8254 timer.
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100566
567config HPET_EMULATE_RTC
Harvey Harrison3c2362e2008-01-30 13:31:03 +0100568 def_bool y
Bernhard Walle9d8af782008-02-06 01:38:52 -0800569 depends on HPET_TIMER && (RTC=y || RTC=m || RTC_DRV_CMOS=m || RTC_DRV_CMOS=y)
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100570
571# Mark as embedded because too many people got it wrong.
572# The code disables itself when not needed.
Thomas Petazzoni7ae93922008-04-28 02:14:14 -0700573config DMI
574 default y
575 bool "Enable DMI scanning" if EMBEDDED
Ingo Molnar8f9ca472009-02-05 16:21:53 +0100576 ---help---
Thomas Petazzoni7ae93922008-04-28 02:14:14 -0700577 Enabled scanning of DMI to identify machine quirks. Say Y
578 here unless you have verified that your setup is not
579 affected by entries in the DMI blacklist. Required by PNP
580 BIOS code.
581
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100582config GART_IOMMU
583 bool "GART IOMMU support" if EMBEDDED
584 default y
585 select SWIOTLB
586 select AGP
587 depends on X86_64 && PCI
Ingo Molnar8f9ca472009-02-05 16:21:53 +0100588 ---help---
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100589 Support for full DMA access of devices with 32bit memory access only
590 on systems with more than 3GB. This is usually needed for USB,
591 sound, many IDE/SATA chipsets and some other devices.
592 Provides a driver for the AMD Athlon64/Opteron/Turion/Sempron GART
593 based hardware IOMMU and a software bounce buffer based IOMMU used
594 on Intel systems and as fallback.
595 The code is only active when needed (enough memory and limited
596 device) unless CONFIG_IOMMU_DEBUG or iommu=force is specified
597 too.
598
599config CALGARY_IOMMU
600 bool "IBM Calgary IOMMU support"
601 select SWIOTLB
602 depends on X86_64 && PCI && EXPERIMENTAL
Ingo Molnar8f9ca472009-02-05 16:21:53 +0100603 ---help---
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100604 Support for hardware IOMMUs in IBM's xSeries x366 and x460
605 systems. Needed to run systems with more than 3GB of memory
606 properly with 32-bit PCI devices that do not support DAC
607 (Double Address Cycle). Calgary also supports bus level
608 isolation, where all DMAs pass through the IOMMU. This
609 prevents them from going anywhere except their intended
610 destination. This catches hard-to-find kernel bugs and
611 mis-behaving drivers and devices that do not use the DMA-API
612 properly to set up their DMA buffers. The IOMMU can be
613 turned off at boot time with the iommu=off parameter.
614 Normally the kernel will make the right choice by itself.
615 If unsure, say Y.
616
617config CALGARY_IOMMU_ENABLED_BY_DEFAULT
Harvey Harrison3c2362e2008-01-30 13:31:03 +0100618 def_bool y
619 prompt "Should Calgary be enabled by default?"
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100620 depends on CALGARY_IOMMU
Ingo Molnar8f9ca472009-02-05 16:21:53 +0100621 ---help---
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100622 Should Calgary be enabled by default? if you choose 'y', Calgary
623 will be used (if it exists). If you choose 'n', Calgary will not be
624 used even if it exists. If you choose 'n' and would like to use
625 Calgary anyway, pass 'iommu=calgary' on the kernel command line.
626 If unsure, say Y.
627
Joerg Roedel2b188722008-06-26 21:27:37 +0200628config AMD_IOMMU
629 bool "AMD IOMMU support"
Ingo Molnar07c40e82008-06-27 11:31:28 +0200630 select SWIOTLB
Joerg Roedela80dc3e2008-09-11 16:51:41 +0200631 select PCI_MSI
Ingo Molnar24d2ba02008-06-27 10:37:03 +0200632 depends on X86_64 && PCI && ACPI
Ingo Molnar8f9ca472009-02-05 16:21:53 +0100633 ---help---
Joerg Roedel18d22202008-07-03 19:35:06 +0200634 With this option you can enable support for AMD IOMMU hardware in
635 your system. An IOMMU is a hardware component which provides
636 remapping of DMA memory accesses from devices. With an AMD IOMMU you
637 can isolate the the DMA memory of different devices and protect the
638 system from misbehaving device drivers or hardware.
639
640 You can find out if your system has an AMD IOMMU if you look into
641 your BIOS for an option to enable it or if you have an IVRS ACPI
642 table.
Joerg Roedel2b188722008-06-26 21:27:37 +0200643
Joerg Roedel2e117602008-12-11 19:00:12 +0100644config AMD_IOMMU_STATS
645 bool "Export AMD IOMMU statistics to debugfs"
646 depends on AMD_IOMMU
647 select DEBUG_FS
Ingo Molnar8f9ca472009-02-05 16:21:53 +0100648 ---help---
Joerg Roedel2e117602008-12-11 19:00:12 +0100649 This option enables code in the AMD IOMMU driver to collect various
650 statistics about whats happening in the driver and exports that
651 information to userspace via debugfs.
652 If unsure, say N.
653
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100654# need this always selected by IOMMU for the VIA workaround
655config SWIOTLB
Joerg Roedela1afd012008-11-18 12:44:21 +0100656 def_bool y if X86_64
Ingo Molnar8f9ca472009-02-05 16:21:53 +0100657 ---help---
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100658 Support for software bounce buffers used on x86-64 systems
659 which don't have a hardware IOMMU (e.g. the current generation
660 of Intel's x86-64 CPUs). Using this PCI devices which can only
661 access 32-bits of memory can be used on systems with more than
662 3 GB of memory. If unsure, say Y.
663
FUJITA Tomonoria8522502008-04-29 00:59:36 -0700664config IOMMU_HELPER
FUJITA Tomonori18b743d2008-07-10 09:50:50 +0900665 def_bool (CALGARY_IOMMU || GART_IOMMU || SWIOTLB || AMD_IOMMU)
Linus Torvaldsd25e26b2008-08-25 14:15:38 -0700666
Joerg Roedel1aaf1182008-11-26 17:25:13 +0100667config IOMMU_API
668 def_bool (AMD_IOMMU || DMAR)
669
Mike Travis1184dc22008-05-12 21:21:12 +0200670config MAXSMP
671 bool "Configure Maximum number of SMP Processors and NUMA Nodes"
Mike Travis36f51012008-12-16 17:33:51 -0800672 depends on X86_64 && SMP && DEBUG_KERNEL && EXPERIMENTAL
673 select CPUMASK_OFFSTACK
Mike Travis1184dc22008-05-12 21:21:12 +0200674 default n
Ingo Molnar8f9ca472009-02-05 16:21:53 +0100675 ---help---
Mike Travis1184dc22008-05-12 21:21:12 +0200676 Configure maximum number of CPUS and NUMA Nodes for this architecture.
677 If unsure, say N.
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100678
679config NR_CPUS
Mike Travis36f51012008-12-16 17:33:51 -0800680 int "Maximum number of CPUs" if SMP && !MAXSMP
Michael K. Johnson2a3313f2009-04-21 21:44:48 -0400681 range 2 8 if SMP && X86_32 && !X86_BIGSMP
Mike Travis36f51012008-12-16 17:33:51 -0800682 range 2 512 if SMP && !MAXSMP
Mike Travis78637a92008-12-16 17:34:00 -0800683 default "1" if !SMP
Linus Torvaldsd25e26b2008-08-25 14:15:38 -0700684 default "4096" if MAXSMP
Mike Travis78637a92008-12-16 17:34:00 -0800685 default "32" if SMP && (X86_NUMAQ || X86_SUMMIT || X86_BIGSMP || X86_ES7000)
686 default "8" if SMP
Ingo Molnar8f9ca472009-02-05 16:21:53 +0100687 ---help---
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100688 This allows you to specify the maximum number of CPUs which this
Linus Torvaldsd25e26b2008-08-25 14:15:38 -0700689 kernel will support. The maximum supported value is 512 and the
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100690 minimum value which makes sense is 2.
691
692 This is purely to save memory - each supported CPU adds
693 approximately eight kilobytes to the kernel image.
694
695config SCHED_SMT
696 bool "SMT (Hyperthreading) scheduler support"
Hiroshi Shimamotob089c122008-02-27 13:16:30 -0800697 depends on X86_HT
Ingo Molnar8f9ca472009-02-05 16:21:53 +0100698 ---help---
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100699 SMT scheduler support improves the CPU scheduler's decision making
700 when dealing with Intel Pentium 4 chips with HyperThreading at a
701 cost of slightly increased overhead in some places. If unsure say
702 N here.
703
704config SCHED_MC
Harvey Harrison3c2362e2008-01-30 13:31:03 +0100705 def_bool y
706 prompt "Multi-core scheduler support"
Hiroshi Shimamotob089c122008-02-27 13:16:30 -0800707 depends on X86_HT
Ingo Molnar8f9ca472009-02-05 16:21:53 +0100708 ---help---
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100709 Multi-core scheduler support improves the CPU scheduler's decision
710 making when dealing with multi-core CPU chips at a cost of slightly
711 increased overhead in some places. If unsure say N here.
712
713source "kernel/Kconfig.preempt"
714
715config X86_UP_APIC
716 bool "Local APIC support on uniprocessors"
Ingo Molnare0c7ae32009-01-27 18:43:09 +0100717 depends on X86_32 && !SMP && !X86_32_NON_STANDARD
Ingo Molnar8f9ca472009-02-05 16:21:53 +0100718 ---help---
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100719 A local APIC (Advanced Programmable Interrupt Controller) is an
720 integrated interrupt controller in the CPU. If you have a single-CPU
721 system which has a processor with a local APIC, you can say Y here to
722 enable and use it. If you say Y here even though your machine doesn't
723 have a local APIC, then the kernel will still run with no slowdown at
724 all. The local APIC supports CPU-generated self-interrupts (timer,
725 performance counters), and the NMI watchdog which detects hard
726 lockups.
727
728config X86_UP_IOAPIC
729 bool "IO-APIC support on uniprocessors"
730 depends on X86_UP_APIC
Ingo Molnar8f9ca472009-02-05 16:21:53 +0100731 ---help---
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100732 An IO-APIC (I/O Advanced Programmable Interrupt Controller) is an
733 SMP-capable replacement for PC-style interrupt controllers. Most
734 SMP systems and many recent uniprocessor systems have one.
735
736 If you have a single-CPU system with an IO-APIC, you can say Y here
737 to use it. If you say Y here even though your machine doesn't have
738 an IO-APIC, then the kernel will still run with no slowdown at all.
739
740config X86_LOCAL_APIC
Harvey Harrison3c2362e2008-01-30 13:31:03 +0100741 def_bool y
Ingo Molnare0c7ae32009-01-27 18:43:09 +0100742 depends on X86_64 || SMP || X86_32_NON_STANDARD || X86_UP_APIC
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100743
744config X86_IO_APIC
Harvey Harrison3c2362e2008-01-30 13:31:03 +0100745 def_bool y
Ingo Molnare0c7ae32009-01-27 18:43:09 +0100746 depends on X86_64 || SMP || X86_32_NON_STANDARD || X86_UP_APIC
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100747
748config X86_VISWS_APIC
Harvey Harrison3c2362e2008-01-30 13:31:03 +0100749 def_bool y
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100750 depends on X86_32 && X86_VISWS
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100751
Stefan Assmann41b9eb22008-07-15 13:48:55 +0200752config X86_REROUTE_FOR_BROKEN_BOOT_IRQS
753 bool "Reroute for broken boot IRQs"
754 default n
755 depends on X86_IO_APIC
Ingo Molnar8f9ca472009-02-05 16:21:53 +0100756 ---help---
Stefan Assmann41b9eb22008-07-15 13:48:55 +0200757 This option enables a workaround that fixes a source of
758 spurious interrupts. This is recommended when threaded
759 interrupt handling is used on systems where the generation of
760 superfluous "boot interrupts" cannot be disabled.
761
762 Some chipsets generate a legacy INTx "boot IRQ" when the IRQ
763 entry in the chipset's IO-APIC is masked (as, e.g. the RT
764 kernel does during interrupt handling). On chipsets where this
765 boot IRQ generation cannot be disabled, this workaround keeps
766 the original IRQ line masked so that only the equivalent "boot
767 IRQ" is delivered to the CPUs. The workaround also tells the
768 kernel to set up the IRQ handler on the boot IRQ line. In this
769 way only one interrupt is delivered to the kernel. Otherwise
770 the spurious second interrupt may cause the kernel to bring
771 down (vital) interrupt lines.
772
773 Only affects "broken" chipsets. Interrupt sharing may be
774 increased on these systems.
775
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100776config X86_MCE
777 bool "Machine Check Exception"
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100778 ---help---
779 Machine Check Exception support allows the processor to notify the
780 kernel if it detects a problem (e.g. overheating, component failure).
781 The action the kernel takes depends on the severity of the problem,
782 ranging from a warning message on the console, to halting the machine.
783 Your processor must be a Pentium or newer to support this - check the
784 flags in /proc/cpuinfo for mce. Note that some older Pentium systems
785 have a design flaw which leads to false MCE events - hence MCE is
786 disabled on all P5 processors, unless explicitly enabled with "mce"
787 as a boot argument. Similarly, if MCE is built in and creates a
788 problem on some new non-standard machine, you can boot with "nomce"
789 to disable it. MCE support simply ignores non-MCE processors like
790 the 386 and 486, so nearly everyone can say Y here.
791
Andi Kleen4efc0672009-04-28 19:07:31 +0200792config X86_OLD_MCE
793 depends on X86_32 && X86_MCE
794 bool "Use legacy machine check code (will go away)"
795 default n
796 select X86_ANCIENT_MCE
797 ---help---
798 Use the old i386 machine check code. This is merely intended for
799 testing in a transition period. Try this if you run into any machine
800 check related software problems, but report the problem to
801 linux-kernel. When in doubt say no.
802
803config X86_NEW_MCE
804 depends on X86_MCE
805 bool
806 default y if (!X86_OLD_MCE && X86_32) || X86_64
807
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100808config X86_MCE_INTEL
Harvey Harrison3c2362e2008-01-30 13:31:03 +0100809 def_bool y
810 prompt "Intel MCE features"
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100811 depends on X86_64 && X86_MCE && X86_LOCAL_APIC
Ingo Molnar8f9ca472009-02-05 16:21:53 +0100812 ---help---
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100813 Additional support for intel specific MCE features such as
814 the thermal monitor.
815
816config X86_MCE_AMD
Harvey Harrison3c2362e2008-01-30 13:31:03 +0100817 def_bool y
818 prompt "AMD MCE features"
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100819 depends on X86_64 && X86_MCE && X86_LOCAL_APIC
Ingo Molnar8f9ca472009-02-05 16:21:53 +0100820 ---help---
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100821 Additional support for AMD specific MCE features such as
822 the DRAM Error Threshold.
823
Andi Kleen4efc0672009-04-28 19:07:31 +0200824config X86_ANCIENT_MCE
825 def_bool n
826 depends on X86_32
827 prompt "Support for old Pentium 5 / WinChip machine checks"
828 ---help---
829 Include support for machine check handling on old Pentium 5 or WinChip
830 systems. These typically need to be enabled explicitely on the command
831 line.
832
Andi Kleenb2762682009-02-12 13:49:31 +0100833config X86_MCE_THRESHOLD
834 depends on X86_MCE_AMD || X86_MCE_INTEL
835 bool
836 default y
837
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100838config X86_MCE_NONFATAL
839 tristate "Check for non-fatal errors on AMD Athlon/Duron / Intel Pentium 4"
Andi Kleen4efc0672009-04-28 19:07:31 +0200840 depends on X86_OLD_MCE
Ingo Molnar8f9ca472009-02-05 16:21:53 +0100841 ---help---
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100842 Enabling this feature starts a timer that triggers every 5 seconds which
843 will look at the machine check registers to see if anything happened.
844 Non-fatal problems automatically get corrected (but still logged).
845 Disable this if you don't want to see these messages.
846 Seeing the messages this option prints out may be indicative of dying
847 or out-of-spec (ie, overclocked) hardware.
848 This option only does something on certain CPUs.
849 (AMD Athlon/Duron and Intel Pentium 4)
850
851config X86_MCE_P4THERMAL
852 bool "check for P4 thermal throttling interrupt."
Andi Kleen4efc0672009-04-28 19:07:31 +0200853 depends on X86_OLD_MCE && X86_MCE && (X86_UP_APIC || SMP)
Ingo Molnar8f9ca472009-02-05 16:21:53 +0100854 ---help---
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100855 Enabling this feature will cause a message to be printed when the P4
856 enters thermal throttling.
857
Andi Kleen4efc0672009-04-28 19:07:31 +0200858config X86_THERMAL_VECTOR
859 def_bool y
860 depends on X86_MCE_P4THERMAL || X86_MCE_INTEL
861
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100862config VM86
863 bool "Enable VM86 support" if EMBEDDED
864 default y
865 depends on X86_32
Ingo Molnar8f9ca472009-02-05 16:21:53 +0100866 ---help---
867 This option is required by programs like DOSEMU to run 16-bit legacy
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100868 code on X86 processors. It also may be needed by software like
Ingo Molnar8f9ca472009-02-05 16:21:53 +0100869 XFree86 to initialize some video cards via BIOS. Disabling this
870 option saves about 6k.
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100871
872config TOSHIBA
873 tristate "Toshiba Laptop support"
874 depends on X86_32
875 ---help---
876 This adds a driver to safely access the System Management Mode of
877 the CPU on Toshiba portables with a genuine Toshiba BIOS. It does
878 not work on models with a Phoenix BIOS. The System Management Mode
879 is used to set the BIOS and power saving options on Toshiba portables.
880
881 For information on utilities to make use of this driver see the
882 Toshiba Linux utilities web site at:
883 <http://www.buzzard.org.uk/toshiba/>.
884
885 Say Y if you intend to run this kernel on a Toshiba portable.
886 Say N otherwise.
887
888config I8K
889 tristate "Dell laptop support"
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100890 ---help---
891 This adds a driver to safely access the System Management Mode
892 of the CPU on the Dell Inspiron 8000. The System Management Mode
893 is used to read cpu temperature and cooling fan status and to
894 control the fans on the I8K portables.
895
896 This driver has been tested only on the Inspiron 8000 but it may
897 also work with other Dell laptops. You can force loading on other
898 models by passing the parameter `force=1' to the module. Use at
899 your own risk.
900
901 For information on utilities to make use of this driver see the
902 I8K Linux utilities web site at:
903 <http://people.debian.org/~dz/i8k/>
904
905 Say Y if you intend to run this kernel on a Dell Inspiron 8000.
906 Say N otherwise.
907
908config X86_REBOOTFIXUPS
Jan Beulich9ba16082008-10-15 22:01:38 -0700909 bool "Enable X86 board specific fixups for reboot"
910 depends on X86_32
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100911 ---help---
912 This enables chipset and/or board specific fixups to be done
913 in order to get reboot to work correctly. This is only needed on
914 some combinations of hardware and BIOS. The symptom, for which
915 this config is intended, is when reboot ends with a stalled/hung
916 system.
917
918 Currently, the only fixup is for the Geode machines using
Florian Fainelli5e3a77e2008-01-30 13:33:36 +0100919 CS5530A and CS5536 chipsets and the RDC R-321x SoC.
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100920
921 Say Y if you want to enable the fixup. Currently, it's safe to
922 enable this option even if you don't need it.
923 Say N otherwise.
924
925config MICROCODE
Peter Oruba8d86f392008-07-28 18:44:21 +0200926 tristate "/dev/cpu/microcode - microcode support"
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100927 select FW_LOADER
928 ---help---
929 If you say Y here, you will be able to update the microcode on
Peter Oruba80cc9f12008-07-28 18:44:22 +0200930 certain Intel and AMD processors. The Intel support is for the
931 IA32 family, e.g. Pentium Pro, Pentium II, Pentium III,
932 Pentium 4, Xeon etc. The AMD support is for family 0x10 and
933 0x11 processors, e.g. Opteron, Phenom and Turion 64 Ultra.
934 You will obviously need the actual microcode binary data itself
935 which is not shipped with the Linux kernel.
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100936
Peter Oruba8d86f392008-07-28 18:44:21 +0200937 This option selects the general module only, you need to select
938 at least one vendor specific module as well.
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100939
940 To compile this driver as a module, choose M here: the
941 module will be called microcode.
942
Peter Oruba8d86f392008-07-28 18:44:21 +0200943config MICROCODE_INTEL
Ingo Molnar8f9ca472009-02-05 16:21:53 +0100944 bool "Intel microcode patch loading support"
945 depends on MICROCODE
946 default MICROCODE
947 select FW_LOADER
948 ---help---
949 This options enables microcode patch loading support for Intel
950 processors.
Peter Oruba8d86f392008-07-28 18:44:21 +0200951
Ingo Molnar8f9ca472009-02-05 16:21:53 +0100952 For latest news and information on obtaining all the required
953 Intel ingredients for this driver, check:
954 <http://www.urbanmyth.org/microcode/>.
Peter Oruba8d86f392008-07-28 18:44:21 +0200955
Peter Oruba80cc9f12008-07-28 18:44:22 +0200956config MICROCODE_AMD
Ingo Molnar8f9ca472009-02-05 16:21:53 +0100957 bool "AMD microcode patch loading support"
958 depends on MICROCODE
959 select FW_LOADER
960 ---help---
961 If you select this option, microcode patch loading support for AMD
962 processors will be enabled.
Peter Oruba80cc9f12008-07-28 18:44:22 +0200963
Ingo Molnar8f9ca472009-02-05 16:21:53 +0100964config MICROCODE_OLD_INTERFACE
Harvey Harrison3c2362e2008-01-30 13:31:03 +0100965 def_bool y
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100966 depends on MICROCODE
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100967
968config X86_MSR
969 tristate "/dev/cpu/*/msr - Model-specific register support"
Ingo Molnar8f9ca472009-02-05 16:21:53 +0100970 ---help---
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100971 This device gives privileged processes access to the x86
972 Model-Specific Registers (MSRs). It is a character device with
973 major 202 and minors 0 to 31 for /dev/cpu/0/msr to /dev/cpu/31/msr.
974 MSR accesses are directed to a specific CPU on multi-processor
975 systems.
976
977config X86_CPUID
978 tristate "/dev/cpu/*/cpuid - CPU information support"
Ingo Molnar8f9ca472009-02-05 16:21:53 +0100979 ---help---
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100980 This device gives processes access to the x86 CPUID instruction to
981 be executed on a specific processor. It is a character device
982 with major 203 and minors 0 to 31 for /dev/cpu/0/cpuid to
983 /dev/cpu/31/cpuid.
984
Jaswinder Singh Rajput9b779ed2009-03-10 15:37:51 +0530985config X86_CPU_DEBUG
986 tristate "/sys/kernel/debug/x86/cpu/* - CPU Debug support"
987 ---help---
988 If you select this option, this will provide various x86 CPUs
989 information through debugfs.
990
Sam Ravnborg506f1d02007-11-09 21:56:54 +0100991choice
992 prompt "High Memory Support"
993 default HIGHMEM4G if !X86_NUMAQ
994 default HIGHMEM64G if X86_NUMAQ
995 depends on X86_32
996
997config NOHIGHMEM
998 bool "off"
999 depends on !X86_NUMAQ
1000 ---help---
1001 Linux can use up to 64 Gigabytes of physical memory on x86 systems.
1002 However, the address space of 32-bit x86 processors is only 4
1003 Gigabytes large. That means that, if you have a large amount of
1004 physical memory, not all of it can be "permanently mapped" by the
1005 kernel. The physical memory that's not permanently mapped is called
1006 "high memory".
1007
1008 If you are compiling a kernel which will never run on a machine with
1009 more than 1 Gigabyte total physical RAM, answer "off" here (default
1010 choice and suitable for most users). This will result in a "3GB/1GB"
1011 split: 3GB are mapped so that each process sees a 3GB virtual memory
1012 space and the remaining part of the 4GB virtual memory space is used
1013 by the kernel to permanently map as much physical memory as
1014 possible.
1015
1016 If the machine has between 1 and 4 Gigabytes physical RAM, then
1017 answer "4GB" here.
1018
1019 If more than 4 Gigabytes is used then answer "64GB" here. This
1020 selection turns Intel PAE (Physical Address Extension) mode on.
1021 PAE implements 3-level paging on IA32 processors. PAE is fully
1022 supported by Linux, PAE mode is implemented on all recent Intel
1023 processors (Pentium Pro and better). NOTE: If you say "64GB" here,
1024 then the kernel will not boot on CPUs that don't support PAE!
1025
1026 The actual amount of total physical memory will either be
1027 auto detected or can be forced by using a kernel command line option
1028 such as "mem=256M". (Try "man bootparam" or see the documentation of
1029 your boot loader (lilo or loadlin) about how to pass options to the
1030 kernel at boot time.)
1031
1032 If unsure, say "off".
1033
1034config HIGHMEM4G
1035 bool "4GB"
1036 depends on !X86_NUMAQ
Ingo Molnar8f9ca472009-02-05 16:21:53 +01001037 ---help---
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001038 Select this if you have a 32-bit processor and between 1 and 4
1039 gigabytes of physical RAM.
1040
1041config HIGHMEM64G
1042 bool "64GB"
1043 depends on !M386 && !M486
1044 select X86_PAE
Ingo Molnar8f9ca472009-02-05 16:21:53 +01001045 ---help---
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001046 Select this if you have a 32-bit processor and more than 4
1047 gigabytes of physical RAM.
1048
1049endchoice
1050
1051choice
1052 depends on EXPERIMENTAL
1053 prompt "Memory split" if EMBEDDED
1054 default VMSPLIT_3G
1055 depends on X86_32
Ingo Molnar8f9ca472009-02-05 16:21:53 +01001056 ---help---
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001057 Select the desired split between kernel and user memory.
1058
1059 If the address range available to the kernel is less than the
1060 physical memory installed, the remaining memory will be available
1061 as "high memory". Accessing high memory is a little more costly
1062 than low memory, as it needs to be mapped into the kernel first.
1063 Note that increasing the kernel address space limits the range
1064 available to user programs, making the address space there
1065 tighter. Selecting anything other than the default 3G/1G split
1066 will also likely make your kernel incompatible with binary-only
1067 kernel modules.
1068
1069 If you are not absolutely sure what you are doing, leave this
1070 option alone!
1071
1072 config VMSPLIT_3G
1073 bool "3G/1G user/kernel split"
1074 config VMSPLIT_3G_OPT
1075 depends on !X86_PAE
1076 bool "3G/1G user/kernel split (for full 1G low memory)"
1077 config VMSPLIT_2G
1078 bool "2G/2G user/kernel split"
1079 config VMSPLIT_2G_OPT
1080 depends on !X86_PAE
1081 bool "2G/2G user/kernel split (for full 2G low memory)"
1082 config VMSPLIT_1G
1083 bool "1G/3G user/kernel split"
1084endchoice
1085
1086config PAGE_OFFSET
1087 hex
1088 default 0xB0000000 if VMSPLIT_3G_OPT
1089 default 0x80000000 if VMSPLIT_2G
1090 default 0x78000000 if VMSPLIT_2G_OPT
1091 default 0x40000000 if VMSPLIT_1G
1092 default 0xC0000000
1093 depends on X86_32
1094
1095config HIGHMEM
Harvey Harrison3c2362e2008-01-30 13:31:03 +01001096 def_bool y
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001097 depends on X86_32 && (HIGHMEM64G || HIGHMEM4G)
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001098
1099config X86_PAE
Jan Beulich9ba16082008-10-15 22:01:38 -07001100 bool "PAE (Physical Address Extension) Support"
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001101 depends on X86_32 && !HIGHMEM4G
Ingo Molnar8f9ca472009-02-05 16:21:53 +01001102 ---help---
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001103 PAE is required for NX support, and furthermore enables
1104 larger swapspace support for non-overcommit purposes. It
1105 has the cost of more pagetable lookup overhead, and also
1106 consumes more pagetable space per process.
1107
Jeremy Fitzhardinge600715d2008-09-11 01:31:45 -07001108config ARCH_PHYS_ADDR_T_64BIT
Ingo Molnar8f9ca472009-02-05 16:21:53 +01001109 def_bool X86_64 || X86_PAE
Jeremy Fitzhardinge600715d2008-09-11 01:31:45 -07001110
Nick Piggin9e899812008-10-22 12:33:16 +02001111config DIRECT_GBPAGES
1112 bool "Enable 1GB pages for kernel pagetables" if EMBEDDED
1113 default y
1114 depends on X86_64
Ingo Molnar8f9ca472009-02-05 16:21:53 +01001115 ---help---
Nick Piggin9e899812008-10-22 12:33:16 +02001116 Allow the kernel linear mapping to use 1GB pages on CPUs that
1117 support it. This can improve the kernel's performance a tiny bit by
1118 reducing TLB pressure. If in doubt, say "Y".
1119
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001120# Common NUMA Features
1121config NUMA
KOSAKI Motohirofd51b2d2008-11-05 02:27:19 +09001122 bool "Numa Memory Allocation and Scheduler Support"
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001123 depends on SMP
Yinghai Lu0699eae2008-06-17 15:39:01 -07001124 depends on X86_64 || (X86_32 && HIGHMEM64G && (X86_NUMAQ || X86_BIGSMP || X86_SUMMIT && ACPI) && EXPERIMENTAL)
Yinghai Lu0699eae2008-06-17 15:39:01 -07001125 default y if (X86_NUMAQ || X86_SUMMIT || X86_BIGSMP)
Ingo Molnar8f9ca472009-02-05 16:21:53 +01001126 ---help---
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001127 Enable NUMA (Non Uniform Memory Access) support.
KOSAKI Motohirofd51b2d2008-11-05 02:27:19 +09001128
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001129 The kernel will try to allocate memory used by a CPU on the
1130 local memory controller of the CPU and add some more
1131 NUMA awareness to the kernel.
1132
Ingo Molnarc280ea52008-11-08 13:29:45 +01001133 For 64-bit this is recommended if the system is Intel Core i7
KOSAKI Motohirofd51b2d2008-11-05 02:27:19 +09001134 (or later), AMD Opteron, or EM64T NUMA.
1135
1136 For 32-bit this is only needed on (rare) 32-bit-only platforms
1137 that support NUMA topologies, such as NUMAQ / Summit, or if you
1138 boot a 32-bit kernel on a 64-bit NUMA platform.
1139
1140 Otherwise, you should say N.
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001141
1142comment "NUMA (Summit) requires SMP, 64GB highmem support, ACPI"
1143 depends on X86_32 && X86_SUMMIT && (!HIGHMEM64G || !ACPI)
1144
1145config K8_NUMA
Harvey Harrison3c2362e2008-01-30 13:31:03 +01001146 def_bool y
1147 prompt "Old style AMD Opteron NUMA detection"
1148 depends on X86_64 && NUMA && PCI
Ingo Molnar8f9ca472009-02-05 16:21:53 +01001149 ---help---
1150 Enable K8 NUMA node topology detection. You should say Y here if
1151 you have a multi processor AMD K8 system. This uses an old
1152 method to read the NUMA configuration directly from the builtin
1153 Northbridge of Opteron. It is recommended to use X86_64_ACPI_NUMA
1154 instead, which also takes priority if both are compiled in.
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001155
1156config X86_64_ACPI_NUMA
Harvey Harrison3c2362e2008-01-30 13:31:03 +01001157 def_bool y
1158 prompt "ACPI NUMA detection"
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001159 depends on X86_64 && NUMA && ACPI && PCI
1160 select ACPI_NUMA
Ingo Molnar8f9ca472009-02-05 16:21:53 +01001161 ---help---
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001162 Enable ACPI SRAT based node topology detection.
1163
Suresh Siddha6ec6e0d2008-03-25 10:14:35 -07001164# Some NUMA nodes have memory ranges that span
1165# other nodes. Even though a pfn is valid and
1166# between a node's start and end pfns, it may not
1167# reside on that node. See memmap_init_zone()
1168# for details.
1169config NODES_SPAN_OTHER_NODES
1170 def_bool y
1171 depends on X86_64_ACPI_NUMA
1172
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001173config NUMA_EMU
1174 bool "NUMA emulation"
1175 depends on X86_64 && NUMA
Ingo Molnar8f9ca472009-02-05 16:21:53 +01001176 ---help---
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001177 Enable NUMA emulation. A flat machine will be split
1178 into virtual nodes when booted with "numa=fake=N", where N is the
1179 number of nodes. This is only useful for debugging.
1180
1181config NODES_SHIFT
Linus Torvaldsd25e26b2008-08-25 14:15:38 -07001182 int "Maximum NUMA Nodes (as a power of 2)" if !MAXSMP
Jan Beulich46d50c92009-03-12 12:33:06 +00001183 range 1 9
Linus Torvaldsd25e26b2008-08-25 14:15:38 -07001184 default "9" if MAXSMP
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001185 default "6" if X86_64
1186 default "4" if X86_NUMAQ
1187 default "3"
1188 depends on NEED_MULTIPLE_NODES
Ingo Molnar8f9ca472009-02-05 16:21:53 +01001189 ---help---
Mike Travis1184dc22008-05-12 21:21:12 +02001190 Specify the maximum number of NUMA Nodes available on the target
Matt LaPlante692105b2009-01-26 11:12:25 +01001191 system. Increases memory reserved to accommodate various tables.
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001192
Tejun Heoc1329372009-02-24 11:57:20 +09001193config HAVE_ARCH_BOOTMEM
Harvey Harrison3c2362e2008-01-30 13:31:03 +01001194 def_bool y
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001195 depends on X86_32 && NUMA
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001196
1197config ARCH_HAVE_MEMORY_PRESENT
Harvey Harrison3c2362e2008-01-30 13:31:03 +01001198 def_bool y
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001199 depends on X86_32 && DISCONTIGMEM
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001200
1201config NEED_NODE_MEMMAP_SIZE
Harvey Harrison3c2362e2008-01-30 13:31:03 +01001202 def_bool y
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001203 depends on X86_32 && (DISCONTIGMEM || SPARSEMEM)
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001204
1205config HAVE_ARCH_ALLOC_REMAP
Harvey Harrison3c2362e2008-01-30 13:31:03 +01001206 def_bool y
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001207 depends on X86_32 && NUMA
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001208
1209config ARCH_FLATMEM_ENABLE
1210 def_bool y
Jeff Chua99809962008-08-06 19:09:53 +08001211 depends on X86_32 && ARCH_SELECT_MEMORY_MODEL && !NUMA
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001212
1213config ARCH_DISCONTIGMEM_ENABLE
1214 def_bool y
Christoph Lameterb2632952008-01-30 13:30:47 +01001215 depends on NUMA && X86_32
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001216
1217config ARCH_DISCONTIGMEM_DEFAULT
1218 def_bool y
Christoph Lameterb2632952008-01-30 13:30:47 +01001219 depends on NUMA && X86_32
1220
1221config ARCH_SPARSEMEM_DEFAULT
1222 def_bool y
1223 depends on X86_64
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001224
1225config ARCH_SPARSEMEM_ENABLE
1226 def_bool y
Yinghai Lu4272ebf2009-01-29 15:14:46 -08001227 depends on X86_64 || NUMA || (EXPERIMENTAL && X86_32) || X86_32_NON_STANDARD
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001228 select SPARSEMEM_STATIC if X86_32
1229 select SPARSEMEM_VMEMMAP_ENABLE if X86_64
1230
1231config ARCH_SELECT_MEMORY_MODEL
1232 def_bool y
Christoph Lameterb2632952008-01-30 13:30:47 +01001233 depends on ARCH_SPARSEMEM_ENABLE
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001234
1235config ARCH_MEMORY_PROBE
1236 def_bool X86_64
1237 depends on MEMORY_HOTPLUG
1238
1239source "mm/Kconfig"
1240
1241config HIGHPTE
1242 bool "Allocate 3rd-level pagetables from highmem"
1243 depends on X86_32 && (HIGHMEM4G || HIGHMEM64G)
Ingo Molnar8f9ca472009-02-05 16:21:53 +01001244 ---help---
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001245 The VM uses one page table entry for each page of physical memory.
1246 For systems with a lot of RAM, this can be wasteful of precious
1247 low memory. Setting this option will put user-space page table
1248 entries in high memory.
1249
Jeremy Fitzhardinge9f077872008-09-07 01:51:34 -07001250config X86_CHECK_BIOS_CORRUPTION
Ingo Molnar8f9ca472009-02-05 16:21:53 +01001251 bool "Check for low memory corruption"
1252 ---help---
1253 Periodically check for memory corruption in low memory, which
1254 is suspected to be caused by BIOS. Even when enabled in the
1255 configuration, it is disabled at runtime. Enable it by
1256 setting "memory_corruption_check=1" on the kernel command
1257 line. By default it scans the low 64k of memory every 60
1258 seconds; see the memory_corruption_check_size and
1259 memory_corruption_check_period parameters in
1260 Documentation/kernel-parameters.txt to adjust this.
Jeremy Fitzhardinge9f077872008-09-07 01:51:34 -07001261
Ingo Molnar8f9ca472009-02-05 16:21:53 +01001262 When enabled with the default parameters, this option has
1263 almost no overhead, as it reserves a relatively small amount
1264 of memory and scans it infrequently. It both detects corruption
1265 and prevents it from affecting the running system.
Jeremy Fitzhardinge9f077872008-09-07 01:51:34 -07001266
Ingo Molnar8f9ca472009-02-05 16:21:53 +01001267 It is, however, intended as a diagnostic tool; if repeatable
1268 BIOS-originated corruption always affects the same memory,
1269 you can use memmap= to prevent the kernel from using that
1270 memory.
Jeremy Fitzhardinge9f077872008-09-07 01:51:34 -07001271
Jeremy Fitzhardingec885df52008-09-07 02:37:32 -07001272config X86_BOOTPARAM_MEMORY_CORRUPTION_CHECK
Ingo Molnar8f9ca472009-02-05 16:21:53 +01001273 bool "Set the default setting of memory_corruption_check"
Jeremy Fitzhardingec885df52008-09-07 02:37:32 -07001274 depends on X86_CHECK_BIOS_CORRUPTION
1275 default y
Ingo Molnar8f9ca472009-02-05 16:21:53 +01001276 ---help---
1277 Set whether the default state of memory_corruption_check is
1278 on or off.
Jeremy Fitzhardingec885df52008-09-07 02:37:32 -07001279
Ingo Molnarfc381512008-09-16 10:07:34 +02001280config X86_RESERVE_LOW_64K
Ingo Molnar8f9ca472009-02-05 16:21:53 +01001281 bool "Reserve low 64K of RAM on AMI/Phoenix BIOSen"
Ingo Molnarfc381512008-09-16 10:07:34 +02001282 default y
Ingo Molnar8f9ca472009-02-05 16:21:53 +01001283 ---help---
1284 Reserve the first 64K of physical RAM on BIOSes that are known
1285 to potentially corrupt that memory range. A numbers of BIOSes are
1286 known to utilize this area during suspend/resume, so it must not
1287 be used by the kernel.
Ingo Molnarfc381512008-09-16 10:07:34 +02001288
Ingo Molnar8f9ca472009-02-05 16:21:53 +01001289 Set this to N if you are absolutely sure that you trust the BIOS
1290 to get all its memory reservations and usages right.
Ingo Molnarfc381512008-09-16 10:07:34 +02001291
Ingo Molnar8f9ca472009-02-05 16:21:53 +01001292 If you have doubts about the BIOS (e.g. suspend/resume does not
1293 work or there's kernel crashes after certain hardware hotplug
1294 events) and it's not AMI or Phoenix, then you might want to enable
1295 X86_CHECK_BIOS_CORRUPTION=y to allow the kernel to check typical
1296 corruption patterns.
Ingo Molnarfc381512008-09-16 10:07:34 +02001297
Ingo Molnar8f9ca472009-02-05 16:21:53 +01001298 Say Y if unsure.
Ingo Molnarfc381512008-09-16 10:07:34 +02001299
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001300config MATH_EMULATION
1301 bool
1302 prompt "Math emulation" if X86_32
1303 ---help---
1304 Linux can emulate a math coprocessor (used for floating point
1305 operations) if you don't have one. 486DX and Pentium processors have
1306 a math coprocessor built in, 486SX and 386 do not, unless you added
1307 a 487DX or 387, respectively. (The messages during boot time can
1308 give you some hints here ["man dmesg"].) Everyone needs either a
1309 coprocessor or this emulation.
1310
1311 If you don't have a math coprocessor, you need to say Y here; if you
1312 say Y here even though you have a coprocessor, the coprocessor will
1313 be used nevertheless. (This behavior can be changed with the kernel
1314 command line option "no387", which comes handy if your coprocessor
1315 is broken. Try "man bootparam" or see the documentation of your boot
1316 loader (lilo or loadlin) about how to pass options to the kernel at
1317 boot time.) This means that it is a good idea to say Y here if you
1318 intend to use this kernel on different machines.
1319
1320 More information about the internals of the Linux math coprocessor
1321 emulation can be found in <file:arch/x86/math-emu/README>.
1322
1323 If you are not sure, say Y; apart from resulting in a 66 KB bigger
1324 kernel, it won't hurt.
1325
1326config MTRR
1327 bool "MTRR (Memory Type Range Register) support"
1328 ---help---
1329 On Intel P6 family processors (Pentium Pro, Pentium II and later)
1330 the Memory Type Range Registers (MTRRs) may be used to control
1331 processor access to memory ranges. This is most useful if you have
1332 a video (VGA) card on a PCI or AGP bus. Enabling write-combining
1333 allows bus write transfers to be combined into a larger transfer
1334 before bursting over the PCI/AGP bus. This can increase performance
1335 of image write operations 2.5 times or more. Saying Y here creates a
1336 /proc/mtrr file which may be used to manipulate your processor's
1337 MTRRs. Typically the X server should use this.
1338
1339 This code has a reasonably generic interface so that similar
1340 control registers on other processors can be easily supported
1341 as well:
1342
1343 The Cyrix 6x86, 6x86MX and M II processors have Address Range
1344 Registers (ARRs) which provide a similar functionality to MTRRs. For
1345 these, the ARRs are used to emulate the MTRRs.
1346 The AMD K6-2 (stepping 8 and above) and K6-3 processors have two
1347 MTRRs. The Centaur C6 (WinChip) has 8 MCRs, allowing
1348 write-combining. All of these processors are supported by this code
1349 and it makes sense to say Y here if you have one of them.
1350
1351 Saying Y here also fixes a problem with buggy SMP BIOSes which only
1352 set the MTRRs for the boot CPU and not for the secondary CPUs. This
1353 can lead to all sorts of problems, so it's good to say Y here.
1354
1355 You can safely say Y even if your machine doesn't have MTRRs, you'll
1356 just add about 9 KB to your kernel.
1357
Randy Dunlap7225e752008-07-26 17:54:22 -07001358 See <file:Documentation/x86/mtrr.txt> for more information.
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001359
Yinghai Lu95ffa242008-04-29 03:52:33 -07001360config MTRR_SANITIZER
Yinghai Lu2ffb3502008-09-30 16:29:40 -07001361 def_bool y
Yinghai Lu95ffa242008-04-29 03:52:33 -07001362 prompt "MTRR cleanup support"
1363 depends on MTRR
Ingo Molnar8f9ca472009-02-05 16:21:53 +01001364 ---help---
Thomas Gleixneraba37282008-07-15 14:48:48 +02001365 Convert MTRR layout from continuous to discrete, so X drivers can
1366 add writeback entries.
Yinghai Lu95ffa242008-04-29 03:52:33 -07001367
Thomas Gleixneraba37282008-07-15 14:48:48 +02001368 Can be disabled with disable_mtrr_cleanup on the kernel command line.
Matt LaPlante692105b2009-01-26 11:12:25 +01001369 The largest mtrr entry size for a continuous block can be set with
Thomas Gleixneraba37282008-07-15 14:48:48 +02001370 mtrr_chunk_size.
Yinghai Lu95ffa242008-04-29 03:52:33 -07001371
Yinghai Lu2ffb3502008-09-30 16:29:40 -07001372 If unsure, say Y.
Yinghai Lu95ffa242008-04-29 03:52:33 -07001373
1374config MTRR_SANITIZER_ENABLE_DEFAULT
Yinghai Luf5098d62008-04-29 20:25:58 -07001375 int "MTRR cleanup enable value (0-1)"
1376 range 0 1
1377 default "0"
Yinghai Lu95ffa242008-04-29 03:52:33 -07001378 depends on MTRR_SANITIZER
Ingo Molnar8f9ca472009-02-05 16:21:53 +01001379 ---help---
Yinghai Luf5098d62008-04-29 20:25:58 -07001380 Enable mtrr cleanup default value
Yinghai Lu95ffa242008-04-29 03:52:33 -07001381
Yinghai Lu12031a62008-05-02 02:40:22 -07001382config MTRR_SANITIZER_SPARE_REG_NR_DEFAULT
1383 int "MTRR cleanup spare reg num (0-7)"
1384 range 0 7
1385 default "1"
1386 depends on MTRR_SANITIZER
Ingo Molnar8f9ca472009-02-05 16:21:53 +01001387 ---help---
Yinghai Lu12031a62008-05-02 02:40:22 -07001388 mtrr cleanup spare entries default, it can be changed via
Thomas Gleixneraba37282008-07-15 14:48:48 +02001389 mtrr_spare_reg_nr=N on the kernel command line.
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001390
venkatesh.pallipadi@intel.com2e5d9c82008-03-18 17:00:14 -07001391config X86_PAT
Ingo Molnar2a8a2712008-04-26 10:26:52 +02001392 bool
venkatesh.pallipadi@intel.com2e5d9c82008-03-18 17:00:14 -07001393 prompt "x86 PAT support"
Ingo Molnar2a8a2712008-04-26 10:26:52 +02001394 depends on MTRR
Ingo Molnar8f9ca472009-02-05 16:21:53 +01001395 ---help---
venkatesh.pallipadi@intel.com2e5d9c82008-03-18 17:00:14 -07001396 Use PAT attributes to setup page level cache control.
Venki Pallipadi042b78e2008-03-24 14:22:35 -07001397
venkatesh.pallipadi@intel.com2e5d9c82008-03-18 17:00:14 -07001398 PATs are the modern equivalents of MTRRs and are much more
1399 flexible than MTRRs.
1400
1401 Say N here if you see bootup problems (boot crash, boot hang,
Venki Pallipadi042b78e2008-03-24 14:22:35 -07001402 spontaneous reboots) or a non-working video driver.
venkatesh.pallipadi@intel.com2e5d9c82008-03-18 17:00:14 -07001403
1404 If unsure, say Y.
1405
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001406config EFI
Jan Beulich9ba16082008-10-15 22:01:38 -07001407 bool "EFI runtime service support"
Huang, Ying5b836832008-01-30 13:31:19 +01001408 depends on ACPI
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001409 ---help---
Ingo Molnar8f9ca472009-02-05 16:21:53 +01001410 This enables the kernel to use EFI runtime services that are
1411 available (such as the EFI variable services).
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001412
Ingo Molnar8f9ca472009-02-05 16:21:53 +01001413 This option is only useful on systems that have EFI firmware.
1414 In addition, you should use the latest ELILO loader available
1415 at <http://elilo.sourceforge.net> in order to take advantage
1416 of EFI runtime services. However, even with this option, the
1417 resultant kernel should continue to boot on existing non-EFI
1418 platforms.
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001419
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001420config SECCOMP
Harvey Harrison3c2362e2008-01-30 13:31:03 +01001421 def_bool y
1422 prompt "Enable seccomp to safely compute untrusted bytecode"
Ingo Molnar8f9ca472009-02-05 16:21:53 +01001423 ---help---
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001424 This kernel feature is useful for number crunching applications
1425 that may need to compute untrusted bytecode during their
1426 execution. By using pipes or other transports made available to
1427 the process as file descriptors supporting the read/write
1428 syscalls, it's possible to isolate those applications in
1429 their own address space using seccomp. Once seccomp is
Alexey Dobriyan9c0bbee2008-09-09 11:01:31 +04001430 enabled via prctl(PR_SET_SECCOMP), it cannot be disabled
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001431 and the task is only allowed to execute a few safe syscalls
1432 defined by each seccomp mode.
1433
1434 If unsure, say Y. Only embedded should say N here.
1435
Ingo Molnar113c5412008-02-14 10:36:03 +01001436config CC_STACKPROTECTOR_ALL
1437 bool
1438
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001439config CC_STACKPROTECTOR
1440 bool "Enable -fstack-protector buffer overflow detection (EXPERIMENTAL)"
Ingo Molnar113c5412008-02-14 10:36:03 +01001441 select CC_STACKPROTECTOR_ALL
Ingo Molnar8f9ca472009-02-05 16:21:53 +01001442 ---help---
1443 This option turns on the -fstack-protector GCC feature. This
Ingo Molnar113c5412008-02-14 10:36:03 +01001444 feature puts, at the beginning of functions, a canary value on
1445 the stack just before the return address, and validates
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001446 the value just before actually returning. Stack based buffer
1447 overflows (that need to overwrite this return address) now also
1448 overwrite the canary, which gets detected and the attack is then
1449 neutralized via a kernel panic.
1450
1451 This feature requires gcc version 4.2 or above, or a distribution
1452 gcc with the feature backported. Older versions are automatically
Ingo Molnar113c5412008-02-14 10:36:03 +01001453 detected and for those versions, this configuration option is
1454 ignored. (and a warning is printed during bootup)
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001455
1456source kernel/Kconfig.hz
1457
1458config KEXEC
1459 bool "kexec system call"
Ingo Molnar8f9ca472009-02-05 16:21:53 +01001460 ---help---
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001461 kexec is a system call that implements the ability to shutdown your
1462 current kernel, and to start another kernel. It is like a reboot
1463 but it is independent of the system firmware. And like a reboot
1464 you can start any kernel with it, not just Linux.
1465
1466 The name comes from the similarity to the exec system call.
1467
1468 It is an ongoing process to be certain the hardware in a machine
1469 is properly shutdown, so do not be surprised if this code does not
1470 initially work for you. It may help to enable device hotplugging
1471 support. As of this writing the exact hardware interface is
1472 strongly in flux, so no good recommendation can be made.
1473
1474config CRASH_DUMP
Pavel Machek04b69442008-08-14 17:16:50 +02001475 bool "kernel crash dumps"
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001476 depends on X86_64 || (X86_32 && HIGHMEM)
Ingo Molnar8f9ca472009-02-05 16:21:53 +01001477 ---help---
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001478 Generate crash dump after being started by kexec.
1479 This should be normally only set in special crash dump kernels
1480 which are loaded in the main kernel with kexec-tools into
1481 a specially reserved region and then later executed after
1482 a crash by kdump/kexec. The crash dump kernel must be compiled
1483 to a memory address not used by the main kernel or BIOS using
1484 PHYSICAL_START, or it must be built as a relocatable image
1485 (CONFIG_RELOCATABLE=y).
1486 For more details see Documentation/kdump/kdump.txt
1487
Huang Ying3ab83522008-07-25 19:45:07 -07001488config KEXEC_JUMP
1489 bool "kexec jump (EXPERIMENTAL)"
1490 depends on EXPERIMENTAL
Huang Yingfee7b0d2009-03-10 10:57:16 +08001491 depends on KEXEC && HIBERNATION
Ingo Molnar8f9ca472009-02-05 16:21:53 +01001492 ---help---
Huang Ying89081d12008-07-25 19:45:10 -07001493 Jump between original kernel and kexeced kernel and invoke
1494 code in physical address mode via KEXEC
Huang Ying3ab83522008-07-25 19:45:07 -07001495
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001496config PHYSICAL_START
1497 hex "Physical address where the kernel is loaded" if (EMBEDDED || CRASH_DUMP)
1498 default "0x1000000" if X86_NUMAQ
1499 default "0x200000" if X86_64
1500 default "0x100000"
Ingo Molnar8f9ca472009-02-05 16:21:53 +01001501 ---help---
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001502 This gives the physical address where the kernel is loaded.
1503
1504 If kernel is a not relocatable (CONFIG_RELOCATABLE=n) then
1505 bzImage will decompress itself to above physical address and
1506 run from there. Otherwise, bzImage will run from the address where
1507 it has been loaded by the boot loader and will ignore above physical
1508 address.
1509
1510 In normal kdump cases one does not have to set/change this option
1511 as now bzImage can be compiled as a completely relocatable image
1512 (CONFIG_RELOCATABLE=y) and be used to load and run from a different
1513 address. This option is mainly useful for the folks who don't want
1514 to use a bzImage for capturing the crash dump and want to use a
1515 vmlinux instead. vmlinux is not relocatable hence a kernel needs
1516 to be specifically compiled to run from a specific memory area
1517 (normally a reserved region) and this option comes handy.
1518
1519 So if you are using bzImage for capturing the crash dump, leave
1520 the value here unchanged to 0x100000 and set CONFIG_RELOCATABLE=y.
1521 Otherwise if you plan to use vmlinux for capturing the crash dump
1522 change this value to start of the reserved region (Typically 16MB
1523 0x1000000). In other words, it can be set based on the "X" value as
1524 specified in the "crashkernel=YM@XM" command line boot parameter
1525 passed to the panic-ed kernel. Typically this parameter is set as
1526 crashkernel=64M@16M. Please take a look at
1527 Documentation/kdump/kdump.txt for more details about crash dumps.
1528
1529 Usage of bzImage for capturing the crash dump is recommended as
1530 one does not have to build two kernels. Same kernel can be used
1531 as production kernel and capture kernel. Above option should have
1532 gone away after relocatable bzImage support is introduced. But it
1533 is present because there are users out there who continue to use
1534 vmlinux for dump capture. This option should go away down the
1535 line.
1536
1537 Don't change this unless you know what you are doing.
1538
1539config RELOCATABLE
1540 bool "Build a relocatable kernel (EXPERIMENTAL)"
1541 depends on EXPERIMENTAL
Ingo Molnar8f9ca472009-02-05 16:21:53 +01001542 ---help---
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001543 This builds a kernel image that retains relocation information
1544 so it can be loaded someplace besides the default 1MB.
1545 The relocations tend to make the kernel binary about 10% larger,
1546 but are discarded at runtime.
1547
1548 One use is for the kexec on panic case where the recovery kernel
1549 must live at a different physical address than the primary
1550 kernel.
1551
1552 Note: If CONFIG_RELOCATABLE=y, then the kernel runs from the address
1553 it has been loaded at and the compile time physical address
1554 (CONFIG_PHYSICAL_START) is ignored.
1555
1556config PHYSICAL_ALIGN
1557 hex
1558 prompt "Alignment value to which kernel should be aligned" if X86_32
1559 default "0x100000" if X86_32
1560 default "0x200000" if X86_64
1561 range 0x2000 0x400000
Ingo Molnar8f9ca472009-02-05 16:21:53 +01001562 ---help---
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001563 This value puts the alignment restrictions on physical address
1564 where kernel is loaded and run from. Kernel is compiled for an
1565 address which meets above alignment restriction.
1566
1567 If bootloader loads the kernel at a non-aligned address and
1568 CONFIG_RELOCATABLE is set, kernel will move itself to nearest
1569 address aligned to above value and run from there.
1570
1571 If bootloader loads the kernel at a non-aligned address and
1572 CONFIG_RELOCATABLE is not set, kernel will ignore the run time
1573 load address and decompress itself to the address it has been
1574 compiled for and run from there. The address for which kernel is
1575 compiled already meets above alignment restrictions. Hence the
1576 end result is that kernel runs from a physical address meeting
1577 above alignment restrictions.
1578
1579 Don't change this unless you know what you are doing.
1580
1581config HOTPLUG_CPU
Dimitri Sivanich7c13e6a2008-08-11 10:46:46 -05001582 bool "Support for hot-pluggable CPUs"
Ingo Molnar4b19ed92009-01-27 17:47:24 +01001583 depends on SMP && HOTPLUG
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001584 ---help---
Dimitri Sivanich7c13e6a2008-08-11 10:46:46 -05001585 Say Y here to allow turning CPUs off and on. CPUs can be
1586 controlled through /sys/devices/system/cpu.
1587 ( Note: power management support will enable this option
1588 automatically on SMP systems. )
1589 Say N if you want to disable CPU hotplug.
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001590
1591config COMPAT_VDSO
Harvey Harrison3c2362e2008-01-30 13:31:03 +01001592 def_bool y
1593 prompt "Compat VDSO support"
Roland McGrathaf65d642008-01-30 13:30:43 +01001594 depends on X86_32 || IA32_EMULATION
Ingo Molnar8f9ca472009-02-05 16:21:53 +01001595 ---help---
Roland McGrathaf65d642008-01-30 13:30:43 +01001596 Map the 32-bit VDSO to the predictable old-style address too.
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001597 ---help---
1598 Say N here if you are running a sufficiently recent glibc
1599 version (2.3.3 or later), to remove the high-mapped
1600 VDSO mapping and to exclusively use the randomized VDSO.
1601
1602 If unsure, say Y.
1603
Tim Bird516cbf32008-08-12 12:52:36 -07001604config CMDLINE_BOOL
1605 bool "Built-in kernel command line"
1606 default n
Ingo Molnar8f9ca472009-02-05 16:21:53 +01001607 ---help---
Tim Bird516cbf32008-08-12 12:52:36 -07001608 Allow for specifying boot arguments to the kernel at
1609 build time. On some systems (e.g. embedded ones), it is
1610 necessary or convenient to provide some or all of the
1611 kernel boot arguments with the kernel itself (that is,
1612 to not rely on the boot loader to provide them.)
1613
1614 To compile command line arguments into the kernel,
1615 set this option to 'Y', then fill in the
1616 the boot arguments in CONFIG_CMDLINE.
1617
1618 Systems with fully functional boot loaders (i.e. non-embedded)
1619 should leave this option set to 'N'.
1620
1621config CMDLINE
1622 string "Built-in kernel command string"
1623 depends on CMDLINE_BOOL
1624 default ""
Ingo Molnar8f9ca472009-02-05 16:21:53 +01001625 ---help---
Tim Bird516cbf32008-08-12 12:52:36 -07001626 Enter arguments here that should be compiled into the kernel
1627 image and used at boot time. If the boot loader provides a
1628 command line at boot time, it is appended to this string to
1629 form the full kernel command line, when the system boots.
1630
1631 However, you can use the CONFIG_CMDLINE_OVERRIDE option to
1632 change this behavior.
1633
1634 In most cases, the command line (whether built-in or provided
1635 by the boot loader) should specify the device for the root
1636 file system.
1637
1638config CMDLINE_OVERRIDE
1639 bool "Built-in command line overrides boot loader arguments"
1640 default n
1641 depends on CMDLINE_BOOL
Ingo Molnar8f9ca472009-02-05 16:21:53 +01001642 ---help---
Tim Bird516cbf32008-08-12 12:52:36 -07001643 Set this option to 'Y' to have the kernel ignore the boot loader
1644 command line, and use ONLY the built-in command line.
1645
1646 This is used to work around broken boot loaders. This should
1647 be set to 'N' under normal conditions.
1648
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001649endmenu
1650
1651config ARCH_ENABLE_MEMORY_HOTPLUG
1652 def_bool y
1653 depends on X86_64 || (X86_32 && HIGHMEM)
1654
Gary Hade35551052008-10-31 10:52:03 -07001655config ARCH_ENABLE_MEMORY_HOTREMOVE
1656 def_bool y
1657 depends on MEMORY_HOTPLUG
1658
Sam Ravnborg506f1d02007-11-09 21:56:54 +01001659config HAVE_ARCH_EARLY_PFN_TO_NID
1660 def_bool X86_64
1661 depends on NUMA
1662
Bjorn Helgaasda85f862008-11-05 13:37:27 -06001663menu "Power management and ACPI options"
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001664
1665config ARCH_HIBERNATION_HEADER
Harvey Harrison3c2362e2008-01-30 13:31:03 +01001666 def_bool y
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001667 depends on X86_64 && HIBERNATION
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001668
1669source "kernel/power/Kconfig"
1670
1671source "drivers/acpi/Kconfig"
1672
Andi Kleena6b68072008-01-30 13:32:49 +01001673config X86_APM_BOOT
1674 bool
1675 default y
1676 depends on APM || APM_MODULE
1677
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001678menuconfig APM
1679 tristate "APM (Advanced Power Management) BIOS support"
Ingo Molnarefefa6f2008-07-10 16:09:50 +02001680 depends on X86_32 && PM_SLEEP
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001681 ---help---
1682 APM is a BIOS specification for saving power using several different
1683 techniques. This is mostly useful for battery powered laptops with
1684 APM compliant BIOSes. If you say Y here, the system time will be
1685 reset after a RESUME operation, the /proc/apm device will provide
1686 battery status information, and user-space programs will receive
1687 notification of APM "events" (e.g. battery status change).
1688
1689 If you select "Y" here, you can disable actual use of the APM
1690 BIOS by passing the "apm=off" option to the kernel at boot time.
1691
1692 Note that the APM support is almost completely disabled for
1693 machines with more than one CPU.
1694
1695 In order to use APM, you will need supporting software. For location
Randy Dunlap53471122008-03-12 18:10:51 -04001696 and more information, read <file:Documentation/power/pm.txt> and the
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001697 Battery Powered Linux mini-HOWTO, available from
1698 <http://www.tldp.org/docs.html#howto>.
1699
1700 This driver does not spin down disk drives (see the hdparm(8)
1701 manpage ("man 8 hdparm") for that), and it doesn't turn off
1702 VESA-compliant "green" monitors.
1703
1704 This driver does not support the TI 4000M TravelMate and the ACER
1705 486/DX4/75 because they don't have compliant BIOSes. Many "green"
1706 desktop machines also don't have compliant BIOSes, and this driver
1707 may cause those machines to panic during the boot phase.
1708
1709 Generally, if you don't have a battery in your machine, there isn't
1710 much point in using this driver and you should say N. If you get
1711 random kernel OOPSes or reboots that don't seem to be related to
1712 anything, try disabling/enabling this option (or disabling/enabling
1713 APM in your BIOS).
1714
1715 Some other things you should try when experiencing seemingly random,
1716 "weird" problems:
1717
1718 1) make sure that you have enough swap space and that it is
1719 enabled.
1720 2) pass the "no-hlt" option to the kernel
1721 3) switch on floating point emulation in the kernel and pass
1722 the "no387" option to the kernel
1723 4) pass the "floppy=nodma" option to the kernel
1724 5) pass the "mem=4M" option to the kernel (thereby disabling
1725 all but the first 4 MB of RAM)
1726 6) make sure that the CPU is not over clocked.
1727 7) read the sig11 FAQ at <http://www.bitwizard.nl/sig11/>
1728 8) disable the cache from your BIOS settings
1729 9) install a fan for the video card or exchange video RAM
1730 10) install a better fan for the CPU
1731 11) exchange RAM chips
1732 12) exchange the motherboard.
1733
1734 To compile this driver as a module, choose M here: the
1735 module will be called apm.
1736
1737if APM
1738
1739config APM_IGNORE_USER_SUSPEND
1740 bool "Ignore USER SUSPEND"
Ingo Molnar8f9ca472009-02-05 16:21:53 +01001741 ---help---
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001742 This option will ignore USER SUSPEND requests. On machines with a
1743 compliant APM BIOS, you want to say N. However, on the NEC Versa M
1744 series notebooks, it is necessary to say Y because of a BIOS bug.
1745
1746config APM_DO_ENABLE
1747 bool "Enable PM at boot time"
1748 ---help---
1749 Enable APM features at boot time. From page 36 of the APM BIOS
1750 specification: "When disabled, the APM BIOS does not automatically
1751 power manage devices, enter the Standby State, enter the Suspend
1752 State, or take power saving steps in response to CPU Idle calls."
1753 This driver will make CPU Idle calls when Linux is idle (unless this
1754 feature is turned off -- see "Do CPU IDLE calls", below). This
1755 should always save battery power, but more complicated APM features
1756 will be dependent on your BIOS implementation. You may need to turn
1757 this option off if your computer hangs at boot time when using APM
1758 support, or if it beeps continuously instead of suspending. Turn
1759 this off if you have a NEC UltraLite Versa 33/C or a Toshiba
1760 T400CDT. This is off by default since most machines do fine without
1761 this feature.
1762
1763config APM_CPU_IDLE
1764 bool "Make CPU Idle calls when idle"
Ingo Molnar8f9ca472009-02-05 16:21:53 +01001765 ---help---
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001766 Enable calls to APM CPU Idle/CPU Busy inside the kernel's idle loop.
1767 On some machines, this can activate improved power savings, such as
1768 a slowed CPU clock rate, when the machine is idle. These idle calls
1769 are made after the idle loop has run for some length of time (e.g.,
1770 333 mS). On some machines, this will cause a hang at boot time or
1771 whenever the CPU becomes idle. (On machines with more than one CPU,
1772 this option does nothing.)
1773
1774config APM_DISPLAY_BLANK
1775 bool "Enable console blanking using APM"
Ingo Molnar8f9ca472009-02-05 16:21:53 +01001776 ---help---
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001777 Enable console blanking using the APM. Some laptops can use this to
1778 turn off the LCD backlight when the screen blanker of the Linux
1779 virtual console blanks the screen. Note that this is only used by
1780 the virtual console screen blanker, and won't turn off the backlight
1781 when using the X Window system. This also doesn't have anything to
1782 do with your VESA-compliant power-saving monitor. Further, this
1783 option doesn't work for all laptops -- it might not turn off your
1784 backlight at all, or it might print a lot of errors to the console,
1785 especially if you are using gpm.
1786
1787config APM_ALLOW_INTS
1788 bool "Allow interrupts during APM BIOS calls"
Ingo Molnar8f9ca472009-02-05 16:21:53 +01001789 ---help---
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001790 Normally we disable external interrupts while we are making calls to
1791 the APM BIOS as a measure to lessen the effects of a badly behaving
1792 BIOS implementation. The BIOS should reenable interrupts if it
1793 needs to. Unfortunately, some BIOSes do not -- especially those in
1794 many of the newer IBM Thinkpads. If you experience hangs when you
1795 suspend, try setting this to Y. Otherwise, say N.
1796
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001797endif # APM
1798
1799source "arch/x86/kernel/cpu/cpufreq/Kconfig"
1800
1801source "drivers/cpuidle/Kconfig"
1802
Andy Henroid27471fd2008-10-09 11:45:22 -07001803source "drivers/idle/Kconfig"
1804
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001805endmenu
1806
1807
1808menu "Bus options (PCI etc.)"
1809
1810config PCI
Ingo Molnar1ac97012008-05-19 14:10:14 +02001811 bool "PCI support"
Adrian Bunk1c858082008-01-30 13:32:32 +01001812 default y
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001813 select ARCH_SUPPORTS_MSI if (X86_LOCAL_APIC && X86_IO_APIC)
Ingo Molnar8f9ca472009-02-05 16:21:53 +01001814 ---help---
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001815 Find out whether you have a PCI motherboard. PCI is the name of a
1816 bus system, i.e. the way the CPU talks to the other stuff inside
1817 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
1818 VESA. If you have PCI, say Y, otherwise N.
1819
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001820choice
1821 prompt "PCI access mode"
Ingo Molnarefefa6f2008-07-10 16:09:50 +02001822 depends on X86_32 && PCI
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001823 default PCI_GOANY
1824 ---help---
1825 On PCI systems, the BIOS can be used to detect the PCI devices and
1826 determine their configuration. However, some old PCI motherboards
1827 have BIOS bugs and may crash if this is done. Also, some embedded
1828 PCI-based systems don't have any BIOS at all. Linux can also try to
1829 detect the PCI hardware directly without using the BIOS.
1830
1831 With this option, you can specify how Linux should detect the
1832 PCI devices. If you choose "BIOS", the BIOS will be used,
1833 if you choose "Direct", the BIOS won't be used, and if you
1834 choose "MMConfig", then PCI Express MMCONFIG will be used.
1835 If you choose "Any", the kernel will try MMCONFIG, then the
1836 direct access method and falls back to the BIOS if that doesn't
1837 work. If unsure, go with the default, which is "Any".
1838
1839config PCI_GOBIOS
1840 bool "BIOS"
1841
1842config PCI_GOMMCONFIG
1843 bool "MMConfig"
1844
1845config PCI_GODIRECT
1846 bool "Direct"
1847
Andres Salomon3ef0e1f2008-04-29 00:59:53 -07001848config PCI_GOOLPC
1849 bool "OLPC"
1850 depends on OLPC
1851
Andres Salomon2bdd1b02008-06-05 14:14:41 -07001852config PCI_GOANY
1853 bool "Any"
1854
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001855endchoice
1856
1857config PCI_BIOS
Harvey Harrison3c2362e2008-01-30 13:31:03 +01001858 def_bool y
Ingo Molnarefefa6f2008-07-10 16:09:50 +02001859 depends on X86_32 && PCI && (PCI_GOBIOS || PCI_GOANY)
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001860
1861# x86-64 doesn't support PCI BIOS access from long mode so always go direct.
1862config PCI_DIRECT
Harvey Harrison3c2362e2008-01-30 13:31:03 +01001863 def_bool y
Ingo Molnarefefa6f2008-07-10 16:09:50 +02001864 depends on PCI && (X86_64 || (PCI_GODIRECT || PCI_GOANY || PCI_GOOLPC))
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001865
1866config PCI_MMCONFIG
Harvey Harrison3c2362e2008-01-30 13:31:03 +01001867 def_bool y
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001868 depends on X86_32 && PCI && ACPI && (PCI_GOMMCONFIG || PCI_GOANY)
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001869
Andres Salomon3ef0e1f2008-04-29 00:59:53 -07001870config PCI_OLPC
Andres Salomon2bdd1b02008-06-05 14:14:41 -07001871 def_bool y
1872 depends on PCI && OLPC && (PCI_GOOLPC || PCI_GOANY)
Andres Salomon3ef0e1f2008-04-29 00:59:53 -07001873
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001874config PCI_DOMAINS
Harvey Harrison3c2362e2008-01-30 13:31:03 +01001875 def_bool y
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001876 depends on PCI
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001877
1878config PCI_MMCONFIG
1879 bool "Support mmconfig PCI config space access"
1880 depends on X86_64 && PCI && ACPI
1881
1882config DMAR
1883 bool "Support for DMA Remapping Devices (EXPERIMENTAL)"
David Woodhouse4cf2e752009-02-11 17:23:43 +00001884 depends on PCI_MSI && ACPI && EXPERIMENTAL
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001885 help
1886 DMA remapping (DMAR) devices support enables independent address
1887 translations for Direct Memory Access (DMA) from devices.
1888 These DMA remapping devices are reported via ACPI tables
1889 and include PCI device scope covered by these DMA
1890 remapping devices.
1891
Kyle McMartin0cd5c3c2009-02-04 14:29:19 -08001892config DMAR_DEFAULT_ON
Kyle McMartinf6be37f2009-02-26 12:57:56 -05001893 def_bool y
Kyle McMartin0cd5c3c2009-02-04 14:29:19 -08001894 prompt "Enable DMA Remapping Devices by default"
1895 depends on DMAR
1896 help
1897 Selecting this option will enable a DMAR device at boot time if
1898 one is found. If this option is not selected, DMAR support can
1899 be enabled by passing intel_iommu=on to the kernel. It is
1900 recommended you say N here while the DMAR code remains
1901 experimental.
1902
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001903config DMAR_GFX_WA
Harvey Harrison3c2362e2008-01-30 13:31:03 +01001904 def_bool y
1905 prompt "Support for Graphics workaround"
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001906 depends on DMAR
Ingo Molnar8f9ca472009-02-05 16:21:53 +01001907 ---help---
1908 Current Graphics drivers tend to use physical address
1909 for DMA and avoid using DMA APIs. Setting this config
1910 option permits the IOMMU driver to set a unity map for
1911 all the OS-visible memory. Hence the driver can continue
1912 to use physical addresses for DMA.
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001913
1914config DMAR_FLOPPY_WA
Harvey Harrison3c2362e2008-01-30 13:31:03 +01001915 def_bool y
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001916 depends on DMAR
Ingo Molnar8f9ca472009-02-05 16:21:53 +01001917 ---help---
1918 Floppy disk drivers are know to bypass DMA API calls
1919 thereby failing to work when IOMMU is enabled. This
1920 workaround will setup a 1:1 mapping for the first
1921 16M to make floppy (an ISA device) work.
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001922
Suresh Siddha9fa8c482008-07-10 11:17:00 -07001923config INTR_REMAP
1924 bool "Support for Interrupt Remapping (EXPERIMENTAL)"
1925 depends on X86_64 && X86_IO_APIC && PCI_MSI && ACPI && EXPERIMENTAL
Ingo Molnar8f9ca472009-02-05 16:21:53 +01001926 ---help---
1927 Supports Interrupt remapping for IO-APIC and MSI devices.
1928 To use x2apic mode in the CPU's which support x2APIC enhancements or
1929 to support platforms with CPU's having > 8 bit APIC ID, say Y.
Suresh Siddha9fa8c482008-07-10 11:17:00 -07001930
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001931source "drivers/pci/pcie/Kconfig"
1932
1933source "drivers/pci/Kconfig"
1934
1935# x86_64 have no ISA slots, but do have ISA-style DMA.
1936config ISA_DMA_API
Harvey Harrison3c2362e2008-01-30 13:31:03 +01001937 def_bool y
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001938
1939if X86_32
1940
1941config ISA
1942 bool "ISA support"
Ingo Molnar8f9ca472009-02-05 16:21:53 +01001943 ---help---
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001944 Find out whether you have ISA slots on your motherboard. ISA is the
1945 name of a bus system, i.e. the way the CPU talks to the other stuff
1946 inside your box. Other bus systems are PCI, EISA, MicroChannel
1947 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
1948 newer boards don't support it. If you have ISA, say Y, otherwise N.
1949
1950config EISA
1951 bool "EISA support"
1952 depends on ISA
1953 ---help---
1954 The Extended Industry Standard Architecture (EISA) bus was
1955 developed as an open alternative to the IBM MicroChannel bus.
1956
1957 The EISA bus provided some of the features of the IBM MicroChannel
1958 bus while maintaining backward compatibility with cards made for
1959 the older ISA bus. The EISA bus saw limited use between 1988 and
1960 1995 when it was made obsolete by the PCI bus.
1961
1962 Say Y here if you are building a kernel for an EISA-based machine.
1963
1964 Otherwise, say N.
1965
1966source "drivers/eisa/Kconfig"
1967
1968config MCA
Ingo Molnar72ee6eb2009-01-27 16:57:49 +01001969 bool "MCA support"
Ingo Molnar8f9ca472009-02-05 16:21:53 +01001970 ---help---
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001971 MicroChannel Architecture is found in some IBM PS/2 machines and
1972 laptops. It is a bus system similar to PCI or ISA. See
1973 <file:Documentation/mca.txt> (and especially the web page given
1974 there) before attempting to build an MCA bus kernel.
1975
1976source "drivers/mca/Kconfig"
1977
1978config SCx200
1979 tristate "NatSemi SCx200 support"
Ingo Molnar8f9ca472009-02-05 16:21:53 +01001980 ---help---
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001981 This provides basic support for National Semiconductor's
1982 (now AMD's) Geode processors. The driver probes for the
1983 PCI-IDs of several on-chip devices, so its a good dependency
1984 for other scx200_* drivers.
1985
1986 If compiled as a module, the driver is named scx200.
1987
1988config SCx200HR_TIMER
1989 tristate "NatSemi SCx200 27MHz High-Resolution Timer Support"
1990 depends on SCx200 && GENERIC_TIME
1991 default y
Ingo Molnar8f9ca472009-02-05 16:21:53 +01001992 ---help---
Sam Ravnborge279b6c2007-11-06 20:41:05 +01001993 This driver provides a clocksource built upon the on-chip
1994 27MHz high-resolution timer. Its also a workaround for
1995 NSC Geode SC-1100's buggy TSC, which loses time when the
1996 processor goes idle (as is done by the scheduler). The
1997 other workaround is idle=poll boot option.
1998
1999config GEODE_MFGPT_TIMER
Harvey Harrison3c2362e2008-01-30 13:31:03 +01002000 def_bool y
2001 prompt "Geode Multi-Function General Purpose Timer (MFGPT) events"
Sam Ravnborge279b6c2007-11-06 20:41:05 +01002002 depends on MGEODE_LX && GENERIC_TIME && GENERIC_CLOCKEVENTS
Ingo Molnar8f9ca472009-02-05 16:21:53 +01002003 ---help---
Sam Ravnborge279b6c2007-11-06 20:41:05 +01002004 This driver provides a clock event source based on the MFGPT
2005 timer(s) in the CS5535 and CS5536 companion chip for the geode.
2006 MFGPTs have a better resolution and max interval than the
2007 generic PIT, and are suitable for use as high-res timers.
2008
Andres Salomon3ef0e1f2008-04-29 00:59:53 -07002009config OLPC
2010 bool "One Laptop Per Child support"
2011 default n
Ingo Molnar8f9ca472009-02-05 16:21:53 +01002012 ---help---
Andres Salomon3ef0e1f2008-04-29 00:59:53 -07002013 Add support for detecting the unique features of the OLPC
2014 XO hardware.
2015
Sam Ravnborgbc0120f2007-11-06 23:10:39 +01002016endif # X86_32
2017
Sam Ravnborge279b6c2007-11-06 20:41:05 +01002018config K8_NB
2019 def_bool y
Sam Ravnborgbc0120f2007-11-06 23:10:39 +01002020 depends on AGP_AMD64 || (X86_64 && (GART_IOMMU || (PCI && NUMA)))
Sam Ravnborge279b6c2007-11-06 20:41:05 +01002021
2022source "drivers/pcmcia/Kconfig"
2023
2024source "drivers/pci/hotplug/Kconfig"
2025
2026endmenu
2027
2028
2029menu "Executable file formats / Emulations"
2030
2031source "fs/Kconfig.binfmt"
2032
2033config IA32_EMULATION
2034 bool "IA32 Emulation"
2035 depends on X86_64
Roland McGratha97f52e2008-01-30 13:31:55 +01002036 select COMPAT_BINFMT_ELF
Ingo Molnar8f9ca472009-02-05 16:21:53 +01002037 ---help---
Sam Ravnborge279b6c2007-11-06 20:41:05 +01002038 Include code to run 32-bit programs under a 64-bit kernel. You should
2039 likely turn this on, unless you're 100% sure that you don't have any
2040 32-bit programs left.
2041
2042config IA32_AOUT
Ingo Molnar8f9ca472009-02-05 16:21:53 +01002043 tristate "IA32 a.out support"
2044 depends on IA32_EMULATION
2045 ---help---
2046 Support old a.out binaries in the 32bit emulation.
Sam Ravnborge279b6c2007-11-06 20:41:05 +01002047
2048config COMPAT
Harvey Harrison3c2362e2008-01-30 13:31:03 +01002049 def_bool y
Sam Ravnborge279b6c2007-11-06 20:41:05 +01002050 depends on IA32_EMULATION
Sam Ravnborge279b6c2007-11-06 20:41:05 +01002051
2052config COMPAT_FOR_U64_ALIGNMENT
2053 def_bool COMPAT
2054 depends on X86_64
2055
2056config SYSVIPC_COMPAT
Harvey Harrison3c2362e2008-01-30 13:31:03 +01002057 def_bool y
Alexey Dobriyanb8992192008-09-14 13:44:41 +04002058 depends on COMPAT && SYSVIPC
Sam Ravnborge279b6c2007-11-06 20:41:05 +01002059
2060endmenu
2061
2062
Keith Packarde5beae12008-11-03 18:21:45 +01002063config HAVE_ATOMIC_IOMAP
2064 def_bool y
2065 depends on X86_32
2066
Sam Ravnborge279b6c2007-11-06 20:41:05 +01002067source "net/Kconfig"
2068
2069source "drivers/Kconfig"
2070
2071source "drivers/firmware/Kconfig"
2072
2073source "fs/Kconfig"
2074
Sam Ravnborge279b6c2007-11-06 20:41:05 +01002075source "arch/x86/Kconfig.debug"
2076
2077source "security/Kconfig"
2078
2079source "crypto/Kconfig"
2080
Avi Kivityedf88412007-12-16 11:02:48 +02002081source "arch/x86/kvm/Kconfig"
2082
Sam Ravnborge279b6c2007-11-06 20:41:05 +01002083source "lib/Kconfig"