Commit | Line | Data |
---|---|---|
daa93fab SR |
1 | # Select 32 or 64 bit |
2 | config 64BIT | |
6840999b | 3 | bool "64-bit kernel" if ARCH = "x86" |
ffee0de4 | 4 | default ARCH != "i386" |
8f9ca475 | 5 | ---help--- |
daa93fab SR |
6 | Say yes to build a 64-bit kernel - formerly known as x86_64 |
7 | Say no to build a 32-bit kernel - formerly known as i386 | |
8 | ||
9 | config X86_32 | |
3120e25e JB |
10 | def_bool y |
11 | depends on !64BIT | |
82491451 | 12 | select CLKSRC_I8253 |
af1839eb | 13 | select HAVE_UID16 |
daa93fab SR |
14 | |
15 | config X86_64 | |
3120e25e JB |
16 | def_bool y |
17 | depends on 64BIT | |
4692d77f | 18 | select X86_DEV_DMA_OPS |
bc08b449 | 19 | select ARCH_USE_CMPXCHG_LOCKREF |
1032c0ba SR |
20 | |
21 | ### Arch settings | |
8d5fffb9 | 22 | config X86 |
3c2362e6 | 23 | def_bool y |
46ba51ea | 24 | select ARCH_MIGHT_HAVE_ACPI_PDC if ACPI |
446f24d1 | 25 | select ARCH_HAS_DEBUG_STRICT_USER_COPY_CHECKS |
72d93104 | 26 | select ARCH_HAS_FAST_MULTIPLIER |
957e3fac | 27 | select ARCH_HAS_GCOV_PROFILE_ALL |
77fbbc81 | 28 | select ARCH_MIGHT_HAVE_PC_PARPORT |
5e2c18c0 | 29 | select ARCH_MIGHT_HAVE_PC_SERIO |
e17c6d56 | 30 | select HAVE_AOUT if X86_32 |
a5574cf6 | 31 | select HAVE_UNSTABLE_SCHED_CLOCK |
4468dd76 | 32 | select ARCH_SUPPORTS_NUMA_BALANCING if X86_64 |
be5e610c | 33 | select ARCH_SUPPORTS_INT128 if X86_64 |
ec7748b5 | 34 | select HAVE_IDE |
42d4b839 | 35 | select HAVE_OPROFILE |
8761f1ab | 36 | select HAVE_PCSPKR_PLATFORM |
cc2067a5 | 37 | select HAVE_PERF_EVENTS |
28b2ee20 | 38 | select HAVE_IOREMAP_PROT |
3f550096 | 39 | select HAVE_KPROBES |
72d7c3b3 | 40 | select HAVE_MEMBLOCK |
0608f70c | 41 | select HAVE_MEMBLOCK_NODE_MAP |
c378ddd5 | 42 | select ARCH_DISCARD_MEMBLOCK |
1f972768 | 43 | select ARCH_WANT_OPTIONAL_GPIOLIB |
da4276b8 | 44 | select ARCH_WANT_FRAME_POINTERS |
7c095e46 | 45 | select HAVE_DMA_ATTRS |
9c5a3621 | 46 | select HAVE_DMA_CONTIGUOUS |
9edddaa2 | 47 | select HAVE_KRETPROBES |
5b7c73e0 | 48 | select GENERIC_EARLY_IOREMAP |
c0f7ac3a | 49 | select HAVE_OPTPROBES |
e7dbfe34 | 50 | select HAVE_KPROBES_ON_FTRACE |
e4b2b886 | 51 | select HAVE_FTRACE_MCOUNT_RECORD |
d57c5d51 | 52 | select HAVE_FENTRY if X86_64 |
cf4db259 | 53 | select HAVE_C_RECORDMCOUNT |
677aa9f7 | 54 | select HAVE_DYNAMIC_FTRACE |
06aeaaea | 55 | select HAVE_DYNAMIC_FTRACE_WITH_REGS |
606576ce | 56 | select HAVE_FUNCTION_TRACER |
48d68b20 | 57 | select HAVE_FUNCTION_GRAPH_TRACER |
71e308a2 | 58 | select HAVE_FUNCTION_GRAPH_FP_TEST |
66700001 | 59 | select HAVE_SYSCALL_TRACEPOINTS |
7ac57a89 | 60 | select SYSCTL_EXCEPTION_TRACE |
e0ec9483 | 61 | select HAVE_KVM |
49793b03 | 62 | select HAVE_ARCH_KGDB |
99bbc4b1 | 63 | select HAVE_ARCH_TRACEHOOK |
323ec001 | 64 | select HAVE_GENERIC_DMA_COHERENT if X86_32 |
58340a07 | 65 | select HAVE_EFFICIENT_UNALIGNED_ACCESS |
8d26487f | 66 | select USER_STACKTRACE_SUPPORT |
f850c30c | 67 | select HAVE_REGS_AND_STACK_ACCESS_API |
2118d0c5 | 68 | select HAVE_DMA_API_DEBUG |
2e9f3bdd PA |
69 | select HAVE_KERNEL_GZIP |
70 | select HAVE_KERNEL_BZIP2 | |
71 | select HAVE_KERNEL_LZMA | |
30314804 | 72 | select HAVE_KERNEL_XZ |
13510997 | 73 | select HAVE_KERNEL_LZO |
f9b493ac | 74 | select HAVE_KERNEL_LZ4 |
0067f129 | 75 | select HAVE_HW_BREAKPOINT |
0102752e | 76 | select HAVE_MIXED_BREAKPOINTS_REGS |
99e8c5a3 | 77 | select PERF_EVENTS |
c01d4323 | 78 | select HAVE_PERF_EVENTS_NMI |
c5e63197 | 79 | select HAVE_PERF_REGS |
c5ebcedb | 80 | select HAVE_PERF_USER_STACK_DUMP |
b69ec42b | 81 | select HAVE_DEBUG_KMEMLEAK |
99e8c5a3 | 82 | select ANON_INODES |
eb068e78 PA |
83 | select HAVE_ALIGNED_STRUCT_PAGE if SLUB |
84 | select HAVE_CMPXCHG_LOCAL | |
2565409f | 85 | select HAVE_CMPXCHG_DOUBLE |
0a4af3b0 | 86 | select HAVE_ARCH_KMEMCHECK |
7c68af6e | 87 | select HAVE_USER_RETURN_NOTIFIER |
e39f5602 | 88 | select ARCH_BINFMT_ELF_RANDOMIZE_PIE |
46eb3b64 | 89 | select HAVE_ARCH_JUMP_LABEL |
7463449b | 90 | select ARCH_HAS_ATOMIC64_DEC_IF_POSITIVE |
141d55e6 | 91 | select SPARSE_IRQ |
c49aa5bd | 92 | select GENERIC_FIND_FIRST_BIT |
3bb9808e TG |
93 | select GENERIC_IRQ_PROBE |
94 | select GENERIC_PENDING_IRQ if SMP | |
517e4981 | 95 | select GENERIC_IRQ_SHOW |
d1748302 | 96 | select GENERIC_CLOCKEVENTS_MIN_ADJUST |
c0185808 | 97 | select IRQ_FORCED_THREADING |
e47b65b0 | 98 | select HAVE_BPF_JIT if X86_64 |
15626062 | 99 | select HAVE_ARCH_TRANSPARENT_HUGEPAGE |
308c09f1 | 100 | select ARCH_HAS_SG_CHAIN |
0a779c57 | 101 | select CLKEVT_I8253 |
df013ffb | 102 | select ARCH_HAVE_NMI_SAFE_CMPXCHG |
4673ca8e | 103 | select GENERIC_IOMAP |
e419b4cc | 104 | select DCACHE_WORD_ACCESS |
7eb43a6d | 105 | select GENERIC_SMP_IDLE_THREAD |
c1d7e01d | 106 | select ARCH_WANT_IPC_PARSE_VERSION if X86_32 |
c6cfbeb4 | 107 | select HAVE_ARCH_SECCOMP_FILTER |
8b5ad472 | 108 | select BUILDTIME_EXTABLE_SORT |
bdebaf80 | 109 | select GENERIC_CMOS_UPDATE |
2bf01f9f | 110 | select HAVE_ARCH_SOFT_DIRTY if X86_64 |
bdebaf80 TG |
111 | select CLOCKSOURCE_WATCHDOG |
112 | select GENERIC_CLOCKEVENTS | |
d2312e33 | 113 | select ARCH_CLOCKSOURCE_DATA |
09ec5442 | 114 | select CLOCKSOURCE_VALIDATE_LAST_CYCLE |
bdebaf80 | 115 | select GENERIC_CLOCKEVENTS_BROADCAST if X86_64 || (X86_32 && X86_LOCAL_APIC) |
d2312e33 | 116 | select GENERIC_TIME_VSYSCALL |
4ae73f2d | 117 | select GENERIC_STRNCPY_FROM_USER |
5723aa99 | 118 | select GENERIC_STRNLEN_USER |
91d1aa43 | 119 | select HAVE_CONTEXT_TRACKING if X86_64 |
fdf9c356 | 120 | select HAVE_IRQ_TIME_ACCOUNTING |
4febd95a | 121 | select VIRT_TO_BUS |
786d35d4 DH |
122 | select MODULES_USE_ELF_REL if X86_32 |
123 | select MODULES_USE_ELF_RELA if X86_64 | |
1d4b4b29 | 124 | select CLONE_BACKWARDS if X86_32 |
83a57a4d | 125 | select ARCH_USE_BUILTIN_BSWAP |
bd01ec1a | 126 | select ARCH_USE_QUEUE_RWLOCK |
15ce1f71 | 127 | select OLD_SIGSUSPEND3 if X86_32 || IA32_EMULATION |
5b3eb3ad AV |
128 | select OLD_SIGACTION if X86_32 |
129 | select COMPAT_OLD_SIGACTION if IA32_EMULATION | |
3195ef59 | 130 | select RTC_LIB |
d1a1dc0b | 131 | select HAVE_DEBUG_STACKOVERFLOW |
a2cd11f7 | 132 | select HAVE_IRQ_EXIT_ON_IRQ_STACK if X86_64 |
19952a92 | 133 | select HAVE_CC_STACKPROTECTOR |
2b9c1f03 | 134 | select GENERIC_CPU_AUTOPROBE |
7a017721 | 135 | select HAVE_ARCH_AUDITSYSCALL |
4badad35 | 136 | select ARCH_SUPPORTS_ATOMIC_RMW |
44a69f61 TN |
137 | select HAVE_ACPI_APEI if ACPI |
138 | select HAVE_ACPI_APEI_NMI if ACPI | |
8a1664be | 139 | select ACPI_LEGACY_TABLES_LOOKUP if ACPI |
9def39be | 140 | select X86_FEATURE_NAMES if PROC_FS |
83fe27ea | 141 | select SRCU |
7d8330a5 | 142 | |
ba7e4d13 | 143 | config INSTRUCTION_DECODER |
3120e25e JB |
144 | def_bool y |
145 | depends on KPROBES || PERF_EVENTS || UPROBES | |
ba7e4d13 | 146 | |
7fb0f1de PZ |
147 | config PERF_EVENTS_INTEL_UNCORE |
148 | def_bool y | |
ce5686d4 | 149 | depends on PERF_EVENTS && CPU_SUP_INTEL && PCI |
7fb0f1de | 150 | |
51b26ada LT |
151 | config OUTPUT_FORMAT |
152 | string | |
153 | default "elf32-i386" if X86_32 | |
154 | default "elf64-x86-64" if X86_64 | |
155 | ||
73531905 | 156 | config ARCH_DEFCONFIG |
b9b39bfb | 157 | string |
73531905 SR |
158 | default "arch/x86/configs/i386_defconfig" if X86_32 |
159 | default "arch/x86/configs/x86_64_defconfig" if X86_64 | |
b9b39bfb | 160 | |
8d5fffb9 | 161 | config LOCKDEP_SUPPORT |
3c2362e6 | 162 | def_bool y |
8d5fffb9 SR |
163 | |
164 | config STACKTRACE_SUPPORT | |
3c2362e6 | 165 | def_bool y |
8d5fffb9 | 166 | |
aa7d9350 HC |
167 | config HAVE_LATENCYTOP_SUPPORT |
168 | def_bool y | |
169 | ||
8d5fffb9 | 170 | config MMU |
3c2362e6 | 171 | def_bool y |
8d5fffb9 | 172 | |
8d5fffb9 SR |
173 | config SBUS |
174 | bool | |
175 | ||
3bc4e459 | 176 | config NEED_DMA_MAP_STATE |
3120e25e JB |
177 | def_bool y |
178 | depends on X86_64 || INTEL_IOMMU || DMA_API_DEBUG | |
3bc4e459 | 179 | |
18e98307 | 180 | config NEED_SG_DMA_LENGTH |
4a14d84e | 181 | def_bool y |
18e98307 | 182 | |
8d5fffb9 | 183 | config GENERIC_ISA_DMA |
3120e25e JB |
184 | def_bool y |
185 | depends on ISA_DMA_API | |
8d5fffb9 | 186 | |
8d5fffb9 | 187 | config GENERIC_BUG |
3c2362e6 | 188 | def_bool y |
8d5fffb9 | 189 | depends on BUG |
b93a531e JB |
190 | select GENERIC_BUG_RELATIVE_POINTERS if X86_64 |
191 | ||
192 | config GENERIC_BUG_RELATIVE_POINTERS | |
193 | bool | |
8d5fffb9 SR |
194 | |
195 | config GENERIC_HWEIGHT | |
3c2362e6 | 196 | def_bool y |
8d5fffb9 SR |
197 | |
198 | config ARCH_MAY_HAVE_PC_FDC | |
3120e25e JB |
199 | def_bool y |
200 | depends on ISA_DMA_API | |
8d5fffb9 | 201 | |
1032c0ba | 202 | config RWSEM_XCHGADD_ALGORITHM |
3120e25e | 203 | def_bool y |
1032c0ba | 204 | |
1032c0ba SR |
205 | config GENERIC_CALIBRATE_DELAY |
206 | def_bool y | |
207 | ||
9a0b8415 | 208 | config ARCH_HAS_CPU_RELAX |
209 | def_bool y | |
210 | ||
1b27d05b PE |
211 | config ARCH_HAS_CACHE_LINE_SIZE |
212 | def_bool y | |
213 | ||
dd5af90a | 214 | config HAVE_SETUP_PER_CPU_AREA |
89c9c4c5 | 215 | def_bool y |
b32ef636 | 216 | |
08fc4580 TH |
217 | config NEED_PER_CPU_EMBED_FIRST_CHUNK |
218 | def_bool y | |
219 | ||
220 | config NEED_PER_CPU_PAGE_FIRST_CHUNK | |
11124411 TH |
221 | def_bool y |
222 | ||
801e4062 JB |
223 | config ARCH_HIBERNATION_POSSIBLE |
224 | def_bool y | |
801e4062 | 225 | |
f4cb5700 JB |
226 | config ARCH_SUSPEND_POSSIBLE |
227 | def_bool y | |
f4cb5700 | 228 | |
cfe28c5d SC |
229 | config ARCH_WANT_HUGE_PMD_SHARE |
230 | def_bool y | |
231 | ||
53313b2c SC |
232 | config ARCH_WANT_GENERAL_HUGETLB |
233 | def_bool y | |
234 | ||
8d5fffb9 | 235 | config ZONE_DMA32 |
e0fd24a3 | 236 | def_bool y if X86_64 |
8d5fffb9 | 237 | |
8d5fffb9 | 238 | config AUDIT_ARCH |
e0fd24a3 | 239 | def_bool y if X86_64 |
8d5fffb9 | 240 | |
765c68bd IM |
241 | config ARCH_SUPPORTS_OPTIMIZED_INLINING |
242 | def_bool y | |
243 | ||
6a11f75b AM |
244 | config ARCH_SUPPORTS_DEBUG_PAGEALLOC |
245 | def_bool y | |
246 | ||
69575d38 SW |
247 | config HAVE_INTEL_TXT |
248 | def_bool y | |
6ea30386 | 249 | depends on INTEL_IOMMU && ACPI |
69575d38 | 250 | |
6b0c3d44 SR |
251 | config X86_32_SMP |
252 | def_bool y | |
253 | depends on X86_32 && SMP | |
254 | ||
255 | config X86_64_SMP | |
256 | def_bool y | |
257 | depends on X86_64 && SMP | |
258 | ||
8d5fffb9 | 259 | config X86_HT |
6fc108a0 | 260 | def_bool y |
ee0011a7 | 261 | depends on SMP |
8d5fffb9 | 262 | |
ccbeed3a TH |
263 | config X86_32_LAZY_GS |
264 | def_bool y | |
60a5317f | 265 | depends on X86_32 && !CC_STACKPROTECTOR |
ccbeed3a | 266 | |
d61931d8 BP |
267 | config ARCH_HWEIGHT_CFLAGS |
268 | string | |
269 | default "-fcall-saved-ecx -fcall-saved-edx" if X86_32 | |
270 | default "-fcall-saved-rdi -fcall-saved-rsi -fcall-saved-rdx -fcall-saved-rcx -fcall-saved-r8 -fcall-saved-r9 -fcall-saved-r10 -fcall-saved-r11" if X86_64 | |
271 | ||
2b144498 SD |
272 | config ARCH_SUPPORTS_UPROBES |
273 | def_bool y | |
274 | ||
d20642f0 RH |
275 | config FIX_EARLYCON_MEM |
276 | def_bool y | |
277 | ||
506f1d07 | 278 | source "init/Kconfig" |
dc52ddc0 | 279 | source "kernel/Kconfig.freezer" |
8d5fffb9 | 280 | |
506f1d07 SR |
281 | menu "Processor type and features" |
282 | ||
5ee71535 RD |
283 | config ZONE_DMA |
284 | bool "DMA memory allocation support" if EXPERT | |
285 | default y | |
286 | help | |
287 | DMA memory allocation support allows devices with less than 32-bit | |
288 | addressing to allocate within the first 16MB of address space. | |
289 | Disable if no such devices will be used. | |
290 | ||
291 | If unsure, say Y. | |
292 | ||
506f1d07 SR |
293 | config SMP |
294 | bool "Symmetric multi-processing support" | |
295 | ---help--- | |
296 | This enables support for systems with more than one CPU. If you have | |
4a474157 RG |
297 | a system with only one CPU, say N. If you have a system with more |
298 | than one CPU, say Y. | |
506f1d07 | 299 | |
4a474157 | 300 | If you say N here, the kernel will run on uni- and multiprocessor |
506f1d07 SR |
301 | machines, but will use only one CPU of a multiprocessor machine. If |
302 | you say Y here, the kernel will run on many, but not all, | |
4a474157 | 303 | uniprocessor machines. On a uniprocessor machine, the kernel |
506f1d07 SR |
304 | will run faster if you say N here. |
305 | ||
306 | Note that if you say Y here and choose architecture "586" or | |
307 | "Pentium" under "Processor family", the kernel will not work on 486 | |
308 | architectures. Similarly, multiprocessor kernels for the "PPro" | |
309 | architecture may not work on all Pentium based boards. | |
310 | ||
311 | People using multiprocessor machines who say Y here should also say | |
312 | Y to "Enhanced Real Time Clock Support", below. The "Advanced Power | |
313 | Management" code will be disabled if you say Y here. | |
314 | ||
395cf969 | 315 | See also <file:Documentation/x86/i386/IO-APIC.txt>, |
506f1d07 SR |
316 | <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at |
317 | <http://www.tldp.org/docs.html#howto>. | |
318 | ||
319 | If you don't know what to do here, say N. | |
320 | ||
9def39be JT |
321 | config X86_FEATURE_NAMES |
322 | bool "Processor feature human-readable names" if EMBEDDED | |
323 | default y | |
324 | ---help--- | |
325 | This option compiles in a table of x86 feature bits and corresponding | |
326 | names. This is required to support /proc/cpuinfo and a few kernel | |
327 | messages. You can disable this to save space, at the expense of | |
328 | making those few kernel messages show numeric feature bits instead. | |
329 | ||
330 | If in doubt, say Y. | |
331 | ||
06cd9a7d YL |
332 | config X86_X2APIC |
333 | bool "Support x2apic" | |
d3f13810 | 334 | depends on X86_LOCAL_APIC && X86_64 && IRQ_REMAP |
06cd9a7d YL |
335 | ---help--- |
336 | This enables x2apic support on CPUs that have this feature. | |
337 | ||
338 | This allows 32-bit apic IDs (so it can support very large systems), | |
339 | and accesses the local apic via MSRs not via mmio. | |
340 | ||
06cd9a7d YL |
341 | If you don't know what to do here, say N. |
342 | ||
6695c85b | 343 | config X86_MPPARSE |
6e87f9b7 | 344 | bool "Enable MPS table" if ACPI || SFI |
7a527688 | 345 | default y |
5ab74722 | 346 | depends on X86_LOCAL_APIC |
8f9ca475 | 347 | ---help--- |
6695c85b YL |
348 | For old smp systems that do not have proper acpi support. Newer systems |
349 | (esp with 64bit cpus) with acpi support, MADT and DSDT will override it | |
6695c85b | 350 | |
26f7ef14 YL |
351 | config X86_BIGSMP |
352 | bool "Support for big SMP systems with more than 8 CPUs" | |
353 | depends on X86_32 && SMP | |
8f9ca475 | 354 | ---help--- |
26f7ef14 | 355 | This option is needed for the systems that have more than 8 CPUs |
506f1d07 | 356 | |
ddd70cf9 JN |
357 | config GOLDFISH |
358 | def_bool y | |
359 | depends on X86_GOLDFISH | |
360 | ||
8425091f | 361 | if X86_32 |
c5c606d9 RT |
362 | config X86_EXTENDED_PLATFORM |
363 | bool "Support for extended (non-PC) x86 platforms" | |
364 | default y | |
8f9ca475 | 365 | ---help--- |
06ac8346 IM |
366 | If you disable this option then the kernel will only support |
367 | standard PC platforms. (which covers the vast majority of | |
368 | systems out there.) | |
369 | ||
8425091f RT |
370 | If you enable this option then you'll be able to select support |
371 | for the following (non-PC) 32 bit x86 platforms: | |
cb7b8023 | 372 | Goldfish (Android emulator) |
8425091f | 373 | AMD Elan |
8425091f RT |
374 | RDC R-321x SoC |
375 | SGI 320/540 (Visual Workstation) | |
83125a3a | 376 | STA2X11-based (e.g. Northville) |
3f4110a4 | 377 | Moorestown MID devices |
06ac8346 IM |
378 | |
379 | If you have one of these systems, or if you want to build a | |
380 | generic distribution kernel, say Y here - otherwise say N. | |
8425091f | 381 | endif |
06ac8346 | 382 | |
8425091f RT |
383 | if X86_64 |
384 | config X86_EXTENDED_PLATFORM | |
385 | bool "Support for extended (non-PC) x86 platforms" | |
386 | default y | |
387 | ---help--- | |
388 | If you disable this option then the kernel will only support | |
389 | standard PC platforms. (which covers the vast majority of | |
390 | systems out there.) | |
391 | ||
392 | If you enable this option then you'll be able to select support | |
393 | for the following (non-PC) 64 bit x86 platforms: | |
44b111b5 | 394 | Numascale NumaChip |
8425091f RT |
395 | ScaleMP vSMP |
396 | SGI Ultraviolet | |
397 | ||
398 | If you have one of these systems, or if you want to build a | |
399 | generic distribution kernel, say Y here - otherwise say N. | |
400 | endif | |
c5c606d9 RT |
401 | # This is an alphabetically sorted list of 64 bit extended platforms |
402 | # Please maintain the alphabetic order if and when there are additions | |
44b111b5 SP |
403 | config X86_NUMACHIP |
404 | bool "Numascale NumaChip" | |
405 | depends on X86_64 | |
406 | depends on X86_EXTENDED_PLATFORM | |
407 | depends on NUMA | |
408 | depends on SMP | |
409 | depends on X86_X2APIC | |
f9726bfd | 410 | depends on PCI_MMCONFIG |
44b111b5 SP |
411 | ---help--- |
412 | Adds support for Numascale NumaChip large-SMP systems. Needed to | |
413 | enable more than ~168 cores. | |
414 | If you don't have one of these, you should say N here. | |
506f1d07 | 415 | |
c5c606d9 RT |
416 | config X86_VSMP |
417 | bool "ScaleMP vSMP" | |
6276a074 | 418 | select HYPERVISOR_GUEST |
c5c606d9 RT |
419 | select PARAVIRT |
420 | depends on X86_64 && PCI | |
421 | depends on X86_EXTENDED_PLATFORM | |
ead91d4b | 422 | depends on SMP |
8f9ca475 | 423 | ---help--- |
c5c606d9 RT |
424 | Support for ScaleMP vSMP systems. Say 'Y' here if this kernel is |
425 | supposed to run on these EM64T-based machines. Only choose this option | |
426 | if you have one of these machines. | |
5e3a77e9 | 427 | |
03b48632 NP |
428 | config X86_UV |
429 | bool "SGI Ultraviolet" | |
430 | depends on X86_64 | |
c5c606d9 | 431 | depends on X86_EXTENDED_PLATFORM |
54c28d29 | 432 | depends on NUMA |
9d6c26e7 | 433 | depends on X86_X2APIC |
8f9ca475 | 434 | ---help--- |
03b48632 NP |
435 | This option is needed in order to support SGI Ultraviolet systems. |
436 | If you don't have one of these, you should say N here. | |
437 | ||
c5c606d9 RT |
438 | # Following is an alphabetically sorted list of 32 bit extended platforms |
439 | # Please maintain the alphabetic order if and when there are additions | |
506f1d07 | 440 | |
ddd70cf9 JN |
441 | config X86_GOLDFISH |
442 | bool "Goldfish (Virtual Platform)" | |
cb7b8023 | 443 | depends on X86_EXTENDED_PLATFORM |
ddd70cf9 JN |
444 | ---help--- |
445 | Enable support for the Goldfish virtual platform used primarily | |
446 | for Android development. Unless you are building for the Android | |
447 | Goldfish emulator say N here. | |
448 | ||
c751e17b TG |
449 | config X86_INTEL_CE |
450 | bool "CE4100 TV platform" | |
451 | depends on PCI | |
452 | depends on PCI_GODIRECT | |
6084a6e2 | 453 | depends on X86_IO_APIC |
c751e17b TG |
454 | depends on X86_32 |
455 | depends on X86_EXTENDED_PLATFORM | |
37bc9f50 | 456 | select X86_REBOOTFIXUPS |
da6b737b SAS |
457 | select OF |
458 | select OF_EARLY_FLATTREE | |
b4e51854 | 459 | select IRQ_DOMAIN |
c751e17b TG |
460 | ---help--- |
461 | Select for the Intel CE media processor (CE4100) SOC. | |
462 | This option compiles in support for the CE4100 SOC for settop | |
463 | boxes and media devices. | |
464 | ||
4cb9b00f | 465 | config X86_INTEL_MID |
43605ef1 AC |
466 | bool "Intel MID platform support" |
467 | depends on X86_32 | |
468 | depends on X86_EXTENDED_PLATFORM | |
edc6bc78 | 469 | depends on X86_PLATFORM_DEVICES |
1ea7c673 AC |
470 | depends on PCI |
471 | depends on PCI_GOANY | |
472 | depends on X86_IO_APIC | |
7c9c3a1e | 473 | select SFI |
4cb9b00f | 474 | select I2C |
7c9c3a1e | 475 | select DW_APB_TIMER |
1ea7c673 | 476 | select APB_TIMER |
1ea7c673 | 477 | select INTEL_SCU_IPC |
15a713df | 478 | select MFD_INTEL_MSIC |
1ea7c673 | 479 | ---help--- |
4cb9b00f DC |
480 | Select to build a kernel capable of supporting Intel MID (Mobile |
481 | Internet Device) platform systems which do not have the PCI legacy | |
482 | interfaces. If you are building for a PC class system say N here. | |
1ea7c673 | 483 | |
4cb9b00f DC |
484 | Intel MID platforms are based on an Intel processor and chipset which |
485 | consume less power than most of the x86 derivatives. | |
43605ef1 | 486 | |
3d48aab1 MW |
487 | config X86_INTEL_LPSS |
488 | bool "Intel Low Power Subsystem Support" | |
489 | depends on ACPI | |
490 | select COMMON_CLK | |
0f531431 | 491 | select PINCTRL |
3d48aab1 MW |
492 | ---help--- |
493 | Select to build support for Intel Low Power Subsystem such as | |
494 | found on Intel Lynxpoint PCH. Selecting this option enables | |
0f531431 MN |
495 | things like clock tree (common clock framework) and pincontrol |
496 | which are needed by the LPSS peripheral drivers. | |
3d48aab1 | 497 | |
ced3ce76 DB |
498 | config IOSF_MBI |
499 | tristate "Intel SoC IOSF Sideband support for SoC platforms" | |
500 | depends on PCI | |
501 | ---help--- | |
502 | This option enables sideband register access support for Intel SoC | |
503 | platforms. On these platforms the IOSF sideband is used in lieu of | |
504 | MSR's for some register accesses, mostly but not limited to thermal | |
505 | and power. Drivers may query the availability of this device to | |
506 | determine if they need the sideband in order to work on these | |
507 | platforms. The sideband is available on the following SoC products. | |
508 | This list is not meant to be exclusive. | |
509 | - BayTrail | |
510 | - Braswell | |
511 | - Quark | |
512 | ||
513 | You should say Y if you are running a kernel on one of these SoC's. | |
514 | ||
ed2226bd DB |
515 | config IOSF_MBI_DEBUG |
516 | bool "Enable IOSF sideband access through debugfs" | |
517 | depends on IOSF_MBI && DEBUG_FS | |
518 | ---help--- | |
519 | Select this option to expose the IOSF sideband access registers (MCR, | |
520 | MDR, MCRX) through debugfs to write and read register information from | |
521 | different units on the SoC. This is most useful for obtaining device | |
522 | state information for debug and analysis. As this is a general access | |
523 | mechanism, users of this option would have specific knowledge of the | |
524 | device they want to access. | |
525 | ||
526 | If you don't require the option or are in doubt, say N. | |
527 | ||
c5c606d9 RT |
528 | config X86_RDC321X |
529 | bool "RDC R-321x SoC" | |
506f1d07 | 530 | depends on X86_32 |
c5c606d9 RT |
531 | depends on X86_EXTENDED_PLATFORM |
532 | select M486 | |
533 | select X86_REBOOTFIXUPS | |
534 | ---help--- | |
535 | This option is needed for RDC R-321x system-on-chip, also known | |
536 | as R-8610-(G). | |
537 | If you don't have one of these chips, you should say N here. | |
538 | ||
e0c7ae37 | 539 | config X86_32_NON_STANDARD |
9c398017 IM |
540 | bool "Support non-standard 32-bit SMP architectures" |
541 | depends on X86_32 && SMP | |
c5c606d9 | 542 | depends on X86_EXTENDED_PLATFORM |
8f9ca475 | 543 | ---help--- |
b5660ba7 PA |
544 | This option compiles in the bigsmp and STA2X11 default |
545 | subarchitectures. It is intended for a generic binary | |
546 | kernel. If you select them all, kernel will probe it one by | |
547 | one and will fallback to default. | |
d49c4288 | 548 | |
c5c606d9 | 549 | # Alphabetically sorted list of Non standard 32 bit platforms |
d49c4288 | 550 | |
d949f36f | 551 | config X86_SUPPORTS_MEMORY_FAILURE |
6fc108a0 | 552 | def_bool y |
d949f36f LT |
553 | # MCE code calls memory_failure(): |
554 | depends on X86_MCE | |
555 | # On 32-bit this adds too big of NODES_SHIFT and we run out of page flags: | |
d949f36f LT |
556 | # On 32-bit SPARSEMEM adds too big of SECTIONS_WIDTH: |
557 | depends on X86_64 || !SPARSEMEM | |
558 | select ARCH_SUPPORTS_MEMORY_FAILURE | |
d949f36f | 559 | |
83125a3a AR |
560 | config STA2X11 |
561 | bool "STA2X11 Companion Chip Support" | |
562 | depends on X86_32_NON_STANDARD && PCI | |
563 | select X86_DEV_DMA_OPS | |
564 | select X86_DMA_REMAP | |
565 | select SWIOTLB | |
566 | select MFD_STA2X11 | |
567 | select ARCH_REQUIRE_GPIOLIB | |
568 | default n | |
569 | ---help--- | |
570 | This adds support for boards based on the STA2X11 IO-Hub, | |
571 | a.k.a. "ConneXt". The chip is used in place of the standard | |
572 | PC chipset, so all "standard" peripherals are missing. If this | |
573 | option is selected the kernel will still be able to boot on | |
574 | standard PC machines. | |
575 | ||
82148d1d S |
576 | config X86_32_IRIS |
577 | tristate "Eurobraille/Iris poweroff module" | |
578 | depends on X86_32 | |
579 | ---help--- | |
580 | The Iris machines from EuroBraille do not have APM or ACPI support | |
581 | to shut themselves down properly. A special I/O sequence is | |
582 | needed to do so, which is what this module does at | |
583 | kernel shutdown. | |
584 | ||
585 | This is only for Iris machines from EuroBraille. | |
586 | ||
587 | If unused, say N. | |
588 | ||
ae1e9130 | 589 | config SCHED_OMIT_FRAME_POINTER |
3c2362e6 HH |
590 | def_bool y |
591 | prompt "Single-depth WCHAN output" | |
a87d0914 | 592 | depends on X86 |
8f9ca475 | 593 | ---help--- |
506f1d07 SR |
594 | Calculate simpler /proc/<PID>/wchan values. If this option |
595 | is disabled then wchan values will recurse back to the | |
596 | caller function. This provides more accurate wchan values, | |
597 | at the expense of slightly more scheduling overhead. | |
598 | ||
599 | If in doubt, say "Y". | |
600 | ||
6276a074 BP |
601 | menuconfig HYPERVISOR_GUEST |
602 | bool "Linux guest support" | |
8f9ca475 | 603 | ---help--- |
6276a074 BP |
604 | Say Y here to enable options for running Linux under various hyper- |
605 | visors. This option enables basic hypervisor detection and platform | |
606 | setup. | |
506f1d07 | 607 | |
6276a074 BP |
608 | If you say N, all options in this submenu will be skipped and |
609 | disabled, and Linux guest support won't be built in. | |
506f1d07 | 610 | |
6276a074 | 611 | if HYPERVISOR_GUEST |
506f1d07 | 612 | |
e61bd94a EPH |
613 | config PARAVIRT |
614 | bool "Enable paravirtualization code" | |
8f9ca475 | 615 | ---help--- |
e61bd94a EPH |
616 | This changes the kernel so it can modify itself when it is run |
617 | under a hypervisor, potentially improving performance significantly | |
618 | over full virtualization. However, when run without a hypervisor | |
619 | the kernel is theoretically slower and slightly larger. | |
620 | ||
6276a074 BP |
621 | config PARAVIRT_DEBUG |
622 | bool "paravirt-ops debugging" | |
623 | depends on PARAVIRT && DEBUG_KERNEL | |
624 | ---help--- | |
625 | Enable to debug paravirt_ops internals. Specifically, BUG if | |
626 | a paravirt_op is missing when it is called. | |
627 | ||
b4ecc126 JF |
628 | config PARAVIRT_SPINLOCKS |
629 | bool "Paravirtualization layer for spinlocks" | |
6ea30386 | 630 | depends on PARAVIRT && SMP |
8db73266 | 631 | select UNINLINE_SPIN_UNLOCK |
b4ecc126 JF |
632 | ---help--- |
633 | Paravirtualized spinlocks allow a pvops backend to replace the | |
634 | spinlock implementation with something virtualization-friendly | |
635 | (for example, block the virtual CPU rather than spinning). | |
636 | ||
4c4e4f61 R |
637 | It has a minimal impact on native kernels and gives a nice performance |
638 | benefit on paravirtualized KVM / Xen kernels. | |
b4ecc126 | 639 | |
4c4e4f61 | 640 | If you are unsure how to answer this question, answer Y. |
b4ecc126 | 641 | |
6276a074 | 642 | source "arch/x86/xen/Kconfig" |
7af192c9 | 643 | |
6276a074 BP |
644 | config KVM_GUEST |
645 | bool "KVM Guest support (including kvmclock)" | |
646 | depends on PARAVIRT | |
647 | select PARAVIRT_CLOCK | |
648 | default y | |
8f9ca475 | 649 | ---help--- |
6276a074 BP |
650 | This option enables various optimizations for running under the KVM |
651 | hypervisor. It includes a paravirtualized clock, so that instead | |
652 | of relying on a PIT (or probably other) emulation by the | |
653 | underlying device model, the host provides the guest with | |
654 | timing infrastructure such as time of day, and system time | |
506f1d07 | 655 | |
1e20eb85 SV |
656 | config KVM_DEBUG_FS |
657 | bool "Enable debug information for KVM Guests in debugfs" | |
658 | depends on KVM_GUEST && DEBUG_FS | |
659 | default n | |
660 | ---help--- | |
661 | This option enables collection of various statistics for KVM guest. | |
662 | Statistics are displayed in debugfs filesystem. Enabling this option | |
663 | may incur significant overhead. | |
664 | ||
6276a074 BP |
665 | source "arch/x86/lguest/Kconfig" |
666 | ||
667 | config PARAVIRT_TIME_ACCOUNTING | |
668 | bool "Paravirtual steal time accounting" | |
669 | depends on PARAVIRT | |
670 | default n | |
8f9ca475 | 671 | ---help--- |
6276a074 BP |
672 | Select this option to enable fine granularity task steal time |
673 | accounting. Time spent executing other tasks in parallel with | |
674 | the current vCPU is discounted from the vCPU power. To account for | |
675 | that, there can be a small performance impact. | |
676 | ||
677 | If in doubt, say N here. | |
678 | ||
679 | config PARAVIRT_CLOCK | |
680 | bool | |
97349135 | 681 | |
6276a074 | 682 | endif #HYPERVISOR_GUEST |
97349135 | 683 | |
08677214 | 684 | config NO_BOOTMEM |
774ea0bc | 685 | def_bool y |
08677214 | 686 | |
03273184 YL |
687 | config MEMTEST |
688 | bool "Memtest" | |
8f9ca475 | 689 | ---help--- |
c64df707 | 690 | This option adds a kernel parameter 'memtest', which allows memtest |
03273184 | 691 | to be set. |
8f9ca475 IM |
692 | memtest=0, mean disabled; -- default |
693 | memtest=1, mean do 1 test pattern; | |
694 | ... | |
695 | memtest=4, mean do 4 test patterns. | |
aba3728c | 696 | If you are unsure how to answer this question, answer N. |
506f1d07 | 697 | |
506f1d07 SR |
698 | source "arch/x86/Kconfig.cpu" |
699 | ||
700 | config HPET_TIMER | |
3c2362e6 | 701 | def_bool X86_64 |
506f1d07 | 702 | prompt "HPET Timer Support" if X86_32 |
8f9ca475 IM |
703 | ---help--- |
704 | Use the IA-PC HPET (High Precision Event Timer) to manage | |
705 | time in preference to the PIT and RTC, if a HPET is | |
706 | present. | |
707 | HPET is the next generation timer replacing legacy 8254s. | |
708 | The HPET provides a stable time base on SMP | |
709 | systems, unlike the TSC, but it is more expensive to access, | |
710 | as it is off-chip. You can find the HPET spec at | |
711 | <http://www.intel.com/hardwaredesign/hpetspec_1.pdf>. | |
506f1d07 | 712 | |
8f9ca475 IM |
713 | You can safely choose Y here. However, HPET will only be |
714 | activated if the platform and the BIOS support this feature. | |
715 | Otherwise the 8254 will be used for timing services. | |
506f1d07 | 716 | |
8f9ca475 | 717 | Choose N to continue using the legacy 8254 timer. |
506f1d07 SR |
718 | |
719 | config HPET_EMULATE_RTC | |
3c2362e6 | 720 | def_bool y |
9d8af78b | 721 | depends on HPET_TIMER && (RTC=y || RTC=m || RTC_DRV_CMOS=m || RTC_DRV_CMOS=y) |
506f1d07 | 722 | |
bb24c471 | 723 | config APB_TIMER |
933b9463 AC |
724 | def_bool y if X86_INTEL_MID |
725 | prompt "Intel MID APB Timer Support" if X86_INTEL_MID | |
06c3df49 | 726 | select DW_APB_TIMER |
a0c3832a | 727 | depends on X86_INTEL_MID && SFI |
bb24c471 JP |
728 | help |
729 | APB timer is the replacement for 8254, HPET on X86 MID platforms. | |
730 | The APBT provides a stable time base on SMP | |
731 | systems, unlike the TSC, but it is more expensive to access, | |
732 | as it is off-chip. APB timers are always running regardless of CPU | |
733 | C states, they are used as per CPU clockevent device when possible. | |
734 | ||
6a108a14 | 735 | # Mark as expert because too many people got it wrong. |
506f1d07 | 736 | # The code disables itself when not needed. |
7ae9392c TP |
737 | config DMI |
738 | default y | |
cf074402 | 739 | select DMI_SCAN_MACHINE_NON_EFI_FALLBACK |
6a108a14 | 740 | bool "Enable DMI scanning" if EXPERT |
8f9ca475 | 741 | ---help--- |
7ae9392c TP |
742 | Enabled scanning of DMI to identify machine quirks. Say Y |
743 | here unless you have verified that your setup is not | |
744 | affected by entries in the DMI blacklist. Required by PNP | |
745 | BIOS code. | |
746 | ||
506f1d07 | 747 | config GART_IOMMU |
38901f1c | 748 | bool "Old AMD GART IOMMU support" |
506f1d07 | 749 | select SWIOTLB |
23ac4ae8 | 750 | depends on X86_64 && PCI && AMD_NB |
8f9ca475 | 751 | ---help--- |
ced3c42c IM |
752 | Provides a driver for older AMD Athlon64/Opteron/Turion/Sempron |
753 | GART based hardware IOMMUs. | |
754 | ||
755 | The GART supports full DMA access for devices with 32-bit access | |
756 | limitations, on systems with more than 3 GB. This is usually needed | |
757 | for USB, sound, many IDE/SATA chipsets and some other devices. | |
758 | ||
759 | Newer systems typically have a modern AMD IOMMU, supported via | |
760 | the CONFIG_AMD_IOMMU=y config option. | |
761 | ||
762 | In normal configurations this driver is only active when needed: | |
763 | there's more than 3 GB of memory and the system contains a | |
764 | 32-bit limited device. | |
765 | ||
766 | If unsure, say Y. | |
506f1d07 SR |
767 | |
768 | config CALGARY_IOMMU | |
769 | bool "IBM Calgary IOMMU support" | |
770 | select SWIOTLB | |
6ea30386 | 771 | depends on X86_64 && PCI |
8f9ca475 | 772 | ---help--- |
506f1d07 SR |
773 | Support for hardware IOMMUs in IBM's xSeries x366 and x460 |
774 | systems. Needed to run systems with more than 3GB of memory | |
775 | properly with 32-bit PCI devices that do not support DAC | |
776 | (Double Address Cycle). Calgary also supports bus level | |
777 | isolation, where all DMAs pass through the IOMMU. This | |
778 | prevents them from going anywhere except their intended | |
779 | destination. This catches hard-to-find kernel bugs and | |
780 | mis-behaving drivers and devices that do not use the DMA-API | |
781 | properly to set up their DMA buffers. The IOMMU can be | |
782 | turned off at boot time with the iommu=off parameter. | |
783 | Normally the kernel will make the right choice by itself. | |
784 | If unsure, say Y. | |
785 | ||
786 | config CALGARY_IOMMU_ENABLED_BY_DEFAULT | |
3c2362e6 HH |
787 | def_bool y |
788 | prompt "Should Calgary be enabled by default?" | |
506f1d07 | 789 | depends on CALGARY_IOMMU |
8f9ca475 | 790 | ---help--- |
506f1d07 SR |
791 | Should Calgary be enabled by default? if you choose 'y', Calgary |
792 | will be used (if it exists). If you choose 'n', Calgary will not be | |
793 | used even if it exists. If you choose 'n' and would like to use | |
794 | Calgary anyway, pass 'iommu=calgary' on the kernel command line. | |
795 | If unsure, say Y. | |
796 | ||
797 | # need this always selected by IOMMU for the VIA workaround | |
798 | config SWIOTLB | |
a1afd01c | 799 | def_bool y if X86_64 |
8f9ca475 | 800 | ---help--- |
506f1d07 | 801 | Support for software bounce buffers used on x86-64 systems |
4454d327 JM |
802 | which don't have a hardware IOMMU. Using this PCI devices |
803 | which can only access 32-bits of memory can be used on systems | |
804 | with more than 3 GB of memory. | |
805 | If unsure, say Y. | |
506f1d07 | 806 | |
a8522509 | 807 | config IOMMU_HELPER |
3120e25e JB |
808 | def_bool y |
809 | depends on CALGARY_IOMMU || GART_IOMMU || SWIOTLB || AMD_IOMMU | |
d25e26b6 | 810 | |
1184dc2f | 811 | config MAXSMP |
ddb0c5a6 | 812 | bool "Enable Maximum number of SMP Processors and NUMA Nodes" |
6ea30386 | 813 | depends on X86_64 && SMP && DEBUG_KERNEL |
36f5101a | 814 | select CPUMASK_OFFSTACK |
8f9ca475 | 815 | ---help--- |
ddb0c5a6 | 816 | Enable maximum number of CPUS and NUMA Nodes for this architecture. |
1184dc2f | 817 | If unsure, say N. |
506f1d07 SR |
818 | |
819 | config NR_CPUS | |
36f5101a | 820 | int "Maximum number of CPUs" if SMP && !MAXSMP |
2a3313f4 | 821 | range 2 8 if SMP && X86_32 && !X86_BIGSMP |
bb61ccc7 | 822 | range 2 512 if SMP && !MAXSMP && !CPUMASK_OFFSTACK |
b53b5eda | 823 | range 2 8192 if SMP && !MAXSMP && CPUMASK_OFFSTACK && X86_64 |
78637a97 | 824 | default "1" if !SMP |
b53b5eda | 825 | default "8192" if MAXSMP |
b5660ba7 | 826 | default "32" if SMP && X86_BIGSMP |
78637a97 | 827 | default "8" if SMP |
8f9ca475 | 828 | ---help--- |
506f1d07 | 829 | This allows you to specify the maximum number of CPUs which this |
bb61ccc7 JB |
830 | kernel will support. If CPUMASK_OFFSTACK is enabled, the maximum |
831 | supported value is 4096, otherwise the maximum value is 512. The | |
506f1d07 SR |
832 | minimum value which makes sense is 2. |
833 | ||
834 | This is purely to save memory - each supported CPU adds | |
835 | approximately eight kilobytes to the kernel image. | |
836 | ||
837 | config SCHED_SMT | |
838 | bool "SMT (Hyperthreading) scheduler support" | |
b089c12b | 839 | depends on X86_HT |
8f9ca475 | 840 | ---help--- |
506f1d07 SR |
841 | SMT scheduler support improves the CPU scheduler's decision making |
842 | when dealing with Intel Pentium 4 chips with HyperThreading at a | |
843 | cost of slightly increased overhead in some places. If unsure say | |
844 | N here. | |
845 | ||
846 | config SCHED_MC | |
3c2362e6 HH |
847 | def_bool y |
848 | prompt "Multi-core scheduler support" | |
b089c12b | 849 | depends on X86_HT |
8f9ca475 | 850 | ---help--- |
506f1d07 SR |
851 | Multi-core scheduler support improves the CPU scheduler's decision |
852 | making when dealing with multi-core CPU chips at a cost of slightly | |
853 | increased overhead in some places. If unsure say N here. | |
854 | ||
855 | source "kernel/Kconfig.preempt" | |
856 | ||
30b8b006 TG |
857 | config UP_LATE_INIT |
858 | def_bool y | |
ba360f88 | 859 | depends on !SMP && X86_LOCAL_APIC |
30b8b006 | 860 | |
506f1d07 SR |
861 | config X86_UP_APIC |
862 | bool "Local APIC support on uniprocessors" | |
38a1dfda | 863 | depends on X86_32 && !SMP && !X86_32_NON_STANDARD |
8f9ca475 | 864 | ---help--- |
506f1d07 SR |
865 | A local APIC (Advanced Programmable Interrupt Controller) is an |
866 | integrated interrupt controller in the CPU. If you have a single-CPU | |
867 | system which has a processor with a local APIC, you can say Y here to | |
868 | enable and use it. If you say Y here even though your machine doesn't | |
869 | have a local APIC, then the kernel will still run with no slowdown at | |
870 | all. The local APIC supports CPU-generated self-interrupts (timer, | |
871 | performance counters), and the NMI watchdog which detects hard | |
872 | lockups. | |
873 | ||
38a1dfda BD |
874 | config X86_UP_APIC_MSI |
875 | def_bool y | |
876 | select X86_UP_APIC if X86_32 && !SMP && !X86_32_NON_STANDARD && PCI_MSI | |
877 | ||
506f1d07 SR |
878 | config X86_UP_IOAPIC |
879 | bool "IO-APIC support on uniprocessors" | |
880 | depends on X86_UP_APIC | |
8f9ca475 | 881 | ---help--- |
506f1d07 SR |
882 | An IO-APIC (I/O Advanced Programmable Interrupt Controller) is an |
883 | SMP-capable replacement for PC-style interrupt controllers. Most | |
884 | SMP systems and many recent uniprocessor systems have one. | |
885 | ||
886 | If you have a single-CPU system with an IO-APIC, you can say Y here | |
887 | to use it. If you say Y here even though your machine doesn't have | |
888 | an IO-APIC, then the kernel will still run with no slowdown at all. | |
889 | ||
890 | config X86_LOCAL_APIC | |
3c2362e6 | 891 | def_bool y |
0dbc6078 | 892 | depends on X86_64 || SMP || X86_32_NON_STANDARD || X86_UP_APIC || PCI_MSI |
74afab7a | 893 | select GENERIC_IRQ_LEGACY_ALLOC_HWIRQ |
506f1d07 SR |
894 | |
895 | config X86_IO_APIC | |
2f600025 JL |
896 | def_bool X86_64 || SMP || X86_32_NON_STANDARD || X86_UP_IOAPIC |
897 | depends on X86_LOCAL_APIC | |
d7f3d478 | 898 | select IRQ_DOMAIN |
506f1d07 | 899 | |
41b9eb26 SA |
900 | config X86_REROUTE_FOR_BROKEN_BOOT_IRQS |
901 | bool "Reroute for broken boot IRQs" | |
41b9eb26 | 902 | depends on X86_IO_APIC |
8f9ca475 | 903 | ---help--- |
41b9eb26 SA |
904 | This option enables a workaround that fixes a source of |
905 | spurious interrupts. This is recommended when threaded | |
906 | interrupt handling is used on systems where the generation of | |
907 | superfluous "boot interrupts" cannot be disabled. | |
908 | ||
909 | Some chipsets generate a legacy INTx "boot IRQ" when the IRQ | |
910 | entry in the chipset's IO-APIC is masked (as, e.g. the RT | |
911 | kernel does during interrupt handling). On chipsets where this | |
912 | boot IRQ generation cannot be disabled, this workaround keeps | |
913 | the original IRQ line masked so that only the equivalent "boot | |
914 | IRQ" is delivered to the CPUs. The workaround also tells the | |
915 | kernel to set up the IRQ handler on the boot IRQ line. In this | |
916 | way only one interrupt is delivered to the kernel. Otherwise | |
917 | the spurious second interrupt may cause the kernel to bring | |
918 | down (vital) interrupt lines. | |
919 | ||
920 | Only affects "broken" chipsets. Interrupt sharing may be | |
921 | increased on these systems. | |
922 | ||
506f1d07 | 923 | config X86_MCE |
bab9bc65 | 924 | bool "Machine Check / overheating reporting" |
e57dbaf7 | 925 | default y |
506f1d07 | 926 | ---help--- |
bab9bc65 AK |
927 | Machine Check support allows the processor to notify the |
928 | kernel if it detects a problem (e.g. overheating, data corruption). | |
506f1d07 | 929 | The action the kernel takes depends on the severity of the problem, |
bab9bc65 | 930 | ranging from warning messages to halting the machine. |
4efc0670 | 931 | |
506f1d07 | 932 | config X86_MCE_INTEL |
3c2362e6 HH |
933 | def_bool y |
934 | prompt "Intel MCE features" | |
c1ebf835 | 935 | depends on X86_MCE && X86_LOCAL_APIC |
8f9ca475 | 936 | ---help--- |
506f1d07 SR |
937 | Additional support for intel specific MCE features such as |
938 | the thermal monitor. | |
939 | ||
940 | config X86_MCE_AMD | |
3c2362e6 HH |
941 | def_bool y |
942 | prompt "AMD MCE features" | |
c1ebf835 | 943 | depends on X86_MCE && X86_LOCAL_APIC |
8f9ca475 | 944 | ---help--- |
506f1d07 SR |
945 | Additional support for AMD specific MCE features such as |
946 | the DRAM Error Threshold. | |
947 | ||
4efc0670 | 948 | config X86_ANCIENT_MCE |
6fc108a0 | 949 | bool "Support for old Pentium 5 / WinChip machine checks" |
c31d9633 | 950 | depends on X86_32 && X86_MCE |
cd13adcc HS |
951 | ---help--- |
952 | Include support for machine check handling on old Pentium 5 or WinChip | |
5065a706 | 953 | systems. These typically need to be enabled explicitly on the command |
cd13adcc | 954 | line. |
4efc0670 | 955 | |
b2762686 AK |
956 | config X86_MCE_THRESHOLD |
957 | depends on X86_MCE_AMD || X86_MCE_INTEL | |
6fc108a0 | 958 | def_bool y |
b2762686 | 959 | |
ea149b36 | 960 | config X86_MCE_INJECT |
c1ebf835 | 961 | depends on X86_MCE |
ea149b36 AK |
962 | tristate "Machine check injector support" |
963 | ---help--- | |
964 | Provide support for injecting machine checks for testing purposes. | |
965 | If you don't know what a machine check is and you don't do kernel | |
966 | QA it is safe to say n. | |
967 | ||
4efc0670 AK |
968 | config X86_THERMAL_VECTOR |
969 | def_bool y | |
5bb38adc | 970 | depends on X86_MCE_INTEL |
4efc0670 | 971 | |
506f1d07 | 972 | config VM86 |
6a108a14 | 973 | bool "Enable VM86 support" if EXPERT |
506f1d07 SR |
974 | default y |
975 | depends on X86_32 | |
8f9ca475 | 976 | ---help--- |
34273f41 PA |
977 | This option is required by programs like DOSEMU to run |
978 | 16-bit real mode legacy code on x86 processors. It also may | |
979 | be needed by software like XFree86 to initialize some video | |
980 | cards via BIOS. Disabling this option saves about 6K. | |
981 | ||
982 | config X86_16BIT | |
983 | bool "Enable support for 16-bit segments" if EXPERT | |
984 | default y | |
985 | ---help--- | |
986 | This option is required by programs like Wine to run 16-bit | |
987 | protected mode legacy code on x86 processors. Disabling | |
988 | this option saves about 300 bytes on i386, or around 6K text | |
989 | plus 16K runtime memory on x86-64, | |
990 | ||
991 | config X86_ESPFIX32 | |
992 | def_bool y | |
993 | depends on X86_16BIT && X86_32 | |
506f1d07 | 994 | |
197725de PA |
995 | config X86_ESPFIX64 |
996 | def_bool y | |
34273f41 | 997 | depends on X86_16BIT && X86_64 |
506f1d07 | 998 | |
1ad83c85 AL |
999 | config X86_VSYSCALL_EMULATION |
1000 | bool "Enable vsyscall emulation" if EXPERT | |
1001 | default y | |
1002 | depends on X86_64 | |
1003 | ---help--- | |
1004 | This enables emulation of the legacy vsyscall page. Disabling | |
1005 | it is roughly equivalent to booting with vsyscall=none, except | |
1006 | that it will also disable the helpful warning if a program | |
1007 | tries to use a vsyscall. With this option set to N, offending | |
1008 | programs will just segfault, citing addresses of the form | |
1009 | 0xffffffffff600?00. | |
1010 | ||
1011 | This option is required by many programs built before 2013, and | |
1012 | care should be used even with newer programs if set to N. | |
1013 | ||
1014 | Disabling this option saves about 7K of kernel size and | |
1015 | possibly 4K of additional runtime pagetable memory. | |
1016 | ||
506f1d07 SR |
1017 | config TOSHIBA |
1018 | tristate "Toshiba Laptop support" | |
1019 | depends on X86_32 | |
1020 | ---help--- | |
1021 | This adds a driver to safely access the System Management Mode of | |
1022 | the CPU on Toshiba portables with a genuine Toshiba BIOS. It does | |
1023 | not work on models with a Phoenix BIOS. The System Management Mode | |
1024 | is used to set the BIOS and power saving options on Toshiba portables. | |
1025 | ||
1026 | For information on utilities to make use of this driver see the | |
1027 | Toshiba Linux utilities web site at: | |
1028 | <http://www.buzzard.org.uk/toshiba/>. | |
1029 | ||
1030 | Say Y if you intend to run this kernel on a Toshiba portable. | |
1031 | Say N otherwise. | |
1032 | ||
1033 | config I8K | |
1034 | tristate "Dell laptop support" | |
949a9d70 | 1035 | select HWMON |
506f1d07 SR |
1036 | ---help--- |
1037 | This adds a driver to safely access the System Management Mode | |
1038 | of the CPU on the Dell Inspiron 8000. The System Management Mode | |
1039 | is used to read cpu temperature and cooling fan status and to | |
1040 | control the fans on the I8K portables. | |
1041 | ||
1042 | This driver has been tested only on the Inspiron 8000 but it may | |
1043 | also work with other Dell laptops. You can force loading on other | |
1044 | models by passing the parameter `force=1' to the module. Use at | |
1045 | your own risk. | |
1046 | ||
1047 | For information on utilities to make use of this driver see the | |
1048 | I8K Linux utilities web site at: | |
1049 | <http://people.debian.org/~dz/i8k/> | |
1050 | ||
1051 | Say Y if you intend to run this kernel on a Dell Inspiron 8000. | |
1052 | Say N otherwise. | |
1053 | ||
1054 | config X86_REBOOTFIXUPS | |
9ba16087 JB |
1055 | bool "Enable X86 board specific fixups for reboot" |
1056 | depends on X86_32 | |
506f1d07 SR |
1057 | ---help--- |
1058 | This enables chipset and/or board specific fixups to be done | |
1059 | in order to get reboot to work correctly. This is only needed on | |
1060 | some combinations of hardware and BIOS. The symptom, for which | |
1061 | this config is intended, is when reboot ends with a stalled/hung | |
1062 | system. | |
1063 | ||
1064 | Currently, the only fixup is for the Geode machines using | |
5e3a77e9 | 1065 | CS5530A and CS5536 chipsets and the RDC R-321x SoC. |
506f1d07 SR |
1066 | |
1067 | Say Y if you want to enable the fixup. Currently, it's safe to | |
1068 | enable this option even if you don't need it. | |
1069 | Say N otherwise. | |
1070 | ||
1071 | config MICROCODE | |
e43f6e67 | 1072 | tristate "CPU microcode loading support" |
80030e3d | 1073 | depends on CPU_SUP_AMD || CPU_SUP_INTEL |
506f1d07 SR |
1074 | select FW_LOADER |
1075 | ---help--- | |
e43f6e67 | 1076 | |
506f1d07 | 1077 | If you say Y here, you will be able to update the microcode on |
80cc9f10 | 1078 | certain Intel and AMD processors. The Intel support is for the |
e43f6e67 BP |
1079 | IA32 family, e.g. Pentium Pro, Pentium II, Pentium III, Pentium 4, |
1080 | Xeon etc. The AMD support is for families 0x10 and later. You will | |
1081 | obviously need the actual microcode binary data itself which is not | |
1082 | shipped with the Linux kernel. | |
506f1d07 | 1083 | |
8d86f390 PO |
1084 | This option selects the general module only, you need to select |
1085 | at least one vendor specific module as well. | |
506f1d07 | 1086 | |
e43f6e67 BP |
1087 | To compile this driver as a module, choose M here: the module |
1088 | will be called microcode. | |
506f1d07 | 1089 | |
8d86f390 | 1090 | config MICROCODE_INTEL |
e43f6e67 | 1091 | bool "Intel microcode loading support" |
8f9ca475 IM |
1092 | depends on MICROCODE |
1093 | default MICROCODE | |
1094 | select FW_LOADER | |
1095 | ---help--- | |
1096 | This options enables microcode patch loading support for Intel | |
1097 | processors. | |
1098 | ||
b8989db9 A |
1099 | For the current Intel microcode data package go to |
1100 | <https://downloadcenter.intel.com> and search for | |
1101 | 'Linux Processor Microcode Data File'. | |
8d86f390 | 1102 | |
80cc9f10 | 1103 | config MICROCODE_AMD |
e43f6e67 | 1104 | bool "AMD microcode loading support" |
8f9ca475 IM |
1105 | depends on MICROCODE |
1106 | select FW_LOADER | |
1107 | ---help--- | |
1108 | If you select this option, microcode patch loading support for AMD | |
1109 | processors will be enabled. | |
80cc9f10 | 1110 | |
8f9ca475 | 1111 | config MICROCODE_OLD_INTERFACE |
3c2362e6 | 1112 | def_bool y |
506f1d07 | 1113 | depends on MICROCODE |
506f1d07 | 1114 | |
da76f64e | 1115 | config MICROCODE_INTEL_EARLY |
e0fd24a3 | 1116 | bool |
757885e9 JS |
1117 | |
1118 | config MICROCODE_AMD_EARLY | |
e0fd24a3 | 1119 | bool |
757885e9 JS |
1120 | |
1121 | config MICROCODE_EARLY | |
da76f64e | 1122 | bool "Early load microcode" |
6b3389ac | 1123 | depends on MICROCODE=y && BLK_DEV_INITRD |
757885e9 JS |
1124 | select MICROCODE_INTEL_EARLY if MICROCODE_INTEL |
1125 | select MICROCODE_AMD_EARLY if MICROCODE_AMD | |
da76f64e FY |
1126 | default y |
1127 | help | |
1128 | This option provides functionality to read additional microcode data | |
1129 | at the beginning of initrd image. The data tells kernel to load | |
1130 | microcode to CPU's as early as possible. No functional change if no | |
1131 | microcode data is glued to the initrd, therefore it's safe to say Y. | |
1132 | ||
506f1d07 SR |
1133 | config X86_MSR |
1134 | tristate "/dev/cpu/*/msr - Model-specific register support" | |
8f9ca475 | 1135 | ---help--- |
506f1d07 SR |
1136 | This device gives privileged processes access to the x86 |
1137 | Model-Specific Registers (MSRs). It is a character device with | |
1138 | major 202 and minors 0 to 31 for /dev/cpu/0/msr to /dev/cpu/31/msr. | |
1139 | MSR accesses are directed to a specific CPU on multi-processor | |
1140 | systems. | |
1141 | ||
1142 | config X86_CPUID | |
1143 | tristate "/dev/cpu/*/cpuid - CPU information support" | |
8f9ca475 | 1144 | ---help--- |
506f1d07 SR |
1145 | This device gives processes access to the x86 CPUID instruction to |
1146 | be executed on a specific processor. It is a character device | |
1147 | with major 203 and minors 0 to 31 for /dev/cpu/0/cpuid to | |
1148 | /dev/cpu/31/cpuid. | |
1149 | ||
1150 | choice | |
1151 | prompt "High Memory Support" | |
6fc108a0 | 1152 | default HIGHMEM4G |
506f1d07 SR |
1153 | depends on X86_32 |
1154 | ||
1155 | config NOHIGHMEM | |
1156 | bool "off" | |
506f1d07 SR |
1157 | ---help--- |
1158 | Linux can use up to 64 Gigabytes of physical memory on x86 systems. | |
1159 | However, the address space of 32-bit x86 processors is only 4 | |
1160 | Gigabytes large. That means that, if you have a large amount of | |
1161 | physical memory, not all of it can be "permanently mapped" by the | |
1162 | kernel. The physical memory that's not permanently mapped is called | |
1163 | "high memory". | |
1164 | ||
1165 | If you are compiling a kernel which will never run on a machine with | |
1166 | more than 1 Gigabyte total physical RAM, answer "off" here (default | |
1167 | choice and suitable for most users). This will result in a "3GB/1GB" | |
1168 | split: 3GB are mapped so that each process sees a 3GB virtual memory | |
1169 | space and the remaining part of the 4GB virtual memory space is used | |
1170 | by the kernel to permanently map as much physical memory as | |
1171 | possible. | |
1172 | ||
1173 | If the machine has between 1 and 4 Gigabytes physical RAM, then | |
1174 | answer "4GB" here. | |
1175 | ||
1176 | If more than 4 Gigabytes is used then answer "64GB" here. This | |
1177 | selection turns Intel PAE (Physical Address Extension) mode on. | |
1178 | PAE implements 3-level paging on IA32 processors. PAE is fully | |
1179 | supported by Linux, PAE mode is implemented on all recent Intel | |
1180 | processors (Pentium Pro and better). NOTE: If you say "64GB" here, | |
1181 | then the kernel will not boot on CPUs that don't support PAE! | |
1182 | ||
1183 | The actual amount of total physical memory will either be | |
1184 | auto detected or can be forced by using a kernel command line option | |
1185 | such as "mem=256M". (Try "man bootparam" or see the documentation of | |
1186 | your boot loader (lilo or loadlin) about how to pass options to the | |
1187 | kernel at boot time.) | |
1188 | ||
1189 | If unsure, say "off". | |
1190 | ||
1191 | config HIGHMEM4G | |
1192 | bool "4GB" | |
8f9ca475 | 1193 | ---help--- |
506f1d07 SR |
1194 | Select this if you have a 32-bit processor and between 1 and 4 |
1195 | gigabytes of physical RAM. | |
1196 | ||
1197 | config HIGHMEM64G | |
1198 | bool "64GB" | |
eb068e78 | 1199 | depends on !M486 |
506f1d07 | 1200 | select X86_PAE |
8f9ca475 | 1201 | ---help--- |
506f1d07 SR |
1202 | Select this if you have a 32-bit processor and more than 4 |
1203 | gigabytes of physical RAM. | |
1204 | ||
1205 | endchoice | |
1206 | ||
1207 | choice | |
6a108a14 | 1208 | prompt "Memory split" if EXPERT |
506f1d07 SR |
1209 | default VMSPLIT_3G |
1210 | depends on X86_32 | |
8f9ca475 | 1211 | ---help--- |
506f1d07 SR |
1212 | Select the desired split between kernel and user memory. |
1213 | ||
1214 | If the address range available to the kernel is less than the | |
1215 | physical memory installed, the remaining memory will be available | |
1216 | as "high memory". Accessing high memory is a little more costly | |
1217 | than low memory, as it needs to be mapped into the kernel first. | |
1218 | Note that increasing the kernel address space limits the range | |
1219 | available to user programs, making the address space there | |
1220 | tighter. Selecting anything other than the default 3G/1G split | |
1221 | will also likely make your kernel incompatible with binary-only | |
1222 | kernel modules. | |
1223 | ||
1224 | If you are not absolutely sure what you are doing, leave this | |
1225 | option alone! | |
1226 | ||
1227 | config VMSPLIT_3G | |
1228 | bool "3G/1G user/kernel split" | |
1229 | config VMSPLIT_3G_OPT | |
1230 | depends on !X86_PAE | |
1231 | bool "3G/1G user/kernel split (for full 1G low memory)" | |
1232 | config VMSPLIT_2G | |
1233 | bool "2G/2G user/kernel split" | |
1234 | config VMSPLIT_2G_OPT | |
1235 | depends on !X86_PAE | |
1236 | bool "2G/2G user/kernel split (for full 2G low memory)" | |
1237 | config VMSPLIT_1G | |
1238 | bool "1G/3G user/kernel split" | |
1239 | endchoice | |
1240 | ||
1241 | config PAGE_OFFSET | |
1242 | hex | |
1243 | default 0xB0000000 if VMSPLIT_3G_OPT | |
1244 | default 0x80000000 if VMSPLIT_2G | |
1245 | default 0x78000000 if VMSPLIT_2G_OPT | |
1246 | default 0x40000000 if VMSPLIT_1G | |
1247 | default 0xC0000000 | |
1248 | depends on X86_32 | |
1249 | ||
1250 | config HIGHMEM | |
3c2362e6 | 1251 | def_bool y |
506f1d07 | 1252 | depends on X86_32 && (HIGHMEM64G || HIGHMEM4G) |
506f1d07 SR |
1253 | |
1254 | config X86_PAE | |
9ba16087 | 1255 | bool "PAE (Physical Address Extension) Support" |
506f1d07 | 1256 | depends on X86_32 && !HIGHMEM4G |
8f9ca475 | 1257 | ---help--- |
506f1d07 SR |
1258 | PAE is required for NX support, and furthermore enables |
1259 | larger swapspace support for non-overcommit purposes. It | |
1260 | has the cost of more pagetable lookup overhead, and also | |
1261 | consumes more pagetable space per process. | |
1262 | ||
600715dc | 1263 | config ARCH_PHYS_ADDR_T_64BIT |
3120e25e JB |
1264 | def_bool y |
1265 | depends on X86_64 || X86_PAE | |
600715dc | 1266 | |
66f2b061 | 1267 | config ARCH_DMA_ADDR_T_64BIT |
3120e25e JB |
1268 | def_bool y |
1269 | depends on X86_64 || HIGHMEM64G | |
66f2b061 | 1270 | |
9e899816 | 1271 | config DIRECT_GBPAGES |
6a108a14 | 1272 | bool "Enable 1GB pages for kernel pagetables" if EXPERT |
9e899816 NP |
1273 | default y |
1274 | depends on X86_64 | |
8f9ca475 | 1275 | ---help--- |
9e899816 NP |
1276 | Allow the kernel linear mapping to use 1GB pages on CPUs that |
1277 | support it. This can improve the kernel's performance a tiny bit by | |
1278 | reducing TLB pressure. If in doubt, say "Y". | |
1279 | ||
506f1d07 SR |
1280 | # Common NUMA Features |
1281 | config NUMA | |
fd51b2d7 | 1282 | bool "Numa Memory Allocation and Scheduler Support" |
506f1d07 | 1283 | depends on SMP |
b5660ba7 PA |
1284 | depends on X86_64 || (X86_32 && HIGHMEM64G && X86_BIGSMP) |
1285 | default y if X86_BIGSMP | |
8f9ca475 | 1286 | ---help--- |
506f1d07 | 1287 | Enable NUMA (Non Uniform Memory Access) support. |
fd51b2d7 | 1288 | |
506f1d07 SR |
1289 | The kernel will try to allocate memory used by a CPU on the |
1290 | local memory controller of the CPU and add some more | |
1291 | NUMA awareness to the kernel. | |
1292 | ||
c280ea5e | 1293 | For 64-bit this is recommended if the system is Intel Core i7 |
fd51b2d7 KM |
1294 | (or later), AMD Opteron, or EM64T NUMA. |
1295 | ||
b5660ba7 | 1296 | For 32-bit this is only needed if you boot a 32-bit |
7cf6c945 | 1297 | kernel on a 64-bit NUMA platform. |
fd51b2d7 KM |
1298 | |
1299 | Otherwise, you should say N. | |
506f1d07 | 1300 | |
eec1d4fa | 1301 | config AMD_NUMA |
3c2362e6 HH |
1302 | def_bool y |
1303 | prompt "Old style AMD Opteron NUMA detection" | |
5da0ef9a | 1304 | depends on X86_64 && NUMA && PCI |
8f9ca475 | 1305 | ---help--- |
eec1d4fa HR |
1306 | Enable AMD NUMA node topology detection. You should say Y here if |
1307 | you have a multi processor AMD system. This uses an old method to | |
1308 | read the NUMA configuration directly from the builtin Northbridge | |
1309 | of Opteron. It is recommended to use X86_64_ACPI_NUMA instead, | |
1310 | which also takes priority if both are compiled in. | |
506f1d07 SR |
1311 | |
1312 | config X86_64_ACPI_NUMA | |
3c2362e6 HH |
1313 | def_bool y |
1314 | prompt "ACPI NUMA detection" | |
506f1d07 SR |
1315 | depends on X86_64 && NUMA && ACPI && PCI |
1316 | select ACPI_NUMA | |
8f9ca475 | 1317 | ---help--- |
506f1d07 SR |
1318 | Enable ACPI SRAT based node topology detection. |
1319 | ||
6ec6e0d9 SS |
1320 | # Some NUMA nodes have memory ranges that span |
1321 | # other nodes. Even though a pfn is valid and | |
1322 | # between a node's start and end pfns, it may not | |
1323 | # reside on that node. See memmap_init_zone() | |
1324 | # for details. | |
1325 | config NODES_SPAN_OTHER_NODES | |
1326 | def_bool y | |
1327 | depends on X86_64_ACPI_NUMA | |
1328 | ||
506f1d07 SR |
1329 | config NUMA_EMU |
1330 | bool "NUMA emulation" | |
1b7e03ef | 1331 | depends on NUMA |
8f9ca475 | 1332 | ---help--- |
506f1d07 SR |
1333 | Enable NUMA emulation. A flat machine will be split |
1334 | into virtual nodes when booted with "numa=fake=N", where N is the | |
1335 | number of nodes. This is only useful for debugging. | |
1336 | ||
1337 | config NODES_SHIFT | |
d25e26b6 | 1338 | int "Maximum NUMA Nodes (as a power of 2)" if !MAXSMP |
51591e31 DR |
1339 | range 1 10 |
1340 | default "10" if MAXSMP | |
506f1d07 | 1341 | default "6" if X86_64 |
506f1d07 SR |
1342 | default "3" |
1343 | depends on NEED_MULTIPLE_NODES | |
8f9ca475 | 1344 | ---help--- |
1184dc2f | 1345 | Specify the maximum number of NUMA Nodes available on the target |
692105b8 | 1346 | system. Increases memory reserved to accommodate various tables. |
506f1d07 | 1347 | |
506f1d07 | 1348 | config ARCH_HAVE_MEMORY_PRESENT |
3c2362e6 | 1349 | def_bool y |
506f1d07 | 1350 | depends on X86_32 && DISCONTIGMEM |
506f1d07 SR |
1351 | |
1352 | config NEED_NODE_MEMMAP_SIZE | |
3c2362e6 | 1353 | def_bool y |
506f1d07 | 1354 | depends on X86_32 && (DISCONTIGMEM || SPARSEMEM) |
506f1d07 | 1355 | |
506f1d07 SR |
1356 | config ARCH_FLATMEM_ENABLE |
1357 | def_bool y | |
3b16651f | 1358 | depends on X86_32 && !NUMA |
506f1d07 SR |
1359 | |
1360 | config ARCH_DISCONTIGMEM_ENABLE | |
1361 | def_bool y | |
b263295d | 1362 | depends on NUMA && X86_32 |
506f1d07 SR |
1363 | |
1364 | config ARCH_DISCONTIGMEM_DEFAULT | |
1365 | def_bool y | |
b263295d CL |
1366 | depends on NUMA && X86_32 |
1367 | ||
506f1d07 SR |
1368 | config ARCH_SPARSEMEM_ENABLE |
1369 | def_bool y | |
6ea30386 | 1370 | depends on X86_64 || NUMA || X86_32 || X86_32_NON_STANDARD |
506f1d07 SR |
1371 | select SPARSEMEM_STATIC if X86_32 |
1372 | select SPARSEMEM_VMEMMAP_ENABLE if X86_64 | |
1373 | ||
3b16651f TH |
1374 | config ARCH_SPARSEMEM_DEFAULT |
1375 | def_bool y | |
1376 | depends on X86_64 | |
1377 | ||
506f1d07 SR |
1378 | config ARCH_SELECT_MEMORY_MODEL |
1379 | def_bool y | |
b263295d | 1380 | depends on ARCH_SPARSEMEM_ENABLE |
506f1d07 SR |
1381 | |
1382 | config ARCH_MEMORY_PROBE | |
a0842b70 | 1383 | bool "Enable sysfs memory/probe interface" |
3120e25e | 1384 | depends on X86_64 && MEMORY_HOTPLUG |
a0842b70 TK |
1385 | help |
1386 | This option enables a sysfs memory/probe interface for testing. | |
1387 | See Documentation/memory-hotplug.txt for more information. | |
1388 | If you are unsure how to answer this question, answer N. | |
506f1d07 | 1389 | |
3b16651f TH |
1390 | config ARCH_PROC_KCORE_TEXT |
1391 | def_bool y | |
1392 | depends on X86_64 && PROC_KCORE | |
1393 | ||
a29815a3 AK |
1394 | config ILLEGAL_POINTER_VALUE |
1395 | hex | |
1396 | default 0 if X86_32 | |
1397 | default 0xdead000000000000 if X86_64 | |
1398 | ||
506f1d07 SR |
1399 | source "mm/Kconfig" |
1400 | ||
1401 | config HIGHPTE | |
1402 | bool "Allocate 3rd-level pagetables from highmem" | |
6fc108a0 | 1403 | depends on HIGHMEM |
8f9ca475 | 1404 | ---help--- |
506f1d07 SR |
1405 | The VM uses one page table entry for each page of physical memory. |
1406 | For systems with a lot of RAM, this can be wasteful of precious | |
1407 | low memory. Setting this option will put user-space page table | |
1408 | entries in high memory. | |
1409 | ||
9f077871 | 1410 | config X86_CHECK_BIOS_CORRUPTION |
8f9ca475 IM |
1411 | bool "Check for low memory corruption" |
1412 | ---help--- | |
1413 | Periodically check for memory corruption in low memory, which | |
1414 | is suspected to be caused by BIOS. Even when enabled in the | |
1415 | configuration, it is disabled at runtime. Enable it by | |
1416 | setting "memory_corruption_check=1" on the kernel command | |
1417 | line. By default it scans the low 64k of memory every 60 | |
1418 | seconds; see the memory_corruption_check_size and | |
1419 | memory_corruption_check_period parameters in | |
1420 | Documentation/kernel-parameters.txt to adjust this. | |
1421 | ||
1422 | When enabled with the default parameters, this option has | |
1423 | almost no overhead, as it reserves a relatively small amount | |
1424 | of memory and scans it infrequently. It both detects corruption | |
1425 | and prevents it from affecting the running system. | |
1426 | ||
1427 | It is, however, intended as a diagnostic tool; if repeatable | |
1428 | BIOS-originated corruption always affects the same memory, | |
1429 | you can use memmap= to prevent the kernel from using that | |
1430 | memory. | |
9f077871 | 1431 | |
c885df50 | 1432 | config X86_BOOTPARAM_MEMORY_CORRUPTION_CHECK |
8f9ca475 | 1433 | bool "Set the default setting of memory_corruption_check" |
c885df50 JF |
1434 | depends on X86_CHECK_BIOS_CORRUPTION |
1435 | default y | |
8f9ca475 IM |
1436 | ---help--- |
1437 | Set whether the default state of memory_corruption_check is | |
1438 | on or off. | |
c885df50 | 1439 | |
9ea77bdb | 1440 | config X86_RESERVE_LOW |
d0cd7425 PA |
1441 | int "Amount of low memory, in kilobytes, to reserve for the BIOS" |
1442 | default 64 | |
1443 | range 4 640 | |
8f9ca475 | 1444 | ---help--- |
d0cd7425 PA |
1445 | Specify the amount of low memory to reserve for the BIOS. |
1446 | ||
1447 | The first page contains BIOS data structures that the kernel | |
1448 | must not use, so that page must always be reserved. | |
1449 | ||
1450 | By default we reserve the first 64K of physical RAM, as a | |
1451 | number of BIOSes are known to corrupt that memory range | |
1452 | during events such as suspend/resume or monitor cable | |
1453 | insertion, so it must not be used by the kernel. | |
fc381519 | 1454 | |
d0cd7425 PA |
1455 | You can set this to 4 if you are absolutely sure that you |
1456 | trust the BIOS to get all its memory reservations and usages | |
1457 | right. If you know your BIOS have problems beyond the | |
1458 | default 64K area, you can set this to 640 to avoid using the | |
1459 | entire low memory range. | |
fc381519 | 1460 | |
d0cd7425 PA |
1461 | If you have doubts about the BIOS (e.g. suspend/resume does |
1462 | not work or there's kernel crashes after certain hardware | |
1463 | hotplug events) then you might want to enable | |
1464 | X86_CHECK_BIOS_CORRUPTION=y to allow the kernel to check | |
1465 | typical corruption patterns. | |
fc381519 | 1466 | |
d0cd7425 | 1467 | Leave this to the default value of 64 if you are unsure. |
fc381519 | 1468 | |
506f1d07 SR |
1469 | config MATH_EMULATION |
1470 | bool | |
1471 | prompt "Math emulation" if X86_32 | |
1472 | ---help--- | |
1473 | Linux can emulate a math coprocessor (used for floating point | |
1474 | operations) if you don't have one. 486DX and Pentium processors have | |
1475 | a math coprocessor built in, 486SX and 386 do not, unless you added | |
1476 | a 487DX or 387, respectively. (The messages during boot time can | |
1477 | give you some hints here ["man dmesg"].) Everyone needs either a | |
1478 | coprocessor or this emulation. | |
1479 | ||
1480 | If you don't have a math coprocessor, you need to say Y here; if you | |
1481 | say Y here even though you have a coprocessor, the coprocessor will | |
1482 | be used nevertheless. (This behavior can be changed with the kernel | |
1483 | command line option "no387", which comes handy if your coprocessor | |
1484 | is broken. Try "man bootparam" or see the documentation of your boot | |
1485 | loader (lilo or loadlin) about how to pass options to the kernel at | |
1486 | boot time.) This means that it is a good idea to say Y here if you | |
1487 | intend to use this kernel on different machines. | |
1488 | ||
1489 | More information about the internals of the Linux math coprocessor | |
1490 | emulation can be found in <file:arch/x86/math-emu/README>. | |
1491 | ||
1492 | If you are not sure, say Y; apart from resulting in a 66 KB bigger | |
1493 | kernel, it won't hurt. | |
1494 | ||
1495 | config MTRR | |
6fc108a0 | 1496 | def_bool y |
6a108a14 | 1497 | prompt "MTRR (Memory Type Range Register) support" if EXPERT |
506f1d07 SR |
1498 | ---help--- |
1499 | On Intel P6 family processors (Pentium Pro, Pentium II and later) | |
1500 | the Memory Type Range Registers (MTRRs) may be used to control | |
1501 | processor access to memory ranges. This is most useful if you have | |
1502 | a video (VGA) card on a PCI or AGP bus. Enabling write-combining | |
1503 | allows bus write transfers to be combined into a larger transfer | |
1504 | before bursting over the PCI/AGP bus. This can increase performance | |
1505 | of image write operations 2.5 times or more. Saying Y here creates a | |
1506 | /proc/mtrr file which may be used to manipulate your processor's | |
1507 | MTRRs. Typically the X server should use this. | |
1508 | ||
1509 | This code has a reasonably generic interface so that similar | |
1510 | control registers on other processors can be easily supported | |
1511 | as well: | |
1512 | ||
1513 | The Cyrix 6x86, 6x86MX and M II processors have Address Range | |
1514 | Registers (ARRs) which provide a similar functionality to MTRRs. For | |
1515 | these, the ARRs are used to emulate the MTRRs. | |
1516 | The AMD K6-2 (stepping 8 and above) and K6-3 processors have two | |
1517 | MTRRs. The Centaur C6 (WinChip) has 8 MCRs, allowing | |
1518 | write-combining. All of these processors are supported by this code | |
1519 | and it makes sense to say Y here if you have one of them. | |
1520 | ||
1521 | Saying Y here also fixes a problem with buggy SMP BIOSes which only | |
1522 | set the MTRRs for the boot CPU and not for the secondary CPUs. This | |
1523 | can lead to all sorts of problems, so it's good to say Y here. | |
1524 | ||
1525 | You can safely say Y even if your machine doesn't have MTRRs, you'll | |
1526 | just add about 9 KB to your kernel. | |
1527 | ||
7225e751 | 1528 | See <file:Documentation/x86/mtrr.txt> for more information. |
506f1d07 | 1529 | |
95ffa243 | 1530 | config MTRR_SANITIZER |
2ffb3501 | 1531 | def_bool y |
95ffa243 YL |
1532 | prompt "MTRR cleanup support" |
1533 | depends on MTRR | |
8f9ca475 | 1534 | ---help--- |
aba3728c TG |
1535 | Convert MTRR layout from continuous to discrete, so X drivers can |
1536 | add writeback entries. | |
95ffa243 | 1537 | |
aba3728c | 1538 | Can be disabled with disable_mtrr_cleanup on the kernel command line. |
692105b8 | 1539 | The largest mtrr entry size for a continuous block can be set with |
aba3728c | 1540 | mtrr_chunk_size. |
95ffa243 | 1541 | |
2ffb3501 | 1542 | If unsure, say Y. |
95ffa243 YL |
1543 | |
1544 | config MTRR_SANITIZER_ENABLE_DEFAULT | |
f5098d62 YL |
1545 | int "MTRR cleanup enable value (0-1)" |
1546 | range 0 1 | |
1547 | default "0" | |
95ffa243 | 1548 | depends on MTRR_SANITIZER |
8f9ca475 | 1549 | ---help--- |
f5098d62 | 1550 | Enable mtrr cleanup default value |
95ffa243 | 1551 | |
12031a62 YL |
1552 | config MTRR_SANITIZER_SPARE_REG_NR_DEFAULT |
1553 | int "MTRR cleanup spare reg num (0-7)" | |
1554 | range 0 7 | |
1555 | default "1" | |
1556 | depends on MTRR_SANITIZER | |
8f9ca475 | 1557 | ---help--- |
12031a62 | 1558 | mtrr cleanup spare entries default, it can be changed via |
aba3728c | 1559 | mtrr_spare_reg_nr=N on the kernel command line. |
12031a62 | 1560 | |
2e5d9c85 | 1561 | config X86_PAT |
6fc108a0 | 1562 | def_bool y |
6a108a14 | 1563 | prompt "x86 PAT support" if EXPERT |
2a8a2719 | 1564 | depends on MTRR |
8f9ca475 | 1565 | ---help--- |
2e5d9c85 | 1566 | Use PAT attributes to setup page level cache control. |
042b78e4 | 1567 | |
2e5d9c85 | 1568 | PATs are the modern equivalents of MTRRs and are much more |
1569 | flexible than MTRRs. | |
1570 | ||
1571 | Say N here if you see bootup problems (boot crash, boot hang, | |
042b78e4 | 1572 | spontaneous reboots) or a non-working video driver. |
2e5d9c85 | 1573 | |
1574 | If unsure, say Y. | |
1575 | ||
46cf98cd VP |
1576 | config ARCH_USES_PG_UNCACHED |
1577 | def_bool y | |
1578 | depends on X86_PAT | |
1579 | ||
628c6246 PA |
1580 | config ARCH_RANDOM |
1581 | def_bool y | |
1582 | prompt "x86 architectural random number generator" if EXPERT | |
1583 | ---help--- | |
1584 | Enable the x86 architectural RDRAND instruction | |
1585 | (Intel Bull Mountain technology) to generate random numbers. | |
1586 | If supported, this is a high bandwidth, cryptographically | |
1587 | secure hardware random number generator. | |
1588 | ||
51ae4a2d PA |
1589 | config X86_SMAP |
1590 | def_bool y | |
1591 | prompt "Supervisor Mode Access Prevention" if EXPERT | |
1592 | ---help--- | |
1593 | Supervisor Mode Access Prevention (SMAP) is a security | |
1594 | feature in newer Intel processors. There is a small | |
1595 | performance cost if this enabled and turned on; there is | |
1596 | also a small increase in the kernel size if this is enabled. | |
1597 | ||
1598 | If unsure, say Y. | |
1599 | ||
72e9b5fe DH |
1600 | config X86_INTEL_MPX |
1601 | prompt "Intel MPX (Memory Protection Extensions)" | |
1602 | def_bool n | |
1603 | depends on CPU_SUP_INTEL | |
1604 | ---help--- | |
1605 | MPX provides hardware features that can be used in | |
1606 | conjunction with compiler-instrumented code to check | |
1607 | memory references. It is designed to detect buffer | |
1608 | overflow or underflow bugs. | |
1609 | ||
1610 | This option enables running applications which are | |
1611 | instrumented or otherwise use MPX. It does not use MPX | |
1612 | itself inside the kernel or to protect the kernel | |
1613 | against bad memory references. | |
1614 | ||
1615 | Enabling this option will make the kernel larger: | |
1616 | ~8k of kernel text and 36 bytes of data on a 64-bit | |
1617 | defconfig. It adds a long to the 'mm_struct' which | |
1618 | will increase the kernel memory overhead of each | |
1619 | process and adds some branches to paths used during | |
1620 | exec() and munmap(). | |
1621 | ||
1622 | For details, see Documentation/x86/intel_mpx.txt | |
1623 | ||
1624 | If unsure, say N. | |
1625 | ||
506f1d07 | 1626 | config EFI |
9ba16087 | 1627 | bool "EFI runtime service support" |
5b83683f | 1628 | depends on ACPI |
f6ce5002 | 1629 | select UCS2_STRING |
022ee6c5 | 1630 | select EFI_RUNTIME_WRAPPERS |
506f1d07 | 1631 | ---help--- |
8f9ca475 IM |
1632 | This enables the kernel to use EFI runtime services that are |
1633 | available (such as the EFI variable services). | |
506f1d07 | 1634 | |
8f9ca475 IM |
1635 | This option is only useful on systems that have EFI firmware. |
1636 | In addition, you should use the latest ELILO loader available | |
1637 | at <http://elilo.sourceforge.net> in order to take advantage | |
1638 | of EFI runtime services. However, even with this option, the | |
1639 | resultant kernel should continue to boot on existing non-EFI | |
1640 | platforms. | |
506f1d07 | 1641 | |
291f3632 MF |
1642 | config EFI_STUB |
1643 | bool "EFI stub support" | |
b16d8c23 | 1644 | depends on EFI && !X86_USE_3DNOW |
7b2a583a | 1645 | select RELOCATABLE |
291f3632 MF |
1646 | ---help--- |
1647 | This kernel feature allows a bzImage to be loaded directly | |
1648 | by EFI firmware without the use of a bootloader. | |
1649 | ||
4172fe2f | 1650 | See Documentation/efi-stub.txt for more information. |
0c759662 | 1651 | |
7d453eee MF |
1652 | config EFI_MIXED |
1653 | bool "EFI mixed-mode support" | |
1654 | depends on EFI_STUB && X86_64 | |
1655 | ---help--- | |
1656 | Enabling this feature allows a 64-bit kernel to be booted | |
1657 | on a 32-bit firmware, provided that your CPU supports 64-bit | |
1658 | mode. | |
1659 | ||
1660 | Note that it is not possible to boot a mixed-mode enabled | |
1661 | kernel via the EFI boot stub - a bootloader that supports | |
1662 | the EFI handover protocol must be used. | |
1663 | ||
1664 | If unsure, say N. | |
1665 | ||
506f1d07 | 1666 | config SECCOMP |
3c2362e6 HH |
1667 | def_bool y |
1668 | prompt "Enable seccomp to safely compute untrusted bytecode" | |
8f9ca475 | 1669 | ---help--- |
506f1d07 SR |
1670 | This kernel feature is useful for number crunching applications |
1671 | that may need to compute untrusted bytecode during their | |
1672 | execution. By using pipes or other transports made available to | |
1673 | the process as file descriptors supporting the read/write | |
1674 | syscalls, it's possible to isolate those applications in | |
1675 | their own address space using seccomp. Once seccomp is | |
9c0bbee8 | 1676 | enabled via prctl(PR_SET_SECCOMP), it cannot be disabled |
506f1d07 SR |
1677 | and the task is only allowed to execute a few safe syscalls |
1678 | defined by each seccomp mode. | |
1679 | ||
1680 | If unsure, say Y. Only embedded should say N here. | |
1681 | ||
506f1d07 SR |
1682 | source kernel/Kconfig.hz |
1683 | ||
1684 | config KEXEC | |
1685 | bool "kexec system call" | |
8f9ca475 | 1686 | ---help--- |
506f1d07 SR |
1687 | kexec is a system call that implements the ability to shutdown your |
1688 | current kernel, and to start another kernel. It is like a reboot | |
1689 | but it is independent of the system firmware. And like a reboot | |
1690 | you can start any kernel with it, not just Linux. | |
1691 | ||
1692 | The name comes from the similarity to the exec system call. | |
1693 | ||
1694 | It is an ongoing process to be certain the hardware in a machine | |
1695 | is properly shutdown, so do not be surprised if this code does not | |
bf220695 GU |
1696 | initially work for you. As of this writing the exact hardware |
1697 | interface is strongly in flux, so no good recommendation can be | |
1698 | made. | |
506f1d07 | 1699 | |
74ca317c VG |
1700 | config KEXEC_FILE |
1701 | bool "kexec file based system call" | |
1702 | select BUILD_BIN2C | |
1703 | depends on KEXEC | |
1704 | depends on X86_64 | |
1705 | depends on CRYPTO=y | |
1706 | depends on CRYPTO_SHA256=y | |
1707 | ---help--- | |
1708 | This is new version of kexec system call. This system call is | |
1709 | file based and takes file descriptors as system call argument | |
1710 | for kernel and initramfs as opposed to list of segments as | |
1711 | accepted by previous system call. | |
1712 | ||
8e7d8381 VG |
1713 | config KEXEC_VERIFY_SIG |
1714 | bool "Verify kernel signature during kexec_file_load() syscall" | |
74ca317c | 1715 | depends on KEXEC_FILE |
8e7d8381 VG |
1716 | ---help--- |
1717 | This option makes kernel signature verification mandatory for | |
1718 | kexec_file_load() syscall. If kernel is signature can not be | |
1719 | verified, kexec_file_load() will fail. | |
1720 | ||
1721 | This option enforces signature verification at generic level. | |
1722 | One needs to enable signature verification for type of kernel | |
1723 | image being loaded to make sure it works. For example, enable | |
1724 | bzImage signature verification option to be able to load and | |
1725 | verify signatures of bzImage. Otherwise kernel loading will fail. | |
1726 | ||
1727 | config KEXEC_BZIMAGE_VERIFY_SIG | |
1728 | bool "Enable bzImage signature verification support" | |
1729 | depends on KEXEC_VERIFY_SIG | |
1730 | depends on SIGNED_PE_FILE_VERIFICATION | |
1731 | select SYSTEM_TRUSTED_KEYRING | |
1732 | ---help--- | |
1733 | Enable bzImage signature verification support. | |
1734 | ||
506f1d07 | 1735 | config CRASH_DUMP |
04b69447 | 1736 | bool "kernel crash dumps" |
506f1d07 | 1737 | depends on X86_64 || (X86_32 && HIGHMEM) |
8f9ca475 | 1738 | ---help--- |
506f1d07 SR |
1739 | Generate crash dump after being started by kexec. |
1740 | This should be normally only set in special crash dump kernels | |
1741 | which are loaded in the main kernel with kexec-tools into | |
1742 | a specially reserved region and then later executed after | |
1743 | a crash by kdump/kexec. The crash dump kernel must be compiled | |
1744 | to a memory address not used by the main kernel or BIOS using | |
1745 | PHYSICAL_START, or it must be built as a relocatable image | |
1746 | (CONFIG_RELOCATABLE=y). | |
1747 | For more details see Documentation/kdump/kdump.txt | |
1748 | ||
3ab83521 | 1749 | config KEXEC_JUMP |
6ea30386 | 1750 | bool "kexec jump" |
fee7b0d8 | 1751 | depends on KEXEC && HIBERNATION |
8f9ca475 | 1752 | ---help--- |
89081d17 HY |
1753 | Jump between original kernel and kexeced kernel and invoke |
1754 | code in physical address mode via KEXEC | |
3ab83521 | 1755 | |
506f1d07 | 1756 | config PHYSICAL_START |
6a108a14 | 1757 | hex "Physical address where the kernel is loaded" if (EXPERT || CRASH_DUMP) |
ceefccc9 | 1758 | default "0x1000000" |
8f9ca475 | 1759 | ---help--- |
506f1d07 SR |
1760 | This gives the physical address where the kernel is loaded. |
1761 | ||
1762 | If kernel is a not relocatable (CONFIG_RELOCATABLE=n) then | |
1763 | bzImage will decompress itself to above physical address and | |
1764 | run from there. Otherwise, bzImage will run from the address where | |
1765 | it has been loaded by the boot loader and will ignore above physical | |
1766 | address. | |
1767 | ||
1768 | In normal kdump cases one does not have to set/change this option | |
1769 | as now bzImage can be compiled as a completely relocatable image | |
1770 | (CONFIG_RELOCATABLE=y) and be used to load and run from a different | |
1771 | address. This option is mainly useful for the folks who don't want | |
1772 | to use a bzImage for capturing the crash dump and want to use a | |
1773 | vmlinux instead. vmlinux is not relocatable hence a kernel needs | |
1774 | to be specifically compiled to run from a specific memory area | |
1775 | (normally a reserved region) and this option comes handy. | |
1776 | ||
ceefccc9 PA |
1777 | So if you are using bzImage for capturing the crash dump, |
1778 | leave the value here unchanged to 0x1000000 and set | |
1779 | CONFIG_RELOCATABLE=y. Otherwise if you plan to use vmlinux | |
1780 | for capturing the crash dump change this value to start of | |
1781 | the reserved region. In other words, it can be set based on | |
1782 | the "X" value as specified in the "crashkernel=YM@XM" | |
1783 | command line boot parameter passed to the panic-ed | |
1784 | kernel. Please take a look at Documentation/kdump/kdump.txt | |
1785 | for more details about crash dumps. | |
506f1d07 SR |
1786 | |
1787 | Usage of bzImage for capturing the crash dump is recommended as | |
1788 | one does not have to build two kernels. Same kernel can be used | |
1789 | as production kernel and capture kernel. Above option should have | |
1790 | gone away after relocatable bzImage support is introduced. But it | |
1791 | is present because there are users out there who continue to use | |
1792 | vmlinux for dump capture. This option should go away down the | |
1793 | line. | |
1794 | ||
1795 | Don't change this unless you know what you are doing. | |
1796 | ||
1797 | config RELOCATABLE | |
26717808 PA |
1798 | bool "Build a relocatable kernel" |
1799 | default y | |
8f9ca475 | 1800 | ---help--- |
506f1d07 SR |
1801 | This builds a kernel image that retains relocation information |
1802 | so it can be loaded someplace besides the default 1MB. | |
1803 | The relocations tend to make the kernel binary about 10% larger, | |
1804 | but are discarded at runtime. | |
1805 | ||
1806 | One use is for the kexec on panic case where the recovery kernel | |
1807 | must live at a different physical address than the primary | |
1808 | kernel. | |
1809 | ||
1810 | Note: If CONFIG_RELOCATABLE=y, then the kernel runs from the address | |
1811 | it has been loaded at and the compile time physical address | |
8ab3820f | 1812 | (CONFIG_PHYSICAL_START) is used as the minimum location. |
506f1d07 | 1813 | |
8ab3820f KC |
1814 | config RANDOMIZE_BASE |
1815 | bool "Randomize the address of the kernel image" | |
1816 | depends on RELOCATABLE | |
8ab3820f KC |
1817 | default n |
1818 | ---help--- | |
1819 | Randomizes the physical and virtual address at which the | |
1820 | kernel image is decompressed, as a security feature that | |
1821 | deters exploit attempts relying on knowledge of the location | |
1822 | of kernel internals. | |
1823 | ||
a653f356 KC |
1824 | Entropy is generated using the RDRAND instruction if it is |
1825 | supported. If RDTSC is supported, it is used as well. If | |
1826 | neither RDRAND nor RDTSC are supported, then randomness is | |
1827 | read from the i8254 timer. | |
8ab3820f KC |
1828 | |
1829 | The kernel will be offset by up to RANDOMIZE_BASE_MAX_OFFSET, | |
a653f356 KC |
1830 | and aligned according to PHYSICAL_ALIGN. Since the kernel is |
1831 | built using 2GiB addressing, and PHYSICAL_ALGIN must be at a | |
1832 | minimum of 2MiB, only 10 bits of entropy is theoretically | |
1833 | possible. At best, due to page table layouts, 64-bit can use | |
1834 | 9 bits of entropy and 32-bit uses 8 bits. | |
8ab3820f | 1835 | |
da2b6fb9 KC |
1836 | If unsure, say N. |
1837 | ||
8ab3820f | 1838 | config RANDOMIZE_BASE_MAX_OFFSET |
da2b6fb9 | 1839 | hex "Maximum kASLR offset allowed" if EXPERT |
8ab3820f | 1840 | depends on RANDOMIZE_BASE |
6145cfe3 KC |
1841 | range 0x0 0x20000000 if X86_32 |
1842 | default "0x20000000" if X86_32 | |
1843 | range 0x0 0x40000000 if X86_64 | |
1844 | default "0x40000000" if X86_64 | |
8ab3820f | 1845 | ---help--- |
da2b6fb9 KC |
1846 | The lesser of RANDOMIZE_BASE_MAX_OFFSET and available physical |
1847 | memory is used to determine the maximal offset in bytes that will | |
1848 | be applied to the kernel when kernel Address Space Layout | |
1849 | Randomization (kASLR) is active. This must be a multiple of | |
1850 | PHYSICAL_ALIGN. | |
1851 | ||
1852 | On 32-bit this is limited to 512MiB by page table layouts. The | |
1853 | default is 512MiB. | |
6145cfe3 | 1854 | |
da2b6fb9 KC |
1855 | On 64-bit this is limited by how the kernel fixmap page table is |
1856 | positioned, so this cannot be larger than 1GiB currently. Without | |
1857 | RANDOMIZE_BASE, there is a 512MiB to 1.5GiB split between kernel | |
1858 | and modules. When RANDOMIZE_BASE_MAX_OFFSET is above 512MiB, the | |
1859 | modules area will shrink to compensate, up to the current maximum | |
1860 | 1GiB to 1GiB split. The default is 1GiB. | |
6145cfe3 | 1861 | |
da2b6fb9 | 1862 | If unsure, leave at the default value. |
8ab3820f KC |
1863 | |
1864 | # Relocation on x86 needs some additional build support | |
845adf72 PA |
1865 | config X86_NEED_RELOCS |
1866 | def_bool y | |
8ab3820f | 1867 | depends on RANDOMIZE_BASE || (X86_32 && RELOCATABLE) |
845adf72 | 1868 | |
506f1d07 | 1869 | config PHYSICAL_ALIGN |
a0215061 | 1870 | hex "Alignment value to which kernel should be aligned" |
8ab3820f | 1871 | default "0x200000" |
a0215061 KC |
1872 | range 0x2000 0x1000000 if X86_32 |
1873 | range 0x200000 0x1000000 if X86_64 | |
8f9ca475 | 1874 | ---help--- |
506f1d07 SR |
1875 | This value puts the alignment restrictions on physical address |
1876 | where kernel is loaded and run from. Kernel is compiled for an | |
1877 | address which meets above alignment restriction. | |
1878 | ||
1879 | If bootloader loads the kernel at a non-aligned address and | |
1880 | CONFIG_RELOCATABLE is set, kernel will move itself to nearest | |
1881 | address aligned to above value and run from there. | |
1882 | ||
1883 | If bootloader loads the kernel at a non-aligned address and | |
1884 | CONFIG_RELOCATABLE is not set, kernel will ignore the run time | |
1885 | load address and decompress itself to the address it has been | |
1886 | compiled for and run from there. The address for which kernel is | |
1887 | compiled already meets above alignment restrictions. Hence the | |
1888 | end result is that kernel runs from a physical address meeting | |
1889 | above alignment restrictions. | |
1890 | ||
a0215061 KC |
1891 | On 32-bit this value must be a multiple of 0x2000. On 64-bit |
1892 | this value must be a multiple of 0x200000. | |
1893 | ||
506f1d07 SR |
1894 | Don't change this unless you know what you are doing. |
1895 | ||
1896 | config HOTPLUG_CPU | |
7c13e6a3 | 1897 | bool "Support for hot-pluggable CPUs" |
40b31360 | 1898 | depends on SMP |
506f1d07 | 1899 | ---help--- |
7c13e6a3 DS |
1900 | Say Y here to allow turning CPUs off and on. CPUs can be |
1901 | controlled through /sys/devices/system/cpu. | |
1902 | ( Note: power management support will enable this option | |
1903 | automatically on SMP systems. ) | |
1904 | Say N if you want to disable CPU hotplug. | |
506f1d07 | 1905 | |
80aa1dff FY |
1906 | config BOOTPARAM_HOTPLUG_CPU0 |
1907 | bool "Set default setting of cpu0_hotpluggable" | |
1908 | default n | |
2c922cd0 | 1909 | depends on HOTPLUG_CPU |
80aa1dff FY |
1910 | ---help--- |
1911 | Set whether default state of cpu0_hotpluggable is on or off. | |
1912 | ||
1913 | Say Y here to enable CPU0 hotplug by default. If this switch | |
1914 | is turned on, there is no need to give cpu0_hotplug kernel | |
1915 | parameter and the CPU0 hotplug feature is enabled by default. | |
1916 | ||
1917 | Please note: there are two known CPU0 dependencies if you want | |
1918 | to enable the CPU0 hotplug feature either by this switch or by | |
1919 | cpu0_hotplug kernel parameter. | |
1920 | ||
1921 | First, resume from hibernate or suspend always starts from CPU0. | |
1922 | So hibernate and suspend are prevented if CPU0 is offline. | |
1923 | ||
1924 | Second dependency is PIC interrupts always go to CPU0. CPU0 can not | |
1925 | offline if any interrupt can not migrate out of CPU0. There may | |
1926 | be other CPU0 dependencies. | |
1927 | ||
1928 | Please make sure the dependencies are under your control before | |
1929 | you enable this feature. | |
1930 | ||
1931 | Say N if you don't want to enable CPU0 hotplug feature by default. | |
1932 | You still can enable the CPU0 hotplug feature at boot by kernel | |
1933 | parameter cpu0_hotplug. | |
1934 | ||
a71c8bc5 FY |
1935 | config DEBUG_HOTPLUG_CPU0 |
1936 | def_bool n | |
1937 | prompt "Debug CPU0 hotplug" | |
2c922cd0 | 1938 | depends on HOTPLUG_CPU |
a71c8bc5 FY |
1939 | ---help--- |
1940 | Enabling this option offlines CPU0 (if CPU0 can be offlined) as | |
1941 | soon as possible and boots up userspace with CPU0 offlined. User | |
1942 | can online CPU0 back after boot time. | |
1943 | ||
1944 | To debug CPU0 hotplug, you need to enable CPU0 offline/online | |
1945 | feature by either turning on CONFIG_BOOTPARAM_HOTPLUG_CPU0 during | |
1946 | compilation or giving cpu0_hotplug kernel parameter at boot. | |
1947 | ||
1948 | If unsure, say N. | |
1949 | ||
506f1d07 | 1950 | config COMPAT_VDSO |
b0b49f26 AL |
1951 | def_bool n |
1952 | prompt "Disable the 32-bit vDSO (needed for glibc 2.3.3)" | |
af65d648 | 1953 | depends on X86_32 || IA32_EMULATION |
8f9ca475 | 1954 | ---help--- |
b0b49f26 AL |
1955 | Certain buggy versions of glibc will crash if they are |
1956 | presented with a 32-bit vDSO that is not mapped at the address | |
1957 | indicated in its segment table. | |
e84446de | 1958 | |
b0b49f26 AL |
1959 | The bug was introduced by f866314b89d56845f55e6f365e18b31ec978ec3a |
1960 | and fixed by 3b3ddb4f7db98ec9e912ccdf54d35df4aa30e04a and | |
1961 | 49ad572a70b8aeb91e57483a11dd1b77e31c4468. Glibc 2.3.3 is | |
1962 | the only released version with the bug, but OpenSUSE 9 | |
1963 | contains a buggy "glibc 2.3.2". | |
506f1d07 | 1964 | |
b0b49f26 AL |
1965 | The symptom of the bug is that everything crashes on startup, saying: |
1966 | dl_main: Assertion `(void *) ph->p_vaddr == _rtld_local._dl_sysinfo_dso' failed! | |
1967 | ||
1968 | Saying Y here changes the default value of the vdso32 boot | |
1969 | option from 1 to 0, which turns off the 32-bit vDSO entirely. | |
1970 | This works around the glibc bug but hurts performance. | |
1971 | ||
1972 | If unsure, say N: if you are compiling your own kernel, you | |
1973 | are unlikely to be using a buggy version of glibc. | |
506f1d07 | 1974 | |
516cbf37 TB |
1975 | config CMDLINE_BOOL |
1976 | bool "Built-in kernel command line" | |
8f9ca475 | 1977 | ---help--- |
516cbf37 TB |
1978 | Allow for specifying boot arguments to the kernel at |
1979 | build time. On some systems (e.g. embedded ones), it is | |
1980 | necessary or convenient to provide some or all of the | |
1981 | kernel boot arguments with the kernel itself (that is, | |
1982 | to not rely on the boot loader to provide them.) | |
1983 | ||
1984 | To compile command line arguments into the kernel, | |
1985 | set this option to 'Y', then fill in the | |
1986 | the boot arguments in CONFIG_CMDLINE. | |
1987 | ||
1988 | Systems with fully functional boot loaders (i.e. non-embedded) | |
1989 | should leave this option set to 'N'. | |
1990 | ||
1991 | config CMDLINE | |
1992 | string "Built-in kernel command string" | |
1993 | depends on CMDLINE_BOOL | |
1994 | default "" | |
8f9ca475 | 1995 | ---help--- |
516cbf37 TB |
1996 | Enter arguments here that should be compiled into the kernel |
1997 | image and used at boot time. If the boot loader provides a | |
1998 | command line at boot time, it is appended to this string to | |
1999 | form the full kernel command line, when the system boots. | |
2000 | ||
2001 | However, you can use the CONFIG_CMDLINE_OVERRIDE option to | |
2002 | change this behavior. | |
2003 | ||
2004 | In most cases, the command line (whether built-in or provided | |
2005 | by the boot loader) should specify the device for the root | |
2006 | file system. | |
2007 | ||
2008 | config CMDLINE_OVERRIDE | |
2009 | bool "Built-in command line overrides boot loader arguments" | |
516cbf37 | 2010 | depends on CMDLINE_BOOL |
8f9ca475 | 2011 | ---help--- |
516cbf37 TB |
2012 | Set this option to 'Y' to have the kernel ignore the boot loader |
2013 | command line, and use ONLY the built-in command line. | |
2014 | ||
2015 | This is used to work around broken boot loaders. This should | |
2016 | be set to 'N' under normal conditions. | |
2017 | ||
506f1d07 SR |
2018 | endmenu |
2019 | ||
2020 | config ARCH_ENABLE_MEMORY_HOTPLUG | |
2021 | def_bool y | |
2022 | depends on X86_64 || (X86_32 && HIGHMEM) | |
2023 | ||
35551053 GH |
2024 | config ARCH_ENABLE_MEMORY_HOTREMOVE |
2025 | def_bool y | |
2026 | depends on MEMORY_HOTPLUG | |
2027 | ||
e534c7c5 | 2028 | config USE_PERCPU_NUMA_NODE_ID |
645a7919 | 2029 | def_bool y |
e534c7c5 LS |
2030 | depends on NUMA |
2031 | ||
9491846f KS |
2032 | config ARCH_ENABLE_SPLIT_PMD_PTLOCK |
2033 | def_bool y | |
2034 | depends on X86_64 || X86_PAE | |
2035 | ||
c177c81e NH |
2036 | config ARCH_ENABLE_HUGEPAGE_MIGRATION |
2037 | def_bool y | |
2038 | depends on X86_64 && HUGETLB_PAGE && MIGRATION | |
2039 | ||
da85f865 | 2040 | menu "Power management and ACPI options" |
e279b6c1 SR |
2041 | |
2042 | config ARCH_HIBERNATION_HEADER | |
3c2362e6 | 2043 | def_bool y |
e279b6c1 | 2044 | depends on X86_64 && HIBERNATION |
e279b6c1 SR |
2045 | |
2046 | source "kernel/power/Kconfig" | |
2047 | ||
2048 | source "drivers/acpi/Kconfig" | |
2049 | ||
efafc8b2 FT |
2050 | source "drivers/sfi/Kconfig" |
2051 | ||
a6b68076 | 2052 | config X86_APM_BOOT |
6fc108a0 | 2053 | def_bool y |
282e5aab | 2054 | depends on APM |
a6b68076 | 2055 | |
e279b6c1 SR |
2056 | menuconfig APM |
2057 | tristate "APM (Advanced Power Management) BIOS support" | |
efefa6f6 | 2058 | depends on X86_32 && PM_SLEEP |
e279b6c1 SR |
2059 | ---help--- |
2060 | APM is a BIOS specification for saving power using several different | |
2061 | techniques. This is mostly useful for battery powered laptops with | |
2062 | APM compliant BIOSes. If you say Y here, the system time will be | |
2063 | reset after a RESUME operation, the /proc/apm device will provide | |
2064 | battery status information, and user-space programs will receive | |
2065 | notification of APM "events" (e.g. battery status change). | |
2066 | ||
2067 | If you select "Y" here, you can disable actual use of the APM | |
2068 | BIOS by passing the "apm=off" option to the kernel at boot time. | |
2069 | ||
2070 | Note that the APM support is almost completely disabled for | |
2071 | machines with more than one CPU. | |
2072 | ||
2073 | In order to use APM, you will need supporting software. For location | |
2dc98fd3 MW |
2074 | and more information, read <file:Documentation/power/apm-acpi.txt> |
2075 | and the Battery Powered Linux mini-HOWTO, available from | |
e279b6c1 SR |
2076 | <http://www.tldp.org/docs.html#howto>. |
2077 | ||
2078 | This driver does not spin down disk drives (see the hdparm(8) | |
2079 | manpage ("man 8 hdparm") for that), and it doesn't turn off | |
2080 | VESA-compliant "green" monitors. | |
2081 | ||
2082 | This driver does not support the TI 4000M TravelMate and the ACER | |
2083 | 486/DX4/75 because they don't have compliant BIOSes. Many "green" | |
2084 | desktop machines also don't have compliant BIOSes, and this driver | |
2085 | may cause those machines to panic during the boot phase. | |
2086 | ||
2087 | Generally, if you don't have a battery in your machine, there isn't | |
2088 | much point in using this driver and you should say N. If you get | |
2089 | random kernel OOPSes or reboots that don't seem to be related to | |
2090 | anything, try disabling/enabling this option (or disabling/enabling | |
2091 | APM in your BIOS). | |
2092 | ||
2093 | Some other things you should try when experiencing seemingly random, | |
2094 | "weird" problems: | |
2095 | ||
2096 | 1) make sure that you have enough swap space and that it is | |
2097 | enabled. | |
2098 | 2) pass the "no-hlt" option to the kernel | |
2099 | 3) switch on floating point emulation in the kernel and pass | |
2100 | the "no387" option to the kernel | |
2101 | 4) pass the "floppy=nodma" option to the kernel | |
2102 | 5) pass the "mem=4M" option to the kernel (thereby disabling | |
2103 | all but the first 4 MB of RAM) | |
2104 | 6) make sure that the CPU is not over clocked. | |
2105 | 7) read the sig11 FAQ at <http://www.bitwizard.nl/sig11/> | |
2106 | 8) disable the cache from your BIOS settings | |
2107 | 9) install a fan for the video card or exchange video RAM | |
2108 | 10) install a better fan for the CPU | |
2109 | 11) exchange RAM chips | |
2110 | 12) exchange the motherboard. | |
2111 | ||
2112 | To compile this driver as a module, choose M here: the | |
2113 | module will be called apm. | |
2114 | ||
2115 | if APM | |
2116 | ||
2117 | config APM_IGNORE_USER_SUSPEND | |
2118 | bool "Ignore USER SUSPEND" | |
8f9ca475 | 2119 | ---help--- |
e279b6c1 SR |
2120 | This option will ignore USER SUSPEND requests. On machines with a |
2121 | compliant APM BIOS, you want to say N. However, on the NEC Versa M | |
2122 | series notebooks, it is necessary to say Y because of a BIOS bug. | |
2123 | ||
2124 | config APM_DO_ENABLE | |
2125 | bool "Enable PM at boot time" | |
2126 | ---help--- | |
2127 | Enable APM features at boot time. From page 36 of the APM BIOS | |
2128 | specification: "When disabled, the APM BIOS does not automatically | |
2129 | power manage devices, enter the Standby State, enter the Suspend | |
2130 | State, or take power saving steps in response to CPU Idle calls." | |
2131 | This driver will make CPU Idle calls when Linux is idle (unless this | |
2132 | feature is turned off -- see "Do CPU IDLE calls", below). This | |
2133 | should always save battery power, but more complicated APM features | |
2134 | will be dependent on your BIOS implementation. You may need to turn | |
2135 | this option off if your computer hangs at boot time when using APM | |
2136 | support, or if it beeps continuously instead of suspending. Turn | |
2137 | this off if you have a NEC UltraLite Versa 33/C or a Toshiba | |
2138 | T400CDT. This is off by default since most machines do fine without | |
2139 | this feature. | |
2140 | ||
2141 | config APM_CPU_IDLE | |
dd8af076 | 2142 | depends on CPU_IDLE |
e279b6c1 | 2143 | bool "Make CPU Idle calls when idle" |
8f9ca475 | 2144 | ---help--- |
e279b6c1 SR |
2145 | Enable calls to APM CPU Idle/CPU Busy inside the kernel's idle loop. |
2146 | On some machines, this can activate improved power savings, such as | |
2147 | a slowed CPU clock rate, when the machine is idle. These idle calls | |
2148 | are made after the idle loop has run for some length of time (e.g., | |
2149 | 333 mS). On some machines, this will cause a hang at boot time or | |
2150 | whenever the CPU becomes idle. (On machines with more than one CPU, | |
2151 | this option does nothing.) | |
2152 | ||
2153 | config APM_DISPLAY_BLANK | |
2154 | bool "Enable console blanking using APM" | |
8f9ca475 | 2155 | ---help--- |
e279b6c1 SR |
2156 | Enable console blanking using the APM. Some laptops can use this to |
2157 | turn off the LCD backlight when the screen blanker of the Linux | |
2158 | virtual console blanks the screen. Note that this is only used by | |
2159 | the virtual console screen blanker, and won't turn off the backlight | |
2160 | when using the X Window system. This also doesn't have anything to | |
2161 | do with your VESA-compliant power-saving monitor. Further, this | |
2162 | option doesn't work for all laptops -- it might not turn off your | |
2163 | backlight at all, or it might print a lot of errors to the console, | |
2164 | especially if you are using gpm. | |
2165 | ||
2166 | config APM_ALLOW_INTS | |
2167 | bool "Allow interrupts during APM BIOS calls" | |
8f9ca475 | 2168 | ---help--- |
e279b6c1 SR |
2169 | Normally we disable external interrupts while we are making calls to |
2170 | the APM BIOS as a measure to lessen the effects of a badly behaving | |
2171 | BIOS implementation. The BIOS should reenable interrupts if it | |
2172 | needs to. Unfortunately, some BIOSes do not -- especially those in | |
2173 | many of the newer IBM Thinkpads. If you experience hangs when you | |
2174 | suspend, try setting this to Y. Otherwise, say N. | |
2175 | ||
e279b6c1 SR |
2176 | endif # APM |
2177 | ||
bb0a56ec | 2178 | source "drivers/cpufreq/Kconfig" |
e279b6c1 SR |
2179 | |
2180 | source "drivers/cpuidle/Kconfig" | |
2181 | ||
27471fdb AH |
2182 | source "drivers/idle/Kconfig" |
2183 | ||
e279b6c1 SR |
2184 | endmenu |
2185 | ||
2186 | ||
2187 | menu "Bus options (PCI etc.)" | |
2188 | ||
2189 | config PCI | |
1ac97018 | 2190 | bool "PCI support" |
1c858087 | 2191 | default y |
8f9ca475 | 2192 | ---help--- |
e279b6c1 SR |
2193 | Find out whether you have a PCI motherboard. PCI is the name of a |
2194 | bus system, i.e. the way the CPU talks to the other stuff inside | |
2195 | your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or | |
2196 | VESA. If you have PCI, say Y, otherwise N. | |
2197 | ||
e279b6c1 SR |
2198 | choice |
2199 | prompt "PCI access mode" | |
efefa6f6 | 2200 | depends on X86_32 && PCI |
e279b6c1 SR |
2201 | default PCI_GOANY |
2202 | ---help--- | |
2203 | On PCI systems, the BIOS can be used to detect the PCI devices and | |
2204 | determine their configuration. However, some old PCI motherboards | |
2205 | have BIOS bugs and may crash if this is done. Also, some embedded | |
2206 | PCI-based systems don't have any BIOS at all. Linux can also try to | |
2207 | detect the PCI hardware directly without using the BIOS. | |
2208 | ||
2209 | With this option, you can specify how Linux should detect the | |
2210 | PCI devices. If you choose "BIOS", the BIOS will be used, | |
2211 | if you choose "Direct", the BIOS won't be used, and if you | |
2212 | choose "MMConfig", then PCI Express MMCONFIG will be used. | |
2213 | If you choose "Any", the kernel will try MMCONFIG, then the | |
2214 | direct access method and falls back to the BIOS if that doesn't | |
2215 | work. If unsure, go with the default, which is "Any". | |
2216 | ||
2217 | config PCI_GOBIOS | |
2218 | bool "BIOS" | |
2219 | ||
2220 | config PCI_GOMMCONFIG | |
2221 | bool "MMConfig" | |
2222 | ||
2223 | config PCI_GODIRECT | |
2224 | bool "Direct" | |
2225 | ||
3ef0e1f8 | 2226 | config PCI_GOOLPC |
76fb6570 | 2227 | bool "OLPC XO-1" |
3ef0e1f8 AS |
2228 | depends on OLPC |
2229 | ||
2bdd1b03 AS |
2230 | config PCI_GOANY |
2231 | bool "Any" | |
2232 | ||
e279b6c1 SR |
2233 | endchoice |
2234 | ||
2235 | config PCI_BIOS | |
3c2362e6 | 2236 | def_bool y |
efefa6f6 | 2237 | depends on X86_32 && PCI && (PCI_GOBIOS || PCI_GOANY) |
e279b6c1 SR |
2238 | |
2239 | # x86-64 doesn't support PCI BIOS access from long mode so always go direct. | |
2240 | config PCI_DIRECT | |
3c2362e6 | 2241 | def_bool y |
0aba496f | 2242 | depends on PCI && (X86_64 || (PCI_GODIRECT || PCI_GOANY || PCI_GOOLPC || PCI_GOMMCONFIG)) |
e279b6c1 SR |
2243 | |
2244 | config PCI_MMCONFIG | |
3c2362e6 | 2245 | def_bool y |
5f0db7a2 | 2246 | depends on X86_32 && PCI && (ACPI || SFI) && (PCI_GOMMCONFIG || PCI_GOANY) |
e279b6c1 | 2247 | |
3ef0e1f8 | 2248 | config PCI_OLPC |
2bdd1b03 AS |
2249 | def_bool y |
2250 | depends on PCI && OLPC && (PCI_GOOLPC || PCI_GOANY) | |
3ef0e1f8 | 2251 | |
b5401a96 AN |
2252 | config PCI_XEN |
2253 | def_bool y | |
2254 | depends on PCI && XEN | |
2255 | select SWIOTLB_XEN | |
2256 | ||
e279b6c1 | 2257 | config PCI_DOMAINS |
3c2362e6 | 2258 | def_bool y |
e279b6c1 | 2259 | depends on PCI |
e279b6c1 SR |
2260 | |
2261 | config PCI_MMCONFIG | |
2262 | bool "Support mmconfig PCI config space access" | |
2263 | depends on X86_64 && PCI && ACPI | |
2264 | ||
3f6ea84a | 2265 | config PCI_CNB20LE_QUIRK |
6a108a14 | 2266 | bool "Read CNB20LE Host Bridge Windows" if EXPERT |
6ea30386 | 2267 | depends on PCI |
3f6ea84a IS |
2268 | help |
2269 | Read the PCI windows out of the CNB20LE host bridge. This allows | |
2270 | PCI hotplug to work on systems with the CNB20LE chipset which do | |
2271 | not have ACPI. | |
2272 | ||
64a5fed6 BH |
2273 | There's no public spec for this chipset, and this functionality |
2274 | is known to be incomplete. | |
2275 | ||
2276 | You should say N unless you know you need this. | |
2277 | ||
e279b6c1 SR |
2278 | source "drivers/pci/pcie/Kconfig" |
2279 | ||
2280 | source "drivers/pci/Kconfig" | |
2281 | ||
1c00f016 | 2282 | # x86_64 have no ISA slots, but can have ISA-style DMA. |
e279b6c1 | 2283 | config ISA_DMA_API |
1c00f016 DR |
2284 | bool "ISA-style DMA support" if (X86_64 && EXPERT) |
2285 | default y | |
2286 | help | |
2287 | Enables ISA-style DMA support for devices requiring such controllers. | |
2288 | If unsure, say Y. | |
e279b6c1 SR |
2289 | |
2290 | if X86_32 | |
2291 | ||
2292 | config ISA | |
2293 | bool "ISA support" | |
8f9ca475 | 2294 | ---help--- |
e279b6c1 SR |
2295 | Find out whether you have ISA slots on your motherboard. ISA is the |
2296 | name of a bus system, i.e. the way the CPU talks to the other stuff | |
2297 | inside your box. Other bus systems are PCI, EISA, MicroChannel | |
2298 | (MCA) or VESA. ISA is an older system, now being displaced by PCI; | |
2299 | newer boards don't support it. If you have ISA, say Y, otherwise N. | |
2300 | ||
2301 | config EISA | |
2302 | bool "EISA support" | |
2303 | depends on ISA | |
2304 | ---help--- | |
2305 | The Extended Industry Standard Architecture (EISA) bus was | |
2306 | developed as an open alternative to the IBM MicroChannel bus. | |
2307 | ||
2308 | The EISA bus provided some of the features of the IBM MicroChannel | |
2309 | bus while maintaining backward compatibility with cards made for | |
2310 | the older ISA bus. The EISA bus saw limited use between 1988 and | |
2311 | 1995 when it was made obsolete by the PCI bus. | |
2312 | ||
2313 | Say Y here if you are building a kernel for an EISA-based machine. | |
2314 | ||
2315 | Otherwise, say N. | |
2316 | ||
2317 | source "drivers/eisa/Kconfig" | |
2318 | ||
e279b6c1 SR |
2319 | config SCx200 |
2320 | tristate "NatSemi SCx200 support" | |
8f9ca475 | 2321 | ---help--- |
e279b6c1 SR |
2322 | This provides basic support for National Semiconductor's |
2323 | (now AMD's) Geode processors. The driver probes for the | |
2324 | PCI-IDs of several on-chip devices, so its a good dependency | |
2325 | for other scx200_* drivers. | |
2326 | ||
2327 | If compiled as a module, the driver is named scx200. | |
2328 | ||
2329 | config SCx200HR_TIMER | |
2330 | tristate "NatSemi SCx200 27MHz High-Resolution Timer Support" | |
592913ec | 2331 | depends on SCx200 |
e279b6c1 | 2332 | default y |
8f9ca475 | 2333 | ---help--- |
e279b6c1 SR |
2334 | This driver provides a clocksource built upon the on-chip |
2335 | 27MHz high-resolution timer. Its also a workaround for | |
2336 | NSC Geode SC-1100's buggy TSC, which loses time when the | |
2337 | processor goes idle (as is done by the scheduler). The | |
2338 | other workaround is idle=poll boot option. | |
2339 | ||
3ef0e1f8 AS |
2340 | config OLPC |
2341 | bool "One Laptop Per Child support" | |
54008979 | 2342 | depends on !X86_PAE |
3c554946 | 2343 | select GPIOLIB |
dc3119e7 | 2344 | select OF |
45bb1674 | 2345 | select OF_PROMTREE |
b4e51854 | 2346 | select IRQ_DOMAIN |
8f9ca475 | 2347 | ---help--- |
3ef0e1f8 AS |
2348 | Add support for detecting the unique features of the OLPC |
2349 | XO hardware. | |
2350 | ||
a3128588 DD |
2351 | config OLPC_XO1_PM |
2352 | bool "OLPC XO-1 Power Management" | |
97c4cb71 | 2353 | depends on OLPC && MFD_CS5535 && PM_SLEEP |
a3128588 | 2354 | select MFD_CORE |
bf1ebf00 | 2355 | ---help--- |
97c4cb71 | 2356 | Add support for poweroff and suspend of the OLPC XO-1 laptop. |
bf1ebf00 | 2357 | |
cfee9597 DD |
2358 | config OLPC_XO1_RTC |
2359 | bool "OLPC XO-1 Real Time Clock" | |
2360 | depends on OLPC_XO1_PM && RTC_DRV_CMOS | |
2361 | ---help--- | |
2362 | Add support for the XO-1 real time clock, which can be used as a | |
2363 | programmable wakeup source. | |
2364 | ||
7feda8e9 DD |
2365 | config OLPC_XO1_SCI |
2366 | bool "OLPC XO-1 SCI extras" | |
d8d01a63 | 2367 | depends on OLPC && OLPC_XO1_PM |
ed8e47fe | 2368 | depends on INPUT=y |
d8d01a63 | 2369 | select POWER_SUPPLY |
7feda8e9 DD |
2370 | select GPIO_CS5535 |
2371 | select MFD_CORE | |
2372 | ---help--- | |
2373 | Add support for SCI-based features of the OLPC XO-1 laptop: | |
7bc74b3d | 2374 | - EC-driven system wakeups |
7feda8e9 | 2375 | - Power button |
7bc74b3d | 2376 | - Ebook switch |
2cf2baea | 2377 | - Lid switch |
e1040ac6 DD |
2378 | - AC adapter status updates |
2379 | - Battery status updates | |
7feda8e9 | 2380 | |
a0f30f59 DD |
2381 | config OLPC_XO15_SCI |
2382 | bool "OLPC XO-1.5 SCI extras" | |
d8d01a63 DD |
2383 | depends on OLPC && ACPI |
2384 | select POWER_SUPPLY | |
a0f30f59 DD |
2385 | ---help--- |
2386 | Add support for SCI-based features of the OLPC XO-1.5 laptop: | |
2387 | - EC-driven system wakeups | |
2388 | - AC adapter status updates | |
2389 | - Battery status updates | |
bf1ebf00 | 2390 | |
d4f3e350 EW |
2391 | config ALIX |
2392 | bool "PCEngines ALIX System Support (LED setup)" | |
2393 | select GPIOLIB | |
2394 | ---help--- | |
2395 | This option enables system support for the PCEngines ALIX. | |
2396 | At present this just sets up LEDs for GPIO control on | |
2397 | ALIX2/3/6 boards. However, other system specific setup should | |
2398 | get added here. | |
2399 | ||
2400 | Note: You must still enable the drivers for GPIO and LED support | |
2401 | (GPIO_CS5535 & LEDS_GPIO) to actually use the LEDs | |
2402 | ||
2403 | Note: You have to set alix.force=1 for boards with Award BIOS. | |
2404 | ||
da4e3302 PP |
2405 | config NET5501 |
2406 | bool "Soekris Engineering net5501 System Support (LEDS, GPIO, etc)" | |
2407 | select GPIOLIB | |
2408 | ---help--- | |
2409 | This option enables system support for the Soekris Engineering net5501. | |
2410 | ||
3197059a PP |
2411 | config GEOS |
2412 | bool "Traverse Technologies GEOS System Support (LEDS, GPIO, etc)" | |
2413 | select GPIOLIB | |
2414 | depends on DMI | |
2415 | ---help--- | |
2416 | This option enables system support for the Traverse Technologies GEOS. | |
2417 | ||
7d029125 VD |
2418 | config TS5500 |
2419 | bool "Technologic Systems TS-5500 platform support" | |
2420 | depends on MELAN | |
2421 | select CHECK_SIGNATURE | |
2422 | select NEW_LEDS | |
2423 | select LEDS_CLASS | |
2424 | ---help--- | |
2425 | This option enables system support for the Technologic Systems TS-5500. | |
2426 | ||
bc0120fd SR |
2427 | endif # X86_32 |
2428 | ||
23ac4ae8 | 2429 | config AMD_NB |
e279b6c1 | 2430 | def_bool y |
0e152cd7 | 2431 | depends on CPU_SUP_AMD && PCI |
e279b6c1 SR |
2432 | |
2433 | source "drivers/pcmcia/Kconfig" | |
2434 | ||
2435 | source "drivers/pci/hotplug/Kconfig" | |
2436 | ||
388b78ad | 2437 | config RAPIDIO |
fdf90abc | 2438 | tristate "RapidIO support" |
388b78ad AB |
2439 | depends on PCI |
2440 | default n | |
2441 | help | |
fdf90abc | 2442 | If enabled this option will include drivers and the core |
388b78ad AB |
2443 | infrastructure code to support RapidIO interconnect devices. |
2444 | ||
2445 | source "drivers/rapidio/Kconfig" | |
2446 | ||
e3263ab3 DH |
2447 | config X86_SYSFB |
2448 | bool "Mark VGA/VBE/EFI FB as generic system framebuffer" | |
2449 | help | |
2450 | Firmwares often provide initial graphics framebuffers so the BIOS, | |
2451 | bootloader or kernel can show basic video-output during boot for | |
2452 | user-guidance and debugging. Historically, x86 used the VESA BIOS | |
2453 | Extensions and EFI-framebuffers for this, which are mostly limited | |
2454 | to x86. | |
2455 | This option, if enabled, marks VGA/VBE/EFI framebuffers as generic | |
2456 | framebuffers so the new generic system-framebuffer drivers can be | |
2457 | used on x86. If the framebuffer is not compatible with the generic | |
2458 | modes, it is adverticed as fallback platform framebuffer so legacy | |
2459 | drivers like efifb, vesafb and uvesafb can pick it up. | |
2460 | If this option is not selected, all system framebuffers are always | |
2461 | marked as fallback platform framebuffers as usual. | |
2462 | ||
2463 | Note: Legacy fbdev drivers, including vesafb, efifb, uvesafb, will | |
2464 | not be able to pick up generic system framebuffers if this option | |
2465 | is selected. You are highly encouraged to enable simplefb as | |
2466 | replacement if you select this option. simplefb can correctly deal | |
2467 | with generic system framebuffers. But you should still keep vesafb | |
2468 | and others enabled as fallback if a system framebuffer is | |
2469 | incompatible with simplefb. | |
2470 | ||
2471 | If unsure, say Y. | |
2472 | ||
e279b6c1 SR |
2473 | endmenu |
2474 | ||
2475 | ||
2476 | menu "Executable file formats / Emulations" | |
2477 | ||
2478 | source "fs/Kconfig.binfmt" | |
2479 | ||
2480 | config IA32_EMULATION | |
2481 | bool "IA32 Emulation" | |
2482 | depends on X86_64 | |
d1603990 | 2483 | select BINFMT_ELF |
a97f52e6 | 2484 | select COMPAT_BINFMT_ELF |
af1839eb | 2485 | select HAVE_UID16 |
8f9ca475 | 2486 | ---help--- |
5fd92e65 L |
2487 | Include code to run legacy 32-bit programs under a |
2488 | 64-bit kernel. You should likely turn this on, unless you're | |
2489 | 100% sure that you don't have any 32-bit programs left. | |
e279b6c1 SR |
2490 | |
2491 | config IA32_AOUT | |
8f9ca475 IM |
2492 | tristate "IA32 a.out support" |
2493 | depends on IA32_EMULATION | |
2494 | ---help--- | |
2495 | Support old a.out binaries in the 32bit emulation. | |
e279b6c1 | 2496 | |
0bf62763 | 2497 | config X86_X32 |
6ea30386 KC |
2498 | bool "x32 ABI for 64-bit mode" |
2499 | depends on X86_64 && IA32_EMULATION | |
5fd92e65 L |
2500 | ---help--- |
2501 | Include code to run binaries for the x32 native 32-bit ABI | |
2502 | for 64-bit processors. An x32 process gets access to the | |
2503 | full 64-bit register file and wide data path while leaving | |
2504 | pointers at 32 bits for smaller memory footprint. | |
2505 | ||
2506 | You will need a recent binutils (2.22 or later) with | |
2507 | elf32_x86_64 support enabled to compile a kernel with this | |
2508 | option set. | |
2509 | ||
e279b6c1 | 2510 | config COMPAT |
3c2362e6 | 2511 | def_bool y |
0bf62763 | 2512 | depends on IA32_EMULATION || X86_X32 |
48b25c43 | 2513 | select ARCH_WANT_OLD_COMPAT_IPC |
e279b6c1 | 2514 | |
3120e25e | 2515 | if COMPAT |
e279b6c1 | 2516 | config COMPAT_FOR_U64_ALIGNMENT |
3120e25e | 2517 | def_bool y |
e279b6c1 SR |
2518 | |
2519 | config SYSVIPC_COMPAT | |
3c2362e6 | 2520 | def_bool y |
3120e25e | 2521 | depends on SYSVIPC |
e279b6c1 | 2522 | |
ee009e4a | 2523 | config KEYS_COMPAT |
3120e25e JB |
2524 | def_bool y |
2525 | depends on KEYS | |
2526 | endif | |
ee009e4a | 2527 | |
e279b6c1 SR |
2528 | endmenu |
2529 | ||
2530 | ||
e5beae16 KP |
2531 | config HAVE_ATOMIC_IOMAP |
2532 | def_bool y | |
2533 | depends on X86_32 | |
2534 | ||
4692d77f AR |
2535 | config X86_DEV_DMA_OPS |
2536 | bool | |
83125a3a | 2537 | depends on X86_64 || STA2X11 |
4692d77f | 2538 | |
f7219a53 AR |
2539 | config X86_DMA_REMAP |
2540 | bool | |
83125a3a | 2541 | depends on STA2X11 |
f7219a53 | 2542 | |
93e5eadd LA |
2543 | config PMC_ATOM |
2544 | def_bool y | |
2545 | depends on PCI | |
2546 | ||
e279b6c1 SR |
2547 | source "net/Kconfig" |
2548 | ||
2549 | source "drivers/Kconfig" | |
2550 | ||
2551 | source "drivers/firmware/Kconfig" | |
2552 | ||
2553 | source "fs/Kconfig" | |
2554 | ||
e279b6c1 SR |
2555 | source "arch/x86/Kconfig.debug" |
2556 | ||
2557 | source "security/Kconfig" | |
2558 | ||
2559 | source "crypto/Kconfig" | |
2560 | ||
edf88417 AK |
2561 | source "arch/x86/kvm/Kconfig" |
2562 | ||
e279b6c1 | 2563 | source "lib/Kconfig" |