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