]>
Commit | Line | Data |
---|---|---|
daa93fab SR |
1 | # Select 32 or 64 bit |
2 | config 64BIT | |
6840999b SR |
3 | bool "64-bit kernel" if ARCH = "x86" |
4 | default ARCH = "x86_64" | |
8f9ca475 | 5 | ---help--- |
daa93fab SR |
6 | Say yes to build a 64-bit kernel - formerly known as x86_64 |
7 | Say no to build a 32-bit kernel - formerly known as i386 | |
8 | ||
9 | config X86_32 | |
10 | def_bool !64BIT | |
11 | ||
12 | config X86_64 | |
13 | def_bool 64BIT | |
1032c0ba SR |
14 | |
15 | ### Arch settings | |
8d5fffb9 | 16 | config X86 |
3c2362e6 | 17 | def_bool y |
e17c6d56 | 18 | select HAVE_AOUT if X86_32 |
2c5643b1 HM |
19 | select HAVE_READQ |
20 | select HAVE_WRITEQ | |
a5574cf6 | 21 | select HAVE_UNSTABLE_SCHED_CLOCK |
ec7748b5 | 22 | select HAVE_IDE |
42d4b839 | 23 | select HAVE_OPROFILE |
cdd6c482 | 24 | select HAVE_PERF_EVENTS if (!M386 && !M486) |
e360adbe | 25 | select HAVE_IRQ_WORK |
28b2ee20 | 26 | select HAVE_IOREMAP_PROT |
3f550096 | 27 | select HAVE_KPROBES |
72d7c3b3 | 28 | select HAVE_MEMBLOCK |
1f972768 | 29 | select ARCH_WANT_OPTIONAL_GPIOLIB |
da4276b8 | 30 | select ARCH_WANT_FRAME_POINTERS |
7c095e46 | 31 | select HAVE_DMA_ATTRS |
9edddaa2 | 32 | select HAVE_KRETPROBES |
c0f7ac3a | 33 | select HAVE_OPTPROBES |
e4b2b886 | 34 | select HAVE_FTRACE_MCOUNT_RECORD |
cf4db259 | 35 | select HAVE_C_RECORDMCOUNT |
677aa9f7 | 36 | select HAVE_DYNAMIC_FTRACE |
606576ce | 37 | select HAVE_FUNCTION_TRACER |
48d68b20 | 38 | select HAVE_FUNCTION_GRAPH_TRACER |
71e308a2 | 39 | select HAVE_FUNCTION_GRAPH_FP_TEST |
60a7ecf4 | 40 | select HAVE_FUNCTION_TRACE_MCOUNT_TEST |
9a5fd902 | 41 | select HAVE_FTRACE_NMI_ENTER if DYNAMIC_FTRACE |
66700001 | 42 | select HAVE_SYSCALL_TRACEPOINTS |
e0ec9483 | 43 | select HAVE_KVM |
49793b03 | 44 | select HAVE_ARCH_KGDB |
99bbc4b1 | 45 | select HAVE_ARCH_TRACEHOOK |
323ec001 | 46 | select HAVE_GENERIC_DMA_COHERENT if X86_32 |
58340a07 | 47 | select HAVE_EFFICIENT_UNALIGNED_ACCESS |
8d26487f | 48 | select USER_STACKTRACE_SUPPORT |
f850c30c | 49 | select HAVE_REGS_AND_STACK_ACCESS_API |
2118d0c5 | 50 | select HAVE_DMA_API_DEBUG |
2e9f3bdd PA |
51 | select HAVE_KERNEL_GZIP |
52 | select HAVE_KERNEL_BZIP2 | |
53 | select HAVE_KERNEL_LZMA | |
13510997 | 54 | select HAVE_KERNEL_LZO |
0067f129 | 55 | select HAVE_HW_BREAKPOINT |
0102752e | 56 | select HAVE_MIXED_BREAKPOINTS_REGS |
99e8c5a3 | 57 | select PERF_EVENTS |
c01d4323 | 58 | select HAVE_PERF_EVENTS_NMI |
99e8c5a3 | 59 | select ANON_INODES |
0a4af3b0 | 60 | select HAVE_ARCH_KMEMCHECK |
7c68af6e | 61 | select HAVE_USER_RETURN_NOTIFIER |
46eb3b64 | 62 | select HAVE_ARCH_JUMP_LABEL |
3cba11d3 | 63 | select HAVE_TEXT_POKE_SMP |
3bb9808e TG |
64 | select HAVE_GENERIC_HARDIRQS |
65 | select HAVE_SPARSE_IRQ | |
3bb9808e TG |
66 | select GENERIC_IRQ_PROBE |
67 | select GENERIC_PENDING_IRQ if SMP | |
7d8330a5 | 68 | |
ba7e4d13 IM |
69 | config INSTRUCTION_DECODER |
70 | def_bool (KPROBES || PERF_EVENTS) | |
71 | ||
51b26ada LT |
72 | config OUTPUT_FORMAT |
73 | string | |
74 | default "elf32-i386" if X86_32 | |
75 | default "elf64-x86-64" if X86_64 | |
76 | ||
73531905 | 77 | config ARCH_DEFCONFIG |
b9b39bfb | 78 | string |
73531905 SR |
79 | default "arch/x86/configs/i386_defconfig" if X86_32 |
80 | default "arch/x86/configs/x86_64_defconfig" if X86_64 | |
b9b39bfb | 81 | |
8d5fffb9 | 82 | config GENERIC_CMOS_UPDATE |
3c2362e6 | 83 | def_bool y |
8d5fffb9 SR |
84 | |
85 | config CLOCKSOURCE_WATCHDOG | |
3c2362e6 | 86 | def_bool y |
8d5fffb9 SR |
87 | |
88 | config GENERIC_CLOCKEVENTS | |
3c2362e6 | 89 | def_bool y |
8d5fffb9 SR |
90 | |
91 | config GENERIC_CLOCKEVENTS_BROADCAST | |
3c2362e6 | 92 | def_bool y |
8d5fffb9 SR |
93 | depends on X86_64 || (X86_32 && X86_LOCAL_APIC) |
94 | ||
95 | config LOCKDEP_SUPPORT | |
3c2362e6 | 96 | def_bool y |
8d5fffb9 SR |
97 | |
98 | config STACKTRACE_SUPPORT | |
3c2362e6 | 99 | def_bool y |
8d5fffb9 | 100 | |
aa7d9350 HC |
101 | config HAVE_LATENCYTOP_SUPPORT |
102 | def_bool y | |
103 | ||
8d5fffb9 | 104 | config MMU |
3c2362e6 | 105 | def_bool y |
8d5fffb9 SR |
106 | |
107 | config ZONE_DMA | |
3c2362e6 | 108 | def_bool y |
8d5fffb9 | 109 | |
8d5fffb9 SR |
110 | config SBUS |
111 | bool | |
112 | ||
3bc4e459 FT |
113 | config NEED_DMA_MAP_STATE |
114 | def_bool (X86_64 || DMAR || DMA_API_DEBUG) | |
115 | ||
18e98307 | 116 | config NEED_SG_DMA_LENGTH |
4a14d84e | 117 | def_bool y |
18e98307 | 118 | |
8d5fffb9 | 119 | config GENERIC_ISA_DMA |
3c2362e6 | 120 | def_bool y |
8d5fffb9 SR |
121 | |
122 | config GENERIC_IOMAP | |
3c2362e6 | 123 | def_bool y |
8d5fffb9 SR |
124 | |
125 | config GENERIC_BUG | |
3c2362e6 | 126 | def_bool y |
8d5fffb9 | 127 | depends on BUG |
b93a531e JB |
128 | select GENERIC_BUG_RELATIVE_POINTERS if X86_64 |
129 | ||
130 | config GENERIC_BUG_RELATIVE_POINTERS | |
131 | bool | |
8d5fffb9 SR |
132 | |
133 | config GENERIC_HWEIGHT | |
3c2362e6 | 134 | def_bool y |
8d5fffb9 | 135 | |
a6082959 | 136 | config GENERIC_GPIO |
9ba16087 | 137 | bool |
a6082959 | 138 | |
8d5fffb9 | 139 | config ARCH_MAY_HAVE_PC_FDC |
3c2362e6 | 140 | def_bool y |
8d5fffb9 | 141 | |
1032c0ba SR |
142 | config RWSEM_GENERIC_SPINLOCK |
143 | def_bool !X86_XADD | |
144 | ||
145 | config RWSEM_XCHGADD_ALGORITHM | |
146 | def_bool X86_XADD | |
147 | ||
a6869cc4 VP |
148 | config ARCH_HAS_CPU_IDLE_WAIT |
149 | def_bool y | |
150 | ||
1032c0ba SR |
151 | config GENERIC_CALIBRATE_DELAY |
152 | def_bool y | |
153 | ||
8d5fffb9 SR |
154 | config GENERIC_TIME_VSYSCALL |
155 | bool | |
156 | default X86_64 | |
157 | ||
9a0b8415 | 158 | config ARCH_HAS_CPU_RELAX |
159 | def_bool y | |
160 | ||
89cedfef VP |
161 | config ARCH_HAS_DEFAULT_IDLE |
162 | def_bool y | |
163 | ||
1b27d05b PE |
164 | config ARCH_HAS_CACHE_LINE_SIZE |
165 | def_bool y | |
166 | ||
dd5af90a | 167 | config HAVE_SETUP_PER_CPU_AREA |
89c9c4c5 | 168 | def_bool y |
b32ef636 | 169 | |
08fc4580 TH |
170 | config NEED_PER_CPU_EMBED_FIRST_CHUNK |
171 | def_bool y | |
172 | ||
173 | config NEED_PER_CPU_PAGE_FIRST_CHUNK | |
11124411 TH |
174 | def_bool y |
175 | ||
9f0e8d04 MT |
176 | config HAVE_CPUMASK_OF_CPU_MAP |
177 | def_bool X86_64_SMP | |
178 | ||
801e4062 JB |
179 | config ARCH_HIBERNATION_POSSIBLE |
180 | def_bool y | |
801e4062 | 181 | |
f4cb5700 JB |
182 | config ARCH_SUSPEND_POSSIBLE |
183 | def_bool y | |
f4cb5700 | 184 | |
8d5fffb9 SR |
185 | config ZONE_DMA32 |
186 | bool | |
187 | default X86_64 | |
188 | ||
189 | config ARCH_POPULATES_NODE_MAP | |
190 | def_bool y | |
191 | ||
192 | config AUDIT_ARCH | |
193 | bool | |
194 | default X86_64 | |
195 | ||
765c68bd IM |
196 | config ARCH_SUPPORTS_OPTIMIZED_INLINING |
197 | def_bool y | |
198 | ||
6a11f75b AM |
199 | config ARCH_SUPPORTS_DEBUG_PAGEALLOC |
200 | def_bool y | |
201 | ||
69575d38 SW |
202 | config HAVE_INTEL_TXT |
203 | def_bool y | |
204 | depends on EXPERIMENTAL && DMAR && ACPI | |
205 | ||
6cd10f8d JB |
206 | config USE_GENERIC_SMP_HELPERS |
207 | def_bool y | |
208 | depends on SMP | |
209 | ||
6b0c3d44 SR |
210 | config X86_32_SMP |
211 | def_bool y | |
212 | depends on X86_32 && SMP | |
213 | ||
214 | config X86_64_SMP | |
215 | def_bool y | |
216 | depends on X86_64 && SMP | |
217 | ||
8d5fffb9 | 218 | config X86_HT |
6fc108a0 | 219 | def_bool y |
ee0011a7 | 220 | depends on SMP |
8d5fffb9 SR |
221 | |
222 | config X86_TRAMPOLINE | |
6fc108a0 | 223 | def_bool y |
3e5095d1 | 224 | depends on SMP || (64BIT && ACPI_SLEEP) |
8d5fffb9 | 225 | |
ccbeed3a TH |
226 | config X86_32_LAZY_GS |
227 | def_bool y | |
60a5317f | 228 | depends on X86_32 && !CC_STACKPROTECTOR |
ccbeed3a | 229 | |
d61931d8 BP |
230 | config ARCH_HWEIGHT_CFLAGS |
231 | string | |
232 | default "-fcall-saved-ecx -fcall-saved-edx" if X86_32 | |
233 | default "-fcall-saved-rdi -fcall-saved-rsi -fcall-saved-rdx -fcall-saved-rcx -fcall-saved-r8 -fcall-saved-r9 -fcall-saved-r10 -fcall-saved-r11" if X86_64 | |
234 | ||
8d5fffb9 SR |
235 | config KTIME_SCALAR |
236 | def_bool X86_32 | |
d7c53c9e BP |
237 | |
238 | config ARCH_CPU_PROBE_RELEASE | |
239 | def_bool y | |
240 | depends on HOTPLUG_CPU | |
241 | ||
506f1d07 | 242 | source "init/Kconfig" |
dc52ddc0 | 243 | source "kernel/Kconfig.freezer" |
8d5fffb9 | 244 | |
506f1d07 SR |
245 | menu "Processor type and features" |
246 | ||
247 | source "kernel/time/Kconfig" | |
248 | ||
249 | config SMP | |
250 | bool "Symmetric multi-processing support" | |
251 | ---help--- | |
252 | This enables support for systems with more than one CPU. If you have | |
253 | a system with only one CPU, like most personal computers, say N. If | |
254 | you have a system with more than one CPU, say Y. | |
255 | ||
256 | If you say N here, the kernel will run on single and multiprocessor | |
257 | machines, but will use only one CPU of a multiprocessor machine. If | |
258 | you say Y here, the kernel will run on many, but not all, | |
259 | singleprocessor machines. On a singleprocessor machine, the kernel | |
260 | will run faster if you say N here. | |
261 | ||
262 | Note that if you say Y here and choose architecture "586" or | |
263 | "Pentium" under "Processor family", the kernel will not work on 486 | |
264 | architectures. Similarly, multiprocessor kernels for the "PPro" | |
265 | architecture may not work on all Pentium based boards. | |
266 | ||
267 | People using multiprocessor machines who say Y here should also say | |
268 | Y to "Enhanced Real Time Clock Support", below. The "Advanced Power | |
269 | Management" code will be disabled if you say Y here. | |
270 | ||
03502faa | 271 | See also <file:Documentation/i386/IO-APIC.txt>, |
506f1d07 SR |
272 | <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at |
273 | <http://www.tldp.org/docs.html#howto>. | |
274 | ||
275 | If you don't know what to do here, say N. | |
276 | ||
06cd9a7d YL |
277 | config X86_X2APIC |
278 | bool "Support x2apic" | |
f7d7f866 | 279 | depends on X86_LOCAL_APIC && X86_64 && INTR_REMAP |
06cd9a7d YL |
280 | ---help--- |
281 | This enables x2apic support on CPUs that have this feature. | |
282 | ||
283 | This allows 32-bit apic IDs (so it can support very large systems), | |
284 | and accesses the local apic via MSRs not via mmio. | |
285 | ||
06cd9a7d YL |
286 | If you don't know what to do here, say N. |
287 | ||
6695c85b | 288 | config X86_MPPARSE |
7a527688 JB |
289 | bool "Enable MPS table" if ACPI |
290 | default y | |
5ab74722 | 291 | depends on X86_LOCAL_APIC |
8f9ca475 | 292 | ---help--- |
6695c85b YL |
293 | For old smp systems that do not have proper acpi support. Newer systems |
294 | (esp with 64bit cpus) with acpi support, MADT and DSDT will override it | |
6695c85b | 295 | |
26f7ef14 YL |
296 | config X86_BIGSMP |
297 | bool "Support for big SMP systems with more than 8 CPUs" | |
298 | depends on X86_32 && SMP | |
8f9ca475 | 299 | ---help--- |
26f7ef14 | 300 | This option is needed for the systems that have more than 8 CPUs |
506f1d07 | 301 | |
8425091f | 302 | if X86_32 |
c5c606d9 RT |
303 | config X86_EXTENDED_PLATFORM |
304 | bool "Support for extended (non-PC) x86 platforms" | |
305 | default y | |
8f9ca475 | 306 | ---help--- |
06ac8346 IM |
307 | If you disable this option then the kernel will only support |
308 | standard PC platforms. (which covers the vast majority of | |
309 | systems out there.) | |
310 | ||
8425091f RT |
311 | If you enable this option then you'll be able to select support |
312 | for the following (non-PC) 32 bit x86 platforms: | |
313 | AMD Elan | |
314 | NUMAQ (IBM/Sequent) | |
315 | RDC R-321x SoC | |
316 | SGI 320/540 (Visual Workstation) | |
317 | Summit/EXA (IBM x440) | |
318 | Unisys ES7000 IA32 series | |
3f4110a4 | 319 | Moorestown MID devices |
06ac8346 IM |
320 | |
321 | If you have one of these systems, or if you want to build a | |
322 | generic distribution kernel, say Y here - otherwise say N. | |
8425091f | 323 | endif |
06ac8346 | 324 | |
8425091f RT |
325 | if X86_64 |
326 | config X86_EXTENDED_PLATFORM | |
327 | bool "Support for extended (non-PC) x86 platforms" | |
328 | default y | |
329 | ---help--- | |
330 | If you disable this option then the kernel will only support | |
331 | standard PC platforms. (which covers the vast majority of | |
332 | systems out there.) | |
333 | ||
334 | If you enable this option then you'll be able to select support | |
335 | for the following (non-PC) 64 bit x86 platforms: | |
336 | ScaleMP vSMP | |
337 | SGI Ultraviolet | |
338 | ||
339 | If you have one of these systems, or if you want to build a | |
340 | generic distribution kernel, say Y here - otherwise say N. | |
341 | endif | |
c5c606d9 RT |
342 | # This is an alphabetically sorted list of 64 bit extended platforms |
343 | # Please maintain the alphabetic order if and when there are additions | |
506f1d07 | 344 | |
c5c606d9 RT |
345 | config X86_VSMP |
346 | bool "ScaleMP vSMP" | |
03f1a17c | 347 | select PARAVIRT_GUEST |
c5c606d9 RT |
348 | select PARAVIRT |
349 | depends on X86_64 && PCI | |
350 | depends on X86_EXTENDED_PLATFORM | |
8f9ca475 | 351 | ---help--- |
c5c606d9 RT |
352 | Support for ScaleMP vSMP systems. Say 'Y' here if this kernel is |
353 | supposed to run on these EM64T-based machines. Only choose this option | |
354 | if you have one of these machines. | |
5e3a77e9 | 355 | |
03b48632 NP |
356 | config X86_UV |
357 | bool "SGI Ultraviolet" | |
358 | depends on X86_64 | |
c5c606d9 | 359 | depends on X86_EXTENDED_PLATFORM |
54c28d29 | 360 | depends on NUMA |
9d6c26e7 | 361 | depends on X86_X2APIC |
8f9ca475 | 362 | ---help--- |
03b48632 NP |
363 | This option is needed in order to support SGI Ultraviolet systems. |
364 | If you don't have one of these, you should say N here. | |
365 | ||
c5c606d9 RT |
366 | # Following is an alphabetically sorted list of 32 bit extended platforms |
367 | # Please maintain the alphabetic order if and when there are additions | |
506f1d07 SR |
368 | |
369 | config X86_ELAN | |
370 | bool "AMD Elan" | |
371 | depends on X86_32 | |
c5c606d9 | 372 | depends on X86_EXTENDED_PLATFORM |
8f9ca475 | 373 | ---help--- |
506f1d07 SR |
374 | Select this for an AMD Elan processor. |
375 | ||
376 | Do not use this option for K6/Athlon/Opteron processors! | |
377 | ||
378 | If unsure, choose "PC-compatible" instead. | |
379 | ||
c751e17b TG |
380 | config X86_INTEL_CE |
381 | bool "CE4100 TV platform" | |
382 | depends on PCI | |
383 | depends on PCI_GODIRECT | |
384 | depends on X86_32 | |
385 | depends on X86_EXTENDED_PLATFORM | |
37bc9f50 | 386 | select X86_REBOOTFIXUPS |
c751e17b TG |
387 | ---help--- |
388 | Select for the Intel CE media processor (CE4100) SOC. | |
389 | This option compiles in support for the CE4100 SOC for settop | |
390 | boxes and media devices. | |
391 | ||
3f4110a4 TG |
392 | config X86_MRST |
393 | bool "Moorestown MID platform" | |
4b2f3f7d JP |
394 | depends on PCI |
395 | depends on PCI_GOANY | |
3f4110a4 TG |
396 | depends on X86_32 |
397 | depends on X86_EXTENDED_PLATFORM | |
4b2f3f7d | 398 | depends on X86_IO_APIC |
bb24c471 | 399 | select APB_TIMER |
1da4b1c6 FT |
400 | select I2C |
401 | select SPI | |
b9fc71f4 | 402 | select INTEL_SCU_IPC |
ad02519a | 403 | select X86_PLATFORM_DEVICES |
3f4110a4 TG |
404 | ---help--- |
405 | Moorestown is Intel's Low Power Intel Architecture (LPIA) based Moblin | |
406 | Internet Device(MID) platform. Moorestown consists of two chips: | |
407 | Lincroft (CPU core, graphics, and memory controller) and Langwell IOH. | |
408 | Unlike standard x86 PCs, Moorestown does not have many legacy devices | |
409 | nor standard legacy replacement devices/features. e.g. Moorestown does | |
410 | not contain i8259, i8254, HPET, legacy BIOS, most of the io ports. | |
411 | ||
c5c606d9 RT |
412 | config X86_RDC321X |
413 | bool "RDC R-321x SoC" | |
506f1d07 | 414 | depends on X86_32 |
c5c606d9 RT |
415 | depends on X86_EXTENDED_PLATFORM |
416 | select M486 | |
417 | select X86_REBOOTFIXUPS | |
418 | ---help--- | |
419 | This option is needed for RDC R-321x system-on-chip, also known | |
420 | as R-8610-(G). | |
421 | If you don't have one of these chips, you should say N here. | |
422 | ||
e0c7ae37 | 423 | config X86_32_NON_STANDARD |
9c398017 IM |
424 | bool "Support non-standard 32-bit SMP architectures" |
425 | depends on X86_32 && SMP | |
c5c606d9 | 426 | depends on X86_EXTENDED_PLATFORM |
8f9ca475 IM |
427 | ---help--- |
428 | This option compiles in the NUMAQ, Summit, bigsmp, ES7000, default | |
d49c4288 YL |
429 | subarchitectures. It is intended for a generic binary kernel. |
430 | if you select them all, kernel will probe it one by one. and will | |
431 | fallback to default. | |
432 | ||
c5c606d9 | 433 | # Alphabetically sorted list of Non standard 32 bit platforms |
d49c4288 | 434 | |
506f1d07 SR |
435 | config X86_NUMAQ |
436 | bool "NUMAQ (IBM/Sequent)" | |
e0c7ae37 | 437 | depends on X86_32_NON_STANDARD |
a92d152e | 438 | depends on PCI |
506f1d07 | 439 | select NUMA |
9c398017 | 440 | select X86_MPPARSE |
8f9ca475 | 441 | ---help--- |
d49c4288 YL |
442 | This option is used for getting Linux to run on a NUMAQ (IBM/Sequent) |
443 | NUMA multiquad box. This changes the way that processors are | |
444 | bootstrapped, and uses Clustered Logical APIC addressing mode instead | |
445 | of Flat Logical. You will need a new lynxer.elf file to flash your | |
446 | firmware with - send email to <Martin.Bligh@us.ibm.com>. | |
506f1d07 | 447 | |
d949f36f | 448 | config X86_SUPPORTS_MEMORY_FAILURE |
6fc108a0 | 449 | def_bool y |
d949f36f LT |
450 | # MCE code calls memory_failure(): |
451 | depends on X86_MCE | |
452 | # On 32-bit this adds too big of NODES_SHIFT and we run out of page flags: | |
453 | depends on !X86_NUMAQ | |
454 | # On 32-bit SPARSEMEM adds too big of SECTIONS_WIDTH: | |
455 | depends on X86_64 || !SPARSEMEM | |
456 | select ARCH_SUPPORTS_MEMORY_FAILURE | |
d949f36f | 457 | |
1b84e1c8 IM |
458 | config X86_VISWS |
459 | bool "SGI 320/540 (Visual Workstation)" | |
c5c606d9 RT |
460 | depends on X86_32 && PCI && X86_MPPARSE && PCI_GODIRECT |
461 | depends on X86_32_NON_STANDARD | |
462 | ---help--- | |
1b84e1c8 IM |
463 | The SGI Visual Workstation series is an IA32-based workstation |
464 | based on SGI systems chips with some legacy PC hardware attached. | |
465 | ||
466 | Say Y here to create a kernel to run on the SGI 320 or 540. | |
467 | ||
468 | A kernel compiled for the Visual Workstation will run on general | |
469 | PCs as well. See <file:Documentation/sgi-visws.txt> for details. | |
470 | ||
9c398017 IM |
471 | config X86_SUMMIT |
472 | bool "Summit/EXA (IBM x440)" | |
e0c7ae37 | 473 | depends on X86_32_NON_STANDARD |
8f9ca475 | 474 | ---help--- |
9c398017 IM |
475 | This option is needed for IBM systems that use the Summit/EXA chipset. |
476 | In particular, it is needed for the x440. | |
1f972768 | 477 | |
9c398017 | 478 | config X86_ES7000 |
c5c606d9 | 479 | bool "Unisys ES7000 IA32 series" |
26f7ef14 | 480 | depends on X86_32_NON_STANDARD && X86_BIGSMP |
8f9ca475 | 481 | ---help--- |
9c398017 IM |
482 | Support for Unisys ES7000 systems. Say 'Y' here if this kernel is |
483 | supposed to run on an IA32-based Unisys ES7000 system. | |
484 | ||
ae1e9130 | 485 | config SCHED_OMIT_FRAME_POINTER |
3c2362e6 HH |
486 | def_bool y |
487 | prompt "Single-depth WCHAN output" | |
a87d0914 | 488 | depends on X86 |
8f9ca475 | 489 | ---help--- |
506f1d07 SR |
490 | Calculate simpler /proc/<PID>/wchan values. If this option |
491 | is disabled then wchan values will recurse back to the | |
492 | caller function. This provides more accurate wchan values, | |
493 | at the expense of slightly more scheduling overhead. | |
494 | ||
495 | If in doubt, say "Y". | |
496 | ||
506f1d07 SR |
497 | menuconfig PARAVIRT_GUEST |
498 | bool "Paravirtualized guest support" | |
8f9ca475 | 499 | ---help--- |
506f1d07 SR |
500 | Say Y here to get to see options related to running Linux under |
501 | various hypervisors. This option alone does not add any kernel code. | |
502 | ||
503 | If you say N, all options in this submenu will be skipped and disabled. | |
504 | ||
505 | if PARAVIRT_GUEST | |
506 | ||
507 | source "arch/x86/xen/Kconfig" | |
508 | ||
790c73f6 GOC |
509 | config KVM_CLOCK |
510 | bool "KVM paravirtualized clock" | |
511 | select PARAVIRT | |
f6e16d5a | 512 | select PARAVIRT_CLOCK |
8f9ca475 | 513 | ---help--- |
790c73f6 GOC |
514 | Turning on this option will allow you to run a paravirtualized clock |
515 | when running over the KVM hypervisor. Instead of relying on a PIT | |
516 | (or probably other) emulation by the underlying device model, the host | |
517 | provides the guest with timing infrastructure such as time of day, and | |
518 | system time | |
519 | ||
0cf1bfd2 MT |
520 | config KVM_GUEST |
521 | bool "KVM Guest support" | |
522 | select PARAVIRT | |
8f9ca475 IM |
523 | ---help--- |
524 | This option enables various optimizations for running under the KVM | |
525 | hypervisor. | |
0cf1bfd2 | 526 | |
506f1d07 SR |
527 | source "arch/x86/lguest/Kconfig" |
528 | ||
e61bd94a EPH |
529 | config PARAVIRT |
530 | bool "Enable paravirtualization code" | |
8f9ca475 | 531 | ---help--- |
e61bd94a EPH |
532 | This changes the kernel so it can modify itself when it is run |
533 | under a hypervisor, potentially improving performance significantly | |
534 | over full virtualization. However, when run without a hypervisor | |
535 | the kernel is theoretically slower and slightly larger. | |
536 | ||
b4ecc126 JF |
537 | config PARAVIRT_SPINLOCKS |
538 | bool "Paravirtualization layer for spinlocks" | |
539 | depends on PARAVIRT && SMP && EXPERIMENTAL | |
540 | ---help--- | |
541 | Paravirtualized spinlocks allow a pvops backend to replace the | |
542 | spinlock implementation with something virtualization-friendly | |
543 | (for example, block the virtual CPU rather than spinning). | |
544 | ||
545 | Unfortunately the downside is an up to 5% performance hit on | |
546 | native kernels, with various workloads. | |
547 | ||
548 | If you are unsure how to answer this question, answer N. | |
549 | ||
7af192c9 GH |
550 | config PARAVIRT_CLOCK |
551 | bool | |
7af192c9 | 552 | |
506f1d07 SR |
553 | endif |
554 | ||
97349135 | 555 | config PARAVIRT_DEBUG |
8f9ca475 IM |
556 | bool "paravirt-ops debugging" |
557 | depends on PARAVIRT && DEBUG_KERNEL | |
558 | ---help--- | |
559 | Enable to debug paravirt_ops internals. Specifically, BUG if | |
560 | a paravirt_op is missing when it is called. | |
97349135 | 561 | |
08677214 | 562 | config NO_BOOTMEM |
774ea0bc | 563 | def_bool y |
08677214 | 564 | |
03273184 YL |
565 | config MEMTEST |
566 | bool "Memtest" | |
8f9ca475 | 567 | ---help--- |
c64df707 | 568 | This option adds a kernel parameter 'memtest', which allows memtest |
03273184 | 569 | to be set. |
8f9ca475 IM |
570 | memtest=0, mean disabled; -- default |
571 | memtest=1, mean do 1 test pattern; | |
572 | ... | |
573 | memtest=4, mean do 4 test patterns. | |
aba3728c | 574 | If you are unsure how to answer this question, answer N. |
506f1d07 SR |
575 | |
576 | config X86_SUMMIT_NUMA | |
3c2362e6 | 577 | def_bool y |
e0c7ae37 | 578 | depends on X86_32 && NUMA && X86_32_NON_STANDARD |
506f1d07 SR |
579 | |
580 | config X86_CYCLONE_TIMER | |
3c2362e6 | 581 | def_bool y |
e0c7ae37 | 582 | depends on X86_32_NON_STANDARD |
506f1d07 | 583 | |
506f1d07 SR |
584 | source "arch/x86/Kconfig.cpu" |
585 | ||
586 | config HPET_TIMER | |
3c2362e6 | 587 | def_bool X86_64 |
506f1d07 | 588 | prompt "HPET Timer Support" if X86_32 |
8f9ca475 IM |
589 | ---help--- |
590 | Use the IA-PC HPET (High Precision Event Timer) to manage | |
591 | time in preference to the PIT and RTC, if a HPET is | |
592 | present. | |
593 | HPET is the next generation timer replacing legacy 8254s. | |
594 | The HPET provides a stable time base on SMP | |
595 | systems, unlike the TSC, but it is more expensive to access, | |
596 | as it is off-chip. You can find the HPET spec at | |
597 | <http://www.intel.com/hardwaredesign/hpetspec_1.pdf>. | |
506f1d07 | 598 | |
8f9ca475 IM |
599 | You can safely choose Y here. However, HPET will only be |
600 | activated if the platform and the BIOS support this feature. | |
601 | Otherwise the 8254 will be used for timing services. | |
506f1d07 | 602 | |
8f9ca475 | 603 | Choose N to continue using the legacy 8254 timer. |
506f1d07 SR |
604 | |
605 | config HPET_EMULATE_RTC | |
3c2362e6 | 606 | def_bool y |
9d8af78b | 607 | depends on HPET_TIMER && (RTC=y || RTC=m || RTC_DRV_CMOS=m || RTC_DRV_CMOS=y) |
506f1d07 | 608 | |
bb24c471 JP |
609 | config APB_TIMER |
610 | def_bool y if MRST | |
611 | prompt "Langwell APB Timer Support" if X86_MRST | |
612 | help | |
613 | APB timer is the replacement for 8254, HPET on X86 MID platforms. | |
614 | The APBT provides a stable time base on SMP | |
615 | systems, unlike the TSC, but it is more expensive to access, | |
616 | as it is off-chip. APB timers are always running regardless of CPU | |
617 | C states, they are used as per CPU clockevent device when possible. | |
618 | ||
506f1d07 SR |
619 | # Mark as embedded because too many people got it wrong. |
620 | # The code disables itself when not needed. | |
7ae9392c TP |
621 | config DMI |
622 | default y | |
623 | bool "Enable DMI scanning" if EMBEDDED | |
8f9ca475 | 624 | ---help--- |
7ae9392c TP |
625 | Enabled scanning of DMI to identify machine quirks. Say Y |
626 | here unless you have verified that your setup is not | |
627 | affected by entries in the DMI blacklist. Required by PNP | |
628 | BIOS code. | |
629 | ||
506f1d07 SR |
630 | config GART_IOMMU |
631 | bool "GART IOMMU support" if EMBEDDED | |
632 | default y | |
633 | select SWIOTLB | |
23ac4ae8 | 634 | depends on X86_64 && PCI && AMD_NB |
8f9ca475 | 635 | ---help--- |
506f1d07 SR |
636 | Support for full DMA access of devices with 32bit memory access only |
637 | on systems with more than 3GB. This is usually needed for USB, | |
638 | sound, many IDE/SATA chipsets and some other devices. | |
639 | Provides a driver for the AMD Athlon64/Opteron/Turion/Sempron GART | |
640 | based hardware IOMMU and a software bounce buffer based IOMMU used | |
641 | on Intel systems and as fallback. | |
642 | The code is only active when needed (enough memory and limited | |
643 | device) unless CONFIG_IOMMU_DEBUG or iommu=force is specified | |
644 | too. | |
645 | ||
646 | config CALGARY_IOMMU | |
647 | bool "IBM Calgary IOMMU support" | |
648 | select SWIOTLB | |
649 | depends on X86_64 && PCI && EXPERIMENTAL | |
8f9ca475 | 650 | ---help--- |
506f1d07 SR |
651 | Support for hardware IOMMUs in IBM's xSeries x366 and x460 |
652 | systems. Needed to run systems with more than 3GB of memory | |
653 | properly with 32-bit PCI devices that do not support DAC | |
654 | (Double Address Cycle). Calgary also supports bus level | |
655 | isolation, where all DMAs pass through the IOMMU. This | |
656 | prevents them from going anywhere except their intended | |
657 | destination. This catches hard-to-find kernel bugs and | |
658 | mis-behaving drivers and devices that do not use the DMA-API | |
659 | properly to set up their DMA buffers. The IOMMU can be | |
660 | turned off at boot time with the iommu=off parameter. | |
661 | Normally the kernel will make the right choice by itself. | |
662 | If unsure, say Y. | |
663 | ||
664 | config CALGARY_IOMMU_ENABLED_BY_DEFAULT | |
3c2362e6 HH |
665 | def_bool y |
666 | prompt "Should Calgary be enabled by default?" | |
506f1d07 | 667 | depends on CALGARY_IOMMU |
8f9ca475 | 668 | ---help--- |
506f1d07 SR |
669 | Should Calgary be enabled by default? if you choose 'y', Calgary |
670 | will be used (if it exists). If you choose 'n', Calgary will not be | |
671 | used even if it exists. If you choose 'n' and would like to use | |
672 | Calgary anyway, pass 'iommu=calgary' on the kernel command line. | |
673 | If unsure, say Y. | |
674 | ||
2b188723 JR |
675 | config AMD_IOMMU |
676 | bool "AMD IOMMU support" | |
07c40e8a | 677 | select SWIOTLB |
a80dc3e0 | 678 | select PCI_MSI |
24d2ba0a | 679 | depends on X86_64 && PCI && ACPI |
8f9ca475 | 680 | ---help--- |
18d22200 JR |
681 | With this option you can enable support for AMD IOMMU hardware in |
682 | your system. An IOMMU is a hardware component which provides | |
683 | remapping of DMA memory accesses from devices. With an AMD IOMMU you | |
684 | can isolate the the DMA memory of different devices and protect the | |
685 | system from misbehaving device drivers or hardware. | |
686 | ||
687 | You can find out if your system has an AMD IOMMU if you look into | |
688 | your BIOS for an option to enable it or if you have an IVRS ACPI | |
689 | table. | |
2b188723 | 690 | |
2e117604 JR |
691 | config AMD_IOMMU_STATS |
692 | bool "Export AMD IOMMU statistics to debugfs" | |
693 | depends on AMD_IOMMU | |
694 | select DEBUG_FS | |
8f9ca475 | 695 | ---help--- |
2e117604 JR |
696 | This option enables code in the AMD IOMMU driver to collect various |
697 | statistics about whats happening in the driver and exports that | |
698 | information to userspace via debugfs. | |
699 | If unsure, say N. | |
700 | ||
506f1d07 SR |
701 | # need this always selected by IOMMU for the VIA workaround |
702 | config SWIOTLB | |
a1afd01c | 703 | def_bool y if X86_64 |
8f9ca475 | 704 | ---help--- |
506f1d07 SR |
705 | Support for software bounce buffers used on x86-64 systems |
706 | which don't have a hardware IOMMU (e.g. the current generation | |
707 | of Intel's x86-64 CPUs). Using this PCI devices which can only | |
708 | access 32-bits of memory can be used on systems with more than | |
709 | 3 GB of memory. If unsure, say Y. | |
710 | ||
a8522509 | 711 | config IOMMU_HELPER |
18b743dc | 712 | def_bool (CALGARY_IOMMU || GART_IOMMU || SWIOTLB || AMD_IOMMU) |
d25e26b6 | 713 | |
1aaf1183 JR |
714 | config IOMMU_API |
715 | def_bool (AMD_IOMMU || DMAR) | |
716 | ||
1184dc2f | 717 | config MAXSMP |
ddb0c5a6 | 718 | bool "Enable Maximum number of SMP Processors and NUMA Nodes" |
36f5101a MT |
719 | depends on X86_64 && SMP && DEBUG_KERNEL && EXPERIMENTAL |
720 | select CPUMASK_OFFSTACK | |
8f9ca475 | 721 | ---help--- |
ddb0c5a6 | 722 | Enable maximum number of CPUS and NUMA Nodes for this architecture. |
1184dc2f | 723 | If unsure, say N. |
506f1d07 SR |
724 | |
725 | config NR_CPUS | |
36f5101a | 726 | int "Maximum number of CPUs" if SMP && !MAXSMP |
2a3313f4 | 727 | range 2 8 if SMP && X86_32 && !X86_BIGSMP |
36f5101a | 728 | range 2 512 if SMP && !MAXSMP |
78637a97 | 729 | default "1" if !SMP |
d25e26b6 | 730 | default "4096" if MAXSMP |
78637a97 MT |
731 | default "32" if SMP && (X86_NUMAQ || X86_SUMMIT || X86_BIGSMP || X86_ES7000) |
732 | default "8" if SMP | |
8f9ca475 | 733 | ---help--- |
506f1d07 | 734 | This allows you to specify the maximum number of CPUs which this |
d25e26b6 | 735 | kernel will support. The maximum supported value is 512 and the |
506f1d07 SR |
736 | minimum value which makes sense is 2. |
737 | ||
738 | This is purely to save memory - each supported CPU adds | |
739 | approximately eight kilobytes to the kernel image. | |
740 | ||
741 | config SCHED_SMT | |
742 | bool "SMT (Hyperthreading) scheduler support" | |
b089c12b | 743 | depends on X86_HT |
8f9ca475 | 744 | ---help--- |
506f1d07 SR |
745 | SMT scheduler support improves the CPU scheduler's decision making |
746 | when dealing with Intel Pentium 4 chips with HyperThreading at a | |
747 | cost of slightly increased overhead in some places. If unsure say | |
748 | N here. | |
749 | ||
750 | config SCHED_MC | |
3c2362e6 HH |
751 | def_bool y |
752 | prompt "Multi-core scheduler support" | |
b089c12b | 753 | depends on X86_HT |
8f9ca475 | 754 | ---help--- |
506f1d07 SR |
755 | Multi-core scheduler support improves the CPU scheduler's decision |
756 | making when dealing with multi-core CPU chips at a cost of slightly | |
757 | increased overhead in some places. If unsure say N here. | |
758 | ||
e82b8e4e VP |
759 | config IRQ_TIME_ACCOUNTING |
760 | bool "Fine granularity task level IRQ time accounting" | |
761 | default n | |
762 | ---help--- | |
763 | Select this option to enable fine granularity task irq time | |
764 | accounting. This is done by reading a timestamp on each | |
765 | transitions between softirq and hardirq state, so there can be a | |
766 | small performance impact. | |
767 | ||
768 | If in doubt, say N here. | |
769 | ||
506f1d07 SR |
770 | source "kernel/Kconfig.preempt" |
771 | ||
772 | config X86_UP_APIC | |
773 | bool "Local APIC support on uniprocessors" | |
e0c7ae37 | 774 | depends on X86_32 && !SMP && !X86_32_NON_STANDARD |
8f9ca475 | 775 | ---help--- |
506f1d07 SR |
776 | A local APIC (Advanced Programmable Interrupt Controller) is an |
777 | integrated interrupt controller in the CPU. If you have a single-CPU | |
778 | system which has a processor with a local APIC, you can say Y here to | |
779 | enable and use it. If you say Y here even though your machine doesn't | |
780 | have a local APIC, then the kernel will still run with no slowdown at | |
781 | all. The local APIC supports CPU-generated self-interrupts (timer, | |
782 | performance counters), and the NMI watchdog which detects hard | |
783 | lockups. | |
784 | ||
785 | config X86_UP_IOAPIC | |
786 | bool "IO-APIC support on uniprocessors" | |
787 | depends on X86_UP_APIC | |
8f9ca475 | 788 | ---help--- |
506f1d07 SR |
789 | An IO-APIC (I/O Advanced Programmable Interrupt Controller) is an |
790 | SMP-capable replacement for PC-style interrupt controllers. Most | |
791 | SMP systems and many recent uniprocessor systems have one. | |
792 | ||
793 | If you have a single-CPU system with an IO-APIC, you can say Y here | |
794 | to use it. If you say Y here even though your machine doesn't have | |
795 | an IO-APIC, then the kernel will still run with no slowdown at all. | |
796 | ||
797 | config X86_LOCAL_APIC | |
3c2362e6 | 798 | def_bool y |
e0c7ae37 | 799 | depends on X86_64 || SMP || X86_32_NON_STANDARD || X86_UP_APIC |
506f1d07 SR |
800 | |
801 | config X86_IO_APIC | |
3c2362e6 | 802 | def_bool y |
e0c7ae37 | 803 | depends on X86_64 || SMP || X86_32_NON_STANDARD || X86_UP_APIC |
506f1d07 SR |
804 | |
805 | config X86_VISWS_APIC | |
3c2362e6 | 806 | def_bool y |
506f1d07 | 807 | depends on X86_32 && X86_VISWS |
506f1d07 | 808 | |
41b9eb26 SA |
809 | config X86_REROUTE_FOR_BROKEN_BOOT_IRQS |
810 | bool "Reroute for broken boot IRQs" | |
41b9eb26 | 811 | depends on X86_IO_APIC |
8f9ca475 | 812 | ---help--- |
41b9eb26 SA |
813 | This option enables a workaround that fixes a source of |
814 | spurious interrupts. This is recommended when threaded | |
815 | interrupt handling is used on systems where the generation of | |
816 | superfluous "boot interrupts" cannot be disabled. | |
817 | ||
818 | Some chipsets generate a legacy INTx "boot IRQ" when the IRQ | |
819 | entry in the chipset's IO-APIC is masked (as, e.g. the RT | |
820 | kernel does during interrupt handling). On chipsets where this | |
821 | boot IRQ generation cannot be disabled, this workaround keeps | |
822 | the original IRQ line masked so that only the equivalent "boot | |
823 | IRQ" is delivered to the CPUs. The workaround also tells the | |
824 | kernel to set up the IRQ handler on the boot IRQ line. In this | |
825 | way only one interrupt is delivered to the kernel. Otherwise | |
826 | the spurious second interrupt may cause the kernel to bring | |
827 | down (vital) interrupt lines. | |
828 | ||
829 | Only affects "broken" chipsets. Interrupt sharing may be | |
830 | increased on these systems. | |
831 | ||
506f1d07 | 832 | config X86_MCE |
bab9bc65 | 833 | bool "Machine Check / overheating reporting" |
506f1d07 | 834 | ---help--- |
bab9bc65 AK |
835 | Machine Check support allows the processor to notify the |
836 | kernel if it detects a problem (e.g. overheating, data corruption). | |
506f1d07 | 837 | The action the kernel takes depends on the severity of the problem, |
bab9bc65 | 838 | ranging from warning messages to halting the machine. |
4efc0670 | 839 | |
506f1d07 | 840 | config X86_MCE_INTEL |
3c2362e6 HH |
841 | def_bool y |
842 | prompt "Intel MCE features" | |
c1ebf835 | 843 | depends on X86_MCE && X86_LOCAL_APIC |
8f9ca475 | 844 | ---help--- |
506f1d07 SR |
845 | Additional support for intel specific MCE features such as |
846 | the thermal monitor. | |
847 | ||
848 | config X86_MCE_AMD | |
3c2362e6 HH |
849 | def_bool y |
850 | prompt "AMD MCE features" | |
c1ebf835 | 851 | depends on X86_MCE && X86_LOCAL_APIC |
8f9ca475 | 852 | ---help--- |
506f1d07 SR |
853 | Additional support for AMD specific MCE features such as |
854 | the DRAM Error Threshold. | |
855 | ||
4efc0670 | 856 | config X86_ANCIENT_MCE |
6fc108a0 | 857 | bool "Support for old Pentium 5 / WinChip machine checks" |
c31d9633 | 858 | depends on X86_32 && X86_MCE |
cd13adcc HS |
859 | ---help--- |
860 | Include support for machine check handling on old Pentium 5 or WinChip | |
861 | systems. These typically need to be enabled explicitely on the command | |
862 | line. | |
4efc0670 | 863 | |
b2762686 AK |
864 | config X86_MCE_THRESHOLD |
865 | depends on X86_MCE_AMD || X86_MCE_INTEL | |
6fc108a0 | 866 | def_bool y |
b2762686 | 867 | |
ea149b36 | 868 | config X86_MCE_INJECT |
c1ebf835 | 869 | depends on X86_MCE |
ea149b36 AK |
870 | tristate "Machine check injector support" |
871 | ---help--- | |
872 | Provide support for injecting machine checks for testing purposes. | |
873 | If you don't know what a machine check is and you don't do kernel | |
874 | QA it is safe to say n. | |
875 | ||
4efc0670 AK |
876 | config X86_THERMAL_VECTOR |
877 | def_bool y | |
5bb38adc | 878 | depends on X86_MCE_INTEL |
4efc0670 | 879 | |
506f1d07 SR |
880 | config VM86 |
881 | bool "Enable VM86 support" if EMBEDDED | |
882 | default y | |
883 | depends on X86_32 | |
8f9ca475 IM |
884 | ---help--- |
885 | This option is required by programs like DOSEMU to run 16-bit legacy | |
506f1d07 | 886 | code on X86 processors. It also may be needed by software like |
8f9ca475 IM |
887 | XFree86 to initialize some video cards via BIOS. Disabling this |
888 | option saves about 6k. | |
506f1d07 SR |
889 | |
890 | config TOSHIBA | |
891 | tristate "Toshiba Laptop support" | |
892 | depends on X86_32 | |
893 | ---help--- | |
894 | This adds a driver to safely access the System Management Mode of | |
895 | the CPU on Toshiba portables with a genuine Toshiba BIOS. It does | |
896 | not work on models with a Phoenix BIOS. The System Management Mode | |
897 | is used to set the BIOS and power saving options on Toshiba portables. | |
898 | ||
899 | For information on utilities to make use of this driver see the | |
900 | Toshiba Linux utilities web site at: | |
901 | <http://www.buzzard.org.uk/toshiba/>. | |
902 | ||
903 | Say Y if you intend to run this kernel on a Toshiba portable. | |
904 | Say N otherwise. | |
905 | ||
906 | config I8K | |
907 | tristate "Dell laptop support" | |
506f1d07 SR |
908 | ---help--- |
909 | This adds a driver to safely access the System Management Mode | |
910 | of the CPU on the Dell Inspiron 8000. The System Management Mode | |
911 | is used to read cpu temperature and cooling fan status and to | |
912 | control the fans on the I8K portables. | |
913 | ||
914 | This driver has been tested only on the Inspiron 8000 but it may | |
915 | also work with other Dell laptops. You can force loading on other | |
916 | models by passing the parameter `force=1' to the module. Use at | |
917 | your own risk. | |
918 | ||
919 | For information on utilities to make use of this driver see the | |
920 | I8K Linux utilities web site at: | |
921 | <http://people.debian.org/~dz/i8k/> | |
922 | ||
923 | Say Y if you intend to run this kernel on a Dell Inspiron 8000. | |
924 | Say N otherwise. | |
925 | ||
926 | config X86_REBOOTFIXUPS | |
9ba16087 JB |
927 | bool "Enable X86 board specific fixups for reboot" |
928 | depends on X86_32 | |
506f1d07 SR |
929 | ---help--- |
930 | This enables chipset and/or board specific fixups to be done | |
931 | in order to get reboot to work correctly. This is only needed on | |
932 | some combinations of hardware and BIOS. The symptom, for which | |
933 | this config is intended, is when reboot ends with a stalled/hung | |
934 | system. | |
935 | ||
936 | Currently, the only fixup is for the Geode machines using | |
5e3a77e9 | 937 | CS5530A and CS5536 chipsets and the RDC R-321x SoC. |
506f1d07 SR |
938 | |
939 | Say Y if you want to enable the fixup. Currently, it's safe to | |
940 | enable this option even if you don't need it. | |
941 | Say N otherwise. | |
942 | ||
943 | config MICROCODE | |
8d86f390 | 944 | tristate "/dev/cpu/microcode - microcode support" |
506f1d07 SR |
945 | select FW_LOADER |
946 | ---help--- | |
947 | If you say Y here, you will be able to update the microcode on | |
80cc9f10 PO |
948 | certain Intel and AMD processors. The Intel support is for the |
949 | IA32 family, e.g. Pentium Pro, Pentium II, Pentium III, | |
950 | Pentium 4, Xeon etc. The AMD support is for family 0x10 and | |
951 | 0x11 processors, e.g. Opteron, Phenom and Turion 64 Ultra. | |
952 | You will obviously need the actual microcode binary data itself | |
953 | which is not shipped with the Linux kernel. | |
506f1d07 | 954 | |
8d86f390 PO |
955 | This option selects the general module only, you need to select |
956 | at least one vendor specific module as well. | |
506f1d07 SR |
957 | |
958 | To compile this driver as a module, choose M here: the | |
959 | module will be called microcode. | |
960 | ||
8d86f390 | 961 | config MICROCODE_INTEL |
8f9ca475 IM |
962 | bool "Intel microcode patch loading support" |
963 | depends on MICROCODE | |
964 | default MICROCODE | |
965 | select FW_LOADER | |
966 | ---help--- | |
967 | This options enables microcode patch loading support for Intel | |
968 | processors. | |
969 | ||
970 | For latest news and information on obtaining all the required | |
971 | Intel ingredients for this driver, check: | |
972 | <http://www.urbanmyth.org/microcode/>. | |
8d86f390 | 973 | |
80cc9f10 | 974 | config MICROCODE_AMD |
8f9ca475 IM |
975 | bool "AMD microcode patch loading support" |
976 | depends on MICROCODE | |
977 | select FW_LOADER | |
978 | ---help--- | |
979 | If you select this option, microcode patch loading support for AMD | |
980 | processors will be enabled. | |
80cc9f10 | 981 | |
8f9ca475 | 982 | config MICROCODE_OLD_INTERFACE |
3c2362e6 | 983 | def_bool y |
506f1d07 | 984 | depends on MICROCODE |
506f1d07 SR |
985 | |
986 | config X86_MSR | |
987 | tristate "/dev/cpu/*/msr - Model-specific register support" | |
8f9ca475 | 988 | ---help--- |
506f1d07 SR |
989 | This device gives privileged processes access to the x86 |
990 | Model-Specific Registers (MSRs). It is a character device with | |
991 | major 202 and minors 0 to 31 for /dev/cpu/0/msr to /dev/cpu/31/msr. | |
992 | MSR accesses are directed to a specific CPU on multi-processor | |
993 | systems. | |
994 | ||
995 | config X86_CPUID | |
996 | tristate "/dev/cpu/*/cpuid - CPU information support" | |
8f9ca475 | 997 | ---help--- |
506f1d07 SR |
998 | This device gives processes access to the x86 CPUID instruction to |
999 | be executed on a specific processor. It is a character device | |
1000 | with major 203 and minors 0 to 31 for /dev/cpu/0/cpuid to | |
1001 | /dev/cpu/31/cpuid. | |
1002 | ||
1003 | choice | |
1004 | prompt "High Memory Support" | |
506f1d07 | 1005 | default HIGHMEM64G if X86_NUMAQ |
6fc108a0 | 1006 | default HIGHMEM4G |
506f1d07 SR |
1007 | depends on X86_32 |
1008 | ||
1009 | config NOHIGHMEM | |
1010 | bool "off" | |
1011 | depends on !X86_NUMAQ | |
1012 | ---help--- | |
1013 | Linux can use up to 64 Gigabytes of physical memory on x86 systems. | |
1014 | However, the address space of 32-bit x86 processors is only 4 | |
1015 | Gigabytes large. That means that, if you have a large amount of | |
1016 | physical memory, not all of it can be "permanently mapped" by the | |
1017 | kernel. The physical memory that's not permanently mapped is called | |
1018 | "high memory". | |
1019 | ||
1020 | If you are compiling a kernel which will never run on a machine with | |
1021 | more than 1 Gigabyte total physical RAM, answer "off" here (default | |
1022 | choice and suitable for most users). This will result in a "3GB/1GB" | |
1023 | split: 3GB are mapped so that each process sees a 3GB virtual memory | |
1024 | space and the remaining part of the 4GB virtual memory space is used | |
1025 | by the kernel to permanently map as much physical memory as | |
1026 | possible. | |
1027 | ||
1028 | If the machine has between 1 and 4 Gigabytes physical RAM, then | |
1029 | answer "4GB" here. | |
1030 | ||
1031 | If more than 4 Gigabytes is used then answer "64GB" here. This | |
1032 | selection turns Intel PAE (Physical Address Extension) mode on. | |
1033 | PAE implements 3-level paging on IA32 processors. PAE is fully | |
1034 | supported by Linux, PAE mode is implemented on all recent Intel | |
1035 | processors (Pentium Pro and better). NOTE: If you say "64GB" here, | |
1036 | then the kernel will not boot on CPUs that don't support PAE! | |
1037 | ||
1038 | The actual amount of total physical memory will either be | |
1039 | auto detected or can be forced by using a kernel command line option | |
1040 | such as "mem=256M". (Try "man bootparam" or see the documentation of | |
1041 | your boot loader (lilo or loadlin) about how to pass options to the | |
1042 | kernel at boot time.) | |
1043 | ||
1044 | If unsure, say "off". | |
1045 | ||
1046 | config HIGHMEM4G | |
1047 | bool "4GB" | |
1048 | depends on !X86_NUMAQ | |
8f9ca475 | 1049 | ---help--- |
506f1d07 SR |
1050 | Select this if you have a 32-bit processor and between 1 and 4 |
1051 | gigabytes of physical RAM. | |
1052 | ||
1053 | config HIGHMEM64G | |
1054 | bool "64GB" | |
1055 | depends on !M386 && !M486 | |
1056 | select X86_PAE | |
8f9ca475 | 1057 | ---help--- |
506f1d07 SR |
1058 | Select this if you have a 32-bit processor and more than 4 |
1059 | gigabytes of physical RAM. | |
1060 | ||
1061 | endchoice | |
1062 | ||
1063 | choice | |
1064 | depends on EXPERIMENTAL | |
1065 | prompt "Memory split" if EMBEDDED | |
1066 | default VMSPLIT_3G | |
1067 | depends on X86_32 | |
8f9ca475 | 1068 | ---help--- |
506f1d07 SR |
1069 | Select the desired split between kernel and user memory. |
1070 | ||
1071 | If the address range available to the kernel is less than the | |
1072 | physical memory installed, the remaining memory will be available | |
1073 | as "high memory". Accessing high memory is a little more costly | |
1074 | than low memory, as it needs to be mapped into the kernel first. | |
1075 | Note that increasing the kernel address space limits the range | |
1076 | available to user programs, making the address space there | |
1077 | tighter. Selecting anything other than the default 3G/1G split | |
1078 | will also likely make your kernel incompatible with binary-only | |
1079 | kernel modules. | |
1080 | ||
1081 | If you are not absolutely sure what you are doing, leave this | |
1082 | option alone! | |
1083 | ||
1084 | config VMSPLIT_3G | |
1085 | bool "3G/1G user/kernel split" | |
1086 | config VMSPLIT_3G_OPT | |
1087 | depends on !X86_PAE | |
1088 | bool "3G/1G user/kernel split (for full 1G low memory)" | |
1089 | config VMSPLIT_2G | |
1090 | bool "2G/2G user/kernel split" | |
1091 | config VMSPLIT_2G_OPT | |
1092 | depends on !X86_PAE | |
1093 | bool "2G/2G user/kernel split (for full 2G low memory)" | |
1094 | config VMSPLIT_1G | |
1095 | bool "1G/3G user/kernel split" | |
1096 | endchoice | |
1097 | ||
1098 | config PAGE_OFFSET | |
1099 | hex | |
1100 | default 0xB0000000 if VMSPLIT_3G_OPT | |
1101 | default 0x80000000 if VMSPLIT_2G | |
1102 | default 0x78000000 if VMSPLIT_2G_OPT | |
1103 | default 0x40000000 if VMSPLIT_1G | |
1104 | default 0xC0000000 | |
1105 | depends on X86_32 | |
1106 | ||
1107 | config HIGHMEM | |
3c2362e6 | 1108 | def_bool y |
506f1d07 | 1109 | depends on X86_32 && (HIGHMEM64G || HIGHMEM4G) |
506f1d07 SR |
1110 | |
1111 | config X86_PAE | |
9ba16087 | 1112 | bool "PAE (Physical Address Extension) Support" |
506f1d07 | 1113 | depends on X86_32 && !HIGHMEM4G |
8f9ca475 | 1114 | ---help--- |
506f1d07 SR |
1115 | PAE is required for NX support, and furthermore enables |
1116 | larger swapspace support for non-overcommit purposes. It | |
1117 | has the cost of more pagetable lookup overhead, and also | |
1118 | consumes more pagetable space per process. | |
1119 | ||
600715dc | 1120 | config ARCH_PHYS_ADDR_T_64BIT |
8f9ca475 | 1121 | def_bool X86_64 || X86_PAE |
600715dc | 1122 | |
66f2b061 FT |
1123 | config ARCH_DMA_ADDR_T_64BIT |
1124 | def_bool X86_64 || HIGHMEM64G | |
1125 | ||
9e899816 NP |
1126 | config DIRECT_GBPAGES |
1127 | bool "Enable 1GB pages for kernel pagetables" if EMBEDDED | |
1128 | default y | |
1129 | depends on X86_64 | |
8f9ca475 | 1130 | ---help--- |
9e899816 NP |
1131 | Allow the kernel linear mapping to use 1GB pages on CPUs that |
1132 | support it. This can improve the kernel's performance a tiny bit by | |
1133 | reducing TLB pressure. If in doubt, say "Y". | |
1134 | ||
506f1d07 SR |
1135 | # Common NUMA Features |
1136 | config NUMA | |
fd51b2d7 | 1137 | bool "Numa Memory Allocation and Scheduler Support" |
506f1d07 | 1138 | depends on SMP |
604d2055 | 1139 | depends on X86_64 || (X86_32 && HIGHMEM64G && (X86_NUMAQ || X86_BIGSMP || X86_SUMMIT && ACPI) && EXPERIMENTAL) |
0699eae1 | 1140 | default y if (X86_NUMAQ || X86_SUMMIT || X86_BIGSMP) |
8f9ca475 | 1141 | ---help--- |
506f1d07 | 1142 | Enable NUMA (Non Uniform Memory Access) support. |
fd51b2d7 | 1143 | |
506f1d07 SR |
1144 | The kernel will try to allocate memory used by a CPU on the |
1145 | local memory controller of the CPU and add some more | |
1146 | NUMA awareness to the kernel. | |
1147 | ||
c280ea5e | 1148 | For 64-bit this is recommended if the system is Intel Core i7 |
fd51b2d7 KM |
1149 | (or later), AMD Opteron, or EM64T NUMA. |
1150 | ||
1151 | For 32-bit this is only needed on (rare) 32-bit-only platforms | |
1152 | that support NUMA topologies, such as NUMAQ / Summit, or if you | |
1153 | boot a 32-bit kernel on a 64-bit NUMA platform. | |
1154 | ||
1155 | Otherwise, you should say N. | |
506f1d07 SR |
1156 | |
1157 | comment "NUMA (Summit) requires SMP, 64GB highmem support, ACPI" | |
1158 | depends on X86_32 && X86_SUMMIT && (!HIGHMEM64G || !ACPI) | |
1159 | ||
1160 | config K8_NUMA | |
3c2362e6 HH |
1161 | def_bool y |
1162 | prompt "Old style AMD Opteron NUMA detection" | |
1163 | depends on X86_64 && NUMA && PCI | |
8f9ca475 IM |
1164 | ---help--- |
1165 | Enable K8 NUMA node topology detection. You should say Y here if | |
1166 | you have a multi processor AMD K8 system. This uses an old | |
1167 | method to read the NUMA configuration directly from the builtin | |
1168 | Northbridge of Opteron. It is recommended to use X86_64_ACPI_NUMA | |
1169 | instead, which also takes priority if both are compiled in. | |
506f1d07 SR |
1170 | |
1171 | config X86_64_ACPI_NUMA | |
3c2362e6 HH |
1172 | def_bool y |
1173 | prompt "ACPI NUMA detection" | |
506f1d07 SR |
1174 | depends on X86_64 && NUMA && ACPI && PCI |
1175 | select ACPI_NUMA | |
8f9ca475 | 1176 | ---help--- |
506f1d07 SR |
1177 | Enable ACPI SRAT based node topology detection. |
1178 | ||
6ec6e0d9 SS |
1179 | # Some NUMA nodes have memory ranges that span |
1180 | # other nodes. Even though a pfn is valid and | |
1181 | # between a node's start and end pfns, it may not | |
1182 | # reside on that node. See memmap_init_zone() | |
1183 | # for details. | |
1184 | config NODES_SPAN_OTHER_NODES | |
1185 | def_bool y | |
1186 | depends on X86_64_ACPI_NUMA | |
1187 | ||
506f1d07 SR |
1188 | config NUMA_EMU |
1189 | bool "NUMA emulation" | |
1190 | depends on X86_64 && NUMA | |
8f9ca475 | 1191 | ---help--- |
506f1d07 SR |
1192 | Enable NUMA emulation. A flat machine will be split |
1193 | into virtual nodes when booted with "numa=fake=N", where N is the | |
1194 | number of nodes. This is only useful for debugging. | |
1195 | ||
1196 | config NODES_SHIFT | |
d25e26b6 | 1197 | int "Maximum NUMA Nodes (as a power of 2)" if !MAXSMP |
51591e31 DR |
1198 | range 1 10 |
1199 | default "10" if MAXSMP | |
506f1d07 SR |
1200 | default "6" if X86_64 |
1201 | default "4" if X86_NUMAQ | |
1202 | default "3" | |
1203 | depends on NEED_MULTIPLE_NODES | |
8f9ca475 | 1204 | ---help--- |
1184dc2f | 1205 | Specify the maximum number of NUMA Nodes available on the target |
692105b8 | 1206 | system. Increases memory reserved to accommodate various tables. |
506f1d07 | 1207 | |
c1329375 | 1208 | config HAVE_ARCH_BOOTMEM |
3c2362e6 | 1209 | def_bool y |
506f1d07 | 1210 | depends on X86_32 && NUMA |
506f1d07 SR |
1211 | |
1212 | config ARCH_HAVE_MEMORY_PRESENT | |
3c2362e6 | 1213 | def_bool y |
506f1d07 | 1214 | depends on X86_32 && DISCONTIGMEM |
506f1d07 SR |
1215 | |
1216 | config NEED_NODE_MEMMAP_SIZE | |
3c2362e6 | 1217 | def_bool y |
506f1d07 | 1218 | depends on X86_32 && (DISCONTIGMEM || SPARSEMEM) |
506f1d07 SR |
1219 | |
1220 | config HAVE_ARCH_ALLOC_REMAP | |
3c2362e6 | 1221 | def_bool y |
506f1d07 | 1222 | depends on X86_32 && NUMA |
506f1d07 SR |
1223 | |
1224 | config ARCH_FLATMEM_ENABLE | |
1225 | def_bool y | |
99809963 | 1226 | depends on X86_32 && ARCH_SELECT_MEMORY_MODEL && !NUMA |
506f1d07 SR |
1227 | |
1228 | config ARCH_DISCONTIGMEM_ENABLE | |
1229 | def_bool y | |
b263295d | 1230 | depends on NUMA && X86_32 |
506f1d07 SR |
1231 | |
1232 | config ARCH_DISCONTIGMEM_DEFAULT | |
1233 | def_bool y | |
b263295d CL |
1234 | depends on NUMA && X86_32 |
1235 | ||
9492587c KH |
1236 | config ARCH_PROC_KCORE_TEXT |
1237 | def_bool y | |
1238 | depends on X86_64 && PROC_KCORE | |
1239 | ||
b263295d CL |
1240 | config ARCH_SPARSEMEM_DEFAULT |
1241 | def_bool y | |
1242 | depends on X86_64 | |
506f1d07 SR |
1243 | |
1244 | config ARCH_SPARSEMEM_ENABLE | |
1245 | def_bool y | |
4272ebfb | 1246 | depends on X86_64 || NUMA || (EXPERIMENTAL && X86_32) || X86_32_NON_STANDARD |
506f1d07 SR |
1247 | select SPARSEMEM_STATIC if X86_32 |
1248 | select SPARSEMEM_VMEMMAP_ENABLE if X86_64 | |
1249 | ||
1250 | config ARCH_SELECT_MEMORY_MODEL | |
1251 | def_bool y | |
b263295d | 1252 | depends on ARCH_SPARSEMEM_ENABLE |
506f1d07 SR |
1253 | |
1254 | config ARCH_MEMORY_PROBE | |
1255 | def_bool X86_64 | |
1256 | depends on MEMORY_HOTPLUG | |
1257 | ||
a29815a3 AK |
1258 | config ILLEGAL_POINTER_VALUE |
1259 | hex | |
1260 | default 0 if X86_32 | |
1261 | default 0xdead000000000000 if X86_64 | |
1262 | ||
506f1d07 SR |
1263 | source "mm/Kconfig" |
1264 | ||
1265 | config HIGHPTE | |
1266 | bool "Allocate 3rd-level pagetables from highmem" | |
6fc108a0 | 1267 | depends on HIGHMEM |
8f9ca475 | 1268 | ---help--- |
506f1d07 SR |
1269 | The VM uses one page table entry for each page of physical memory. |
1270 | For systems with a lot of RAM, this can be wasteful of precious | |
1271 | low memory. Setting this option will put user-space page table | |
1272 | entries in high memory. | |
1273 | ||
9f077871 | 1274 | config X86_CHECK_BIOS_CORRUPTION |
8f9ca475 IM |
1275 | bool "Check for low memory corruption" |
1276 | ---help--- | |
1277 | Periodically check for memory corruption in low memory, which | |
1278 | is suspected to be caused by BIOS. Even when enabled in the | |
1279 | configuration, it is disabled at runtime. Enable it by | |
1280 | setting "memory_corruption_check=1" on the kernel command | |
1281 | line. By default it scans the low 64k of memory every 60 | |
1282 | seconds; see the memory_corruption_check_size and | |
1283 | memory_corruption_check_period parameters in | |
1284 | Documentation/kernel-parameters.txt to adjust this. | |
1285 | ||
1286 | When enabled with the default parameters, this option has | |
1287 | almost no overhead, as it reserves a relatively small amount | |
1288 | of memory and scans it infrequently. It both detects corruption | |
1289 | and prevents it from affecting the running system. | |
1290 | ||
1291 | It is, however, intended as a diagnostic tool; if repeatable | |
1292 | BIOS-originated corruption always affects the same memory, | |
1293 | you can use memmap= to prevent the kernel from using that | |
1294 | memory. | |
9f077871 | 1295 | |
c885df50 | 1296 | config X86_BOOTPARAM_MEMORY_CORRUPTION_CHECK |
8f9ca475 | 1297 | bool "Set the default setting of memory_corruption_check" |
c885df50 JF |
1298 | depends on X86_CHECK_BIOS_CORRUPTION |
1299 | default y | |
8f9ca475 IM |
1300 | ---help--- |
1301 | Set whether the default state of memory_corruption_check is | |
1302 | on or off. | |
c885df50 | 1303 | |
9ea77bdb | 1304 | config X86_RESERVE_LOW |
d0cd7425 PA |
1305 | int "Amount of low memory, in kilobytes, to reserve for the BIOS" |
1306 | default 64 | |
1307 | range 4 640 | |
8f9ca475 | 1308 | ---help--- |
d0cd7425 PA |
1309 | Specify the amount of low memory to reserve for the BIOS. |
1310 | ||
1311 | The first page contains BIOS data structures that the kernel | |
1312 | must not use, so that page must always be reserved. | |
1313 | ||
1314 | By default we reserve the first 64K of physical RAM, as a | |
1315 | number of BIOSes are known to corrupt that memory range | |
1316 | during events such as suspend/resume or monitor cable | |
1317 | insertion, so it must not be used by the kernel. | |
fc381519 | 1318 | |
d0cd7425 PA |
1319 | You can set this to 4 if you are absolutely sure that you |
1320 | trust the BIOS to get all its memory reservations and usages | |
1321 | right. If you know your BIOS have problems beyond the | |
1322 | default 64K area, you can set this to 640 to avoid using the | |
1323 | entire low memory range. | |
fc381519 | 1324 | |
d0cd7425 PA |
1325 | If you have doubts about the BIOS (e.g. suspend/resume does |
1326 | not work or there's kernel crashes after certain hardware | |
1327 | hotplug events) then you might want to enable | |
1328 | X86_CHECK_BIOS_CORRUPTION=y to allow the kernel to check | |
1329 | typical corruption patterns. | |
fc381519 | 1330 | |
d0cd7425 | 1331 | Leave this to the default value of 64 if you are unsure. |
fc381519 | 1332 | |
506f1d07 SR |
1333 | config MATH_EMULATION |
1334 | bool | |
1335 | prompt "Math emulation" if X86_32 | |
1336 | ---help--- | |
1337 | Linux can emulate a math coprocessor (used for floating point | |
1338 | operations) if you don't have one. 486DX and Pentium processors have | |
1339 | a math coprocessor built in, 486SX and 386 do not, unless you added | |
1340 | a 487DX or 387, respectively. (The messages during boot time can | |
1341 | give you some hints here ["man dmesg"].) Everyone needs either a | |
1342 | coprocessor or this emulation. | |
1343 | ||
1344 | If you don't have a math coprocessor, you need to say Y here; if you | |
1345 | say Y here even though you have a coprocessor, the coprocessor will | |
1346 | be used nevertheless. (This behavior can be changed with the kernel | |
1347 | command line option "no387", which comes handy if your coprocessor | |
1348 | is broken. Try "man bootparam" or see the documentation of your boot | |
1349 | loader (lilo or loadlin) about how to pass options to the kernel at | |
1350 | boot time.) This means that it is a good idea to say Y here if you | |
1351 | intend to use this kernel on different machines. | |
1352 | ||
1353 | More information about the internals of the Linux math coprocessor | |
1354 | emulation can be found in <file:arch/x86/math-emu/README>. | |
1355 | ||
1356 | If you are not sure, say Y; apart from resulting in a 66 KB bigger | |
1357 | kernel, it won't hurt. | |
1358 | ||
1359 | config MTRR | |
6fc108a0 | 1360 | def_bool y |
c03cb314 | 1361 | prompt "MTRR (Memory Type Range Register) support" if EMBEDDED |
506f1d07 SR |
1362 | ---help--- |
1363 | On Intel P6 family processors (Pentium Pro, Pentium II and later) | |
1364 | the Memory Type Range Registers (MTRRs) may be used to control | |
1365 | processor access to memory ranges. This is most useful if you have | |
1366 | a video (VGA) card on a PCI or AGP bus. Enabling write-combining | |
1367 | allows bus write transfers to be combined into a larger transfer | |
1368 | before bursting over the PCI/AGP bus. This can increase performance | |
1369 | of image write operations 2.5 times or more. Saying Y here creates a | |
1370 | /proc/mtrr file which may be used to manipulate your processor's | |
1371 | MTRRs. Typically the X server should use this. | |
1372 | ||
1373 | This code has a reasonably generic interface so that similar | |
1374 | control registers on other processors can be easily supported | |
1375 | as well: | |
1376 | ||
1377 | The Cyrix 6x86, 6x86MX and M II processors have Address Range | |
1378 | Registers (ARRs) which provide a similar functionality to MTRRs. For | |
1379 | these, the ARRs are used to emulate the MTRRs. | |
1380 | The AMD K6-2 (stepping 8 and above) and K6-3 processors have two | |
1381 | MTRRs. The Centaur C6 (WinChip) has 8 MCRs, allowing | |
1382 | write-combining. All of these processors are supported by this code | |
1383 | and it makes sense to say Y here if you have one of them. | |
1384 | ||
1385 | Saying Y here also fixes a problem with buggy SMP BIOSes which only | |
1386 | set the MTRRs for the boot CPU and not for the secondary CPUs. This | |
1387 | can lead to all sorts of problems, so it's good to say Y here. | |
1388 | ||
1389 | You can safely say Y even if your machine doesn't have MTRRs, you'll | |
1390 | just add about 9 KB to your kernel. | |
1391 | ||
7225e751 | 1392 | See <file:Documentation/x86/mtrr.txt> for more information. |
506f1d07 | 1393 | |
95ffa243 | 1394 | config MTRR_SANITIZER |
2ffb3501 | 1395 | def_bool y |
95ffa243 YL |
1396 | prompt "MTRR cleanup support" |
1397 | depends on MTRR | |
8f9ca475 | 1398 | ---help--- |
aba3728c TG |
1399 | Convert MTRR layout from continuous to discrete, so X drivers can |
1400 | add writeback entries. | |
95ffa243 | 1401 | |
aba3728c | 1402 | Can be disabled with disable_mtrr_cleanup on the kernel command line. |
692105b8 | 1403 | The largest mtrr entry size for a continuous block can be set with |
aba3728c | 1404 | mtrr_chunk_size. |
95ffa243 | 1405 | |
2ffb3501 | 1406 | If unsure, say Y. |
95ffa243 YL |
1407 | |
1408 | config MTRR_SANITIZER_ENABLE_DEFAULT | |
f5098d62 YL |
1409 | int "MTRR cleanup enable value (0-1)" |
1410 | range 0 1 | |
1411 | default "0" | |
95ffa243 | 1412 | depends on MTRR_SANITIZER |
8f9ca475 | 1413 | ---help--- |
f5098d62 | 1414 | Enable mtrr cleanup default value |
95ffa243 | 1415 | |
12031a62 YL |
1416 | config MTRR_SANITIZER_SPARE_REG_NR_DEFAULT |
1417 | int "MTRR cleanup spare reg num (0-7)" | |
1418 | range 0 7 | |
1419 | default "1" | |
1420 | depends on MTRR_SANITIZER | |
8f9ca475 | 1421 | ---help--- |
12031a62 | 1422 | mtrr cleanup spare entries default, it can be changed via |
aba3728c | 1423 | mtrr_spare_reg_nr=N on the kernel command line. |
12031a62 | 1424 | |
2e5d9c85 | 1425 | config X86_PAT |
6fc108a0 | 1426 | def_bool y |
c03cb314 | 1427 | prompt "x86 PAT support" if EMBEDDED |
2a8a2719 | 1428 | depends on MTRR |
8f9ca475 | 1429 | ---help--- |
2e5d9c85 | 1430 | Use PAT attributes to setup page level cache control. |
042b78e4 | 1431 | |
2e5d9c85 | 1432 | PATs are the modern equivalents of MTRRs and are much more |
1433 | flexible than MTRRs. | |
1434 | ||
1435 | Say N here if you see bootup problems (boot crash, boot hang, | |
042b78e4 | 1436 | spontaneous reboots) or a non-working video driver. |
2e5d9c85 | 1437 | |
1438 | If unsure, say Y. | |
1439 | ||
46cf98cd VP |
1440 | config ARCH_USES_PG_UNCACHED |
1441 | def_bool y | |
1442 | depends on X86_PAT | |
1443 | ||
506f1d07 | 1444 | config EFI |
9ba16087 | 1445 | bool "EFI runtime service support" |
5b83683f | 1446 | depends on ACPI |
506f1d07 | 1447 | ---help--- |
8f9ca475 IM |
1448 | This enables the kernel to use EFI runtime services that are |
1449 | available (such as the EFI variable services). | |
506f1d07 | 1450 | |
8f9ca475 IM |
1451 | This option is only useful on systems that have EFI firmware. |
1452 | In addition, you should use the latest ELILO loader available | |
1453 | at <http://elilo.sourceforge.net> in order to take advantage | |
1454 | of EFI runtime services. However, even with this option, the | |
1455 | resultant kernel should continue to boot on existing non-EFI | |
1456 | platforms. | |
506f1d07 | 1457 | |
506f1d07 | 1458 | config SECCOMP |
3c2362e6 HH |
1459 | def_bool y |
1460 | prompt "Enable seccomp to safely compute untrusted bytecode" | |
8f9ca475 | 1461 | ---help--- |
506f1d07 SR |
1462 | This kernel feature is useful for number crunching applications |
1463 | that may need to compute untrusted bytecode during their | |
1464 | execution. By using pipes or other transports made available to | |
1465 | the process as file descriptors supporting the read/write | |
1466 | syscalls, it's possible to isolate those applications in | |
1467 | their own address space using seccomp. Once seccomp is | |
9c0bbee8 | 1468 | enabled via prctl(PR_SET_SECCOMP), it cannot be disabled |
506f1d07 SR |
1469 | and the task is only allowed to execute a few safe syscalls |
1470 | defined by each seccomp mode. | |
1471 | ||
1472 | If unsure, say Y. Only embedded should say N here. | |
1473 | ||
1474 | config CC_STACKPROTECTOR | |
1475 | bool "Enable -fstack-protector buffer overflow detection (EXPERIMENTAL)" | |
8f9ca475 IM |
1476 | ---help--- |
1477 | This option turns on the -fstack-protector GCC feature. This | |
113c5413 IM |
1478 | feature puts, at the beginning of functions, a canary value on |
1479 | the stack just before the return address, and validates | |
506f1d07 SR |
1480 | the value just before actually returning. Stack based buffer |
1481 | overflows (that need to overwrite this return address) now also | |
1482 | overwrite the canary, which gets detected and the attack is then | |
1483 | neutralized via a kernel panic. | |
1484 | ||
1485 | This feature requires gcc version 4.2 or above, or a distribution | |
1486 | gcc with the feature backported. Older versions are automatically | |
113c5413 IM |
1487 | detected and for those versions, this configuration option is |
1488 | ignored. (and a warning is printed during bootup) | |
506f1d07 SR |
1489 | |
1490 | source kernel/Kconfig.hz | |
1491 | ||
1492 | config KEXEC | |
1493 | bool "kexec system call" | |
8f9ca475 | 1494 | ---help--- |
506f1d07 SR |
1495 | kexec is a system call that implements the ability to shutdown your |
1496 | current kernel, and to start another kernel. It is like a reboot | |
1497 | but it is independent of the system firmware. And like a reboot | |
1498 | you can start any kernel with it, not just Linux. | |
1499 | ||
1500 | The name comes from the similarity to the exec system call. | |
1501 | ||
1502 | It is an ongoing process to be certain the hardware in a machine | |
1503 | is properly shutdown, so do not be surprised if this code does not | |
1504 | initially work for you. It may help to enable device hotplugging | |
1505 | support. As of this writing the exact hardware interface is | |
1506 | strongly in flux, so no good recommendation can be made. | |
1507 | ||
1508 | config CRASH_DUMP | |
04b69447 | 1509 | bool "kernel crash dumps" |
506f1d07 | 1510 | depends on X86_64 || (X86_32 && HIGHMEM) |
8f9ca475 | 1511 | ---help--- |
506f1d07 SR |
1512 | Generate crash dump after being started by kexec. |
1513 | This should be normally only set in special crash dump kernels | |
1514 | which are loaded in the main kernel with kexec-tools into | |
1515 | a specially reserved region and then later executed after | |
1516 | a crash by kdump/kexec. The crash dump kernel must be compiled | |
1517 | to a memory address not used by the main kernel or BIOS using | |
1518 | PHYSICAL_START, or it must be built as a relocatable image | |
1519 | (CONFIG_RELOCATABLE=y). | |
1520 | For more details see Documentation/kdump/kdump.txt | |
1521 | ||
3ab83521 HY |
1522 | config KEXEC_JUMP |
1523 | bool "kexec jump (EXPERIMENTAL)" | |
1524 | depends on EXPERIMENTAL | |
fee7b0d8 | 1525 | depends on KEXEC && HIBERNATION |
8f9ca475 | 1526 | ---help--- |
89081d17 HY |
1527 | Jump between original kernel and kexeced kernel and invoke |
1528 | code in physical address mode via KEXEC | |
3ab83521 | 1529 | |
506f1d07 SR |
1530 | config PHYSICAL_START |
1531 | hex "Physical address where the kernel is loaded" if (EMBEDDED || CRASH_DUMP) | |
ceefccc9 | 1532 | default "0x1000000" |
8f9ca475 | 1533 | ---help--- |
506f1d07 SR |
1534 | This gives the physical address where the kernel is loaded. |
1535 | ||
1536 | If kernel is a not relocatable (CONFIG_RELOCATABLE=n) then | |
1537 | bzImage will decompress itself to above physical address and | |
1538 | run from there. Otherwise, bzImage will run from the address where | |
1539 | it has been loaded by the boot loader and will ignore above physical | |
1540 | address. | |
1541 | ||
1542 | In normal kdump cases one does not have to set/change this option | |
1543 | as now bzImage can be compiled as a completely relocatable image | |
1544 | (CONFIG_RELOCATABLE=y) and be used to load and run from a different | |
1545 | address. This option is mainly useful for the folks who don't want | |
1546 | to use a bzImage for capturing the crash dump and want to use a | |
1547 | vmlinux instead. vmlinux is not relocatable hence a kernel needs | |
1548 | to be specifically compiled to run from a specific memory area | |
1549 | (normally a reserved region) and this option comes handy. | |
1550 | ||
ceefccc9 PA |
1551 | So if you are using bzImage for capturing the crash dump, |
1552 | leave the value here unchanged to 0x1000000 and set | |
1553 | CONFIG_RELOCATABLE=y. Otherwise if you plan to use vmlinux | |
1554 | for capturing the crash dump change this value to start of | |
1555 | the reserved region. In other words, it can be set based on | |
1556 | the "X" value as specified in the "crashkernel=YM@XM" | |
1557 | command line boot parameter passed to the panic-ed | |
1558 | kernel. Please take a look at Documentation/kdump/kdump.txt | |
1559 | for more details about crash dumps. | |
506f1d07 SR |
1560 | |
1561 | Usage of bzImage for capturing the crash dump is recommended as | |
1562 | one does not have to build two kernels. Same kernel can be used | |
1563 | as production kernel and capture kernel. Above option should have | |
1564 | gone away after relocatable bzImage support is introduced. But it | |
1565 | is present because there are users out there who continue to use | |
1566 | vmlinux for dump capture. This option should go away down the | |
1567 | line. | |
1568 | ||
1569 | Don't change this unless you know what you are doing. | |
1570 | ||
1571 | config RELOCATABLE | |
26717808 PA |
1572 | bool "Build a relocatable kernel" |
1573 | default y | |
8f9ca475 | 1574 | ---help--- |
506f1d07 SR |
1575 | This builds a kernel image that retains relocation information |
1576 | so it can be loaded someplace besides the default 1MB. | |
1577 | The relocations tend to make the kernel binary about 10% larger, | |
1578 | but are discarded at runtime. | |
1579 | ||
1580 | One use is for the kexec on panic case where the recovery kernel | |
1581 | must live at a different physical address than the primary | |
1582 | kernel. | |
1583 | ||
1584 | Note: If CONFIG_RELOCATABLE=y, then the kernel runs from the address | |
1585 | it has been loaded at and the compile time physical address | |
1586 | (CONFIG_PHYSICAL_START) is ignored. | |
1587 | ||
845adf72 PA |
1588 | # Relocation on x86-32 needs some additional build support |
1589 | config X86_NEED_RELOCS | |
1590 | def_bool y | |
1591 | depends on X86_32 && RELOCATABLE | |
1592 | ||
506f1d07 | 1593 | config PHYSICAL_ALIGN |
6fc108a0 | 1594 | hex "Alignment value to which kernel should be aligned" if X86_32 |
ceefccc9 PA |
1595 | default "0x1000000" |
1596 | range 0x2000 0x1000000 | |
8f9ca475 | 1597 | ---help--- |
506f1d07 SR |
1598 | This value puts the alignment restrictions on physical address |
1599 | where kernel is loaded and run from. Kernel is compiled for an | |
1600 | address which meets above alignment restriction. | |
1601 | ||
1602 | If bootloader loads the kernel at a non-aligned address and | |
1603 | CONFIG_RELOCATABLE is set, kernel will move itself to nearest | |
1604 | address aligned to above value and run from there. | |
1605 | ||
1606 | If bootloader loads the kernel at a non-aligned address and | |
1607 | CONFIG_RELOCATABLE is not set, kernel will ignore the run time | |
1608 | load address and decompress itself to the address it has been | |
1609 | compiled for and run from there. The address for which kernel is | |
1610 | compiled already meets above alignment restrictions. Hence the | |
1611 | end result is that kernel runs from a physical address meeting | |
1612 | above alignment restrictions. | |
1613 | ||
1614 | Don't change this unless you know what you are doing. | |
1615 | ||
1616 | config HOTPLUG_CPU | |
7c13e6a3 | 1617 | bool "Support for hot-pluggable CPUs" |
4b19ed91 | 1618 | depends on SMP && HOTPLUG |
506f1d07 | 1619 | ---help--- |
7c13e6a3 DS |
1620 | Say Y here to allow turning CPUs off and on. CPUs can be |
1621 | controlled through /sys/devices/system/cpu. | |
1622 | ( Note: power management support will enable this option | |
1623 | automatically on SMP systems. ) | |
1624 | Say N if you want to disable CPU hotplug. | |
506f1d07 SR |
1625 | |
1626 | config COMPAT_VDSO | |
3c2362e6 HH |
1627 | def_bool y |
1628 | prompt "Compat VDSO support" | |
af65d648 | 1629 | depends on X86_32 || IA32_EMULATION |
8f9ca475 | 1630 | ---help--- |
af65d648 | 1631 | Map the 32-bit VDSO to the predictable old-style address too. |
e84446de | 1632 | |
506f1d07 SR |
1633 | Say N here if you are running a sufficiently recent glibc |
1634 | version (2.3.3 or later), to remove the high-mapped | |
1635 | VDSO mapping and to exclusively use the randomized VDSO. | |
1636 | ||
1637 | If unsure, say Y. | |
1638 | ||
516cbf37 TB |
1639 | config CMDLINE_BOOL |
1640 | bool "Built-in kernel command line" | |
8f9ca475 | 1641 | ---help--- |
516cbf37 TB |
1642 | Allow for specifying boot arguments to the kernel at |
1643 | build time. On some systems (e.g. embedded ones), it is | |
1644 | necessary or convenient to provide some or all of the | |
1645 | kernel boot arguments with the kernel itself (that is, | |
1646 | to not rely on the boot loader to provide them.) | |
1647 | ||
1648 | To compile command line arguments into the kernel, | |
1649 | set this option to 'Y', then fill in the | |
1650 | the boot arguments in CONFIG_CMDLINE. | |
1651 | ||
1652 | Systems with fully functional boot loaders (i.e. non-embedded) | |
1653 | should leave this option set to 'N'. | |
1654 | ||
1655 | config CMDLINE | |
1656 | string "Built-in kernel command string" | |
1657 | depends on CMDLINE_BOOL | |
1658 | default "" | |
8f9ca475 | 1659 | ---help--- |
516cbf37 TB |
1660 | Enter arguments here that should be compiled into the kernel |
1661 | image and used at boot time. If the boot loader provides a | |
1662 | command line at boot time, it is appended to this string to | |
1663 | form the full kernel command line, when the system boots. | |
1664 | ||
1665 | However, you can use the CONFIG_CMDLINE_OVERRIDE option to | |
1666 | change this behavior. | |
1667 | ||
1668 | In most cases, the command line (whether built-in or provided | |
1669 | by the boot loader) should specify the device for the root | |
1670 | file system. | |
1671 | ||
1672 | config CMDLINE_OVERRIDE | |
1673 | bool "Built-in command line overrides boot loader arguments" | |
516cbf37 | 1674 | depends on CMDLINE_BOOL |
8f9ca475 | 1675 | ---help--- |
516cbf37 TB |
1676 | Set this option to 'Y' to have the kernel ignore the boot loader |
1677 | command line, and use ONLY the built-in command line. | |
1678 | ||
1679 | This is used to work around broken boot loaders. This should | |
1680 | be set to 'N' under normal conditions. | |
1681 | ||
506f1d07 SR |
1682 | endmenu |
1683 | ||
1684 | config ARCH_ENABLE_MEMORY_HOTPLUG | |
1685 | def_bool y | |
1686 | depends on X86_64 || (X86_32 && HIGHMEM) | |
1687 | ||
35551053 GH |
1688 | config ARCH_ENABLE_MEMORY_HOTREMOVE |
1689 | def_bool y | |
1690 | depends on MEMORY_HOTPLUG | |
1691 | ||
506f1d07 SR |
1692 | config HAVE_ARCH_EARLY_PFN_TO_NID |
1693 | def_bool X86_64 | |
1694 | depends on NUMA | |
1695 | ||
e534c7c5 LS |
1696 | config USE_PERCPU_NUMA_NODE_ID |
1697 | def_bool X86_64 | |
1698 | depends on NUMA | |
1699 | ||
da85f865 | 1700 | menu "Power management and ACPI options" |
e279b6c1 SR |
1701 | |
1702 | config ARCH_HIBERNATION_HEADER | |
3c2362e6 | 1703 | def_bool y |
e279b6c1 | 1704 | depends on X86_64 && HIBERNATION |
e279b6c1 SR |
1705 | |
1706 | source "kernel/power/Kconfig" | |
1707 | ||
1708 | source "drivers/acpi/Kconfig" | |
1709 | ||
efafc8b2 FT |
1710 | source "drivers/sfi/Kconfig" |
1711 | ||
a6b68076 | 1712 | config X86_APM_BOOT |
6fc108a0 | 1713 | def_bool y |
a6b68076 AK |
1714 | depends on APM || APM_MODULE |
1715 | ||
e279b6c1 SR |
1716 | menuconfig APM |
1717 | tristate "APM (Advanced Power Management) BIOS support" | |
efefa6f6 | 1718 | depends on X86_32 && PM_SLEEP |
e279b6c1 SR |
1719 | ---help--- |
1720 | APM is a BIOS specification for saving power using several different | |
1721 | techniques. This is mostly useful for battery powered laptops with | |
1722 | APM compliant BIOSes. If you say Y here, the system time will be | |
1723 | reset after a RESUME operation, the /proc/apm device will provide | |
1724 | battery status information, and user-space programs will receive | |
1725 | notification of APM "events" (e.g. battery status change). | |
1726 | ||
1727 | If you select "Y" here, you can disable actual use of the APM | |
1728 | BIOS by passing the "apm=off" option to the kernel at boot time. | |
1729 | ||
1730 | Note that the APM support is almost completely disabled for | |
1731 | machines with more than one CPU. | |
1732 | ||
1733 | In order to use APM, you will need supporting software. For location | |
53471121 | 1734 | and more information, read <file:Documentation/power/pm.txt> and the |
e279b6c1 SR |
1735 | Battery Powered Linux mini-HOWTO, available from |
1736 | <http://www.tldp.org/docs.html#howto>. | |
1737 | ||
1738 | This driver does not spin down disk drives (see the hdparm(8) | |
1739 | manpage ("man 8 hdparm") for that), and it doesn't turn off | |
1740 | VESA-compliant "green" monitors. | |
1741 | ||
1742 | This driver does not support the TI 4000M TravelMate and the ACER | |
1743 | 486/DX4/75 because they don't have compliant BIOSes. Many "green" | |
1744 | desktop machines also don't have compliant BIOSes, and this driver | |
1745 | may cause those machines to panic during the boot phase. | |
1746 | ||
1747 | Generally, if you don't have a battery in your machine, there isn't | |
1748 | much point in using this driver and you should say N. If you get | |
1749 | random kernel OOPSes or reboots that don't seem to be related to | |
1750 | anything, try disabling/enabling this option (or disabling/enabling | |
1751 | APM in your BIOS). | |
1752 | ||
1753 | Some other things you should try when experiencing seemingly random, | |
1754 | "weird" problems: | |
1755 | ||
1756 | 1) make sure that you have enough swap space and that it is | |
1757 | enabled. | |
1758 | 2) pass the "no-hlt" option to the kernel | |
1759 | 3) switch on floating point emulation in the kernel and pass | |
1760 | the "no387" option to the kernel | |
1761 | 4) pass the "floppy=nodma" option to the kernel | |
1762 | 5) pass the "mem=4M" option to the kernel (thereby disabling | |
1763 | all but the first 4 MB of RAM) | |
1764 | 6) make sure that the CPU is not over clocked. | |
1765 | 7) read the sig11 FAQ at <http://www.bitwizard.nl/sig11/> | |
1766 | 8) disable the cache from your BIOS settings | |
1767 | 9) install a fan for the video card or exchange video RAM | |
1768 | 10) install a better fan for the CPU | |
1769 | 11) exchange RAM chips | |
1770 | 12) exchange the motherboard. | |
1771 | ||
1772 | To compile this driver as a module, choose M here: the | |
1773 | module will be called apm. | |
1774 | ||
1775 | if APM | |
1776 | ||
1777 | config APM_IGNORE_USER_SUSPEND | |
1778 | bool "Ignore USER SUSPEND" | |
8f9ca475 | 1779 | ---help--- |
e279b6c1 SR |
1780 | This option will ignore USER SUSPEND requests. On machines with a |
1781 | compliant APM BIOS, you want to say N. However, on the NEC Versa M | |
1782 | series notebooks, it is necessary to say Y because of a BIOS bug. | |
1783 | ||
1784 | config APM_DO_ENABLE | |
1785 | bool "Enable PM at boot time" | |
1786 | ---help--- | |
1787 | Enable APM features at boot time. From page 36 of the APM BIOS | |
1788 | specification: "When disabled, the APM BIOS does not automatically | |
1789 | power manage devices, enter the Standby State, enter the Suspend | |
1790 | State, or take power saving steps in response to CPU Idle calls." | |
1791 | This driver will make CPU Idle calls when Linux is idle (unless this | |
1792 | feature is turned off -- see "Do CPU IDLE calls", below). This | |
1793 | should always save battery power, but more complicated APM features | |
1794 | will be dependent on your BIOS implementation. You may need to turn | |
1795 | this option off if your computer hangs at boot time when using APM | |
1796 | support, or if it beeps continuously instead of suspending. Turn | |
1797 | this off if you have a NEC UltraLite Versa 33/C or a Toshiba | |
1798 | T400CDT. This is off by default since most machines do fine without | |
1799 | this feature. | |
1800 | ||
1801 | config APM_CPU_IDLE | |
1802 | bool "Make CPU Idle calls when idle" | |
8f9ca475 | 1803 | ---help--- |
e279b6c1 SR |
1804 | Enable calls to APM CPU Idle/CPU Busy inside the kernel's idle loop. |
1805 | On some machines, this can activate improved power savings, such as | |
1806 | a slowed CPU clock rate, when the machine is idle. These idle calls | |
1807 | are made after the idle loop has run for some length of time (e.g., | |
1808 | 333 mS). On some machines, this will cause a hang at boot time or | |
1809 | whenever the CPU becomes idle. (On machines with more than one CPU, | |
1810 | this option does nothing.) | |
1811 | ||
1812 | config APM_DISPLAY_BLANK | |
1813 | bool "Enable console blanking using APM" | |
8f9ca475 | 1814 | ---help--- |
e279b6c1 SR |
1815 | Enable console blanking using the APM. Some laptops can use this to |
1816 | turn off the LCD backlight when the screen blanker of the Linux | |
1817 | virtual console blanks the screen. Note that this is only used by | |
1818 | the virtual console screen blanker, and won't turn off the backlight | |
1819 | when using the X Window system. This also doesn't have anything to | |
1820 | do with your VESA-compliant power-saving monitor. Further, this | |
1821 | option doesn't work for all laptops -- it might not turn off your | |
1822 | backlight at all, or it might print a lot of errors to the console, | |
1823 | especially if you are using gpm. | |
1824 | ||
1825 | config APM_ALLOW_INTS | |
1826 | bool "Allow interrupts during APM BIOS calls" | |
8f9ca475 | 1827 | ---help--- |
e279b6c1 SR |
1828 | Normally we disable external interrupts while we are making calls to |
1829 | the APM BIOS as a measure to lessen the effects of a badly behaving | |
1830 | BIOS implementation. The BIOS should reenable interrupts if it | |
1831 | needs to. Unfortunately, some BIOSes do not -- especially those in | |
1832 | many of the newer IBM Thinkpads. If you experience hangs when you | |
1833 | suspend, try setting this to Y. Otherwise, say N. | |
1834 | ||
e279b6c1 SR |
1835 | endif # APM |
1836 | ||
1837 | source "arch/x86/kernel/cpu/cpufreq/Kconfig" | |
1838 | ||
1839 | source "drivers/cpuidle/Kconfig" | |
1840 | ||
27471fdb AH |
1841 | source "drivers/idle/Kconfig" |
1842 | ||
e279b6c1 SR |
1843 | endmenu |
1844 | ||
1845 | ||
1846 | menu "Bus options (PCI etc.)" | |
1847 | ||
1848 | config PCI | |
1ac97018 | 1849 | bool "PCI support" |
1c858087 | 1850 | default y |
e279b6c1 | 1851 | select ARCH_SUPPORTS_MSI if (X86_LOCAL_APIC && X86_IO_APIC) |
8f9ca475 | 1852 | ---help--- |
e279b6c1 SR |
1853 | Find out whether you have a PCI motherboard. PCI is the name of a |
1854 | bus system, i.e. the way the CPU talks to the other stuff inside | |
1855 | your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or | |
1856 | VESA. If you have PCI, say Y, otherwise N. | |
1857 | ||
e279b6c1 SR |
1858 | choice |
1859 | prompt "PCI access mode" | |
efefa6f6 | 1860 | depends on X86_32 && PCI |
e279b6c1 SR |
1861 | default PCI_GOANY |
1862 | ---help--- | |
1863 | On PCI systems, the BIOS can be used to detect the PCI devices and | |
1864 | determine their configuration. However, some old PCI motherboards | |
1865 | have BIOS bugs and may crash if this is done. Also, some embedded | |
1866 | PCI-based systems don't have any BIOS at all. Linux can also try to | |
1867 | detect the PCI hardware directly without using the BIOS. | |
1868 | ||
1869 | With this option, you can specify how Linux should detect the | |
1870 | PCI devices. If you choose "BIOS", the BIOS will be used, | |
1871 | if you choose "Direct", the BIOS won't be used, and if you | |
1872 | choose "MMConfig", then PCI Express MMCONFIG will be used. | |
1873 | If you choose "Any", the kernel will try MMCONFIG, then the | |
1874 | direct access method and falls back to the BIOS if that doesn't | |
1875 | work. If unsure, go with the default, which is "Any". | |
1876 | ||
1877 | config PCI_GOBIOS | |
1878 | bool "BIOS" | |
1879 | ||
1880 | config PCI_GOMMCONFIG | |
1881 | bool "MMConfig" | |
1882 | ||
1883 | config PCI_GODIRECT | |
1884 | bool "Direct" | |
1885 | ||
3ef0e1f8 | 1886 | config PCI_GOOLPC |
76fb6570 | 1887 | bool "OLPC XO-1" |
3ef0e1f8 AS |
1888 | depends on OLPC |
1889 | ||
2bdd1b03 AS |
1890 | config PCI_GOANY |
1891 | bool "Any" | |
1892 | ||
e279b6c1 SR |
1893 | endchoice |
1894 | ||
1895 | config PCI_BIOS | |
3c2362e6 | 1896 | def_bool y |
efefa6f6 | 1897 | depends on X86_32 && PCI && (PCI_GOBIOS || PCI_GOANY) |
e279b6c1 SR |
1898 | |
1899 | # x86-64 doesn't support PCI BIOS access from long mode so always go direct. | |
1900 | config PCI_DIRECT | |
3c2362e6 | 1901 | def_bool y |
efefa6f6 | 1902 | depends on PCI && (X86_64 || (PCI_GODIRECT || PCI_GOANY || PCI_GOOLPC)) |
e279b6c1 SR |
1903 | |
1904 | config PCI_MMCONFIG | |
3c2362e6 | 1905 | def_bool y |
5f0db7a2 | 1906 | depends on X86_32 && PCI && (ACPI || SFI) && (PCI_GOMMCONFIG || PCI_GOANY) |
e279b6c1 | 1907 | |
3ef0e1f8 | 1908 | config PCI_OLPC |
2bdd1b03 AS |
1909 | def_bool y |
1910 | depends on PCI && OLPC && (PCI_GOOLPC || PCI_GOANY) | |
3ef0e1f8 | 1911 | |
b5401a96 AN |
1912 | config PCI_XEN |
1913 | def_bool y | |
1914 | depends on PCI && XEN | |
1915 | select SWIOTLB_XEN | |
1916 | ||
e279b6c1 | 1917 | config PCI_DOMAINS |
3c2362e6 | 1918 | def_bool y |
e279b6c1 | 1919 | depends on PCI |
e279b6c1 SR |
1920 | |
1921 | config PCI_MMCONFIG | |
1922 | bool "Support mmconfig PCI config space access" | |
1923 | depends on X86_64 && PCI && ACPI | |
1924 | ||
3f6ea84a IS |
1925 | config PCI_CNB20LE_QUIRK |
1926 | bool "Read CNB20LE Host Bridge Windows" | |
1927 | depends on PCI | |
1928 | help | |
1929 | Read the PCI windows out of the CNB20LE host bridge. This allows | |
1930 | PCI hotplug to work on systems with the CNB20LE chipset which do | |
1931 | not have ACPI. | |
1932 | ||
e279b6c1 SR |
1933 | config DMAR |
1934 | bool "Support for DMA Remapping Devices (EXPERIMENTAL)" | |
4cf2e75d | 1935 | depends on PCI_MSI && ACPI && EXPERIMENTAL |
e279b6c1 SR |
1936 | help |
1937 | DMA remapping (DMAR) devices support enables independent address | |
1938 | translations for Direct Memory Access (DMA) from devices. | |
1939 | These DMA remapping devices are reported via ACPI tables | |
1940 | and include PCI device scope covered by these DMA | |
1941 | remapping devices. | |
1942 | ||
0cd5c3c8 | 1943 | config DMAR_DEFAULT_ON |
f6be37fd | 1944 | def_bool y |
0cd5c3c8 KM |
1945 | prompt "Enable DMA Remapping Devices by default" |
1946 | depends on DMAR | |
1947 | help | |
1948 | Selecting this option will enable a DMAR device at boot time if | |
1949 | one is found. If this option is not selected, DMAR support can | |
1950 | be enabled by passing intel_iommu=on to the kernel. It is | |
1951 | recommended you say N here while the DMAR code remains | |
1952 | experimental. | |
1953 | ||
62edf5dc | 1954 | config DMAR_BROKEN_GFX_WA |
6fc108a0 | 1955 | bool "Workaround broken graphics drivers (going away soon)" |
0c02a20f | 1956 | depends on DMAR && BROKEN |
62edf5dc DW |
1957 | ---help--- |
1958 | Current Graphics drivers tend to use physical address | |
1959 | for DMA and avoid using DMA APIs. Setting this config | |
1960 | option permits the IOMMU driver to set a unity map for | |
1961 | all the OS-visible memory. Hence the driver can continue | |
1962 | to use physical addresses for DMA, at least until this | |
1963 | option is removed in the 2.6.32 kernel. | |
1964 | ||
e279b6c1 | 1965 | config DMAR_FLOPPY_WA |
3c2362e6 | 1966 | def_bool y |
e279b6c1 | 1967 | depends on DMAR |
8f9ca475 | 1968 | ---help--- |
c7ab48d2 | 1969 | Floppy disk drivers are known to bypass DMA API calls |
8f9ca475 IM |
1970 | thereby failing to work when IOMMU is enabled. This |
1971 | workaround will setup a 1:1 mapping for the first | |
c7ab48d2 | 1972 | 16MiB to make floppy (an ISA device) work. |
e279b6c1 | 1973 | |
9fa8c481 SS |
1974 | config INTR_REMAP |
1975 | bool "Support for Interrupt Remapping (EXPERIMENTAL)" | |
1976 | depends on X86_64 && X86_IO_APIC && PCI_MSI && ACPI && EXPERIMENTAL | |
8f9ca475 IM |
1977 | ---help--- |
1978 | Supports Interrupt remapping for IO-APIC and MSI devices. | |
1979 | To use x2apic mode in the CPU's which support x2APIC enhancements or | |
1980 | to support platforms with CPU's having > 8 bit APIC ID, say Y. | |
9fa8c481 | 1981 | |
e279b6c1 SR |
1982 | source "drivers/pci/pcie/Kconfig" |
1983 | ||
1984 | source "drivers/pci/Kconfig" | |
1985 | ||
1986 | # x86_64 have no ISA slots, but do have ISA-style DMA. | |
1987 | config ISA_DMA_API | |
3c2362e6 | 1988 | def_bool y |
e279b6c1 SR |
1989 | |
1990 | if X86_32 | |
1991 | ||
1992 | config ISA | |
1993 | bool "ISA support" | |
8f9ca475 | 1994 | ---help--- |
e279b6c1 SR |
1995 | Find out whether you have ISA slots on your motherboard. ISA is the |
1996 | name of a bus system, i.e. the way the CPU talks to the other stuff | |
1997 | inside your box. Other bus systems are PCI, EISA, MicroChannel | |
1998 | (MCA) or VESA. ISA is an older system, now being displaced by PCI; | |
1999 | newer boards don't support it. If you have ISA, say Y, otherwise N. | |
2000 | ||
2001 | config EISA | |
2002 | bool "EISA support" | |
2003 | depends on ISA | |
2004 | ---help--- | |
2005 | The Extended Industry Standard Architecture (EISA) bus was | |
2006 | developed as an open alternative to the IBM MicroChannel bus. | |
2007 | ||
2008 | The EISA bus provided some of the features of the IBM MicroChannel | |
2009 | bus while maintaining backward compatibility with cards made for | |
2010 | the older ISA bus. The EISA bus saw limited use between 1988 and | |
2011 | 1995 when it was made obsolete by the PCI bus. | |
2012 | ||
2013 | Say Y here if you are building a kernel for an EISA-based machine. | |
2014 | ||
2015 | Otherwise, say N. | |
2016 | ||
2017 | source "drivers/eisa/Kconfig" | |
2018 | ||
2019 | config MCA | |
72ee6ebb | 2020 | bool "MCA support" |
8f9ca475 | 2021 | ---help--- |
e279b6c1 SR |
2022 | MicroChannel Architecture is found in some IBM PS/2 machines and |
2023 | laptops. It is a bus system similar to PCI or ISA. See | |
2024 | <file:Documentation/mca.txt> (and especially the web page given | |
2025 | there) before attempting to build an MCA bus kernel. | |
2026 | ||
2027 | source "drivers/mca/Kconfig" | |
2028 | ||
2029 | config SCx200 | |
2030 | tristate "NatSemi SCx200 support" | |
8f9ca475 | 2031 | ---help--- |
e279b6c1 SR |
2032 | This provides basic support for National Semiconductor's |
2033 | (now AMD's) Geode processors. The driver probes for the | |
2034 | PCI-IDs of several on-chip devices, so its a good dependency | |
2035 | for other scx200_* drivers. | |
2036 | ||
2037 | If compiled as a module, the driver is named scx200. | |
2038 | ||
2039 | config SCx200HR_TIMER | |
2040 | tristate "NatSemi SCx200 27MHz High-Resolution Timer Support" | |
592913ec | 2041 | depends on SCx200 |
e279b6c1 | 2042 | default y |
8f9ca475 | 2043 | ---help--- |
e279b6c1 SR |
2044 | This driver provides a clocksource built upon the on-chip |
2045 | 27MHz high-resolution timer. Its also a workaround for | |
2046 | NSC Geode SC-1100's buggy TSC, which loses time when the | |
2047 | processor goes idle (as is done by the scheduler). The | |
2048 | other workaround is idle=poll boot option. | |
2049 | ||
3ef0e1f8 AS |
2050 | config OLPC |
2051 | bool "One Laptop Per Child support" | |
3c554946 | 2052 | select GPIOLIB |
3e3c4860 | 2053 | select OLPC_OPENFIRMWARE |
8f9ca475 | 2054 | ---help--- |
3ef0e1f8 AS |
2055 | Add support for detecting the unique features of the OLPC |
2056 | XO hardware. | |
2057 | ||
bf1ebf00 DD |
2058 | config OLPC_XO1 |
2059 | tristate "OLPC XO-1 support" | |
9e9006e9 | 2060 | depends on OLPC && PCI |
bf1ebf00 DD |
2061 | ---help--- |
2062 | Add support for non-essential features of the OLPC XO-1 laptop. | |
2063 | ||
fd699c76 AS |
2064 | config OLPC_OPENFIRMWARE |
2065 | bool "Support for OLPC's Open Firmware" | |
2066 | depends on !X86_64 && !X86_PAE | |
3e3c4860 | 2067 | default n |
fd699c76 AS |
2068 | help |
2069 | This option adds support for the implementation of Open Firmware | |
2070 | that is used on the OLPC XO-1 Children's Machine. | |
2071 | If unsure, say N here. | |
2072 | ||
bc0120fd SR |
2073 | endif # X86_32 |
2074 | ||
23ac4ae8 | 2075 | config AMD_NB |
e279b6c1 | 2076 | def_bool y |
0e152cd7 | 2077 | depends on CPU_SUP_AMD && PCI |
e279b6c1 SR |
2078 | |
2079 | source "drivers/pcmcia/Kconfig" | |
2080 | ||
2081 | source "drivers/pci/hotplug/Kconfig" | |
2082 | ||
2083 | endmenu | |
2084 | ||
2085 | ||
2086 | menu "Executable file formats / Emulations" | |
2087 | ||
2088 | source "fs/Kconfig.binfmt" | |
2089 | ||
2090 | config IA32_EMULATION | |
2091 | bool "IA32 Emulation" | |
2092 | depends on X86_64 | |
a97f52e6 | 2093 | select COMPAT_BINFMT_ELF |
8f9ca475 | 2094 | ---help--- |
e279b6c1 SR |
2095 | Include code to run 32-bit programs under a 64-bit kernel. You should |
2096 | likely turn this on, unless you're 100% sure that you don't have any | |
2097 | 32-bit programs left. | |
2098 | ||
2099 | config IA32_AOUT | |
8f9ca475 IM |
2100 | tristate "IA32 a.out support" |
2101 | depends on IA32_EMULATION | |
2102 | ---help--- | |
2103 | Support old a.out binaries in the 32bit emulation. | |
e279b6c1 SR |
2104 | |
2105 | config COMPAT | |
3c2362e6 | 2106 | def_bool y |
e279b6c1 | 2107 | depends on IA32_EMULATION |
e279b6c1 SR |
2108 | |
2109 | config COMPAT_FOR_U64_ALIGNMENT | |
2110 | def_bool COMPAT | |
2111 | depends on X86_64 | |
2112 | ||
2113 | config SYSVIPC_COMPAT | |
3c2362e6 | 2114 | def_bool y |
b8992195 | 2115 | depends on COMPAT && SYSVIPC |
e279b6c1 SR |
2116 | |
2117 | endmenu | |
2118 | ||
2119 | ||
e5beae16 KP |
2120 | config HAVE_ATOMIC_IOMAP |
2121 | def_bool y | |
2122 | depends on X86_32 | |
2123 | ||
3cba11d3 MH |
2124 | config HAVE_TEXT_POKE_SMP |
2125 | bool | |
2126 | select STOP_MACHINE if SMP | |
2127 | ||
e279b6c1 SR |
2128 | source "net/Kconfig" |
2129 | ||
2130 | source "drivers/Kconfig" | |
2131 | ||
2132 | source "drivers/firmware/Kconfig" | |
2133 | ||
2134 | source "fs/Kconfig" | |
2135 | ||
e279b6c1 SR |
2136 | source "arch/x86/Kconfig.debug" |
2137 | ||
2138 | source "security/Kconfig" | |
2139 | ||
2140 | source "crypto/Kconfig" | |
2141 | ||
edf88417 AK |
2142 | source "arch/x86/kvm/Kconfig" |
2143 | ||
e279b6c1 | 2144 | source "lib/Kconfig" |