Commit | Line | Data |
---|---|---|
ec8f24b7 | 1 | # SPDX-License-Identifier: GPL-2.0-only |
8c2c3df3 CM |
2 | config ARM64 |
3 | def_bool y | |
b6197b93 | 4 | select ACPI_CCA_REQUIRED if ACPI |
d8f4f161 | 5 | select ACPI_GENERIC_GSI if ACPI |
5f1ae4eb | 6 | select ACPI_GTDT if ACPI |
c6bb8f89 | 7 | select ACPI_IORT if ACPI |
6933de0c | 8 | select ACPI_REDUCED_HARDWARE_ONLY if ACPI |
52146173 | 9 | select ACPI_MCFG if (ACPI && PCI) |
888125a7 | 10 | select ACPI_SPCR_TABLE if ACPI |
0ce82232 | 11 | select ACPI_PPTT if ACPI |
09587a09 | 12 | select ARCH_HAS_DEBUG_WX |
6dd8b1a0 | 13 | select ARCH_BINFMT_ELF_EXTRA_PHDRS |
ab7876a9 | 14 | select ARCH_BINFMT_ELF_STATE |
cd9bc2c9 | 15 | select ARCH_CORRECT_STACKTRACE_ON_KRETPROBE |
1e866974 | 16 | select ARCH_ENABLE_HUGEPAGE_MIGRATION if HUGETLB_PAGE && MIGRATION |
91024b3c AK |
17 | select ARCH_ENABLE_MEMORY_HOTPLUG |
18 | select ARCH_ENABLE_MEMORY_HOTREMOVE | |
66f24fa7 | 19 | select ARCH_ENABLE_SPLIT_PMD_PTLOCK if PGTABLE_LEVELS > 2 |
1e866974 | 20 | select ARCH_ENABLE_THP_MIGRATION if TRANSPARENT_HUGEPAGE |
c2280be8 | 21 | select ARCH_HAS_CACHE_LINE_SIZE |
2792d84e | 22 | select ARCH_HAS_CURRENT_STACK_POINTER |
ec6d06ef | 23 | select ARCH_HAS_DEBUG_VIRTUAL |
399145f9 | 24 | select ARCH_HAS_DEBUG_VM_PGTABLE |
13bf5ced | 25 | select ARCH_HAS_DMA_PREP_COHERENT |
38b04a74 | 26 | select ARCH_HAS_ACPI_TABLE_UPGRADE if ACPI |
e75bef2a | 27 | select ARCH_HAS_FAST_MULTIPLIER |
6974f0c4 | 28 | select ARCH_HAS_FORTIFY_SOURCE |
957e3fac | 29 | select ARCH_HAS_GCOV_PROFILE_ALL |
4eb0716e | 30 | select ARCH_HAS_GIGANTIC_PAGE |
5e4c7549 | 31 | select ARCH_HAS_KCOV |
d8ae8a37 | 32 | select ARCH_HAS_KEEPINITRD |
f1e3a12b | 33 | select ARCH_HAS_MEMBARRIER_SYNC_CORE |
0ebeea8c | 34 | select ARCH_HAS_NON_OVERLAPPING_ADDRESS_SPACE |
73b20c84 | 35 | select ARCH_HAS_PTE_DEVMAP |
3010a5ea | 36 | select ARCH_HAS_PTE_SPECIAL |
347cb6af | 37 | select ARCH_HAS_SETUP_DMA_OPS |
4739d53f | 38 | select ARCH_HAS_SET_DIRECT_MAP |
d2852a22 | 39 | select ARCH_HAS_SET_MEMORY |
5fc57df2 | 40 | select ARCH_STACKWALK |
ad21fc4f LA |
41 | select ARCH_HAS_STRICT_KERNEL_RWX |
42 | select ARCH_HAS_STRICT_MODULE_RWX | |
886643b7 CH |
43 | select ARCH_HAS_SYNC_DMA_FOR_DEVICE |
44 | select ARCH_HAS_SYNC_DMA_FOR_CPU | |
4378a7d4 | 45 | select ARCH_HAS_SYSCALL_WRAPPER |
dc2acded | 46 | select ARCH_HAS_TEARDOWN_DMA_OPS if IOMMU_SUPPORT |
1f85008e | 47 | select ARCH_HAS_TICK_BROADCAST if GENERIC_CLOCKEVENTS_BROADCAST |
63703f37 | 48 | select ARCH_HAS_ZONE_DMA_SET if EXPERT |
ab7876a9 | 49 | select ARCH_HAVE_ELF_PROT |
396a5d4a | 50 | select ARCH_HAVE_NMI_SAFE_CMPXCHG |
7ef858da TG |
51 | select ARCH_INLINE_READ_LOCK if !PREEMPTION |
52 | select ARCH_INLINE_READ_LOCK_BH if !PREEMPTION | |
53 | select ARCH_INLINE_READ_LOCK_IRQ if !PREEMPTION | |
54 | select ARCH_INLINE_READ_LOCK_IRQSAVE if !PREEMPTION | |
55 | select ARCH_INLINE_READ_UNLOCK if !PREEMPTION | |
56 | select ARCH_INLINE_READ_UNLOCK_BH if !PREEMPTION | |
57 | select ARCH_INLINE_READ_UNLOCK_IRQ if !PREEMPTION | |
58 | select ARCH_INLINE_READ_UNLOCK_IRQRESTORE if !PREEMPTION | |
59 | select ARCH_INLINE_WRITE_LOCK if !PREEMPTION | |
60 | select ARCH_INLINE_WRITE_LOCK_BH if !PREEMPTION | |
61 | select ARCH_INLINE_WRITE_LOCK_IRQ if !PREEMPTION | |
62 | select ARCH_INLINE_WRITE_LOCK_IRQSAVE if !PREEMPTION | |
63 | select ARCH_INLINE_WRITE_UNLOCK if !PREEMPTION | |
64 | select ARCH_INLINE_WRITE_UNLOCK_BH if !PREEMPTION | |
65 | select ARCH_INLINE_WRITE_UNLOCK_IRQ if !PREEMPTION | |
66 | select ARCH_INLINE_WRITE_UNLOCK_IRQRESTORE if !PREEMPTION | |
67 | select ARCH_INLINE_SPIN_TRYLOCK if !PREEMPTION | |
68 | select ARCH_INLINE_SPIN_TRYLOCK_BH if !PREEMPTION | |
69 | select ARCH_INLINE_SPIN_LOCK if !PREEMPTION | |
70 | select ARCH_INLINE_SPIN_LOCK_BH if !PREEMPTION | |
71 | select ARCH_INLINE_SPIN_LOCK_IRQ if !PREEMPTION | |
72 | select ARCH_INLINE_SPIN_LOCK_IRQSAVE if !PREEMPTION | |
73 | select ARCH_INLINE_SPIN_UNLOCK if !PREEMPTION | |
74 | select ARCH_INLINE_SPIN_UNLOCK_BH if !PREEMPTION | |
75 | select ARCH_INLINE_SPIN_UNLOCK_IRQ if !PREEMPTION | |
76 | select ARCH_INLINE_SPIN_UNLOCK_IRQRESTORE if !PREEMPTION | |
350e88ba | 77 | select ARCH_KEEP_MEMBLOCK |
c63c8700 | 78 | select ARCH_USE_CMPXCHG_LOCKREF |
bf7f15c5 | 79 | select ARCH_USE_GNU_PROPERTY |
dce44566 | 80 | select ARCH_USE_MEMTEST |
087133ac | 81 | select ARCH_USE_QUEUED_RWLOCKS |
c1109047 | 82 | select ARCH_USE_QUEUED_SPINLOCKS |
50479d58 | 83 | select ARCH_USE_SYM_ANNOTATIONS |
5d6ad668 | 84 | select ARCH_SUPPORTS_DEBUG_PAGEALLOC |
855f9a8e | 85 | select ARCH_SUPPORTS_HUGETLBFS |
c484f256 | 86 | select ARCH_SUPPORTS_MEMORY_FAILURE |
5287569a | 87 | select ARCH_SUPPORTS_SHADOW_CALL_STACK if CC_HAVE_SHADOW_CALL_STACK |
112b6a8e ST |
88 | select ARCH_SUPPORTS_LTO_CLANG if CPU_LITTLE_ENDIAN |
89 | select ARCH_SUPPORTS_LTO_CLANG_THIN | |
9186ad8e | 90 | select ARCH_SUPPORTS_CFI_CLANG |
4badad35 | 91 | select ARCH_SUPPORTS_ATOMIC_RMW |
42a7ba16 | 92 | select ARCH_SUPPORTS_INT128 if CC_HAS_INT128 |
56166230 | 93 | select ARCH_SUPPORTS_NUMA_BALANCING |
84c187af | 94 | select ARCH_WANT_COMPAT_IPC_PARSE_VERSION if COMPAT |
81c22041 | 95 | select ARCH_WANT_DEFAULT_BPF_JIT |
67f3977f | 96 | select ARCH_WANT_DEFAULT_TOPDOWN_MMAP_LAYOUT |
b6f35981 | 97 | select ARCH_WANT_FRAME_POINTERS |
3876d4a3 | 98 | select ARCH_WANT_HUGE_PMD_SHARE if ARM64_4K_PAGES || (ARM64_16K_PAGES && !ARM64_VA_BITS_36) |
59612b24 | 99 | select ARCH_WANT_LD_ORPHAN_WARN |
51c2ee6d | 100 | select ARCH_WANTS_NO_INSTR |
f0b7f8a4 | 101 | select ARCH_HAS_UBSAN_SANITIZE_ALL |
25c92a37 | 102 | select ARM_AMBA |
1aee5d7a | 103 | select ARM_ARCH_TIMER |
c4188edc | 104 | select ARM_GIC |
875cbf3e | 105 | select AUDIT_ARCH_COMPAT_GENERIC |
3ee80364 | 106 | select ARM_GIC_V2M if PCI |
021f6537 | 107 | select ARM_GIC_V3 |
3ee80364 | 108 | select ARM_GIC_V3_ITS if PCI |
bff60792 | 109 | select ARM_PSCI_FW |
10916706 | 110 | select BUILDTIME_TABLE_SORT |
db2789b5 | 111 | select CLONE_BACKWARDS |
7ca2ef33 | 112 | select COMMON_CLK |
166936ba | 113 | select CPU_PM if (SUSPEND || CPU_IDLE) |
7481cddf | 114 | select CRC32 |
7bc13fd3 | 115 | select DCACHE_WORD_ACCESS |
0c3b3171 | 116 | select DMA_DIRECT_REMAP |
ef37566c | 117 | select EDAC_SUPPORT |
2f34f173 | 118 | select FRAME_POINTER |
d4932f9e | 119 | select GENERIC_ALLOCATOR |
2ef7a295 | 120 | select GENERIC_ARCH_TOPOLOGY |
4b3dc967 | 121 | select GENERIC_CLOCKEVENTS_BROADCAST |
3be1a5c4 | 122 | select GENERIC_CPU_AUTOPROBE |
61ae1321 | 123 | select GENERIC_CPU_VULNERABILITIES |
bf4b558e | 124 | select GENERIC_EARLY_IOREMAP |
2314ee4d | 125 | select GENERIC_IDLE_POLL_SETUP |
d3afc7f1 | 126 | select GENERIC_IRQ_IPI |
8c2c3df3 CM |
127 | select GENERIC_IRQ_PROBE |
128 | select GENERIC_IRQ_SHOW | |
6544e67b | 129 | select GENERIC_IRQ_SHOW_LEVEL |
6585bd82 | 130 | select GENERIC_LIB_DEVMEM_IS_ALLOWED |
cb61f676 | 131 | select GENERIC_PCI_IOMAP |
102f45fd | 132 | select GENERIC_PTDUMP |
65cd4f6c | 133 | select GENERIC_SCHED_CLOCK |
8c2c3df3 CM |
134 | select GENERIC_SMP_IDLE_THREAD |
135 | select GENERIC_TIME_VSYSCALL | |
28b1a824 | 136 | select GENERIC_GETTIMEOFDAY |
9614cc57 | 137 | select GENERIC_VDSO_TIME_NS |
8c2c3df3 | 138 | select HARDIRQS_SW_RESEND |
45544eee | 139 | select HAVE_MOVE_PMD |
f5308c89 | 140 | select HAVE_MOVE_PUD |
eb01d42a | 141 | select HAVE_PCI |
9f9a35a7 | 142 | select HAVE_ACPI_APEI if (ACPI && EFI) |
5284e1b4 | 143 | select HAVE_ALIGNED_STRUCT_PAGE if SLUB |
875cbf3e | 144 | select HAVE_ARCH_AUDITSYSCALL |
8e7a4cef | 145 | select HAVE_ARCH_BITREVERSE |
689eae42 | 146 | select HAVE_ARCH_COMPILER_H |
324420bf | 147 | select HAVE_ARCH_HUGE_VMAP |
9732cafd | 148 | select HAVE_ARCH_JUMP_LABEL |
c296146c | 149 | select HAVE_ARCH_JUMP_LABEL_RELATIVE |
e17d8025 | 150 | select HAVE_ARCH_KASAN if !(ARM64_16K_PAGES && ARM64_VA_BITS_48) |
71b613fc | 151 | select HAVE_ARCH_KASAN_VMALLOC if HAVE_ARCH_KASAN |
2d4acb90 | 152 | select HAVE_ARCH_KASAN_SW_TAGS if HAVE_ARCH_KASAN |
94ab5b61 | 153 | select HAVE_ARCH_KASAN_HW_TAGS if (HAVE_ARCH_KASAN && ARM64_MTE) |
dd03762a KW |
154 | # Some instrumentation may be unsound, hence EXPERT |
155 | select HAVE_ARCH_KCSAN if EXPERT | |
840b2398 | 156 | select HAVE_ARCH_KFENCE |
9529247d | 157 | select HAVE_ARCH_KGDB |
8f0d3aa9 DC |
158 | select HAVE_ARCH_MMAP_RND_BITS |
159 | select HAVE_ARCH_MMAP_RND_COMPAT_BITS if COMPAT | |
271ca788 | 160 | select HAVE_ARCH_PREL32_RELOCATIONS |
70918779 | 161 | select HAVE_ARCH_RANDOMIZE_KSTACK_OFFSET |
a1ae65b2 | 162 | select HAVE_ARCH_SECCOMP_FILTER |
0b3e3366 | 163 | select HAVE_ARCH_STACKLEAK |
9e8084d3 | 164 | select HAVE_ARCH_THREAD_STRUCT_WHITELIST |
8c2c3df3 | 165 | select HAVE_ARCH_TRACEHOOK |
8ee70879 | 166 | select HAVE_ARCH_TRANSPARENT_HUGEPAGE |
e3067861 | 167 | select HAVE_ARCH_VMAP_STACK |
8ee70879 | 168 | select HAVE_ARM_SMCCC |
2ff2b7ec | 169 | select HAVE_ASM_MODVERSIONS |
6077776b | 170 | select HAVE_EBPF_JIT |
af64d2aa | 171 | select HAVE_C_RECORDMCOUNT |
5284e1b4 | 172 | select HAVE_CMPXCHG_DOUBLE |
95eff6b2 | 173 | select HAVE_CMPXCHG_LOCAL |
8ee70879 | 174 | select HAVE_CONTEXT_TRACKING |
b69ec42b | 175 | select HAVE_DEBUG_KMEMLEAK |
6ac2104d | 176 | select HAVE_DMA_CONTIGUOUS |
bd7d38db | 177 | select HAVE_DYNAMIC_FTRACE |
3b23e499 TD |
178 | select HAVE_DYNAMIC_FTRACE_WITH_REGS \ |
179 | if $(cc-option,-fpatchable-function-entry=2) | |
a31d793d ST |
180 | select FTRACE_MCOUNT_USE_PATCHABLE_FUNCTION_ENTRY \ |
181 | if DYNAMIC_FTRACE_WITH_REGS | |
50afc33a | 182 | select HAVE_EFFICIENT_UNALIGNED_ACCESS |
67a929e0 | 183 | select HAVE_FAST_GUP |
af64d2aa | 184 | select HAVE_FTRACE_MCOUNT_RECORD |
819e50e2 | 185 | select HAVE_FUNCTION_TRACER |
42d038c4 | 186 | select HAVE_FUNCTION_ERROR_INJECTION |
819e50e2 | 187 | select HAVE_FUNCTION_GRAPH_TRACER |
6b90bd4b | 188 | select HAVE_GCC_PLUGINS |
8c2c3df3 | 189 | select HAVE_HW_BREAKPOINT if PERF_EVENTS |
24da208d | 190 | select HAVE_IRQ_TIME_ACCOUNTING |
e26bb75a | 191 | select HAVE_KVM |
396a5d4a | 192 | select HAVE_NMI |
55834a77 | 193 | select HAVE_PATA_PLATFORM |
8c2c3df3 | 194 | select HAVE_PERF_EVENTS |
2ee0d7fd JP |
195 | select HAVE_PERF_REGS |
196 | select HAVE_PERF_USER_STACK_DUMP | |
1b2d3451 | 197 | select HAVE_PREEMPT_DYNAMIC_KEY |
0a8ea52c | 198 | select HAVE_REGS_AND_STACK_ACCESS_API |
a68773bd | 199 | select HAVE_POSIX_CPU_TIMERS_TASK_WORK |
a823c35f | 200 | select HAVE_FUNCTION_ARG_ACCESS_API |
ff2e6d72 | 201 | select MMU_GATHER_RCU_TABLE_FREE |
409d5db4 | 202 | select HAVE_RSEQ |
d148eac0 | 203 | select HAVE_STACKPROTECTOR |
055b1212 | 204 | select HAVE_SYSCALL_TRACEPOINTS |
2dd0e8d2 | 205 | select HAVE_KPROBES |
cd1ee3b1 | 206 | select HAVE_KRETPROBES |
28b1a824 | 207 | select HAVE_GENERIC_VDSO |
876945db | 208 | select IOMMU_DMA if IOMMU_SUPPORT |
8c2c3df3 | 209 | select IRQ_DOMAIN |
e8557d1f | 210 | select IRQ_FORCED_THREADING |
f6f37d93 | 211 | select KASAN_VMALLOC if KASAN |
fea2acaa | 212 | select MODULES_USE_ELF_RELA |
f616ab59 | 213 | select NEED_DMA_MAP_STATE |
86596f0a | 214 | select NEED_SG_DMA_LENGTH |
8c2c3df3 CM |
215 | select OF |
216 | select OF_EARLY_FLATTREE | |
2eac9c2d | 217 | select PCI_DOMAINS_GENERIC if PCI |
52146173 | 218 | select PCI_ECAM if (ACPI && PCI) |
20f1b79d | 219 | select PCI_SYSCALL if PCI |
aa1e8ec1 CM |
220 | select POWER_RESET |
221 | select POWER_SUPPLY | |
8c2c3df3 | 222 | select SPARSE_IRQ |
09230cbc | 223 | select SWIOTLB |
7ac57a89 | 224 | select SYSCTL_EXCEPTION_TRACE |
c02433dd | 225 | select THREAD_INFO_IN_TASK |
7677f7fd | 226 | select HAVE_ARCH_USERFAULTFD_MINOR if USERFAULTFD |
4aae683f | 227 | select TRACE_IRQFLAGS_SUPPORT |
8c2c3df3 CM |
228 | help |
229 | ARM 64-bit (AArch64) Linux support. | |
230 | ||
231 | config 64BIT | |
232 | def_bool y | |
233 | ||
8c2c3df3 CM |
234 | config MMU |
235 | def_bool y | |
236 | ||
030c4d24 MR |
237 | config ARM64_PAGE_SHIFT |
238 | int | |
239 | default 16 if ARM64_64K_PAGES | |
240 | default 14 if ARM64_16K_PAGES | |
241 | default 12 | |
242 | ||
c0d6de32 | 243 | config ARM64_CONT_PTE_SHIFT |
030c4d24 MR |
244 | int |
245 | default 5 if ARM64_64K_PAGES | |
246 | default 7 if ARM64_16K_PAGES | |
247 | default 4 | |
248 | ||
e6765941 GS |
249 | config ARM64_CONT_PMD_SHIFT |
250 | int | |
251 | default 5 if ARM64_64K_PAGES | |
252 | default 5 if ARM64_16K_PAGES | |
253 | default 4 | |
254 | ||
8f0d3aa9 DC |
255 | config ARCH_MMAP_RND_BITS_MIN |
256 | default 14 if ARM64_64K_PAGES | |
257 | default 16 if ARM64_16K_PAGES | |
258 | default 18 | |
259 | ||
260 | # max bits determined by the following formula: | |
261 | # VA_BITS - PAGE_SHIFT - 3 | |
262 | config ARCH_MMAP_RND_BITS_MAX | |
263 | default 19 if ARM64_VA_BITS=36 | |
264 | default 24 if ARM64_VA_BITS=39 | |
265 | default 27 if ARM64_VA_BITS=42 | |
266 | default 30 if ARM64_VA_BITS=47 | |
267 | default 29 if ARM64_VA_BITS=48 && ARM64_64K_PAGES | |
268 | default 31 if ARM64_VA_BITS=48 && ARM64_16K_PAGES | |
269 | default 33 if ARM64_VA_BITS=48 | |
270 | default 14 if ARM64_64K_PAGES | |
271 | default 16 if ARM64_16K_PAGES | |
272 | default 18 | |
273 | ||
274 | config ARCH_MMAP_RND_COMPAT_BITS_MIN | |
275 | default 7 if ARM64_64K_PAGES | |
276 | default 9 if ARM64_16K_PAGES | |
277 | default 11 | |
278 | ||
279 | config ARCH_MMAP_RND_COMPAT_BITS_MAX | |
280 | default 16 | |
281 | ||
ce816fa8 | 282 | config NO_IOPORT_MAP |
d1e6dc91 | 283 | def_bool y if !PCI |
8c2c3df3 CM |
284 | |
285 | config STACKTRACE_SUPPORT | |
286 | def_bool y | |
287 | ||
bf0c4e04 JVS |
288 | config ILLEGAL_POINTER_VALUE |
289 | hex | |
290 | default 0xdead000000000000 | |
291 | ||
8c2c3df3 CM |
292 | config LOCKDEP_SUPPORT |
293 | def_bool y | |
294 | ||
9fb7410f DM |
295 | config GENERIC_BUG |
296 | def_bool y | |
297 | depends on BUG | |
298 | ||
299 | config GENERIC_BUG_RELATIVE_POINTERS | |
300 | def_bool y | |
301 | depends on GENERIC_BUG | |
302 | ||
8c2c3df3 CM |
303 | config GENERIC_HWEIGHT |
304 | def_bool y | |
305 | ||
306 | config GENERIC_CSUM | |
307 | def_bool y | |
308 | ||
309 | config GENERIC_CALIBRATE_DELAY | |
310 | def_bool y | |
311 | ||
ca6e51d5 OS |
312 | config ARCH_MHP_MEMMAP_ON_MEMORY_ENABLE |
313 | def_bool y | |
314 | ||
4b3dc967 WD |
315 | config SMP |
316 | def_bool y | |
317 | ||
4cfb3613 AB |
318 | config KERNEL_MODE_NEON |
319 | def_bool y | |
320 | ||
92cc15fc RH |
321 | config FIX_EARLYCON_MEM |
322 | def_bool y | |
323 | ||
9f25e6ad KS |
324 | config PGTABLE_LEVELS |
325 | int | |
21539939 | 326 | default 2 if ARM64_16K_PAGES && ARM64_VA_BITS_36 |
9f25e6ad | 327 | default 2 if ARM64_64K_PAGES && ARM64_VA_BITS_42 |
b6d00d47 | 328 | default 3 if ARM64_64K_PAGES && (ARM64_VA_BITS_48 || ARM64_VA_BITS_52) |
9f25e6ad | 329 | default 3 if ARM64_4K_PAGES && ARM64_VA_BITS_39 |
44eaacf1 SP |
330 | default 3 if ARM64_16K_PAGES && ARM64_VA_BITS_47 |
331 | default 4 if !ARM64_64K_PAGES && ARM64_VA_BITS_48 | |
9f25e6ad | 332 | |
9842ceae PA |
333 | config ARCH_SUPPORTS_UPROBES |
334 | def_bool y | |
335 | ||
8f360948 AB |
336 | config ARCH_PROC_KCORE_TEXT |
337 | def_bool y | |
338 | ||
8bf9284d VM |
339 | config BROKEN_GAS_INST |
340 | def_bool !$(as-instr,1:\n.inst 0\n.rept . - 1b\n\nnop\n.endr\n) | |
341 | ||
6bd1d0be SC |
342 | config KASAN_SHADOW_OFFSET |
343 | hex | |
0fea6e9a | 344 | depends on KASAN_GENERIC || KASAN_SW_TAGS |
f4693c27 AB |
345 | default 0xdfff800000000000 if (ARM64_VA_BITS_48 || ARM64_VA_BITS_52) && !KASAN_SW_TAGS |
346 | default 0xdfffc00000000000 if ARM64_VA_BITS_47 && !KASAN_SW_TAGS | |
347 | default 0xdffffe0000000000 if ARM64_VA_BITS_42 && !KASAN_SW_TAGS | |
348 | default 0xdfffffc000000000 if ARM64_VA_BITS_39 && !KASAN_SW_TAGS | |
349 | default 0xdffffff800000000 if ARM64_VA_BITS_36 && !KASAN_SW_TAGS | |
350 | default 0xefff800000000000 if (ARM64_VA_BITS_48 || ARM64_VA_BITS_52) && KASAN_SW_TAGS | |
351 | default 0xefffc00000000000 if ARM64_VA_BITS_47 && KASAN_SW_TAGS | |
352 | default 0xeffffe0000000000 if ARM64_VA_BITS_42 && KASAN_SW_TAGS | |
353 | default 0xefffffc000000000 if ARM64_VA_BITS_39 && KASAN_SW_TAGS | |
354 | default 0xeffffff800000000 if ARM64_VA_BITS_36 && KASAN_SW_TAGS | |
6bd1d0be SC |
355 | default 0xffffffffffffffff |
356 | ||
6a377491 | 357 | source "arch/arm64/Kconfig.platforms" |
8c2c3df3 | 358 | |
8c2c3df3 CM |
359 | menu "Kernel Features" |
360 | ||
c0a01b84 AP |
361 | menu "ARM errata workarounds via the alternatives framework" |
362 | ||
c9460dcb | 363 | config ARM64_WORKAROUND_CLEAN_CACHE |
bc15cf70 | 364 | bool |
c9460dcb | 365 | |
c0a01b84 AP |
366 | config ARM64_ERRATUM_826319 |
367 | bool "Cortex-A53: 826319: System might deadlock if a write cannot complete until read data is accepted" | |
368 | default y | |
c9460dcb | 369 | select ARM64_WORKAROUND_CLEAN_CACHE |
c0a01b84 AP |
370 | help |
371 | This option adds an alternative code sequence to work around ARM | |
372 | erratum 826319 on Cortex-A53 parts up to r0p2 with an AMBA 4 ACE or | |
373 | AXI master interface and an L2 cache. | |
374 | ||
375 | If a Cortex-A53 uses an AMBA AXI4 ACE interface to other processors | |
376 | and is unable to accept a certain write via this interface, it will | |
377 | not progress on read data presented on the read data channel and the | |
378 | system can deadlock. | |
379 | ||
380 | The workaround promotes data cache clean instructions to | |
381 | data cache clean-and-invalidate. | |
382 | Please note that this does not necessarily enable the workaround, | |
383 | as it depends on the alternative framework, which will only patch | |
384 | the kernel if an affected CPU is detected. | |
385 | ||
386 | If unsure, say Y. | |
387 | ||
388 | config ARM64_ERRATUM_827319 | |
389 | bool "Cortex-A53: 827319: Data cache clean instructions might cause overlapping transactions to the interconnect" | |
390 | default y | |
c9460dcb | 391 | select ARM64_WORKAROUND_CLEAN_CACHE |
c0a01b84 AP |
392 | help |
393 | This option adds an alternative code sequence to work around ARM | |
394 | erratum 827319 on Cortex-A53 parts up to r0p2 with an AMBA 5 CHI | |
395 | master interface and an L2 cache. | |
396 | ||
397 | Under certain conditions this erratum can cause a clean line eviction | |
398 | to occur at the same time as another transaction to the same address | |
399 | on the AMBA 5 CHI interface, which can cause data corruption if the | |
400 | interconnect reorders the two transactions. | |
401 | ||
402 | The workaround promotes data cache clean instructions to | |
403 | data cache clean-and-invalidate. | |
404 | Please note that this does not necessarily enable the workaround, | |
405 | as it depends on the alternative framework, which will only patch | |
406 | the kernel if an affected CPU is detected. | |
407 | ||
408 | If unsure, say Y. | |
409 | ||
410 | config ARM64_ERRATUM_824069 | |
411 | bool "Cortex-A53: 824069: Cache line might not be marked as clean after a CleanShared snoop" | |
412 | default y | |
c9460dcb | 413 | select ARM64_WORKAROUND_CLEAN_CACHE |
c0a01b84 AP |
414 | help |
415 | This option adds an alternative code sequence to work around ARM | |
416 | erratum 824069 on Cortex-A53 parts up to r0p2 when it is connected | |
417 | to a coherent interconnect. | |
418 | ||
419 | If a Cortex-A53 processor is executing a store or prefetch for | |
420 | write instruction at the same time as a processor in another | |
421 | cluster is executing a cache maintenance operation to the same | |
422 | address, then this erratum might cause a clean cache line to be | |
423 | incorrectly marked as dirty. | |
424 | ||
425 | The workaround promotes data cache clean instructions to | |
426 | data cache clean-and-invalidate. | |
427 | Please note that this option does not necessarily enable the | |
428 | workaround, as it depends on the alternative framework, which will | |
429 | only patch the kernel if an affected CPU is detected. | |
430 | ||
431 | If unsure, say Y. | |
432 | ||
433 | config ARM64_ERRATUM_819472 | |
434 | bool "Cortex-A53: 819472: Store exclusive instructions might cause data corruption" | |
435 | default y | |
c9460dcb | 436 | select ARM64_WORKAROUND_CLEAN_CACHE |
c0a01b84 AP |
437 | help |
438 | This option adds an alternative code sequence to work around ARM | |
439 | erratum 819472 on Cortex-A53 parts up to r0p1 with an L2 cache | |
440 | present when it is connected to a coherent interconnect. | |
441 | ||
442 | If the processor is executing a load and store exclusive sequence at | |
443 | the same time as a processor in another cluster is executing a cache | |
444 | maintenance operation to the same address, then this erratum might | |
445 | cause data corruption. | |
446 | ||
447 | The workaround promotes data cache clean instructions to | |
448 | data cache clean-and-invalidate. | |
449 | Please note that this does not necessarily enable the workaround, | |
450 | as it depends on the alternative framework, which will only patch | |
451 | the kernel if an affected CPU is detected. | |
452 | ||
453 | If unsure, say Y. | |
454 | ||
455 | config ARM64_ERRATUM_832075 | |
456 | bool "Cortex-A57: 832075: possible deadlock on mixing exclusive memory accesses with device loads" | |
457 | default y | |
458 | help | |
459 | This option adds an alternative code sequence to work around ARM | |
460 | erratum 832075 on Cortex-A57 parts up to r1p2. | |
461 | ||
462 | Affected Cortex-A57 parts might deadlock when exclusive load/store | |
463 | instructions to Write-Back memory are mixed with Device loads. | |
464 | ||
465 | The workaround is to promote device loads to use Load-Acquire | |
466 | semantics. | |
467 | Please note that this does not necessarily enable the workaround, | |
498cd5c3 MZ |
468 | as it depends on the alternative framework, which will only patch |
469 | the kernel if an affected CPU is detected. | |
470 | ||
471 | If unsure, say Y. | |
472 | ||
473 | config ARM64_ERRATUM_834220 | |
474 | bool "Cortex-A57: 834220: Stage 2 translation fault might be incorrectly reported in presence of a Stage 1 fault" | |
475 | depends on KVM | |
476 | default y | |
477 | help | |
478 | This option adds an alternative code sequence to work around ARM | |
479 | erratum 834220 on Cortex-A57 parts up to r1p2. | |
480 | ||
481 | Affected Cortex-A57 parts might report a Stage 2 translation | |
482 | fault as the result of a Stage 1 fault for load crossing a | |
483 | page boundary when there is a permission or device memory | |
484 | alignment fault at Stage 1 and a translation fault at Stage 2. | |
485 | ||
486 | The workaround is to verify that the Stage 1 translation | |
487 | doesn't generate a fault before handling the Stage 2 fault. | |
488 | Please note that this does not necessarily enable the workaround, | |
c0a01b84 AP |
489 | as it depends on the alternative framework, which will only patch |
490 | the kernel if an affected CPU is detected. | |
491 | ||
492 | If unsure, say Y. | |
493 | ||
905e8c5d WD |
494 | config ARM64_ERRATUM_845719 |
495 | bool "Cortex-A53: 845719: a load might read incorrect data" | |
496 | depends on COMPAT | |
497 | default y | |
498 | help | |
499 | This option adds an alternative code sequence to work around ARM | |
500 | erratum 845719 on Cortex-A53 parts up to r0p4. | |
501 | ||
502 | When running a compat (AArch32) userspace on an affected Cortex-A53 | |
503 | part, a load at EL0 from a virtual address that matches the bottom 32 | |
504 | bits of the virtual address used by a recent load at (AArch64) EL1 | |
505 | might return incorrect data. | |
506 | ||
507 | The workaround is to write the contextidr_el1 register on exception | |
508 | return to a 32-bit task. | |
509 | Please note that this does not necessarily enable the workaround, | |
510 | as it depends on the alternative framework, which will only patch | |
511 | the kernel if an affected CPU is detected. | |
512 | ||
513 | If unsure, say Y. | |
514 | ||
df057cc7 WD |
515 | config ARM64_ERRATUM_843419 |
516 | bool "Cortex-A53: 843419: A load or store might access an incorrect address" | |
df057cc7 | 517 | default y |
a257e025 | 518 | select ARM64_MODULE_PLTS if MODULES |
df057cc7 | 519 | help |
6ffe9923 | 520 | This option links the kernel with '--fix-cortex-a53-843419' and |
a257e025 AB |
521 | enables PLT support to replace certain ADRP instructions, which can |
522 | cause subsequent memory accesses to use an incorrect address on | |
523 | Cortex-A53 parts up to r0p4. | |
df057cc7 WD |
524 | |
525 | If unsure, say Y. | |
526 | ||
987fdfec MY |
527 | config ARM64_LD_HAS_FIX_ERRATUM_843419 |
528 | def_bool $(ld-option,--fix-cortex-a53-843419) | |
529 | ||
ece1397c SP |
530 | config ARM64_ERRATUM_1024718 |
531 | bool "Cortex-A55: 1024718: Update of DBM/AP bits without break before make might result in incorrect update" | |
532 | default y | |
533 | help | |
bc15cf70 | 534 | This option adds a workaround for ARM Cortex-A55 Erratum 1024718. |
ece1397c | 535 | |
c0b15c25 | 536 | Affected Cortex-A55 cores (all revisions) could cause incorrect |
ece1397c | 537 | update of the hardware dirty bit when the DBM/AP bits are updated |
bc15cf70 | 538 | without a break-before-make. The workaround is to disable the usage |
ece1397c | 539 | of hardware DBM locally on the affected cores. CPUs not affected by |
bc15cf70 | 540 | this erratum will continue to use the feature. |
df057cc7 WD |
541 | |
542 | If unsure, say Y. | |
543 | ||
a5325089 | 544 | config ARM64_ERRATUM_1418040 |
6989303a | 545 | bool "Cortex-A76/Neoverse-N1: MRC read following MRRC read of specific Generic Timer in AArch32 might give incorrect result" |
95b861a4 | 546 | default y |
c2b5bba3 | 547 | depends on COMPAT |
95b861a4 | 548 | help |
24cf262d | 549 | This option adds a workaround for ARM Cortex-A76/Neoverse-N1 |
a5325089 | 550 | errata 1188873 and 1418040. |
95b861a4 | 551 | |
a5325089 | 552 | Affected Cortex-A76/Neoverse-N1 cores (r0p0 to r3p1) could |
6989303a MZ |
553 | cause register corruption when accessing the timer registers |
554 | from AArch32 userspace. | |
95b861a4 MZ |
555 | |
556 | If unsure, say Y. | |
557 | ||
02ab1f50 | 558 | config ARM64_WORKAROUND_SPECULATIVE_AT |
e85d68fa SP |
559 | bool |
560 | ||
a457b0f7 | 561 | config ARM64_ERRATUM_1165522 |
02ab1f50 | 562 | bool "Cortex-A76: 1165522: Speculative AT instruction using out-of-context translation regime could cause subsequent request to generate an incorrect translation" |
a457b0f7 | 563 | default y |
02ab1f50 | 564 | select ARM64_WORKAROUND_SPECULATIVE_AT |
a457b0f7 | 565 | help |
bc15cf70 | 566 | This option adds a workaround for ARM Cortex-A76 erratum 1165522. |
a457b0f7 MZ |
567 | |
568 | Affected Cortex-A76 cores (r0p0, r1p0, r2p0) could end-up with | |
569 | corrupted TLBs by speculating an AT instruction during a guest | |
570 | context switch. | |
571 | ||
572 | If unsure, say Y. | |
573 | ||
02ab1f50 AS |
574 | config ARM64_ERRATUM_1319367 |
575 | bool "Cortex-A57/A72: 1319537: Speculative AT instruction using out-of-context translation regime could cause subsequent request to generate an incorrect translation" | |
576 | default y | |
577 | select ARM64_WORKAROUND_SPECULATIVE_AT | |
578 | help | |
579 | This option adds work arounds for ARM Cortex-A57 erratum 1319537 | |
580 | and A72 erratum 1319367 | |
581 | ||
582 | Cortex-A57 and A72 cores could end-up with corrupted TLBs by | |
583 | speculating an AT instruction during a guest context switch. | |
584 | ||
585 | If unsure, say Y. | |
586 | ||
275fa0ea | 587 | config ARM64_ERRATUM_1530923 |
02ab1f50 | 588 | bool "Cortex-A55: 1530923: Speculative AT instruction using out-of-context translation regime could cause subsequent request to generate an incorrect translation" |
275fa0ea | 589 | default y |
02ab1f50 | 590 | select ARM64_WORKAROUND_SPECULATIVE_AT |
275fa0ea SP |
591 | help |
592 | This option adds a workaround for ARM Cortex-A55 erratum 1530923. | |
593 | ||
594 | Affected Cortex-A55 cores (r0p0, r0p1, r1p0, r2p0) could end-up with | |
595 | corrupted TLBs by speculating an AT instruction during a guest | |
596 | context switch. | |
597 | ||
598 | If unsure, say Y. | |
a457b0f7 | 599 | |
ebcea694 GU |
600 | config ARM64_WORKAROUND_REPEAT_TLBI |
601 | bool | |
602 | ||
ce8c80c5 CM |
603 | config ARM64_ERRATUM_1286807 |
604 | bool "Cortex-A76: Modification of the translation table for a virtual address might lead to read-after-read ordering violation" | |
605 | default y | |
606 | select ARM64_WORKAROUND_REPEAT_TLBI | |
607 | help | |
bc15cf70 | 608 | This option adds a workaround for ARM Cortex-A76 erratum 1286807. |
ce8c80c5 CM |
609 | |
610 | On the affected Cortex-A76 cores (r0p0 to r3p0), if a virtual | |
611 | address for a cacheable mapping of a location is being | |
612 | accessed by a core while another core is remapping the virtual | |
613 | address to a new physical page using the recommended | |
614 | break-before-make sequence, then under very rare circumstances | |
615 | TLBI+DSB completes before a read using the translation being | |
616 | invalidated has been observed by other observers. The | |
617 | workaround repeats the TLBI+DSB operation. | |
618 | ||
969f5ea6 WD |
619 | config ARM64_ERRATUM_1463225 |
620 | bool "Cortex-A76: Software Step might prevent interrupt recognition" | |
621 | default y | |
622 | help | |
623 | This option adds a workaround for Arm Cortex-A76 erratum 1463225. | |
624 | ||
625 | On the affected Cortex-A76 cores (r0p0 to r3p1), software stepping | |
626 | of a system call instruction (SVC) can prevent recognition of | |
627 | subsequent interrupts when software stepping is disabled in the | |
628 | exception handler of the system call and either kernel debugging | |
629 | is enabled or VHE is in use. | |
630 | ||
631 | Work around the erratum by triggering a dummy step exception | |
632 | when handling a system call from a task that is being stepped | |
633 | in a VHE configuration of the kernel. | |
634 | ||
635 | If unsure, say Y. | |
636 | ||
05460849 JM |
637 | config ARM64_ERRATUM_1542419 |
638 | bool "Neoverse-N1: workaround mis-ordering of instruction fetches" | |
639 | default y | |
640 | help | |
641 | This option adds a workaround for ARM Neoverse-N1 erratum | |
642 | 1542419. | |
643 | ||
644 | Affected Neoverse-N1 cores could execute a stale instruction when | |
645 | modified by another CPU. The workaround depends on a firmware | |
646 | counterpart. | |
647 | ||
648 | Workaround the issue by hiding the DIC feature from EL0. This | |
649 | forces user-space to perform cache maintenance. | |
650 | ||
651 | If unsure, say Y. | |
652 | ||
96d389ca RH |
653 | config ARM64_ERRATUM_1508412 |
654 | bool "Cortex-A77: 1508412: workaround deadlock on sequence of NC/Device load and store exclusive or PAR read" | |
655 | default y | |
656 | help | |
657 | This option adds a workaround for Arm Cortex-A77 erratum 1508412. | |
658 | ||
659 | Affected Cortex-A77 cores (r0p0, r1p0) could deadlock on a sequence | |
660 | of a store-exclusive or read of PAR_EL1 and a load with device or | |
661 | non-cacheable memory attributes. The workaround depends on a firmware | |
662 | counterpart. | |
663 | ||
664 | KVM guests must also have the workaround implemented or they can | |
665 | deadlock the system. | |
666 | ||
667 | Work around the issue by inserting DMB SY barriers around PAR_EL1 | |
668 | register reads and warning KVM users. The DMB barrier is sufficient | |
669 | to prevent a speculative PAR_EL1 read. | |
670 | ||
671 | If unsure, say Y. | |
672 | ||
b9d216fc SP |
673 | config ARM64_WORKAROUND_TRBE_OVERWRITE_FILL_MODE |
674 | bool | |
675 | ||
297ae1eb JM |
676 | config ARM64_ERRATUM_2051678 |
677 | bool "Cortex-A510: 2051678: disable Hardware Update of the page table dirty bit" | |
a4b92ceb | 678 | default y |
297ae1eb JM |
679 | help |
680 | This options adds the workaround for ARM Cortex-A510 erratum ARM64_ERRATUM_2051678. | |
681 | Affected Coretex-A510 might not respect the ordering rules for | |
682 | hardware update of the page table's dirty bit. The workaround | |
683 | is to not enable the feature on affected CPUs. | |
684 | ||
685 | If unsure, say Y. | |
686 | ||
1dd498e5 JM |
687 | config ARM64_ERRATUM_2077057 |
688 | bool "Cortex-A510: 2077057: workaround software-step corrupting SPSR_EL2" | |
4c11113c | 689 | default y |
1dd498e5 JM |
690 | help |
691 | This option adds the workaround for ARM Cortex-A510 erratum 2077057. | |
692 | Affected Cortex-A510 may corrupt SPSR_EL2 when the a step exception is | |
693 | expected, but a Pointer Authentication trap is taken instead. The | |
694 | erratum causes SPSR_EL1 to be copied to SPSR_EL2, which could allow | |
695 | EL1 to cause a return to EL2 with a guest controlled ELR_EL2. | |
696 | ||
697 | This can only happen when EL2 is stepping EL1. | |
698 | ||
699 | When these conditions occur, the SPSR_EL2 value is unchanged from the | |
700 | previous guest entry, and can be restored from the in-memory copy. | |
701 | ||
702 | If unsure, say Y. | |
703 | ||
b9d216fc | 704 | config ARM64_ERRATUM_2119858 |
eb30d838 | 705 | bool "Cortex-A710/X2: 2119858: workaround TRBE overwriting trace data in FILL mode" |
b9d216fc | 706 | default y |
b9d216fc SP |
707 | depends on CORESIGHT_TRBE |
708 | select ARM64_WORKAROUND_TRBE_OVERWRITE_FILL_MODE | |
709 | help | |
eb30d838 | 710 | This option adds the workaround for ARM Cortex-A710/X2 erratum 2119858. |
b9d216fc | 711 | |
eb30d838 | 712 | Affected Cortex-A710/X2 cores could overwrite up to 3 cache lines of trace |
b9d216fc SP |
713 | data at the base of the buffer (pointed to by TRBASER_EL1) in FILL mode in |
714 | the event of a WRAP event. | |
715 | ||
716 | Work around the issue by always making sure we move the TRBPTR_EL1 by | |
717 | 256 bytes before enabling the buffer and filling the first 256 bytes of | |
718 | the buffer with ETM ignore packets upon disabling. | |
719 | ||
720 | If unsure, say Y. | |
721 | ||
722 | config ARM64_ERRATUM_2139208 | |
723 | bool "Neoverse-N2: 2139208: workaround TRBE overwriting trace data in FILL mode" | |
724 | default y | |
b9d216fc SP |
725 | depends on CORESIGHT_TRBE |
726 | select ARM64_WORKAROUND_TRBE_OVERWRITE_FILL_MODE | |
727 | help | |
728 | This option adds the workaround for ARM Neoverse-N2 erratum 2139208. | |
729 | ||
730 | Affected Neoverse-N2 cores could overwrite up to 3 cache lines of trace | |
731 | data at the base of the buffer (pointed to by TRBASER_EL1) in FILL mode in | |
732 | the event of a WRAP event. | |
733 | ||
734 | Work around the issue by always making sure we move the TRBPTR_EL1 by | |
735 | 256 bytes before enabling the buffer and filling the first 256 bytes of | |
736 | the buffer with ETM ignore packets upon disabling. | |
737 | ||
738 | If unsure, say Y. | |
739 | ||
fa82d0b4 SP |
740 | config ARM64_WORKAROUND_TSB_FLUSH_FAILURE |
741 | bool | |
742 | ||
743 | config ARM64_ERRATUM_2054223 | |
744 | bool "Cortex-A710: 2054223: workaround TSB instruction failing to flush trace" | |
745 | default y | |
746 | select ARM64_WORKAROUND_TSB_FLUSH_FAILURE | |
747 | help | |
748 | Enable workaround for ARM Cortex-A710 erratum 2054223 | |
749 | ||
750 | Affected cores may fail to flush the trace data on a TSB instruction, when | |
751 | the PE is in trace prohibited state. This will cause losing a few bytes | |
752 | of the trace cached. | |
753 | ||
754 | Workaround is to issue two TSB consecutively on affected cores. | |
755 | ||
756 | If unsure, say Y. | |
757 | ||
758 | config ARM64_ERRATUM_2067961 | |
759 | bool "Neoverse-N2: 2067961: workaround TSB instruction failing to flush trace" | |
760 | default y | |
761 | select ARM64_WORKAROUND_TSB_FLUSH_FAILURE | |
762 | help | |
763 | Enable workaround for ARM Neoverse-N2 erratum 2067961 | |
764 | ||
765 | Affected cores may fail to flush the trace data on a TSB instruction, when | |
766 | the PE is in trace prohibited state. This will cause losing a few bytes | |
767 | of the trace cached. | |
768 | ||
769 | Workaround is to issue two TSB consecutively on affected cores. | |
770 | ||
771 | If unsure, say Y. | |
772 | ||
8d81b2a3 SP |
773 | config ARM64_WORKAROUND_TRBE_WRITE_OUT_OF_RANGE |
774 | bool | |
775 | ||
776 | config ARM64_ERRATUM_2253138 | |
777 | bool "Neoverse-N2: 2253138: workaround TRBE writing to address out-of-range" | |
8d81b2a3 SP |
778 | depends on CORESIGHT_TRBE |
779 | default y | |
780 | select ARM64_WORKAROUND_TRBE_WRITE_OUT_OF_RANGE | |
781 | help | |
782 | This option adds the workaround for ARM Neoverse-N2 erratum 2253138. | |
783 | ||
784 | Affected Neoverse-N2 cores might write to an out-of-range address, not reserved | |
785 | for TRBE. Under some conditions, the TRBE might generate a write to the next | |
786 | virtually addressed page following the last page of the TRBE address space | |
787 | (i.e., the TRBLIMITR_EL1.LIMIT), instead of wrapping around to the base. | |
788 | ||
789 | Work around this in the driver by always making sure that there is a | |
790 | page beyond the TRBLIMITR_EL1.LIMIT, within the space allowed for the TRBE. | |
791 | ||
792 | If unsure, say Y. | |
793 | ||
794 | config ARM64_ERRATUM_2224489 | |
eb30d838 | 795 | bool "Cortex-A710/X2: 2224489: workaround TRBE writing to address out-of-range" |
8d81b2a3 SP |
796 | depends on CORESIGHT_TRBE |
797 | default y | |
798 | select ARM64_WORKAROUND_TRBE_WRITE_OUT_OF_RANGE | |
799 | help | |
eb30d838 | 800 | This option adds the workaround for ARM Cortex-A710/X2 erratum 2224489. |
8d81b2a3 | 801 | |
eb30d838 | 802 | Affected Cortex-A710/X2 cores might write to an out-of-range address, not reserved |
8d81b2a3 SP |
803 | for TRBE. Under some conditions, the TRBE might generate a write to the next |
804 | virtually addressed page following the last page of the TRBE address space | |
805 | (i.e., the TRBLIMITR_EL1.LIMIT), instead of wrapping around to the base. | |
806 | ||
807 | Work around this in the driver by always making sure that there is a | |
808 | page beyond the TRBLIMITR_EL1.LIMIT, within the space allowed for the TRBE. | |
809 | ||
810 | If unsure, say Y. | |
811 | ||
607a9afa AK |
812 | config ARM64_ERRATUM_2064142 |
813 | bool "Cortex-A510: 2064142: workaround TRBE register writes while disabled" | |
ac0ba210 | 814 | depends on CORESIGHT_TRBE |
607a9afa AK |
815 | default y |
816 | help | |
817 | This option adds the workaround for ARM Cortex-A510 erratum 2064142. | |
818 | ||
819 | Affected Cortex-A510 core might fail to write into system registers after the | |
820 | TRBE has been disabled. Under some conditions after the TRBE has been disabled | |
821 | writes into TRBE registers TRBLIMITR_EL1, TRBPTR_EL1, TRBBASER_EL1, TRBSR_EL1, | |
822 | and TRBTRG_EL1 will be ignored and will not be effected. | |
823 | ||
824 | Work around this in the driver by executing TSB CSYNC and DSB after collection | |
825 | is stopped and before performing a system register write to one of the affected | |
826 | registers. | |
827 | ||
828 | If unsure, say Y. | |
829 | ||
3bd94a87 AK |
830 | config ARM64_ERRATUM_2038923 |
831 | bool "Cortex-A510: 2038923: workaround TRBE corruption with enable" | |
f209e9fe | 832 | depends on CORESIGHT_TRBE |
3bd94a87 AK |
833 | default y |
834 | help | |
835 | This option adds the workaround for ARM Cortex-A510 erratum 2038923. | |
836 | ||
837 | Affected Cortex-A510 core might cause an inconsistent view on whether trace is | |
838 | prohibited within the CPU. As a result, the trace buffer or trace buffer state | |
839 | might be corrupted. This happens after TRBE buffer has been enabled by setting | |
840 | TRBLIMITR_EL1.E, followed by just a single context synchronization event before | |
841 | execution changes from a context, in which trace is prohibited to one where it | |
842 | isn't, or vice versa. In these mentioned conditions, the view of whether trace | |
843 | is prohibited is inconsistent between parts of the CPU, and the trace buffer or | |
844 | the trace buffer state might be corrupted. | |
845 | ||
846 | Work around this in the driver by preventing an inconsistent view of whether the | |
847 | trace is prohibited or not based on TRBLIMITR_EL1.E by immediately following a | |
848 | change to TRBLIMITR_EL1.E with at least one ISB instruction before an ERET, or | |
849 | two ISB instructions if no ERET is to take place. | |
850 | ||
851 | If unsure, say Y. | |
852 | ||
708e8af4 AK |
853 | config ARM64_ERRATUM_1902691 |
854 | bool "Cortex-A510: 1902691: workaround TRBE trace corruption" | |
3a828845 | 855 | depends on CORESIGHT_TRBE |
708e8af4 AK |
856 | default y |
857 | help | |
858 | This option adds the workaround for ARM Cortex-A510 erratum 1902691. | |
859 | ||
860 | Affected Cortex-A510 core might cause trace data corruption, when being written | |
861 | into the memory. Effectively TRBE is broken and hence cannot be used to capture | |
862 | trace data. | |
863 | ||
864 | Work around this problem in the driver by just preventing TRBE initialization on | |
865 | affected cpus. The firmware must have disabled the access to TRBE for the kernel | |
866 | on such implementations. This will cover the kernel for any firmware that doesn't | |
867 | do this already. | |
868 | ||
869 | If unsure, say Y. | |
870 | ||
94100970 RR |
871 | config CAVIUM_ERRATUM_22375 |
872 | bool "Cavium erratum 22375, 24313" | |
873 | default y | |
874 | help | |
bc15cf70 | 875 | Enable workaround for errata 22375 and 24313. |
94100970 RR |
876 | |
877 | This implements two gicv3-its errata workarounds for ThunderX. Both | |
bc15cf70 | 878 | with a small impact affecting only ITS table allocation. |
94100970 RR |
879 | |
880 | erratum 22375: only alloc 8MB table size | |
881 | erratum 24313: ignore memory access type | |
882 | ||
883 | The fixes are in ITS initialization and basically ignore memory access | |
884 | type and table size provided by the TYPER and BASER registers. | |
885 | ||
886 | If unsure, say Y. | |
887 | ||
fbf8f40e GK |
888 | config CAVIUM_ERRATUM_23144 |
889 | bool "Cavium erratum 23144: ITS SYNC hang on dual socket system" | |
890 | depends on NUMA | |
891 | default y | |
892 | help | |
893 | ITS SYNC command hang for cross node io and collections/cpu mapping. | |
894 | ||
895 | If unsure, say Y. | |
896 | ||
6d4e11c5 | 897 | config CAVIUM_ERRATUM_23154 |
24a147bc | 898 | bool "Cavium errata 23154 and 38545: GICv3 lacks HW synchronisation" |
6d4e11c5 RR |
899 | default y |
900 | help | |
24a147bc | 901 | The ThunderX GICv3 implementation requires a modified version for |
6d4e11c5 RR |
902 | reading the IAR status to ensure data synchronization |
903 | (access to icc_iar1_el1 is not sync'ed before and after). | |
904 | ||
24a147bc LC |
905 | It also suffers from erratum 38545 (also present on Marvell's |
906 | OcteonTX and OcteonTX2), resulting in deactivated interrupts being | |
907 | spuriously presented to the CPU interface. | |
908 | ||
6d4e11c5 RR |
909 | If unsure, say Y. |
910 | ||
104a0c02 AP |
911 | config CAVIUM_ERRATUM_27456 |
912 | bool "Cavium erratum 27456: Broadcast TLBI instructions may cause icache corruption" | |
913 | default y | |
914 | help | |
915 | On ThunderX T88 pass 1.x through 2.1 parts, broadcast TLBI | |
916 | instructions may cause the icache to become corrupted if it | |
917 | contains data for a non-current ASID. The fix is to | |
918 | invalidate the icache when changing the mm context. | |
919 | ||
920 | If unsure, say Y. | |
921 | ||
690a3415 DD |
922 | config CAVIUM_ERRATUM_30115 |
923 | bool "Cavium erratum 30115: Guest may disable interrupts in host" | |
924 | default y | |
925 | help | |
926 | On ThunderX T88 pass 1.x through 2.2, T81 pass 1.0 through | |
927 | 1.2, and T83 Pass 1.0, KVM guest execution may disable | |
928 | interrupts in host. Trapping both GICv3 group-0 and group-1 | |
929 | accesses sidesteps the issue. | |
930 | ||
931 | If unsure, say Y. | |
932 | ||
603afdc9 MZ |
933 | config CAVIUM_TX2_ERRATUM_219 |
934 | bool "Cavium ThunderX2 erratum 219: PRFM between TTBR change and ISB fails" | |
935 | default y | |
936 | help | |
937 | On Cavium ThunderX2, a load, store or prefetch instruction between a | |
938 | TTBR update and the corresponding context synchronizing operation can | |
939 | cause a spurious Data Abort to be delivered to any hardware thread in | |
940 | the CPU core. | |
941 | ||
942 | Work around the issue by avoiding the problematic code sequence and | |
943 | trapping KVM guest TTBRx_EL1 writes to EL2 when SMT is enabled. The | |
944 | trap handler performs the corresponding register access, skips the | |
945 | instruction and ensures context synchronization by virtue of the | |
946 | exception return. | |
947 | ||
948 | If unsure, say Y. | |
949 | ||
ebcea694 GU |
950 | config FUJITSU_ERRATUM_010001 |
951 | bool "Fujitsu-A64FX erratum E#010001: Undefined fault may occur wrongly" | |
952 | default y | |
953 | help | |
954 | This option adds a workaround for Fujitsu-A64FX erratum E#010001. | |
955 | On some variants of the Fujitsu-A64FX cores ver(1.0, 1.1), memory | |
956 | accesses may cause undefined fault (Data abort, DFSC=0b111111). | |
957 | This fault occurs under a specific hardware condition when a | |
958 | load/store instruction performs an address translation using: | |
959 | case-1 TTBR0_EL1 with TCR_EL1.NFD0 == 1. | |
960 | case-2 TTBR0_EL2 with TCR_EL2.NFD0 == 1. | |
961 | case-3 TTBR1_EL1 with TCR_EL1.NFD1 == 1. | |
962 | case-4 TTBR1_EL2 with TCR_EL2.NFD1 == 1. | |
963 | ||
964 | The workaround is to ensure these bits are clear in TCR_ELx. | |
965 | The workaround only affects the Fujitsu-A64FX. | |
966 | ||
967 | If unsure, say Y. | |
968 | ||
969 | config HISILICON_ERRATUM_161600802 | |
970 | bool "Hip07 161600802: Erroneous redistributor VLPI base" | |
971 | default y | |
972 | help | |
973 | The HiSilicon Hip07 SoC uses the wrong redistributor base | |
974 | when issued ITS commands such as VMOVP and VMAPP, and requires | |
975 | a 128kB offset to be applied to the target address in this commands. | |
976 | ||
977 | If unsure, say Y. | |
978 | ||
38fd94b0 CC |
979 | config QCOM_FALKOR_ERRATUM_1003 |
980 | bool "Falkor E1003: Incorrect translation due to ASID change" | |
981 | default y | |
38fd94b0 CC |
982 | help |
983 | On Falkor v1, an incorrect ASID may be cached in the TLB when ASID | |
d1777e68 WD |
984 | and BADDR are changed together in TTBRx_EL1. Since we keep the ASID |
985 | in TTBR1_EL1, this situation only occurs in the entry trampoline and | |
986 | then only for entries in the walk cache, since the leaf translation | |
987 | is unchanged. Work around the erratum by invalidating the walk cache | |
988 | entries for the trampoline before entering the kernel proper. | |
38fd94b0 | 989 | |
d9ff80f8 CC |
990 | config QCOM_FALKOR_ERRATUM_1009 |
991 | bool "Falkor E1009: Prematurely complete a DSB after a TLBI" | |
992 | default y | |
ce8c80c5 | 993 | select ARM64_WORKAROUND_REPEAT_TLBI |
d9ff80f8 CC |
994 | help |
995 | On Falkor v1, the CPU may prematurely complete a DSB following a | |
996 | TLBI xxIS invalidate maintenance operation. Repeat the TLBI operation | |
997 | one more time to fix the issue. | |
998 | ||
999 | If unsure, say Y. | |
1000 | ||
90922a2d SD |
1001 | config QCOM_QDF2400_ERRATUM_0065 |
1002 | bool "QDF2400 E0065: Incorrect GITS_TYPER.ITT_Entry_size" | |
1003 | default y | |
1004 | help | |
1005 | On Qualcomm Datacenter Technologies QDF2400 SoC, ITS hardware reports | |
1006 | ITE size incorrectly. The GITS_TYPER.ITT_Entry_size field should have | |
1007 | been indicated as 16Bytes (0xf), not 8Bytes (0x7). | |
1008 | ||
1009 | If unsure, say Y. | |
1010 | ||
932b50c7 SD |
1011 | config QCOM_FALKOR_ERRATUM_E1041 |
1012 | bool "Falkor E1041: Speculative instruction fetches might cause errant memory access" | |
1013 | default y | |
1014 | help | |
1015 | Falkor CPU may speculatively fetch instructions from an improper | |
1016 | memory location when MMU translation is changed from SCTLR_ELn[M]=1 | |
1017 | to SCTLR_ELn[M]=0. Prefix an ISB instruction to fix the problem. | |
1018 | ||
1019 | If unsure, say Y. | |
1020 | ||
20109a85 RW |
1021 | config NVIDIA_CARMEL_CNP_ERRATUM |
1022 | bool "NVIDIA Carmel CNP: CNP on Carmel semantically different than ARM cores" | |
1023 | default y | |
1024 | help | |
1025 | If CNP is enabled on Carmel cores, non-sharable TLBIs on a core will not | |
1026 | invalidate shared TLB entries installed by a different core, as it would | |
1027 | on standard ARM cores. | |
1028 | ||
1029 | If unsure, say Y. | |
1030 | ||
ebcea694 GU |
1031 | config SOCIONEXT_SYNQUACER_PREITS |
1032 | bool "Socionext Synquacer: Workaround for GICv3 pre-ITS" | |
3e32131a ZL |
1033 | default y |
1034 | help | |
ebcea694 GU |
1035 | Socionext Synquacer SoCs implement a separate h/w block to generate |
1036 | MSI doorbell writes with non-zero values for the device ID. | |
3e32131a ZL |
1037 | |
1038 | If unsure, say Y. | |
1039 | ||
c0a01b84 AP |
1040 | endmenu |
1041 | ||
1042 | ||
e41ceed0 JL |
1043 | choice |
1044 | prompt "Page size" | |
1045 | default ARM64_4K_PAGES | |
1046 | help | |
1047 | Page size (translation granule) configuration. | |
1048 | ||
1049 | config ARM64_4K_PAGES | |
1050 | bool "4KB" | |
1051 | help | |
1052 | This feature enables 4KB pages support. | |
1053 | ||
44eaacf1 SP |
1054 | config ARM64_16K_PAGES |
1055 | bool "16KB" | |
1056 | help | |
1057 | The system will use 16KB pages support. AArch32 emulation | |
1058 | requires applications compiled with 16K (or a multiple of 16K) | |
1059 | aligned segments. | |
1060 | ||
8c2c3df3 | 1061 | config ARM64_64K_PAGES |
e41ceed0 | 1062 | bool "64KB" |
8c2c3df3 CM |
1063 | help |
1064 | This feature enables 64KB pages support (4KB by default) | |
1065 | allowing only two levels of page tables and faster TLB | |
db488be3 SP |
1066 | look-up. AArch32 emulation requires applications compiled |
1067 | with 64K aligned segments. | |
8c2c3df3 | 1068 | |
e41ceed0 JL |
1069 | endchoice |
1070 | ||
1071 | choice | |
1072 | prompt "Virtual address space size" | |
1073 | default ARM64_VA_BITS_39 if ARM64_4K_PAGES | |
44eaacf1 | 1074 | default ARM64_VA_BITS_47 if ARM64_16K_PAGES |
e41ceed0 JL |
1075 | default ARM64_VA_BITS_42 if ARM64_64K_PAGES |
1076 | help | |
1077 | Allows choosing one of multiple possible virtual address | |
1078 | space sizes. The level of translation table is determined by | |
1079 | a combination of page size and virtual address space size. | |
1080 | ||
21539939 | 1081 | config ARM64_VA_BITS_36 |
56a3f30e | 1082 | bool "36-bit" if EXPERT |
21539939 SP |
1083 | depends on ARM64_16K_PAGES |
1084 | ||
e41ceed0 JL |
1085 | config ARM64_VA_BITS_39 |
1086 | bool "39-bit" | |
1087 | depends on ARM64_4K_PAGES | |
1088 | ||
1089 | config ARM64_VA_BITS_42 | |
1090 | bool "42-bit" | |
1091 | depends on ARM64_64K_PAGES | |
1092 | ||
44eaacf1 SP |
1093 | config ARM64_VA_BITS_47 |
1094 | bool "47-bit" | |
1095 | depends on ARM64_16K_PAGES | |
1096 | ||
c79b954b JL |
1097 | config ARM64_VA_BITS_48 |
1098 | bool "48-bit" | |
c79b954b | 1099 | |
b6d00d47 SC |
1100 | config ARM64_VA_BITS_52 |
1101 | bool "52-bit" | |
68d23da4 WD |
1102 | depends on ARM64_64K_PAGES && (ARM64_PAN || !ARM64_SW_TTBR0_PAN) |
1103 | help | |
1104 | Enable 52-bit virtual addressing for userspace when explicitly | |
b6d00d47 SC |
1105 | requested via a hint to mmap(). The kernel will also use 52-bit |
1106 | virtual addresses for its own mappings (provided HW support for | |
1107 | this feature is available, otherwise it reverts to 48-bit). | |
68d23da4 WD |
1108 | |
1109 | NOTE: Enabling 52-bit virtual addressing in conjunction with | |
1110 | ARMv8.3 Pointer Authentication will result in the PAC being | |
1111 | reduced from 7 bits to 3 bits, which may have a significant | |
1112 | impact on its susceptibility to brute-force attacks. | |
1113 | ||
1114 | If unsure, select 48-bit virtual addressing instead. | |
1115 | ||
e41ceed0 JL |
1116 | endchoice |
1117 | ||
68d23da4 WD |
1118 | config ARM64_FORCE_52BIT |
1119 | bool "Force 52-bit virtual addresses for userspace" | |
b6d00d47 | 1120 | depends on ARM64_VA_BITS_52 && EXPERT |
68d23da4 WD |
1121 | help |
1122 | For systems with 52-bit userspace VAs enabled, the kernel will attempt | |
1123 | to maintain compatibility with older software by providing 48-bit VAs | |
1124 | unless a hint is supplied to mmap. | |
1125 | ||
1126 | This configuration option disables the 48-bit compatibility logic, and | |
1127 | forces all userspace addresses to be 52-bit on HW that supports it. One | |
1128 | should only enable this configuration option for stress testing userspace | |
1129 | memory management code. If unsure say N here. | |
1130 | ||
e41ceed0 JL |
1131 | config ARM64_VA_BITS |
1132 | int | |
21539939 | 1133 | default 36 if ARM64_VA_BITS_36 |
e41ceed0 JL |
1134 | default 39 if ARM64_VA_BITS_39 |
1135 | default 42 if ARM64_VA_BITS_42 | |
44eaacf1 | 1136 | default 47 if ARM64_VA_BITS_47 |
b6d00d47 SC |
1137 | default 48 if ARM64_VA_BITS_48 |
1138 | default 52 if ARM64_VA_BITS_52 | |
e41ceed0 | 1139 | |
982aa7c5 KM |
1140 | choice |
1141 | prompt "Physical address space size" | |
1142 | default ARM64_PA_BITS_48 | |
1143 | help | |
1144 | Choose the maximum physical address range that the kernel will | |
1145 | support. | |
1146 | ||
1147 | config ARM64_PA_BITS_48 | |
1148 | bool "48-bit" | |
1149 | ||
f77d2817 KM |
1150 | config ARM64_PA_BITS_52 |
1151 | bool "52-bit (ARMv8.2)" | |
1152 | depends on ARM64_64K_PAGES | |
1153 | depends on ARM64_PAN || !ARM64_SW_TTBR0_PAN | |
1154 | help | |
1155 | Enable support for a 52-bit physical address space, introduced as | |
1156 | part of the ARMv8.2-LPA extension. | |
1157 | ||
1158 | With this enabled, the kernel will also continue to work on CPUs that | |
1159 | do not support ARMv8.2-LPA, but with some added memory overhead (and | |
1160 | minor performance overhead). | |
1161 | ||
982aa7c5 KM |
1162 | endchoice |
1163 | ||
1164 | config ARM64_PA_BITS | |
1165 | int | |
1166 | default 48 if ARM64_PA_BITS_48 | |
f77d2817 | 1167 | default 52 if ARM64_PA_BITS_52 |
982aa7c5 | 1168 | |
d8e85e14 AR |
1169 | choice |
1170 | prompt "Endianness" | |
1171 | default CPU_LITTLE_ENDIAN | |
1172 | help | |
1173 | Select the endianness of data accesses performed by the CPU. Userspace | |
1174 | applications will need to be compiled and linked for the endianness | |
1175 | that is selected here. | |
1176 | ||
a872013d | 1177 | config CPU_BIG_ENDIAN |
e9c6deee NC |
1178 | bool "Build big-endian kernel" |
1179 | depends on !LD_IS_LLD || LLD_VERSION >= 130000 | |
1180 | help | |
d8e85e14 AR |
1181 | Say Y if you plan on running a kernel with a big-endian userspace. |
1182 | ||
1183 | config CPU_LITTLE_ENDIAN | |
1184 | bool "Build little-endian kernel" | |
1185 | help | |
1186 | Say Y if you plan on running a kernel with a little-endian userspace. | |
1187 | This is usually the case for distributions targeting arm64. | |
1188 | ||
1189 | endchoice | |
a872013d | 1190 | |
f6e763b9 MB |
1191 | config SCHED_MC |
1192 | bool "Multi-core scheduler support" | |
f6e763b9 MB |
1193 | help |
1194 | Multi-core scheduler support improves the CPU scheduler's decision | |
1195 | making when dealing with multi-core CPU chips at a cost of slightly | |
1196 | increased overhead in some places. If unsure say N here. | |
1197 | ||
778c558f BS |
1198 | config SCHED_CLUSTER |
1199 | bool "Cluster scheduler support" | |
1200 | help | |
1201 | Cluster scheduler support improves the CPU scheduler's decision | |
1202 | making when dealing with machines that have clusters of CPUs. | |
1203 | Cluster usually means a couple of CPUs which are placed closely | |
1204 | by sharing mid-level caches, last-level cache tags or internal | |
1205 | busses. | |
1206 | ||
f6e763b9 MB |
1207 | config SCHED_SMT |
1208 | bool "SMT scheduler support" | |
f6e763b9 MB |
1209 | help |
1210 | Improves the CPU scheduler's decision making when dealing with | |
1211 | MultiThreading at a cost of slightly increased overhead in some | |
1212 | places. If unsure say N here. | |
1213 | ||
8c2c3df3 | 1214 | config NR_CPUS |
62aa9655 GK |
1215 | int "Maximum number of CPUs (2-4096)" |
1216 | range 2 4096 | |
846a415b | 1217 | default "256" |
8c2c3df3 | 1218 | |
9327e2c6 MR |
1219 | config HOTPLUG_CPU |
1220 | bool "Support for hot-pluggable CPUs" | |
217d453d | 1221 | select GENERIC_IRQ_MIGRATION |
9327e2c6 MR |
1222 | help |
1223 | Say Y here to experiment with turning CPUs off and on. CPUs | |
1224 | can be controlled through /sys/devices/system/cpu. | |
1225 | ||
1a2db300 GK |
1226 | # Common NUMA Features |
1227 | config NUMA | |
4399e6cd | 1228 | bool "NUMA Memory Allocation and Scheduler Support" |
ae3c107c | 1229 | select GENERIC_ARCH_NUMA |
0c2a6cce KW |
1230 | select ACPI_NUMA if ACPI |
1231 | select OF_NUMA | |
7ecd19cf KW |
1232 | select HAVE_SETUP_PER_CPU_AREA |
1233 | select NEED_PER_CPU_EMBED_FIRST_CHUNK | |
1234 | select NEED_PER_CPU_PAGE_FIRST_CHUNK | |
1235 | select USE_PERCPU_NUMA_NODE_ID | |
1a2db300 | 1236 | help |
4399e6cd | 1237 | Enable NUMA (Non-Uniform Memory Access) support. |
1a2db300 GK |
1238 | |
1239 | The kernel will try to allocate memory used by a CPU on the | |
1240 | local memory of the CPU and add some more | |
1241 | NUMA awareness to the kernel. | |
1242 | ||
1243 | config NODES_SHIFT | |
1244 | int "Maximum NUMA Nodes (as a power of 2)" | |
1245 | range 1 10 | |
2a13c13b | 1246 | default "4" |
a9ee6cf5 | 1247 | depends on NUMA |
1a2db300 GK |
1248 | help |
1249 | Specify the maximum number of NUMA Nodes available on the target | |
1250 | system. Increases memory reserved to accommodate various tables. | |
1251 | ||
8636a1f9 | 1252 | source "kernel/Kconfig.hz" |
8c2c3df3 | 1253 | |
8c2c3df3 CM |
1254 | config ARCH_SPARSEMEM_ENABLE |
1255 | def_bool y | |
1256 | select SPARSEMEM_VMEMMAP_ENABLE | |
782276b4 | 1257 | select SPARSEMEM_VMEMMAP |
e7d4bac4 | 1258 | |
8c2c3df3 | 1259 | config HW_PERF_EVENTS |
6475b2d8 MR |
1260 | def_bool y |
1261 | depends on ARM_PMU | |
8c2c3df3 | 1262 | |
afcf5441 | 1263 | # Supported by clang >= 7.0 or GCC >= 12.0.0 |
5287569a ST |
1264 | config CC_HAVE_SHADOW_CALL_STACK |
1265 | def_bool $(cc-option, -fsanitize=shadow-call-stack -ffixed-x18) | |
1266 | ||
dfd57bc3 SS |
1267 | config PARAVIRT |
1268 | bool "Enable paravirtualization code" | |
1269 | help | |
1270 | This changes the kernel so it can modify itself when it is run | |
1271 | under a hypervisor, potentially improving performance significantly | |
1272 | over full virtualization. | |
1273 | ||
1274 | config PARAVIRT_TIME_ACCOUNTING | |
1275 | bool "Paravirtual steal time accounting" | |
1276 | select PARAVIRT | |
dfd57bc3 SS |
1277 | help |
1278 | Select this option to enable fine granularity task steal time | |
1279 | accounting. Time spent executing other tasks in parallel with | |
1280 | the current vCPU is discounted from the vCPU power. To account for | |
1281 | that, there can be a small performance impact. | |
1282 | ||
1283 | If in doubt, say N here. | |
1284 | ||
d28f6df1 GL |
1285 | config KEXEC |
1286 | depends on PM_SLEEP_SMP | |
1287 | select KEXEC_CORE | |
1288 | bool "kexec system call" | |
a7f7f624 | 1289 | help |
d28f6df1 GL |
1290 | kexec is a system call that implements the ability to shutdown your |
1291 | current kernel, and to start another kernel. It is like a reboot | |
1292 | but it is independent of the system firmware. And like a reboot | |
1293 | you can start any kernel with it, not just Linux. | |
1294 | ||
3ddd9992 AT |
1295 | config KEXEC_FILE |
1296 | bool "kexec file based system call" | |
1297 | select KEXEC_CORE | |
dce92f6b | 1298 | select HAVE_IMA_KEXEC if IMA |
3ddd9992 AT |
1299 | help |
1300 | This is new version of kexec system call. This system call is | |
1301 | file based and takes file descriptors as system call argument | |
1302 | for kernel and initramfs as opposed to list of segments as | |
1303 | accepted by previous system call. | |
1304 | ||
99d5cadf | 1305 | config KEXEC_SIG |
732b7b93 AT |
1306 | bool "Verify kernel signature during kexec_file_load() syscall" |
1307 | depends on KEXEC_FILE | |
1308 | help | |
1309 | Select this option to verify a signature with loaded kernel | |
1310 | image. If configured, any attempt of loading a image without | |
1311 | valid signature will fail. | |
1312 | ||
1313 | In addition to that option, you need to enable signature | |
1314 | verification for the corresponding kernel image type being | |
1315 | loaded in order for this to work. | |
1316 | ||
1317 | config KEXEC_IMAGE_VERIFY_SIG | |
1318 | bool "Enable Image signature verification support" | |
1319 | default y | |
99d5cadf | 1320 | depends on KEXEC_SIG |
732b7b93 AT |
1321 | depends on EFI && SIGNED_PE_FILE_VERIFICATION |
1322 | help | |
1323 | Enable Image signature verification support. | |
1324 | ||
1325 | comment "Support for PE file signature verification disabled" | |
99d5cadf | 1326 | depends on KEXEC_SIG |
732b7b93 AT |
1327 | depends on !EFI || !SIGNED_PE_FILE_VERIFICATION |
1328 | ||
e62aaeac AT |
1329 | config CRASH_DUMP |
1330 | bool "Build kdump crash kernel" | |
1331 | help | |
1332 | Generate crash dump after being started by kexec. This should | |
1333 | be normally only set in special crash dump kernels which are | |
1334 | loaded in the main kernel with kexec-tools into a specially | |
1335 | reserved region and then later executed after a crash by | |
1336 | kdump/kexec. | |
1337 | ||
330d4810 | 1338 | For more details see Documentation/admin-guide/kdump/kdump.rst |
e62aaeac | 1339 | |
072e3d96 PT |
1340 | config TRANS_TABLE |
1341 | def_bool y | |
08eae0ef | 1342 | depends on HIBERNATION || KEXEC_CORE |
072e3d96 | 1343 | |
aa42aa13 SS |
1344 | config XEN_DOM0 |
1345 | def_bool y | |
1346 | depends on XEN | |
1347 | ||
1348 | config XEN | |
c2ba1f7d | 1349 | bool "Xen guest support on ARM64" |
aa42aa13 | 1350 | depends on ARM64 && OF |
83862ccf | 1351 | select SWIOTLB_XEN |
dfd57bc3 | 1352 | select PARAVIRT |
aa42aa13 SS |
1353 | help |
1354 | Say Y if you want to run Linux in a Virtual Machine on Xen on ARM64. | |
1355 | ||
d03bb145 SC |
1356 | config FORCE_MAX_ZONEORDER |
1357 | int | |
79cc2ed5 AK |
1358 | default "14" if ARM64_64K_PAGES |
1359 | default "12" if ARM64_16K_PAGES | |
d03bb145 | 1360 | default "11" |
44eaacf1 SP |
1361 | help |
1362 | The kernel memory allocator divides physically contiguous memory | |
1363 | blocks into "zones", where each zone is a power of two number of | |
1364 | pages. This option selects the largest power of two that the kernel | |
1365 | keeps in the memory allocator. If you need to allocate very large | |
1366 | blocks of physically contiguous memory, then you may need to | |
1367 | increase this value. | |
1368 | ||
1369 | This config option is actually maximum order plus one. For example, | |
1370 | a value of 11 means that the largest free memory block is 2^10 pages. | |
1371 | ||
1372 | We make sure that we can allocate upto a HugePage size for each configuration. | |
1373 | Hence we have : | |
1374 | MAX_ORDER = (PMD_SHIFT - PAGE_SHIFT) + 1 => PAGE_SHIFT - 2 | |
1375 | ||
1376 | However for 4K, we choose a higher default value, 11 as opposed to 10, giving us | |
1377 | 4M allocations matching the default size used by generic code. | |
d03bb145 | 1378 | |
084eb77c | 1379 | config UNMAP_KERNEL_AT_EL0 |
0617052d | 1380 | bool "Unmap kernel when running in userspace (aka \"KAISER\")" if EXPERT |
084eb77c WD |
1381 | default y |
1382 | help | |
0617052d WD |
1383 | Speculation attacks against some high-performance processors can |
1384 | be used to bypass MMU permission checks and leak kernel data to | |
1385 | userspace. This can be defended against by unmapping the kernel | |
1386 | when running in userspace, mapping it back in on exception entry | |
1387 | via a trampoline page in the vector table. | |
084eb77c WD |
1388 | |
1389 | If unsure, say Y. | |
1390 | ||
558c303c JM |
1391 | config MITIGATE_SPECTRE_BRANCH_HISTORY |
1392 | bool "Mitigate Spectre style attacks against branch history" if EXPERT | |
1393 | default y | |
1394 | help | |
1395 | Speculation attacks against some high-performance processors can | |
1396 | make use of branch history to influence future speculation. | |
1397 | When taking an exception from user-space, a sequence of branches | |
1398 | or a firmware call overwrites the branch history. | |
1399 | ||
c55191e9 AB |
1400 | config RODATA_FULL_DEFAULT_ENABLED |
1401 | bool "Apply r/o permissions of VM areas also to their linear aliases" | |
1402 | default y | |
1403 | help | |
1404 | Apply read-only attributes of VM areas to the linear alias of | |
1405 | the backing pages as well. This prevents code or read-only data | |
1406 | from being modified (inadvertently or intentionally) via another | |
1407 | mapping of the same memory page. This additional enhancement can | |
1408 | be turned off at runtime by passing rodata=[off|on] (and turned on | |
1409 | with rodata=full if this option is set to 'n') | |
1410 | ||
1411 | This requires the linear region to be mapped down to pages, | |
1412 | which may adversely affect performance in some cases. | |
1413 | ||
dd523791 WD |
1414 | config ARM64_SW_TTBR0_PAN |
1415 | bool "Emulate Privileged Access Never using TTBR0_EL1 switching" | |
1416 | help | |
1417 | Enabling this option prevents the kernel from accessing | |
1418 | user-space memory directly by pointing TTBR0_EL1 to a reserved | |
1419 | zeroed area and reserved ASID. The user access routines | |
1420 | restore the valid TTBR0_EL1 temporarily. | |
1421 | ||
63f0c603 CM |
1422 | config ARM64_TAGGED_ADDR_ABI |
1423 | bool "Enable the tagged user addresses syscall ABI" | |
1424 | default y | |
1425 | help | |
1426 | When this option is enabled, user applications can opt in to a | |
1427 | relaxed ABI via prctl() allowing tagged addresses to be passed | |
1428 | to system calls as pointer arguments. For details, see | |
799c8510 | 1429 | Documentation/arm64/tagged-address-abi.rst. |
63f0c603 | 1430 | |
dd523791 WD |
1431 | menuconfig COMPAT |
1432 | bool "Kernel support for 32-bit EL0" | |
1433 | depends on ARM64_4K_PAGES || EXPERT | |
dd523791 WD |
1434 | select HAVE_UID16 |
1435 | select OLD_SIGSUSPEND3 | |
1436 | select COMPAT_OLD_SIGACTION | |
1437 | help | |
1438 | This option enables support for a 32-bit EL0 running under a 64-bit | |
1439 | kernel at EL1. AArch32-specific components such as system calls, | |
1440 | the user helper functions, VFP support and the ptrace interface are | |
1441 | handled appropriately by the kernel. | |
1442 | ||
1443 | If you use a page size other than 4KB (i.e, 16KB or 64KB), please be aware | |
1444 | that you will only be able to execute AArch32 binaries that were compiled | |
1445 | with page size aligned segments. | |
1446 | ||
1447 | If you want to execute 32-bit userspace applications, say Y. | |
1448 | ||
1449 | if COMPAT | |
1450 | ||
1451 | config KUSER_HELPERS | |
7c4791c9 | 1452 | bool "Enable kuser helpers page for 32-bit applications" |
dd523791 WD |
1453 | default y |
1454 | help | |
1455 | Warning: disabling this option may break 32-bit user programs. | |
1456 | ||
1457 | Provide kuser helpers to compat tasks. The kernel provides | |
1458 | helper code to userspace in read only form at a fixed location | |
1459 | to allow userspace to be independent of the CPU type fitted to | |
1460 | the system. This permits binaries to be run on ARMv4 through | |
1461 | to ARMv8 without modification. | |
1462 | ||
dc7a12bd | 1463 | See Documentation/arm/kernel_user_helpers.rst for details. |
dd523791 WD |
1464 | |
1465 | However, the fixed address nature of these helpers can be used | |
1466 | by ROP (return orientated programming) authors when creating | |
1467 | exploits. | |
1468 | ||
1469 | If all of the binaries and libraries which run on your platform | |
1470 | are built specifically for your platform, and make no use of | |
1471 | these helpers, then you can turn this option off to hinder | |
1472 | such exploits. However, in that case, if a binary or library | |
1473 | relying on those helpers is run, it will not function correctly. | |
1474 | ||
1475 | Say N here only if you are absolutely certain that you do not | |
1476 | need these helpers; otherwise, the safe option is to say Y. | |
1477 | ||
7c4791c9 WD |
1478 | config COMPAT_VDSO |
1479 | bool "Enable vDSO for 32-bit applications" | |
3e6f8d1f ND |
1480 | depends on !CPU_BIG_ENDIAN |
1481 | depends on (CC_IS_CLANG && LD_IS_LLD) || "$(CROSS_COMPILE_COMPAT)" != "" | |
7c4791c9 WD |
1482 | select GENERIC_COMPAT_VDSO |
1483 | default y | |
1484 | help | |
1485 | Place in the process address space of 32-bit applications an | |
1486 | ELF shared object providing fast implementations of gettimeofday | |
1487 | and clock_gettime. | |
1488 | ||
1489 | You must have a 32-bit build of glibc 2.22 or later for programs | |
1490 | to seamlessly take advantage of this. | |
dd523791 | 1491 | |
625412c2 ND |
1492 | config THUMB2_COMPAT_VDSO |
1493 | bool "Compile the 32-bit vDSO for Thumb-2 mode" if EXPERT | |
1494 | depends on COMPAT_VDSO | |
1495 | default y | |
1496 | help | |
1497 | Compile the compat vDSO with '-mthumb -fomit-frame-pointer' if y, | |
1498 | otherwise with '-marm'. | |
1499 | ||
1b907f46 WD |
1500 | menuconfig ARMV8_DEPRECATED |
1501 | bool "Emulate deprecated/obsolete ARMv8 instructions" | |
6cfa7cc4 | 1502 | depends on SYSCTL |
1b907f46 WD |
1503 | help |
1504 | Legacy software support may require certain instructions | |
1505 | that have been deprecated or obsoleted in the architecture. | |
1506 | ||
1507 | Enable this config to enable selective emulation of these | |
1508 | features. | |
1509 | ||
1510 | If unsure, say Y | |
1511 | ||
1512 | if ARMV8_DEPRECATED | |
1513 | ||
1514 | config SWP_EMULATION | |
1515 | bool "Emulate SWP/SWPB instructions" | |
1516 | help | |
1517 | ARMv8 obsoletes the use of A32 SWP/SWPB instructions such that | |
1518 | they are always undefined. Say Y here to enable software | |
1519 | emulation of these instructions for userspace using LDXR/STXR. | |
dd720784 MB |
1520 | This feature can be controlled at runtime with the abi.swp |
1521 | sysctl which is disabled by default. | |
1b907f46 WD |
1522 | |
1523 | In some older versions of glibc [<=2.8] SWP is used during futex | |
1524 | trylock() operations with the assumption that the code will not | |
1525 | be preempted. This invalid assumption may be more likely to fail | |
1526 | with SWP emulation enabled, leading to deadlock of the user | |
1527 | application. | |
1528 | ||
1529 | NOTE: when accessing uncached shared regions, LDXR/STXR rely | |
1530 | on an external transaction monitoring block called a global | |
1531 | monitor to maintain update atomicity. If your system does not | |
1532 | implement a global monitor, this option can cause programs that | |
1533 | perform SWP operations to uncached memory to deadlock. | |
1534 | ||
1535 | If unsure, say Y | |
1536 | ||
1537 | config CP15_BARRIER_EMULATION | |
1538 | bool "Emulate CP15 Barrier instructions" | |
1539 | help | |
1540 | The CP15 barrier instructions - CP15ISB, CP15DSB, and | |
1541 | CP15DMB - are deprecated in ARMv8 (and ARMv7). It is | |
1542 | strongly recommended to use the ISB, DSB, and DMB | |
1543 | instructions instead. | |
1544 | ||
1545 | Say Y here to enable software emulation of these | |
1546 | instructions for AArch32 userspace code. When this option is | |
1547 | enabled, CP15 barrier usage is traced which can help | |
dd720784 MB |
1548 | identify software that needs updating. This feature can be |
1549 | controlled at runtime with the abi.cp15_barrier sysctl. | |
1b907f46 WD |
1550 | |
1551 | If unsure, say Y | |
1552 | ||
2d888f48 SP |
1553 | config SETEND_EMULATION |
1554 | bool "Emulate SETEND instruction" | |
1555 | help | |
1556 | The SETEND instruction alters the data-endianness of the | |
1557 | AArch32 EL0, and is deprecated in ARMv8. | |
1558 | ||
1559 | Say Y here to enable software emulation of the instruction | |
dd720784 MB |
1560 | for AArch32 userspace code. This feature can be controlled |
1561 | at runtime with the abi.setend sysctl. | |
2d888f48 SP |
1562 | |
1563 | Note: All the cpus on the system must have mixed endian support at EL0 | |
1564 | for this feature to be enabled. If a new CPU - which doesn't support mixed | |
1565 | endian - is hotplugged in after this feature has been enabled, there could | |
1566 | be unexpected results in the applications. | |
1567 | ||
1568 | If unsure, say Y | |
1b907f46 WD |
1569 | endif |
1570 | ||
dd523791 | 1571 | endif |
ba42822a | 1572 | |
0e4a0709 WD |
1573 | menu "ARMv8.1 architectural features" |
1574 | ||
1575 | config ARM64_HW_AFDBM | |
1576 | bool "Support for hardware updates of the Access and Dirty page flags" | |
1577 | default y | |
1578 | help | |
1579 | The ARMv8.1 architecture extensions introduce support for | |
1580 | hardware updates of the access and dirty information in page | |
1581 | table entries. When enabled in TCR_EL1 (HA and HD bits) on | |
1582 | capable processors, accesses to pages with PTE_AF cleared will | |
1583 | set this bit instead of raising an access flag fault. | |
1584 | Similarly, writes to read-only pages with the DBM bit set will | |
1585 | clear the read-only bit (AP[2]) instead of raising a | |
1586 | permission fault. | |
1587 | ||
1588 | Kernels built with this configuration option enabled continue | |
1589 | to work on pre-ARMv8.1 hardware and the performance impact is | |
1590 | minimal. If unsure, say Y. | |
1591 | ||
1592 | config ARM64_PAN | |
1593 | bool "Enable support for Privileged Access Never (PAN)" | |
1594 | default y | |
1595 | help | |
1596 | Privileged Access Never (PAN; part of the ARMv8.1 Extensions) | |
1597 | prevents the kernel or hypervisor from accessing user-space (EL0) | |
1598 | memory directly. | |
1599 | ||
1600 | Choosing this option will cause any unprotected (not using | |
1601 | copy_to_user et al) memory access to fail with a permission fault. | |
1602 | ||
1603 | The feature is detected at runtime, and will remain as a 'nop' | |
1604 | instruction if the cpu does not implement the feature. | |
1605 | ||
364a5a8a WD |
1606 | config AS_HAS_LDAPR |
1607 | def_bool $(as-instr,.arch_extension rcpc) | |
1608 | ||
2decad92 CM |
1609 | config AS_HAS_LSE_ATOMICS |
1610 | def_bool $(as-instr,.arch_extension lse) | |
1611 | ||
0e4a0709 | 1612 | config ARM64_LSE_ATOMICS |
395af861 CM |
1613 | bool |
1614 | default ARM64_USE_LSE_ATOMICS | |
2decad92 | 1615 | depends on AS_HAS_LSE_ATOMICS |
395af861 CM |
1616 | |
1617 | config ARM64_USE_LSE_ATOMICS | |
0e4a0709 | 1618 | bool "Atomic instructions" |
b32baf91 | 1619 | depends on JUMP_LABEL |
7bd99b40 | 1620 | default y |
0e4a0709 WD |
1621 | help |
1622 | As part of the Large System Extensions, ARMv8.1 introduces new | |
1623 | atomic instructions that are designed specifically to scale in | |
1624 | very large systems. | |
1625 | ||
1626 | Say Y here to make use of these instructions for the in-kernel | |
1627 | atomic routines. This incurs a small overhead on CPUs that do | |
1628 | not support these instructions and requires the kernel to be | |
7bd99b40 WD |
1629 | built with binutils >= 2.25 in order for the new instructions |
1630 | to be used. | |
0e4a0709 WD |
1631 | |
1632 | endmenu | |
1633 | ||
f993318b WD |
1634 | menu "ARMv8.2 architectural features" |
1635 | ||
2c54b423 AB |
1636 | config AS_HAS_ARMV8_2 |
1637 | def_bool $(cc-option,-Wa$(comma)-march=armv8.2-a) | |
1638 | ||
1639 | config AS_HAS_SHA3 | |
1640 | def_bool $(as-instr,.arch armv8.2-a+sha3) | |
1641 | ||
d50e071f RM |
1642 | config ARM64_PMEM |
1643 | bool "Enable support for persistent memory" | |
1644 | select ARCH_HAS_PMEM_API | |
5d7bdeb1 | 1645 | select ARCH_HAS_UACCESS_FLUSHCACHE |
d50e071f RM |
1646 | help |
1647 | Say Y to enable support for the persistent memory API based on the | |
1648 | ARMv8.2 DCPoP feature. | |
1649 | ||
1650 | The feature is detected at runtime, and the kernel will use DC CVAC | |
1651 | operations if DC CVAP is not supported (following the behaviour of | |
1652 | DC CVAP itself if the system does not define a point of persistence). | |
1653 | ||
64c02720 XX |
1654 | config ARM64_RAS_EXTN |
1655 | bool "Enable support for RAS CPU Extensions" | |
1656 | default y | |
1657 | help | |
1658 | CPUs that support the Reliability, Availability and Serviceability | |
1659 | (RAS) Extensions, part of ARMv8.2 are able to track faults and | |
1660 | errors, classify them and report them to software. | |
1661 | ||
1662 | On CPUs with these extensions system software can use additional | |
1663 | barriers to determine if faults are pending and read the | |
1664 | classification from a new set of registers. | |
1665 | ||
1666 | Selecting this feature will allow the kernel to use these barriers | |
1667 | and access the new registers if the system supports the extension. | |
1668 | Platform RAS features may additionally depend on firmware support. | |
1669 | ||
5ffdfaed VM |
1670 | config ARM64_CNP |
1671 | bool "Enable support for Common Not Private (CNP) translations" | |
1672 | default y | |
1673 | depends on ARM64_PAN || !ARM64_SW_TTBR0_PAN | |
1674 | help | |
1675 | Common Not Private (CNP) allows translation table entries to | |
1676 | be shared between different PEs in the same inner shareable | |
1677 | domain, so the hardware can use this fact to optimise the | |
1678 | caching of such entries in the TLB. | |
1679 | ||
1680 | Selecting this option allows the CNP feature to be detected | |
1681 | at runtime, and does not affect PEs that do not implement | |
1682 | this feature. | |
1683 | ||
f993318b WD |
1684 | endmenu |
1685 | ||
04ca3204 MR |
1686 | menu "ARMv8.3 architectural features" |
1687 | ||
1688 | config ARM64_PTR_AUTH | |
1689 | bool "Enable support for pointer authentication" | |
1690 | default y | |
1691 | help | |
1692 | Pointer authentication (part of the ARMv8.3 Extensions) provides | |
1693 | instructions for signing and authenticating pointers against secret | |
1694 | keys, which can be used to mitigate Return Oriented Programming (ROP) | |
1695 | and other attacks. | |
1696 | ||
1697 | This option enables these instructions at EL0 (i.e. for userspace). | |
04ca3204 MR |
1698 | Choosing this option will cause the kernel to initialise secret keys |
1699 | for each process at exec() time, with these keys being | |
1700 | context-switched along with the process. | |
1701 | ||
1702 | The feature is detected at runtime. If the feature is not present in | |
384b40ca | 1703 | hardware it will not be advertised to userspace/KVM guest nor will it |
dfb0589c | 1704 | be enabled. |
04ca3204 | 1705 | |
6982934e KM |
1706 | If the feature is present on the boot CPU but not on a late CPU, then |
1707 | the late CPU will be parked. Also, if the boot CPU does not have | |
1708 | address auth and the late CPU has then the late CPU will still boot | |
1709 | but with the feature disabled. On such a system, this option should | |
1710 | not be selected. | |
1711 | ||
b27a9f41 | 1712 | config ARM64_PTR_AUTH_KERNEL |
d053e71a | 1713 | bool "Use pointer authentication for kernel" |
b27a9f41 DK |
1714 | default y |
1715 | depends on ARM64_PTR_AUTH | |
1716 | depends on (CC_HAS_SIGN_RETURN_ADDRESS || CC_HAS_BRANCH_PROT_PAC_RET) && AS_HAS_PAC | |
1717 | # Modern compilers insert a .note.gnu.property section note for PAC | |
1718 | # which is only understood by binutils starting with version 2.33.1. | |
1719 | depends on LD_IS_LLD || LD_VERSION >= 23301 || (CC_IS_GCC && GCC_VERSION < 90100) | |
1720 | depends on !CC_IS_CLANG || AS_HAS_CFI_NEGATE_RA_STATE | |
1721 | depends on (!FUNCTION_GRAPH_TRACER || DYNAMIC_FTRACE_WITH_REGS) | |
1722 | help | |
1723 | If the compiler supports the -mbranch-protection or | |
1724 | -msign-return-address flag (e.g. GCC 7 or later), then this option | |
1725 | will cause the kernel itself to be compiled with return address | |
1726 | protection. In this case, and if the target hardware is known to | |
1727 | support pointer authentication, then CONFIG_STACKPROTECTOR can be | |
1728 | disabled with minimal loss of protection. | |
1729 | ||
74afda40 KM |
1730 | This feature works with FUNCTION_GRAPH_TRACER option only if |
1731 | DYNAMIC_FTRACE_WITH_REGS is enabled. | |
1732 | ||
1733 | config CC_HAS_BRANCH_PROT_PAC_RET | |
1734 | # GCC 9 or later, clang 8 or later | |
1735 | def_bool $(cc-option,-mbranch-protection=pac-ret+leaf) | |
1736 | ||
1737 | config CC_HAS_SIGN_RETURN_ADDRESS | |
1738 | # GCC 7, 8 | |
1739 | def_bool $(cc-option,-msign-return-address=all) | |
1740 | ||
1741 | config AS_HAS_PAC | |
4d0831e8 | 1742 | def_bool $(cc-option,-Wa$(comma)-march=armv8.3-a) |
74afda40 | 1743 | |
3b446c7d ND |
1744 | config AS_HAS_CFI_NEGATE_RA_STATE |
1745 | def_bool $(as-instr,.cfi_startproc\n.cfi_negate_ra_state\n.cfi_endproc\n) | |
1746 | ||
04ca3204 MR |
1747 | endmenu |
1748 | ||
2c9d45b4 IV |
1749 | menu "ARMv8.4 architectural features" |
1750 | ||
1751 | config ARM64_AMU_EXTN | |
1752 | bool "Enable support for the Activity Monitors Unit CPU extension" | |
1753 | default y | |
1754 | help | |
1755 | The activity monitors extension is an optional extension introduced | |
1756 | by the ARMv8.4 CPU architecture. This enables support for version 1 | |
1757 | of the activity monitors architecture, AMUv1. | |
1758 | ||
1759 | To enable the use of this extension on CPUs that implement it, say Y. | |
1760 | ||
1761 | Note that for architectural reasons, firmware _must_ implement AMU | |
1762 | support when running on CPUs that present the activity monitors | |
1763 | extension. The required support is present in: | |
1764 | * Version 1.5 and later of the ARM Trusted Firmware | |
1765 | ||
1766 | For kernels that have this configuration enabled but boot with broken | |
1767 | firmware, you may need to say N here until the firmware is fixed. | |
1768 | Otherwise you may experience firmware panics or lockups when | |
1769 | accessing the counter registers. Even if you are not observing these | |
1770 | symptoms, the values returned by the register reads might not | |
1771 | correctly reflect reality. Most commonly, the value read will be 0, | |
1772 | indicating that the counter is not enabled. | |
1773 | ||
7c78f67e ZY |
1774 | config AS_HAS_ARMV8_4 |
1775 | def_bool $(cc-option,-Wa$(comma)-march=armv8.4-a) | |
1776 | ||
1777 | config ARM64_TLB_RANGE | |
1778 | bool "Enable support for tlbi range feature" | |
1779 | default y | |
1780 | depends on AS_HAS_ARMV8_4 | |
1781 | help | |
1782 | ARMv8.4-TLBI provides TLBI invalidation instruction that apply to a | |
1783 | range of input addresses. | |
1784 | ||
1785 | The feature introduces new assembly instructions, and they were | |
1786 | support when binutils >= 2.30. | |
1787 | ||
04ca3204 MR |
1788 | endmenu |
1789 | ||
3e6c69a0 MB |
1790 | menu "ARMv8.5 architectural features" |
1791 | ||
f469c032 VF |
1792 | config AS_HAS_ARMV8_5 |
1793 | def_bool $(cc-option,-Wa$(comma)-march=armv8.5-a) | |
1794 | ||
383499f8 DM |
1795 | config ARM64_BTI |
1796 | bool "Branch Target Identification support" | |
1797 | default y | |
1798 | help | |
1799 | Branch Target Identification (part of the ARMv8.5 Extensions) | |
1800 | provides a mechanism to limit the set of locations to which computed | |
1801 | branch instructions such as BR or BLR can jump. | |
1802 | ||
1803 | To make use of BTI on CPUs that support it, say Y. | |
1804 | ||
1805 | BTI is intended to provide complementary protection to other control | |
1806 | flow integrity protection mechanisms, such as the Pointer | |
1807 | authentication mechanism provided as part of the ARMv8.3 Extensions. | |
1808 | For this reason, it does not make sense to enable this option without | |
1809 | also enabling support for pointer authentication. Thus, when | |
1810 | enabling this option you should also select ARM64_PTR_AUTH=y. | |
1811 | ||
1812 | Userspace binaries must also be specifically compiled to make use of | |
1813 | this mechanism. If you say N here or the hardware does not support | |
1814 | BTI, such binaries can still run, but you get no additional | |
1815 | enforcement of branch destinations. | |
1816 | ||
97fed779 MB |
1817 | config ARM64_BTI_KERNEL |
1818 | bool "Use Branch Target Identification for kernel" | |
1819 | default y | |
1820 | depends on ARM64_BTI | |
b27a9f41 | 1821 | depends on ARM64_PTR_AUTH_KERNEL |
97fed779 | 1822 | depends on CC_HAS_BRANCH_PROT_PAC_RET_BTI |
3a88d7c5 WD |
1823 | # https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94697 |
1824 | depends on !CC_IS_GCC || GCC_VERSION >= 100100 | |
8cdd23c2 NC |
1825 | # https://github.com/llvm/llvm-project/commit/a88c722e687e6780dcd6a58718350dc76fcc4cc9 |
1826 | depends on !CC_IS_CLANG || CLANG_VERSION >= 120000 | |
97fed779 MB |
1827 | depends on (!FUNCTION_GRAPH_TRACER || DYNAMIC_FTRACE_WITH_REGS) |
1828 | help | |
1829 | Build the kernel with Branch Target Identification annotations | |
1830 | and enable enforcement of this for kernel code. When this option | |
1831 | is enabled and the system supports BTI all kernel code including | |
1832 | modular code must have BTI enabled. | |
1833 | ||
1834 | config CC_HAS_BRANCH_PROT_PAC_RET_BTI | |
1835 | # GCC 9 or later, clang 8 or later | |
1836 | def_bool $(cc-option,-mbranch-protection=pac-ret+leaf+bti) | |
1837 | ||
3e6c69a0 MB |
1838 | config ARM64_E0PD |
1839 | bool "Enable support for E0PD" | |
1840 | default y | |
1841 | help | |
e717d93b WD |
1842 | E0PD (part of the ARMv8.5 extensions) allows us to ensure |
1843 | that EL0 accesses made via TTBR1 always fault in constant time, | |
1844 | providing similar benefits to KASLR as those provided by KPTI, but | |
1845 | with lower overhead and without disrupting legitimate access to | |
1846 | kernel memory such as SPE. | |
3e6c69a0 | 1847 | |
e717d93b | 1848 | This option enables E0PD for TTBR1 where available. |
3e6c69a0 | 1849 | |
1a50ec0b RH |
1850 | config ARCH_RANDOM |
1851 | bool "Enable support for random number generation" | |
1852 | default y | |
1853 | help | |
1854 | Random number generation (part of the ARMv8.5 Extensions) | |
1855 | provides a high bandwidth, cryptographically secure | |
1856 | hardware random number generator. | |
1857 | ||
89b94df9 VF |
1858 | config ARM64_AS_HAS_MTE |
1859 | # Initial support for MTE went in binutils 2.32.0, checked with | |
1860 | # ".arch armv8.5-a+memtag" below. However, this was incomplete | |
1861 | # as a late addition to the final architecture spec (LDGM/STGM) | |
1862 | # is only supported in the newer 2.32.x and 2.33 binutils | |
1863 | # versions, hence the extra "stgm" instruction check below. | |
1864 | def_bool $(as-instr,.arch armv8.5-a+memtag\nstgm xzr$(comma)[x0]) | |
1865 | ||
1866 | config ARM64_MTE | |
1867 | bool "Memory Tagging Extension support" | |
1868 | default y | |
1869 | depends on ARM64_AS_HAS_MTE && ARM64_TAGGED_ADDR_ABI | |
f469c032 | 1870 | depends on AS_HAS_ARMV8_5 |
2decad92 | 1871 | depends on AS_HAS_LSE_ATOMICS |
98c970da VF |
1872 | # Required for tag checking in the uaccess routines |
1873 | depends on ARM64_PAN | |
89b94df9 VF |
1874 | select ARCH_USES_HIGH_VMA_FLAGS |
1875 | help | |
1876 | Memory Tagging (part of the ARMv8.5 Extensions) provides | |
1877 | architectural support for run-time, always-on detection of | |
1878 | various classes of memory error to aid with software debugging | |
1879 | to eliminate vulnerabilities arising from memory-unsafe | |
1880 | languages. | |
1881 | ||
1882 | This option enables the support for the Memory Tagging | |
1883 | Extension at EL0 (i.e. for userspace). | |
1884 | ||
1885 | Selecting this option allows the feature to be detected at | |
1886 | runtime. Any secondary CPU not implementing this feature will | |
1887 | not be allowed a late bring-up. | |
1888 | ||
1889 | Userspace binaries that want to use this feature must | |
1890 | explicitly opt in. The mechanism for the userspace is | |
1891 | described in: | |
1892 | ||
1893 | Documentation/arm64/memory-tagging-extension.rst. | |
1894 | ||
3e6c69a0 MB |
1895 | endmenu |
1896 | ||
18107f8a VM |
1897 | menu "ARMv8.7 architectural features" |
1898 | ||
1899 | config ARM64_EPAN | |
1900 | bool "Enable support for Enhanced Privileged Access Never (EPAN)" | |
1901 | default y | |
1902 | depends on ARM64_PAN | |
1903 | help | |
1904 | Enhanced Privileged Access Never (EPAN) allows Privileged | |
1905 | Access Never to be used with Execute-only mappings. | |
1906 | ||
1907 | The feature is detected at runtime, and will remain disabled | |
1908 | if the cpu does not implement the feature. | |
1909 | endmenu | |
1910 | ||
ddd25ad1 DM |
1911 | config ARM64_SVE |
1912 | bool "ARM Scalable Vector Extension support" | |
1913 | default y | |
1914 | help | |
1915 | The Scalable Vector Extension (SVE) is an extension to the AArch64 | |
1916 | execution state which complements and extends the SIMD functionality | |
1917 | of the base architecture to support much larger vectors and to enable | |
1918 | additional vectorisation opportunities. | |
1919 | ||
1920 | To enable use of this extension on CPUs that implement it, say Y. | |
1921 | ||
06a916fe DM |
1922 | On CPUs that support the SVE2 extensions, this option will enable |
1923 | those too. | |
1924 | ||
5043694e DM |
1925 | Note that for architectural reasons, firmware _must_ implement SVE |
1926 | support when running on SVE capable hardware. The required support | |
1927 | is present in: | |
1928 | ||
1929 | * version 1.5 and later of the ARM Trusted Firmware | |
1930 | * the AArch64 boot wrapper since commit 5e1261e08abf | |
1931 | ("bootwrapper: SVE: Enable SVE for EL2 and below"). | |
1932 | ||
1933 | For other firmware implementations, consult the firmware documentation | |
1934 | or vendor. | |
1935 | ||
1936 | If you need the kernel to boot on SVE-capable hardware with broken | |
1937 | firmware, you may need to say N here until you get your firmware | |
1938 | fixed. Otherwise, you may experience firmware panics or lockups when | |
1939 | booting the kernel. If unsure and you are not observing these | |
1940 | symptoms, you should assume that it is safe to say Y. | |
fd045f6c AB |
1941 | |
1942 | config ARM64_MODULE_PLTS | |
58557e48 | 1943 | bool "Use PLTs to allow module memory to spill over into vmalloc area" |
faaa73bc | 1944 | depends on MODULES |
fd045f6c | 1945 | select HAVE_MOD_ARCH_SPECIFIC |
58557e48 FF |
1946 | help |
1947 | Allocate PLTs when loading modules so that jumps and calls whose | |
1948 | targets are too far away for their relative offsets to be encoded | |
1949 | in the instructions themselves can be bounced via veneers in the | |
1950 | module's PLT. This allows modules to be allocated in the generic | |
1951 | vmalloc area after the dedicated module memory area has been | |
1952 | exhausted. | |
1953 | ||
1954 | When running with address space randomization (KASLR), the module | |
1955 | region itself may be too far away for ordinary relative jumps and | |
1956 | calls, and so in that case, module PLTs are required and cannot be | |
1957 | disabled. | |
1958 | ||
1959 | Specific errata workaround(s) might also force module PLTs to be | |
1960 | enabled (ARM64_ERRATUM_843419). | |
fd045f6c | 1961 | |
bc3c03cc JT |
1962 | config ARM64_PSEUDO_NMI |
1963 | bool "Support for NMI-like interrupts" | |
3c9c1dcd | 1964 | select ARM_GIC_V3 |
bc3c03cc JT |
1965 | help |
1966 | Adds support for mimicking Non-Maskable Interrupts through the use of | |
1967 | GIC interrupt priority. This support requires version 3 or later of | |
bc15cf70 | 1968 | ARM GIC. |
bc3c03cc JT |
1969 | |
1970 | This high priority configuration for interrupts needs to be | |
1971 | explicitly enabled by setting the kernel parameter | |
1972 | "irqchip.gicv3_pseudo_nmi" to 1. | |
1973 | ||
1974 | If unsure, say N | |
1975 | ||
48ce8f80 JT |
1976 | if ARM64_PSEUDO_NMI |
1977 | config ARM64_DEBUG_PRIORITY_MASKING | |
1978 | bool "Debug interrupt priority masking" | |
1979 | help | |
1980 | This adds runtime checks to functions enabling/disabling | |
1981 | interrupts when using priority masking. The additional checks verify | |
1982 | the validity of ICC_PMR_EL1 when calling concerned functions. | |
1983 | ||
1984 | If unsure, say N | |
1985 | endif | |
1986 | ||
1e48ef7f | 1987 | config RELOCATABLE |
dd4bc607 | 1988 | bool "Build a relocatable kernel image" if EXPERT |
5cf896fb | 1989 | select ARCH_HAS_RELR |
dd4bc607 | 1990 | default y |
1e48ef7f AB |
1991 | help |
1992 | This builds the kernel as a Position Independent Executable (PIE), | |
1993 | which retains all relocation metadata required to relocate the | |
1994 | kernel binary at runtime to a different virtual address than the | |
1995 | address it was linked at. | |
1996 | Since AArch64 uses the RELA relocation format, this requires a | |
1997 | relocation pass at runtime even if the kernel is loaded at the | |
1998 | same address it was linked at. | |
1999 | ||
f80fb3a3 AB |
2000 | config RANDOMIZE_BASE |
2001 | bool "Randomize the address of the kernel image" | |
b9c220b5 | 2002 | select ARM64_MODULE_PLTS if MODULES |
f80fb3a3 AB |
2003 | select RELOCATABLE |
2004 | help | |
2005 | Randomizes the virtual address at which the kernel image is | |
2006 | loaded, as a security feature that deters exploit attempts | |
2007 | relying on knowledge of the location of kernel internals. | |
2008 | ||
2009 | It is the bootloader's job to provide entropy, by passing a | |
2010 | random u64 value in /chosen/kaslr-seed at kernel entry. | |
2011 | ||
2b5fe07a AB |
2012 | When booting via the UEFI stub, it will invoke the firmware's |
2013 | EFI_RNG_PROTOCOL implementation (if available) to supply entropy | |
2014 | to the kernel proper. In addition, it will randomise the physical | |
2015 | location of the kernel Image as well. | |
2016 | ||
f80fb3a3 AB |
2017 | If unsure, say N. |
2018 | ||
2019 | config RANDOMIZE_MODULE_REGION_FULL | |
f9c4ff2a | 2020 | bool "Randomize the module region over a 2 GB range" |
e71a4e1b | 2021 | depends on RANDOMIZE_BASE |
f80fb3a3 AB |
2022 | default y |
2023 | help | |
f9c4ff2a | 2024 | Randomizes the location of the module region inside a 2 GB window |
f2b9ba87 | 2025 | covering the core kernel. This way, it is less likely for modules |
f80fb3a3 AB |
2026 | to leak information about the location of core kernel data structures |
2027 | but it does imply that function calls between modules and the core | |
2028 | kernel will need to be resolved via veneers in the module PLT. | |
2029 | ||
2030 | When this option is not set, the module region will be randomized over | |
2031 | a limited range that contains the [_stext, _etext] interval of the | |
f9c4ff2a BS |
2032 | core kernel, so branch relocations are almost always in range unless |
2033 | ARM64_MODULE_PLTS is enabled and the region is exhausted. In this | |
2034 | particular case of region exhaustion, modules might be able to fall | |
2035 | back to a larger 2GB area. | |
f80fb3a3 | 2036 | |
0a1213fa AB |
2037 | config CC_HAVE_STACKPROTECTOR_SYSREG |
2038 | def_bool $(cc-option,-mstack-protector-guard=sysreg -mstack-protector-guard-reg=sp_el0 -mstack-protector-guard-offset=0) | |
2039 | ||
2040 | config STACKPROTECTOR_PER_TASK | |
2041 | def_bool y | |
2042 | depends on STACKPROTECTOR && CC_HAVE_STACKPROTECTOR_SYSREG | |
2043 | ||
8c2c3df3 CM |
2044 | endmenu |
2045 | ||
2046 | menu "Boot options" | |
2047 | ||
5e89c55e LP |
2048 | config ARM64_ACPI_PARKING_PROTOCOL |
2049 | bool "Enable support for the ARM64 ACPI parking protocol" | |
2050 | depends on ACPI | |
2051 | help | |
2052 | Enable support for the ARM64 ACPI parking protocol. If disabled | |
2053 | the kernel will not allow booting through the ARM64 ACPI parking | |
2054 | protocol even if the corresponding data is present in the ACPI | |
2055 | MADT table. | |
2056 | ||
8c2c3df3 CM |
2057 | config CMDLINE |
2058 | string "Default kernel command string" | |
2059 | default "" | |
2060 | help | |
2061 | Provide a set of default command-line options at build time by | |
2062 | entering them here. As a minimum, you should specify the the | |
2063 | root device (e.g. root=/dev/nfs). | |
2064 | ||
1e40d105 TH |
2065 | choice |
2066 | prompt "Kernel command line type" if CMDLINE != "" | |
2067 | default CMDLINE_FROM_BOOTLOADER | |
2068 | help | |
2069 | Choose how the kernel will handle the provided default kernel | |
2070 | command line string. | |
2071 | ||
2072 | config CMDLINE_FROM_BOOTLOADER | |
2073 | bool "Use bootloader kernel arguments if available" | |
2074 | help | |
2075 | Uses the command-line options passed by the boot loader. If | |
2076 | the boot loader doesn't provide any, the default kernel command | |
2077 | string provided in CMDLINE will be used. | |
2078 | ||
8c2c3df3 CM |
2079 | config CMDLINE_FORCE |
2080 | bool "Always use the default kernel command string" | |
2081 | help | |
2082 | Always use the default kernel command string, even if the boot | |
2083 | loader passes other arguments to the kernel. | |
2084 | This is useful if you cannot or don't want to change the | |
2085 | command-line options your boot loader passes to the kernel. | |
2086 | ||
1e40d105 TH |
2087 | endchoice |
2088 | ||
f4f75ad5 AB |
2089 | config EFI_STUB |
2090 | bool | |
2091 | ||
f84d0275 MS |
2092 | config EFI |
2093 | bool "UEFI runtime support" | |
2094 | depends on OF && !CPU_BIG_ENDIAN | |
b472db6c | 2095 | depends on KERNEL_MODE_NEON |
2c870e61 | 2096 | select ARCH_SUPPORTS_ACPI |
f84d0275 MS |
2097 | select LIBFDT |
2098 | select UCS2_STRING | |
2099 | select EFI_PARAMS_FROM_FDT | |
e15dd494 | 2100 | select EFI_RUNTIME_WRAPPERS |
f4f75ad5 | 2101 | select EFI_STUB |
2e0eb483 | 2102 | select EFI_GENERIC_STUB |
8d39cee0 | 2103 | imply IMA_SECURE_AND_OR_TRUSTED_BOOT |
f84d0275 MS |
2104 | default y |
2105 | help | |
2106 | This option provides support for runtime services provided | |
2107 | by UEFI firmware (such as non-volatile variables, realtime | |
3c7f2550 MS |
2108 | clock, and platform reset). A UEFI stub is also provided to |
2109 | allow the kernel to be booted as an EFI application. This | |
2110 | is only useful on systems that have UEFI firmware. | |
f84d0275 | 2111 | |
d1ae8c00 YL |
2112 | config DMI |
2113 | bool "Enable support for SMBIOS (DMI) tables" | |
2114 | depends on EFI | |
2115 | default y | |
2116 | help | |
2117 | This enables SMBIOS/DMI feature for systems. | |
2118 | ||
2119 | This option is only useful on systems that have UEFI firmware. | |
2120 | However, even with this option, the resultant kernel should | |
2121 | continue to boot on existing non-UEFI platforms. | |
2122 | ||
8c2c3df3 CM |
2123 | endmenu |
2124 | ||
8c2c3df3 CM |
2125 | config SYSVIPC_COMPAT |
2126 | def_bool y | |
2127 | depends on COMPAT && SYSVIPC | |
2128 | ||
166936ba LP |
2129 | menu "Power management options" |
2130 | ||
2131 | source "kernel/power/Kconfig" | |
2132 | ||
82869ac5 JM |
2133 | config ARCH_HIBERNATION_POSSIBLE |
2134 | def_bool y | |
2135 | depends on CPU_PM | |
2136 | ||
2137 | config ARCH_HIBERNATION_HEADER | |
2138 | def_bool y | |
2139 | depends on HIBERNATION | |
2140 | ||
166936ba LP |
2141 | config ARCH_SUSPEND_POSSIBLE |
2142 | def_bool y | |
2143 | ||
166936ba LP |
2144 | endmenu |
2145 | ||
1307220d LP |
2146 | menu "CPU Power Management" |
2147 | ||
2148 | source "drivers/cpuidle/Kconfig" | |
2149 | ||
52e7e816 RH |
2150 | source "drivers/cpufreq/Kconfig" |
2151 | ||
2152 | endmenu | |
2153 | ||
b6a02173 GG |
2154 | source "drivers/acpi/Kconfig" |
2155 | ||
c3eb5b14 MZ |
2156 | source "arch/arm64/kvm/Kconfig" |
2157 | ||
2c98833a AB |
2158 | if CRYPTO |
2159 | source "arch/arm64/crypto/Kconfig" | |
2160 | endif |