1 # SPDX-License-Identifier: GPL-2.0
3 # General architecture dependent options
7 # Note: arch/$(SRCARCH)/Kconfig needs to be included first so that it can
8 # override the default values in this file.
10 source "arch/$(SRCARCH)/Kconfig"
12 menu "General architecture-dependent options"
34 tristate "OProfile system profiling"
36 depends on HAVE_OPROFILE
38 select RING_BUFFER_ALLOW_SWAP
40 OProfile is a profiling system capable of profiling the
41 whole system, include the kernel, kernel modules, libraries,
46 config OPROFILE_EVENT_MULTIPLEX
47 bool "OProfile multiplexing support (EXPERIMENTAL)"
49 depends on OPROFILE && X86
51 The number of hardware counters is limited. The multiplexing
52 feature enables OProfile to gather more events than counters
53 are provided by the hardware. This is realized by switching
54 between events at a user specified time interval.
61 config OPROFILE_NMI_TIMER
63 depends on PERF_EVENTS && HAVE_PERF_EVENTS_NMI && !PPC64
68 depends on HAVE_KPROBES
71 Kprobes allows you to trap at almost any kernel address and
72 execute a callback function. register_kprobe() establishes
73 a probepoint and specifies the callback. Kprobes is useful
74 for kernel debugging, non-intrusive instrumentation and testing.
78 bool "Optimize very unlikely/likely branches"
79 depends on HAVE_ARCH_JUMP_LABEL
80 depends on CC_HAS_ASM_GOTO
82 This option enables a transparent branch optimization that
83 makes certain almost-always-true or almost-always-false branch
84 conditions even cheaper to execute within the kernel.
86 Certain performance-sensitive kernel code, such as trace points,
87 scheduler functionality, networking code and KVM have such
88 branches and include support for this optimization technique.
90 If it is detected that the compiler has support for "asm goto",
91 the kernel will compile such branches with just a nop
92 instruction. When the condition flag is toggled to true, the
93 nop will be converted to a jump instruction to execute the
94 conditional block of instructions.
96 This technique lowers overhead and stress on the branch prediction
97 of the processor and generally makes the kernel faster. The update
98 of the condition is slower, but those are always very rare.
100 ( On 32-bit x86, the necessary options added to the compiler
101 flags may increase the size of the kernel slightly. )
103 config STATIC_KEYS_SELFTEST
104 bool "Static key selftest"
105 depends on JUMP_LABEL
107 Boot time self-test of the branch patching code.
109 config STATIC_CALL_SELFTEST
110 bool "Static call selftest"
111 depends on HAVE_STATIC_CALL
113 Boot time self-test of the call patching code.
117 depends on KPROBES && HAVE_OPTPROBES
118 select TASKS_RCU if PREEMPTION
120 config KPROBES_ON_FTRACE
122 depends on KPROBES && HAVE_KPROBES_ON_FTRACE
123 depends on DYNAMIC_FTRACE_WITH_REGS
125 If function tracer is enabled and the arch supports full
126 passing of pt_regs to function tracing, then kprobes can
127 optimize on top of function tracing.
131 depends on ARCH_SUPPORTS_UPROBES
133 Uprobes is the user-space counterpart to kprobes: they
134 enable instrumentation applications (such as 'perf probe')
135 to establish unintrusive probes in user-space binaries and
136 libraries, by executing handler functions when the probes
137 are hit by user-space applications.
139 ( These probes come in the form of single-byte breakpoints,
140 managed by the kernel and kept transparent to the probed
143 config HAVE_EFFICIENT_UNALIGNED_ACCESS
146 Some architectures are unable to perform unaligned accesses
147 without the use of get_unaligned/put_unaligned. Others are
148 unable to perform such accesses efficiently (e.g. trap on
149 unaligned access and require fixing it up in the exception
152 This symbol should be selected by an architecture if it can
153 perform unaligned accesses efficiently to allow different
154 code paths to be selected for these cases. Some network
155 drivers, for example, could opt to not fix up alignment
156 problems with received packets if doing so would not help
159 See Documentation/core-api/unaligned-memory-access.rst for more
160 information on the topic of unaligned memory accesses.
162 config ARCH_USE_BUILTIN_BSWAP
165 Modern versions of GCC (since 4.4) have builtin functions
166 for handling byte-swapping. Using these, instead of the old
167 inline assembler that the architecture code provides in the
168 __arch_bswapXX() macros, allows the compiler to see what's
169 happening and offers more opportunity for optimisation. In
170 particular, the compiler will be able to combine the byteswap
171 with a nearby load or store and use load-and-swap or
172 store-and-swap instructions if the architecture has them. It
173 should almost *never* result in code which is worse than the
174 hand-coded assembler in <asm/swab.h>. But just in case it
175 does, the use of the builtins is optional.
177 Any architecture with load-and-swap or store-and-swap
178 instructions should set this. And it shouldn't hurt to set it
179 on architectures that don't have such instructions.
183 depends on KPROBES && HAVE_KRETPROBES
185 config USER_RETURN_NOTIFIER
187 depends on HAVE_USER_RETURN_NOTIFIER
189 Provide a kernel-internal notification when a cpu is about to
192 config HAVE_IOREMAP_PROT
198 config HAVE_KRETPROBES
201 config HAVE_OPTPROBES
204 config HAVE_KPROBES_ON_FTRACE
207 config HAVE_FUNCTION_ERROR_INJECTION
214 # An arch should select this if it provides all these things:
216 # task_pt_regs() in asm/processor.h or asm/ptrace.h
217 # arch_has_single_step() if there is hardware single-step support
218 # arch_has_block_step() if there is hardware block-step support
219 # asm/syscall.h supplying asm-generic/syscall.h interface
220 # linux/regset.h user_regset interfaces
221 # CORE_DUMP_USE_REGSET #define'd in linux/elf.h
222 # TIF_SYSCALL_TRACE calls tracehook_report_syscall_{entry,exit}
223 # TIF_NOTIFY_RESUME calls tracehook_notify_resume()
224 # signal delivery calls tracehook_signal_handler()
226 config HAVE_ARCH_TRACEHOOK
229 config HAVE_DMA_CONTIGUOUS
232 config GENERIC_SMP_IDLE_THREAD
235 config GENERIC_IDLE_POLL_SETUP
238 config ARCH_HAS_FORTIFY_SOURCE
241 An architecture should select this when it can successfully
242 build and run with CONFIG_FORTIFY_SOURCE.
245 # Select if the arch provides a historic keepinit alias for the retain_initrd
246 # command line option
248 config ARCH_HAS_KEEPINITRD
251 # Select if arch has all set_memory_ro/rw/x/nx() functions in asm/cacheflush.h
252 config ARCH_HAS_SET_MEMORY
255 # Select if arch has all set_direct_map_invalid/default() functions
256 config ARCH_HAS_SET_DIRECT_MAP
260 # Select if the architecture provides the arch_dma_set_uncached symbol to
261 # either provide an uncached segement alias for a DMA allocation, or
262 # to remap the page tables in place.
264 config ARCH_HAS_DMA_SET_UNCACHED
268 # Select if the architectures provides the arch_dma_clear_uncached symbol
269 # to undo an in-place page table remap for uncached access.
271 config ARCH_HAS_DMA_CLEAR_UNCACHED
274 # Select if arch init_task must go in the __init_task_data section
275 config ARCH_TASK_STRUCT_ON_STACK
278 # Select if arch has its private alloc_task_struct() function
279 config ARCH_TASK_STRUCT_ALLOCATOR
282 config HAVE_ARCH_THREAD_STRUCT_WHITELIST
284 depends on !ARCH_TASK_STRUCT_ALLOCATOR
286 An architecture should select this to provide hardened usercopy
287 knowledge about what region of the thread_struct should be
288 whitelisted for copying to userspace. Normally this is only the
289 FPU registers. Specifically, arch_thread_struct_whitelist()
290 should be implemented. Without this, the entire thread_struct
291 field in task_struct will be left whitelisted.
293 # Select if arch has its private alloc_thread_stack() function
294 config ARCH_THREAD_STACK_ALLOCATOR
297 # Select if arch wants to size task_struct dynamically via arch_task_struct_size:
298 config ARCH_WANTS_DYNAMIC_TASK_STRUCT
301 config ARCH_32BIT_OFF_T
305 All new 32-bit architectures should have 64-bit off_t type on
306 userspace side which corresponds to the loff_t kernel type. This
307 is the requirement for modern ABIs. Some existing architectures
308 still support 32-bit off_t. This option is enabled for all such
309 architectures explicitly.
311 config HAVE_ASM_MODVERSIONS
314 This symbol should be selected by an architecure if it provides
315 <asm/asm-prototypes.h> to support the module versioning for symbols
316 exported from assembly code.
318 config HAVE_REGS_AND_STACK_ACCESS_API
321 This symbol should be selected by an architecure if it supports
322 the API needed to access registers and stack entries from pt_regs,
323 declared in asm/ptrace.h
324 For example the kprobes-based event tracer needs this API.
328 depends on HAVE_REGS_AND_STACK_ACCESS_API
330 This symbol should be selected by an architecture if it
331 supports an implementation of restartable sequences.
333 config HAVE_FUNCTION_ARG_ACCESS_API
336 This symbol should be selected by an architecure if it supports
337 the API needed to access function arguments from pt_regs,
338 declared in asm/ptrace.h
340 config HAVE_HW_BREAKPOINT
342 depends on PERF_EVENTS
344 config HAVE_MIXED_BREAKPOINTS_REGS
346 depends on HAVE_HW_BREAKPOINT
348 Depending on the arch implementation of hardware breakpoints,
349 some of them have separate registers for data and instruction
350 breakpoints addresses, others have mixed registers to store
351 them but define the access type in a control register.
352 Select this option if your arch implements breakpoints under the
355 config HAVE_USER_RETURN_NOTIFIER
358 config HAVE_PERF_EVENTS_NMI
361 System hardware can generate an NMI using the perf event
362 subsystem. Also has support for calculating CPU cycle events
363 to determine how many clock cycles in a given period.
365 config HAVE_HARDLOCKUP_DETECTOR_PERF
367 depends on HAVE_PERF_EVENTS_NMI
369 The arch chooses to use the generic perf-NMI-based hardlockup
370 detector. Must define HAVE_PERF_EVENTS_NMI.
372 config HAVE_NMI_WATCHDOG
376 The arch provides a low level NMI watchdog. It provides
377 asm/nmi.h, and defines its own arch_touch_nmi_watchdog().
379 config HAVE_HARDLOCKUP_DETECTOR_ARCH
381 select HAVE_NMI_WATCHDOG
383 The arch chooses to provide its own hardlockup detector, which is
384 a superset of the HAVE_NMI_WATCHDOG. It also conforms to config
385 interfaces and parameters provided by hardlockup detector subsystem.
387 config HAVE_PERF_REGS
390 Support selective register dumps for perf events. This includes
391 bit-mapping of each registers and a unique architecture id.
393 config HAVE_PERF_USER_STACK_DUMP
396 Support user stack dumps for perf event samples. This needs
397 access to the user stack pointer which is not unified across
400 config HAVE_ARCH_JUMP_LABEL
403 config HAVE_ARCH_JUMP_LABEL_RELATIVE
406 config MMU_GATHER_TABLE_FREE
409 config MMU_GATHER_RCU_TABLE_FREE
411 select MMU_GATHER_TABLE_FREE
413 config MMU_GATHER_PAGE_SIZE
416 config MMU_GATHER_NO_RANGE
419 config MMU_GATHER_NO_GATHER
421 depends on MMU_GATHER_TABLE_FREE
423 config ARCH_WANT_IRQS_OFF_ACTIVATE_MM
426 Temporary select until all architectures can be converted to have
427 irqs disabled over activate_mm. Architectures that do IPI based TLB
428 shootdowns should enable this.
430 config ARCH_HAVE_NMI_SAFE_CMPXCHG
433 config HAVE_ALIGNED_STRUCT_PAGE
436 This makes sure that struct pages are double word aligned and that
437 e.g. the SLUB allocator can perform double word atomic operations
438 on a struct page for better performance. However selecting this
439 might increase the size of a struct page by a word.
441 config HAVE_CMPXCHG_LOCAL
444 config HAVE_CMPXCHG_DOUBLE
447 config ARCH_WEAK_RELEASE_ACQUIRE
450 config ARCH_WANT_IPC_PARSE_VERSION
453 config ARCH_WANT_COMPAT_IPC_PARSE_VERSION
456 config ARCH_WANT_OLD_COMPAT_IPC
457 select ARCH_WANT_COMPAT_IPC_PARSE_VERSION
460 config HAVE_ARCH_SECCOMP
463 An arch should select this symbol to support seccomp mode 1 (the fixed
464 syscall policy), and must provide an overrides for __NR_seccomp_sigreturn,
465 and compat syscalls if the asm-generic/seccomp.h defaults need adjustment:
466 - __NR_seccomp_read_32
467 - __NR_seccomp_write_32
468 - __NR_seccomp_exit_32
469 - __NR_seccomp_sigreturn_32
471 config HAVE_ARCH_SECCOMP_FILTER
473 select HAVE_ARCH_SECCOMP
475 An arch should select this symbol if it provides all of these things:
476 - all the requirements for HAVE_ARCH_SECCOMP
478 - syscall_get_arguments()
480 - syscall_set_return_value()
481 - SIGSYS siginfo_t support
482 - secure_computing is called from a ptrace_event()-safe context
483 - secure_computing return value is checked and a return value of -1
484 results in the system call being skipped immediately.
485 - seccomp syscall wired up
488 prompt "Enable seccomp to safely execute untrusted bytecode"
490 depends on HAVE_ARCH_SECCOMP
492 This kernel feature is useful for number crunching applications
493 that may need to handle untrusted bytecode during their
494 execution. By using pipes or other transports made available
495 to the process as file descriptors supporting the read/write
496 syscalls, it's possible to isolate those applications in their
497 own address space using seccomp. Once seccomp is enabled via
498 prctl(PR_SET_SECCOMP) or the seccomp() syscall, it cannot be
499 disabled and the task is only allowed to execute a few safe
500 syscalls defined by each seccomp mode.
504 config SECCOMP_FILTER
506 depends on HAVE_ARCH_SECCOMP_FILTER && SECCOMP && NET
508 Enable tasks to build secure computing environments defined
509 in terms of Berkeley Packet Filter programs which implement
510 task-defined system call filtering polices.
512 See Documentation/userspace-api/seccomp_filter.rst for details.
514 config HAVE_ARCH_STACKLEAK
517 An architecture should select this if it has the code which
518 fills the used part of the kernel stack with the STACKLEAK_POISON
519 value before returning from system calls.
521 config HAVE_STACKPROTECTOR
524 An arch should select this symbol if:
525 - it has implemented a stack canary (e.g. __stack_chk_guard)
527 config STACKPROTECTOR
528 bool "Stack Protector buffer overflow detection"
529 depends on HAVE_STACKPROTECTOR
530 depends on $(cc-option,-fstack-protector)
533 This option turns on the "stack-protector" GCC feature. This
534 feature puts, at the beginning of functions, a canary value on
535 the stack just before the return address, and validates
536 the value just before actually returning. Stack based buffer
537 overflows (that need to overwrite this return address) now also
538 overwrite the canary, which gets detected and the attack is then
539 neutralized via a kernel panic.
541 Functions will have the stack-protector canary logic added if they
542 have an 8-byte or larger character array on the stack.
544 This feature requires gcc version 4.2 or above, or a distribution
545 gcc with the feature backported ("-fstack-protector").
547 On an x86 "defconfig" build, this feature adds canary checks to
548 about 3% of all kernel functions, which increases kernel code size
551 config STACKPROTECTOR_STRONG
552 bool "Strong Stack Protector"
553 depends on STACKPROTECTOR
554 depends on $(cc-option,-fstack-protector-strong)
557 Functions will have the stack-protector canary logic added in any
558 of the following conditions:
560 - local variable's address used as part of the right hand side of an
561 assignment or function argument
562 - local variable is an array (or union containing an array),
563 regardless of array type or length
564 - uses register local variables
566 This feature requires gcc version 4.9 or above, or a distribution
567 gcc with the feature backported ("-fstack-protector-strong").
569 On an x86 "defconfig" build, this feature adds canary checks to
570 about 20% of all kernel functions, which increases the kernel code
573 config ARCH_SUPPORTS_SHADOW_CALL_STACK
576 An architecture should select this if it supports Clang's Shadow
577 Call Stack and implements runtime support for shadow stack
580 config SHADOW_CALL_STACK
581 bool "Clang Shadow Call Stack"
582 depends on CC_IS_CLANG && ARCH_SUPPORTS_SHADOW_CALL_STACK
583 depends on DYNAMIC_FTRACE_WITH_REGS || !FUNCTION_GRAPH_TRACER
585 This option enables Clang's Shadow Call Stack, which uses a
586 shadow stack to protect function return addresses from being
587 overwritten by an attacker. More information can be found in
588 Clang's documentation:
590 https://clang.llvm.org/docs/ShadowCallStack.html
592 Note that security guarantees in the kernel differ from the
593 ones documented for user space. The kernel must store addresses
594 of shadow stacks in memory, which means an attacker capable of
595 reading and writing arbitrary memory may be able to locate them
596 and hijack control flow by modifying the stacks.
598 config HAVE_ARCH_WITHIN_STACK_FRAMES
601 An architecture should select this if it can walk the kernel stack
602 frames to determine if an object is part of either the arguments
603 or local variables (i.e. that it excludes saved return addresses,
604 and similar) by implementing an inline arch_within_stack_frames(),
605 which is used by CONFIG_HARDENED_USERCOPY.
607 config HAVE_CONTEXT_TRACKING
610 Provide kernel/user boundaries probes necessary for subsystems
611 that need it, such as userspace RCU extended quiescent state.
612 Syscalls need to be wrapped inside user_exit()-user_enter(), either
613 optimized behind static key or through the slow path using TIF_NOHZ
614 flag. Exceptions handlers must be wrapped as well. Irqs are already
615 protected inside rcu_irq_enter/rcu_irq_exit() but preemption or signal
616 handling on irq exit still need to be protected.
621 Arch relies on TIF_NOHZ and syscall slow path to implement context
622 tracking calls to user_enter()/user_exit().
624 config HAVE_VIRT_CPU_ACCOUNTING
627 config ARCH_HAS_SCALED_CPUTIME
630 config HAVE_VIRT_CPU_ACCOUNTING_GEN
634 With VIRT_CPU_ACCOUNTING_GEN, cputime_t becomes 64-bit.
635 Before enabling this option, arch code must be audited
636 to ensure there are no races in concurrent read/write of
637 cputime_t. For example, reading/writing 64-bit cputime_t on
638 some 32-bit arches may require multiple accesses, so proper
639 locking is needed to protect against concurrent accesses.
642 config HAVE_IRQ_TIME_ACCOUNTING
645 Archs need to ensure they use a high enough resolution clock to
646 support irq time accounting and then call enable_sched_clock_irqtime().
651 Archs that select this are able to move page tables at the PMD level.
653 config HAVE_ARCH_TRANSPARENT_HUGEPAGE
656 config HAVE_ARCH_TRANSPARENT_HUGEPAGE_PUD
659 config HAVE_ARCH_HUGE_VMAP
662 config ARCH_WANT_HUGE_PMD_SHARE
665 config HAVE_ARCH_SOFT_DIRTY
668 config HAVE_MOD_ARCH_SPECIFIC
671 The arch uses struct mod_arch_specific to store data. Many arches
672 just need a simple module loader without arch specific data - those
673 should not enable this.
675 config MODULES_USE_ELF_RELA
678 Modules only use ELF RELA relocations. Modules with ELF REL
679 relocations will give an error.
681 config MODULES_USE_ELF_REL
684 Modules only use ELF REL relocations. Modules with ELF RELA
685 relocations will give an error.
687 config HAVE_IRQ_EXIT_ON_IRQ_STACK
690 Architecture doesn't only execute the irq handler on the irq stack
691 but also irq_exit(). This way we can process softirqs on this irq
692 stack instead of switching to a new one when we call __do_softirq()
693 in the end of an hardirq.
694 This spares a stack switch and improves cache usage on softirq
697 config PGTABLE_LEVELS
701 config ARCH_HAS_ELF_RANDOMIZE
704 An architecture supports choosing randomized locations for
705 stack, mmap, brk, and ET_DYN. Defined functions:
707 - arch_randomize_brk()
709 config HAVE_ARCH_MMAP_RND_BITS
712 An arch should select this symbol if it supports setting a variable
713 number of bits for use in establishing the base address for mmap
714 allocations, has MMU enabled and provides values for both:
715 - ARCH_MMAP_RND_BITS_MIN
716 - ARCH_MMAP_RND_BITS_MAX
718 config HAVE_EXIT_THREAD
721 An architecture implements exit_thread.
723 config ARCH_MMAP_RND_BITS_MIN
726 config ARCH_MMAP_RND_BITS_MAX
729 config ARCH_MMAP_RND_BITS_DEFAULT
732 config ARCH_MMAP_RND_BITS
733 int "Number of bits to use for ASLR of mmap base address" if EXPERT
734 range ARCH_MMAP_RND_BITS_MIN ARCH_MMAP_RND_BITS_MAX
735 default ARCH_MMAP_RND_BITS_DEFAULT if ARCH_MMAP_RND_BITS_DEFAULT
736 default ARCH_MMAP_RND_BITS_MIN
737 depends on HAVE_ARCH_MMAP_RND_BITS
739 This value can be used to select the number of bits to use to
740 determine the random offset to the base address of vma regions
741 resulting from mmap allocations. This value will be bounded
742 by the architecture's minimum and maximum supported values.
744 This value can be changed after boot using the
745 /proc/sys/vm/mmap_rnd_bits tunable
747 config HAVE_ARCH_MMAP_RND_COMPAT_BITS
750 An arch should select this symbol if it supports running applications
751 in compatibility mode, supports setting a variable number of bits for
752 use in establishing the base address for mmap allocations, has MMU
753 enabled and provides values for both:
754 - ARCH_MMAP_RND_COMPAT_BITS_MIN
755 - ARCH_MMAP_RND_COMPAT_BITS_MAX
757 config ARCH_MMAP_RND_COMPAT_BITS_MIN
760 config ARCH_MMAP_RND_COMPAT_BITS_MAX
763 config ARCH_MMAP_RND_COMPAT_BITS_DEFAULT
766 config ARCH_MMAP_RND_COMPAT_BITS
767 int "Number of bits to use for ASLR of mmap base address for compatible applications" if EXPERT
768 range ARCH_MMAP_RND_COMPAT_BITS_MIN ARCH_MMAP_RND_COMPAT_BITS_MAX
769 default ARCH_MMAP_RND_COMPAT_BITS_DEFAULT if ARCH_MMAP_RND_COMPAT_BITS_DEFAULT
770 default ARCH_MMAP_RND_COMPAT_BITS_MIN
771 depends on HAVE_ARCH_MMAP_RND_COMPAT_BITS
773 This value can be used to select the number of bits to use to
774 determine the random offset to the base address of vma regions
775 resulting from mmap allocations for compatible applications This
776 value will be bounded by the architecture's minimum and maximum
779 This value can be changed after boot using the
780 /proc/sys/vm/mmap_rnd_compat_bits tunable
782 config HAVE_ARCH_COMPAT_MMAP_BASES
785 This allows 64bit applications to invoke 32-bit mmap() syscall
786 and vice-versa 32-bit applications to call 64-bit mmap().
787 Required for applications doing different bitness syscalls.
789 # This allows to use a set of generic functions to determine mmap base
790 # address by giving priority to top-down scheme only if the process
791 # is not in legacy mode (compat task, unlimited stack size or
792 # sysctl_legacy_va_layout).
793 # Architecture that selects this option can provide its own version of:
795 config ARCH_WANT_DEFAULT_TOPDOWN_MMAP_LAYOUT
798 select ARCH_HAS_ELF_RANDOMIZE
800 config HAVE_STACK_VALIDATION
803 Architecture supports the 'objtool check' host tool command, which
804 performs compile-time stack metadata validation.
806 config HAVE_RELIABLE_STACKTRACE
809 Architecture has either save_stack_trace_tsk_reliable() or
810 arch_stack_walk_reliable() function which only returns a stack trace
811 if it can guarantee the trace is reliable.
813 config HAVE_ARCH_HASH
817 If this is set, the architecture provides an <asm/hash.h>
818 file which provides platform-specific implementations of some
819 functions in <linux/hash.h> or fs/namei.c.
821 config HAVE_ARCH_NVRAM_OPS
830 config CLONE_BACKWARDS
833 Architecture has tls passed as the 4th argument of clone(2),
836 config CLONE_BACKWARDS2
839 Architecture has the first two arguments of clone(2) swapped.
841 config CLONE_BACKWARDS3
844 Architecture has tls passed as the 3rd argument of clone(2),
847 config ODD_RT_SIGACTION
850 Architecture has unusual rt_sigaction(2) arguments
852 config OLD_SIGSUSPEND
855 Architecture has old sigsuspend(2) syscall, of one-argument variety
857 config OLD_SIGSUSPEND3
860 Even weirder antique ABI - three-argument sigsuspend(2)
865 Architecture has old sigaction(2) syscall. Nope, not the same
866 as OLD_SIGSUSPEND | OLD_SIGSUSPEND3 - alpha has sigsuspend(2),
867 but fairly different variant of sigaction(2), thanks to OSF/1
870 config COMPAT_OLD_SIGACTION
873 config COMPAT_32BIT_TIME
874 bool "Provide system calls for 32-bit time_t"
875 default !64BIT || COMPAT
877 This enables 32 bit time_t support in addition to 64 bit time_t support.
878 This is relevant on all 32-bit architectures, and 64-bit architectures
879 as part of compat syscall handling.
881 config ARCH_NO_PREEMPT
884 config ARCH_SUPPORTS_RT
887 config CPU_NO_EFFICIENT_FFS
890 config HAVE_ARCH_VMAP_STACK
893 An arch should select this symbol if it can support kernel stacks
894 in vmalloc space. This means:
896 - vmalloc space must be large enough to hold many kernel stacks.
897 This may rule out many 32-bit architectures.
899 - Stacks in vmalloc space need to work reliably. For example, if
900 vmap page tables are created on demand, either this mechanism
901 needs to work while the stack points to a virtual address with
902 unpopulated page tables or arch code (switch_to() and switch_mm(),
903 most likely) needs to ensure that the stack's page table entries
904 are populated before running on a possibly unpopulated stack.
906 - If the stack overflows into a guard page, something reasonable
907 should happen. The definition of "reasonable" is flexible, but
908 instantly rebooting without logging anything would be unfriendly.
912 bool "Use a virtually-mapped stack"
913 depends on HAVE_ARCH_VMAP_STACK
914 depends on !KASAN || KASAN_VMALLOC
916 Enable this if you want the use virtually-mapped kernel stacks
917 with guard pages. This causes kernel stack overflows to be
918 caught immediately rather than causing difficult-to-diagnose
921 To use this with KASAN, the architecture must support backing
922 virtual mappings with real shadow memory, and KASAN_VMALLOC must
925 config ARCH_OPTIONAL_KERNEL_RWX
928 config ARCH_OPTIONAL_KERNEL_RWX_DEFAULT
931 config ARCH_HAS_STRICT_KERNEL_RWX
934 config STRICT_KERNEL_RWX
935 bool "Make kernel text and rodata read-only" if ARCH_OPTIONAL_KERNEL_RWX
936 depends on ARCH_HAS_STRICT_KERNEL_RWX
937 default !ARCH_OPTIONAL_KERNEL_RWX || ARCH_OPTIONAL_KERNEL_RWX_DEFAULT
939 If this is set, kernel text and rodata memory will be made read-only,
940 and non-text memory will be made non-executable. This provides
941 protection against certain security exploits (e.g. executing the heap
944 These features are considered standard security practice these days.
945 You should say Y here in almost all cases.
947 config ARCH_HAS_STRICT_MODULE_RWX
950 config STRICT_MODULE_RWX
951 bool "Set loadable kernel module data as NX and text as RO" if ARCH_OPTIONAL_KERNEL_RWX
952 depends on ARCH_HAS_STRICT_MODULE_RWX && MODULES
953 default !ARCH_OPTIONAL_KERNEL_RWX || ARCH_OPTIONAL_KERNEL_RWX_DEFAULT
955 If this is set, module text and rodata memory will be made read-only,
956 and non-text memory will be made non-executable. This provides
957 protection against certain security exploits (e.g. writing to text)
959 # select if the architecture provides an asm/dma-direct.h header
960 config ARCH_HAS_PHYS_TO_DMA
963 config HAVE_ARCH_COMPILER_H
966 An architecture can select this if it provides an
967 asm/compiler.h header that should be included after
968 linux/compiler-*.h in order to override macro definitions that those
969 headers generally provide.
971 config HAVE_ARCH_PREL32_RELOCATIONS
974 May be selected by an architecture if it supports place-relative
975 32-bit relocations, both in the toolchain and in the module loader,
976 in which case relative references can be used in special sections
977 for PCI fixup, initcalls etc which are only half the size on 64 bit
978 architectures, and don't require runtime relocation on relocatable
981 config ARCH_USE_MEMREMAP_PROT
984 config LOCK_EVENT_COUNTS
985 bool "Locking event counts collection"
988 Enable light-weight counting of various locking related events
989 in the system with minimal performance impact. This reduces
990 the chance of application behavior change because of timing
991 differences. The counts are reported via debugfs.
993 # Select if the architecture has support for applying RELR relocations.
998 bool "Use RELR relocation packing"
999 depends on ARCH_HAS_RELR && TOOLS_SUPPORT_RELR
1002 Store the kernel's dynamic relocations in the RELR relocation packing
1003 format. Requires a compatible linker (LLD supports this feature), as
1004 well as compatible NM and OBJCOPY utilities (llvm-nm and llvm-objcopy
1007 config ARCH_HAS_MEM_ENCRYPT
1010 config HAVE_SPARSE_SYSCALL_NR
1013 An architecture should select this if its syscall numbering is sparse
1014 to save space. For example, MIPS architecture has a syscall array with
1015 entries at 4000, 5000 and 6000 locations. This option turns on syscall
1016 related optimizations for a given architecture.
1018 config ARCH_HAS_VDSO_DATA
1021 config HAVE_STATIC_CALL
1024 config HAVE_STATIC_CALL_INLINE
1026 depends on HAVE_STATIC_CALL
1028 source "kernel/gcov/Kconfig"
1030 source "scripts/gcc-plugins/Kconfig"