1 # SPDX-License-Identifier: GPL-2.0-only !! 1 #
2 config ARM64 !! 2 # For a description of the syntax of this configuration file,
3 def_bool y !! 3 # see Documentation/kbuild/kconfig-language.txt.
4 select ACPI_APMT if ACPI !! 4 #
5 select ACPI_CCA_REQUIRED if ACPI !! 5 config M68K
6 select ACPI_GENERIC_GSI if ACPI <<
7 select ACPI_GTDT if ACPI <<
8 select ACPI_HOTPLUG_CPU if ACPI_PROCES <<
9 select ACPI_IORT if ACPI <<
10 select ACPI_REDUCED_HARDWARE_ONLY if A <<
11 select ACPI_MCFG if (ACPI && PCI) <<
12 select ACPI_SPCR_TABLE if ACPI <<
13 select ACPI_PPTT if ACPI <<
14 select ARCH_HAS_DEBUG_WX <<
15 select ARCH_BINFMT_ELF_EXTRA_PHDRS <<
16 select ARCH_BINFMT_ELF_STATE <<
17 select ARCH_CORRECT_STACKTRACE_ON_KRET <<
18 select ARCH_ENABLE_HUGEPAGE_MIGRATION <<
19 select ARCH_ENABLE_MEMORY_HOTPLUG <<
20 select ARCH_ENABLE_MEMORY_HOTREMOVE <<
21 select ARCH_ENABLE_SPLIT_PMD_PTLOCK if <<
22 select ARCH_ENABLE_THP_MIGRATION if TR <<
23 select ARCH_HAS_CACHE_LINE_SIZE <<
24 select ARCH_HAS_CURRENT_STACK_POINTER <<
25 select ARCH_HAS_DEBUG_VIRTUAL <<
26 select ARCH_HAS_DEBUG_VM_PGTABLE <<
27 select ARCH_HAS_DMA_OPS if XEN <<
28 select ARCH_HAS_DMA_PREP_COHERENT <<
29 select ARCH_HAS_ACPI_TABLE_UPGRADE if <<
30 select ARCH_HAS_FAST_MULTIPLIER <<
31 select ARCH_HAS_FORTIFY_SOURCE <<
32 select ARCH_HAS_GCOV_PROFILE_ALL <<
33 select ARCH_HAS_GIGANTIC_PAGE <<
34 select ARCH_HAS_KCOV <<
35 select ARCH_HAS_KERNEL_FPU_SUPPORT if <<
36 select ARCH_HAS_KEEPINITRD <<
37 select ARCH_HAS_MEMBARRIER_SYNC_CORE <<
38 select ARCH_HAS_MEM_ENCRYPT <<
39 select ARCH_HAS_NMI_SAFE_THIS_CPU_OPS <<
40 select ARCH_HAS_NON_OVERLAPPING_ADDRES <<
41 select ARCH_HAS_PTE_DEVMAP <<
42 select ARCH_HAS_PTE_SPECIAL <<
43 select ARCH_HAS_HW_PTE_YOUNG <<
44 select ARCH_HAS_SETUP_DMA_OPS <<
45 select ARCH_HAS_SET_DIRECT_MAP <<
46 select ARCH_HAS_SET_MEMORY <<
47 select ARCH_STACKWALK <<
48 select ARCH_HAS_STRICT_KERNEL_RWX <<
49 select ARCH_HAS_STRICT_MODULE_RWX <<
50 select ARCH_HAS_SYNC_DMA_FOR_DEVICE <<
51 select ARCH_HAS_SYNC_DMA_FOR_CPU <<
52 select ARCH_HAS_SYSCALL_WRAPPER <<
53 select ARCH_HAS_TICK_BROADCAST if GENE <<
54 select ARCH_HAS_ZONE_DMA_SET if EXPERT <<
55 select ARCH_HAVE_ELF_PROT <<
56 select ARCH_HAVE_NMI_SAFE_CMPXCHG <<
57 select ARCH_HAVE_TRACE_MMIO_ACCESS <<
58 select ARCH_INLINE_READ_LOCK if !PREEM <<
59 select ARCH_INLINE_READ_LOCK_BH if !PR <<
60 select ARCH_INLINE_READ_LOCK_IRQ if !P <<
61 select ARCH_INLINE_READ_LOCK_IRQSAVE i <<
62 select ARCH_INLINE_READ_UNLOCK if !PRE <<
63 select ARCH_INLINE_READ_UNLOCK_BH if ! <<
64 select ARCH_INLINE_READ_UNLOCK_IRQ if <<
65 select ARCH_INLINE_READ_UNLOCK_IRQREST <<
66 select ARCH_INLINE_WRITE_LOCK if !PREE <<
67 select ARCH_INLINE_WRITE_LOCK_BH if !P <<
68 select ARCH_INLINE_WRITE_LOCK_IRQ if ! <<
69 select ARCH_INLINE_WRITE_LOCK_IRQSAVE <<
70 select ARCH_INLINE_WRITE_UNLOCK if !PR <<
71 select ARCH_INLINE_WRITE_UNLOCK_BH if <<
72 select ARCH_INLINE_WRITE_UNLOCK_IRQ if <<
73 select ARCH_INLINE_WRITE_UNLOCK_IRQRES <<
74 select ARCH_INLINE_SPIN_TRYLOCK if !PR <<
75 select ARCH_INLINE_SPIN_TRYLOCK_BH if <<
76 select ARCH_INLINE_SPIN_LOCK if !PREEM <<
77 select ARCH_INLINE_SPIN_LOCK_BH if !PR <<
78 select ARCH_INLINE_SPIN_LOCK_IRQ if !P <<
79 select ARCH_INLINE_SPIN_LOCK_IRQSAVE i <<
80 select ARCH_INLINE_SPIN_UNLOCK if !PRE <<
81 select ARCH_INLINE_SPIN_UNLOCK_BH if ! <<
82 select ARCH_INLINE_SPIN_UNLOCK_IRQ if <<
83 select ARCH_INLINE_SPIN_UNLOCK_IRQREST <<
84 select ARCH_KEEP_MEMBLOCK <<
85 select ARCH_MHP_MEMMAP_ON_MEMORY_ENABL <<
86 select ARCH_USE_CMPXCHG_LOCKREF <<
87 select ARCH_USE_GNU_PROPERTY <<
88 select ARCH_USE_MEMTEST <<
89 select ARCH_USE_QUEUED_RWLOCKS <<
90 select ARCH_USE_QUEUED_SPINLOCKS <<
91 select ARCH_USE_SYM_ANNOTATIONS <<
92 select ARCH_SUPPORTS_DEBUG_PAGEALLOC <<
93 select ARCH_SUPPORTS_HUGETLBFS <<
94 select ARCH_SUPPORTS_MEMORY_FAILURE <<
95 select ARCH_SUPPORTS_SHADOW_CALL_STACK <<
96 select ARCH_SUPPORTS_LTO_CLANG if CPU_ <<
97 select ARCH_SUPPORTS_LTO_CLANG_THIN <<
98 select ARCH_SUPPORTS_CFI_CLANG <<
99 select ARCH_SUPPORTS_ATOMIC_RMW <<
100 select ARCH_SUPPORTS_INT128 if CC_HAS_ <<
101 select ARCH_SUPPORTS_NUMA_BALANCING <<
102 select ARCH_SUPPORTS_PAGE_TABLE_CHECK <<
103 select ARCH_SUPPORTS_PER_VMA_LOCK <<
104 select ARCH_SUPPORTS_HUGE_PFNMAP if TR <<
105 select ARCH_SUPPORTS_RT <<
106 select ARCH_WANT_BATCHED_UNMAP_TLB_FLU <<
107 select ARCH_WANT_COMPAT_IPC_PARSE_VERS <<
108 select ARCH_WANT_DEFAULT_BPF_JIT <<
109 select ARCH_WANT_DEFAULT_TOPDOWN_MMAP_ <<
110 select ARCH_WANT_FRAME_POINTERS <<
111 select ARCH_WANT_HUGE_PMD_SHARE if ARM <<
112 select ARCH_WANT_LD_ORPHAN_WARN <<
113 select ARCH_WANTS_EXECMEM_LATE if EXEC <<
114 select ARCH_WANTS_NO_INSTR <<
115 select ARCH_WANTS_THP_SWAP if ARM64_4K <<
116 select ARCH_HAS_UBSAN <<
117 select ARM_AMBA <<
118 select ARM_ARCH_TIMER <<
119 select ARM_GIC <<
120 select AUDIT_ARCH_COMPAT_GENERIC <<
121 select ARM_GIC_V2M if PCI <<
122 select ARM_GIC_V3 <<
123 select ARM_GIC_V3_ITS if PCI <<
124 select ARM_PSCI_FW <<
125 select BUILDTIME_TABLE_SORT <<
126 select CLONE_BACKWARDS <<
127 select COMMON_CLK <<
128 select CPU_PM if (SUSPEND || CPU_IDLE) <<
129 select CPUMASK_OFFSTACK if NR_CPUS > 2 <<
130 select CRC32 <<
131 select DCACHE_WORD_ACCESS <<
132 select DYNAMIC_FTRACE if FUNCTION_TRAC <<
133 select DMA_BOUNCE_UNALIGNED_KMALLOC <<
134 select DMA_DIRECT_REMAP <<
135 select EDAC_SUPPORT <<
136 select FRAME_POINTER <<
137 select FUNCTION_ALIGNMENT_4B <<
138 select FUNCTION_ALIGNMENT_8B if DYNAMI <<
139 select GENERIC_ALLOCATOR <<
140 select GENERIC_ARCH_TOPOLOGY <<
141 select GENERIC_CLOCKEVENTS_BROADCAST <<
142 select GENERIC_CPU_AUTOPROBE <<
143 select GENERIC_CPU_DEVICES <<
144 select GENERIC_CPU_VULNERABILITIES <<
145 select GENERIC_EARLY_IOREMAP <<
146 select GENERIC_IDLE_POLL_SETUP <<
147 select GENERIC_IOREMAP <<
148 select GENERIC_IRQ_IPI <<
149 select GENERIC_IRQ_PROBE <<
150 select GENERIC_IRQ_SHOW <<
151 select GENERIC_IRQ_SHOW_LEVEL <<
152 select GENERIC_LIB_DEVMEM_IS_ALLOWED <<
153 select GENERIC_PCI_IOMAP <<
154 select GENERIC_PTDUMP <<
155 select GENERIC_SCHED_CLOCK <<
156 select GENERIC_SMP_IDLE_THREAD <<
157 select GENERIC_TIME_VSYSCALL <<
158 select GENERIC_GETTIMEOFDAY <<
159 select GENERIC_VDSO_TIME_NS <<
160 select HARDIRQS_SW_RESEND <<
161 select HAS_IOPORT <<
162 select HAVE_MOVE_PMD <<
163 select HAVE_MOVE_PUD <<
164 select HAVE_PCI <<
165 select HAVE_ACPI_APEI if (ACPI && EFI) <<
166 select HAVE_ALIGNED_STRUCT_PAGE <<
167 select HAVE_ARCH_AUDITSYSCALL <<
168 select HAVE_ARCH_BITREVERSE <<
169 select HAVE_ARCH_COMPILER_H <<
170 select HAVE_ARCH_HUGE_VMALLOC <<
171 select HAVE_ARCH_HUGE_VMAP <<
172 select HAVE_ARCH_JUMP_LABEL <<
173 select HAVE_ARCH_JUMP_LABEL_RELATIVE <<
174 select HAVE_ARCH_KASAN <<
175 select HAVE_ARCH_KASAN_VMALLOC <<
176 select HAVE_ARCH_KASAN_SW_TAGS <<
177 select HAVE_ARCH_KASAN_HW_TAGS if ARM6 <<
178 # Some instrumentation may be unsound, <<
179 select HAVE_ARCH_KCSAN if EXPERT <<
180 select HAVE_ARCH_KFENCE <<
181 select HAVE_ARCH_KGDB <<
182 select HAVE_ARCH_MMAP_RND_BITS <<
183 select HAVE_ARCH_MMAP_RND_COMPAT_BITS <<
184 select HAVE_ARCH_PREL32_RELOCATIONS <<
185 select HAVE_ARCH_RANDOMIZE_KSTACK_OFFS <<
186 select HAVE_ARCH_SECCOMP_FILTER <<
187 select HAVE_ARCH_STACKLEAK <<
188 select HAVE_ARCH_THREAD_STRUCT_WHITELI <<
189 select HAVE_ARCH_TRACEHOOK <<
190 select HAVE_ARCH_TRANSPARENT_HUGEPAGE <<
191 select HAVE_ARCH_VMAP_STACK <<
192 select HAVE_ARM_SMCCC <<
193 select HAVE_ASM_MODVERSIONS <<
194 select HAVE_EBPF_JIT <<
195 select HAVE_C_RECORDMCOUNT <<
196 select HAVE_CMPXCHG_DOUBLE <<
197 select HAVE_CMPXCHG_LOCAL <<
198 select HAVE_CONTEXT_TRACKING_USER <<
199 select HAVE_DEBUG_KMEMLEAK <<
200 select HAVE_DMA_CONTIGUOUS <<
201 select HAVE_DYNAMIC_FTRACE <<
202 select HAVE_DYNAMIC_FTRACE_WITH_ARGS \ <<
203 if (GCC_SUPPORTS_DYNAMIC_FTRAC <<
204 CLANG_SUPPORTS_DYNAMIC_FTR <<
205 select HAVE_DYNAMIC_FTRACE_WITH_DIRECT <<
206 if DYNAMIC_FTRACE_WITH_ARGS && <<
207 select HAVE_DYNAMIC_FTRACE_WITH_CALL_O <<
208 if (DYNAMIC_FTRACE_WITH_ARGS & <<
209 (CC_IS_CLANG || !CC_OPTIMI <<
210 select FTRACE_MCOUNT_USE_PATCHABLE_FUN <<
211 if DYNAMIC_FTRACE_WITH_ARGS <<
212 select HAVE_SAMPLE_FTRACE_DIRECT <<
213 select HAVE_SAMPLE_FTRACE_DIRECT_MULTI <<
214 select HAVE_EFFICIENT_UNALIGNED_ACCESS <<
215 select HAVE_GUP_FAST <<
216 select HAVE_FTRACE_MCOUNT_RECORD <<
217 select HAVE_FUNCTION_TRACER <<
218 select HAVE_FUNCTION_ERROR_INJECTION <<
219 select HAVE_FUNCTION_GRAPH_TRACER <<
220 select HAVE_FUNCTION_GRAPH_RETVAL <<
221 select HAVE_GCC_PLUGINS <<
222 select HAVE_HARDLOCKUP_DETECTOR_PERF i <<
223 HW_PERF_EVENTS && HAVE_PERF_EV <<
224 select HAVE_HW_BREAKPOINT if PERF_EVEN <<
225 select HAVE_IOREMAP_PROT <<
226 select HAVE_IRQ_TIME_ACCOUNTING <<
227 select HAVE_MOD_ARCH_SPECIFIC <<
228 select HAVE_NMI <<
229 select HAVE_PERF_EVENTS <<
230 select HAVE_PERF_EVENTS_NMI if ARM64_P <<
231 select HAVE_PERF_REGS <<
232 select HAVE_PERF_USER_STACK_DUMP <<
233 select HAVE_PREEMPT_DYNAMIC_KEY <<
234 select HAVE_REGS_AND_STACK_ACCESS_API <<
235 select HAVE_POSIX_CPU_TIMERS_TASK_WORK <<
236 select HAVE_FUNCTION_ARG_ACCESS_API <<
237 select MMU_GATHER_RCU_TABLE_FREE <<
238 select HAVE_RSEQ <<
239 select HAVE_RUST if RUSTC_SUPPORTS_ARM <<
240 select HAVE_STACKPROTECTOR <<
241 select HAVE_SYSCALL_TRACEPOINTS <<
242 select HAVE_KPROBES <<
243 select HAVE_KRETPROBES <<
244 select HAVE_GENERIC_VDSO <<
245 select HOTPLUG_CORE_SYNC_DEAD if HOTPL <<
246 select IRQ_DOMAIN <<
247 select IRQ_FORCED_THREADING <<
248 select KASAN_VMALLOC if KASAN <<
249 select LOCK_MM_AND_FIND_VMA <<
250 select MODULES_USE_ELF_RELA <<
251 select NEED_DMA_MAP_STATE <<
252 select NEED_SG_DMA_LENGTH <<
253 select OF <<
254 select OF_EARLY_FLATTREE <<
255 select PCI_DOMAINS_GENERIC if PCI <<
256 select PCI_ECAM if (ACPI && PCI) <<
257 select PCI_SYSCALL if PCI <<
258 select POWER_RESET <<
259 select POWER_SUPPLY <<
260 select SPARSE_IRQ <<
261 select SWIOTLB <<
262 select SYSCTL_EXCEPTION_TRACE <<
263 select THREAD_INFO_IN_TASK <<
264 select HAVE_ARCH_USERFAULTFD_MINOR if <<
265 select HAVE_ARCH_USERFAULTFD_WP if USE <<
266 select TRACE_IRQFLAGS_SUPPORT <<
267 select TRACE_IRQFLAGS_NMI_SUPPORT <<
268 select HAVE_SOFTIRQ_ON_OWN_STACK <<
269 select USER_STACKTRACE_SUPPORT <<
270 select VDSO_GETRANDOM <<
271 help <<
272 ARM 64-bit (AArch64) Linux support. <<
273 <<
274 config RUSTC_SUPPORTS_ARM64 <<
275 def_bool y <<
276 depends on CPU_LITTLE_ENDIAN <<
277 # Shadow call stack is only supported <<
278 # <<
279 # When using the UNWIND_PATCH_PAC_INTO <<
280 # required due to use of the -Zfixed-x <<
281 # <<
282 # Otherwise, rustc version 1.82+ is re <<
283 # -Zsanitizer=shadow-call-stack flag. <<
284 depends on !SHADOW_CALL_STACK || RUSTC <<
285 <<
286 config CLANG_SUPPORTS_DYNAMIC_FTRACE_WITH_ARGS <<
287 def_bool CC_IS_CLANG <<
288 # https://github.com/ClangBuiltLinux/l <<
289 depends on AS_IS_GNU || (AS_IS_LLVM && <<
290 <<
291 config GCC_SUPPORTS_DYNAMIC_FTRACE_WITH_ARGS <<
292 def_bool CC_IS_GCC <<
293 depends on $(cc-option,-fpatchable-fun <<
294 <<
295 config 64BIT <<
296 def_bool y <<
297 <<
298 config MMU <<
299 def_bool y <<
300 <<
301 config ARM64_CONT_PTE_SHIFT <<
302 int <<
303 default 5 if PAGE_SIZE_64KB <<
304 default 7 if PAGE_SIZE_16KB <<
305 default 4 <<
306 <<
307 config ARM64_CONT_PMD_SHIFT <<
308 int <<
309 default 5 if PAGE_SIZE_64KB <<
310 default 5 if PAGE_SIZE_16KB <<
311 default 4 <<
312 <<
313 config ARCH_MMAP_RND_BITS_MIN <<
314 default 14 if PAGE_SIZE_64KB <<
315 default 16 if PAGE_SIZE_16KB <<
316 default 18 <<
317 <<
318 # max bits determined by the following formula <<
319 # VA_BITS - PAGE_SHIFT - 3 <<
320 config ARCH_MMAP_RND_BITS_MAX <<
321 default 19 if ARM64_VA_BITS=36 <<
322 default 24 if ARM64_VA_BITS=39 <<
323 default 27 if ARM64_VA_BITS=42 <<
324 default 30 if ARM64_VA_BITS=47 <<
325 default 29 if ARM64_VA_BITS=48 && ARM6 <<
326 default 31 if ARM64_VA_BITS=48 && ARM6 <<
327 default 33 if ARM64_VA_BITS=48 <<
328 default 14 if ARM64_64K_PAGES <<
329 default 16 if ARM64_16K_PAGES <<
330 default 18 <<
331 <<
332 config ARCH_MMAP_RND_COMPAT_BITS_MIN <<
333 default 7 if ARM64_64K_PAGES <<
334 default 9 if ARM64_16K_PAGES <<
335 default 11 <<
336 <<
337 config ARCH_MMAP_RND_COMPAT_BITS_MAX <<
338 default 16 <<
339 <<
340 config NO_IOPORT_MAP <<
341 def_bool y if !PCI <<
342 <<
343 config STACKTRACE_SUPPORT <<
344 def_bool y <<
345 <<
346 config ILLEGAL_POINTER_VALUE <<
347 hex <<
348 default 0xdead000000000000 <<
349 <<
350 config LOCKDEP_SUPPORT <<
351 def_bool y <<
352 <<
353 config GENERIC_BUG <<
354 def_bool y <<
355 depends on BUG <<
356 <<
357 config GENERIC_BUG_RELATIVE_POINTERS <<
358 def_bool y <<
359 depends on GENERIC_BUG <<
360 <<
361 config GENERIC_HWEIGHT <<
362 def_bool y <<
363 <<
364 config GENERIC_CSUM <<
365 def_bool y <<
366 <<
367 config GENERIC_CALIBRATE_DELAY <<
368 def_bool y <<
369 <<
370 config SMP <<
371 def_bool y <<
372 <<
373 config KERNEL_MODE_NEON <<
374 def_bool y <<
375 <<
376 config FIX_EARLYCON_MEM <<
377 def_bool y <<
378 <<
379 config PGTABLE_LEVELS <<
380 int <<
381 default 2 if ARM64_16K_PAGES && ARM64_ <<
382 default 2 if ARM64_64K_PAGES && ARM64_ <<
383 default 3 if ARM64_64K_PAGES && (ARM64 <<
384 default 3 if ARM64_4K_PAGES && ARM64_V <<
385 default 3 if ARM64_16K_PAGES && ARM64_ <<
386 default 4 if ARM64_16K_PAGES && (ARM64 <<
387 default 4 if !ARM64_64K_PAGES && ARM64 <<
388 default 5 if ARM64_4K_PAGES && ARM64_V <<
389 <<
390 config ARCH_SUPPORTS_UPROBES <<
391 def_bool y <<
392 <<
393 config ARCH_PROC_KCORE_TEXT <<
394 def_bool y <<
395 <<
396 config BROKEN_GAS_INST <<
397 def_bool !$(as-instr,1:\n.inst 0\n.rep <<
398 <<
399 config BUILTIN_RETURN_ADDRESS_STRIPS_PAC <<
400 bool <<
401 # Clang's __builtin_return_address() s <<
402 # https://github.com/llvm/llvm-project <<
403 default y if CC_IS_CLANG <<
404 # GCC's __builtin_return_address() str <<
405 # and this was backported to 10.2.0, 9 <<
406 # https://gcc.gnu.org/bugzilla/show_bu <<
407 default y if CC_IS_GCC && (GCC_VERSION <<
408 default y if CC_IS_GCC && (GCC_VERSION <<
409 default y if CC_IS_GCC && (GCC_VERSION <<
410 default y if CC_IS_GCC && (GCC_VERSION <<
411 default n <<
412 <<
413 config KASAN_SHADOW_OFFSET <<
414 hex <<
415 depends on KASAN_GENERIC || KASAN_SW_T <<
416 default 0xdfff800000000000 if (ARM64_V <<
417 default 0xdfffc00000000000 if (ARM64_V <<
418 default 0xdffffe0000000000 if ARM64_VA <<
419 default 0xdfffffc000000000 if ARM64_VA <<
420 default 0xdffffff800000000 if ARM64_VA <<
421 default 0xefff800000000000 if (ARM64_V <<
422 default 0xefffc00000000000 if (ARM64_V <<
423 default 0xeffffe0000000000 if ARM64_VA <<
424 default 0xefffffc000000000 if ARM64_VA <<
425 default 0xeffffff800000000 if ARM64_VA <<
426 default 0xffffffffffffffff <<
427 <<
428 config UNWIND_TABLES <<
429 bool 6 bool
430 <<
431 source "arch/arm64/Kconfig.platforms" <<
432 <<
433 menu "Kernel Features" <<
434 <<
435 menu "ARM errata workarounds via the alternati <<
436 <<
437 config AMPERE_ERRATUM_AC03_CPU_38 <<
438 bool "AmpereOne: AC03_CPU_38: Certain <<
439 default y 7 default y
440 help <<
441 This option adds an alternative code <<
442 errata AC03_CPU_38 and AC04_CPU_10 o <<
443 8
444 The affected design reports FEAT_HAF !! 9 config MMU
445 ID_AA64MMFR1_EL1.HAFDBS, but (V)TCR_ <<
446 as required by the architecture. The <<
447 implementation suffers from an addit <<
448 A/D updates can occur after a PTE ha <<
449 <<
450 The workaround forces KVM to explici <<
451 which avoids enabling unadvertised h <<
452 at stage-2. <<
453 <<
454 If unsure, say Y. <<
455 <<
456 config ARM64_WORKAROUND_CLEAN_CACHE <<
457 bool 10 bool
458 <<
459 config ARM64_ERRATUM_826319 <<
460 bool "Cortex-A53: 826319: System might <<
461 default y <<
462 select ARM64_WORKAROUND_CLEAN_CACHE <<
463 help <<
464 This option adds an alternative code <<
465 erratum 826319 on Cortex-A53 parts u <<
466 AXI master interface and an L2 cache <<
467 <<
468 If a Cortex-A53 uses an AMBA AXI4 AC <<
469 and is unable to accept a certain wr <<
470 not progress on read data presented <<
471 system can deadlock. <<
472 <<
473 The workaround promotes data cache c <<
474 data cache clean-and-invalidate. <<
475 Please note that this does not neces <<
476 as it depends on the alternative fra <<
477 the kernel if an affected CPU is det <<
478 <<
479 If unsure, say Y. <<
480 <<
481 config ARM64_ERRATUM_827319 <<
482 bool "Cortex-A53: 827319: Data cache c <<
483 default y <<
484 select ARM64_WORKAROUND_CLEAN_CACHE <<
485 help <<
486 This option adds an alternative code <<
487 erratum 827319 on Cortex-A53 parts u <<
488 master interface and an L2 cache. <<
489 <<
490 Under certain conditions this erratu <<
491 to occur at the same time as another <<
492 on the AMBA 5 CHI interface, which c <<
493 interconnect reorders the two transa <<
494 <<
495 The workaround promotes data cache c <<
496 data cache clean-and-invalidate. <<
497 Please note that this does not neces <<
498 as it depends on the alternative fra <<
499 the kernel if an affected CPU is det <<
500 <<
501 If unsure, say Y. <<
502 <<
503 config ARM64_ERRATUM_824069 <<
504 bool "Cortex-A53: 824069: Cache line m <<
505 default y <<
506 select ARM64_WORKAROUND_CLEAN_CACHE <<
507 help <<
508 This option adds an alternative code <<
509 erratum 824069 on Cortex-A53 parts u <<
510 to a coherent interconnect. <<
511 <<
512 If a Cortex-A53 processor is executi <<
513 write instruction at the same time a <<
514 cluster is executing a cache mainten <<
515 address, then this erratum might cau <<
516 incorrectly marked as dirty. <<
517 <<
518 The workaround promotes data cache c <<
519 data cache clean-and-invalidate. <<
520 Please note that this option does no <<
521 workaround, as it depends on the alt <<
522 only patch the kernel if an affected <<
523 <<
524 If unsure, say Y. <<
525 <<
526 config ARM64_ERRATUM_819472 <<
527 bool "Cortex-A53: 819472: Store exclus <<
528 default y <<
529 select ARM64_WORKAROUND_CLEAN_CACHE <<
530 help <<
531 This option adds an alternative code <<
532 erratum 819472 on Cortex-A53 parts u <<
533 present when it is connected to a co <<
534 <<
535 If the processor is executing a load <<
536 the same time as a processor in anot <<
537 maintenance operation to the same ad <<
538 cause data corruption. <<
539 <<
540 The workaround promotes data cache c <<
541 data cache clean-and-invalidate. <<
542 Please note that this does not neces <<
543 as it depends on the alternative fra <<
544 the kernel if an affected CPU is det <<
545 <<
546 If unsure, say Y. <<
547 <<
548 config ARM64_ERRATUM_832075 <<
549 bool "Cortex-A57: 832075: possible dea <<
550 default y <<
551 help <<
552 This option adds an alternative code <<
553 erratum 832075 on Cortex-A57 parts u <<
554 <<
555 Affected Cortex-A57 parts might dead <<
556 instructions to Write-Back memory ar <<
557 <<
558 The workaround is to promote device <<
559 semantics. <<
560 Please note that this does not neces <<
561 as it depends on the alternative fra <<
562 the kernel if an affected CPU is det <<
563 <<
564 If unsure, say Y. <<
565 <<
566 config ARM64_ERRATUM_834220 <<
567 bool "Cortex-A57: 834220: Stage 2 tran <<
568 depends on KVM <<
569 help <<
570 This option adds an alternative code <<
571 erratum 834220 on Cortex-A57 parts u <<
572 <<
573 Affected Cortex-A57 parts might repo <<
574 fault as the result of a Stage 1 fau <<
575 page boundary when there is a permis <<
576 alignment fault at Stage 1 and a tra <<
577 <<
578 The workaround is to verify that the <<
579 doesn't generate a fault before hand <<
580 Please note that this does not neces <<
581 as it depends on the alternative fra <<
582 the kernel if an affected CPU is det <<
583 <<
584 If unsure, say N. <<
585 <<
586 config ARM64_ERRATUM_1742098 <<
587 bool "Cortex-A57/A72: 1742098: ELR rec <<
588 depends on COMPAT <<
589 default y <<
590 help <<
591 This option removes the AES hwcap fo <<
592 workaround erratum 1742098 on Cortex <<
593 <<
594 Affected parts may corrupt the AES s <<
595 taken between a pair of AES instruct <<
596 are only present if the cryptography <<
597 All software should have a fallback <<
598 that don't implement the cryptograph <<
599 <<
600 If unsure, say Y. <<
601 <<
602 config ARM64_ERRATUM_845719 <<
603 bool "Cortex-A53: 845719: a load might <<
604 depends on COMPAT <<
605 default y <<
606 help <<
607 This option adds an alternative code <<
608 erratum 845719 on Cortex-A53 parts u <<
609 <<
610 When running a compat (AArch32) user <<
611 part, a load at EL0 from a virtual a <<
612 bits of the virtual address used by <<
613 might return incorrect data. <<
614 <<
615 The workaround is to write the conte <<
616 return to a 32-bit task. <<
617 Please note that this does not neces <<
618 as it depends on the alternative fra <<
619 the kernel if an affected CPU is det <<
620 <<
621 If unsure, say Y. <<
622 <<
623 config ARM64_ERRATUM_843419 <<
624 bool "Cortex-A53: 843419: A load or st <<
625 default y <<
626 help <<
627 This option links the kernel with '- <<
628 enables PLT support to replace certa <<
629 cause subsequent memory accesses to <<
630 Cortex-A53 parts up to r0p4. <<
631 <<
632 If unsure, say Y. <<
633 <<
634 config ARM64_LD_HAS_FIX_ERRATUM_843419 <<
635 def_bool $(ld-option,--fix-cortex-a53- <<
636 <<
637 config ARM64_ERRATUM_1024718 <<
638 bool "Cortex-A55: 1024718: Update of D <<
639 default y <<
640 help <<
641 This option adds a workaround for AR <<
642 <<
643 Affected Cortex-A55 cores (all revis <<
644 update of the hardware dirty bit whe <<
645 without a break-before-make. The wor <<
646 of hardware DBM locally on the affec <<
647 this erratum will continue to use th <<
648 <<
649 If unsure, say Y. <<
650 <<
651 config ARM64_ERRATUM_1418040 <<
652 bool "Cortex-A76/Neoverse-N1: MRC read <<
653 default y 11 default y
654 depends on COMPAT <<
655 help <<
656 This option adds a workaround for AR <<
657 errata 1188873 and 1418040. <<
658 12
659 Affected Cortex-A76/Neoverse-N1 core !! 13 config UID16
660 cause register corruption when acces <<
661 from AArch32 userspace. <<
662 <<
663 If unsure, say Y. <<
664 <<
665 config ARM64_WORKAROUND_SPECULATIVE_AT <<
666 bool 14 bool
667 <<
668 config ARM64_ERRATUM_1165522 <<
669 bool "Cortex-A76: 1165522: Speculative <<
670 default y 15 default y
671 select ARM64_WORKAROUND_SPECULATIVE_AT <<
672 help <<
673 This option adds a workaround for AR <<
674 <<
675 Affected Cortex-A76 cores (r0p0, r1p <<
676 corrupted TLBs by speculating an AT <<
677 context switch. <<
678 <<
679 If unsure, say Y. <<
680 <<
681 config ARM64_ERRATUM_1319367 <<
682 bool "Cortex-A57/A72: 1319537: Specula <<
683 default y <<
684 select ARM64_WORKAROUND_SPECULATIVE_AT <<
685 help <<
686 This option adds work arounds for AR <<
687 and A72 erratum 1319367 <<
688 <<
689 Cortex-A57 and A72 cores could end-u <<
690 speculating an AT instruction during <<
691 <<
692 If unsure, say Y. <<
693 <<
694 config ARM64_ERRATUM_1530923 <<
695 bool "Cortex-A55: 1530923: Speculative <<
696 default y <<
697 select ARM64_WORKAROUND_SPECULATIVE_AT <<
698 help <<
699 This option adds a workaround for AR <<
700 <<
701 Affected Cortex-A55 cores (r0p0, r0p <<
702 corrupted TLBs by speculating an AT <<
703 context switch. <<
704 <<
705 If unsure, say Y. <<
706 16
707 config ARM64_WORKAROUND_REPEAT_TLBI !! 17 config RWSEM_GENERIC_SPINLOCK
708 bool 18 bool
709 <<
710 config ARM64_ERRATUM_2441007 <<
711 bool "Cortex-A55: Completion of affect <<
712 select ARM64_WORKAROUND_REPEAT_TLBI <<
713 help <<
714 This option adds a workaround for AR <<
715 <<
716 Under very rare circumstances, affec <<
717 may not handle a race between a brea <<
718 CPU, and another CPU accessing the s <<
719 store to a page that has been unmapp <<
720 <<
721 Work around this by adding the affec <<
722 TLB sequences to be done twice. <<
723 <<
724 If unsure, say N. <<
725 <<
726 config ARM64_ERRATUM_1286807 <<
727 bool "Cortex-A76: Modification of the <<
728 select ARM64_WORKAROUND_REPEAT_TLBI <<
729 help <<
730 This option adds a workaround for AR <<
731 <<
732 On the affected Cortex-A76 cores (r0 <<
733 address for a cacheable mapping of a <<
734 accessed by a core while another cor <<
735 address to a new physical page using <<
736 break-before-make sequence, then und <<
737 TLBI+DSB completes before a read usi <<
738 invalidated has been observed by oth <<
739 workaround repeats the TLBI+DSB oper <<
740 <<
741 If unsure, say N. <<
742 <<
743 config ARM64_ERRATUM_1463225 <<
744 bool "Cortex-A76: Software Step might <<
745 default y <<
746 help <<
747 This option adds a workaround for Ar <<
748 <<
749 On the affected Cortex-A76 cores (r0 <<
750 of a system call instruction (SVC) c <<
751 subsequent interrupts when software <<
752 exception handler of the system call <<
753 is enabled or VHE is in use. <<
754 <<
755 Work around the erratum by triggerin <<
756 when handling a system call from a t <<
757 in a VHE configuration of the kernel <<
758 <<
759 If unsure, say Y. <<
760 <<
761 config ARM64_ERRATUM_1542419 <<
762 bool "Neoverse-N1: workaround mis-orde <<
763 help <<
764 This option adds a workaround for AR <<
765 1542419. <<
766 <<
767 Affected Neoverse-N1 cores could exe <<
768 modified by another CPU. The workaro <<
769 counterpart. <<
770 <<
771 Workaround the issue by hiding the D <<
772 forces user-space to perform cache m <<
773 <<
774 If unsure, say N. <<
775 <<
776 config ARM64_ERRATUM_1508412 <<
777 bool "Cortex-A77: 1508412: workaround <<
778 default y 19 default y
779 help <<
780 This option adds a workaround for Ar <<
781 <<
782 Affected Cortex-A77 cores (r0p0, r1p <<
783 of a store-exclusive or read of PAR_ <<
784 non-cacheable memory attributes. The <<
785 counterpart. <<
786 <<
787 KVM guests must also have the workar <<
788 deadlock the system. <<
789 <<
790 Work around the issue by inserting D <<
791 register reads and warning KVM users <<
792 to prevent a speculative PAR_EL1 rea <<
793 <<
794 If unsure, say Y. <<
795 20
796 config ARM64_WORKAROUND_TRBE_OVERWRITE_FILL_MO !! 21 config RWSEM_XCHGADD_ALGORITHM
797 bool 22 bool
798 23
799 config ARM64_ERRATUM_2051678 <<
800 bool "Cortex-A510: 2051678: disable Ha <<
801 default y <<
802 help <<
803 This options adds the workaround for <<
804 Affected Cortex-A510 might not respe <<
805 hardware update of the page table's <<
806 is to not enable the feature on affe <<
807 <<
808 If unsure, say Y. <<
809 24
810 config ARM64_ERRATUM_2077057 !! 25 mainmenu "Linux/68k Kernel Configuration"
811 bool "Cortex-A510: 2077057: workaround <<
812 default y <<
813 help <<
814 This option adds the workaround for <<
815 Affected Cortex-A510 may corrupt SPS <<
816 expected, but a Pointer Authenticati <<
817 erratum causes SPSR_EL1 to be copied <<
818 EL1 to cause a return to EL2 with a <<
819 26
820 This can only happen when EL2 is ste !! 27 source "init/Kconfig"
821 28
822 When these conditions occur, the SPS <<
823 previous guest entry, and can be res <<
824 29
825 If unsure, say Y. !! 30 menu "Platform dependent setup"
826 31
827 config ARM64_ERRATUM_2658417 !! 32 config EISA
828 bool "Cortex-A510: 2658417: remove BF1 <<
829 default y <<
830 help <<
831 This option adds the workaround for <<
832 Affected Cortex-A510 (r0p0 to r1p1) <<
833 BFMMLA or VMMLA instructions in rare <<
834 A510 CPUs are using shared neon hard <<
835 discoverable by the kernel, hide the <<
836 user-space should not be using these <<
837 <<
838 If unsure, say Y. <<
839 <<
840 config ARM64_ERRATUM_2119858 <<
841 bool "Cortex-A710/X2: 2119858: workaro <<
842 default y <<
843 depends on CORESIGHT_TRBE <<
844 select ARM64_WORKAROUND_TRBE_OVERWRITE <<
845 help <<
846 This option adds the workaround for <<
847 <<
848 Affected Cortex-A710/X2 cores could <<
849 data at the base of the buffer (poin <<
850 the event of a WRAP event. <<
851 <<
852 Work around the issue by always maki <<
853 256 bytes before enabling the buffer <<
854 the buffer with ETM ignore packets u <<
855 <<
856 If unsure, say Y. <<
857 <<
858 config ARM64_ERRATUM_2139208 <<
859 bool "Neoverse-N2: 2139208: workaround <<
860 default y <<
861 depends on CORESIGHT_TRBE <<
862 select ARM64_WORKAROUND_TRBE_OVERWRITE <<
863 help <<
864 This option adds the workaround for <<
865 <<
866 Affected Neoverse-N2 cores could ove <<
867 data at the base of the buffer (poin <<
868 the event of a WRAP event. <<
869 <<
870 Work around the issue by always maki <<
871 256 bytes before enabling the buffer <<
872 the buffer with ETM ignore packets u <<
873 <<
874 If unsure, say Y. <<
875 <<
876 config ARM64_WORKAROUND_TSB_FLUSH_FAILURE <<
877 bool 33 bool
>> 34 ---help---
>> 35 The Extended Industry Standard Architecture (EISA) bus was
>> 36 developed as an open alternative to the IBM MicroChannel bus.
878 37
879 config ARM64_ERRATUM_2054223 !! 38 The EISA bus provided some of the features of the IBM MicroChannel
880 bool "Cortex-A710: 2054223: workaround !! 39 bus while maintaining backward compatibility with cards made for
881 default y !! 40 the older ISA bus. The EISA bus saw limited use between 1988 and
882 select ARM64_WORKAROUND_TSB_FLUSH_FAIL !! 41 1995 when it was made obsolete by the PCI bus.
883 help <<
884 Enable workaround for ARM Cortex-A71 <<
885 <<
886 Affected cores may fail to flush the <<
887 the PE is in trace prohibited state. <<
888 of the trace cached. <<
889 <<
890 Workaround is to issue two TSB conse <<
891 <<
892 If unsure, say Y. <<
893 <<
894 config ARM64_ERRATUM_2067961 <<
895 bool "Neoverse-N2: 2067961: workaround <<
896 default y <<
897 select ARM64_WORKAROUND_TSB_FLUSH_FAIL <<
898 help <<
899 Enable workaround for ARM Neoverse-N <<
900 <<
901 Affected cores may fail to flush the <<
902 the PE is in trace prohibited state. <<
903 of the trace cached. <<
904 42
905 Workaround is to issue two TSB conse !! 43 Say Y here if you are building a kernel for an EISA-based machine.
906 44
907 If unsure, say Y. !! 45 Otherwise, say N.
908 46
909 config ARM64_WORKAROUND_TRBE_WRITE_OUT_OF_RANG !! 47 config MCA
910 bool 48 bool
911 <<
912 config ARM64_ERRATUM_2253138 <<
913 bool "Neoverse-N2: 2253138: workaround <<
914 depends on CORESIGHT_TRBE <<
915 default y <<
916 select ARM64_WORKAROUND_TRBE_WRITE_OUT <<
917 help <<
918 This option adds the workaround for <<
919 <<
920 Affected Neoverse-N2 cores might wri <<
921 for TRBE. Under some conditions, the <<
922 virtually addressed page following t <<
923 (i.e., the TRBLIMITR_EL1.LIMIT), ins <<
924 <<
925 Work around this in the driver by al <<
926 page beyond the TRBLIMITR_EL1.LIMIT, <<
927 <<
928 If unsure, say Y. <<
929 <<
930 config ARM64_ERRATUM_2224489 <<
931 bool "Cortex-A710/X2: 2224489: workaro <<
932 depends on CORESIGHT_TRBE <<
933 default y <<
934 select ARM64_WORKAROUND_TRBE_WRITE_OUT <<
935 help <<
936 This option adds the workaround for <<
937 <<
938 Affected Cortex-A710/X2 cores might <<
939 for TRBE. Under some conditions, the <<
940 virtually addressed page following t <<
941 (i.e., the TRBLIMITR_EL1.LIMIT), ins <<
942 <<
943 Work around this in the driver by al <<
944 page beyond the TRBLIMITR_EL1.LIMIT, <<
945 <<
946 If unsure, say Y. <<
947 <<
948 config ARM64_ERRATUM_2441009 <<
949 bool "Cortex-A510: Completion of affec <<
950 select ARM64_WORKAROUND_REPEAT_TLBI <<
951 help <<
952 This option adds a workaround for AR <<
953 <<
954 Under very rare circumstances, affec <<
955 may not handle a race between a brea <<
956 CPU, and another CPU accessing the s <<
957 store to a page that has been unmapp <<
958 <<
959 Work around this by adding the affec <<
960 TLB sequences to be done twice. <<
961 <<
962 If unsure, say N. <<
963 <<
964 config ARM64_ERRATUM_2064142 <<
965 bool "Cortex-A510: 2064142: workaround <<
966 depends on CORESIGHT_TRBE <<
967 default y <<
968 help <<
969 This option adds the workaround for <<
970 <<
971 Affected Cortex-A510 core might fail <<
972 TRBE has been disabled. Under some c <<
973 writes into TRBE registers TRBLIMITR <<
974 and TRBTRG_EL1 will be ignored and w <<
975 <<
976 Work around this in the driver by ex <<
977 is stopped and before performing a s <<
978 registers. <<
979 <<
980 If unsure, say Y. <<
981 <<
982 config ARM64_ERRATUM_2038923 <<
983 bool "Cortex-A510: 2038923: workaround <<
984 depends on CORESIGHT_TRBE <<
985 default y <<
986 help <<
987 This option adds the workaround for <<
988 <<
989 Affected Cortex-A510 core might caus <<
990 prohibited within the CPU. As a resu <<
991 might be corrupted. This happens aft <<
992 TRBLIMITR_EL1.E, followed by just a <<
993 execution changes from a context, in <<
994 isn't, or vice versa. In these menti <<
995 is prohibited is inconsistent betwee <<
996 the trace buffer state might be corr <<
997 <<
998 Work around this in the driver by pr <<
999 trace is prohibited or not based on <<
1000 change to TRBLIMITR_EL1.E with at l <<
1001 two ISB instructions if no ERET is <<
1002 <<
1003 If unsure, say Y. <<
1004 <<
1005 config ARM64_ERRATUM_1902691 <<
1006 bool "Cortex-A510: 1902691: workaroun <<
1007 depends on CORESIGHT_TRBE <<
1008 default y <<
1009 help 49 help
1010 This option adds the workaround for !! 50 MicroChannel Architecture is found in some IBM PS/2 machines and
1011 !! 51 laptops. It is a bus system similar to PCI or ISA. See
1012 Affected Cortex-A510 core might cau !! 52 <file:Documentation/mca.txt> (and especially the web page given
1013 into the memory. Effectively TRBE i !! 53 there) before attempting to build an MCA bus kernel.
1014 trace data. !! 54
1015 !! 55 config PCMCIA
1016 Work around this problem in the dri !! 56 tristate
1017 affected cpus. The firmware must ha !! 57 ---help---
1018 on such implementations. This will !! 58 Say Y here if you want to attach PCMCIA- or PC-cards to your Linux
1019 do this already. !! 59 computer. These are credit-card size devices such as network cards,
1020 !! 60 modems or hard drives often used with laptops computers. There are
1021 If unsure, say Y. !! 61 actually two varieties of these cards: the older 16 bit PCMCIA cards
1022 !! 62 and the newer 32 bit CardBus cards. If you want to use CardBus
1023 config ARM64_ERRATUM_2457168 !! 63 cards, you need to say Y here and also to "CardBus support" below.
1024 bool "Cortex-A510: 2457168: workaroun !! 64
1025 depends on ARM64_AMU_EXTN !! 65 To use your PC-cards, you will need supporting software from David
1026 default y !! 66 Hinds' pcmcia-cs package (see the file <file:Documentation/Changes>
>> 67 for location). Please also read the PCMCIA-HOWTO, available from
>> 68 <http://www.tldp.org/docs.html#howto>.
>> 69
>> 70 To compile this driver as modules, choose M here: the
>> 71 modules will be called pcmcia_core and ds.
>> 72
>> 73 config AMIGA
>> 74 bool "Amiga support"
>> 75 help
>> 76 This option enables support for the Amiga series of computers. If
>> 77 you plan to use this kernel on an Amiga, say Y here and browse the
>> 78 material available in <file:Documentation/m68k>; otherwise say N.
>> 79
>> 80 config ATARI
>> 81 bool "Atari support"
>> 82 help
>> 83 This option enables support for the 68000-based Atari series of
>> 84 computers (including the TT, Falcon and Medusa). If you plan to use
>> 85 this kernel on an Atari, say Y here and browse the material
>> 86 available in <file:Documentation/m68k>; otherwise say N.
>> 87
>> 88 config HADES
>> 89 bool "Hades support"
>> 90 depends on ATARI && BROKEN
1027 help 91 help
1028 This option adds the workaround for !! 92 This option enables support for the Hades Atari clone. If you plan
>> 93 to use this kernel on a Hades, say Y here; otherwise say N.
1029 94
1030 The AMU counter AMEVCNTR01 (constan !! 95 config PCI
1031 as the system counter. On affected <<
1032 incorrectly giving a significantly <<
1033 <<
1034 Work around this problem by returni <<
1035 key locations that results in disab <<
1036 is the same to firmware disabling a <<
1037 <<
1038 If unsure, say Y. <<
1039 <<
1040 config ARM64_ERRATUM_2645198 <<
1041 bool "Cortex-A715: 2645198: Workaroun <<
1042 default y <<
1043 help <<
1044 This option adds the workaround for <<
1045 <<
1046 If a Cortex-A715 cpu sees a page ma <<
1047 to non-executable, it may corrupt t <<
1048 next instruction abort caused by pe <<
1049 <<
1050 Only user-space does executable to <<
1051 mprotect() system call. Workaround <<
1052 TLB invalidation, for all changes t <<
1053 <<
1054 If unsure, say Y. <<
1055 <<
1056 config ARM64_WORKAROUND_SPECULATIVE_UNPRIV_LO <<
1057 bool 96 bool
1058 !! 97 depends on HADES
1059 config ARM64_ERRATUM_2966298 <<
1060 bool "Cortex-A520: 2966298: workaroun <<
1061 select ARM64_WORKAROUND_SPECULATIVE_U <<
1062 default y <<
1063 help <<
1064 This option adds the workaround for <<
1065 <<
1066 On an affected Cortex-A520 core, a <<
1067 load might leak data from a privile <<
1068 <<
1069 Work around this problem by executi <<
1070 <<
1071 If unsure, say Y. <<
1072 <<
1073 config ARM64_ERRATUM_3117295 <<
1074 bool "Cortex-A510: 3117295: workaroun <<
1075 select ARM64_WORKAROUND_SPECULATIVE_U <<
1076 default y <<
1077 help <<
1078 This option adds the workaround for <<
1079 <<
1080 On an affected Cortex-A510 core, a <<
1081 load might leak data from a privile <<
1082 <<
1083 Work around this problem by executi <<
1084 <<
1085 If unsure, say Y. <<
1086 <<
1087 config ARM64_ERRATUM_3194386 <<
1088 bool "Cortex-*/Neoverse-*: workaround <<
1089 default y 98 default y
1090 help 99 help
1091 This option adds the workaround for !! 100 Find out whether you have a PCI motherboard. PCI is the name of a
>> 101 bus system, i.e. the way the CPU talks to the other stuff inside
>> 102 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
>> 103 VESA. If you have PCI, say Y, otherwise N.
1092 104
1093 * ARM Cortex-A76 erratum 3324349 !! 105 The PCI-HOWTO, available from
1094 * ARM Cortex-A77 erratum 3324348 !! 106 <http://www.tldp.org/docs.html#howto>, contains valuable
1095 * ARM Cortex-A78 erratum 3324344 !! 107 information about which PCI hardware does work under Linux and which
1096 * ARM Cortex-A78C erratum 3324346 !! 108 doesn't.
1097 * ARM Cortex-A78C erratum 3324347 <<
1098 * ARM Cortex-A710 erratam 3324338 <<
1099 * ARM Cortex-A715 errartum 3456084 <<
1100 * ARM Cortex-A720 erratum 3456091 <<
1101 * ARM Cortex-A725 erratum 3456106 <<
1102 * ARM Cortex-X1 erratum 3324344 <<
1103 * ARM Cortex-X1C erratum 3324346 <<
1104 * ARM Cortex-X2 erratum 3324338 <<
1105 * ARM Cortex-X3 erratum 3324335 <<
1106 * ARM Cortex-X4 erratum 3194386 <<
1107 * ARM Cortex-X925 erratum 3324334 <<
1108 * ARM Neoverse-N1 erratum 3324349 <<
1109 * ARM Neoverse N2 erratum 3324339 <<
1110 * ARM Neoverse-N3 erratum 3456111 <<
1111 * ARM Neoverse-V1 erratum 3324341 <<
1112 * ARM Neoverse V2 erratum 3324336 <<
1113 * ARM Neoverse-V3 erratum 3312417 <<
1114 <<
1115 On affected cores "MSR SSBS, #0" in <<
1116 subsequent speculative instructions <<
1117 speculative store bypassing. <<
1118 <<
1119 Work around this problem by placing <<
1120 Instruction Synchronization Barrier <<
1121 SSBS. The presence of the SSBS spec <<
1122 from hwcaps and EL0 reads of ID_AA6 <<
1123 will use the PR_SPEC_STORE_BYPASS p <<
1124 109
1125 If unsure, say Y. !! 110 config MAC
1126 !! 111 bool "Macintosh support"
1127 config CAVIUM_ERRATUM_22375 <<
1128 bool "Cavium erratum 22375, 24313" <<
1129 default y <<
1130 help 112 help
1131 Enable workaround for errata 22375 !! 113 This option enables support for the Apple Macintosh series of
1132 !! 114 computers (yes, there is experimental support now, at least for part
1133 This implements two gicv3-its errat !! 115 of the series).
1134 with a small impact affecting only <<
1135 116
1136 erratum 22375: only alloc 8MB tab !! 117 Say N unless you're willing to code the remaining necessary support.
1137 erratum 24313: ignore memory acce !! 118 ;)
1138 119
1139 The fixes are in ITS initialization !! 120 config NUBUS
1140 type and table size provided by the !! 121 bool
1141 !! 122 depends on MAC
1142 If unsure, say Y. <<
1143 <<
1144 config CAVIUM_ERRATUM_23144 <<
1145 bool "Cavium erratum 23144: ITS SYNC <<
1146 depends on NUMA <<
1147 default y <<
1148 help <<
1149 ITS SYNC command hang for cross nod <<
1150 <<
1151 If unsure, say Y. <<
1152 <<
1153 config CAVIUM_ERRATUM_23154 <<
1154 bool "Cavium errata 23154 and 38545: <<
1155 default y <<
1156 help <<
1157 The ThunderX GICv3 implementation r <<
1158 reading the IAR status to ensure da <<
1159 (access to icc_iar1_el1 is not sync <<
1160 <<
1161 It also suffers from erratum 38545 <<
1162 OcteonTX and OcteonTX2), resulting <<
1163 spuriously presented to the CPU int <<
1164 <<
1165 If unsure, say Y. <<
1166 <<
1167 config CAVIUM_ERRATUM_27456 <<
1168 bool "Cavium erratum 27456: Broadcast <<
1169 default y <<
1170 help <<
1171 On ThunderX T88 pass 1.x through 2. <<
1172 instructions may cause the icache t <<
1173 contains data for a non-current ASI <<
1174 invalidate the icache when changing <<
1175 <<
1176 If unsure, say Y. <<
1177 <<
1178 config CAVIUM_ERRATUM_30115 <<
1179 bool "Cavium erratum 30115: Guest may <<
1180 default y 123 default y
1181 help <<
1182 On ThunderX T88 pass 1.x through 2. <<
1183 1.2, and T83 Pass 1.0, KVM guest ex <<
1184 interrupts in host. Trapping both G <<
1185 accesses sidesteps the issue. <<
1186 124
1187 If unsure, say Y. !! 125 config M68K_L2_CACHE
1188 !! 126 bool
1189 config CAVIUM_TX2_ERRATUM_219 !! 127 depends on MAC
1190 bool "Cavium ThunderX2 erratum 219: P <<
1191 default y 128 default y
1192 help <<
1193 On Cavium ThunderX2, a load, store <<
1194 TTBR update and the corresponding c <<
1195 cause a spurious Data Abort to be d <<
1196 the CPU core. <<
1197 <<
1198 Work around the issue by avoiding t <<
1199 trapping KVM guest TTBRx_EL1 writes <<
1200 trap handler performs the correspon <<
1201 instruction and ensures context syn <<
1202 exception return. <<
1203 129
1204 If unsure, say Y. !! 130 config APOLLO
1205 !! 131 bool "Apollo support"
1206 config FUJITSU_ERRATUM_010001 <<
1207 bool "Fujitsu-A64FX erratum E#010001: <<
1208 default y <<
1209 help 132 help
1210 This option adds a workaround for F !! 133 Say Y here if you want to run Linux on an MC680x0-based Apollo
1211 On some variants of the Fujitsu-A64 !! 134 Domain workstation such as the DN3500.
1212 accesses may cause undefined fault <<
1213 This fault occurs under a specific <<
1214 load/store instruction performs an <<
1215 case-1 TTBR0_EL1 with TCR_EL1.NFD0 <<
1216 case-2 TTBR0_EL2 with TCR_EL2.NFD0 <<
1217 case-3 TTBR1_EL1 with TCR_EL1.NFD1 <<
1218 case-4 TTBR1_EL2 with TCR_EL2.NFD1 <<
1219 135
1220 The workaround is to ensure these b !! 136 config VME
1221 The workaround only affects the Fuj !! 137 bool "VME (Motorola and BVM) support"
>> 138 help
>> 139 Say Y here if you want to build a kernel for a 680x0 based VME
>> 140 board. Boards currently supported include Motorola boards MVME147,
>> 141 MVME162, MVME166, MVME167, MVME172, and MVME177. BVME4000 and
>> 142 BVME6000 boards from BVM Ltd are also supported.
>> 143
>> 144 config MVME147
>> 145 bool "MVME147 support"
>> 146 depends on VME
>> 147 help
>> 148 Say Y to include support for early Motorola VME boards. This will
>> 149 build a kernel which can run on MVME147 single-board computers. If
>> 150 you select this option you will have to select the appropriate
>> 151 drivers for SCSI, Ethernet and serial ports later on.
>> 152
>> 153 config MVME16x
>> 154 bool "MVME162, 166 and 167 support"
>> 155 depends on VME
>> 156 help
>> 157 Say Y to include support for Motorola VME boards. This will build a
>> 158 kernel which can run on MVME162, MVME166, MVME167, MVME172, and
>> 159 MVME177 boards. If you select this option you will have to select
>> 160 the appropriate drivers for SCSI, Ethernet and serial ports later
>> 161 on.
>> 162
>> 163 config BVME6000
>> 164 bool "BVME4000 and BVME6000 support"
>> 165 depends on VME
>> 166 help
>> 167 Say Y to include support for VME boards from BVM Ltd. This will
>> 168 build a kernel which can run on BVME4000 and BVME6000 boards. If
>> 169 you select this option you will have to select the appropriate
>> 170 drivers for SCSI, Ethernet and serial ports later on.
>> 171
>> 172 config HP300
>> 173 bool "HP9000/300 support"
>> 174 help
>> 175 This option enables support for the HP9000/300 series of
>> 176 workstations. Support for these machines is still very experimental.
>> 177 If you plan to try to use the kernel on such a machine say Y here.
>> 178 Everybody else says N.
>> 179
>> 180 config DIO
>> 181 bool "DIO bus support"
>> 182 depends on HP300
>> 183 help
>> 184 Say Y here to enable support for the "DIO" expansion bus used in
>> 185 HP300 machines. If you are using such a system you almost certainly
>> 186 want this.
>> 187
>> 188 config SUN3X
>> 189 bool "Sun3x support"
>> 190 help
>> 191 This option enables support for the Sun 3x series of workstations.
>> 192 Be warned that this support is very experimental. You will also want
>> 193 to say Y to 68030 support and N to the other processors below.
>> 194 Note that Sun 3x kernels are not compatible with Sun 3 hardware.
>> 195 General Linux information on the Sun 3x series (now discontinued)
>> 196 is at <http://www.angelfire.com/ca2/tech68k/sun3.html>.
>> 197
>> 198 If you don't want to compile a kernel for a Sun 3x, say N.
>> 199
>> 200 config SUN3
>> 201 bool "Sun3 support"
>> 202 help
>> 203 This option enables support for the Sun 3 series of workstations
>> 204 (3/50, 3/60, 3/1xx, 3/2xx systems). Enabling this option requires
>> 205 that all other hardware types must be disabled, as Sun 3 kernels
>> 206 are incompatible with all other m68k targets (including Sun 3x!).
>> 207 Also, you will want to say Y to 68020 support and N to the other
>> 208 processors below.
>> 209
>> 210 If you don't want to compile a kernel exclusively for a Sun 3, say N.
>> 211
>> 212 config Q40
>> 213 bool "Q40/Q60 support"
>> 214 help
>> 215 The Q40 is a Motorola 68040-based successor to the Sinclair QL
>> 216 manufactured in Germany. There is an official Q40 home page at
>> 217 <http://www.q40.de/>. This option enables support for the Q40 and
>> 218 Q60. Select your CPU below. For 68LC060 don't forget to enable FPU
>> 219 emulation.
>> 220
>> 221 comment "Processor type"
>> 222
>> 223 config M68020
>> 224 bool "68020 support"
>> 225 help
>> 226 If you anticipate running this kernel on a computer with a MC68020
>> 227 processor, say Y. Otherwise, say N. Note that the 68020 requires a
>> 228 68851 MMU (Memory Management Unit) to run Linux/m68k, except on the
>> 229 Sun 3, which provides its own version.
>> 230
>> 231 config M68030
>> 232 bool "68030 support"
>> 233 help
>> 234 If you anticipate running this kernel on a computer with a MC68030
>> 235 processor, say Y. Otherwise, say N. Note that a MC68EC030 will not
>> 236 work, as it does not include an MMU (Memory Management Unit).
>> 237
>> 238 config M68040
>> 239 bool "68040 support"
>> 240 help
>> 241 If you anticipate running this kernel on a computer with a MC68LC040
>> 242 or MC68040 processor, say Y. Otherwise, say N. Note that an
>> 243 MC68EC040 will not work, as it does not include an MMU (Memory
>> 244 Management Unit).
>> 245
>> 246 config M68060
>> 247 bool "68060 support"
>> 248 help
>> 249 If you anticipate running this kernel on a computer with a MC68060
>> 250 processor, say Y. Otherwise, say N.
>> 251
>> 252 config M68KFPU_EMU
>> 253 bool "Math emulation support (EXPERIMENTAL)"
>> 254 depends on EXPERIMENTAL
>> 255 help
>> 256 At some point in the future, this will cause floating-point math
>> 257 instructions to be emulated by the kernel on machines that lack a
>> 258 floating-point math coprocessor. Thrill-seekers and chronically
>> 259 sleep-deprived psychotic hacker types can say Y now, everyone else
>> 260 should probably wait a while.
>> 261
>> 262 config M68KFPU_EMU_EXTRAPREC
>> 263 bool "Math emulation extra precision"
>> 264 depends on M68KFPU_EMU
>> 265 help
>> 266 The fpu uses normally a few bit more during calculations for
>> 267 correct rounding, the emulator can (often) do the same but this
>> 268 extra calculation can cost quite some time, so you can disable
>> 269 it here. The emulator will then "only" calculate with a 64 bit
>> 270 mantissa and round slightly incorrect, what is more then enough
>> 271 for normal usage.
>> 272
>> 273 config M68KFPU_EMU_ONLY
>> 274 bool "Math emulation only kernel"
>> 275 depends on M68KFPU_EMU
>> 276 help
>> 277 This option prevents any floating-point instructions from being
>> 278 compiled into the kernel, thereby the kernel doesn't save any
>> 279 floating point context anymore during task switches, so this
>> 280 kernel will only be usable on machines without a floating-point
>> 281 math coprocessor. This makes the kernel a bit faster as no tests
>> 282 needs to be executed whether a floating-point instruction in the
>> 283 kernel should be executed or not.
>> 284
>> 285 config ADVANCED
>> 286 bool "Advanced configuration options"
>> 287 ---help---
>> 288 This gives you access to some advanced options for the CPU. The
>> 289 defaults should be fine for most users, but these options may make
>> 290 it possible for you to improve performance somewhat if you know what
>> 291 you are doing.
>> 292
>> 293 Note that the answer to this question won't directly affect the
>> 294 kernel: saying N will just cause the configurator to skip all
>> 295 the questions about these options.
>> 296
>> 297 Most users should say N to this question.
>> 298
>> 299 config RMW_INSNS
>> 300 bool "Use read-modify-write instructions"
>> 301 depends on ADVANCED
>> 302 ---help---
>> 303 This allows to use certain instructions that work with indivisible
>> 304 read-modify-write bus cycles. While this is faster than the
>> 305 workaround of disabling interrupts, it can conflict with DMA
>> 306 ( = direct memory access) on many Amiga systems, and it is also said
>> 307 to destabilize other machines. It is very likely that this will
>> 308 cause serious problems on any Amiga or Atari Medusa if set. The only
>> 309 configuration where it should work are 68030-based Ataris, where it
>> 310 apparently improves performance. But you've been warned! Unless you
>> 311 really know what you are doing, say N. Try Y only if you're quite
>> 312 adventurous.
>> 313
>> 314 config SINGLE_MEMORY_CHUNK
>> 315 bool "Use one physical chunk of memory only"
>> 316 depends on ADVANCED && !SUN3
>> 317 help
>> 318 Ignore all but the first contiguous chunk of physical memory for VM
>> 319 purposes. This will save a few bytes kernel size and may speed up
>> 320 some operations. Say N if not sure.
>> 321
>> 322 config 060_WRITETHROUGH
>> 323 bool "Use write-through caching for 68060 supervisor accesses"
>> 324 depends on ADVANCED && M68060
>> 325 ---help---
>> 326 The 68060 generally uses copyback caching of recently accessed data.
>> 327 Copyback caching means that memory writes will be held in an on-chip
>> 328 cache and only written back to memory some time later. Saying Y
>> 329 here will force supervisor (kernel) accesses to use writethrough
>> 330 caching. Writethrough caching means that data is written to memory
>> 331 straight away, so that cache and memory data always agree.
>> 332 Writethrough caching is less efficient, but is needed for some
>> 333 drivers on 68060 based systems where the 68060 bus snooping signal
>> 334 is hardwired on. The 53c710 SCSI driver is known to suffer from
>> 335 this problem.
>> 336
>> 337 endmenu
>> 338
>> 339
>> 340 menu "General setup"
>> 341
>> 342 source "fs/Kconfig.binfmt"
>> 343
>> 344 config ZORRO
>> 345 bool "Amiga Zorro (AutoConfig) bus support"
>> 346 depends on AMIGA
>> 347 help
>> 348 This enables support for the Zorro bus in the Amiga. If you have
>> 349 expansion cards in your Amiga that conform to the Amiga
>> 350 AutoConfig(tm) specification, say Y, otherwise N. Note that even
>> 351 expansion cards that do not fit in the Zorro slots but fit in e.g.
>> 352 the CPU slot may fall in this category, so you have to say Y to let
>> 353 Linux use these.
>> 354
>> 355 config AMIGA_PCMCIA
>> 356 bool "Amiga 1200/600 PCMCIA support (EXPERIMENTAL)"
>> 357 depends on AMIGA && EXPERIMENTAL
>> 358 help
>> 359 Include support in the kernel for pcmcia on Amiga 1200 and Amiga
>> 360 600. If you intend to use pcmcia cards say Y; otherwise say N.
>> 361
>> 362 config STRAM_SWAP
>> 363 bool "Support for ST-RAM as swap space"
>> 364 depends on ATARI && BROKEN
>> 365 ---help---
>> 366 Some Atari 68k macines (including the 520STF and 1020STE) divide
>> 367 their addressible memory into ST and TT sections. The TT section
>> 368 (up to 512MB) is the main memory; the ST section (up to 4MB) is
>> 369 accessible to the built-in graphics board, runs slower, and is
>> 370 present mainly for backward compatibility with older machines.
>> 371
>> 372 This enables support for using (parts of) ST-RAM as swap space,
>> 373 instead of as normal system memory. This can first enhance system
>> 374 performance if you have lots of alternate RAM (compared to the size
>> 375 of ST-RAM), because executable code always will reside in faster
>> 376 memory. ST-RAM will remain as ultra-fast swap space. On the other
>> 377 hand, it allows much improved dynamic allocations of ST-RAM buffers
>> 378 for device driver modules (e.g. floppy, ACSI, SLM printer, DMA
>> 379 sound). The probability that such allocations at module load time
>> 380 fail is drastically reduced.
>> 381
>> 382 config STRAM_PROC
>> 383 bool "ST-RAM statistics in /proc"
>> 384 depends on ATARI
>> 385 help
>> 386 Say Y here to report ST-RAM usage statistics in /proc/stram. See
>> 387 the help for CONFIG_STRAM_SWAP for discussion of ST-RAM and its
>> 388 uses.
>> 389
>> 390 config HEARTBEAT
>> 391 bool "Use power LED as a heartbeat" if AMIGA || APOLLO || ATARI || MAC ||Q40
>> 392 default y if !AMIGA && !APOLLO && !ATARI && !MAC && !Q40 && HP300
>> 393 help
>> 394 Use the power-on LED on your machine as a load meter. The exact
>> 395 behavior is platform-dependent, but normally the flash frequency is
>> 396 a hyperbolic function of the 5-minute load average.
>> 397
>> 398 # We have a dedicated heartbeat LED. :-)
>> 399 config PROC_HARDWARE
>> 400 bool "/proc/hardware support"
>> 401 help
>> 402 Say Y here to support the /proc/hardware file, which gives you
>> 403 access to information about the machine you're running on,
>> 404 including the model, CPU, MMU, clock speed, BogoMIPS rating,
>> 405 and memory size.
>> 406
>> 407 config PARPORT
>> 408 tristate "Parallel port support (EXPERIMENTAL)"
>> 409 depends on EXPERIMENTAL
>> 410 ---help---
>> 411 If you want to use devices connected to your machine's parallel port
>> 412 (the connector at the computer with 25 holes), e.g. printer, ZIP
>> 413 drive, PLIP link (Parallel Line Internet Protocol is mainly used to
>> 414 create a mini network by connecting the parallel ports of two local
>> 415 machines) etc., then you need to say Y here; please read
>> 416 <file:Documentation/parport.txt> and
>> 417 <file:drivers/parport/BUGS-parport>.
>> 418
>> 419 For extensive information about drivers for many devices attaching
>> 420 to the parallel port see <http://www.torque.net/linux-pp.html> on
>> 421 the WWW.
>> 422
>> 423 It is possible to share a single parallel port among several devices
>> 424 and it is safe to compile all the corresponding drivers into the
>> 425 kernel. To compile parallel port support as a module, choose M here:
>> 426 the module will be called parport.
>> 427 If you have more than one parallel port and want to specify which
>> 428 port and IRQ to be used by this driver at module load time, take a
>> 429 look at <file:Documentation/parport.txt>.
>> 430
>> 431 If unsure, say Y.
>> 432
>> 433 config PARPORT_AMIGA
>> 434 tristate "Amiga builtin port"
>> 435 depends on AMIGA && PARPORT
>> 436 help
>> 437 Say Y here if you need support for the parallel port hardware on
>> 438 Amiga machines. This code is also available as a module (say M),
>> 439 called parport_amiga. If in doubt, saying N is the safe plan.
>> 440
>> 441 config PARPORT_MFC3
>> 442 tristate "Multiface III parallel port"
>> 443 depends on ZORRO && PARPORT
>> 444 help
>> 445 Say Y here if you need parallel port support for the MFC3 card.
>> 446 This code is also available as a module (say M), called
>> 447 parport_mfc3. If in doubt, saying N is the safe plan.
1222 448
1223 If unsure, say Y. !! 449 config PARPORT_PC
1224 !! 450 bool
1225 config HISILICON_ERRATUM_161600802 !! 451 depends on Q40 && PARPORT
1226 bool "Hip07 161600802: Erroneous redi <<
1227 default y 452 default y
1228 help !! 453 ---help---
1229 The HiSilicon Hip07 SoC uses the wr !! 454 You should say Y here if you have a PC-style parallel port. All IBM
1230 when issued ITS commands such as VM !! 455 PC compatible computers and some Alphas have PC-style parallel
1231 a 128kB offset to be applied to the !! 456 ports.
>> 457
>> 458 To compile this driver as a module, choose M here: the
>> 459 module will be called parport_pc.
1232 460
1233 If unsure, say Y. 461 If unsure, say Y.
1234 462
1235 config QCOM_FALKOR_ERRATUM_1003 !! 463 config PARPORT_ATARI
1236 bool "Falkor E1003: Incorrect transla !! 464 tristate "Atari builtin port"
1237 default y !! 465 depends on ATARI && PARPORT
1238 help !! 466 help
1239 On Falkor v1, an incorrect ASID may !! 467 Say Y here if you need support for the parallel port hardware on
1240 and BADDR are changed together in T !! 468 Atari machines. This code is also available as a module (say M),
1241 in TTBR1_EL1, this situation only o !! 469 called parport_atari. If in doubt, saying N is the safe plan.
1242 then only for entries in the walk c !! 470
1243 is unchanged. Work around the errat !! 471 config PRINTER
1244 entries for the trampoline before e !! 472 tristate "Parallel printer support"
>> 473 depends on PARPORT
>> 474 ---help---
>> 475 If you intend to attach a printer to the parallel port of your Linux
>> 476 box (as opposed to using a serial printer; if the connector at the
>> 477 printer has 9 or 25 holes ["female"], then it's serial), say Y.
>> 478 Also read the Printing-HOWTO, available from
>> 479 <http://www.tldp.org/docs.html#howto>.
>> 480
>> 481 It is possible to share one parallel port among several devices
>> 482 (e.g. printer and ZIP drive) and it is safe to compile the
>> 483 corresponding drivers into the kernel.
>> 484 To compile this driver as a module, choose M here and read
>> 485 <file:Documentation/parport.txt>. The module will be called lp.
>> 486
>> 487 If you have several parallel ports, you can specify which ports to
>> 488 use with the "lp" kernel command line option. (Try "man bootparam"
>> 489 or see the documentation of your boot loader (lilo or loadlin) about
>> 490 how to pass options to the kernel at boot time.) The syntax of the
>> 491 "lp" command line option can be found in <file:drivers/char/lp.c>.
>> 492
>> 493 If you have more than 8 printers, you need to increase the LP_NO
>> 494 macro in lp.c and the PARPORT_MAX macro in parport.h.
>> 495
>> 496 config PARPORT_1284
>> 497 bool "IEEE 1284 transfer modes"
>> 498 depends on PRINTER
>> 499 help
>> 500 If you have a printer that supports status readback or device ID, or
>> 501 want to use a device that uses enhanced parallel port transfer modes
>> 502 such as EPP and ECP, say Y here to enable advanced IEEE 1284
>> 503 transfer modes. Also say Y if you want device ID information to
>> 504 appear in /proc/sys/dev/parport/*/autoprobe*. It is safe to say N.
1245 505
1246 config QCOM_FALKOR_ERRATUM_1009 !! 506 config ISA
1247 bool "Falkor E1009: Prematurely compl !! 507 bool
>> 508 depends on Q40 || AMIGA_PCMCIA || GG2
1248 default y 509 default y
1249 select ARM64_WORKAROUND_REPEAT_TLBI <<
1250 help 510 help
1251 On Falkor v1, the CPU may premature !! 511 Find out whether you have ISA slots on your motherboard. ISA is the
1252 TLBI xxIS invalidate maintenance op !! 512 name of a bus system, i.e. the way the CPU talks to the other stuff
1253 one more time to fix the issue. !! 513 inside your box. Other bus systems are PCI, EISA, MicroChannel
>> 514 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
>> 515 newer boards don't support it. If you have ISA, say Y, otherwise N.
1254 516
1255 If unsure, say Y. !! 517 config GENERIC_ISA_DMA
1256 !! 518 bool
1257 config QCOM_QDF2400_ERRATUM_0065 !! 519 depends on Q40 || AMIGA_PCMCIA || GG2
1258 bool "QDF2400 E0065: Incorrect GITS_T <<
1259 default y 520 default y
1260 help <<
1261 On Qualcomm Datacenter Technologies <<
1262 ITE size incorrectly. The GITS_TYPE <<
1263 been indicated as 16Bytes (0xf), no <<
1264 <<
1265 If unsure, say Y. <<
1266 521
1267 config QCOM_FALKOR_ERRATUM_E1041 !! 522 source "drivers/pci/Kconfig"
1268 bool "Falkor E1041: Speculative instr <<
1269 default y <<
1270 help <<
1271 Falkor CPU may speculatively fetch <<
1272 memory location when MMU translatio <<
1273 to SCTLR_ELn[M]=0. Prefix an ISB in <<
1274 523
1275 If unsure, say Y. !! 524 source "drivers/zorro/Kconfig"
1276 525
1277 config NVIDIA_CARMEL_CNP_ERRATUM !! 526 if Q40
1278 bool "NVIDIA Carmel CNP: CNP on Carme !! 527 source "drivers/pnp/Kconfig"
1279 default y !! 528 endif
1280 help !! 529
1281 If CNP is enabled on Carmel cores, !! 530 endmenu
1282 invalidate shared TLB entries insta !! 531
1283 on standard ARM cores. !! 532 source "drivers/base/Kconfig"
>> 533
>> 534 source "drivers/mtd/Kconfig"
>> 535
>> 536 source "drivers/block/Kconfig"
>> 537
>> 538 source "drivers/md/Kconfig"
>> 539
>> 540 source "drivers/input/Kconfig"
>> 541
>> 542 source "drivers/ide/Kconfig"
>> 543
>> 544 source "drivers/scsi/Kconfig"
>> 545
>> 546 source "net/Kconfig"
>> 547
>> 548
>> 549 menu "Character devices"
>> 550
>> 551 config SERIAL
>> 552 tristate "Q40 Standard/generic serial support" if Q40
>> 553 default DN_SERIAL if APOLLO
>> 554 ---help---
>> 555 This selects whether you want to include the driver for the standard
>> 556 serial ports. The standard answer is Y. People who might say N
>> 557 here are those that are setting up dedicated Ethernet WWW/FTP
>> 558 servers, or users that have one of the various bus mice instead of a
>> 559 serial mouse and don't intend to use their machine's standard serial
>> 560 port for anything. (Note that the Cyclades and Stallion multi
>> 561 serial port drivers do not need this driver built in for them to
>> 562 work.)
>> 563
>> 564 To compile this driver as a module, choose M here: the
>> 565 module will be called serial.
>> 566 [WARNING: Do not compile this driver as a module if you are using
>> 567 non-standard serial ports, since the configuration information will
>> 568 be lost when the driver is unloaded. This limitation may be lifted
>> 569 in the future.]
>> 570
>> 571 BTW1: If you have a mouseman serial mouse which is not recognized by
>> 572 the X window system, try running gpm first.
>> 573
>> 574 BTW2: If you intend to use a software modem (also called Winmodem)
>> 575 under Linux, forget it. These modems are crippled and require
>> 576 proprietary drivers which are only available under Windows.
>> 577
>> 578 Most people will say Y or M here, so that they can use serial mice,
>> 579 modems and similar devices connecting to the standard serial ports.
>> 580
>> 581 config SERIAL_EXTENDED
>> 582 bool "Extended dumb serial driver options"
>> 583 depends on SERIAL=y
>> 584 help
>> 585 If you wish to use any non-standard features of the standard "dumb"
>> 586 driver, say Y here. This includes HUB6 support, shared serial
>> 587 interrupts, special multiport support, support for more than the
>> 588 four COM 1/2/3/4 boards, etc.
>> 589
>> 590 Note that the answer to this question won't directly affect the
>> 591 kernel: saying N will just cause the configurator to skip all
>> 592 the questions about serial driver options. If unsure, say N.
>> 593
>> 594 config SERIAL_MANY_PORTS
>> 595 bool "Support more than 4 serial ports"
>> 596 depends on SERIAL_EXTENDED
>> 597 help
>> 598 Say Y here if you have dumb serial boards other than the four
>> 599 standard COM 1/2/3/4 ports. This may happen if you have an AST
>> 600 FourPort, Accent Async, Boca (read the Boca mini-HOWTO, available
>> 601 from <http://www.tldp.org/docs.html#howto>), or other custom
>> 602 serial port hardware which acts similar to standard serial port
>> 603 hardware. If you only use the standard COM 1/2/3/4 ports, you can
>> 604 say N here to save some memory. You can also say Y if you have an
>> 605 "intelligent" multiport card such as Cyclades, Digiboards, etc.
>> 606
>> 607 config SERIAL_SHARE_IRQ
>> 608 bool "Support for sharing serial interrupts"
>> 609 depends on SERIAL_EXTENDED
>> 610 help
>> 611 Some serial boards have hardware support which allows multiple dumb
>> 612 serial ports on the same board to share a single IRQ. To enable
>> 613 support for this in the serial driver, say Y here.
>> 614
>> 615 config SERIAL_MULTIPORT
>> 616 bool "Support special multiport boards"
>> 617 depends on SERIAL_EXTENDED
>> 618 help
>> 619 Some multiport serial ports have special ports which are used to
>> 620 signal when there are any serial ports on the board which need
>> 621 servicing. Say Y here to enable the serial driver to take advantage
>> 622 of those special I/O ports.
>> 623
>> 624 config HUB6
>> 625 bool "Support the Bell Technologies HUB6 card"
>> 626 depends on SERIAL_EXTENDED
>> 627 help
>> 628 Say Y here to enable support in the dumb serial driver to support
>> 629 the HUB6 card.
>> 630
>> 631 config VT
>> 632 bool "Virtual terminal"
>> 633 ---help---
>> 634 If you say Y here, you will get support for terminal devices with
>> 635 display and keyboard devices. These are called "virtual" because you
>> 636 can run several virtual terminals (also called virtual consoles) on
>> 637 one physical terminal. This is rather useful, for example one
>> 638 virtual terminal can collect system messages and warnings, another
>> 639 one can be used for a text-mode user session, and a third could run
>> 640 an X session, all in parallel. Switching between virtual terminals
>> 641 is done with certain key combinations, usually Alt-<function key>.
>> 642
>> 643 The setterm command ("man setterm") can be used to change the
>> 644 properties (such as colors or beeping) of a virtual terminal. The
>> 645 man page console_codes(4) ("man console_codes") contains the special
>> 646 character sequences that can be used to change those properties
>> 647 directly. The fonts used on virtual terminals can be changed with
>> 648 the setfont ("man setfont") command and the key bindings are defined
>> 649 with the loadkeys ("man loadkeys") command.
>> 650
>> 651 You need at least one virtual terminal device in order to make use
>> 652 of your keyboard and monitor. Therefore, only people configuring an
>> 653 embedded system would want to say N here in order to save some
>> 654 memory; the only way to log into such a system is then via a serial
>> 655 or network connection.
>> 656
>> 657 If unsure, say Y, or else you won't be able to do much with your new
>> 658 shiny Linux system :-)
>> 659
>> 660 config VT_CONSOLE
>> 661 bool "Support for console on virtual terminal"
>> 662 depends on VT
>> 663 ---help---
>> 664 The system console is the device which receives all kernel messages
>> 665 and warnings and which allows logins in single user mode. If you
>> 666 answer Y here, a virtual terminal (the device used to interact with
>> 667 a physical terminal) can be used as system console. This is the most
>> 668 common mode of operations, so you should say Y here unless you want
>> 669 the kernel messages be output only to a serial port (in which case
>> 670 you should say Y to "Console on serial port", below).
>> 671
>> 672 If you do say Y here, by default the currently visible virtual
>> 673 terminal (/dev/tty0) will be used as system console. You can change
>> 674 that with a kernel command line option such as "console=tty3" which
>> 675 would use the third virtual terminal as system console. (Try "man
>> 676 bootparam" or see the documentation of your boot loader (lilo or
>> 677 loadlin) about how to pass options to the kernel at boot time.)
1284 678
1285 If unsure, say Y. 679 If unsure, say Y.
1286 680
1287 config ROCKCHIP_ERRATUM_3588001 !! 681 config HW_CONSOLE
1288 bool "Rockchip 3588001: GIC600 can no !! 682 bool
>> 683 depends on VT
1289 default y 684 default y
1290 help <<
1291 The Rockchip RK3588 GIC600 SoC inte <<
1292 This means, that its sharability fe <<
1293 is supported by the IP itself. <<
1294 685
1295 If unsure, say Y. !! 686 config NVRAM
1296 !! 687 bool
1297 config SOCIONEXT_SYNQUACER_PREITS !! 688 depends on ATARI
1298 bool "Socionext Synquacer: Workaround <<
1299 default y 689 default y
1300 help !! 690 ---help---
1301 Socionext Synquacer SoCs implement !! 691 If you say Y here and create a character special file /dev/nvram
1302 MSI doorbell writes with non-zero v !! 692 with major number 10 and minor number 144 using mknod ("man mknod"),
1303 !! 693 you get read and write access to the 50 bytes of non-volatile memory
1304 If unsure, say Y. !! 694 in the real time clock (RTC), which is contained in every PC and
1305 !! 695 most Ataris.
1306 endmenu # "ARM errata workarounds via the alt !! 696
1307 !! 697 This memory is conventionally called "CMOS RAM" on PCs and "NVRAM"
1308 choice !! 698 on Ataris. /dev/nvram may be used to view settings there, or to
1309 prompt "Page size" !! 699 change them (with some utility). It could also be used to frequently
1310 default ARM64_4K_PAGES !! 700 save a few bits of very important data that may not be lost over
1311 help !! 701 power-off and for which writing to disk is too insecure. Note
1312 Page size (translation granule) con !! 702 however that most NVRAM space in a PC belongs to the BIOS and you
1313 !! 703 should NEVER idly tamper with it. See Ralf Brown's interrupt list
1314 config ARM64_4K_PAGES !! 704 for a guide to the use of CMOS bytes by your BIOS.
1315 bool "4KB" !! 705
1316 select HAVE_PAGE_SIZE_4KB !! 706 On Atari machines, /dev/nvram is always configured and does not need
1317 help !! 707 to be selected.
1318 This feature enables 4KB pages supp !! 708
1319 !! 709 To compile this driver as a module, choose M here: the
1320 config ARM64_16K_PAGES !! 710 module will be called nvram.
1321 bool "16KB" !! 711
1322 select HAVE_PAGE_SIZE_16KB !! 712 config ATARI_MFPSER
1323 help !! 713 tristate "Atari MFP serial support"
1324 The system will use 16KB pages supp !! 714 depends on ATARI
1325 requires applications compiled with !! 715 ---help---
1326 aligned segments. !! 716 If you like to use the MFP serial ports ("Modem1", "Serial1") under
1327 !! 717 Linux, say Y. The driver equally supports all kinds of MFP serial
1328 config ARM64_64K_PAGES !! 718 ports and automatically detects whether Serial1 is available.
1329 bool "64KB" !! 719
1330 select HAVE_PAGE_SIZE_64KB !! 720 To compile this driver as a module, choose M here.
1331 help !! 721
1332 This feature enables 64KB pages sup !! 722 Note for Falcon users: You also have an MFP port, it's just not
1333 allowing only two levels of page ta !! 723 wired to the outside... But you could use the port under Linux.
1334 look-up. AArch32 emulation requires !! 724
1335 with 64K aligned segments. !! 725 config ATARI_SCC
1336 !! 726 tristate "Atari SCC serial support"
1337 endchoice !! 727 depends on ATARI
1338 !! 728 ---help---
1339 choice !! 729 If you have serial ports based on a Zilog SCC chip (Modem2, Serial2,
1340 prompt "Virtual address space size" !! 730 LAN) and like to use them under Linux, say Y. All built-in SCC's are
1341 default ARM64_VA_BITS_52 !! 731 supported (TT, MegaSTE, Falcon), and also the ST-ESCC. If you have
1342 help !! 732 two connectors for channel A (Serial2 and LAN), they are visible as
1343 Allows choosing one of multiple pos !! 733 two separate devices.
1344 space sizes. The level of translati !! 734
1345 a combination of page size and virt !! 735 To compile this driver as a module, choose M here.
1346 !! 736
1347 config ARM64_VA_BITS_36 !! 737 config ATARI_SCC_DMA
1348 bool "36-bit" if EXPERT !! 738 bool "Atari SCC serial DMA support"
1349 depends on PAGE_SIZE_16KB !! 739 depends on ATARI_SCC
1350 !! 740 help
1351 config ARM64_VA_BITS_39 !! 741 This enables DMA support for receiving data on channel A of the SCC.
1352 bool "39-bit" !! 742 If you have a TT you may say Y here and read
1353 depends on PAGE_SIZE_4KB !! 743 drivers/char/atari_SCC.README. All other users should say N here,
>> 744 because only the TT has SCC-DMA, even if your machine keeps claiming
>> 745 so at boot time.
>> 746
>> 747 config ATARI_MIDI
>> 748 tristate "Atari MIDI serial support"
>> 749 depends on ATARI
>> 750 help
>> 751 If you want to use your Atari's MIDI port in Linux, say Y.
>> 752
>> 753 To compile this driver as a module, choose M here.
>> 754
>> 755 config ATARI_DSP56K
>> 756 tristate "Atari DSP56k support (EXPERIMENTAL)"
>> 757 depends on ATARI && EXPERIMENTAL
>> 758 help
>> 759 If you want to be able to use the DSP56001 in Falcons, say Y. This
>> 760 driver is still experimental, and if you don't know what it is, or
>> 761 if you don't have this processor, just say N.
>> 762
>> 763 To compile this driver as a module, choose M here.
>> 764
>> 765 config AMIGA_BUILTIN_SERIAL
>> 766 tristate "Amiga builtin serial support"
>> 767 depends on AMIGA
>> 768 help
>> 769 If you want to use your Amiga's built-in serial port in Linux,
>> 770 answer Y.
>> 771
>> 772 To compile this driver as a module, choose M here.
>> 773
>> 774 config WHIPPET_SERIAL
>> 775 tristate "Hisoft Whippet PCMCIA serial support"
>> 776 depends on AMIGA_PCMCIA
>> 777 help
>> 778 HiSoft has a web page at <http://www.hisoft.co.uk/>, but there
>> 779 is no listing for the Whippet in their Amiga section.
>> 780
>> 781 config MULTIFACE_III_TTY
>> 782 tristate "Multiface Card III serial support"
>> 783 depends on AMIGA
>> 784 help
>> 785 If you want to use a Multiface III card's serial port in Linux,
>> 786 answer Y.
>> 787
>> 788 To compile this driver as a module, choose M here.
>> 789
>> 790 config A2232
>> 791 tristate "Commodore A2232 serial support (EXPERIMENTAL)"
>> 792 depends on AMIGA && EXPERIMENTAL
>> 793 ---help---
>> 794 This option supports the 2232 7-port serial card shipped with the
>> 795 Amiga 2000 and other Zorro-bus machines, dating from 1989. At
>> 796 a max of 19,200 bps, the ports are served by a 6551 ACIA UART chip
>> 797 each, plus a 8520 CIA, and a master 6502 CPU and buffer as well. The
>> 798 ports were connected with 8 pin DIN connectors on the card bracket,
>> 799 for which 8 pin to DB25 adapters were supplied. The card also had
>> 800 jumpers internally to toggle various pinning configurations.
>> 801
>> 802 This driver can be built as a module; but then "generic_serial"
>> 803 will also be built as a module. This has to be loaded before
>> 804 "ser_a2232". If you want to do this, answer M here.
>> 805
>> 806 config GVPIOEXT
>> 807 tristate "GVP IO-Extender support"
>> 808 depends on PARPORT=n && ZORRO
>> 809 help
>> 810 If you want to use a GVP IO-Extender serial card in Linux, say Y.
>> 811 Otherwise, say N.
>> 812
>> 813 config GVPIOEXT_LP
>> 814 tristate "GVP IO-Extender parallel printer support"
>> 815 depends on GVPIOEXT
>> 816 help
>> 817 Say Y to enable driving a printer from the parallel port on your
>> 818 GVP IO-Extender card, N otherwise.
>> 819
>> 820 config GVPIOEXT_PLIP
>> 821 tristate "GVP IO-Extender PLIP support"
>> 822 depends on GVPIOEXT
>> 823 help
>> 824 Say Y to enable doing IP over the parallel port on your GVP
>> 825 IO-Extender card, N otherwise.
>> 826
>> 827 config MAC_SCC
>> 828 tristate "Macintosh serial support"
>> 829 depends on MAC
>> 830
>> 831 config ADB
>> 832 bool "Apple Desktop Bus (ADB) support"
>> 833 depends on MAC
>> 834 help
>> 835 Apple Desktop Bus (ADB) support is for support of devices which
>> 836 are connected to an ADB port. ADB devices tend to have 4 pins.
>> 837 If you have an Apple Macintosh prior to the iMac, or a
>> 838 "Blue and White G3", you probably want to say Y here. Otherwise
>> 839 say N.
>> 840
>> 841 config ADB_MACII
>> 842 bool "Include Mac II ADB driver"
>> 843 depends on ADB
>> 844 help
>> 845 Say Y here if want your kernel to support Macintosh systems that use
>> 846 the Mac II style ADB. This includes the II, IIx, IIcx, SE/30, IIci,
>> 847 Quadra 610, Quadra 650, Quadra 700, Quadra 800, Centris 610 and
>> 848 Centris 650.
>> 849
>> 850 config ADB_MACIISI
>> 851 bool "Include Mac IIsi ADB driver"
>> 852 depends on ADB
>> 853 help
>> 854 Say Y here if want your kernel to support Macintosh systems that use
>> 855 the Mac IIsi style ADB. This includes the IIsi, IIvi, IIvx, Classic
>> 856 II, LC, LC II, LC III, Performa 460, and the Performa 600.
>> 857
>> 858 config ADB_CUDA
>> 859 bool "Include CUDA ADB driver"
>> 860 depends on ADB
>> 861 help
>> 862 This provides support for CUDA based Power Macintosh systems. This
>> 863 includes most OldWorld PowerMacs, the first generation iMacs, the
>> 864 Blue&White G3 and the Yikes G4 (PCI Graphics). All later models
>> 865 should use CONFIG_ADB_PMU instead.
>> 866
>> 867 If unsure say Y.
>> 868
>> 869 config ADB_IOP
>> 870 bool "Include IOP (IIfx/Quadra 9x0) ADB driver"
>> 871 depends on ADB
>> 872 help
>> 873 The I/O Processor (IOP) is an Apple custom IC designed to provide
>> 874 intelligent support for I/O controllers. It is described at
>> 875 <http://www.angelfire.com/ca2/dev68k/iopdesc.html> to enable direct
>> 876 support for it, say 'Y' here.
>> 877
>> 878 config ADB_PMU68K
>> 879 bool "Include PMU (Powerbook) ADB driver"
>> 880 depends on ADB
>> 881 help
>> 882 Say Y here if want your kernel to support the m68k based Powerbooks.
>> 883 This includes the PowerBook 140, PowerBook 145, PowerBook 150,
>> 884 PowerBook 160, PowerBook 165, PowerBook 165c, PowerBook 170,
>> 885 PowerBook 180, PowerBook, 180c, PowerBook 190cs, PowerBook 520,
>> 886 PowerBook Duo 210, PowerBook Duo 230, PowerBook Duo 250,
>> 887 PowerBook Duo 270c, PowerBook Duo 280 and PowerBook Duo 280c.
>> 888
>> 889 config INPUT_ADBHID
>> 890 bool "Use input layer for ADB devices"
>> 891 depends on MAC && INPUT=y
>> 892 ---help---
>> 893 Say Y here if you want to have ADB (Apple Desktop Bus) HID devices
>> 894 such as keyboards, mice, joysticks, or graphic tablets handled by
>> 895 the input layer. If you say Y here, make sure to say Y to the
>> 896 corresponding drivers "Keyboard support" (CONFIG_INPUT_KEYBDEV),
>> 897 "Mouse Support" (CONFIG_INPUT_MOUSEDEV) and "Event interface
>> 898 support" (CONFIG_INPUT_EVDEV) as well.
1354 899
1355 config ARM64_VA_BITS_42 !! 900 If you say N here, you still have the option of using the old ADB
1356 bool "42-bit" !! 901 keyboard and mouse drivers.
1357 depends on PAGE_SIZE_64KB <<
1358 <<
1359 config ARM64_VA_BITS_47 <<
1360 bool "47-bit" <<
1361 depends on PAGE_SIZE_16KB <<
1362 <<
1363 config ARM64_VA_BITS_48 <<
1364 bool "48-bit" <<
1365 <<
1366 config ARM64_VA_BITS_52 <<
1367 bool "52-bit" <<
1368 depends on ARM64_PAN || !ARM64_SW_TTB <<
1369 help <<
1370 Enable 52-bit virtual addressing fo <<
1371 requested via a hint to mmap(). The <<
1372 virtual addresses for its own mappi <<
1373 this feature is available, otherwis <<
1374 <<
1375 NOTE: Enabling 52-bit virtual addre <<
1376 ARMv8.3 Pointer Authentication will <<
1377 reduced from 7 bits to 3 bits, whic <<
1378 impact on its susceptibility to bru <<
1379 <<
1380 If unsure, select 48-bit virtual ad <<
1381 <<
1382 endchoice <<
1383 <<
1384 config ARM64_FORCE_52BIT <<
1385 bool "Force 52-bit virtual addresses <<
1386 depends on ARM64_VA_BITS_52 && EXPERT <<
1387 help <<
1388 For systems with 52-bit userspace V <<
1389 to maintain compatibility with olde <<
1390 unless a hint is supplied to mmap. <<
1391 <<
1392 This configuration option disables <<
1393 forces all userspace addresses to b <<
1394 should only enable this configurati <<
1395 memory management code. If unsure s <<
1396 <<
1397 config ARM64_VA_BITS <<
1398 int <<
1399 default 36 if ARM64_VA_BITS_36 <<
1400 default 39 if ARM64_VA_BITS_39 <<
1401 default 42 if ARM64_VA_BITS_42 <<
1402 default 47 if ARM64_VA_BITS_47 <<
1403 default 48 if ARM64_VA_BITS_48 <<
1404 default 52 if ARM64_VA_BITS_52 <<
1405 <<
1406 choice <<
1407 prompt "Physical address space size" <<
1408 default ARM64_PA_BITS_48 <<
1409 help <<
1410 Choose the maximum physical address <<
1411 support. <<
1412 <<
1413 config ARM64_PA_BITS_48 <<
1414 bool "48-bit" <<
1415 depends on ARM64_64K_PAGES || !ARM64_ <<
1416 <<
1417 config ARM64_PA_BITS_52 <<
1418 bool "52-bit" <<
1419 depends on ARM64_64K_PAGES || ARM64_V <<
1420 depends on ARM64_PAN || !ARM64_SW_TTB <<
1421 help <<
1422 Enable support for a 52-bit physica <<
1423 part of the ARMv8.2-LPA extension. <<
1424 <<
1425 With this enabled, the kernel will <<
1426 do not support ARMv8.2-LPA, but wit <<
1427 minor performance overhead). <<
1428 <<
1429 endchoice <<
1430 <<
1431 config ARM64_PA_BITS <<
1432 int <<
1433 default 48 if ARM64_PA_BITS_48 <<
1434 default 52 if ARM64_PA_BITS_52 <<
1435 <<
1436 config ARM64_LPA2 <<
1437 def_bool y <<
1438 depends on ARM64_PA_BITS_52 && !ARM64 <<
1439 <<
1440 choice <<
1441 prompt "Endianness" <<
1442 default CPU_LITTLE_ENDIAN <<
1443 help <<
1444 Select the endianness of data acces <<
1445 applications will need to be compil <<
1446 that is selected here. <<
1447 <<
1448 config CPU_BIG_ENDIAN <<
1449 bool "Build big-endian kernel" <<
1450 # https://github.com/llvm/llvm-projec <<
1451 depends on AS_IS_GNU || AS_VERSION >= <<
1452 help <<
1453 Say Y if you plan on running a kern <<
1454 <<
1455 config CPU_LITTLE_ENDIAN <<
1456 bool "Build little-endian kernel" <<
1457 help <<
1458 Say Y if you plan on running a kern <<
1459 This is usually the case for distri <<
1460 <<
1461 endchoice <<
1462 <<
1463 config SCHED_MC <<
1464 bool "Multi-core scheduler support" <<
1465 help <<
1466 Multi-core scheduler support improv <<
1467 making when dealing with multi-core <<
1468 increased overhead in some places. <<
1469 <<
1470 config SCHED_CLUSTER <<
1471 bool "Cluster scheduler support" <<
1472 help <<
1473 Cluster scheduler support improves <<
1474 making when dealing with machines t <<
1475 Cluster usually means a couple of C <<
1476 by sharing mid-level caches, last-l <<
1477 busses. <<
1478 <<
1479 config SCHED_SMT <<
1480 bool "SMT scheduler support" <<
1481 help <<
1482 Improves the CPU scheduler's decisi <<
1483 MultiThreading at a cost of slightl <<
1484 places. If unsure say N here. <<
1485 <<
1486 config NR_CPUS <<
1487 int "Maximum number of CPUs (2-4096)" <<
1488 range 2 4096 <<
1489 default "512" <<
1490 <<
1491 config HOTPLUG_CPU <<
1492 bool "Support for hot-pluggable CPUs" <<
1493 select GENERIC_IRQ_MIGRATION <<
1494 help <<
1495 Say Y here to experiment with turni <<
1496 can be controlled through /sys/devi <<
1497 <<
1498 # Common NUMA Features <<
1499 config NUMA <<
1500 bool "NUMA Memory Allocation and Sche <<
1501 select GENERIC_ARCH_NUMA <<
1502 select OF_NUMA <<
1503 select HAVE_SETUP_PER_CPU_AREA <<
1504 select NEED_PER_CPU_EMBED_FIRST_CHUNK <<
1505 select NEED_PER_CPU_PAGE_FIRST_CHUNK <<
1506 select USE_PERCPU_NUMA_NODE_ID <<
1507 help <<
1508 Enable NUMA (Non-Uniform Memory Acc <<
1509 <<
1510 The kernel will try to allocate mem <<
1511 local memory of the CPU and add som <<
1512 NUMA awareness to the kernel. <<
1513 <<
1514 config NODES_SHIFT <<
1515 int "Maximum NUMA Nodes (as a power o <<
1516 range 1 10 <<
1517 default "4" <<
1518 depends on NUMA <<
1519 help <<
1520 Specify the maximum number of NUMA <<
1521 system. Increases memory reserved <<
1522 <<
1523 source "kernel/Kconfig.hz" <<
1524 <<
1525 config ARCH_SPARSEMEM_ENABLE <<
1526 def_bool y <<
1527 select SPARSEMEM_VMEMMAP_ENABLE <<
1528 select SPARSEMEM_VMEMMAP <<
1529 <<
1530 config HW_PERF_EVENTS <<
1531 def_bool y <<
1532 depends on ARM_PMU <<
1533 <<
1534 # Supported by clang >= 7.0 or GCC >= 12.0.0 <<
1535 config CC_HAVE_SHADOW_CALL_STACK <<
1536 def_bool $(cc-option, -fsanitize=shad <<
1537 <<
1538 config PARAVIRT <<
1539 bool "Enable paravirtualization code" <<
1540 help <<
1541 This changes the kernel so it can m <<
1542 under a hypervisor, potentially imp <<
1543 over full virtualization. <<
1544 <<
1545 config PARAVIRT_TIME_ACCOUNTING <<
1546 bool "Paravirtual steal time accounti <<
1547 select PARAVIRT <<
1548 help <<
1549 Select this option to enable fine g <<
1550 accounting. Time spent executing ot <<
1551 the current vCPU is discounted from <<
1552 that, there can be a small performa <<
1553 <<
1554 If in doubt, say N here. <<
1555 <<
1556 config ARCH_SUPPORTS_KEXEC <<
1557 def_bool PM_SLEEP_SMP <<
1558 <<
1559 config ARCH_SUPPORTS_KEXEC_FILE <<
1560 def_bool y <<
1561 <<
1562 config ARCH_SELECTS_KEXEC_FILE <<
1563 def_bool y <<
1564 depends on KEXEC_FILE <<
1565 select HAVE_IMA_KEXEC if IMA <<
1566 <<
1567 config ARCH_SUPPORTS_KEXEC_SIG <<
1568 def_bool y <<
1569 <<
1570 config ARCH_SUPPORTS_KEXEC_IMAGE_VERIFY_SIG <<
1571 def_bool y <<
1572 <<
1573 config ARCH_DEFAULT_KEXEC_IMAGE_VERIFY_SIG <<
1574 def_bool y <<
1575 <<
1576 config ARCH_SUPPORTS_CRASH_DUMP <<
1577 def_bool y <<
1578 <<
1579 config ARCH_HAS_GENERIC_CRASHKERNEL_RESERVATI <<
1580 def_bool CRASH_RESERVE <<
1581 <<
1582 config TRANS_TABLE <<
1583 def_bool y <<
1584 depends on HIBERNATION || KEXEC_CORE <<
1585 <<
1586 config XEN_DOM0 <<
1587 def_bool y <<
1588 depends on XEN <<
1589 <<
1590 config XEN <<
1591 bool "Xen guest support on ARM64" <<
1592 depends on ARM64 && OF <<
1593 select SWIOTLB_XEN <<
1594 select PARAVIRT <<
1595 help <<
1596 Say Y if you want to run Linux in a <<
1597 <<
1598 # include/linux/mmzone.h requires the followi <<
1599 # <<
1600 # MAX_PAGE_ORDER + PAGE_SHIFT <= SECTION_SI <<
1601 # <<
1602 # so the maximum value of MAX_PAGE_ORDER is S <<
1603 # <<
1604 # | SECTION_SIZE_BITS | PAGE_SHIFT | m <<
1605 # ----+-------------------+--------------+--- <<
1606 # 4K | 27 | 12 | <<
1607 # 16K | 27 | 14 | <<
1608 # 64K | 29 | 16 | <<
1609 config ARCH_FORCE_MAX_ORDER <<
1610 int <<
1611 default "13" if ARM64_64K_PAGES <<
1612 default "11" if ARM64_16K_PAGES <<
1613 default "10" <<
1614 help <<
1615 The kernel page allocator limits th <<
1616 contiguous allocations. The limit i <<
1617 defines the maximal power of two of <<
1618 allocated as a single contiguous bl <<
1619 overriding the default setting when <<
1620 large blocks of physically contiguo <<
1621 <<
1622 The maximal size of allocation cann <<
1623 section, so the value of MAX_PAGE_O <<
1624 <<
1625 MAX_PAGE_ORDER + PAGE_SHIFT <= SE <<
1626 <<
1627 Don't change if unsure. <<
1628 <<
1629 config UNMAP_KERNEL_AT_EL0 <<
1630 bool "Unmap kernel when running in us <<
1631 default y <<
1632 help <<
1633 Speculation attacks against some hi <<
1634 be used to bypass MMU permission ch <<
1635 userspace. This can be defended aga <<
1636 when running in userspace, mapping <<
1637 via a trampoline page in the vector <<
1638 902
1639 If unsure, say Y. 903 If unsure, say Y.
1640 904
1641 config MITIGATE_SPECTRE_BRANCH_HISTORY !! 905 config MAC_HID
1642 bool "Mitigate Spectre style attacks <<
1643 default y <<
1644 help <<
1645 Speculation attacks against some hi <<
1646 make use of branch history to influ <<
1647 When taking an exception from user- <<
1648 or a firmware call overwrites the b <<
1649 <<
1650 config RODATA_FULL_DEFAULT_ENABLED <<
1651 bool "Apply r/o permissions of VM are <<
1652 default y <<
1653 help <<
1654 Apply read-only attributes of VM ar <<
1655 the backing pages as well. This pre <<
1656 from being modified (inadvertently <<
1657 mapping of the same memory page. Th <<
1658 be turned off at runtime by passing <<
1659 with rodata=full if this option is <<
1660 <<
1661 This requires the linear region to <<
1662 which may adversely affect performa <<
1663 <<
1664 config ARM64_SW_TTBR0_PAN <<
1665 bool "Emulate Privileged Access Never <<
1666 depends on !KCSAN <<
1667 help <<
1668 Enabling this option prevents the k <<
1669 user-space memory directly by point <<
1670 zeroed area and reserved ASID. The <<
1671 restore the valid TTBR0_EL1 tempora <<
1672 <<
1673 config ARM64_TAGGED_ADDR_ABI <<
1674 bool "Enable the tagged user addresse <<
1675 default y <<
1676 help <<
1677 When this option is enabled, user a <<
1678 relaxed ABI via prctl() allowing ta <<
1679 to system calls as pointer argument <<
1680 Documentation/arch/arm64/tagged-add <<
1681 <<
1682 menuconfig COMPAT <<
1683 bool "Kernel support for 32-bit EL0" <<
1684 depends on ARM64_4K_PAGES || EXPERT <<
1685 select HAVE_UID16 <<
1686 select OLD_SIGSUSPEND3 <<
1687 select COMPAT_OLD_SIGACTION <<
1688 help <<
1689 This option enables support for a 3 <<
1690 kernel at EL1. AArch32-specific com <<
1691 the user helper functions, VFP supp <<
1692 handled appropriately by the kernel <<
1693 <<
1694 If you use a page size other than 4 <<
1695 that you will only be able to execu <<
1696 with page size aligned segments. <<
1697 <<
1698 If you want to execute 32-bit users <<
1699 <<
1700 if COMPAT <<
1701 <<
1702 config KUSER_HELPERS <<
1703 bool "Enable kuser helpers page for 3 <<
1704 default y <<
1705 help <<
1706 Warning: disabling this option may <<
1707 <<
1708 Provide kuser helpers to compat tas <<
1709 helper code to userspace in read on <<
1710 to allow userspace to be independen <<
1711 the system. This permits binaries t <<
1712 to ARMv8 without modification. <<
1713 <<
1714 See Documentation/arch/arm/kernel_u <<
1715 <<
1716 However, the fixed address nature o <<
1717 by ROP (return orientated programmi <<
1718 exploits. <<
1719 <<
1720 If all of the binaries and librarie <<
1721 are built specifically for your pla <<
1722 these helpers, then you can turn th <<
1723 such exploits. However, in that cas <<
1724 relying on those helpers is run, it <<
1725 <<
1726 Say N here only if you are absolute <<
1727 need these helpers; otherwise, the <<
1728 <<
1729 config COMPAT_VDSO <<
1730 bool "Enable vDSO for 32-bit applicat <<
1731 depends on !CPU_BIG_ENDIAN <<
1732 depends on (CC_IS_CLANG && LD_IS_LLD) <<
1733 select GENERIC_COMPAT_VDSO <<
1734 default y <<
1735 help <<
1736 Place in the process address space <<
1737 ELF shared object providing fast im <<
1738 and clock_gettime. <<
1739 <<
1740 You must have a 32-bit build of gli <<
1741 to seamlessly take advantage of thi <<
1742 <<
1743 config THUMB2_COMPAT_VDSO <<
1744 bool "Compile the 32-bit vDSO for Thu <<
1745 depends on COMPAT_VDSO <<
1746 default y <<
1747 help <<
1748 Compile the compat vDSO with '-mthu <<
1749 otherwise with '-marm'. <<
1750 <<
1751 config COMPAT_ALIGNMENT_FIXUPS <<
1752 bool "Fix up misaligned multi-word lo <<
1753 <<
1754 menuconfig ARMV8_DEPRECATED <<
1755 bool "Emulate deprecated/obsolete ARM <<
1756 depends on SYSCTL <<
1757 help <<
1758 Legacy software support may require <<
1759 that have been deprecated or obsole <<
1760 <<
1761 Enable this config to enable select <<
1762 features. <<
1763 <<
1764 If unsure, say Y <<
1765 <<
1766 if ARMV8_DEPRECATED <<
1767 <<
1768 config SWP_EMULATION <<
1769 bool "Emulate SWP/SWPB instructions" <<
1770 help <<
1771 ARMv8 obsoletes the use of A32 SWP/ <<
1772 they are always undefined. Say Y he <<
1773 emulation of these instructions for <<
1774 This feature can be controlled at r <<
1775 sysctl which is disabled by default <<
1776 <<
1777 In some older versions of glibc [<= <<
1778 trylock() operations with the assum <<
1779 be preempted. This invalid assumpti <<
1780 with SWP emulation enabled, leading <<
1781 application. <<
1782 <<
1783 NOTE: when accessing uncached share <<
1784 on an external transaction monitori <<
1785 monitor to maintain update atomicit <<
1786 implement a global monitor, this op <<
1787 perform SWP operations to uncached <<
1788 <<
1789 If unsure, say Y <<
1790 <<
1791 config CP15_BARRIER_EMULATION <<
1792 bool "Emulate CP15 Barrier instructio <<
1793 help <<
1794 The CP15 barrier instructions - CP1 <<
1795 CP15DMB - are deprecated in ARMv8 ( <<
1796 strongly recommended to use the ISB <<
1797 instructions instead. <<
1798 <<
1799 Say Y here to enable software emula <<
1800 instructions for AArch32 userspace <<
1801 enabled, CP15 barrier usage is trac <<
1802 identify software that needs updati <<
1803 controlled at runtime with the abi. <<
1804 <<
1805 If unsure, say Y <<
1806 <<
1807 config SETEND_EMULATION <<
1808 bool "Emulate SETEND instruction" <<
1809 help <<
1810 The SETEND instruction alters the d <<
1811 AArch32 EL0, and is deprecated in A <<
1812 <<
1813 Say Y here to enable software emula <<
1814 for AArch32 userspace code. This fe <<
1815 at runtime with the abi.setend sysc <<
1816 <<
1817 Note: All the cpus on the system mu <<
1818 for this feature to be enabled. If <<
1819 endian - is hotplugged in after thi <<
1820 be unexpected results in the applic <<
1821 <<
1822 If unsure, say Y <<
1823 endif # ARMV8_DEPRECATED <<
1824 <<
1825 endif # COMPAT <<
1826 <<
1827 menu "ARMv8.1 architectural features" <<
1828 <<
1829 config ARM64_HW_AFDBM <<
1830 bool "Support for hardware updates of <<
1831 default y <<
1832 help <<
1833 The ARMv8.1 architecture extensions <<
1834 hardware updates of the access and <<
1835 table entries. When enabled in TCR_ <<
1836 capable processors, accesses to pag <<
1837 set this bit instead of raising an <<
1838 Similarly, writes to read-only page <<
1839 clear the read-only bit (AP[2]) ins <<
1840 permission fault. <<
1841 <<
1842 Kernels built with this configurati <<
1843 to work on pre-ARMv8.1 hardware and <<
1844 minimal. If unsure, say Y. <<
1845 <<
1846 config ARM64_PAN <<
1847 bool "Enable support for Privileged A <<
1848 default y <<
1849 help <<
1850 Privileged Access Never (PAN; part <<
1851 prevents the kernel or hypervisor f <<
1852 memory directly. <<
1853 <<
1854 Choosing this option will cause any <<
1855 copy_to_user et al) memory access t <<
1856 <<
1857 The feature is detected at runtime, <<
1858 instruction if the cpu does not imp <<
1859 <<
1860 config AS_HAS_LSE_ATOMICS <<
1861 def_bool $(as-instr,.arch_extension l <<
1862 <<
1863 config ARM64_LSE_ATOMICS <<
1864 bool 906 bool
1865 default ARM64_USE_LSE_ATOMICS !! 907 depends on INPUT_ADBHID
1866 depends on AS_HAS_LSE_ATOMICS <<
1867 <<
1868 config ARM64_USE_LSE_ATOMICS <<
1869 bool "Atomic instructions" <<
1870 default y <<
1871 help <<
1872 As part of the Large System Extensi <<
1873 atomic instructions that are design <<
1874 very large systems. <<
1875 <<
1876 Say Y here to make use of these ins <<
1877 atomic routines. This incurs a smal <<
1878 not support these instructions and <<
1879 built with binutils >= 2.25 in orde <<
1880 to be used. <<
1881 <<
1882 endmenu # "ARMv8.1 architectural features" <<
1883 <<
1884 menu "ARMv8.2 architectural features" <<
1885 <<
1886 config AS_HAS_ARMV8_2 <<
1887 def_bool $(cc-option,-Wa$(comma)-marc <<
1888 <<
1889 config AS_HAS_SHA3 <<
1890 def_bool $(as-instr,.arch armv8.2-a+s <<
1891 <<
1892 config ARM64_PMEM <<
1893 bool "Enable support for persistent m <<
1894 select ARCH_HAS_PMEM_API <<
1895 select ARCH_HAS_UACCESS_FLUSHCACHE <<
1896 help <<
1897 Say Y to enable support for the per <<
1898 ARMv8.2 DCPoP feature. <<
1899 <<
1900 The feature is detected at runtime, <<
1901 operations if DC CVAP is not suppor <<
1902 DC CVAP itself if the system does n <<
1903 <<
1904 config ARM64_RAS_EXTN <<
1905 bool "Enable support for RAS CPU Exte <<
1906 default y <<
1907 help <<
1908 CPUs that support the Reliability, <<
1909 (RAS) Extensions, part of ARMv8.2 a <<
1910 errors, classify them and report th <<
1911 <<
1912 On CPUs with these extensions syste <<
1913 barriers to determine if faults are <<
1914 classification from a new set of re <<
1915 <<
1916 Selecting this feature will allow t <<
1917 and access the new registers if the <<
1918 Platform RAS features may additiona <<
1919 <<
1920 config ARM64_CNP <<
1921 bool "Enable support for Common Not P <<
1922 default y <<
1923 depends on ARM64_PAN || !ARM64_SW_TTB <<
1924 help <<
1925 Common Not Private (CNP) allows tra <<
1926 be shared between different PEs in <<
1927 domain, so the hardware can use thi <<
1928 caching of such entries in the TLB. <<
1929 <<
1930 Selecting this option allows the CN <<
1931 at runtime, and does not affect PEs <<
1932 this feature. <<
1933 <<
1934 endmenu # "ARMv8.2 architectural features" <<
1935 <<
1936 menu "ARMv8.3 architectural features" <<
1937 <<
1938 config ARM64_PTR_AUTH <<
1939 bool "Enable support for pointer auth <<
1940 default y <<
1941 help <<
1942 Pointer authentication (part of the <<
1943 instructions for signing and authen <<
1944 keys, which can be used to mitigate <<
1945 and other attacks. <<
1946 <<
1947 This option enables these instructi <<
1948 Choosing this option will cause the <<
1949 for each process at exec() time, wi <<
1950 context-switched along with the pro <<
1951 <<
1952 The feature is detected at runtime. <<
1953 hardware it will not be advertised <<
1954 be enabled. <<
1955 <<
1956 If the feature is present on the bo <<
1957 the late CPU will be parked. Also, <<
1958 address auth and the late CPU has t <<
1959 but with the feature disabled. On s <<
1960 not be selected. <<
1961 <<
1962 config ARM64_PTR_AUTH_KERNEL <<
1963 bool "Use pointer authentication for <<
1964 default y <<
1965 depends on ARM64_PTR_AUTH <<
1966 depends on (CC_HAS_SIGN_RETURN_ADDRES <<
1967 # Modern compilers insert a .note.gnu <<
1968 # which is only understood by binutil <<
1969 depends on LD_IS_LLD || LD_VERSION >= <<
1970 depends on !CC_IS_CLANG || AS_HAS_CFI <<
1971 depends on (!FUNCTION_GRAPH_TRACER || <<
1972 help <<
1973 If the compiler supports the -mbran <<
1974 -msign-return-address flag (e.g. GC <<
1975 will cause the kernel itself to be <<
1976 protection. In this case, and if th <<
1977 support pointer authentication, the <<
1978 disabled with minimal loss of prote <<
1979 <<
1980 This feature works with FUNCTION_GR <<
1981 DYNAMIC_FTRACE_WITH_ARGS is enabled <<
1982 <<
1983 config CC_HAS_BRANCH_PROT_PAC_RET <<
1984 # GCC 9 or later, clang 8 or later <<
1985 def_bool $(cc-option,-mbranch-protect <<
1986 <<
1987 config CC_HAS_SIGN_RETURN_ADDRESS <<
1988 # GCC 7, 8 <<
1989 def_bool $(cc-option,-msign-return-ad <<
1990 <<
1991 config AS_HAS_ARMV8_3 <<
1992 def_bool $(cc-option,-Wa$(comma)-marc <<
1993 <<
1994 config AS_HAS_CFI_NEGATE_RA_STATE <<
1995 def_bool $(as-instr,.cfi_startproc\n. <<
1996 <<
1997 config AS_HAS_LDAPR <<
1998 def_bool $(as-instr,.arch_extension r <<
1999 <<
2000 endmenu # "ARMv8.3 architectural features" <<
2001 <<
2002 menu "ARMv8.4 architectural features" <<
2003 <<
2004 config ARM64_AMU_EXTN <<
2005 bool "Enable support for the Activity <<
2006 default y <<
2007 help <<
2008 The activity monitors extension is <<
2009 by the ARMv8.4 CPU architecture. Th <<
2010 of the activity monitors architectu <<
2011 <<
2012 To enable the use of this extension <<
2013 <<
2014 Note that for architectural reasons <<
2015 support when running on CPUs that p <<
2016 extension. The required support is <<
2017 * Version 1.5 and later of the AR <<
2018 <<
2019 For kernels that have this configur <<
2020 firmware, you may need to say N her <<
2021 Otherwise you may experience firmwa <<
2022 accessing the counter registers. Ev <<
2023 symptoms, the values returned by th <<
2024 correctly reflect reality. Most com <<
2025 indicating that the counter is not <<
2026 <<
2027 config AS_HAS_ARMV8_4 <<
2028 def_bool $(cc-option,-Wa$(comma)-marc <<
2029 <<
2030 config ARM64_TLB_RANGE <<
2031 bool "Enable support for tlbi range f <<
2032 default y 908 default y
2033 depends on AS_HAS_ARMV8_4 <<
2034 help <<
2035 ARMv8.4-TLBI provides TLBI invalida <<
2036 range of input addresses. <<
2037 <<
2038 The feature introduces new assembly <<
2039 support when binutils >= 2.30. <<
2040 909
2041 endmenu # "ARMv8.4 architectural features" !! 910 config MAC_ADBKEYCODES
2042 !! 911 bool "Support for ADB raw keycodes"
2043 menu "ARMv8.5 architectural features" !! 912 depends on INPUT_ADBHID
2044 !! 913 help
2045 config AS_HAS_ARMV8_5 !! 914 This provides support for sending raw ADB keycodes to console
2046 def_bool $(cc-option,-Wa$(comma)-marc !! 915 devices. This is the default up to 2.4.0, but in future this may be
2047 !! 916 phased out in favor of generic Linux keycodes. If you say Y here,
2048 config ARM64_BTI !! 917 you can dynamically switch via the
2049 bool "Branch Target Identification su !! 918 /proc/sys/dev/mac_hid/keyboard_sends_linux_keycodes
2050 default y !! 919 sysctl and with the "keyboard_sends_linux_keycodes=" kernel
2051 help !! 920 argument.
2052 Branch Target Identification (part !! 921
2053 provides a mechanism to limit the s !! 922 If unsure, say Y here.
2054 branch instructions such as BR or B !! 923
2055 !! 924 config MAC_EMUMOUSEBTN
2056 To make use of BTI on CPUs that sup !! 925 bool "Support for mouse button 2+3 emulation"
2057 !! 926 depends on INPUT_ADBHID
2058 BTI is intended to provide compleme !! 927 help
2059 flow integrity protection mechanism !! 928 This provides generic support for emulating the 2nd and 3rd mouse
2060 authentication mechanism provided a !! 929 button with keypresses. If you say Y here, the emulation is still
2061 For this reason, it does not make s !! 930 disabled by default. The emulation is controlled by these sysctl
2062 also enabling support for pointer a !! 931 entries:
2063 enabling this option you should als !! 932 /proc/sys/dev/mac_hid/mouse_button_emulation
2064 !! 933 /proc/sys/dev/mac_hid/mouse_button2_keycode
2065 Userspace binaries must also be spe !! 934 /proc/sys/dev/mac_hid/mouse_button3_keycode
2066 this mechanism. If you say N here !! 935
2067 BTI, such binaries can still run, b !! 936 config ADB_KEYBOARD
2068 enforcement of branch destinations. !! 937 bool "Support for ADB keyboard (old driver)"
2069 !! 938 depends on MAC && !INPUT_ADBHID
2070 config ARM64_BTI_KERNEL !! 939 help
2071 bool "Use Branch Target Identificatio !! 940 This option allows you to use an ADB keyboard attached to your
2072 default y !! 941 machine. Note that this disables any other (ie. PS/2) keyboard
2073 depends on ARM64_BTI !! 942 support, even if your machine is physically capable of using both at
2074 depends on ARM64_PTR_AUTH_KERNEL !! 943 the same time.
2075 depends on CC_HAS_BRANCH_PROT_PAC_RET !! 944
2076 # https://gcc.gnu.org/bugzilla/show_b !! 945 If you use an ADB keyboard (4 pin connector), say Y here.
2077 depends on !CC_IS_GCC || GCC_VERSION !! 946 If you use a PS/2 keyboard (6 pin connector), say N here.
2078 # https://gcc.gnu.org/bugzilla/show_b !! 947
2079 depends on !CC_IS_GCC !! 948 config HPDCA
2080 depends on (!FUNCTION_GRAPH_TRACER || !! 949 tristate "HP DCA serial support"
2081 help !! 950 depends on DIO
2082 Build the kernel with Branch Target !! 951 help
2083 and enable enforcement of this for !! 952 If you want to use the internal "DCA" serial ports on an HP300
2084 is enabled and the system supports !! 953 machine, say Y here.
2085 modular code must have BTI enabled. !! 954
2086 !! 955 config MVME147_SCC
2087 config CC_HAS_BRANCH_PROT_PAC_RET_BTI !! 956 bool "SCC support for MVME147 serial ports"
2088 # GCC 9 or later, clang 8 or later !! 957 depends on MVME147
2089 def_bool $(cc-option,-mbranch-protect !! 958 help
2090 !! 959 This is the driver for the serial ports on the Motorola MVME147
2091 config ARM64_E0PD !! 960 boards. Everyone using one of these boards should say Y here.
2092 bool "Enable support for E0PD" !! 961
2093 default y !! 962 config SERIAL167
2094 help !! 963 bool "CD2401 support for MVME166/7 serial ports"
2095 E0PD (part of the ARMv8.5 extension !! 964 depends on MVME16x && BROKEN
2096 that EL0 accesses made via TTBR1 al !! 965 help
2097 providing similar benefits to KASLR !! 966 This is the driver for the serial ports on the Motorola MVME166,
2098 with lower overhead and without dis !! 967 167, and 172 boards. Everyone using one of these boards should say
2099 kernel memory such as SPE. !! 968 Y here.
2100 !! 969
2101 This option enables E0PD for TTBR1 !! 970 config MVME162_SCC
2102 !! 971 bool "SCC support for MVME162 serial ports"
2103 config ARM64_AS_HAS_MTE !! 972 depends on MVME16x
2104 # Initial support for MTE went in bin !! 973 help
2105 # ".arch armv8.5-a+memtag" below. How !! 974 This is the driver for the serial ports on the Motorola MVME162 and
2106 # as a late addition to the final arc !! 975 172 boards. Everyone using one of these boards should say Y here.
2107 # is only supported in the newer 2.32 !! 976
2108 # versions, hence the extra "stgm" in !! 977 config BVME6000_SCC
2109 def_bool $(as-instr,.arch armv8.5-a+m !! 978 bool "SCC support for BVME6000 serial ports"
2110 !! 979 depends on BVME6000
2111 config ARM64_MTE !! 980 help
2112 bool "Memory Tagging Extension suppor !! 981 This is the driver for the serial ports on the BVME4000 and BVME6000
2113 default y !! 982 boards from BVM Ltd. Everyone using one of these boards should say
2114 depends on ARM64_AS_HAS_MTE && ARM64_ !! 983 Y here.
2115 depends on AS_HAS_ARMV8_5 !! 984
2116 depends on AS_HAS_LSE_ATOMICS !! 985 config DN_SERIAL
2117 # Required for tag checking in the ua !! 986 bool "Support for DN serial port (dummy)"
2118 depends on ARM64_PAN !! 987 depends on APOLLO
2119 select ARCH_HAS_SUBPAGE_FAULTS !! 988
2120 select ARCH_USES_HIGH_VMA_FLAGS !! 989 config SERIAL_CONSOLE
2121 select ARCH_USES_PG_ARCH_2 !! 990 bool "Support for serial port console"
2122 select ARCH_USES_PG_ARCH_3 !! 991 depends on (AMIGA || ATARI || MAC || HP300 || SUN3 || SUN3X || VME || APOLLO) && (ATARI_MFPSER=y || ATARI_SCC=y || ATARI_MIDI=y || MAC_SCC=y || AMIGA_BUILTIN_SERIAL=y || GVPIOEXT=y || MULTIFACE_III_TTY=y || HPDCA=y || SERIAL=y || MVME147_SCC || SERIAL167 || MVME162_SCC || BVME6000_SCC || DN_SERIAL)
2123 help !! 992 ---help---
2124 Memory Tagging (part of the ARMv8.5 !! 993 If you say Y here, it will be possible to use a serial port as the
2125 architectural support for run-time, !! 994 system console (the system console is the device which receives all
2126 various classes of memory error to !! 995 kernel messages and warnings and which allows logins in single user
2127 to eliminate vulnerabilities arisin !! 996 mode). This could be useful if some terminal or printer is connected
2128 languages. !! 997 to that serial port.
2129 !! 998
2130 This option enables the support for !! 999 Even if you say Y here, the currently visible virtual console
2131 Extension at EL0 (i.e. for userspac !! 1000 (/dev/tty0) will still be used as the system console by default, but
2132 !! 1001 you can alter that using a kernel command line option such as
2133 Selecting this option allows the fe !! 1002 "console=ttyS1". (Try "man bootparam" or see the documentation of
2134 runtime. Any secondary CPU not impl !! 1003 your boot loader (lilo or loadlin) about how to pass options to the
2135 not be allowed a late bring-up. !! 1004 kernel at boot time.)
2136 !! 1005
2137 Userspace binaries that want to use !! 1006 If you don't have a VGA card installed and you say Y here, the
2138 explicitly opt in. The mechanism fo !! 1007 kernel will automatically use the first serial line, /dev/ttyS0, as
2139 described in: !! 1008 system console.
2140 <<
2141 Documentation/arch/arm64/memory-tag <<
2142 <<
2143 endmenu # "ARMv8.5 architectural features" <<
2144 <<
2145 menu "ARMv8.7 architectural features" <<
2146 <<
2147 config ARM64_EPAN <<
2148 bool "Enable support for Enhanced Pri <<
2149 default y <<
2150 depends on ARM64_PAN <<
2151 help <<
2152 Enhanced Privileged Access Never (E <<
2153 Access Never to be used with Execut <<
2154 <<
2155 The feature is detected at runtime, <<
2156 if the cpu does not implement the f <<
2157 endmenu # "ARMv8.7 architectural features" <<
2158 <<
2159 menu "ARMv8.9 architectural features" <<
2160 <<
2161 config ARM64_POE <<
2162 prompt "Permission Overlay Extension" <<
2163 def_bool y <<
2164 select ARCH_USES_HIGH_VMA_FLAGS <<
2165 select ARCH_HAS_PKEYS <<
2166 help <<
2167 The Permission Overlay Extension is <<
2168 Protection Keys. Memory Protection <<
2169 enforcing page-based protections, b <<
2170 of the page tables when an applicat <<
2171 <<
2172 For details, see Documentation/core <<
2173 <<
2174 If unsure, say y. <<
2175 <<
2176 config ARCH_PKEY_BITS <<
2177 int <<
2178 default 3 <<
2179 <<
2180 endmenu # "ARMv8.9 architectural features" <<
2181 <<
2182 config ARM64_SVE <<
2183 bool "ARM Scalable Vector Extension s <<
2184 default y <<
2185 help <<
2186 The Scalable Vector Extension (SVE) <<
2187 execution state which complements a <<
2188 of the base architecture to support <<
2189 additional vectorisation opportunit <<
2190 <<
2191 To enable use of this extension on <<
2192 <<
2193 On CPUs that support the SVE2 exten <<
2194 those too. <<
2195 <<
2196 Note that for architectural reasons <<
2197 support when running on SVE capable <<
2198 is present in: <<
2199 <<
2200 * version 1.5 and later of the AR <<
2201 * the AArch64 boot wrapper since <<
2202 ("bootwrapper: SVE: Enable SVE <<
2203 <<
2204 For other firmware implementations, <<
2205 or vendor. <<
2206 <<
2207 If you need the kernel to boot on S <<
2208 firmware, you may need to say N her <<
2209 fixed. Otherwise, you may experien <<
2210 booting the kernel. If unsure and <<
2211 symptoms, you should assume that it <<
2212 <<
2213 config ARM64_SME <<
2214 bool "ARM Scalable Matrix Extension s <<
2215 default y <<
2216 depends on ARM64_SVE <<
2217 depends on BROKEN <<
2218 help <<
2219 The Scalable Matrix Extension (SME) <<
2220 execution state which utilises a su <<
2221 instruction set, together with the <<
2222 register state capable of holding t <<
2223 enable various matrix operations. <<
2224 <<
2225 config ARM64_PSEUDO_NMI <<
2226 bool "Support for NMI-like interrupts <<
2227 select ARM_GIC_V3 <<
2228 help <<
2229 Adds support for mimicking Non-Mask <<
2230 GIC interrupt priority. This suppor <<
2231 ARM GIC. <<
2232 <<
2233 This high priority configuration fo <<
2234 explicitly enabled by setting the k <<
2235 "irqchip.gicv3_pseudo_nmi" to 1. <<
2236 <<
2237 If unsure, say N <<
2238 <<
2239 if ARM64_PSEUDO_NMI <<
2240 config ARM64_DEBUG_PRIORITY_MASKING <<
2241 bool "Debug interrupt priority maskin <<
2242 help <<
2243 This adds runtime checks to functio <<
2244 interrupts when using priority mask <<
2245 the validity of ICC_PMR_EL1 when ca <<
2246 <<
2247 If unsure, say N <<
2248 endif # ARM64_PSEUDO_NMI <<
2249 <<
2250 config RELOCATABLE <<
2251 bool "Build a relocatable kernel imag <<
2252 select ARCH_HAS_RELR <<
2253 default y <<
2254 help <<
2255 This builds the kernel as a Positio <<
2256 which retains all relocation metada <<
2257 kernel binary at runtime to a diffe <<
2258 address it was linked at. <<
2259 Since AArch64 uses the RELA relocat <<
2260 relocation pass at runtime even if <<
2261 same address it was linked at. <<
2262 <<
2263 config RANDOMIZE_BASE <<
2264 bool "Randomize the address of the ke <<
2265 select RELOCATABLE <<
2266 help <<
2267 Randomizes the virtual address at w <<
2268 loaded, as a security feature that <<
2269 relying on knowledge of the locatio <<
2270 <<
2271 It is the bootloader's job to provi <<
2272 random u64 value in /chosen/kaslr-s <<
2273 <<
2274 When booting via the UEFI stub, it <<
2275 EFI_RNG_PROTOCOL implementation (if <<
2276 to the kernel proper. In addition, <<
2277 location of the kernel Image as wel <<
2278 1009
2279 If unsure, say N. 1010 If unsure, say N.
2280 1011
2281 config RANDOMIZE_MODULE_REGION_FULL !! 1012 config USERIAL
2282 bool "Randomize the module region ove !! 1013 bool "Support for user serial device modules"
2283 depends on RANDOMIZE_BASE <<
2284 default y <<
2285 help <<
2286 Randomizes the location of the modu <<
2287 covering the core kernel. This way, <<
2288 to leak information about the locat <<
2289 but it does imply that function cal <<
2290 kernel will need to be resolved via <<
2291 <<
2292 When this option is not set, the mo <<
2293 a limited range that contains the [ <<
2294 core kernel, so branch relocations <<
2295 the region is exhausted. In this pa <<
2296 exhaustion, modules might be able t <<
2297 <<
2298 config CC_HAVE_STACKPROTECTOR_SYSREG <<
2299 def_bool $(cc-option,-mstack-protecto <<
2300 <<
2301 config STACKPROTECTOR_PER_TASK <<
2302 def_bool y <<
2303 depends on STACKPROTECTOR && CC_HAVE_ <<
2304 <<
2305 config UNWIND_PATCH_PAC_INTO_SCS <<
2306 bool "Enable shadow call stack dynami <<
2307 # needs Clang with https://github.com <<
2308 depends on CC_IS_CLANG && CLANG_VERSI <<
2309 depends on ARM64_PTR_AUTH_KERNEL && C <<
2310 depends on SHADOW_CALL_STACK <<
2311 select UNWIND_TABLES <<
2312 select DYNAMIC_SCS <<
2313 <<
2314 config ARM64_CONTPTE <<
2315 bool "Contiguous PTE mappings for use <<
2316 depends on TRANSPARENT_HUGEPAGE <<
2317 default y <<
2318 help <<
2319 When enabled, user mappings are con <<
2320 bit, for any mappings that meet the <<
2321 This reduces TLB pressure and impro <<
2322 <<
2323 endmenu # "Kernel Features" <<
2324 <<
2325 menu "Boot options" <<
2326 <<
2327 config ARM64_ACPI_PARKING_PROTOCOL <<
2328 bool "Enable support for the ARM64 AC <<
2329 depends on ACPI <<
2330 help <<
2331 Enable support for the ARM64 ACPI p <<
2332 the kernel will not allow booting t <<
2333 protocol even if the corresponding <<
2334 MADT table. <<
2335 <<
2336 config CMDLINE <<
2337 string "Default kernel command string <<
2338 default "" <<
2339 help <<
2340 Provide a set of default command-li <<
2341 entering them here. As a minimum, y <<
2342 root device (e.g. root=/dev/nfs). <<
2343 1014
2344 choice !! 1015 config WATCHDOG
2345 prompt "Kernel command line type" !! 1016 bool "Watchdog Timer Support"
2346 depends on CMDLINE != "" !! 1017 ---help---
2347 default CMDLINE_FROM_BOOTLOADER !! 1018 If you say Y here (and to one of the following options) and create a
2348 help !! 1019 character special file /dev/watchdog with major number 10 and minor
2349 Choose how the kernel will handle t !! 1020 number 130 using mknod ("man mknod"), you will get a watchdog, i.e.:
2350 command line string. !! 1021 subsequently opening the file and then failing to write to it for
2351 !! 1022 longer than 1 minute will result in rebooting the machine. This
2352 config CMDLINE_FROM_BOOTLOADER !! 1023 could be useful for a networked machine that needs to come back
2353 bool "Use bootloader kernel arguments !! 1024 online as fast as possible after a lock-up. There's both a watchdog
2354 help !! 1025 implementation entirely in software (which can sometimes fail to
2355 Uses the command-line options passe !! 1026 reboot the machine) and a driver for hardware watchdog boards, which
2356 the boot loader doesn't provide any !! 1027 are more robust and can also keep track of the temperature inside
2357 string provided in CMDLINE will be !! 1028 your computer. For details, read <file:Documentation/watchdog.txt>
2358 !! 1029 in the kernel source.
2359 config CMDLINE_FORCE !! 1030
2360 bool "Always use the default kernel c !! 1031 The watchdog is usually used together with the watchdog daemon
2361 help !! 1032 which is available from
2362 Always use the default kernel comma !! 1033 <ftp://ibiblio.org/pub/Linux/system/daemons/watchdog/>. This daemon can
2363 loader passes other arguments to th !! 1034 also monitor NFS connections and can reboot the machine when the process
2364 This is useful if you cannot or don !! 1035 table is full.
2365 command-line options your boot load <<
2366 <<
2367 endchoice <<
2368 <<
2369 config EFI_STUB <<
2370 bool <<
2371 1036
2372 config EFI !! 1037 If unsure, say N.
2373 bool "UEFI runtime support" <<
2374 depends on OF && !CPU_BIG_ENDIAN <<
2375 depends on KERNEL_MODE_NEON <<
2376 select ARCH_SUPPORTS_ACPI <<
2377 select LIBFDT <<
2378 select UCS2_STRING <<
2379 select EFI_PARAMS_FROM_FDT <<
2380 select EFI_RUNTIME_WRAPPERS <<
2381 select EFI_STUB <<
2382 select EFI_GENERIC_STUB <<
2383 imply IMA_SECURE_AND_OR_TRUSTED_BOOT <<
2384 default y <<
2385 help <<
2386 This option provides support for ru <<
2387 by UEFI firmware (such as non-volat <<
2388 clock, and platform reset). A UEFI <<
2389 allow the kernel to be booted as an <<
2390 is only useful on systems that have <<
2391 <<
2392 config COMPRESSED_INSTALL <<
2393 bool "Install compressed image by def <<
2394 help <<
2395 This makes the regular "make instal <<
2396 image we built, not the legacy unco <<
2397 <<
2398 You can check that a compressed ima <<
2399 "make zinstall" first, and verifyin <<
2400 in your environment before making " <<
2401 you. <<
2402 <<
2403 config DMI <<
2404 bool "Enable support for SMBIOS (DMI) <<
2405 depends on EFI <<
2406 default y <<
2407 help <<
2408 This enables SMBIOS/DMI feature for <<
2409 <<
2410 This option is only useful on syste <<
2411 However, even with this option, the <<
2412 continue to boot on existing non-UE <<
2413 <<
2414 endmenu # "Boot options" <<
2415 <<
2416 menu "Power management options" <<
2417 <<
2418 source "kernel/power/Kconfig" <<
2419 <<
2420 config ARCH_HIBERNATION_POSSIBLE <<
2421 def_bool y <<
2422 depends on CPU_PM <<
2423 <<
2424 config ARCH_HIBERNATION_HEADER <<
2425 def_bool y <<
2426 depends on HIBERNATION <<
2427 <<
2428 config ARCH_SUSPEND_POSSIBLE <<
2429 def_bool y <<
2430 <<
2431 endmenu # "Power management options" <<
2432 <<
2433 menu "CPU Power Management" <<
2434 <<
2435 source "drivers/cpuidle/Kconfig" <<
2436 1038
2437 source "drivers/cpufreq/Kconfig" !! 1039 config WATCHDOG_NOWAYOUT
>> 1040 bool "Disable watchdog shutdown on close"
>> 1041 depends on WATCHDOG
>> 1042 help
>> 1043 The default watchdog behaviour (which you get if you say N here) is
>> 1044 to stop the timer if the process managing it closes the file
>> 1045 /dev/watchdog. It's always remotely possible that this process might
>> 1046 get killed. If you say Y here, the watchdog cannot be stopped once
>> 1047 it has been started.
>> 1048
>> 1049 config SOFT_WATCHDOG
>> 1050 bool "Software watchdog"
>> 1051 depends on WATCHDOG
>> 1052 help
>> 1053 A software monitoring watchdog. This will fail to reboot your system
>> 1054 from some situations that the hardware watchdog will recover
>> 1055 from. Equally it's a lot cheaper to install.
>> 1056
>> 1057 To compile this driver as a module, choose M here: the
>> 1058 module will be called softdog.
>> 1059
>> 1060 config GEN_RTC
>> 1061 tristate "Generic /dev/rtc emulation" if !SUN3
>> 1062 default y if SUN3
>> 1063 ---help---
>> 1064 If you say Y here and create a character special file /dev/rtc with
>> 1065 major number 10 and minor number 135 using mknod ("man mknod"), you
>> 1066 will get access to the real time clock (or hardware clock) built
>> 1067 into your computer.
>> 1068
>> 1069 It reports status information via the file /proc/driver/rtc and its
>> 1070 behaviour is set by various ioctls on /dev/rtc. If you enable the
>> 1071 "extended RTC operation" below it will also provide an emulation
>> 1072 for RTC_UIE which is required by some programs and may improve
>> 1073 precision in some cases.
>> 1074
>> 1075 To compile this driver as a module, choose M here: the
>> 1076 module will be called genrtc. To load the module automatically
>> 1077 add 'alias char-major-10-135 genrtc' to your /etc/modules.conf
>> 1078
>> 1079 config GEN_RTC_X
>> 1080 bool "Extended RTC operation"
>> 1081 depends on GEN_RTC
>> 1082 help
>> 1083 Provides an emulation for RTC_UIE which is required by some programs
>> 1084 and may improve precision of the generic RTC support in some cases.
>> 1085
>> 1086 config UNIX98_PTYS
>> 1087 bool "Unix98 PTY support"
>> 1088 ---help---
>> 1089 A pseudo terminal (PTY) is a software device consisting of two
>> 1090 halves: a master and a slave. The slave device behaves identical to
>> 1091 a physical terminal; the master device is used by a process to
>> 1092 read data from and write data to the slave, thereby emulating a
>> 1093 terminal. Typical programs for the master side are telnet servers
>> 1094 and xterms.
>> 1095
>> 1096 Linux has traditionally used the BSD-like names /dev/ptyxx for
>> 1097 masters and /dev/ttyxx for slaves of pseudo terminals. This scheme
>> 1098 has a number of problems. The GNU C library glibc 2.1 and later,
>> 1099 however, supports the Unix98 naming standard: in order to acquire a
>> 1100 pseudo terminal, a process opens /dev/ptmx; the number of the pseudo
>> 1101 terminal is then made available to the process and the pseudo
>> 1102 terminal slave can be accessed as /dev/pts/<number>. What was
>> 1103 traditionally /dev/ttyp2 will then be /dev/pts/2, for example.
>> 1104
>> 1105 The entries in /dev/pts/ are created on the fly by a virtual
>> 1106 file system; therefore, if you say Y here you should say Y to
>> 1107 "/dev/pts file system for Unix98 PTYs" as well.
>> 1108
>> 1109 If you want to say Y here, you need to have the C library glibc 2.1
>> 1110 or later (equal to libc-6.1, check with "ls -l /lib/libc.so.*").
>> 1111 Read the instructions in <file:Documentation/Changes> pertaining to
>> 1112 pseudo terminals. It's safe to say N.
>> 1113
>> 1114 config UNIX98_PTY_COUNT
>> 1115 int "Maximum number of Unix98 PTYs in use (0-2048)"
>> 1116 depends on UNIX98_PTYS
>> 1117 default "256"
>> 1118 help
>> 1119 The maximum number of Unix98 PTYs that can be used at any one time.
>> 1120 The default is 256, and should be enough for desktop systems. Server
>> 1121 machines which support incoming telnet/rlogin/ssh connections and/or
>> 1122 serve several X terminals may want to increase this: every incoming
>> 1123 connection and every xterm uses up one PTY.
>> 1124
>> 1125 When not in use, each additional set of 256 PTYs occupy
>> 1126 approximately 8 KB of kernel memory on 32-bit architectures.
>> 1127
>> 1128 endmenu
>> 1129
>> 1130 source "sound/Kconfig"
>> 1131
>> 1132 source "fs/Kconfig"
>> 1133
>> 1134 source "drivers/video/Kconfig"
>> 1135
>> 1136 menu "Kernel hacking"
>> 1137
>> 1138 config DEBUG_KERNEL
>> 1139 bool "Kernel debugging"
>> 1140
>> 1141 config MAGIC_SYSRQ
>> 1142 bool "Magic SysRq key"
>> 1143 depends on DEBUG_KERNEL
>> 1144 help
>> 1145 If you say Y here, you will have some control over the system even
>> 1146 if the system crashes for example during kernel debugging (e.g., you
>> 1147 will be able to flush the buffer cache to disk, reboot the system
>> 1148 immediately or dump some status information). This is accomplished
>> 1149 by pressing various keys while holding SysRq (Alt+PrintScreen). It
>> 1150 also works on a serial console (on PC hardware at least), if you
>> 1151 send a BREAK and then within 5 seconds a command keypress. The
>> 1152 keys are documented in <file:Documentation/sysrq.txt>. Don't say Y
>> 1153 unless you really know what this hack does.
>> 1154
>> 1155 config DEBUG_SLAB
>> 1156 bool "Debug memory allocations"
>> 1157 depends on DEBUG_KERNEL
>> 1158
>> 1159 config DEBUG_BUGVERBOSE
>> 1160 bool "Verbose BUG() reporting"
>> 1161 depends on DEBUG_KERNEL
>> 1162
>> 1163 config DEBUG_INFO
>> 1164 bool "Compile the kernel with debug info"
>> 1165 depends on DEBUG_KERNEL
>> 1166 help
>> 1167 If you say Y here the resulting kernel image will include
>> 1168 debugging info resulting in a larger kernel image.
>> 1169 Say Y here only if you plan to use gdb to debug the kernel.
>> 1170 If you don't debug the kernel, you can say N.
>> 1171
>> 1172 endmenu
2438 1173
2439 endmenu # "CPU Power Management" !! 1174 source "security/Kconfig"
2440 1175
2441 source "drivers/acpi/Kconfig" !! 1176 source "crypto/Kconfig"
2442 1177
2443 source "arch/arm64/kvm/Kconfig" !! 1178 source "lib/Kconfig"
2444 1179
Linux® is a registered trademark of Linus Torvalds in the United States and other countries.
TOMOYO® is a registered trademark of NTT DATA CORPORATION.