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