1 # SPDX-License-Identifier: GPL-2.0 1 # SPDX-License-Identifier: GPL-2.0
2 # 2 #
3 # General architecture dependent options 3 # General architecture dependent options
4 # 4 #
5 5
6 # !! 6 config CRASH_CORE
7 # Note: arch/$(SRCARCH)/Kconfig needs to be in <<
8 # override the default values in this file. <<
9 # <<
10 source "arch/$(SRCARCH)/Kconfig" <<
11 <<
12 config ARCH_CONFIGURES_CPU_MITIGATIONS <<
13 bool 7 bool
14 8
15 if !ARCH_CONFIGURES_CPU_MITIGATIONS !! 9 config KEXEC_CORE
16 config CPU_MITIGATIONS !! 10 select CRASH_CORE
17 def_bool y <<
18 endif <<
19 <<
20 # <<
21 # Selected by architectures that need custom D <<
22 # IOMMUs not handled by dma-iommu. Drivers mu <<
23 # <<
24 config ARCH_HAS_DMA_OPS <<
25 depends on HAS_DMA <<
26 select DMA_OPS_HELPERS <<
27 bool 11 bool
28 12
29 menu "General architecture-dependent options" !! 13 config HAVE_IMA_KEXEC
30 <<
31 config ARCH_HAS_SUBPAGE_FAULTS <<
32 bool 14 bool
33 help <<
34 Select if the architecture can check <<
35 granularity (e.g. arm64 MTE). The pr <<
36 must be implemented. <<
37 15
38 config HOTPLUG_SMT 16 config HOTPLUG_SMT
39 bool 17 bool
40 18
41 config SMT_NUM_THREADS_DYNAMIC !! 19 config OPROFILE
42 bool !! 20 tristate "OProfile system profiling"
43 !! 21 depends on PROFILING
44 # Selected by HOTPLUG_CORE_SYNC_DEAD or HOTPLU !! 22 depends on HAVE_OPROFILE
45 config HOTPLUG_CORE_SYNC !! 23 select RING_BUFFER
46 bool !! 24 select RING_BUFFER_ALLOW_SWAP
>> 25 help
>> 26 OProfile is a profiling system capable of profiling the
>> 27 whole system, include the kernel, kernel modules, libraries,
>> 28 and applications.
47 29
48 # Basic CPU dead synchronization selected by a !! 30 If unsure, say N.
49 config HOTPLUG_CORE_SYNC_DEAD <<
50 bool <<
51 select HOTPLUG_CORE_SYNC <<
52 31
53 # Full CPU synchronization with alive state se !! 32 config OPROFILE_EVENT_MULTIPLEX
54 config HOTPLUG_CORE_SYNC_FULL !! 33 bool "OProfile multiplexing support (EXPERIMENTAL)"
55 bool !! 34 default n
56 select HOTPLUG_CORE_SYNC_DEAD if HOTPL !! 35 depends on OPROFILE && X86
57 select HOTPLUG_CORE_SYNC !! 36 help
>> 37 The number of hardware counters is limited. The multiplexing
>> 38 feature enables OProfile to gather more events than counters
>> 39 are provided by the hardware. This is realized by switching
>> 40 between events at a user specified time interval.
58 41
59 config HOTPLUG_SPLIT_STARTUP !! 42 If unsure, say N.
60 bool <<
61 select HOTPLUG_CORE_SYNC_FULL <<
62 43
63 config HOTPLUG_PARALLEL !! 44 config HAVE_OPROFILE
64 bool 45 bool
65 select HOTPLUG_SPLIT_STARTUP <<
66 46
67 config GENERIC_ENTRY !! 47 config OPROFILE_NMI_TIMER
68 bool !! 48 def_bool y
>> 49 depends on PERF_EVENTS && HAVE_PERF_EVENTS_NMI && !PPC64
69 50
70 config KPROBES 51 config KPROBES
71 bool "Kprobes" 52 bool "Kprobes"
>> 53 depends on MODULES
72 depends on HAVE_KPROBES 54 depends on HAVE_KPROBES
73 select KALLSYMS 55 select KALLSYMS
74 select EXECMEM <<
75 select NEED_TASKS_RCU <<
76 help 56 help
77 Kprobes allows you to trap at almost 57 Kprobes allows you to trap at almost any kernel address and
78 execute a callback function. regist 58 execute a callback function. register_kprobe() establishes
79 a probepoint and specifies the callb 59 a probepoint and specifies the callback. Kprobes is useful
80 for kernel debugging, non-intrusive 60 for kernel debugging, non-intrusive instrumentation and testing.
81 If in doubt, say "N". 61 If in doubt, say "N".
82 62
83 config JUMP_LABEL 63 config JUMP_LABEL
84 bool "Optimize very unlikely/likely br !! 64 bool "Optimize very unlikely/likely branches"
85 depends on HAVE_ARCH_JUMP_LABEL !! 65 depends on HAVE_ARCH_JUMP_LABEL
86 select OBJTOOL if HAVE_JUMP_LABEL_HACK !! 66 help
87 help !! 67 This option enables a transparent branch optimization that
88 This option enables a transparent br !! 68 makes certain almost-always-true or almost-always-false branch
89 makes certain almost-always-true or !! 69 conditions even cheaper to execute within the kernel.
90 conditions even cheaper to execute w !! 70
91 !! 71 Certain performance-sensitive kernel code, such as trace points,
92 Certain performance-sensitive kernel !! 72 scheduler functionality, networking code and KVM have such
93 scheduler functionality, networking !! 73 branches and include support for this optimization technique.
94 branches and include support for thi !! 74
95 !! 75 If it is detected that the compiler has support for "asm goto",
96 If it is detected that the compiler !! 76 the kernel will compile such branches with just a nop
97 the kernel will compile such branche !! 77 instruction. When the condition flag is toggled to true, the
98 instruction. When the condition flag !! 78 nop will be converted to a jump instruction to execute the
99 nop will be converted to a jump inst !! 79 conditional block of instructions.
100 conditional block of instructions. !! 80
101 !! 81 This technique lowers overhead and stress on the branch prediction
102 This technique lowers overhead and s !! 82 of the processor and generally makes the kernel faster. The update
103 of the processor and generally makes !! 83 of the condition is slower, but those are always very rare.
104 of the condition is slower, but thos <<
105 84
106 ( On 32-bit x86, the necessary optio !! 85 ( On 32-bit x86, the necessary options added to the compiler
107 flags may increase the size of the !! 86 flags may increase the size of the kernel slightly. )
108 87
109 config STATIC_KEYS_SELFTEST 88 config STATIC_KEYS_SELFTEST
110 bool "Static key selftest" 89 bool "Static key selftest"
111 depends on JUMP_LABEL 90 depends on JUMP_LABEL
112 help 91 help
113 Boot time self-test of the branch pa 92 Boot time self-test of the branch patching code.
114 93
115 config STATIC_CALL_SELFTEST <<
116 bool "Static call selftest" <<
117 depends on HAVE_STATIC_CALL <<
118 help <<
119 Boot time self-test of the call patc <<
120 <<
121 config OPTPROBES 94 config OPTPROBES
122 def_bool y 95 def_bool y
123 depends on KPROBES && HAVE_OPTPROBES 96 depends on KPROBES && HAVE_OPTPROBES
124 select NEED_TASKS_RCU !! 97 select TASKS_RCU if PREEMPT
125 98
126 config KPROBES_ON_FTRACE 99 config KPROBES_ON_FTRACE
127 def_bool y 100 def_bool y
128 depends on KPROBES && HAVE_KPROBES_ON_ 101 depends on KPROBES && HAVE_KPROBES_ON_FTRACE
129 depends on DYNAMIC_FTRACE_WITH_REGS 102 depends on DYNAMIC_FTRACE_WITH_REGS
130 help 103 help
131 If function tracer is enabled and th !! 104 If function tracer is enabled and the arch supports full
132 passing of pt_regs to function traci !! 105 passing of pt_regs to function tracing, then kprobes can
133 optimize on top of function tracing. !! 106 optimize on top of function tracing.
134 107
135 config UPROBES 108 config UPROBES
136 def_bool n 109 def_bool n
137 depends on ARCH_SUPPORTS_UPROBES 110 depends on ARCH_SUPPORTS_UPROBES
138 help 111 help
139 Uprobes is the user-space counterpar 112 Uprobes is the user-space counterpart to kprobes: they
140 enable instrumentation applications 113 enable instrumentation applications (such as 'perf probe')
141 to establish unintrusive probes in u 114 to establish unintrusive probes in user-space binaries and
142 libraries, by executing handler func 115 libraries, by executing handler functions when the probes
143 are hit by user-space applications. 116 are hit by user-space applications.
144 117
145 ( These probes come in the form of s 118 ( These probes come in the form of single-byte breakpoints,
146 managed by the kernel and kept tra 119 managed by the kernel and kept transparent to the probed
147 application. ) 120 application. )
148 121
149 config HAVE_64BIT_ALIGNED_ACCESS 122 config HAVE_64BIT_ALIGNED_ACCESS
150 def_bool 64BIT && !HAVE_EFFICIENT_UNAL 123 def_bool 64BIT && !HAVE_EFFICIENT_UNALIGNED_ACCESS
151 help 124 help
152 Some architectures require 64 bit ac 125 Some architectures require 64 bit accesses to be 64 bit
153 aligned, which also requires structs 126 aligned, which also requires structs containing 64 bit values
154 to be 64 bit aligned too. This inclu 127 to be 64 bit aligned too. This includes some 32 bit
155 architectures which can do 64 bit ac 128 architectures which can do 64 bit accesses, as well as 64 bit
156 architectures without unaligned acce 129 architectures without unaligned access.
157 130
158 This symbol should be selected by an 131 This symbol should be selected by an architecture if 64 bit
159 accesses are required to be 64 bit a 132 accesses are required to be 64 bit aligned in this way even
160 though it is not a 64 bit architectu 133 though it is not a 64 bit architecture.
161 134
162 See Documentation/core-api/unaligned !! 135 See Documentation/unaligned-memory-access.txt for more
163 more information on the topic of una !! 136 information on the topic of unaligned memory accesses.
164 137
165 config HAVE_EFFICIENT_UNALIGNED_ACCESS 138 config HAVE_EFFICIENT_UNALIGNED_ACCESS
166 bool 139 bool
167 help 140 help
168 Some architectures are unable to per 141 Some architectures are unable to perform unaligned accesses
169 without the use of get_unaligned/put 142 without the use of get_unaligned/put_unaligned. Others are
170 unable to perform such accesses effi 143 unable to perform such accesses efficiently (e.g. trap on
171 unaligned access and require fixing 144 unaligned access and require fixing it up in the exception
172 handler.) 145 handler.)
173 146
174 This symbol should be selected by an 147 This symbol should be selected by an architecture if it can
175 perform unaligned accesses efficient 148 perform unaligned accesses efficiently to allow different
176 code paths to be selected for these 149 code paths to be selected for these cases. Some network
177 drivers, for example, could opt to n 150 drivers, for example, could opt to not fix up alignment
178 problems with received packets if do 151 problems with received packets if doing so would not help
179 much. 152 much.
180 153
181 See Documentation/core-api/unaligned !! 154 See Documentation/unaligned-memory-access.txt for more
182 information on the topic of unaligne 155 information on the topic of unaligned memory accesses.
183 156
184 config ARCH_USE_BUILTIN_BSWAP 157 config ARCH_USE_BUILTIN_BSWAP
185 bool !! 158 bool
186 help !! 159 help
187 Modern versions of GCC (since 4.4) h !! 160 Modern versions of GCC (since 4.4) have builtin functions
188 for handling byte-swapping. Using th !! 161 for handling byte-swapping. Using these, instead of the old
189 inline assembler that the architectu !! 162 inline assembler that the architecture code provides in the
190 __arch_bswapXX() macros, allows the !! 163 __arch_bswapXX() macros, allows the compiler to see what's
191 happening and offers more opportunit !! 164 happening and offers more opportunity for optimisation. In
192 particular, the compiler will be abl !! 165 particular, the compiler will be able to combine the byteswap
193 with a nearby load or store and use !! 166 with a nearby load or store and use load-and-swap or
194 store-and-swap instructions if the a !! 167 store-and-swap instructions if the architecture has them. It
195 should almost *never* result in code !! 168 should almost *never* result in code which is worse than the
196 hand-coded assembler in <asm/swab.h> !! 169 hand-coded assembler in <asm/swab.h>. But just in case it
197 does, the use of the builtins is opt !! 170 does, the use of the builtins is optional.
198 !! 171
199 Any architecture with load-and-swap !! 172 Any architecture with load-and-swap or store-and-swap
200 instructions should set this. And it !! 173 instructions should set this. And it shouldn't hurt to set it
201 on architectures that don't have suc !! 174 on architectures that don't have such instructions.
202 175
203 config KRETPROBES 176 config KRETPROBES
204 def_bool y 177 def_bool y
205 depends on KPROBES && (HAVE_KRETPROBES !! 178 depends on KPROBES && HAVE_KRETPROBES
206 <<
207 config KRETPROBE_ON_RETHOOK <<
208 def_bool y <<
209 depends on HAVE_RETHOOK <<
210 depends on KRETPROBES <<
211 select RETHOOK <<
212 179
213 config USER_RETURN_NOTIFIER 180 config USER_RETURN_NOTIFIER
214 bool 181 bool
215 depends on HAVE_USER_RETURN_NOTIFIER 182 depends on HAVE_USER_RETURN_NOTIFIER
216 help 183 help
217 Provide a kernel-internal notificati 184 Provide a kernel-internal notification when a cpu is about to
218 switch to user mode. 185 switch to user mode.
219 186
220 config HAVE_IOREMAP_PROT 187 config HAVE_IOREMAP_PROT
221 bool 188 bool
222 189
223 config HAVE_KPROBES 190 config HAVE_KPROBES
224 bool 191 bool
225 192
226 config HAVE_KRETPROBES 193 config HAVE_KRETPROBES
227 bool 194 bool
228 195
229 config HAVE_OPTPROBES 196 config HAVE_OPTPROBES
230 bool 197 bool
231 198
232 config HAVE_KPROBES_ON_FTRACE 199 config HAVE_KPROBES_ON_FTRACE
233 bool 200 bool
234 201
235 config ARCH_CORRECT_STACKTRACE_ON_KRETPROBE <<
236 bool <<
237 help <<
238 Since kretprobes modifies return add <<
239 stacktrace may see the kretprobe tra <<
240 of correct one. If the architecture <<
241 unwinder can adjust such entries, se <<
242 <<
243 config HAVE_FUNCTION_ERROR_INJECTION 202 config HAVE_FUNCTION_ERROR_INJECTION
244 bool 203 bool
245 204
246 config HAVE_NMI 205 config HAVE_NMI
247 bool 206 bool
248 207
249 config HAVE_FUNCTION_DESCRIPTORS <<
250 bool <<
251 <<
252 config TRACE_IRQFLAGS_SUPPORT <<
253 bool <<
254 <<
255 config TRACE_IRQFLAGS_NMI_SUPPORT <<
256 bool <<
257 <<
258 # 208 #
259 # An arch should select this if it provides al 209 # An arch should select this if it provides all these things:
260 # 210 #
261 # task_pt_regs() in asm/process 211 # task_pt_regs() in asm/processor.h or asm/ptrace.h
262 # arch_has_single_step() if there is ha 212 # arch_has_single_step() if there is hardware single-step support
263 # arch_has_block_step() if there is ha 213 # arch_has_block_step() if there is hardware block-step support
264 # asm/syscall.h supplying asm- 214 # asm/syscall.h supplying asm-generic/syscall.h interface
265 # linux/regset.h user_regset in 215 # linux/regset.h user_regset interfaces
266 # CORE_DUMP_USE_REGSET #define'd in l 216 # CORE_DUMP_USE_REGSET #define'd in linux/elf.h
267 # TIF_SYSCALL_TRACE calls ptrace_r !! 217 # TIF_SYSCALL_TRACE calls tracehook_report_syscall_{entry,exit}
268 # TIF_NOTIFY_RESUME calls resume_u !! 218 # TIF_NOTIFY_RESUME calls tracehook_notify_resume()
>> 219 # signal delivery calls tracehook_signal_handler()
269 # 220 #
270 config HAVE_ARCH_TRACEHOOK 221 config HAVE_ARCH_TRACEHOOK
271 bool 222 bool
272 223
273 config HAVE_DMA_CONTIGUOUS 224 config HAVE_DMA_CONTIGUOUS
274 bool 225 bool
275 226
276 config GENERIC_SMP_IDLE_THREAD 227 config GENERIC_SMP_IDLE_THREAD
277 bool !! 228 bool
278 229
279 config GENERIC_IDLE_POLL_SETUP 230 config GENERIC_IDLE_POLL_SETUP
280 bool !! 231 bool
281 232
282 config ARCH_HAS_FORTIFY_SOURCE 233 config ARCH_HAS_FORTIFY_SOURCE
283 bool 234 bool
284 help 235 help
285 An architecture should select this w 236 An architecture should select this when it can successfully
286 build and run with CONFIG_FORTIFY_SO 237 build and run with CONFIG_FORTIFY_SOURCE.
287 238
288 # <<
289 # Select if the arch provides a historic keepi <<
290 # command line option <<
291 # <<
292 config ARCH_HAS_KEEPINITRD <<
293 bool <<
294 <<
295 # Select if arch has all set_memory_ro/rw/x/nx 239 # Select if arch has all set_memory_ro/rw/x/nx() functions in asm/cacheflush.h
296 config ARCH_HAS_SET_MEMORY 240 config ARCH_HAS_SET_MEMORY
297 bool 241 bool
298 242
299 # Select if arch has all set_direct_map_invali !! 243 # Select if arch init_task must go in the __init_task_data section
300 config ARCH_HAS_SET_DIRECT_MAP !! 244 config ARCH_TASK_STRUCT_ON_STACK
301 bool !! 245 bool
302 <<
303 # <<
304 # Select if the architecture provides the arch <<
305 # either provide an uncached segment alias for <<
306 # to remap the page tables in place. <<
307 # <<
308 config ARCH_HAS_DMA_SET_UNCACHED <<
309 bool <<
310 <<
311 # <<
312 # Select if the architectures provides the arc <<
313 # to undo an in-place page table remap for unc <<
314 # <<
315 config ARCH_HAS_DMA_CLEAR_UNCACHED <<
316 bool <<
317 <<
318 config ARCH_HAS_CPU_FINALIZE_INIT <<
319 bool <<
320 246
321 # The architecture has a per-task state that i !! 247 # Select if arch has its private alloc_task_struct() function
322 config ARCH_HAS_CPU_PASID !! 248 config ARCH_TASK_STRUCT_ALLOCATOR
323 bool 249 bool
324 select IOMMU_MM_DATA <<
325 250
326 config HAVE_ARCH_THREAD_STRUCT_WHITELIST 251 config HAVE_ARCH_THREAD_STRUCT_WHITELIST
327 bool 252 bool
>> 253 depends on !ARCH_TASK_STRUCT_ALLOCATOR
328 help 254 help
329 An architecture should select this t 255 An architecture should select this to provide hardened usercopy
330 knowledge about what region of the t 256 knowledge about what region of the thread_struct should be
331 whitelisted for copying to userspace 257 whitelisted for copying to userspace. Normally this is only the
332 FPU registers. Specifically, arch_th 258 FPU registers. Specifically, arch_thread_struct_whitelist()
333 should be implemented. Without this, 259 should be implemented. Without this, the entire thread_struct
334 field in task_struct will be left wh 260 field in task_struct will be left whitelisted.
335 261
336 # Select if arch wants to size task_struct dyn !! 262 # Select if arch has its private alloc_thread_stack() function
337 config ARCH_WANTS_DYNAMIC_TASK_STRUCT !! 263 config ARCH_THREAD_STACK_ALLOCATOR
338 bool 264 bool
339 265
340 config ARCH_WANTS_NO_INSTR !! 266 # Select if arch wants to size task_struct dynamically via arch_task_struct_size:
341 bool !! 267 config ARCH_WANTS_DYNAMIC_TASK_STRUCT
342 help <<
343 An architecture should select this i <<
344 functions to denote that the toolcha <<
345 functions and is required for correc <<
346 <<
347 config ARCH_32BIT_OFF_T <<
348 bool <<
349 depends on !64BIT <<
350 help <<
351 All new 32-bit architectures should <<
352 userspace side which corresponds to <<
353 is the requirement for modern ABIs. <<
354 still support 32-bit off_t. This opt <<
355 architectures explicitly. <<
356 <<
357 # Selected by 64 bit architectures which have <<
358 config ARCH_32BIT_USTAT_F_TINODE <<
359 bool <<
360 <<
361 config HAVE_ASM_MODVERSIONS <<
362 bool 268 bool
363 help <<
364 This symbol should be selected by an <<
365 <asm/asm-prototypes.h> to support th <<
366 exported from assembly code. <<
367 269
368 config HAVE_REGS_AND_STACK_ACCESS_API 270 config HAVE_REGS_AND_STACK_ACCESS_API
369 bool 271 bool
370 help 272 help
371 This symbol should be selected by an !! 273 This symbol should be selected by an architecure if it supports
372 the API needed to access registers a 274 the API needed to access registers and stack entries from pt_regs,
373 declared in asm/ptrace.h 275 declared in asm/ptrace.h
374 For example the kprobes-based event 276 For example the kprobes-based event tracer needs this API.
375 277
376 config HAVE_RSEQ 278 config HAVE_RSEQ
377 bool 279 bool
378 depends on HAVE_REGS_AND_STACK_ACCESS_ 280 depends on HAVE_REGS_AND_STACK_ACCESS_API
379 help 281 help
380 This symbol should be selected by an 282 This symbol should be selected by an architecture if it
381 supports an implementation of restar 283 supports an implementation of restartable sequences.
382 284
383 config HAVE_RUST !! 285 config HAVE_CLK
384 bool 286 bool
385 help 287 help
386 This symbol should be selected by an !! 288 The <linux/clk.h> calls support software clock gating and
387 supports Rust. !! 289 thus are a key power management tool on many systems.
388 <<
389 config HAVE_FUNCTION_ARG_ACCESS_API <<
390 bool <<
391 help <<
392 This symbol should be selected by an <<
393 the API needed to access function ar <<
394 declared in asm/ptrace.h <<
395 290
396 config HAVE_HW_BREAKPOINT 291 config HAVE_HW_BREAKPOINT
397 bool 292 bool
398 depends on PERF_EVENTS 293 depends on PERF_EVENTS
399 294
400 config HAVE_MIXED_BREAKPOINTS_REGS 295 config HAVE_MIXED_BREAKPOINTS_REGS
401 bool 296 bool
402 depends on HAVE_HW_BREAKPOINT 297 depends on HAVE_HW_BREAKPOINT
403 help 298 help
404 Depending on the arch implementation 299 Depending on the arch implementation of hardware breakpoints,
405 some of them have separate registers 300 some of them have separate registers for data and instruction
406 breakpoints addresses, others have m 301 breakpoints addresses, others have mixed registers to store
407 them but define the access type in a 302 them but define the access type in a control register.
408 Select this option if your arch impl 303 Select this option if your arch implements breakpoints under the
409 latter fashion. 304 latter fashion.
410 305
411 config HAVE_USER_RETURN_NOTIFIER 306 config HAVE_USER_RETURN_NOTIFIER
412 bool 307 bool
413 308
414 config HAVE_PERF_EVENTS_NMI 309 config HAVE_PERF_EVENTS_NMI
415 bool 310 bool
416 help 311 help
417 System hardware can generate an NMI 312 System hardware can generate an NMI using the perf event
418 subsystem. Also has support for cal 313 subsystem. Also has support for calculating CPU cycle events
419 to determine how many clock cycles i 314 to determine how many clock cycles in a given period.
420 315
421 config HAVE_HARDLOCKUP_DETECTOR_PERF 316 config HAVE_HARDLOCKUP_DETECTOR_PERF
422 bool 317 bool
423 depends on HAVE_PERF_EVENTS_NMI 318 depends on HAVE_PERF_EVENTS_NMI
424 help 319 help
425 The arch chooses to use the generic 320 The arch chooses to use the generic perf-NMI-based hardlockup
426 detector. Must define HAVE_PERF_EVEN 321 detector. Must define HAVE_PERF_EVENTS_NMI.
427 322
428 config HAVE_HARDLOCKUP_DETECTOR_ARCH !! 323 config HAVE_NMI_WATCHDOG
>> 324 depends on HAVE_NMI
429 bool 325 bool
430 help 326 help
431 The arch provides its own hardlockup !! 327 The arch provides a low level NMI watchdog. It provides
432 of the generic ones. !! 328 asm/nmi.h, and defines its own arch_touch_nmi_watchdog().
433 329
434 It uses the same command line parame !! 330 config HAVE_HARDLOCKUP_DETECTOR_ARCH
435 as the generic hardlockup detectors. !! 331 bool
>> 332 select HAVE_NMI_WATCHDOG
>> 333 help
>> 334 The arch chooses to provide its own hardlockup detector, which is
>> 335 a superset of the HAVE_NMI_WATCHDOG. It also conforms to config
>> 336 interfaces and parameters provided by hardlockup detector subsystem.
436 337
437 config HAVE_PERF_REGS 338 config HAVE_PERF_REGS
438 bool 339 bool
439 help 340 help
440 Support selective register dumps for 341 Support selective register dumps for perf events. This includes
441 bit-mapping of each registers and a 342 bit-mapping of each registers and a unique architecture id.
442 343
443 config HAVE_PERF_USER_STACK_DUMP 344 config HAVE_PERF_USER_STACK_DUMP
444 bool 345 bool
445 help 346 help
446 Support user stack dumps for perf ev 347 Support user stack dumps for perf event samples. This needs
447 access to the user stack pointer whi 348 access to the user stack pointer which is not unified across
448 architectures. 349 architectures.
449 350
450 config HAVE_ARCH_JUMP_LABEL 351 config HAVE_ARCH_JUMP_LABEL
451 bool 352 bool
452 353
453 config HAVE_ARCH_JUMP_LABEL_RELATIVE !! 354 config HAVE_RCU_TABLE_FREE
454 bool <<
455 <<
456 config MMU_GATHER_TABLE_FREE <<
457 bool <<
458 <<
459 config MMU_GATHER_RCU_TABLE_FREE <<
460 bool <<
461 select MMU_GATHER_TABLE_FREE <<
462 <<
463 config MMU_GATHER_PAGE_SIZE <<
464 bool <<
465 <<
466 config MMU_GATHER_NO_RANGE <<
467 bool <<
468 select MMU_GATHER_MERGE_VMAS <<
469 <<
470 config MMU_GATHER_NO_FLUSH_CACHE <<
471 bool <<
472 <<
473 config MMU_GATHER_MERGE_VMAS <<
474 bool <<
475 <<
476 config MMU_GATHER_NO_GATHER <<
477 bool 355 bool
478 depends on MMU_GATHER_TABLE_FREE <<
479 356
480 config ARCH_WANT_IRQS_OFF_ACTIVATE_MM !! 357 config HAVE_RCU_TABLE_INVALIDATE
481 bool <<
482 help <<
483 Temporary select until all architect <<
484 irqs disabled over activate_mm. Arch <<
485 shootdowns should enable this. <<
486 <<
487 # Use normal mm refcounting for MMU_LAZY_TLB k <<
488 # MMU_LAZY_TLB_REFCOUNT=n can improve the scal <<
489 # to/from kernel threads when the same mm is r <<
490 # multi-threaded application), by reducing con <<
491 # <<
492 # This can be disabled if the architecture ens <<
493 # "lazy tlb" beyond its final refcount (i.e., <<
494 # or its kernel page tables). This could be ar <<
495 # final exit(2) TLB flush, for example. <<
496 # <<
497 # To implement this, an arch *must*: <<
498 # Ensure the _lazy_tlb variants of mmgrab/mmdr <<
499 # the lazy tlb reference of a kthread's ->acti <<
500 # converted already). <<
501 config MMU_LAZY_TLB_REFCOUNT <<
502 def_bool y <<
503 depends on !MMU_LAZY_TLB_SHOOTDOWN <<
504 <<
505 # This option allows MMU_LAZY_TLB_REFCOUNT=n. <<
506 # mm as a lazy tlb beyond its last reference c <<
507 # users before the mm is deallocated. __mmdrop <<
508 # be using the mm as a lazy tlb, so that they <<
509 # init_mm for their active mm. mm_cpumask(mm) <<
510 # may be using mm as a lazy tlb mm. <<
511 # <<
512 # To implement this, an arch *must*: <<
513 # - At the time of the final mmdrop of the mm, <<
514 # at least all possible CPUs in which the mm <<
515 # - It must meet the requirements for MMU_LAZY <<
516 config MMU_LAZY_TLB_SHOOTDOWN <<
517 bool 358 bool
518 359
519 config ARCH_HAVE_NMI_SAFE_CMPXCHG 360 config ARCH_HAVE_NMI_SAFE_CMPXCHG
520 bool 361 bool
521 362
522 config ARCH_HAVE_EXTRA_ELF_NOTES <<
523 bool <<
524 help <<
525 An architecture should select this i <<
526 arch-specific ELF note section to co <<
527 functions: elf_coredump_extra_notes_ <<
528 elf_coredump_extra_notes_write() whi <<
529 dumper. <<
530 <<
531 config ARCH_HAS_NMI_SAFE_THIS_CPU_OPS <<
532 bool <<
533 <<
534 config HAVE_ALIGNED_STRUCT_PAGE 363 config HAVE_ALIGNED_STRUCT_PAGE
535 bool 364 bool
536 help 365 help
537 This makes sure that struct pages ar 366 This makes sure that struct pages are double word aligned and that
538 e.g. the SLUB allocator can perform 367 e.g. the SLUB allocator can perform double word atomic operations
539 on a struct page for better performa 368 on a struct page for better performance. However selecting this
540 might increase the size of a struct 369 might increase the size of a struct page by a word.
541 370
542 config HAVE_CMPXCHG_LOCAL 371 config HAVE_CMPXCHG_LOCAL
543 bool 372 bool
544 373
545 config HAVE_CMPXCHG_DOUBLE 374 config HAVE_CMPXCHG_DOUBLE
546 bool 375 bool
547 376
548 config ARCH_WEAK_RELEASE_ACQUIRE 377 config ARCH_WEAK_RELEASE_ACQUIRE
549 bool 378 bool
550 379
551 config ARCH_WANT_IPC_PARSE_VERSION 380 config ARCH_WANT_IPC_PARSE_VERSION
552 bool 381 bool
553 382
554 config ARCH_WANT_COMPAT_IPC_PARSE_VERSION 383 config ARCH_WANT_COMPAT_IPC_PARSE_VERSION
555 bool 384 bool
556 385
557 config ARCH_WANT_OLD_COMPAT_IPC 386 config ARCH_WANT_OLD_COMPAT_IPC
558 select ARCH_WANT_COMPAT_IPC_PARSE_VERS 387 select ARCH_WANT_COMPAT_IPC_PARSE_VERSION
559 bool 388 bool
560 389
561 config HAVE_ARCH_SECCOMP <<
562 bool <<
563 help <<
564 An arch should select this symbol to <<
565 syscall policy), and must provide an <<
566 and compat syscalls if the asm-gener <<
567 - __NR_seccomp_read_32 <<
568 - __NR_seccomp_write_32 <<
569 - __NR_seccomp_exit_32 <<
570 - __NR_seccomp_sigreturn_32 <<
571 <<
572 config HAVE_ARCH_SECCOMP_FILTER 390 config HAVE_ARCH_SECCOMP_FILTER
573 bool 391 bool
574 select HAVE_ARCH_SECCOMP <<
575 help 392 help
576 An arch should select this symbol if 393 An arch should select this symbol if it provides all of these things:
577 - all the requirements for HAVE_ARCH <<
578 - syscall_get_arch() 394 - syscall_get_arch()
579 - syscall_get_arguments() 395 - syscall_get_arguments()
580 - syscall_rollback() 396 - syscall_rollback()
581 - syscall_set_return_value() 397 - syscall_set_return_value()
582 - SIGSYS siginfo_t support 398 - SIGSYS siginfo_t support
583 - secure_computing is called from a 399 - secure_computing is called from a ptrace_event()-safe context
584 - secure_computing return value is c 400 - secure_computing return value is checked and a return value of -1
585 results in the system call being s 401 results in the system call being skipped immediately.
586 - seccomp syscall wired up 402 - seccomp syscall wired up
587 - if !HAVE_SPARSE_SYSCALL_NR, have S <<
588 SECCOMP_ARCH_NATIVE_NR, SECCOMP_AR <<
589 COMPAT is supported, have the SECC <<
590 <<
591 config SECCOMP <<
592 prompt "Enable seccomp to safely execu <<
593 def_bool y <<
594 depends on HAVE_ARCH_SECCOMP <<
595 help <<
596 This kernel feature is useful for nu <<
597 that may need to handle untrusted by <<
598 execution. By using pipes or other t <<
599 to the process as file descriptors s <<
600 syscalls, it's possible to isolate t <<
601 own address space using seccomp. Onc <<
602 prctl(PR_SET_SECCOMP) or the seccomp <<
603 disabled and the task is only allowe <<
604 syscalls defined by each seccomp mod <<
605 <<
606 If unsure, say Y. <<
607 403
608 config SECCOMP_FILTER 404 config SECCOMP_FILTER
609 def_bool y 405 def_bool y
610 depends on HAVE_ARCH_SECCOMP_FILTER && 406 depends on HAVE_ARCH_SECCOMP_FILTER && SECCOMP && NET
611 help 407 help
612 Enable tasks to build secure computi 408 Enable tasks to build secure computing environments defined
613 in terms of Berkeley Packet Filter p 409 in terms of Berkeley Packet Filter programs which implement
614 task-defined system call filtering p 410 task-defined system call filtering polices.
615 411
616 See Documentation/userspace-api/secc 412 See Documentation/userspace-api/seccomp_filter.rst for details.
617 413
618 config SECCOMP_CACHE_DEBUG !! 414 preferred-plugin-hostcc := $(if-success,[ $(gcc-version) -ge 40800 ],$(HOSTCXX),$(HOSTCC))
619 bool "Show seccomp filter cache status <<
620 depends on SECCOMP_FILTER && !HAVE_SPA <<
621 depends on PROC_FS <<
622 help <<
623 This enables the /proc/pid/seccomp_c <<
624 seccomp cache data. The file format <<
625 the file requires CAP_SYS_ADMIN. <<
626 415
627 This option is for debugging only. E !! 416 config PLUGIN_HOSTCC
628 an adversary may be able to infer th !! 417 string
>> 418 default "$(shell,$(srctree)/scripts/gcc-plugin.sh "$(preferred-plugin-hostcc)" "$(HOSTCXX)" "$(CC)")"
>> 419 help
>> 420 Host compiler used to build GCC plugins. This can be $(HOSTCXX),
>> 421 $(HOSTCC), or a null string if GCC plugin is unsupported.
629 422
630 If unsure, say N. !! 423 config HAVE_GCC_PLUGINS
>> 424 bool
>> 425 help
>> 426 An arch should select this symbol if it supports building with
>> 427 GCC plugins.
>> 428
>> 429 menuconfig GCC_PLUGINS
>> 430 bool "GCC plugins"
>> 431 depends on HAVE_GCC_PLUGINS
>> 432 depends on PLUGIN_HOSTCC != ""
>> 433 help
>> 434 GCC plugins are loadable modules that provide extra features to the
>> 435 compiler. They are useful for runtime instrumentation and static analysis.
>> 436
>> 437 See Documentation/gcc-plugins.txt for details.
>> 438
>> 439 config GCC_PLUGIN_CYC_COMPLEXITY
>> 440 bool "Compute the cyclomatic complexity of a function" if EXPERT
>> 441 depends on GCC_PLUGINS
>> 442 depends on !COMPILE_TEST # too noisy
>> 443 help
>> 444 The complexity M of a function's control flow graph is defined as:
>> 445 M = E - N + 2P
>> 446 where
631 447
632 config HAVE_ARCH_STACKLEAK !! 448 E = the number of edges
>> 449 N = the number of nodes
>> 450 P = the number of connected components (exit nodes).
>> 451
>> 452 Enabling this plugin reports the complexity to stderr during the
>> 453 build. It mainly serves as a simple example of how to create a
>> 454 gcc plugin for the kernel.
>> 455
>> 456 config GCC_PLUGIN_SANCOV
633 bool 457 bool
>> 458 depends on GCC_PLUGINS
>> 459 help
>> 460 This plugin inserts a __sanitizer_cov_trace_pc() call at the start of
>> 461 basic blocks. It supports all gcc versions with plugin support (from
>> 462 gcc-4.5 on). It is based on the commit "Add fuzzing coverage support"
>> 463 by Dmitry Vyukov <dvyukov@google.com>.
>> 464
>> 465 config GCC_PLUGIN_LATENT_ENTROPY
>> 466 bool "Generate some entropy during boot and runtime"
>> 467 depends on GCC_PLUGINS
>> 468 help
>> 469 By saying Y here the kernel will instrument some kernel code to
>> 470 extract some entropy from both original and artificially created
>> 471 program state. This will help especially embedded systems where
>> 472 there is little 'natural' source of entropy normally. The cost
>> 473 is some slowdown of the boot process (about 0.5%) and fork and
>> 474 irq processing.
>> 475
>> 476 Note that entropy extracted this way is not cryptographically
>> 477 secure!
>> 478
>> 479 This plugin was ported from grsecurity/PaX. More information at:
>> 480 * https://grsecurity.net/
>> 481 * https://pax.grsecurity.net/
>> 482
>> 483 config GCC_PLUGIN_STRUCTLEAK
>> 484 bool "Force initialization of variables containing userspace addresses"
>> 485 depends on GCC_PLUGINS
>> 486 # Currently STRUCTLEAK inserts initialization out of live scope of
>> 487 # variables from KASAN point of view. This leads to KASAN false
>> 488 # positive reports. Prohibit this combination for now.
>> 489 depends on !KASAN_EXTRA
634 help 490 help
635 An architecture should select this i !! 491 This plugin zero-initializes any structures containing a
636 fills the used part of the kernel st !! 492 __user attribute. This can prevent some classes of information
637 value before returning from system c !! 493 exposures.
>> 494
>> 495 This plugin was ported from grsecurity/PaX. More information at:
>> 496 * https://grsecurity.net/
>> 497 * https://pax.grsecurity.net/
>> 498
>> 499 config GCC_PLUGIN_STRUCTLEAK_BYREF_ALL
>> 500 bool "Force initialize all struct type variables passed by reference"
>> 501 depends on GCC_PLUGIN_STRUCTLEAK
>> 502 depends on !COMPILE_TEST
>> 503 help
>> 504 Zero initialize any struct type local variable that may be passed by
>> 505 reference without having been initialized.
>> 506
>> 507 config GCC_PLUGIN_STRUCTLEAK_VERBOSE
>> 508 bool "Report forcefully initialized variables"
>> 509 depends on GCC_PLUGIN_STRUCTLEAK
>> 510 depends on !COMPILE_TEST # too noisy
>> 511 help
>> 512 This option will cause a warning to be printed each time the
>> 513 structleak plugin finds a variable it thinks needs to be
>> 514 initialized. Since not all existing initializers are detected
>> 515 by the plugin, this can produce false positive warnings.
>> 516
>> 517 config GCC_PLUGIN_RANDSTRUCT
>> 518 bool "Randomize layout of sensitive kernel structures"
>> 519 depends on GCC_PLUGINS
>> 520 select MODVERSIONS if MODULES
>> 521 help
>> 522 If you say Y here, the layouts of structures that are entirely
>> 523 function pointers (and have not been manually annotated with
>> 524 __no_randomize_layout), or structures that have been explicitly
>> 525 marked with __randomize_layout, will be randomized at compile-time.
>> 526 This can introduce the requirement of an additional information
>> 527 exposure vulnerability for exploits targeting these structure
>> 528 types.
>> 529
>> 530 Enabling this feature will introduce some performance impact,
>> 531 slightly increase memory usage, and prevent the use of forensic
>> 532 tools like Volatility against the system (unless the kernel
>> 533 source tree isn't cleaned after kernel installation).
>> 534
>> 535 The seed used for compilation is located at
>> 536 scripts/gcc-plgins/randomize_layout_seed.h. It remains after
>> 537 a make clean to allow for external modules to be compiled with
>> 538 the existing seed and will be removed by a make mrproper or
>> 539 make distclean.
>> 540
>> 541 Note that the implementation requires gcc 4.7 or newer.
>> 542
>> 543 This plugin was ported from grsecurity/PaX. More information at:
>> 544 * https://grsecurity.net/
>> 545 * https://pax.grsecurity.net/
>> 546
>> 547 config GCC_PLUGIN_RANDSTRUCT_PERFORMANCE
>> 548 bool "Use cacheline-aware structure randomization"
>> 549 depends on GCC_PLUGIN_RANDSTRUCT
>> 550 depends on !COMPILE_TEST # do not reduce test coverage
>> 551 help
>> 552 If you say Y here, the RANDSTRUCT randomization will make a
>> 553 best effort at restricting randomization to cacheline-sized
>> 554 groups of elements. It will further not randomize bitfields
>> 555 in structures. This reduces the performance hit of RANDSTRUCT
>> 556 at the cost of weakened randomization.
638 557
639 config HAVE_STACKPROTECTOR 558 config HAVE_STACKPROTECTOR
640 bool 559 bool
641 help 560 help
642 An arch should select this symbol if 561 An arch should select this symbol if:
643 - it has implemented a stack canary 562 - it has implemented a stack canary (e.g. __stack_chk_guard)
644 563
>> 564 config CC_HAS_STACKPROTECTOR_NONE
>> 565 def_bool $(cc-option,-fno-stack-protector)
>> 566
645 config STACKPROTECTOR 567 config STACKPROTECTOR
646 bool "Stack Protector buffer overflow 568 bool "Stack Protector buffer overflow detection"
647 depends on HAVE_STACKPROTECTOR 569 depends on HAVE_STACKPROTECTOR
648 depends on $(cc-option,-fstack-protect 570 depends on $(cc-option,-fstack-protector)
649 default y 571 default y
650 help 572 help
651 This option turns on the "stack-prot 573 This option turns on the "stack-protector" GCC feature. This
652 feature puts, at the beginning of fu 574 feature puts, at the beginning of functions, a canary value on
653 the stack just before the return add 575 the stack just before the return address, and validates
654 the value just before actually retur 576 the value just before actually returning. Stack based buffer
655 overflows (that need to overwrite th 577 overflows (that need to overwrite this return address) now also
656 overwrite the canary, which gets det 578 overwrite the canary, which gets detected and the attack is then
657 neutralized via a kernel panic. 579 neutralized via a kernel panic.
658 580
659 Functions will have the stack-protec 581 Functions will have the stack-protector canary logic added if they
660 have an 8-byte or larger character a 582 have an 8-byte or larger character array on the stack.
661 583
662 This feature requires gcc version 4. 584 This feature requires gcc version 4.2 or above, or a distribution
663 gcc with the feature backported ("-f 585 gcc with the feature backported ("-fstack-protector").
664 586
665 On an x86 "defconfig" build, this fe 587 On an x86 "defconfig" build, this feature adds canary checks to
666 about 3% of all kernel functions, wh 588 about 3% of all kernel functions, which increases kernel code size
667 by about 0.3%. 589 by about 0.3%.
668 590
669 config STACKPROTECTOR_STRONG 591 config STACKPROTECTOR_STRONG
670 bool "Strong Stack Protector" 592 bool "Strong Stack Protector"
671 depends on STACKPROTECTOR 593 depends on STACKPROTECTOR
672 depends on $(cc-option,-fstack-protect 594 depends on $(cc-option,-fstack-protector-strong)
673 default y 595 default y
674 help 596 help
675 Functions will have the stack-protec 597 Functions will have the stack-protector canary logic added in any
676 of the following conditions: 598 of the following conditions:
677 599
678 - local variable's address used as p 600 - local variable's address used as part of the right hand side of an
679 assignment or function argument 601 assignment or function argument
680 - local variable is an array (or uni 602 - local variable is an array (or union containing an array),
681 regardless of array type or length 603 regardless of array type or length
682 - uses register local variables 604 - uses register local variables
683 605
684 This feature requires gcc version 4. 606 This feature requires gcc version 4.9 or above, or a distribution
685 gcc with the feature backported ("-f 607 gcc with the feature backported ("-fstack-protector-strong").
686 608
687 On an x86 "defconfig" build, this fe 609 On an x86 "defconfig" build, this feature adds canary checks to
688 about 20% of all kernel functions, w 610 about 20% of all kernel functions, which increases the kernel code
689 size by about 2%. 611 size by about 2%.
690 612
691 config ARCH_SUPPORTS_SHADOW_CALL_STACK <<
692 bool <<
693 help <<
694 An architecture should select this i <<
695 Shadow Call Stack and implements run <<
696 switching. <<
697 <<
698 config SHADOW_CALL_STACK <<
699 bool "Shadow Call Stack" <<
700 depends on ARCH_SUPPORTS_SHADOW_CALL_S <<
701 depends on DYNAMIC_FTRACE_WITH_ARGS || <<
702 depends on MMU <<
703 help <<
704 This option enables the compiler's S <<
705 uses a shadow stack to protect funct <<
706 being overwritten by an attacker. Mo <<
707 in the compiler's documentation: <<
708 <<
709 - Clang: https://clang.llvm.org/docs <<
710 - GCC: https://gcc.gnu.org/onlinedoc <<
711 <<
712 Note that security guarantees in the <<
713 ones documented for user space. The <<
714 of shadow stacks in memory, which me <<
715 reading and writing arbitrary memory <<
716 and hijack control flow by modifying <<
717 <<
718 config DYNAMIC_SCS <<
719 bool <<
720 help <<
721 Set by the arch code if it relies on <<
722 shadow call stack push and pop instr <<
723 compiler. <<
724 <<
725 config LTO <<
726 bool <<
727 help <<
728 Selected if the kernel will be built <<
729 <<
730 config LTO_CLANG <<
731 bool <<
732 select LTO <<
733 help <<
734 Selected if the kernel will be built <<
735 <<
736 config ARCH_SUPPORTS_LTO_CLANG <<
737 bool <<
738 help <<
739 An architecture should select this o <<
740 - compiling with Clang, <<
741 - compiling inline assembly with Cla <<
742 - and linking with LLD. <<
743 <<
744 config ARCH_SUPPORTS_LTO_CLANG_THIN <<
745 bool <<
746 help <<
747 An architecture should select this o <<
748 ThinLTO mode. <<
749 <<
750 config HAS_LTO_CLANG <<
751 def_bool y <<
752 depends on CC_IS_CLANG && LD_IS_LLD && <<
753 depends on $(success,$(NM) --help | he <<
754 depends on $(success,$(AR) --help | he <<
755 depends on ARCH_SUPPORTS_LTO_CLANG <<
756 depends on !FTRACE_MCOUNT_USE_RECORDMC <<
757 # https://github.com/ClangBuiltLinux/l <<
758 depends on (!KASAN || KASAN_HW_TAGS || <<
759 depends on (!KCOV || CLANG_VERSION >= <<
760 depends on !GCOV_KERNEL <<
761 help <<
762 The compiler and Kconfig options sup <<
763 LTO. <<
764 <<
765 choice <<
766 prompt "Link Time Optimization (LTO)" <<
767 default LTO_NONE <<
768 help <<
769 This option enables Link Time Optimi <<
770 compiler to optimize binaries global <<
771 <<
772 If unsure, select LTO_NONE. Note tha <<
773 so it's disabled by default. <<
774 <<
775 config LTO_NONE <<
776 bool "None" <<
777 help <<
778 Build the kernel normally, without L <<
779 <<
780 config LTO_CLANG_FULL <<
781 bool "Clang Full LTO (EXPERIMENTAL)" <<
782 depends on HAS_LTO_CLANG <<
783 depends on !COMPILE_TEST <<
784 select LTO_CLANG <<
785 help <<
786 This option enables Clang's full Lin <<
787 allows the compiler to optimize the <<
788 this option, the compiler generates <<
789 object files, and the actual compila <<
790 the LTO link step, which may take se <<
791 kernel configuration. More informati <<
792 documentation: <<
793 <<
794 https://llvm.org/docs/LinkTimeOpti <<
795 <<
796 During link time, this option can us <<
797 may take much longer than the ThinLT <<
798 <<
799 config LTO_CLANG_THIN <<
800 bool "Clang ThinLTO (EXPERIMENTAL)" <<
801 depends on HAS_LTO_CLANG && ARCH_SUPPO <<
802 select LTO_CLANG <<
803 help <<
804 This option enables Clang's ThinLTO, <<
805 optimization and faster incremental <<
806 CONFIG_LTO_CLANG_FULL option. More i <<
807 from Clang's documentation: <<
808 <<
809 https://clang.llvm.org/docs/ThinLT <<
810 <<
811 If unsure, say Y. <<
812 endchoice <<
813 <<
814 config ARCH_SUPPORTS_CFI_CLANG <<
815 bool <<
816 help <<
817 An architecture should select this o <<
818 Control-Flow Integrity (CFI) checkin <<
819 <<
820 config ARCH_USES_CFI_TRAPS <<
821 bool <<
822 <<
823 config CFI_CLANG <<
824 bool "Use Clang's Control Flow Integri <<
825 depends on ARCH_SUPPORTS_CFI_CLANG <<
826 depends on $(cc-option,-fsanitize=kcfi <<
827 help <<
828 This option enables Clang's forward- <<
829 (CFI) checking, where the compiler i <<
830 indirect function call to ensure the <<
831 the correct static type. This restri <<
832 makes it more difficult for an attac <<
833 the modification of stored function <<
834 found from Clang's documentation: <<
835 <<
836 https://clang.llvm.org/docs/Contro <<
837 <<
838 config CFI_ICALL_NORMALIZE_INTEGERS <<
839 bool "Normalize CFI tags for integers" <<
840 depends on CFI_CLANG <<
841 depends on HAVE_CFI_ICALL_NORMALIZE_IN <<
842 help <<
843 This option normalizes the CFI tags <<
844 integer types of the same size and s <<
845 tag. <<
846 <<
847 The option is separate from CONFIG_R <<
848 When working with build systems that <<
849 convenient to be able to turn on thi <<
850 turned on. <<
851 <<
852 This option is necessary for using C <<
853 <<
854 config HAVE_CFI_ICALL_NORMALIZE_INTEGERS_CLANG <<
855 def_bool y <<
856 depends on $(cc-option,-fsanitize=kcfi <<
857 # With GCOV/KASAN we need this fix: ht <<
858 depends on CLANG_VERSION >= 190103 || <<
859 <<
860 config HAVE_CFI_ICALL_NORMALIZE_INTEGERS_RUSTC <<
861 def_bool y <<
862 depends on HAVE_CFI_ICALL_NORMALIZE_IN <<
863 depends on RUSTC_VERSION >= 107900 <<
864 # With GCOV/KASAN we need this fix: ht <<
865 depends on (RUSTC_LLVM_VERSION >= 1901 <<
866 (!GCOV_KERNEL && !KASAN_GENERI <<
867 <<
868 config CFI_PERMISSIVE <<
869 bool "Use CFI in permissive mode" <<
870 depends on CFI_CLANG <<
871 help <<
872 When selected, Control Flow Integrit <<
873 warning instead of a kernel panic. T <<
874 for finding indirect call type misma <<
875 <<
876 If unsure, say N. <<
877 <<
878 config HAVE_ARCH_WITHIN_STACK_FRAMES 613 config HAVE_ARCH_WITHIN_STACK_FRAMES
879 bool 614 bool
880 help 615 help
881 An architecture should select this i 616 An architecture should select this if it can walk the kernel stack
882 frames to determine if an object is 617 frames to determine if an object is part of either the arguments
883 or local variables (i.e. that it exc 618 or local variables (i.e. that it excludes saved return addresses,
884 and similar) by implementing an inli 619 and similar) by implementing an inline arch_within_stack_frames(),
885 which is used by CONFIG_HARDENED_USE 620 which is used by CONFIG_HARDENED_USERCOPY.
886 621
887 config HAVE_CONTEXT_TRACKING_USER !! 622 config HAVE_CONTEXT_TRACKING
888 bool 623 bool
889 help 624 help
890 Provide kernel/user boundaries probe 625 Provide kernel/user boundaries probes necessary for subsystems
891 that need it, such as userspace RCU 626 that need it, such as userspace RCU extended quiescent state.
892 Syscalls need to be wrapped inside u !! 627 Syscalls need to be wrapped inside user_exit()-user_enter() through
893 optimized behind static key or throu !! 628 the slow path using TIF_NOHZ flag. Exceptions handlers must be
894 flag. Exceptions handlers must be wr !! 629 wrapped as well. Irqs are already protected inside
895 protected inside ct_irq_enter/ct_irq !! 630 rcu_irq_enter/rcu_irq_exit() but preemption or signal handling on
896 handling on irq exit still need to b !! 631 irq exit still need to be protected.
897 <<
898 config HAVE_CONTEXT_TRACKING_USER_OFFSTACK <<
899 bool <<
900 help <<
901 Architecture neither relies on excep <<
902 nor on schedule_user(). Also preempt <<
903 preempt_schedule_irq() can't be call <<
904 while context tracking is CT_STATE_U <<
905 entry implementation where the follo <<
906 critical entry code, ie: before user <<
907 <<
908 - Critical entry code isn't preempti <<
909 not interruptible). <<
910 - No use of RCU read side critical s <<
911 got called. <<
912 - No use of instrumentation, unless <<
913 called. <<
914 <<
915 config HAVE_TIF_NOHZ <<
916 bool <<
917 help <<
918 Arch relies on TIF_NOHZ and syscall <<
919 tracking calls to user_enter()/user_ <<
920 632
921 config HAVE_VIRT_CPU_ACCOUNTING 633 config HAVE_VIRT_CPU_ACCOUNTING
922 bool 634 bool
923 635
924 config HAVE_VIRT_CPU_ACCOUNTING_IDLE <<
925 bool <<
926 help <<
927 Architecture has its own way to acco <<
928 doesn't implement vtime_account_idle <<
929 <<
930 config ARCH_HAS_SCALED_CPUTIME 636 config ARCH_HAS_SCALED_CPUTIME
931 bool 637 bool
932 638
933 config HAVE_VIRT_CPU_ACCOUNTING_GEN 639 config HAVE_VIRT_CPU_ACCOUNTING_GEN
934 bool 640 bool
935 default y if 64BIT 641 default y if 64BIT
936 help 642 help
937 With VIRT_CPU_ACCOUNTING_GEN, cputim 643 With VIRT_CPU_ACCOUNTING_GEN, cputime_t becomes 64-bit.
938 Before enabling this option, arch co 644 Before enabling this option, arch code must be audited
939 to ensure there are no races in conc 645 to ensure there are no races in concurrent read/write of
940 cputime_t. For example, reading/writ 646 cputime_t. For example, reading/writing 64-bit cputime_t on
941 some 32-bit arches may require multi 647 some 32-bit arches may require multiple accesses, so proper
942 locking is needed to protect against 648 locking is needed to protect against concurrent accesses.
943 649
>> 650
944 config HAVE_IRQ_TIME_ACCOUNTING 651 config HAVE_IRQ_TIME_ACCOUNTING
945 bool 652 bool
946 help 653 help
947 Archs need to ensure they use a high 654 Archs need to ensure they use a high enough resolution clock to
948 support irq time accounting and then 655 support irq time accounting and then call enable_sched_clock_irqtime().
949 656
950 config HAVE_MOVE_PUD <<
951 bool <<
952 help <<
953 Architectures that select this are a <<
954 PUD level. If there are only 3 page <<
955 happens at the PGD level. <<
956 <<
957 config HAVE_MOVE_PMD <<
958 bool <<
959 help <<
960 Archs that select this are able to m <<
961 <<
962 config HAVE_ARCH_TRANSPARENT_HUGEPAGE 657 config HAVE_ARCH_TRANSPARENT_HUGEPAGE
963 bool 658 bool
964 659
965 config HAVE_ARCH_TRANSPARENT_HUGEPAGE_PUD 660 config HAVE_ARCH_TRANSPARENT_HUGEPAGE_PUD
966 bool 661 bool
967 662
968 config HAVE_ARCH_HUGE_VMAP 663 config HAVE_ARCH_HUGE_VMAP
969 bool 664 bool
970 665
971 # <<
972 # Archs that select this would be capable of <<
973 # arch_vmap_pmd_supported() returns true). Th <<
974 # must be used to enable allocations to use h <<
975 # <<
976 config HAVE_ARCH_HUGE_VMALLOC <<
977 depends on HAVE_ARCH_HUGE_VMAP <<
978 bool <<
979 <<
980 config ARCH_WANT_HUGE_PMD_SHARE <<
981 bool <<
982 <<
983 # Archs that want to use pmd_mkwrite on kernel <<
984 # if there are no userspace memory management <<
985 config ARCH_WANT_KERNEL_PMD_MKWRITE <<
986 bool <<
987 <<
988 config ARCH_WANT_PMD_MKWRITE <<
989 def_bool TRANSPARENT_HUGEPAGE || ARCH_ <<
990 <<
991 config HAVE_ARCH_SOFT_DIRTY 666 config HAVE_ARCH_SOFT_DIRTY
992 bool 667 bool
993 668
994 config HAVE_MOD_ARCH_SPECIFIC 669 config HAVE_MOD_ARCH_SPECIFIC
995 bool 670 bool
996 help 671 help
997 The arch uses struct mod_arch_specif 672 The arch uses struct mod_arch_specific to store data. Many arches
998 just need a simple module loader wit 673 just need a simple module loader without arch specific data - those
999 should not enable this. 674 should not enable this.
1000 675
1001 config MODULES_USE_ELF_RELA 676 config MODULES_USE_ELF_RELA
1002 bool 677 bool
1003 help 678 help
1004 Modules only use ELF RELA relocatio 679 Modules only use ELF RELA relocations. Modules with ELF REL
1005 relocations will give an error. 680 relocations will give an error.
1006 681
1007 config MODULES_USE_ELF_REL 682 config MODULES_USE_ELF_REL
1008 bool 683 bool
1009 help 684 help
1010 Modules only use ELF REL relocation 685 Modules only use ELF REL relocations. Modules with ELF RELA
1011 relocations will give an error. 686 relocations will give an error.
1012 687
1013 config ARCH_WANTS_MODULES_DATA_IN_VMALLOC <<
1014 bool <<
1015 help <<
1016 For architectures like powerpc/32 w <<
1017 allocation and need to allocate mod <<
1018 <<
1019 config ARCH_WANTS_EXECMEM_LATE <<
1020 bool <<
1021 help <<
1022 For architectures that do not alloc <<
1023 boot, but rather require its initia <<
1024 enough entropy for module space ran <<
1025 arm64. <<
1026 <<
1027 config HAVE_IRQ_EXIT_ON_IRQ_STACK 688 config HAVE_IRQ_EXIT_ON_IRQ_STACK
1028 bool 689 bool
1029 help 690 help
1030 Architecture doesn't only execute t 691 Architecture doesn't only execute the irq handler on the irq stack
1031 but also irq_exit(). This way we ca 692 but also irq_exit(). This way we can process softirqs on this irq
1032 stack instead of switching to a new 693 stack instead of switching to a new one when we call __do_softirq()
1033 in the end of an hardirq. 694 in the end of an hardirq.
1034 This spares a stack switch and impr 695 This spares a stack switch and improves cache usage on softirq
1035 processing. 696 processing.
1036 697
1037 config HAVE_SOFTIRQ_ON_OWN_STACK <<
1038 bool <<
1039 help <<
1040 Architecture provides a function to <<
1041 separate stack. <<
1042 <<
1043 config SOFTIRQ_ON_OWN_STACK <<
1044 def_bool HAVE_SOFTIRQ_ON_OWN_STACK && <<
1045 <<
1046 config ALTERNATE_USER_ADDRESS_SPACE <<
1047 bool <<
1048 help <<
1049 Architectures set this when the CPU <<
1050 spaces for kernel and user space po <<
1051 access_ok() check on a __user point <<
1052 <<
1053 config PGTABLE_LEVELS 698 config PGTABLE_LEVELS
1054 int 699 int
1055 default 2 700 default 2
1056 701
1057 config ARCH_HAS_ELF_RANDOMIZE 702 config ARCH_HAS_ELF_RANDOMIZE
1058 bool 703 bool
1059 help 704 help
1060 An architecture supports choosing r 705 An architecture supports choosing randomized locations for
1061 stack, mmap, brk, and ET_DYN. Defin 706 stack, mmap, brk, and ET_DYN. Defined functions:
1062 - arch_mmap_rnd() 707 - arch_mmap_rnd()
1063 - arch_randomize_brk() 708 - arch_randomize_brk()
1064 709
1065 config HAVE_ARCH_MMAP_RND_BITS 710 config HAVE_ARCH_MMAP_RND_BITS
1066 bool 711 bool
1067 help 712 help
1068 An arch should select this symbol i 713 An arch should select this symbol if it supports setting a variable
1069 number of bits for use in establish 714 number of bits for use in establishing the base address for mmap
1070 allocations, has MMU enabled and pr 715 allocations, has MMU enabled and provides values for both:
1071 - ARCH_MMAP_RND_BITS_MIN 716 - ARCH_MMAP_RND_BITS_MIN
1072 - ARCH_MMAP_RND_BITS_MAX 717 - ARCH_MMAP_RND_BITS_MAX
1073 718
1074 config HAVE_EXIT_THREAD 719 config HAVE_EXIT_THREAD
1075 bool 720 bool
1076 help 721 help
1077 An architecture implements exit_thr 722 An architecture implements exit_thread.
1078 723
1079 config ARCH_MMAP_RND_BITS_MIN 724 config ARCH_MMAP_RND_BITS_MIN
1080 int 725 int
1081 726
1082 config ARCH_MMAP_RND_BITS_MAX 727 config ARCH_MMAP_RND_BITS_MAX
1083 int 728 int
1084 729
1085 config ARCH_MMAP_RND_BITS_DEFAULT 730 config ARCH_MMAP_RND_BITS_DEFAULT
1086 int 731 int
1087 732
1088 config ARCH_MMAP_RND_BITS 733 config ARCH_MMAP_RND_BITS
1089 int "Number of bits to use for ASLR o 734 int "Number of bits to use for ASLR of mmap base address" if EXPERT
1090 range ARCH_MMAP_RND_BITS_MIN ARCH_MMA 735 range ARCH_MMAP_RND_BITS_MIN ARCH_MMAP_RND_BITS_MAX
1091 default ARCH_MMAP_RND_BITS_DEFAULT if 736 default ARCH_MMAP_RND_BITS_DEFAULT if ARCH_MMAP_RND_BITS_DEFAULT
1092 default ARCH_MMAP_RND_BITS_MIN 737 default ARCH_MMAP_RND_BITS_MIN
1093 depends on HAVE_ARCH_MMAP_RND_BITS 738 depends on HAVE_ARCH_MMAP_RND_BITS
1094 help 739 help
1095 This value can be used to select th 740 This value can be used to select the number of bits to use to
1096 determine the random offset to the 741 determine the random offset to the base address of vma regions
1097 resulting from mmap allocations. Th 742 resulting from mmap allocations. This value will be bounded
1098 by the architecture's minimum and m 743 by the architecture's minimum and maximum supported values.
1099 744
1100 This value can be changed after boo 745 This value can be changed after boot using the
1101 /proc/sys/vm/mmap_rnd_bits tunable 746 /proc/sys/vm/mmap_rnd_bits tunable
1102 747
1103 config HAVE_ARCH_MMAP_RND_COMPAT_BITS 748 config HAVE_ARCH_MMAP_RND_COMPAT_BITS
1104 bool 749 bool
1105 help 750 help
1106 An arch should select this symbol i 751 An arch should select this symbol if it supports running applications
1107 in compatibility mode, supports set 752 in compatibility mode, supports setting a variable number of bits for
1108 use in establishing the base addres 753 use in establishing the base address for mmap allocations, has MMU
1109 enabled and provides values for bot 754 enabled and provides values for both:
1110 - ARCH_MMAP_RND_COMPAT_BITS_MIN 755 - ARCH_MMAP_RND_COMPAT_BITS_MIN
1111 - ARCH_MMAP_RND_COMPAT_BITS_MAX 756 - ARCH_MMAP_RND_COMPAT_BITS_MAX
1112 757
1113 config ARCH_MMAP_RND_COMPAT_BITS_MIN 758 config ARCH_MMAP_RND_COMPAT_BITS_MIN
1114 int 759 int
1115 760
1116 config ARCH_MMAP_RND_COMPAT_BITS_MAX 761 config ARCH_MMAP_RND_COMPAT_BITS_MAX
1117 int 762 int
1118 763
1119 config ARCH_MMAP_RND_COMPAT_BITS_DEFAULT 764 config ARCH_MMAP_RND_COMPAT_BITS_DEFAULT
1120 int 765 int
1121 766
1122 config ARCH_MMAP_RND_COMPAT_BITS 767 config ARCH_MMAP_RND_COMPAT_BITS
1123 int "Number of bits to use for ASLR o 768 int "Number of bits to use for ASLR of mmap base address for compatible applications" if EXPERT
1124 range ARCH_MMAP_RND_COMPAT_BITS_MIN A 769 range ARCH_MMAP_RND_COMPAT_BITS_MIN ARCH_MMAP_RND_COMPAT_BITS_MAX
1125 default ARCH_MMAP_RND_COMPAT_BITS_DEF 770 default ARCH_MMAP_RND_COMPAT_BITS_DEFAULT if ARCH_MMAP_RND_COMPAT_BITS_DEFAULT
1126 default ARCH_MMAP_RND_COMPAT_BITS_MIN 771 default ARCH_MMAP_RND_COMPAT_BITS_MIN
1127 depends on HAVE_ARCH_MMAP_RND_COMPAT_ 772 depends on HAVE_ARCH_MMAP_RND_COMPAT_BITS
1128 help 773 help
1129 This value can be used to select th 774 This value can be used to select the number of bits to use to
1130 determine the random offset to the 775 determine the random offset to the base address of vma regions
1131 resulting from mmap allocations for 776 resulting from mmap allocations for compatible applications This
1132 value will be bounded by the archit 777 value will be bounded by the architecture's minimum and maximum
1133 supported values. 778 supported values.
1134 779
1135 This value can be changed after boo 780 This value can be changed after boot using the
1136 /proc/sys/vm/mmap_rnd_compat_bits t 781 /proc/sys/vm/mmap_rnd_compat_bits tunable
1137 782
1138 config HAVE_ARCH_COMPAT_MMAP_BASES 783 config HAVE_ARCH_COMPAT_MMAP_BASES
1139 bool 784 bool
1140 help 785 help
1141 This allows 64bit applications to i 786 This allows 64bit applications to invoke 32-bit mmap() syscall
1142 and vice-versa 32-bit applications 787 and vice-versa 32-bit applications to call 64-bit mmap().
1143 Required for applications doing dif 788 Required for applications doing different bitness syscalls.
1144 789
1145 config HAVE_PAGE_SIZE_4KB !! 790 config HAVE_COPY_THREAD_TLS
1146 bool <<
1147 <<
1148 config HAVE_PAGE_SIZE_8KB <<
1149 bool <<
1150 <<
1151 config HAVE_PAGE_SIZE_16KB <<
1152 bool <<
1153 <<
1154 config HAVE_PAGE_SIZE_32KB <<
1155 bool <<
1156 <<
1157 config HAVE_PAGE_SIZE_64KB <<
1158 bool <<
1159 <<
1160 config HAVE_PAGE_SIZE_256KB <<
1161 bool 791 bool
1162 <<
1163 choice <<
1164 prompt "MMU page size" <<
1165 <<
1166 config PAGE_SIZE_4KB <<
1167 bool "4KiB pages" <<
1168 depends on HAVE_PAGE_SIZE_4KB <<
1169 help <<
1170 This option select the standard 4Ki <<
1171 available option on many architectu <<
1172 minimize memory consumption and is <<
1173 memory systems. <<
1174 Some software that is written for x <<
1175 assumptions about the page size and <<
1176 <<
1177 config PAGE_SIZE_8KB <<
1178 bool "8KiB pages" <<
1179 depends on HAVE_PAGE_SIZE_8KB <<
1180 help <<
1181 This option is the only supported p <<
1182 processors, and can be slightly fas <<
1183 <<
1184 config PAGE_SIZE_16KB <<
1185 bool "16KiB pages" <<
1186 depends on HAVE_PAGE_SIZE_16KB <<
1187 help 792 help
1188 This option is usually a good compr !! 793 Architecture provides copy_thread_tls to accept tls argument via
1189 consumption and performance for typ !! 794 normal C parameter passing, rather than extracting the syscall
1190 workloads, often saving a level of !! 795 argument from pt_regs.
1191 to 4KB pages as well as reducing TL <<
1192 per-page operations in the kernel a <<
1193 page cache. <<
1194 <<
1195 config PAGE_SIZE_32KB <<
1196 bool "32KiB pages" <<
1197 depends on HAVE_PAGE_SIZE_32KB <<
1198 help <<
1199 Using 32KiB page size will result i <<
1200 kernel at the price of higher memor <<
1201 16KiB pages. This option is availa <<
1202 Note that you will need a suitable <<
1203 support this. <<
1204 <<
1205 config PAGE_SIZE_64KB <<
1206 bool "64KiB pages" <<
1207 depends on HAVE_PAGE_SIZE_64KB <<
1208 help <<
1209 Using 64KiB page size will result i <<
1210 kernel at the price of much higher <<
1211 4KiB or 16KiB pages. <<
1212 This is not suitable for general-pu <<
1213 better performance may be worth the <<
1214 supercomputing or database applicat <<
1215 large in-memory data rather than sm <<
1216 <<
1217 config PAGE_SIZE_256KB <<
1218 bool "256KiB pages" <<
1219 depends on HAVE_PAGE_SIZE_256KB <<
1220 help <<
1221 256KiB pages have little practical <<
1222 memory usage. The kernel will only <<
1223 that have been compiled with '-zmax <<
1224 (the default is 64KiB or 4KiB on mo <<
1225 <<
1226 endchoice <<
1227 <<
1228 config PAGE_SIZE_LESS_THAN_64KB <<
1229 def_bool y <<
1230 depends on !PAGE_SIZE_64KB <<
1231 depends on PAGE_SIZE_LESS_THAN_256KB <<
1232 <<
1233 config PAGE_SIZE_LESS_THAN_256KB <<
1234 def_bool y <<
1235 depends on !PAGE_SIZE_256KB <<
1236 <<
1237 config PAGE_SHIFT <<
1238 int <<
1239 default 12 if PAGE_SIZE_4KB <<
1240 default 13 if PAGE_SIZE_8KB <<
1241 default 14 if PAGE_SIZE_16KB <<
1242 default 15 if PAGE_SIZE_32KB <<
1243 default 16 if PAGE_SIZE_64KB <<
1244 default 18 if PAGE_SIZE_256KB <<
1245 <<
1246 # This allows to use a set of generic functio <<
1247 # address by giving priority to top-down sche <<
1248 # is not in legacy mode (compat task, unlimit <<
1249 # sysctl_legacy_va_layout). <<
1250 # Architecture that selects this option can p <<
1251 # - STACK_RND_MASK <<
1252 config ARCH_WANT_DEFAULT_TOPDOWN_MMAP_LAYOUT <<
1253 bool <<
1254 depends on MMU <<
1255 select ARCH_HAS_ELF_RANDOMIZE <<
1256 <<
1257 config HAVE_OBJTOOL <<
1258 bool <<
1259 <<
1260 config HAVE_JUMP_LABEL_HACK <<
1261 bool <<
1262 <<
1263 config HAVE_NOINSTR_HACK <<
1264 bool <<
1265 <<
1266 config HAVE_NOINSTR_VALIDATION <<
1267 bool <<
1268 <<
1269 config HAVE_UACCESS_VALIDATION <<
1270 bool <<
1271 select OBJTOOL <<
1272 796
1273 config HAVE_STACK_VALIDATION 797 config HAVE_STACK_VALIDATION
1274 bool 798 bool
1275 help 799 help
1276 Architecture supports objtool compi !! 800 Architecture supports the 'objtool check' host tool command, which
1277 validation. !! 801 performs compile-time stack metadata validation.
1278 802
1279 config HAVE_RELIABLE_STACKTRACE 803 config HAVE_RELIABLE_STACKTRACE
1280 bool 804 bool
1281 help 805 help
1282 Architecture has either save_stack_ !! 806 Architecture has a save_stack_trace_tsk_reliable() function which
1283 arch_stack_walk_reliable() function !! 807 only returns a stack trace if it can guarantee the trace is reliable.
1284 if it can guarantee the trace is re <<
1285 808
1286 config HAVE_ARCH_HASH 809 config HAVE_ARCH_HASH
1287 bool 810 bool
1288 default n 811 default n
1289 help 812 help
1290 If this is set, the architecture pr 813 If this is set, the architecture provides an <asm/hash.h>
1291 file which provides platform-specif 814 file which provides platform-specific implementations of some
1292 functions in <linux/hash.h> or fs/n 815 functions in <linux/hash.h> or fs/namei.c.
1293 816
1294 config HAVE_ARCH_NVRAM_OPS <<
1295 bool <<
1296 <<
1297 config ISA_BUS_API 817 config ISA_BUS_API
1298 def_bool ISA 818 def_bool ISA
1299 819
1300 # 820 #
1301 # ABI hall of shame 821 # ABI hall of shame
1302 # 822 #
1303 config CLONE_BACKWARDS 823 config CLONE_BACKWARDS
1304 bool 824 bool
1305 help 825 help
1306 Architecture has tls passed as the 826 Architecture has tls passed as the 4th argument of clone(2),
1307 not the 5th one. 827 not the 5th one.
1308 828
1309 config CLONE_BACKWARDS2 829 config CLONE_BACKWARDS2
1310 bool 830 bool
1311 help 831 help
1312 Architecture has the first two argu 832 Architecture has the first two arguments of clone(2) swapped.
1313 833
1314 config CLONE_BACKWARDS3 834 config CLONE_BACKWARDS3
1315 bool 835 bool
1316 help 836 help
1317 Architecture has tls passed as the 837 Architecture has tls passed as the 3rd argument of clone(2),
1318 not the 5th one. 838 not the 5th one.
1319 839
1320 config ODD_RT_SIGACTION 840 config ODD_RT_SIGACTION
1321 bool 841 bool
1322 help 842 help
1323 Architecture has unusual rt_sigacti 843 Architecture has unusual rt_sigaction(2) arguments
1324 844
1325 config OLD_SIGSUSPEND 845 config OLD_SIGSUSPEND
1326 bool 846 bool
1327 help 847 help
1328 Architecture has old sigsuspend(2) 848 Architecture has old sigsuspend(2) syscall, of one-argument variety
1329 849
1330 config OLD_SIGSUSPEND3 850 config OLD_SIGSUSPEND3
1331 bool 851 bool
1332 help 852 help
1333 Even weirder antique ABI - three-ar 853 Even weirder antique ABI - three-argument sigsuspend(2)
1334 854
1335 config OLD_SIGACTION 855 config OLD_SIGACTION
1336 bool 856 bool
1337 help 857 help
1338 Architecture has old sigaction(2) s 858 Architecture has old sigaction(2) syscall. Nope, not the same
1339 as OLD_SIGSUSPEND | OLD_SIGSUSPEND3 859 as OLD_SIGSUSPEND | OLD_SIGSUSPEND3 - alpha has sigsuspend(2),
1340 but fairly different variant of sig 860 but fairly different variant of sigaction(2), thanks to OSF/1
1341 compatibility... 861 compatibility...
1342 862
1343 config COMPAT_OLD_SIGACTION 863 config COMPAT_OLD_SIGACTION
1344 bool 864 bool
1345 865
>> 866 config 64BIT_TIME
>> 867 def_bool ARCH_HAS_64BIT_TIME
>> 868 help
>> 869 This should be selected by all architectures that need to support
>> 870 new system calls with a 64-bit time_t. This is relevant on all 32-bit
>> 871 architectures, and 64-bit architectures as part of compat syscall
>> 872 handling.
>> 873
1346 config COMPAT_32BIT_TIME 874 config COMPAT_32BIT_TIME
1347 bool "Provide system calls for 32-bit !! 875 def_bool (!64BIT && 64BIT_TIME) || COMPAT
1348 default !64BIT || COMPAT <<
1349 help 876 help
1350 This enables 32 bit time_t support 877 This enables 32 bit time_t support in addition to 64 bit time_t support.
1351 This is relevant on all 32-bit arch 878 This is relevant on all 32-bit architectures, and 64-bit architectures
1352 as part of compat syscall handling. 879 as part of compat syscall handling.
1353 880
1354 config ARCH_NO_PREEMPT !! 881 config ARCH_NO_COHERENT_DMA_MMAP
1355 bool <<
1356 <<
1357 config ARCH_SUPPORTS_RT <<
1358 bool 882 bool
1359 883
1360 config CPU_NO_EFFICIENT_FFS 884 config CPU_NO_EFFICIENT_FFS
1361 def_bool n 885 def_bool n
1362 886
1363 config HAVE_ARCH_VMAP_STACK 887 config HAVE_ARCH_VMAP_STACK
1364 def_bool n 888 def_bool n
1365 help 889 help
1366 An arch should select this symbol i 890 An arch should select this symbol if it can support kernel stacks
1367 in vmalloc space. This means: 891 in vmalloc space. This means:
1368 892
1369 - vmalloc space must be large enoug 893 - vmalloc space must be large enough to hold many kernel stacks.
1370 This may rule out many 32-bit arc 894 This may rule out many 32-bit architectures.
1371 895
1372 - Stacks in vmalloc space need to w 896 - Stacks in vmalloc space need to work reliably. For example, if
1373 vmap page tables are created on d 897 vmap page tables are created on demand, either this mechanism
1374 needs to work while the stack poi 898 needs to work while the stack points to a virtual address with
1375 unpopulated page tables or arch c 899 unpopulated page tables or arch code (switch_to() and switch_mm(),
1376 most likely) needs to ensure that 900 most likely) needs to ensure that the stack's page table entries
1377 are populated before running on a 901 are populated before running on a possibly unpopulated stack.
1378 902
1379 - If the stack overflows into a gua 903 - If the stack overflows into a guard page, something reasonable
1380 should happen. The definition of 904 should happen. The definition of "reasonable" is flexible, but
1381 instantly rebooting without loggi 905 instantly rebooting without logging anything would be unfriendly.
1382 906
1383 config VMAP_STACK 907 config VMAP_STACK
1384 default y 908 default y
1385 bool "Use a virtually-mapped stack" 909 bool "Use a virtually-mapped stack"
1386 depends on HAVE_ARCH_VMAP_STACK !! 910 depends on HAVE_ARCH_VMAP_STACK && !KASAN
1387 depends on !KASAN || KASAN_HW_TAGS || !! 911 ---help---
1388 help <<
1389 Enable this if you want the use vir 912 Enable this if you want the use virtually-mapped kernel stacks
1390 with guard pages. This causes kern 913 with guard pages. This causes kernel stack overflows to be
1391 caught immediately rather than caus 914 caught immediately rather than causing difficult-to-diagnose
1392 corruption. 915 corruption.
1393 916
1394 To use this with software KASAN mod !! 917 This is presently incompatible with KASAN because KASAN expects
1395 backing virtual mappings with real !! 918 the stack to map directly to the KASAN shadow map using a formula
1396 must be enabled. !! 919 that is incorrect if the stack is in vmalloc space.
1397 <<
1398 config HAVE_ARCH_RANDOMIZE_KSTACK_OFFSET <<
1399 def_bool n <<
1400 help <<
1401 An arch should select this symbol i <<
1402 offset randomization with calls to <<
1403 during syscall entry and choose_ran <<
1404 syscall exit. Careful removal of -f <<
1405 -fstack-protector should also be ap <<
1406 closely examined, as the artificial <<
1407 to the compiler, so it will attempt <<
1408 of the static branch state. <<
1409 <<
1410 config RANDOMIZE_KSTACK_OFFSET <<
1411 bool "Support for randomizing kernel <<
1412 default y <<
1413 depends on HAVE_ARCH_RANDOMIZE_KSTACK <<
1414 depends on INIT_STACK_NONE || !CC_IS_ <<
1415 help <<
1416 The kernel stack offset can be rand <<
1417 roughly 5 bits of entropy, frustrat <<
1418 attacks that depend on stack addres <<
1419 cross-syscall address exposures. <<
1420 <<
1421 The feature is controlled via the " <<
1422 kernel boot param, and if turned of <<
1423 of static branches (see JUMP_LABEL) <<
1424 <<
1425 If unsure, say Y. <<
1426 <<
1427 config RANDOMIZE_KSTACK_OFFSET_DEFAULT <<
1428 bool "Default state of kernel stack o <<
1429 depends on RANDOMIZE_KSTACK_OFFSET <<
1430 help <<
1431 Kernel stack offset randomization i <<
1432 "randomize_kstack_offset=on/off", a <<
1433 boot state. <<
1434 920
1435 config ARCH_OPTIONAL_KERNEL_RWX 921 config ARCH_OPTIONAL_KERNEL_RWX
1436 def_bool n 922 def_bool n
1437 923
1438 config ARCH_OPTIONAL_KERNEL_RWX_DEFAULT 924 config ARCH_OPTIONAL_KERNEL_RWX_DEFAULT
1439 def_bool n 925 def_bool n
1440 926
1441 config ARCH_HAS_STRICT_KERNEL_RWX 927 config ARCH_HAS_STRICT_KERNEL_RWX
1442 def_bool n 928 def_bool n
1443 929
1444 config STRICT_KERNEL_RWX 930 config STRICT_KERNEL_RWX
1445 bool "Make kernel text and rodata rea 931 bool "Make kernel text and rodata read-only" if ARCH_OPTIONAL_KERNEL_RWX
1446 depends on ARCH_HAS_STRICT_KERNEL_RWX 932 depends on ARCH_HAS_STRICT_KERNEL_RWX
1447 default !ARCH_OPTIONAL_KERNEL_RWX || 933 default !ARCH_OPTIONAL_KERNEL_RWX || ARCH_OPTIONAL_KERNEL_RWX_DEFAULT
1448 help 934 help
1449 If this is set, kernel text and rod 935 If this is set, kernel text and rodata memory will be made read-only,
1450 and non-text memory will be made no 936 and non-text memory will be made non-executable. This provides
1451 protection against certain security 937 protection against certain security exploits (e.g. executing the heap
1452 or modifying text) 938 or modifying text)
1453 939
1454 These features are considered stand 940 These features are considered standard security practice these days.
1455 You should say Y here in almost all 941 You should say Y here in almost all cases.
1456 942
1457 config ARCH_HAS_STRICT_MODULE_RWX 943 config ARCH_HAS_STRICT_MODULE_RWX
1458 def_bool n 944 def_bool n
1459 945
1460 config STRICT_MODULE_RWX 946 config STRICT_MODULE_RWX
1461 bool "Set loadable kernel module data 947 bool "Set loadable kernel module data as NX and text as RO" if ARCH_OPTIONAL_KERNEL_RWX
1462 depends on ARCH_HAS_STRICT_MODULE_RWX 948 depends on ARCH_HAS_STRICT_MODULE_RWX && MODULES
1463 default !ARCH_OPTIONAL_KERNEL_RWX || 949 default !ARCH_OPTIONAL_KERNEL_RWX || ARCH_OPTIONAL_KERNEL_RWX_DEFAULT
1464 help 950 help
1465 If this is set, module text and rod 951 If this is set, module text and rodata memory will be made read-only,
1466 and non-text memory will be made no 952 and non-text memory will be made non-executable. This provides
1467 protection against certain security 953 protection against certain security exploits (e.g. writing to text)
1468 954
1469 # select if the architecture provides an asm/ 955 # select if the architecture provides an asm/dma-direct.h header
1470 config ARCH_HAS_PHYS_TO_DMA 956 config ARCH_HAS_PHYS_TO_DMA
1471 bool 957 bool
1472 958
>> 959 config ARCH_HAS_REFCOUNT
>> 960 bool
>> 961 help
>> 962 An architecture selects this when it has implemented refcount_t
>> 963 using open coded assembly primitives that provide an optimized
>> 964 refcount_t implementation, possibly at the expense of some full
>> 965 refcount state checks of CONFIG_REFCOUNT_FULL=y.
>> 966
>> 967 The refcount overflow check behavior, however, must be retained.
>> 968 Catching overflows is the primary security concern for protecting
>> 969 against bugs in reference counts.
>> 970
>> 971 config REFCOUNT_FULL
>> 972 bool "Perform full reference count validation at the expense of speed"
>> 973 help
>> 974 Enabling this switches the refcounting infrastructure from a fast
>> 975 unchecked atomic_t implementation to a fully state checked
>> 976 implementation, which can be (slightly) slower but provides protections
>> 977 against various use-after-free conditions that can be used in
>> 978 security flaw exploits.
>> 979
1473 config HAVE_ARCH_COMPILER_H 980 config HAVE_ARCH_COMPILER_H
1474 bool 981 bool
1475 help 982 help
1476 An architecture can select this if 983 An architecture can select this if it provides an
1477 asm/compiler.h header that should b 984 asm/compiler.h header that should be included after
1478 linux/compiler-*.h in order to over 985 linux/compiler-*.h in order to override macro definitions that those
1479 headers generally provide. 986 headers generally provide.
1480 987
1481 config HAVE_ARCH_PREL32_RELOCATIONS <<
1482 bool <<
1483 help <<
1484 May be selected by an architecture <<
1485 32-bit relocations, both in the too <<
1486 in which case relative references c <<
1487 for PCI fixup, initcalls etc which <<
1488 architectures, and don't require ru <<
1489 kernels. <<
1490 <<
1491 config ARCH_USE_MEMREMAP_PROT <<
1492 bool <<
1493 <<
1494 config LOCK_EVENT_COUNTS <<
1495 bool "Locking event counts collection <<
1496 depends on DEBUG_FS <<
1497 help <<
1498 Enable light-weight counting of var <<
1499 in the system with minimal performa <<
1500 the chance of application behavior <<
1501 differences. The counts are reporte <<
1502 <<
1503 # Select if the architecture has support for <<
1504 config ARCH_HAS_RELR <<
1505 bool <<
1506 <<
1507 config RELR <<
1508 bool "Use RELR relocation packing" <<
1509 depends on ARCH_HAS_RELR && TOOLS_SUP <<
1510 default y <<
1511 help <<
1512 Store the kernel's dynamic relocati <<
1513 format. Requires a compatible linke <<
1514 well as compatible NM and OBJCOPY u <<
1515 are compatible). <<
1516 <<
1517 config ARCH_HAS_MEM_ENCRYPT <<
1518 bool <<
1519 <<
1520 config ARCH_HAS_CC_PLATFORM <<
1521 bool <<
1522 <<
1523 config HAVE_SPARSE_SYSCALL_NR <<
1524 bool <<
1525 help <<
1526 An architecture should select this <<
1527 to save space. For example, MIPS ar <<
1528 entries at 4000, 5000 and 6000 loca <<
1529 related optimizations for a given a <<
1530 <<
1531 config ARCH_HAS_VDSO_DATA <<
1532 bool <<
1533 <<
1534 config HAVE_STATIC_CALL <<
1535 bool <<
1536 <<
1537 config HAVE_STATIC_CALL_INLINE <<
1538 bool <<
1539 depends on HAVE_STATIC_CALL <<
1540 select OBJTOOL <<
1541 <<
1542 config HAVE_PREEMPT_DYNAMIC <<
1543 bool <<
1544 <<
1545 config HAVE_PREEMPT_DYNAMIC_CALL <<
1546 bool <<
1547 depends on HAVE_STATIC_CALL <<
1548 select HAVE_PREEMPT_DYNAMIC <<
1549 help <<
1550 An architecture should select this <<
1551 model being selected at boot time u <<
1552 <<
1553 Where an architecture selects HAVE_ <<
1554 preemption function will be patched <<
1555 <<
1556 Where an architecture does not sele <<
1557 call to a preemption function will <<
1558 trampoline will be patched. <<
1559 <<
1560 It is strongly advised to support i <<
1561 overhead. <<
1562 <<
1563 config HAVE_PREEMPT_DYNAMIC_KEY <<
1564 bool <<
1565 depends on HAVE_ARCH_JUMP_LABEL <<
1566 select HAVE_PREEMPT_DYNAMIC <<
1567 help <<
1568 An architecture should select this <<
1569 model being selected at boot time u <<
1570 <<
1571 Each preemption function will be gi <<
1572 static key. This should have slight <<
1573 static calls, as this effectively i <<
1574 start of its callee. This may avoid <<
1575 integrate better with CFI schemes. <<
1576 <<
1577 This will have greater overhead tha <<
1578 the call to the preemption function <<
1579 <<
1580 config ARCH_WANT_LD_ORPHAN_WARN <<
1581 bool <<
1582 help <<
1583 An arch should select this symbol o <<
1584 included, size-asserted, or discard <<
1585 important because we never want exp <<
1586 by the linker, since the locations <<
1587 versions. <<
1588 <<
1589 config HAVE_ARCH_PFN_VALID <<
1590 bool <<
1591 <<
1592 config ARCH_SUPPORTS_DEBUG_PAGEALLOC <<
1593 bool <<
1594 <<
1595 config ARCH_SUPPORTS_PAGE_TABLE_CHECK <<
1596 bool <<
1597 <<
1598 config ARCH_SPLIT_ARG64 <<
1599 bool <<
1600 help <<
1601 If a 32-bit architecture requires 6 <<
1602 pairs of 32-bit arguments, select t <<
1603 <<
1604 config ARCH_HAS_ELFCORE_COMPAT <<
1605 bool <<
1606 <<
1607 config ARCH_HAS_PARANOID_L1D_FLUSH <<
1608 bool <<
1609 <<
1610 config ARCH_HAVE_TRACE_MMIO_ACCESS <<
1611 bool <<
1612 <<
1613 config DYNAMIC_SIGFRAME <<
1614 bool <<
1615 <<
1616 # Select, if arch has a named attribute group <<
1617 config HAVE_ARCH_NODE_DEV_GROUP <<
1618 bool <<
1619 <<
1620 config ARCH_HAS_HW_PTE_YOUNG <<
1621 bool <<
1622 help <<
1623 Architectures that select this opti <<
1624 accessed bit in PTE entries when us <<
1625 translations. Architectures that re <<
1626 this option and override arch_has_h <<
1627 <<
1628 config ARCH_HAS_NONLEAF_PMD_YOUNG <<
1629 bool <<
1630 help <<
1631 Architectures that select this opti <<
1632 accessed bit in non-leaf PMD entrie <<
1633 address translations. Page table wa <<
1634 may use this capability to reduce t <<
1635 <<
1636 config ARCH_HAS_KERNEL_FPU_SUPPORT <<
1637 bool <<
1638 help <<
1639 Architectures that select this opti <<
1640 the kernel, as described in Documen <<
1641 <<
1642 source "kernel/gcov/Kconfig" 988 source "kernel/gcov/Kconfig"
1643 <<
1644 source "scripts/gcc-plugins/Kconfig" <<
1645 <<
1646 config FUNCTION_ALIGNMENT_4B <<
1647 bool <<
1648 <<
1649 config FUNCTION_ALIGNMENT_8B <<
1650 bool <<
1651 <<
1652 config FUNCTION_ALIGNMENT_16B <<
1653 bool <<
1654 <<
1655 config FUNCTION_ALIGNMENT_32B <<
1656 bool <<
1657 <<
1658 config FUNCTION_ALIGNMENT_64B <<
1659 bool <<
1660 <<
1661 config FUNCTION_ALIGNMENT <<
1662 int <<
1663 default 64 if FUNCTION_ALIGNMENT_64B <<
1664 default 32 if FUNCTION_ALIGNMENT_32B <<
1665 default 16 if FUNCTION_ALIGNMENT_16B <<
1666 default 8 if FUNCTION_ALIGNMENT_8B <<
1667 default 4 if FUNCTION_ALIGNMENT_4B <<
1668 default 0 <<
1669 <<
1670 config CC_HAS_MIN_FUNCTION_ALIGNMENT <<
1671 # Detect availability of the GCC opti <<
1672 # guarantees minimal alignment for al <<
1673 # -falign-functions which the compile <<
1674 def_bool $(cc-option, -fmin-function- <<
1675 <<
1676 config CC_HAS_SANE_FUNCTION_ALIGNMENT <<
1677 # Set if the guaranteed alignment wit <<
1678 # available or extra care is required <<
1679 # strict alignment always, even with <<
1680 def_bool CC_HAS_MIN_FUNCTION_ALIGNMEN <<
1681 <<
1682 config ARCH_NEED_CMPXCHG_1_EMU <<
1683 bool <<
1684 <<
1685 endmenu <<
Linux® is a registered trademark of Linus Torvalds in the United States and other countries.
TOMOYO® is a registered trademark of NTT DATA CORPORATION.