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 | # Note: ISA is disabled and will hopefully never be enabled. | |
6 | # If you managed to buy an ISA x86-64 box you'll have to fix all the | |
7 | # ISA drivers you need yourself. | |
8 | # | |
9 | ||
10 | mainmenu "Linux Kernel Configuration" | |
11 | ||
12 | config X86_64 | |
13 | bool | |
14 | default y | |
15 | help | |
16 | Port to the x86-64 architecture. x86-64 is a 64-bit extension to the | |
17 | classical 32-bit x86 architecture. For details see | |
18 | <http://www.x86-64.org/>. | |
19 | ||
20 | config 64BIT | |
21 | def_bool y | |
22 | ||
23 | config X86 | |
24 | bool | |
25 | default y | |
26 | ||
1489939f | 27 | config GENERIC_TIME |
28 | bool | |
29 | default y | |
30 | ||
7460ed28 | 31 | config GENERIC_TIME_VSYSCALL |
32 | bool | |
33 | default y | |
34 | ||
af74522a TG |
35 | config GENERIC_CMOS_UPDATE |
36 | bool | |
37 | default y | |
38 | ||
89b2bbd6 TG |
39 | config CLOCKSOURCE_WATCHDOG |
40 | bool | |
41 | default y | |
42 | ||
b8ce3359 TG |
43 | config GENERIC_CLOCKEVENTS |
44 | bool | |
45 | default y | |
46 | ||
47 | config GENERIC_CLOCKEVENTS_BROADCAST | |
ba7eda4c TG |
48 | bool |
49 | default y | |
50 | ||
fb0e7942 CL |
51 | config ZONE_DMA32 |
52 | bool | |
53 | default y | |
54 | ||
1e950527 IM |
55 | config LOCKDEP_SUPPORT |
56 | bool | |
57 | default y | |
58 | ||
21b32bbf IM |
59 | config STACKTRACE_SUPPORT |
60 | bool | |
61 | default y | |
62 | ||
52fdd089 BL |
63 | config SEMAPHORE_SLEEPERS |
64 | bool | |
65 | default y | |
66 | ||
1da177e4 LT |
67 | config MMU |
68 | bool | |
69 | default y | |
70 | ||
5ac6da66 CL |
71 | config ZONE_DMA |
72 | bool | |
73 | default y | |
74 | ||
1da177e4 LT |
75 | config ISA |
76 | bool | |
77 | ||
78 | config SBUS | |
79 | bool | |
80 | ||
81 | config RWSEM_GENERIC_SPINLOCK | |
82 | bool | |
83 | default y | |
84 | ||
85 | config RWSEM_XCHGADD_ALGORITHM | |
86 | bool | |
87 | ||
f33e2fba AM |
88 | config GENERIC_HWEIGHT |
89 | bool | |
90 | default y | |
91 | ||
1da177e4 LT |
92 | config GENERIC_CALIBRATE_DELAY |
93 | bool | |
94 | default y | |
95 | ||
96 | config X86_CMPXCHG | |
97 | bool | |
98 | default y | |
99 | ||
100 | config EARLY_PRINTK | |
101 | bool | |
102 | default y | |
103 | ||
104 | config GENERIC_ISA_DMA | |
105 | bool | |
106 | default y | |
107 | ||
108 | config GENERIC_IOMAP | |
109 | bool | |
110 | default y | |
111 | ||
a08b6b79 Z |
112 | config ARCH_MAY_HAVE_PC_FDC |
113 | bool | |
114 | default y | |
115 | ||
5cb248ab MG |
116 | config ARCH_POPULATES_NODE_MAP |
117 | def_bool y | |
118 | ||
e9928674 AK |
119 | config DMI |
120 | bool | |
121 | default y | |
122 | ||
e65e1fc2 AV |
123 | config AUDIT_ARCH |
124 | bool | |
125 | default y | |
126 | ||
c31a0bf3 JF |
127 | config GENERIC_BUG |
128 | bool | |
129 | default y | |
130 | depends on BUG | |
131 | ||
f0d1b0b3 DH |
132 | config ARCH_HAS_ILOG2_U32 |
133 | bool | |
134 | default n | |
135 | ||
136 | config ARCH_HAS_ILOG2_U64 | |
137 | bool | |
138 | default n | |
139 | ||
1da177e4 LT |
140 | source "init/Kconfig" |
141 | ||
142 | ||
143 | menu "Processor type and features" | |
144 | ||
ba7eda4c TG |
145 | source "kernel/time/Kconfig" |
146 | ||
79f12614 RT |
147 | choice |
148 | prompt "Subarchitecture Type" | |
149 | default X86_PC | |
150 | ||
151 | config X86_PC | |
152 | bool "PC-compatible" | |
153 | help | |
154 | Choose this option if your computer is a standard PC or compatible. | |
155 | ||
156 | config X86_VSMP | |
157 | bool "Support for ScaleMP vSMP" | |
f157cbb1 | 158 | depends on PCI |
79f12614 RT |
159 | help |
160 | Support for ScaleMP vSMP systems. Say 'Y' here if this kernel is | |
161 | supposed to run on these EM64T-based machines. Only choose this option | |
162 | if you have one of these machines. | |
163 | ||
164 | endchoice | |
165 | ||
1da177e4 LT |
166 | choice |
167 | prompt "Processor family" | |
71381998 | 168 | default GENERIC_CPU |
1da177e4 LT |
169 | |
170 | config MK8 | |
171 | bool "AMD-Opteron/Athlon64" | |
172 | help | |
173 | Optimize for AMD Opteron/Athlon64/Hammer/K8 CPUs. | |
174 | ||
175 | config MPSC | |
71381998 | 176 | bool "Intel P4 / older Netburst based Xeon" |
1da177e4 | 177 | help |
71381998 AK |
178 | Optimize for Intel Pentium 4 and older Nocona/Dempsey Xeon CPUs |
179 | with Intel Extended Memory 64 Technology(EM64T). For details see | |
1da177e4 | 180 | <http://www.intel.com/technology/64bitextensions/>. |
edf8dd36 NK |
181 | Note that the latest Xeons (Xeon 51xx and 53xx) are not based on the |
182 | Netburst core and shouldn't use this option. You can distinguish them | |
71381998 | 183 | using the cpu family field |
edf8dd36 NK |
184 | in /proc/cpuinfo. Family 15 is an older Xeon, Family 6 a newer one |
185 | (this rule only applies to systems that support EM64T) | |
71381998 AK |
186 | |
187 | config MCORE2 | |
188 | bool "Intel Core2 / newer Xeon" | |
189 | help | |
190 | Optimize for Intel Core2 and newer Xeons (51xx) | |
edf8dd36 NK |
191 | You can distinguish the newer Xeons from the older ones using |
192 | the cpu family field in /proc/cpuinfo. 15 is an older Xeon | |
71381998 AK |
193 | (use CONFIG_MPSC then), 6 is a newer one. This rule only |
194 | applies to CPUs that support EM64T. | |
1da177e4 LT |
195 | |
196 | config GENERIC_CPU | |
197 | bool "Generic-x86-64" | |
198 | help | |
199 | Generic x86-64 CPU. | |
71381998 | 200 | Run equally well on all x86-64 CPUs. |
1da177e4 LT |
201 | |
202 | endchoice | |
203 | ||
204 | # | |
205 | # Define implied options from the CPU selection here | |
206 | # | |
207 | config X86_L1_CACHE_BYTES | |
208 | int | |
209 | default "128" if GENERIC_CPU || MPSC | |
71381998 | 210 | default "64" if MK8 || MCORE2 |
1da177e4 LT |
211 | |
212 | config X86_L1_CACHE_SHIFT | |
213 | int | |
214 | default "7" if GENERIC_CPU || MPSC | |
71381998 | 215 | default "6" if MK8 || MCORE2 |
1da177e4 | 216 | |
e405d067 RT |
217 | config X86_INTERNODE_CACHE_BYTES |
218 | int | |
219 | default "4096" if X86_VSMP | |
220 | default X86_L1_CACHE_BYTES if !X86_VSMP | |
221 | ||
1da177e4 LT |
222 | config X86_TSC |
223 | bool | |
224 | default y | |
225 | ||
226 | config X86_GOOD_APIC | |
227 | bool | |
228 | default y | |
229 | ||
230 | config MICROCODE | |
231 | tristate "/dev/cpu/microcode - Intel CPU microcode support" | |
9a4b9efa | 232 | select FW_LOADER |
1da177e4 LT |
233 | ---help--- |
234 | If you say Y here the 'File systems' section, you will be | |
235 | able to update the microcode on Intel processors. You will | |
236 | obviously need the actual microcode binary data itself which is | |
237 | not shipped with the Linux kernel. | |
238 | ||
239 | For latest news and information on obtaining all the required | |
240 | ingredients for this driver, check: | |
241 | <http://www.urbanmyth.org/microcode/>. | |
242 | ||
243 | To compile this driver as a module, choose M here: the | |
244 | module will be called microcode. | |
245 | If you use modprobe or kmod you may also want to add the line | |
246 | 'alias char-major-10-184 microcode' to your /etc/modules.conf file. | |
247 | ||
9a3110bf SL |
248 | config MICROCODE_OLD_INTERFACE |
249 | bool | |
250 | depends on MICROCODE | |
251 | default y | |
252 | ||
1da177e4 LT |
253 | config X86_MSR |
254 | tristate "/dev/cpu/*/msr - Model-specific register support" | |
255 | help | |
256 | This device gives privileged processes access to the x86 | |
257 | Model-Specific Registers (MSRs). It is a character device with | |
258 | major 202 and minors 0 to 31 for /dev/cpu/0/msr to /dev/cpu/31/msr. | |
259 | MSR accesses are directed to a specific CPU on multi-processor | |
260 | systems. | |
261 | ||
262 | config X86_CPUID | |
263 | tristate "/dev/cpu/*/cpuid - CPU information support" | |
264 | help | |
265 | This device gives processes access to the x86 CPUID instruction to | |
266 | be executed on a specific processor. It is a character device | |
267 | with major 203 and minors 0 to 31 for /dev/cpu/0/cpuid to | |
268 | /dev/cpu/31/cpuid. | |
269 | ||
1da177e4 LT |
270 | config X86_HT |
271 | bool | |
272 | depends on SMP && !MK8 | |
273 | default y | |
274 | ||
275 | config MATH_EMULATION | |
276 | bool | |
277 | ||
278 | config MCA | |
279 | bool | |
280 | ||
281 | config EISA | |
282 | bool | |
283 | ||
284 | config X86_IO_APIC | |
285 | bool | |
286 | default y | |
287 | ||
288 | config X86_LOCAL_APIC | |
289 | bool | |
290 | default y | |
291 | ||
292 | config MTRR | |
293 | bool "MTRR (Memory Type Range Register) support" | |
294 | ---help--- | |
295 | On Intel P6 family processors (Pentium Pro, Pentium II and later) | |
296 | the Memory Type Range Registers (MTRRs) may be used to control | |
297 | processor access to memory ranges. This is most useful if you have | |
298 | a video (VGA) card on a PCI or AGP bus. Enabling write-combining | |
299 | allows bus write transfers to be combined into a larger transfer | |
300 | before bursting over the PCI/AGP bus. This can increase performance | |
301 | of image write operations 2.5 times or more. Saying Y here creates a | |
302 | /proc/mtrr file which may be used to manipulate your processor's | |
303 | MTRRs. Typically the X server should use this. | |
304 | ||
305 | This code has a reasonably generic interface so that similar | |
306 | control registers on other processors can be easily supported | |
307 | as well. | |
308 | ||
309 | Saying Y here also fixes a problem with buggy SMP BIOSes which only | |
310 | set the MTRRs for the boot CPU and not for the secondary CPUs. This | |
311 | can lead to all sorts of problems, so it's good to say Y here. | |
312 | ||
313 | Just say Y here, all x86-64 machines support MTRRs. | |
314 | ||
315 | See <file:Documentation/mtrr.txt> for more information. | |
316 | ||
317 | config SMP | |
318 | bool "Symmetric multi-processing support" | |
319 | ---help--- | |
320 | This enables support for systems with more than one CPU. If you have | |
321 | a system with only one CPU, like most personal computers, say N. If | |
322 | you have a system with more than one CPU, say Y. | |
323 | ||
324 | If you say N here, the kernel will run on single and multiprocessor | |
325 | machines, but will use only one CPU of a multiprocessor machine. If | |
326 | you say Y here, the kernel will run on many, but not all, | |
327 | singleprocessor machines. On a singleprocessor machine, the kernel | |
328 | will run faster if you say N here. | |
329 | ||
330 | If you don't know what to do here, say N. | |
331 | ||
1da177e4 LT |
332 | config SCHED_SMT |
333 | bool "SMT (Hyperthreading) scheduler support" | |
334 | depends on SMP | |
335 | default n | |
336 | help | |
337 | SMT scheduler support improves the CPU scheduler's decision making | |
338 | when dealing with Intel Pentium 4 chips with HyperThreading at a | |
339 | cost of slightly increased overhead in some places. If unsure say | |
340 | N here. | |
341 | ||
1e9f28fa SS |
342 | config SCHED_MC |
343 | bool "Multi-core scheduler support" | |
344 | depends on SMP | |
345 | default y | |
346 | help | |
347 | Multi-core scheduler support improves the CPU scheduler's decision | |
348 | making when dealing with multi-core CPU chips at a cost of slightly | |
349 | increased overhead in some places. If unsure say N here. | |
350 | ||
cc19ca86 IM |
351 | source "kernel/Kconfig.preempt" |
352 | ||
b0bd35e6 RT |
353 | config NUMA |
354 | bool "Non Uniform Memory Access (NUMA) Support" | |
1da177e4 LT |
355 | depends on SMP |
356 | help | |
b0bd35e6 RT |
357 | Enable NUMA (Non Uniform Memory Access) support. The kernel |
358 | will try to allocate memory used by a CPU on the local memory | |
359 | controller of the CPU and add some more NUMA awareness to the kernel. | |
360 | This code is recommended on all multiprocessor Opteron systems. | |
361 | If the system is EM64T, you should say N unless your system is EM64T | |
362 | NUMA. | |
363 | ||
364 | config K8_NUMA | |
365 | bool "Old style AMD Opteron NUMA detection" | |
f157cbb1 | 366 | depends on NUMA && PCI |
b0bd35e6 RT |
367 | default y |
368 | help | |
369 | Enable K8 NUMA node topology detection. You should say Y here if | |
370 | you have a multi processor AMD K8 system. This uses an old | |
44c09201 | 371 | method to read the NUMA configuration directly from the builtin |
b0bd35e6 RT |
372 | Northbridge of Opteron. It is recommended to use X86_64_ACPI_NUMA |
373 | instead, which also takes priority if both are compiled in. | |
374 | ||
c80d79d7 YG |
375 | config NODES_SHIFT |
376 | int | |
377 | default "6" | |
378 | depends on NEED_MULTIPLE_NODES | |
379 | ||
b0bd35e6 RT |
380 | # Dummy CONFIG option to select ACPI_NUMA from drivers/acpi/Kconfig. |
381 | ||
382 | config X86_64_ACPI_NUMA | |
383 | bool "ACPI NUMA detection" | |
384 | depends on NUMA | |
385 | select ACPI | |
1300124f | 386 | select PCI |
b0bd35e6 RT |
387 | select ACPI_NUMA |
388 | default y | |
389 | help | |
390 | Enable ACPI SRAT based node topology detection. | |
1da177e4 LT |
391 | |
392 | config NUMA_EMU | |
b0bd35e6 RT |
393 | bool "NUMA emulation" |
394 | depends on NUMA | |
1da177e4 LT |
395 | help |
396 | Enable NUMA emulation. A flat machine will be split | |
397 | into virtual nodes when booted with "numa=fake=N", where N is the | |
398 | number of nodes. This is only useful for debugging. | |
399 | ||
3f22ab27 | 400 | config ARCH_DISCONTIGMEM_ENABLE |
1da177e4 LT |
401 | bool |
402 | depends on NUMA | |
403 | default y | |
404 | ||
1035faf1 MT |
405 | config ARCH_DISCONTIGMEM_DEFAULT |
406 | def_bool y | |
407 | depends on NUMA | |
408 | ||
409 | config ARCH_SPARSEMEM_ENABLE | |
410 | def_bool y | |
44df75e6 | 411 | depends on (NUMA || EXPERIMENTAL) |
0889eba5 | 412 | select SPARSEMEM_VMEMMAP_ENABLE |
44df75e6 MT |
413 | |
414 | config ARCH_MEMORY_PROBE | |
415 | def_bool y | |
416 | depends on MEMORY_HOTPLUG | |
1035faf1 MT |
417 | |
418 | config ARCH_FLATMEM_ENABLE | |
419 | def_bool y | |
420 | depends on !NUMA | |
421 | ||
3f22ab27 DH |
422 | source "mm/Kconfig" |
423 | ||
ec69acbb KM |
424 | config MEMORY_HOTPLUG_RESERVE |
425 | def_bool y | |
426 | depends on (MEMORY_HOTPLUG && DISCONTIGMEM) | |
427 | ||
1035faf1 MT |
428 | config HAVE_ARCH_EARLY_PFN_TO_NID |
429 | def_bool y | |
44df75e6 | 430 | depends on NUMA |
1035faf1 | 431 | |
dc8ecb43 KH |
432 | config OUT_OF_LINE_PFN_TO_PAGE |
433 | def_bool y | |
434 | depends on DISCONTIGMEM | |
435 | ||
1da177e4 | 436 | config NR_CPUS |
d9c93813 | 437 | int "Maximum number of CPUs (2-255)" |
01d4bed4 | 438 | range 2 255 |
1da177e4 LT |
439 | depends on SMP |
440 | default "8" | |
441 | help | |
442 | This allows you to specify the maximum number of CPUs which this | |
d9c93813 | 443 | kernel will support. Current maximum is 255 CPUs due to |
1da177e4 LT |
444 | APIC addressing limits. Less depending on the hardware. |
445 | ||
446 | This is purely to save memory - each supported CPU requires | |
447 | memory in the static kernel configuration. | |
448 | ||
77e1dd65 PA |
449 | config PHYSICAL_ALIGN |
450 | hex | |
451 | default "0x200000" | |
452 | ||
76e4f660 | 453 | config HOTPLUG_CPU |
1dbf37e8 | 454 | bool "Support for suspend on SMP and hot-pluggable CPUs (EXPERIMENTAL)" |
76e4f660 AR |
455 | depends on SMP && HOTPLUG && EXPERIMENTAL |
456 | help | |
457 | Say Y here to experiment with turning CPUs off and on. CPUs | |
458 | can be controlled through /sys/devices/system/cpu/cpu#. | |
1dbf37e8 SR |
459 | This is also required for suspend/hibernation on SMP systems. |
460 | ||
461 | Say N if you want to disable CPU hotplug and don't need to | |
462 | suspend. | |
76e4f660 | 463 | |
cc57637b YG |
464 | config ARCH_ENABLE_MEMORY_HOTPLUG |
465 | def_bool y | |
76e4f660 | 466 | |
1da177e4 LT |
467 | config HPET_TIMER |
468 | bool | |
469 | default y | |
470 | help | |
471 | Use the IA-PC HPET (High Precision Event Timer) to manage | |
472 | time in preference to the PIT and RTC, if a HPET is | |
473 | present. The HPET provides a stable time base on SMP | |
474 | systems, unlike the TSC, but it is more expensive to access, | |
475 | as it is off-chip. You can find the HPET spec at | |
89d7cbf7 | 476 | <http://www.intel.com/hardwaredesign/hpetspec.htm>. |
1da177e4 LT |
477 | |
478 | config HPET_EMULATE_RTC | |
479 | bool "Provide RTC interrupt" | |
480 | depends on HPET_TIMER && RTC=y | |
481 | ||
a813ce43 AK |
482 | # Mark as embedded because too many people got it wrong. |
483 | # The code disables itself when not needed. | |
484 | config IOMMU | |
485 | bool "IOMMU support" if EMBEDDED | |
a54649b8 | 486 | default y |
17a941d8 | 487 | select SWIOTLB |
dcc1a66a | 488 | select AGP |
1da177e4 LT |
489 | depends on PCI |
490 | help | |
a813ce43 AK |
491 | Support for full DMA access of devices with 32bit memory access only |
492 | on systems with more than 3GB. This is usually needed for USB, | |
493 | sound, many IDE/SATA chipsets and some other devices. | |
494 | Provides a driver for the AMD Athlon64/Opteron/Turion/Sempron GART | |
5558870b KW |
495 | based hardware IOMMU and a software bounce buffer based IOMMU used |
496 | on Intel systems and as fallback. | |
a813ce43 AK |
497 | The code is only active when needed (enough memory and limited |
498 | device) unless CONFIG_IOMMU_DEBUG or iommu=force is specified | |
499 | too. | |
500 | ||
e465058d JM |
501 | config CALGARY_IOMMU |
502 | bool "IBM Calgary IOMMU support" | |
e465058d JM |
503 | select SWIOTLB |
504 | depends on PCI && EXPERIMENTAL | |
505 | help | |
506 | Support for hardware IOMMUs in IBM's xSeries x366 and x460 | |
507 | systems. Needed to run systems with more than 3GB of memory | |
508 | properly with 32-bit PCI devices that do not support DAC | |
509 | (Double Address Cycle). Calgary also supports bus level | |
510 | isolation, where all DMAs pass through the IOMMU. This | |
511 | prevents them from going anywhere except their intended | |
512 | destination. This catches hard-to-find kernel bugs and | |
513 | mis-behaving drivers and devices that do not use the DMA-API | |
514 | properly to set up their DMA buffers. The IOMMU can be | |
515 | turned off at boot time with the iommu=off parameter. | |
516 | Normally the kernel will make the right choice by itself. | |
517 | If unsure, say Y. | |
518 | ||
bff6547b MBY |
519 | config CALGARY_IOMMU_ENABLED_BY_DEFAULT |
520 | bool "Should Calgary be enabled by default?" | |
36f696cd | 521 | default y |
bff6547b MBY |
522 | depends on CALGARY_IOMMU |
523 | help | |
36f696cd | 524 | Should Calgary be enabled by default? if you choose 'y', Calgary |
bff6547b MBY |
525 | will be used (if it exists). If you choose 'n', Calgary will not be |
526 | used even if it exists. If you choose 'n' and would like to use | |
527 | Calgary anyway, pass 'iommu=calgary' on the kernel command line. | |
36f696cd | 528 | If unsure, say Y. |
bff6547b | 529 | |
a813ce43 | 530 | # need this always selected by IOMMU for the VIA workaround |
1da177e4 | 531 | config SWIOTLB |
1da177e4 | 532 | bool |
5558870b KW |
533 | help |
534 | Support for software bounce buffers used on x86-64 systems | |
535 | which don't have a hardware IOMMU (e.g. the current generation | |
536 | of Intel's x86-64 CPUs). Using this PCI devices which can only | |
537 | access 32-bits of memory can be used on systems with more than | |
538 | 3 GB of memory. If unsure, say Y. | |
1da177e4 LT |
539 | |
540 | config X86_MCE | |
541 | bool "Machine check support" if EMBEDDED | |
542 | default y | |
543 | help | |
544 | Include a machine check error handler to report hardware errors. | |
545 | This version will require the mcelog utility to decode some | |
546 | machine check error logs. See | |
547 | ftp://ftp.x86-64.org/pub/linux/tools/mcelog | |
548 | ||
549 | config X86_MCE_INTEL | |
550 | bool "Intel MCE features" | |
551 | depends on X86_MCE && X86_LOCAL_APIC | |
552 | default y | |
553 | help | |
554 | Additional support for intel specific MCE features such as | |
555 | the thermal monitor. | |
556 | ||
89b831ef JS |
557 | config X86_MCE_AMD |
558 | bool "AMD MCE features" | |
559 | depends on X86_MCE && X86_LOCAL_APIC | |
560 | default y | |
561 | help | |
562 | Additional support for AMD specific MCE features such as | |
563 | the DRAM Error Threshold. | |
564 | ||
5234f5eb | 565 | config KEXEC |
1c9c0a6c | 566 | bool "kexec system call" |
5234f5eb EB |
567 | help |
568 | kexec is a system call that implements the ability to shutdown your | |
569 | current kernel, and to start another kernel. It is like a reboot | |
1f1332f7 | 570 | but it is independent of the system firmware. And like a reboot |
5234f5eb EB |
571 | you can start any kernel with it, not just Linux. |
572 | ||
1f1332f7 | 573 | The name comes from the similarity to the exec system call. |
5234f5eb EB |
574 | |
575 | It is an ongoing process to be certain the hardware in a machine | |
576 | is properly shutdown, so do not be surprised if this code does not | |
577 | initially work for you. It may help to enable device hotplugging | |
578 | support. As of this writing the exact hardware interface is | |
579 | strongly in flux, so no good recommendation can be made. | |
580 | ||
ec9ce0db VG |
581 | config CRASH_DUMP |
582 | bool "kernel crash dumps (EXPERIMENTAL)" | |
ec9ce0db VG |
583 | depends on EXPERIMENTAL |
584 | help | |
1edf7778 AK |
585 | Generate crash dump after being started by kexec. |
586 | This should be normally only set in special crash dump kernels | |
587 | which are loaded in the main kernel with kexec-tools into | |
588 | a specially reserved region and then later executed after | |
589 | a crash by kdump/kexec. The crash dump kernel must be compiled | |
590 | to a memory address not used by the main kernel or BIOS using | |
591 | PHYSICAL_START. | |
592 | For more details see Documentation/kdump/kdump.txt | |
ec9ce0db | 593 | |
1ab60e0f VG |
594 | config RELOCATABLE |
595 | bool "Build a relocatable kernel(EXPERIMENTAL)" | |
596 | depends on EXPERIMENTAL | |
597 | help | |
598 | Builds a relocatable kernel. This enables loading and running | |
599 | a kernel binary from a different physical address than it has | |
600 | been compiled for. | |
601 | ||
602 | One use is for the kexec on panic case where the recovery kernel | |
603 | must live at a different physical address than the primary | |
604 | kernel. | |
605 | ||
606 | Note: If CONFIG_RELOCATABLE=y, then kernel run from the address | |
607 | it has been loaded at and compile time physical address | |
608 | (CONFIG_PHYSICAL_START) is ignored. | |
609 | ||
05970d47 MS |
610 | config PHYSICAL_START |
611 | hex "Physical address where the kernel is loaded" if (EMBEDDED || CRASH_DUMP) | |
04103609 | 612 | default "0x200000" |
05970d47 | 613 | help |
1ab60e0f VG |
614 | This gives the physical address where the kernel is loaded. It |
615 | should be aligned to 2MB boundary. | |
616 | ||
617 | If kernel is a not relocatable (CONFIG_RELOCATABLE=n) then | |
618 | bzImage will decompress itself to above physical address and | |
619 | run from there. Otherwise, bzImage will run from the address where | |
620 | it has been loaded by the boot loader and will ignore above physical | |
621 | address. | |
622 | ||
623 | In normal kdump cases one does not have to set/change this option | |
624 | as now bzImage can be compiled as a completely relocatable image | |
625 | (CONFIG_RELOCATABLE=y) and be used to load and run from a different | |
626 | address. This option is mainly useful for the folks who don't want | |
627 | to use a bzImage for capturing the crash dump and want to use a | |
628 | vmlinux instead. | |
629 | ||
630 | So if you are using bzImage for capturing the crash dump, leave | |
631 | the value here unchanged to 0x200000 and set CONFIG_RELOCATABLE=y. | |
632 | Otherwise if you plan to use vmlinux for capturing the crash dump | |
633 | change this value to start of the reserved region (Typically 16MB | |
634 | 0x1000000). In other words, it can be set based on the "X" value as | |
05970d47 MS |
635 | specified in the "crashkernel=YM@XM" command line boot parameter |
636 | passed to the panic-ed kernel. Typically this parameter is set as | |
637 | crashkernel=64M@16M. Please take a look at | |
638 | Documentation/kdump/kdump.txt for more details about crash dumps. | |
639 | ||
1ab60e0f VG |
640 | Usage of bzImage for capturing the crash dump is advantageous as |
641 | one does not have to build two kernels. Same kernel can be used | |
642 | as production kernel and capture kernel. | |
643 | ||
05970d47 MS |
644 | Don't change this unless you know what you are doing. |
645 | ||
1da177e4 LT |
646 | config SECCOMP |
647 | bool "Enable seccomp to safely compute untrusted bytecode" | |
648 | depends on PROC_FS | |
649 | default y | |
650 | help | |
651 | This kernel feature is useful for number crunching applications | |
652 | that may need to compute untrusted bytecode during their | |
653 | execution. By using pipes or other transports made available to | |
654 | the process as file descriptors supporting the read/write | |
655 | syscalls, it's possible to isolate those applications in | |
656 | their own address space using seccomp. Once seccomp is | |
657 | enabled via /proc/<pid>/seccomp, it cannot be disabled | |
658 | and the task is only allowed to execute a few safe syscalls | |
659 | defined by each seccomp mode. | |
660 | ||
661 | If unsure, say Y. Only embedded should say N here. | |
662 | ||
b62a5c74 | 663 | config CC_STACKPROTECTOR |
e45116b8 | 664 | bool "Enable -fstack-protector buffer overflow detection (EXPERIMENTAL)" |
b62a5c74 AV |
665 | depends on EXPERIMENTAL |
666 | help | |
667 | This option turns on the -fstack-protector GCC feature. This | |
668 | feature puts, at the beginning of critical functions, a canary | |
669 | value on the stack just before the return address, and validates | |
670 | the value just before actually returning. Stack based buffer | |
671 | overflows (that need to overwrite this return address) now also | |
672 | overwrite the canary, which gets detected and the attack is then | |
673 | neutralized via a kernel panic. | |
674 | ||
675 | This feature requires gcc version 4.2 or above, or a distribution | |
676 | gcc with the feature backported. Older versions are automatically | |
677 | detected and for those versions, this configuration option is ignored. | |
678 | ||
679 | config CC_STACKPROTECTOR_ALL | |
680 | bool "Use stack-protector for all functions" | |
681 | depends on CC_STACKPROTECTOR | |
682 | help | |
683 | Normally, GCC only inserts the canary value protection for | |
684 | functions that use large-ish on-stack buffers. By enabling | |
685 | this option, GCC will be asked to do this for ALL functions. | |
686 | ||
59121003 CL |
687 | source kernel/Kconfig.hz |
688 | ||
a32073bf AK |
689 | config K8_NB |
690 | def_bool y | |
a813ce43 | 691 | depends on AGP_AMD64 || IOMMU || (PCI && NUMA) |
a32073bf | 692 | |
1da177e4 LT |
693 | endmenu |
694 | ||
695 | # | |
696 | # Use the generic interrupt handling code in kernel/irq/: | |
697 | # | |
698 | config GENERIC_HARDIRQS | |
699 | bool | |
700 | default y | |
701 | ||
702 | config GENERIC_IRQ_PROBE | |
703 | bool | |
704 | default y | |
705 | ||
5cae841b AV |
706 | # we have no ISA slots, but we do have ISA-style DMA. |
707 | config ISA_DMA_API | |
708 | bool | |
709 | default y | |
710 | ||
54d5d424 AR |
711 | config GENERIC_PENDING_IRQ |
712 | bool | |
713 | depends on GENERIC_HARDIRQS && SMP | |
714 | default y | |
715 | ||
1da177e4 LT |
716 | menu "Power management options" |
717 | ||
718 | source kernel/power/Kconfig | |
719 | ||
720 | source "drivers/acpi/Kconfig" | |
721 | ||
51b28330 | 722 | source "arch/x86/kernel/cpufreq/Kconfig" |
1da177e4 LT |
723 | |
724 | endmenu | |
725 | ||
726 | menu "Bus options (PCI etc.)" | |
727 | ||
728 | config PCI | |
729 | bool "PCI support" | |
f282b970 | 730 | select ARCH_SUPPORTS_MSI if (X86_LOCAL_APIC && X86_IO_APIC) |
1da177e4 LT |
731 | |
732 | # x86-64 doesn't support PCI BIOS access from long mode so always go direct. | |
733 | config PCI_DIRECT | |
734 | bool | |
735 | depends on PCI | |
736 | default y | |
737 | ||
738 | config PCI_MMCONFIG | |
739 | bool "Support mmconfig PCI config space access" | |
8aadff7d | 740 | depends on PCI && ACPI |
1da177e4 | 741 | |
a79e4198 JG |
742 | config PCI_DOMAINS |
743 | bool | |
744 | depends on PCI | |
745 | default y | |
746 | ||
1da177e4 LT |
747 | source "drivers/pci/pcie/Kconfig" |
748 | ||
749 | source "drivers/pci/Kconfig" | |
750 | ||
751 | source "drivers/pcmcia/Kconfig" | |
752 | ||
753 | source "drivers/pci/hotplug/Kconfig" | |
754 | ||
755 | endmenu | |
756 | ||
757 | ||
758 | menu "Executable file formats / Emulations" | |
759 | ||
760 | source "fs/Kconfig.binfmt" | |
761 | ||
762 | config IA32_EMULATION | |
763 | bool "IA32 Emulation" | |
764 | help | |
765 | Include code to run 32-bit programs under a 64-bit kernel. You should likely | |
766 | turn this on, unless you're 100% sure that you don't have any 32-bit programs | |
767 | left. | |
768 | ||
769 | config IA32_AOUT | |
ea0be473 | 770 | tristate "IA32 a.out support" |
1da177e4 LT |
771 | depends on IA32_EMULATION |
772 | help | |
773 | Support old a.out binaries in the 32bit emulation. | |
774 | ||
775 | config COMPAT | |
776 | bool | |
777 | depends on IA32_EMULATION | |
778 | default y | |
779 | ||
7a6c8135 TL |
780 | config COMPAT_FOR_U64_ALIGNMENT |
781 | def_bool COMPAT | |
782 | ||
1da177e4 LT |
783 | config SYSVIPC_COMPAT |
784 | bool | |
785 | depends on COMPAT && SYSVIPC | |
786 | default y | |
787 | ||
1da177e4 LT |
788 | endmenu |
789 | ||
d5950b43 SR |
790 | source "net/Kconfig" |
791 | ||
1da177e4 LT |
792 | source drivers/Kconfig |
793 | ||
794 | source "drivers/firmware/Kconfig" | |
795 | ||
796 | source fs/Kconfig | |
797 | ||
cd6b0762 PP |
798 | menu "Instrumentation Support" |
799 | depends on EXPERIMENTAL | |
800 | ||
33fc6d51 | 801 | source "arch/x86/oprofile/Kconfig" |
1da177e4 | 802 | |
cd6b0762 | 803 | config KPROBES |
87a7defb AM |
804 | bool "Kprobes" |
805 | depends on KALLSYMS && MODULES | |
cd6b0762 PP |
806 | help |
807 | Kprobes allows you to trap at almost any kernel address and | |
808 | execute a callback function. register_kprobe() establishes | |
809 | a probepoint and specifies the callback. Kprobes is useful | |
810 | for kernel debugging, non-intrusive instrumentation and testing. | |
811 | If in doubt, say "N". | |
812 | endmenu | |
813 | ||
1da177e4 LT |
814 | source "arch/x86_64/Kconfig.debug" |
815 | ||
816 | source "security/Kconfig" | |
817 | ||
818 | source "crypto/Kconfig" | |
819 | ||
820 | source "lib/Kconfig" |