]>
Commit | Line | Data |
---|---|---|
1da177e4 LT |
1 | # |
2 | # For a description of the syntax of this configuration file, | |
3 | # see Documentation/kbuild/kconfig-language.txt. | |
4 | # | |
5 | ||
6 | mainmenu "Linux Kernel Configuration" | |
7 | ||
0d078f6f | 8 | config X86_32 |
1da177e4 LT |
9 | bool |
10 | default y | |
11 | help | |
12 | This is Linux's home port. Linux was originally native to the Intel | |
13 | 386, and runs on all the later x86 processors including the Intel | |
14 | 486, 586, Pentiums, and various instruction-set-compatible chips by | |
15 | AMD, Cyrix, and others. | |
16 | ||
52fdd089 BL |
17 | config SEMAPHORE_SLEEPERS |
18 | bool | |
19 | default y | |
20 | ||
0d078f6f BG |
21 | config X86 |
22 | bool | |
23 | default y | |
24 | ||
1da177e4 LT |
25 | config MMU |
26 | bool | |
27 | default y | |
28 | ||
29 | config SBUS | |
30 | bool | |
31 | ||
1da177e4 LT |
32 | config GENERIC_ISA_DMA |
33 | bool | |
34 | default y | |
35 | ||
36 | config GENERIC_IOMAP | |
37 | bool | |
38 | default y | |
39 | ||
a08b6b79 | 40 | config ARCH_MAY_HAVE_PC_FDC |
1da177e4 LT |
41 | bool |
42 | default y | |
43 | ||
e9928674 AK |
44 | config DMI |
45 | bool | |
46 | default y | |
47 | ||
1da177e4 LT |
48 | source "init/Kconfig" |
49 | ||
4092bdeb AK |
50 | config DOUBLEFAULT |
51 | default y | |
52 | bool "Enable doublefault exception handler" if EMBEDDED | |
53 | help | |
54 | This option allows trapping of rare doublefault exceptions that | |
55 | would otherwise cause a system to silently reboot. Disabling this | |
56 | option saves about 4k and might cause you much additional grey | |
57 | hair. | |
58 | ||
1da177e4 LT |
59 | menu "Processor type and features" |
60 | ||
61 | choice | |
62 | prompt "Subarchitecture Type" | |
63 | default X86_PC | |
64 | ||
65 | config X86_PC | |
66 | bool "PC-compatible" | |
67 | help | |
68 | Choose this option if your computer is a standard PC or compatible. | |
69 | ||
70 | config X86_ELAN | |
71 | bool "AMD Elan" | |
72 | help | |
73 | Select this for an AMD Elan processor. | |
74 | ||
75 | Do not use this option for K6/Athlon/Opteron processors! | |
76 | ||
77 | If unsure, choose "PC-compatible" instead. | |
78 | ||
79 | config X86_VOYAGER | |
80 | bool "Voyager (NCR)" | |
81 | help | |
82 | Voyager is an MCA-based 32-way capable SMP architecture proprietary | |
83 | to NCR Corp. Machine classes 345x/35xx/4100/51xx are Voyager-based. | |
84 | ||
85 | *** WARNING *** | |
86 | ||
87 | If you do not specifically know you have a Voyager based machine, | |
88 | say N here, otherwise the kernel you build will not be bootable. | |
89 | ||
90 | config X86_NUMAQ | |
91 | bool "NUMAQ (IBM/Sequent)" | |
1da177e4 LT |
92 | select NUMA |
93 | help | |
94 | This option is used for getting Linux to run on a (IBM/Sequent) NUMA | |
95 | multiquad box. This changes the way that processors are bootstrapped, | |
96 | and uses Clustered Logical APIC addressing mode instead of Flat Logical. | |
97 | You will need a new lynxer.elf file to flash your firmware with - send | |
98 | email to <Martin.Bligh@us.ibm.com>. | |
99 | ||
100 | config X86_SUMMIT | |
101 | bool "Summit/EXA (IBM x440)" | |
102 | depends on SMP | |
103 | help | |
104 | This option is needed for IBM systems that use the Summit/EXA chipset. | |
105 | In particular, it is needed for the x440. | |
106 | ||
107 | If you don't have one of these computers, you should say N here. | |
108 | ||
109 | config X86_BIGSMP | |
110 | bool "Support for other sub-arch SMP systems with more than 8 CPUs" | |
111 | depends on SMP | |
112 | help | |
113 | This option is needed for the systems that have more than 8 CPUs | |
114 | and if the system is not of any sub-arch type above. | |
115 | ||
116 | If you don't have such a system, you should say N here. | |
117 | ||
118 | config X86_VISWS | |
119 | bool "SGI 320/540 (Visual Workstation)" | |
120 | help | |
121 | The SGI Visual Workstation series is an IA32-based workstation | |
122 | based on SGI systems chips with some legacy PC hardware attached. | |
123 | ||
124 | Say Y here to create a kernel to run on the SGI 320 or 540. | |
125 | ||
126 | A kernel compiled for the Visual Workstation will not run on PCs | |
127 | and vice versa. See <file:Documentation/sgi-visws.txt> for details. | |
128 | ||
129 | config X86_GENERICARCH | |
130 | bool "Generic architecture (Summit, bigsmp, ES7000, default)" | |
131 | depends on SMP | |
132 | help | |
133 | This option compiles in the Summit, bigsmp, ES7000, default subarchitectures. | |
134 | It is intended for a generic binary kernel. | |
135 | ||
136 | config X86_ES7000 | |
137 | bool "Support for Unisys ES7000 IA32 series" | |
138 | depends on SMP | |
139 | help | |
140 | Support for Unisys ES7000 systems. Say 'Y' here if this kernel is | |
141 | supposed to run on an IA32-based Unisys ES7000 system. | |
142 | Only choose this option if you have such a system, otherwise you | |
143 | should say N here. | |
144 | ||
145 | endchoice | |
146 | ||
147 | config ACPI_SRAT | |
148 | bool | |
149 | default y | |
150 | depends on NUMA && (X86_SUMMIT || X86_GENERICARCH) | |
151 | ||
152 | config X86_SUMMIT_NUMA | |
153 | bool | |
154 | default y | |
155 | depends on NUMA && (X86_SUMMIT || X86_GENERICARCH) | |
156 | ||
157 | config X86_CYCLONE_TIMER | |
158 | bool | |
159 | default y | |
160 | depends on X86_SUMMIT || X86_GENERICARCH | |
161 | ||
162 | config ES7000_CLUSTERED_APIC | |
163 | bool | |
164 | default y | |
165 | depends on SMP && X86_ES7000 && MPENTIUMIII | |
166 | ||
96d55b88 | 167 | source "arch/i386/Kconfig.cpu" |
1da177e4 LT |
168 | |
169 | config HPET_TIMER | |
170 | bool "HPET Timer Support" | |
171 | help | |
172 | This enables the use of the HPET for the kernel's internal timer. | |
173 | HPET is the next generation timer replacing legacy 8254s. | |
174 | You can safely choose Y here. However, HPET will only be | |
175 | activated if the platform and the BIOS support this feature. | |
176 | Otherwise the 8254 will be used for timing services. | |
177 | ||
178 | Choose N to continue using the legacy 8254 timer. | |
179 | ||
180 | config HPET_EMULATE_RTC | |
c91096d8 | 181 | bool |
1da177e4 | 182 | depends on HPET_TIMER && RTC=y |
c91096d8 | 183 | default y |
1da177e4 LT |
184 | |
185 | config SMP | |
186 | bool "Symmetric multi-processing support" | |
187 | ---help--- | |
188 | This enables support for systems with more than one CPU. If you have | |
189 | a system with only one CPU, like most personal computers, say N. If | |
190 | you have a system with more than one CPU, say Y. | |
191 | ||
192 | If you say N here, the kernel will run on single and multiprocessor | |
193 | machines, but will use only one CPU of a multiprocessor machine. If | |
194 | you say Y here, the kernel will run on many, but not all, | |
195 | singleprocessor machines. On a singleprocessor machine, the kernel | |
196 | will run faster if you say N here. | |
197 | ||
198 | Note that if you say Y here and choose architecture "586" or | |
199 | "Pentium" under "Processor family", the kernel will not work on 486 | |
200 | architectures. Similarly, multiprocessor kernels for the "PPro" | |
201 | architecture may not work on all Pentium based boards. | |
202 | ||
203 | People using multiprocessor machines who say Y here should also say | |
204 | Y to "Enhanced Real Time Clock Support", below. The "Advanced Power | |
205 | Management" code will be disabled if you say Y here. | |
206 | ||
207 | See also the <file:Documentation/smp.txt>, | |
208 | <file:Documentation/i386/IO-APIC.txt>, | |
209 | <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at | |
210 | <http://www.tldp.org/docs.html#howto>. | |
211 | ||
212 | If you don't know what to do here, say N. | |
213 | ||
214 | config NR_CPUS | |
215 | int "Maximum number of CPUs (2-255)" | |
216 | range 2 255 | |
217 | depends on SMP | |
218 | default "32" if X86_NUMAQ || X86_SUMMIT || X86_BIGSMP || X86_ES7000 | |
219 | default "8" | |
220 | help | |
221 | This allows you to specify the maximum number of CPUs which this | |
222 | kernel will support. The maximum supported value is 255 and the | |
223 | minimum value which makes sense is 2. | |
224 | ||
225 | This is purely to save memory - each supported CPU adds | |
226 | approximately eight kilobytes to the kernel image. | |
227 | ||
228 | config SCHED_SMT | |
229 | bool "SMT (Hyperthreading) scheduler support" | |
230 | depends on SMP | |
231 | default off | |
232 | help | |
233 | SMT scheduler support improves the CPU scheduler's decision making | |
234 | when dealing with Intel Pentium 4 chips with HyperThreading at a | |
235 | cost of slightly increased overhead in some places. If unsure say | |
236 | N here. | |
237 | ||
cc19ca86 | 238 | source "kernel/Kconfig.preempt" |
1da177e4 LT |
239 | |
240 | config X86_UP_APIC | |
241 | bool "Local APIC support on uniprocessors" | |
242 | depends on !SMP && !(X86_VISWS || X86_VOYAGER) | |
243 | help | |
244 | A local APIC (Advanced Programmable Interrupt Controller) is an | |
245 | integrated interrupt controller in the CPU. If you have a single-CPU | |
246 | system which has a processor with a local APIC, you can say Y here to | |
247 | enable and use it. If you say Y here even though your machine doesn't | |
248 | have a local APIC, then the kernel will still run with no slowdown at | |
249 | all. The local APIC supports CPU-generated self-interrupts (timer, | |
250 | performance counters), and the NMI watchdog which detects hard | |
251 | lockups. | |
252 | ||
253 | config X86_UP_IOAPIC | |
254 | bool "IO-APIC support on uniprocessors" | |
255 | depends on X86_UP_APIC | |
256 | help | |
257 | An IO-APIC (I/O Advanced Programmable Interrupt Controller) is an | |
258 | SMP-capable replacement for PC-style interrupt controllers. Most | |
259 | SMP systems and many recent uniprocessor systems have one. | |
260 | ||
261 | If you have a single-CPU system with an IO-APIC, you can say Y here | |
262 | to use it. If you say Y here even though your machine doesn't have | |
263 | an IO-APIC, then the kernel will still run with no slowdown at all. | |
264 | ||
265 | config X86_LOCAL_APIC | |
266 | bool | |
267 | depends on X86_UP_APIC || ((X86_VISWS || SMP) && !X86_VOYAGER) | |
268 | default y | |
269 | ||
270 | config X86_IO_APIC | |
271 | bool | |
272 | depends on X86_UP_IOAPIC || (SMP && !(X86_VISWS || X86_VOYAGER)) | |
273 | default y | |
274 | ||
275 | config X86_VISWS_APIC | |
276 | bool | |
277 | depends on X86_VISWS | |
278 | default y | |
279 | ||
1da177e4 LT |
280 | config X86_MCE |
281 | bool "Machine Check Exception" | |
282 | depends on !X86_VOYAGER | |
283 | ---help--- | |
284 | Machine Check Exception support allows the processor to notify the | |
285 | kernel if it detects a problem (e.g. overheating, component failure). | |
286 | The action the kernel takes depends on the severity of the problem, | |
287 | ranging from a warning message on the console, to halting the machine. | |
288 | Your processor must be a Pentium or newer to support this - check the | |
289 | flags in /proc/cpuinfo for mce. Note that some older Pentium systems | |
290 | have a design flaw which leads to false MCE events - hence MCE is | |
291 | disabled on all P5 processors, unless explicitly enabled with "mce" | |
292 | as a boot argument. Similarly, if MCE is built in and creates a | |
293 | problem on some new non-standard machine, you can boot with "nomce" | |
294 | to disable it. MCE support simply ignores non-MCE processors like | |
295 | the 386 and 486, so nearly everyone can say Y here. | |
296 | ||
297 | config X86_MCE_NONFATAL | |
298 | tristate "Check for non-fatal errors on AMD Athlon/Duron / Intel Pentium 4" | |
299 | depends on X86_MCE | |
300 | help | |
301 | Enabling this feature starts a timer that triggers every 5 seconds which | |
302 | will look at the machine check registers to see if anything happened. | |
303 | Non-fatal problems automatically get corrected (but still logged). | |
304 | Disable this if you don't want to see these messages. | |
305 | Seeing the messages this option prints out may be indicative of dying hardware, | |
306 | or out-of-spec (ie, overclocked) hardware. | |
307 | This option only does something on certain CPUs. | |
308 | (AMD Athlon/Duron and Intel Pentium 4) | |
309 | ||
310 | config X86_MCE_P4THERMAL | |
311 | bool "check for P4 thermal throttling interrupt." | |
312 | depends on X86_MCE && (X86_UP_APIC || SMP) && !X86_VISWS | |
313 | help | |
314 | Enabling this feature will cause a message to be printed when the P4 | |
315 | enters thermal throttling. | |
316 | ||
317 | config TOSHIBA | |
318 | tristate "Toshiba Laptop support" | |
319 | ---help--- | |
320 | This adds a driver to safely access the System Management Mode of | |
321 | the CPU on Toshiba portables with a genuine Toshiba BIOS. It does | |
322 | not work on models with a Phoenix BIOS. The System Management Mode | |
323 | is used to set the BIOS and power saving options on Toshiba portables. | |
324 | ||
325 | For information on utilities to make use of this driver see the | |
326 | Toshiba Linux utilities web site at: | |
327 | <http://www.buzzard.org.uk/toshiba/>. | |
328 | ||
329 | Say Y if you intend to run this kernel on a Toshiba portable. | |
330 | Say N otherwise. | |
331 | ||
332 | config I8K | |
333 | tristate "Dell laptop support" | |
334 | ---help--- | |
335 | This adds a driver to safely access the System Management Mode | |
336 | of the CPU on the Dell Inspiron 8000. The System Management Mode | |
337 | is used to read cpu temperature and cooling fan status and to | |
338 | control the fans on the I8K portables. | |
339 | ||
340 | This driver has been tested only on the Inspiron 8000 but it may | |
341 | also work with other Dell laptops. You can force loading on other | |
342 | models by passing the parameter `force=1' to the module. Use at | |
343 | your own risk. | |
344 | ||
345 | For information on utilities to make use of this driver see the | |
346 | I8K Linux utilities web site at: | |
347 | <http://people.debian.org/~dz/i8k/> | |
348 | ||
349 | Say Y if you intend to run this kernel on a Dell Inspiron 8000. | |
350 | Say N otherwise. | |
351 | ||
a2f7c354 JK |
352 | config X86_REBOOTFIXUPS |
353 | bool "Enable X86 board specific fixups for reboot" | |
354 | depends on X86 | |
355 | default n | |
356 | ---help--- | |
357 | This enables chipset and/or board specific fixups to be done | |
358 | in order to get reboot to work correctly. This is only needed on | |
359 | some combinations of hardware and BIOS. The symptom, for which | |
360 | this config is intended, is when reboot ends with a stalled/hung | |
361 | system. | |
362 | ||
363 | Currently, the only fixup is for the Geode GX1/CS5530A/TROM2.1. | |
364 | combination. | |
365 | ||
366 | Say Y if you want to enable the fixup. Currently, it's safe to | |
367 | enable this option even if you don't need it. | |
368 | Say N otherwise. | |
369 | ||
1da177e4 LT |
370 | config MICROCODE |
371 | tristate "/dev/cpu/microcode - Intel IA32 CPU microcode support" | |
372 | ---help--- | |
373 | If you say Y here and also to "/dev file system support" in the | |
374 | 'File systems' section, you will be able to update the microcode on | |
375 | Intel processors in the IA32 family, e.g. Pentium Pro, Pentium II, | |
376 | Pentium III, Pentium 4, Xeon etc. You will obviously need the | |
377 | actual microcode binary data itself which is not shipped with the | |
378 | Linux kernel. | |
379 | ||
380 | For latest news and information on obtaining all the required | |
381 | ingredients for this driver, check: | |
382 | <http://www.urbanmyth.org/microcode/>. | |
383 | ||
384 | To compile this driver as a module, choose M here: the | |
385 | module will be called microcode. | |
386 | ||
387 | config X86_MSR | |
388 | tristate "/dev/cpu/*/msr - Model-specific register support" | |
389 | help | |
390 | This device gives privileged processes access to the x86 | |
391 | Model-Specific Registers (MSRs). It is a character device with | |
392 | major 202 and minors 0 to 31 for /dev/cpu/0/msr to /dev/cpu/31/msr. | |
393 | MSR accesses are directed to a specific CPU on multi-processor | |
394 | systems. | |
395 | ||
396 | config X86_CPUID | |
397 | tristate "/dev/cpu/*/cpuid - CPU information support" | |
398 | help | |
399 | This device gives processes access to the x86 CPUID instruction to | |
400 | be executed on a specific processor. It is a character device | |
401 | with major 203 and minors 0 to 31 for /dev/cpu/0/cpuid to | |
402 | /dev/cpu/31/cpuid. | |
403 | ||
404 | source "drivers/firmware/Kconfig" | |
405 | ||
406 | choice | |
407 | prompt "High Memory Support" | |
408 | default NOHIGHMEM | |
409 | ||
410 | config NOHIGHMEM | |
411 | bool "off" | |
412 | ---help--- | |
413 | Linux can use up to 64 Gigabytes of physical memory on x86 systems. | |
414 | However, the address space of 32-bit x86 processors is only 4 | |
415 | Gigabytes large. That means that, if you have a large amount of | |
416 | physical memory, not all of it can be "permanently mapped" by the | |
417 | kernel. The physical memory that's not permanently mapped is called | |
418 | "high memory". | |
419 | ||
420 | If you are compiling a kernel which will never run on a machine with | |
421 | more than 1 Gigabyte total physical RAM, answer "off" here (default | |
422 | choice and suitable for most users). This will result in a "3GB/1GB" | |
423 | split: 3GB are mapped so that each process sees a 3GB virtual memory | |
424 | space and the remaining part of the 4GB virtual memory space is used | |
425 | by the kernel to permanently map as much physical memory as | |
426 | possible. | |
427 | ||
428 | If the machine has between 1 and 4 Gigabytes physical RAM, then | |
429 | answer "4GB" here. | |
430 | ||
431 | If more than 4 Gigabytes is used then answer "64GB" here. This | |
432 | selection turns Intel PAE (Physical Address Extension) mode on. | |
433 | PAE implements 3-level paging on IA32 processors. PAE is fully | |
434 | supported by Linux, PAE mode is implemented on all recent Intel | |
435 | processors (Pentium Pro and better). NOTE: If you say "64GB" here, | |
436 | then the kernel will not boot on CPUs that don't support PAE! | |
437 | ||
438 | The actual amount of total physical memory will either be | |
439 | auto detected or can be forced by using a kernel command line option | |
440 | such as "mem=256M". (Try "man bootparam" or see the documentation of | |
441 | your boot loader (lilo or loadlin) about how to pass options to the | |
442 | kernel at boot time.) | |
443 | ||
444 | If unsure, say "off". | |
445 | ||
446 | config HIGHMEM4G | |
447 | bool "4GB" | |
448 | help | |
449 | Select this if you have a 32-bit processor and between 1 and 4 | |
450 | gigabytes of physical RAM. | |
451 | ||
452 | config HIGHMEM64G | |
453 | bool "64GB" | |
454 | help | |
455 | Select this if you have a 32-bit processor and more than 4 | |
456 | gigabytes of physical RAM. | |
457 | ||
458 | endchoice | |
459 | ||
460 | config HIGHMEM | |
461 | bool | |
462 | depends on HIGHMEM64G || HIGHMEM4G | |
463 | default y | |
464 | ||
465 | config X86_PAE | |
466 | bool | |
467 | depends on HIGHMEM64G | |
468 | default y | |
469 | ||
470 | # Common NUMA Features | |
471 | config NUMA | |
472 | bool "Numa Memory Allocation and Scheduler Support" | |
473 | depends on SMP && HIGHMEM64G && (X86_NUMAQ || X86_GENERICARCH || (X86_SUMMIT && ACPI)) | |
474 | default n if X86_PC | |
475 | default y if (X86_NUMAQ || X86_SUMMIT) | |
476 | ||
477 | # Need comments to help the hapless user trying to turn on NUMA support | |
478 | comment "NUMA (NUMA-Q) requires SMP, 64GB highmem support" | |
479 | depends on X86_NUMAQ && (!HIGHMEM64G || !SMP) | |
480 | ||
481 | comment "NUMA (Summit) requires SMP, 64GB highmem support, ACPI" | |
482 | depends on X86_SUMMIT && (!HIGHMEM64G || !ACPI) | |
483 | ||
1da177e4 LT |
484 | config HAVE_ARCH_BOOTMEM_NODE |
485 | bool | |
486 | depends on NUMA | |
487 | default y | |
488 | ||
af705362 | 489 | config ARCH_HAVE_MEMORY_PRESENT |
1da177e4 LT |
490 | bool |
491 | depends on DISCONTIGMEM | |
492 | default y | |
493 | ||
494 | config NEED_NODE_MEMMAP_SIZE | |
495 | bool | |
05b79bdc | 496 | depends on DISCONTIGMEM || SPARSEMEM |
1da177e4 LT |
497 | default y |
498 | ||
6f167ec7 DH |
499 | config HAVE_ARCH_ALLOC_REMAP |
500 | bool | |
501 | depends on NUMA | |
502 | default y | |
503 | ||
215c3409 AW |
504 | config ARCH_FLATMEM_ENABLE |
505 | def_bool y | |
506 | depends on (ARCH_SELECT_MEMORY_MODEL && X86_PC) | |
507 | ||
05b79bdc AW |
508 | config ARCH_DISCONTIGMEM_ENABLE |
509 | def_bool y | |
510 | depends on NUMA | |
511 | ||
512 | config ARCH_DISCONTIGMEM_DEFAULT | |
513 | def_bool y | |
514 | depends on NUMA | |
515 | ||
516 | config ARCH_SPARSEMEM_ENABLE | |
517 | def_bool y | |
215c3409 AW |
518 | depends on (NUMA || (X86_PC && EXPERIMENTAL)) |
519 | select SPARSEMEM_STATIC | |
05b79bdc AW |
520 | |
521 | config ARCH_SELECT_MEMORY_MODEL | |
522 | def_bool y | |
523 | depends on ARCH_SPARSEMEM_ENABLE | |
524 | ||
3f22ab27 DH |
525 | source "mm/Kconfig" |
526 | ||
b159d43f AW |
527 | config HAVE_ARCH_EARLY_PFN_TO_NID |
528 | bool | |
529 | default y | |
d41dee36 | 530 | depends on NUMA |
b159d43f | 531 | |
1da177e4 LT |
532 | config HIGHPTE |
533 | bool "Allocate 3rd-level pagetables from highmem" | |
534 | depends on HIGHMEM4G || HIGHMEM64G | |
535 | help | |
536 | The VM uses one page table entry for each page of physical memory. | |
537 | For systems with a lot of RAM, this can be wasteful of precious | |
538 | low memory. Setting this option will put user-space page table | |
539 | entries in high memory. | |
540 | ||
541 | config MATH_EMULATION | |
542 | bool "Math emulation" | |
543 | ---help--- | |
544 | Linux can emulate a math coprocessor (used for floating point | |
545 | operations) if you don't have one. 486DX and Pentium processors have | |
546 | a math coprocessor built in, 486SX and 386 do not, unless you added | |
547 | a 487DX or 387, respectively. (The messages during boot time can | |
548 | give you some hints here ["man dmesg"].) Everyone needs either a | |
549 | coprocessor or this emulation. | |
550 | ||
551 | If you don't have a math coprocessor, you need to say Y here; if you | |
552 | say Y here even though you have a coprocessor, the coprocessor will | |
553 | be used nevertheless. (This behavior can be changed with the kernel | |
554 | command line option "no387", which comes handy if your coprocessor | |
555 | is broken. Try "man bootparam" or see the documentation of your boot | |
556 | loader (lilo or loadlin) about how to pass options to the kernel at | |
557 | boot time.) This means that it is a good idea to say Y here if you | |
558 | intend to use this kernel on different machines. | |
559 | ||
560 | More information about the internals of the Linux math coprocessor | |
561 | emulation can be found in <file:arch/i386/math-emu/README>. | |
562 | ||
563 | If you are not sure, say Y; apart from resulting in a 66 KB bigger | |
564 | kernel, it won't hurt. | |
565 | ||
566 | config MTRR | |
567 | bool "MTRR (Memory Type Range Register) support" | |
568 | ---help--- | |
569 | On Intel P6 family processors (Pentium Pro, Pentium II and later) | |
570 | the Memory Type Range Registers (MTRRs) may be used to control | |
571 | processor access to memory ranges. This is most useful if you have | |
572 | a video (VGA) card on a PCI or AGP bus. Enabling write-combining | |
573 | allows bus write transfers to be combined into a larger transfer | |
574 | before bursting over the PCI/AGP bus. This can increase performance | |
575 | of image write operations 2.5 times or more. Saying Y here creates a | |
576 | /proc/mtrr file which may be used to manipulate your processor's | |
577 | MTRRs. Typically the X server should use this. | |
578 | ||
579 | This code has a reasonably generic interface so that similar | |
580 | control registers on other processors can be easily supported | |
581 | as well: | |
582 | ||
583 | The Cyrix 6x86, 6x86MX and M II processors have Address Range | |
584 | Registers (ARRs) which provide a similar functionality to MTRRs. For | |
585 | these, the ARRs are used to emulate the MTRRs. | |
586 | The AMD K6-2 (stepping 8 and above) and K6-3 processors have two | |
587 | MTRRs. The Centaur C6 (WinChip) has 8 MCRs, allowing | |
588 | write-combining. All of these processors are supported by this code | |
589 | and it makes sense to say Y here if you have one of them. | |
590 | ||
591 | Saying Y here also fixes a problem with buggy SMP BIOSes which only | |
592 | set the MTRRs for the boot CPU and not for the secondary CPUs. This | |
593 | can lead to all sorts of problems, so it's good to say Y here. | |
594 | ||
595 | You can safely say Y even if your machine doesn't have MTRRs, you'll | |
596 | just add about 9 KB to your kernel. | |
597 | ||
598 | See <file:Documentation/mtrr.txt> for more information. | |
599 | ||
600 | config EFI | |
601 | bool "Boot from EFI support (EXPERIMENTAL)" | |
602 | depends on ACPI | |
603 | default n | |
604 | ---help--- | |
605 | This enables the the kernel to boot on EFI platforms using | |
606 | system configuration information passed to it from the firmware. | |
607 | This also enables the kernel to use any EFI runtime services that are | |
608 | available (such as the EFI variable services). | |
609 | ||
610 | This option is only useful on systems that have EFI firmware | |
611 | and will result in a kernel image that is ~8k larger. In addition, | |
612 | you must use the latest ELILO loader available at | |
613 | <http://elilo.sourceforge.net> in order to take advantage of | |
614 | kernel initialization using EFI information (neither GRUB nor LILO know | |
615 | anything about EFI). However, even with this option, the resultant | |
616 | kernel should continue to boot on existing non-EFI platforms. | |
617 | ||
618 | config IRQBALANCE | |
619 | bool "Enable kernel irq balancing" | |
620 | depends on SMP && X86_IO_APIC | |
621 | default y | |
622 | help | |
623 | The default yes will allow the kernel to do irq load balancing. | |
624 | Saying no will keep the kernel from doing irq load balancing. | |
625 | ||
1da177e4 LT |
626 | # turning this on wastes a bunch of space. |
627 | # Summit needs it only when NUMA is on | |
628 | config BOOT_IOREMAP | |
629 | bool | |
630 | depends on (((X86_SUMMIT || X86_GENERICARCH) && NUMA) || (X86 && EFI)) | |
631 | default y | |
632 | ||
633 | config REGPARM | |
634 | bool "Use register arguments (EXPERIMENTAL)" | |
635 | depends on EXPERIMENTAL | |
636 | default n | |
637 | help | |
638 | Compile the kernel with -mregparm=3. This uses a different ABI | |
639 | and passes the first three arguments of a function call in registers. | |
640 | This will probably break binary only modules. | |
641 | ||
1da177e4 LT |
642 | config SECCOMP |
643 | bool "Enable seccomp to safely compute untrusted bytecode" | |
644 | depends on PROC_FS | |
645 | default y | |
646 | help | |
647 | This kernel feature is useful for number crunching applications | |
648 | that may need to compute untrusted bytecode during their | |
649 | execution. By using pipes or other transports made available to | |
650 | the process as file descriptors supporting the read/write | |
651 | syscalls, it's possible to isolate those applications in | |
652 | their own address space using seccomp. Once seccomp is | |
653 | enabled via /proc/<pid>/seccomp, it cannot be disabled | |
654 | and the task is only allowed to execute a few safe syscalls | |
655 | defined by each seccomp mode. | |
656 | ||
657 | If unsure, say Y. Only embedded should say N here. | |
658 | ||
59121003 CL |
659 | source kernel/Kconfig.hz |
660 | ||
5033cba0 EB |
661 | config KEXEC |
662 | bool "kexec system call (EXPERIMENTAL)" | |
663 | depends on EXPERIMENTAL | |
664 | help | |
665 | kexec is a system call that implements the ability to shutdown your | |
666 | current kernel, and to start another kernel. It is like a reboot | |
667 | but it is indepedent of the system firmware. And like a reboot | |
668 | you can start any kernel with it, not just Linux. | |
669 | ||
670 | The name comes from the similiarity to the exec system call. | |
671 | ||
672 | It is an ongoing process to be certain the hardware in a machine | |
673 | is properly shutdown, so do not be surprised if this code does not | |
674 | initially work for you. It may help to enable device hotplugging | |
675 | support. As of this writing the exact hardware interface is | |
676 | strongly in flux, so no good recommendation can be made. | |
677 | ||
5f016456 VG |
678 | config CRASH_DUMP |
679 | bool "kernel crash dumps (EXPERIMENTAL)" | |
5f016456 VG |
680 | depends on EXPERIMENTAL |
681 | depends on HIGHMEM | |
682 | help | |
683 | Generate crash dump after being started by kexec. | |
05970d47 MS |
684 | |
685 | config PHYSICAL_START | |
686 | hex "Physical address where the kernel is loaded" if (EMBEDDED || CRASH_DUMP) | |
687 | ||
688 | default "0x1000000" if CRASH_DUMP | |
689 | default "0x100000" | |
690 | help | |
691 | This gives the physical address where the kernel is loaded. Normally | |
692 | for regular kernels this value is 0x100000 (1MB). But in the case | |
693 | of kexec on panic the fail safe kernel needs to run at a different | |
694 | address than the panic-ed kernel. This option is used to set the load | |
695 | address for kernels used to capture crash dump on being kexec'ed | |
696 | after panic. The default value for crash dump kernels is | |
697 | 0x1000000 (16MB). This can also be set based on the "X" value as | |
698 | specified in the "crashkernel=YM@XM" command line boot parameter | |
699 | passed to the panic-ed kernel. Typically this parameter is set as | |
700 | crashkernel=64M@16M. Please take a look at | |
701 | Documentation/kdump/kdump.txt for more details about crash dumps. | |
702 | ||
703 | Don't change this unless you know what you are doing. | |
704 | ||
1da177e4 LT |
705 | endmenu |
706 | ||
707 | ||
708 | menu "Power management options (ACPI, APM)" | |
709 | depends on !X86_VOYAGER | |
710 | ||
711 | source kernel/power/Kconfig | |
712 | ||
713 | source "drivers/acpi/Kconfig" | |
714 | ||
715 | menu "APM (Advanced Power Management) BIOS Support" | |
716 | depends on PM && !X86_VISWS | |
717 | ||
718 | config APM | |
719 | tristate "APM (Advanced Power Management) BIOS support" | |
987d4613 | 720 | depends on PM |
1da177e4 LT |
721 | ---help--- |
722 | APM is a BIOS specification for saving power using several different | |
723 | techniques. This is mostly useful for battery powered laptops with | |
724 | APM compliant BIOSes. If you say Y here, the system time will be | |
725 | reset after a RESUME operation, the /proc/apm device will provide | |
726 | battery status information, and user-space programs will receive | |
727 | notification of APM "events" (e.g. battery status change). | |
728 | ||
729 | If you select "Y" here, you can disable actual use of the APM | |
730 | BIOS by passing the "apm=off" option to the kernel at boot time. | |
731 | ||
732 | Note that the APM support is almost completely disabled for | |
733 | machines with more than one CPU. | |
734 | ||
735 | In order to use APM, you will need supporting software. For location | |
736 | and more information, read <file:Documentation/pm.txt> and the | |
737 | Battery Powered Linux mini-HOWTO, available from | |
738 | <http://www.tldp.org/docs.html#howto>. | |
739 | ||
740 | This driver does not spin down disk drives (see the hdparm(8) | |
741 | manpage ("man 8 hdparm") for that), and it doesn't turn off | |
742 | VESA-compliant "green" monitors. | |
743 | ||
744 | This driver does not support the TI 4000M TravelMate and the ACER | |
745 | 486/DX4/75 because they don't have compliant BIOSes. Many "green" | |
746 | desktop machines also don't have compliant BIOSes, and this driver | |
747 | may cause those machines to panic during the boot phase. | |
748 | ||
749 | Generally, if you don't have a battery in your machine, there isn't | |
750 | much point in using this driver and you should say N. If you get | |
751 | random kernel OOPSes or reboots that don't seem to be related to | |
752 | anything, try disabling/enabling this option (or disabling/enabling | |
753 | APM in your BIOS). | |
754 | ||
755 | Some other things you should try when experiencing seemingly random, | |
756 | "weird" problems: | |
757 | ||
758 | 1) make sure that you have enough swap space and that it is | |
759 | enabled. | |
760 | 2) pass the "no-hlt" option to the kernel | |
761 | 3) switch on floating point emulation in the kernel and pass | |
762 | the "no387" option to the kernel | |
763 | 4) pass the "floppy=nodma" option to the kernel | |
764 | 5) pass the "mem=4M" option to the kernel (thereby disabling | |
765 | all but the first 4 MB of RAM) | |
766 | 6) make sure that the CPU is not over clocked. | |
767 | 7) read the sig11 FAQ at <http://www.bitwizard.nl/sig11/> | |
768 | 8) disable the cache from your BIOS settings | |
769 | 9) install a fan for the video card or exchange video RAM | |
770 | 10) install a better fan for the CPU | |
771 | 11) exchange RAM chips | |
772 | 12) exchange the motherboard. | |
773 | ||
774 | To compile this driver as a module, choose M here: the | |
775 | module will be called apm. | |
776 | ||
777 | config APM_IGNORE_USER_SUSPEND | |
778 | bool "Ignore USER SUSPEND" | |
779 | depends on APM | |
780 | help | |
781 | This option will ignore USER SUSPEND requests. On machines with a | |
782 | compliant APM BIOS, you want to say N. However, on the NEC Versa M | |
783 | series notebooks, it is necessary to say Y because of a BIOS bug. | |
784 | ||
785 | config APM_DO_ENABLE | |
786 | bool "Enable PM at boot time" | |
787 | depends on APM | |
788 | ---help--- | |
789 | Enable APM features at boot time. From page 36 of the APM BIOS | |
790 | specification: "When disabled, the APM BIOS does not automatically | |
791 | power manage devices, enter the Standby State, enter the Suspend | |
792 | State, or take power saving steps in response to CPU Idle calls." | |
793 | This driver will make CPU Idle calls when Linux is idle (unless this | |
794 | feature is turned off -- see "Do CPU IDLE calls", below). This | |
795 | should always save battery power, but more complicated APM features | |
796 | will be dependent on your BIOS implementation. You may need to turn | |
797 | this option off if your computer hangs at boot time when using APM | |
798 | support, or if it beeps continuously instead of suspending. Turn | |
799 | this off if you have a NEC UltraLite Versa 33/C or a Toshiba | |
800 | T400CDT. This is off by default since most machines do fine without | |
801 | this feature. | |
802 | ||
803 | config APM_CPU_IDLE | |
804 | bool "Make CPU Idle calls when idle" | |
805 | depends on APM | |
806 | help | |
807 | Enable calls to APM CPU Idle/CPU Busy inside the kernel's idle loop. | |
808 | On some machines, this can activate improved power savings, such as | |
809 | a slowed CPU clock rate, when the machine is idle. These idle calls | |
810 | are made after the idle loop has run for some length of time (e.g., | |
811 | 333 mS). On some machines, this will cause a hang at boot time or | |
812 | whenever the CPU becomes idle. (On machines with more than one CPU, | |
813 | this option does nothing.) | |
814 | ||
815 | config APM_DISPLAY_BLANK | |
816 | bool "Enable console blanking using APM" | |
817 | depends on APM | |
818 | help | |
819 | Enable console blanking using the APM. Some laptops can use this to | |
820 | turn off the LCD backlight when the screen blanker of the Linux | |
821 | virtual console blanks the screen. Note that this is only used by | |
822 | the virtual console screen blanker, and won't turn off the backlight | |
823 | when using the X Window system. This also doesn't have anything to | |
824 | do with your VESA-compliant power-saving monitor. Further, this | |
825 | option doesn't work for all laptops -- it might not turn off your | |
826 | backlight at all, or it might print a lot of errors to the console, | |
827 | especially if you are using gpm. | |
828 | ||
829 | config APM_RTC_IS_GMT | |
830 | bool "RTC stores time in GMT" | |
831 | depends on APM | |
832 | help | |
833 | Say Y here if your RTC (Real Time Clock a.k.a. hardware clock) | |
834 | stores the time in GMT (Greenwich Mean Time). Say N if your RTC | |
835 | stores localtime. | |
836 | ||
837 | It is in fact recommended to store GMT in your RTC, because then you | |
838 | don't have to worry about daylight savings time changes. The only | |
839 | reason not to use GMT in your RTC is if you also run a broken OS | |
840 | that doesn't understand GMT. | |
841 | ||
842 | config APM_ALLOW_INTS | |
843 | bool "Allow interrupts during APM BIOS calls" | |
844 | depends on APM | |
845 | help | |
846 | Normally we disable external interrupts while we are making calls to | |
847 | the APM BIOS as a measure to lessen the effects of a badly behaving | |
848 | BIOS implementation. The BIOS should reenable interrupts if it | |
849 | needs to. Unfortunately, some BIOSes do not -- especially those in | |
850 | many of the newer IBM Thinkpads. If you experience hangs when you | |
851 | suspend, try setting this to Y. Otherwise, say N. | |
852 | ||
853 | config APM_REAL_MODE_POWER_OFF | |
854 | bool "Use real mode APM BIOS call to power off" | |
855 | depends on APM | |
856 | help | |
857 | Use real mode APM BIOS calls to switch off the computer. This is | |
858 | a work-around for a number of buggy BIOSes. Switch this option on if | |
859 | your computer crashes instead of powering off properly. | |
860 | ||
861 | endmenu | |
862 | ||
863 | source "arch/i386/kernel/cpu/cpufreq/Kconfig" | |
864 | ||
865 | endmenu | |
866 | ||
867 | menu "Bus options (PCI, PCMCIA, EISA, MCA, ISA)" | |
868 | ||
869 | config PCI | |
870 | bool "PCI support" if !X86_VISWS | |
871 | depends on !X86_VOYAGER | |
872 | default y if X86_VISWS | |
873 | help | |
874 | Find out whether you have a PCI motherboard. PCI is the name of a | |
875 | bus system, i.e. the way the CPU talks to the other stuff inside | |
876 | your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or | |
877 | VESA. If you have PCI, say Y, otherwise N. | |
878 | ||
879 | The PCI-HOWTO, available from | |
880 | <http://www.tldp.org/docs.html#howto>, contains valuable | |
881 | information about which PCI hardware does work under Linux and which | |
882 | doesn't. | |
883 | ||
884 | choice | |
885 | prompt "PCI access mode" | |
886 | depends on PCI && !X86_VISWS | |
887 | default PCI_GOANY | |
888 | ---help--- | |
889 | On PCI systems, the BIOS can be used to detect the PCI devices and | |
890 | determine their configuration. However, some old PCI motherboards | |
891 | have BIOS bugs and may crash if this is done. Also, some embedded | |
892 | PCI-based systems don't have any BIOS at all. Linux can also try to | |
893 | detect the PCI hardware directly without using the BIOS. | |
894 | ||
895 | With this option, you can specify how Linux should detect the | |
896 | PCI devices. If you choose "BIOS", the BIOS will be used, | |
897 | if you choose "Direct", the BIOS won't be used, and if you | |
898 | choose "MMConfig", then PCI Express MMCONFIG will be used. | |
899 | If you choose "Any", the kernel will try MMCONFIG, then the | |
900 | direct access method and falls back to the BIOS if that doesn't | |
901 | work. If unsure, go with the default, which is "Any". | |
902 | ||
903 | config PCI_GOBIOS | |
904 | bool "BIOS" | |
905 | ||
906 | config PCI_GOMMCONFIG | |
907 | bool "MMConfig" | |
908 | ||
909 | config PCI_GODIRECT | |
910 | bool "Direct" | |
911 | ||
912 | config PCI_GOANY | |
913 | bool "Any" | |
914 | ||
915 | endchoice | |
916 | ||
917 | config PCI_BIOS | |
918 | bool | |
919 | depends on !X86_VISWS && PCI && (PCI_GOBIOS || PCI_GOANY) | |
920 | default y | |
921 | ||
922 | config PCI_DIRECT | |
923 | bool | |
924 | depends on PCI && ((PCI_GODIRECT || PCI_GOANY) || X86_VISWS) | |
925 | default y | |
926 | ||
927 | config PCI_MMCONFIG | |
928 | bool | |
8aadff7d | 929 | depends on PCI && ACPI && (PCI_GOMMCONFIG || PCI_GOANY) |
1da177e4 LT |
930 | default y |
931 | ||
932 | source "drivers/pci/pcie/Kconfig" | |
933 | ||
934 | source "drivers/pci/Kconfig" | |
935 | ||
5cae841b AV |
936 | config ISA_DMA_API |
937 | bool | |
938 | default y | |
939 | ||
1da177e4 LT |
940 | config ISA |
941 | bool "ISA support" | |
942 | depends on !(X86_VOYAGER || X86_VISWS) | |
943 | help | |
944 | Find out whether you have ISA slots on your motherboard. ISA is the | |
945 | name of a bus system, i.e. the way the CPU talks to the other stuff | |
946 | inside your box. Other bus systems are PCI, EISA, MicroChannel | |
947 | (MCA) or VESA. ISA is an older system, now being displaced by PCI; | |
948 | newer boards don't support it. If you have ISA, say Y, otherwise N. | |
949 | ||
950 | config EISA | |
951 | bool "EISA support" | |
952 | depends on ISA | |
953 | ---help--- | |
954 | The Extended Industry Standard Architecture (EISA) bus was | |
955 | developed as an open alternative to the IBM MicroChannel bus. | |
956 | ||
957 | The EISA bus provided some of the features of the IBM MicroChannel | |
958 | bus while maintaining backward compatibility with cards made for | |
959 | the older ISA bus. The EISA bus saw limited use between 1988 and | |
960 | 1995 when it was made obsolete by the PCI bus. | |
961 | ||
962 | Say Y here if you are building a kernel for an EISA-based machine. | |
963 | ||
964 | Otherwise, say N. | |
965 | ||
966 | source "drivers/eisa/Kconfig" | |
967 | ||
968 | config MCA | |
969 | bool "MCA support" if !(X86_VISWS || X86_VOYAGER) | |
970 | default y if X86_VOYAGER | |
971 | help | |
972 | MicroChannel Architecture is found in some IBM PS/2 machines and | |
973 | laptops. It is a bus system similar to PCI or ISA. See | |
974 | <file:Documentation/mca.txt> (and especially the web page given | |
975 | there) before attempting to build an MCA bus kernel. | |
976 | ||
977 | source "drivers/mca/Kconfig" | |
978 | ||
979 | config SCx200 | |
980 | tristate "NatSemi SCx200 support" | |
981 | depends on !X86_VOYAGER | |
982 | help | |
983 | This provides basic support for the National Semiconductor SCx200 | |
984 | processor. Right now this is just a driver for the GPIO pins. | |
985 | ||
986 | If you don't know what to do here, say N. | |
987 | ||
988 | This support is also available as a module. If compiled as a | |
989 | module, it will be called scx200. | |
990 | ||
f3705136 ZM |
991 | config HOTPLUG_CPU |
992 | bool "Support for hot-pluggable CPUs (EXPERIMENTAL)" | |
993 | depends on SMP && HOTPLUG && EXPERIMENTAL | |
994 | ---help--- | |
995 | Say Y here to experiment with turning CPUs off and on. CPUs | |
996 | can be controlled through /sys/devices/system/cpu. | |
997 | ||
998 | Say N. | |
999 | ||
1da177e4 LT |
1000 | source "drivers/pcmcia/Kconfig" |
1001 | ||
1002 | source "drivers/pci/hotplug/Kconfig" | |
1003 | ||
1004 | endmenu | |
1005 | ||
1006 | menu "Executable file formats" | |
1007 | ||
1008 | source "fs/Kconfig.binfmt" | |
1009 | ||
1010 | endmenu | |
1011 | ||
d5950b43 SR |
1012 | source "net/Kconfig" |
1013 | ||
1da177e4 LT |
1014 | source "drivers/Kconfig" |
1015 | ||
1016 | source "fs/Kconfig" | |
1017 | ||
cd6b0762 PP |
1018 | menu "Instrumentation Support" |
1019 | depends on EXPERIMENTAL | |
1020 | ||
1da177e4 LT |
1021 | source "arch/i386/oprofile/Kconfig" |
1022 | ||
cd6b0762 PP |
1023 | config KPROBES |
1024 | bool "Kprobes (EXPERIMENTAL)" | |
1025 | help | |
1026 | Kprobes allows you to trap at almost any kernel address and | |
1027 | execute a callback function. register_kprobe() establishes | |
1028 | a probepoint and specifies the callback. Kprobes is useful | |
1029 | for kernel debugging, non-intrusive instrumentation and testing. | |
1030 | If in doubt, say "N". | |
1031 | endmenu | |
1032 | ||
1da177e4 LT |
1033 | source "arch/i386/Kconfig.debug" |
1034 | ||
1035 | source "security/Kconfig" | |
1036 | ||
1037 | source "crypto/Kconfig" | |
1038 | ||
1039 | source "lib/Kconfig" | |
1040 | ||
1041 | # | |
1042 | # Use the generic interrupt handling code in kernel/irq/: | |
1043 | # | |
1044 | config GENERIC_HARDIRQS | |
1045 | bool | |
1046 | default y | |
1047 | ||
1048 | config GENERIC_IRQ_PROBE | |
1049 | bool | |
1050 | default y | |
1051 | ||
54d5d424 AR |
1052 | config GENERIC_PENDING_IRQ |
1053 | bool | |
1054 | depends on GENERIC_HARDIRQS && SMP | |
1055 | default y | |
1056 | ||
1da177e4 LT |
1057 | config X86_SMP |
1058 | bool | |
1059 | depends on SMP && !X86_VOYAGER | |
1060 | default y | |
1061 | ||
1062 | config X86_HT | |
1063 | bool | |
1064 | depends on SMP && !(X86_VISWS || X86_VOYAGER) | |
1065 | default y | |
1066 | ||
1067 | config X86_BIOS_REBOOT | |
1068 | bool | |
1069 | depends on !(X86_VISWS || X86_VOYAGER) | |
1070 | default y | |
1071 | ||
1072 | config X86_TRAMPOLINE | |
1073 | bool | |
1074 | depends on X86_SMP || (X86_VOYAGER && SMP) | |
1075 | default y | |
97fc79f9 TG |
1076 | |
1077 | config KTIME_SCALAR | |
1078 | bool | |
1079 | default y |