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