# SPDX-License-Identifier: GPL-2.0## General architecture dependent options# ## Note: arch/$(SRCARCH)/Kconfig needs to be included first so that it can# override the default values in this file.#source "arch/$(SRCARCH)/Kconfig" config ARCH_CONFIGURES_CPU_MITIGATIONS bool if !ARCH_CONFIGURES_CPU_MITIGATIONSconfig CPU_MITIGATIONS def_bool yendif ## Selected by architectures that need custom DMA operations for e.g. legacy# IOMMUs not handled by dma-iommu. Drivers must never select this symbol.#config ARCH_HAS_DMA_OPS depends on HAS_DMA select DMA_OPS_HELPERS bool menu "General architecture-dependent options" config ARCH_HAS_SUBPAGE_FAULTS bool help Select if the architecture can check permissions at sub-page granularity (e.g. arm64 MTE). The probe_user_*() functions must be implemented. config HOTPLUG_SMT bool config SMT_NUM_THREADS_DYNAMIC bool config ARCH_SUPPORTS_SCHED_SMT bool config ARCH_SUPPORTS_SCHED_CLUSTER bool config ARCH_SUPPORTS_SCHED_MC bool config SCHED_SMT bool "SMT (Hyperthreading) scheduler support" depends on ARCH_SUPPORTS_SCHED_SMT default y help Improves the CPU scheduler's decision making when dealing with MultiThreading at a cost of slightly increased overhead in some places. If unsure say N here. config SCHED_CLUSTER bool "Cluster scheduler support" depends on ARCH_SUPPORTS_SCHED_CLUSTER default y help Cluster scheduler support improves the CPU scheduler's decision making when dealing with machines that have clusters of CPUs. Cluster usually means a couple of CPUs which are placed closely by sharing mid-level caches, last-level cache tags or internal busses. config SCHED_MC bool "Multi-Core Cache (MC) scheduler support" depends on ARCH_SUPPORTS_SCHED_MC default y help Multi-core scheduler support improves the CPU scheduler's decision making when dealing with multi-core CPU chips at a cost of slightly increased overhead in some places. If unsure say N here. # Selected by HOTPLUG_CORE_SYNC_DEAD or HOTPLUG_CORE_SYNC_FULLconfig HOTPLUG_CORE_SYNC bool # Basic CPU dead synchronization selected by architectureconfig HOTPLUG_CORE_SYNC_DEAD bool select HOTPLUG_CORE_SYNC # Full CPU synchronization with alive state selected by architectureconfig HOTPLUG_CORE_SYNC_FULL bool select HOTPLUG_CORE_SYNC_DEAD if HOTPLUG_CPU select HOTPLUG_CORE_SYNC config HOTPLUG_SPLIT_STARTUP bool select HOTPLUG_CORE_SYNC_FULL config HOTPLUG_PARALLEL bool select HOTPLUG_SPLIT_STARTUP config GENERIC_IRQ_ENTRY bool config GENERIC_SYSCALL bool depends on GENERIC_IRQ_ENTRY config GENERIC_ENTRY bool select GENERIC_IRQ_ENTRY select GENERIC_SYSCALL config ARCH_SUPPORTS_SYSCALL_USER_DISPATCH bool config SYSCALL_USER_DISPATCH bool "Syscall User Dispatch" depends on ARCH_SUPPORTS_SYSCALL_USER_DISPATCH depends on GENERIC_ENTRY default y help Syscall User Dispatch lets a thread have its own system calls intercepted and redirected to a userspace signal handler based on a prctl() configured instruction pointer range. If unsure, say Y. config KPROBES bool "Kprobes" depends on HAVE_KPROBES select KALLSYMS select EXECMEM select NEED_TASKS_RCU help Kprobes allows you to trap at almost any kernel address and execute a callback function. register_kprobe() establishes a probepoint and specifies the callback. Kprobes is useful for kernel debugging, non-intrusive instrumentation and testing. If in doubt, say "N". config JUMP_LABEL bool "Optimize very unlikely/likely branches" depends on HAVE_ARCH_JUMP_LABEL select OBJTOOL if HAVE_JUMP_LABEL_HACK help This option enables a transparent branch optimization that makes certain almost-always-true or almost-always-false branch conditions even cheaper to execute within the kernel. Certain performance-sensitive kernel code, such as trace points, scheduler functionality, networking code and KVM have such branches and include support for this optimization technique. If it is detected that the compiler has support for "asm goto", the kernel will compile such branches with just a nop instruction. When the condition flag is toggled to true, the nop will be converted to a jump instruction to execute the conditional block of instructions. This technique lowers overhead and stress on the branch prediction of the processor and generally makes the kernel faster. The update of the condition is slower, but those are always very rare. ( On 32-bit x86, the necessary options added to the compiler flags may increase the size of the kernel slightly. ) config STATIC_KEYS_SELFTEST bool "Static key selftest" depends on JUMP_LABEL help Boot time self-test of the branch patching code. config STATIC_CALL_SELFTEST bool "Static call selftest" depends on HAVE_STATIC_CALL help Boot time self-test of the call patching code. config OPTPROBES def_bool y depends on KPROBES && HAVE_OPTPROBES select NEED_TASKS_RCU config KPROBES_ON_FTRACE def_bool y depends on KPROBES && HAVE_KPROBES_ON_FTRACE depends on DYNAMIC_FTRACE_WITH_REGS help If function tracer is enabled and the arch supports full passing of pt_regs to function tracing, then kprobes can optimize on top of function tracing. config UPROBES def_bool n depends on ARCH_SUPPORTS_UPROBES select TASKS_TRACE_RCU help Uprobes is the user-space counterpart to kprobes: they enable instrumentation applications (such as 'perf probe') to establish unintrusive probes in user-space binaries and libraries, by executing handler functions when the probes are hit by user-space applications. ( These probes come in the form of single-byte breakpoints, managed by the kernel and kept transparent to the probed application. ) config HAVE_64BIT_ALIGNED_ACCESS def_bool 64BIT && !HAVE_EFFICIENT_UNALIGNED_ACCESS help Some architectures require 64 bit accesses to be 64 bit aligned, which also requires structs containing 64 bit values to be 64 bit aligned too. This includes some 32 bit architectures which can do 64 bit accesses, as well as 64 bit architectures without unaligned access. This symbol should be selected by an architecture if 64 bit accesses are required to be 64 bit aligned in this way even though it is not a 64 bit architecture. See Documentation/core-api/unaligned-memory-access.rst for more information on the topic of unaligned memory accesses. config HAVE_EFFICIENT_UNALIGNED_ACCESS bool help Some architectures are unable to perform unaligned accesses without the use of get_unaligned/put_unaligned. Others are unable to perform such accesses efficiently (e.g. trap on unaligned access and require fixing it up in the exception handler.) This symbol should be selected by an architecture if it can perform unaligned accesses efficiently to allow different code paths to be selected for these cases. Some network drivers, for example, could opt to not fix up alignment problems with received packets if doing so would not help much. See Documentation/core-api/unaligned-memory-access.rst for more information on the topic of unaligned memory accesses. config ARCH_USE_BUILTIN_BSWAP bool help GCC and Clang have builtin functions for handling byte-swapping. Using these allows the compiler to see what's happening and offers more opportunity for optimisation. In particular, the compiler will be able to combine the byteswap with a nearby load or store and use load-and-swap or store-and-swap instructions if the architecture has them. It should almost *never* result in code which is worse than the hand-coded assembler in <asm/swab.h>. But just in case it does, the use of the builtins is optional. Any architecture with load-and-swap or store-and-swap instructions should set this. And it shouldn't hurt to set it on architectures that don't have such instructions. config KRETPROBES def_bool y depends on KPROBES && (HAVE_KRETPROBES || HAVE_RETHOOK) config KRETPROBE_ON_RETHOOK def_bool y depends on HAVE_RETHOOK depends on KRETPROBES select RETHOOK config USER_RETURN_NOTIFIER bool depends on HAVE_USER_RETURN_NOTIFIER help Provide a kernel-internal notification when a cpu is about to switch to user mode. config HAVE_IOREMAP_PROT bool config HAVE_KPROBES bool config HAVE_KRETPROBES bool config HAVE_OPTPROBES bool config HAVE_KPROBES_ON_FTRACE bool config ARCH_CORRECT_STACKTRACE_ON_KRETPROBE bool help Since kretprobes modifies return address on the stack, the stacktrace may see the kretprobe trampoline address instead of correct one. If the architecture stacktrace code and unwinder can adjust such entries, select this configuration. config HAVE_FUNCTION_ERROR_INJECTION bool config HAVE_NMI bool config HAVE_FUNCTION_DESCRIPTORS bool config TRACE_IRQFLAGS_SUPPORT bool config TRACE_IRQFLAGS_NMI_SUPPORT bool ## An arch should select this if it provides all these things:## task_pt_regs() in asm/processor.h or asm/ptrace.h# arch_has_single_step() if there is hardware single-step support# arch_has_block_step() if there is hardware block-step support# asm/syscall.h supplying asm-generic/syscall.h interface# linux/regset.h user_regset interfaces# CORE_DUMP_USE_REGSET #define'd in linux/elf.h# TIF_SYSCALL_TRACE calls ptrace_report_syscall_{entry,exit}# TIF_NOTIFY_RESUME calls resume_user_mode_work()#config HAVE_ARCH_TRACEHOOK bool config HAVE_DMA_CONTIGUOUS bool config GENERIC_SMP_IDLE_THREAD bool config GENERIC_IDLE_POLL_SETUP bool config ARCH_HAS_FORTIFY_SOURCE bool help An architecture should select this when it can successfully build and run with CONFIG_FORTIFY_SOURCE. ## Select if the arch provides a historic keepinit alias for the retain_initrd# command line option#config ARCH_HAS_KEEPINITRD bool # Select if arch has all set_memory_ro/rw/x/nx() functions in asm/cacheflush.hconfig ARCH_HAS_SET_MEMORY bool # Select if arch has all set_direct_map_invalid/default() functionsconfig ARCH_HAS_SET_DIRECT_MAP bool ## Select if the architecture provides the arch_dma_set_uncached symbol to# either provide an uncached segment alias for a DMA allocation, or# to remap the page tables in place.#config ARCH_HAS_DMA_SET_UNCACHED bool ## Select if the architectures provides the arch_dma_clear_uncached symbol# to undo an in-place page table remap for uncached access.#config ARCH_HAS_DMA_CLEAR_UNCACHED bool config ARCH_HAS_CPU_FINALIZE_INIT bool config ARCH_HAS_DELAY_TIMER bool # The architecture has a per-task state that includes the mm's PASIDconfig ARCH_HAS_CPU_PASID bool select IOMMU_MM_DATA config HAVE_ARCH_THREAD_STRUCT_WHITELIST bool help An architecture should select this to provide hardened usercopy knowledge about what region of the thread_struct should be whitelisted for copying to userspace. Normally this is only the FPU registers. Specifically, arch_thread_struct_whitelist() should be implemented. Without this, the entire thread_struct field in task_struct will be left whitelisted. # Select if arch wants to size task_struct dynamically via arch_task_struct_size:config ARCH_WANTS_DYNAMIC_TASK_STRUCT bool config ARCH_WANTS_NO_INSTR bool help An architecture should select this if the noinstr macro is being used on functions to denote that the toolchain should avoid instrumenting such functions and is required for correctness. config ARCH_32BIT_OFF_T bool depends on !64BIT help All new 32-bit architectures should have 64-bit off_t type on userspace side which corresponds to the loff_t kernel type. This is the requirement for modern ABIs. Some existing architectures still support 32-bit off_t. This option is enabled for all such architectures explicitly. # Selected by 64 bit architectures which have a 32 bit f_tinode in struct ustatconfig ARCH_32BIT_USTAT_F_TINODE bool # Selected by architectures with Total Store Order (TSO)config ARCH_MEMORY_ORDER_TSO bool config HAVE_ASM_MODVERSIONS bool help This symbol should be selected by an architecture if it provides <asm/asm-prototypes.h> to support the module versioning for symbols exported from assembly code. config HAVE_REGS_AND_STACK_ACCESS_API bool help This symbol should be selected by an architecture if it supports the API needed to access registers and stack entries from pt_regs, declared in asm/ptrace.h For example the kprobes-based event tracer needs this API. config HAVE_RSEQ bool depends on HAVE_REGS_AND_STACK_ACCESS_API help This symbol should be selected by an architecture if it supports an implementation of restartable sequences. config HAVE_RUST bool help This symbol should be selected by an architecture if it supports Rust. config HAVE_FUNCTION_ARG_ACCESS_API bool help This symbol should be selected by an architecture if it supports the API needed to access function arguments from pt_regs, declared in asm/ptrace.h config HAVE_HW_BREAKPOINT bool depends on PERF_EVENTS config HAVE_MIXED_BREAKPOINTS_REGS bool depends on HAVE_HW_BREAKPOINT help Depending on the arch implementation of hardware breakpoints, some of them have separate registers for data and instruction breakpoints addresses, others have mixed registers to store them but define the access type in a control register. Select this option if your arch implements breakpoints under the latter fashion. config HAVE_USER_RETURN_NOTIFIER bool config HAVE_PERF_EVENTS_NMI bool help System hardware can generate an NMI using the perf event subsystem. Also has support for calculating CPU cycle events to determine how many clock cycles in a given period. config HAVE_HARDLOCKUP_DETECTOR_PERF bool depends on HAVE_PERF_EVENTS_NMI help The arch chooses to use the generic perf-NMI-based hardlockup detector. Must define HAVE_PERF_EVENTS_NMI. config HAVE_HARDLOCKUP_DETECTOR_ARCH bool help The arch provides its own hardlockup detector implementation instead of the generic ones. It uses the same command line parameters, and sysctl interface,Lines 1–500 of 1881. Load more
# SPDX-License-Identifier: GPL-2.0 # # General architecture dependent options # # # Note: arch/$(SRCARCH)/Kconfig needs to be included first so that it can # override the default values in this file. # source "arch/$(SRCARCH)/Kconfig" config ARCH_CONFIGURES_CPU_MITIGATIONS bool if !ARCH_CONFIGURES_CPU_MITIGATIONS config CPU_MITIGATIONS def_bool y endif # # Selected by architectures that need custom DMA operations for e.g. legacy # IOMMUs not handled by dma-iommu. Drivers must never select this symbol. # config ARCH_HAS_DMA_OPS depends on HAS_DMA select DMA_OPS_HELPERS bool menu "General architecture-dependent options" config ARCH_HAS_SUBPAGE_FAULTS bool help Select if the architecture can check permissions at sub-page granularity (e.g. arm64 MTE). The probe_user_*() functions must be implemented. config HOTPLUG_SMT bool config SMT_NUM_THREADS_DYNAMIC bool config ARCH_SUPPORTS_SCHED_SMT bool config ARCH_SUPPORTS_SCHED_CLUSTER bool config ARCH_SUPPORTS_SCHED_MC bool config SCHED_SMT bool "SMT (Hyperthreading) scheduler support" depends on ARCH_SUPPORTS_SCHED_SMT default y help Improves the CPU scheduler's decision making when dealing with MultiThreading at a cost of slightly increased overhead in some places. If unsure say N here. config SCHED_CLUSTER bool "Cluster scheduler support" depends on ARCH_SUPPORTS_SCHED_CLUSTER default y help Cluster scheduler support improves the CPU scheduler's decision making when dealing with machines that have clusters of CPUs. Cluster usually means a couple of CPUs which are placed closely by sharing mid-level caches, last-level cache tags or internal busses. config SCHED_MC bool "Multi-Core Cache (MC) scheduler support" depends on ARCH_SUPPORTS_SCHED_MC default y help Multi-core scheduler support improves the CPU scheduler's decision making when dealing with multi-core CPU chips at a cost of slightly increased overhead in some places. If unsure say N here. # Selected by HOTPLUG_CORE_SYNC_DEAD or HOTPLUG_CORE_SYNC_FULL config HOTPLUG_CORE_SYNC bool # Basic CPU dead synchronization selected by architecture config HOTPLUG_CORE_SYNC_DEAD bool select HOTPLUG_CORE_SYNC # Full CPU synchronization with alive state selected by architecture config HOTPLUG_CORE_SYNC_FULL bool select HOTPLUG_CORE_SYNC_DEAD if HOTPLUG_CPU select HOTPLUG_CORE_SYNC config HOTPLUG_SPLIT_STARTUP bool select HOTPLUG_CORE_SYNC_FULL config HOTPLUG_PARALLEL bool select HOTPLUG_SPLIT_STARTUP config GENERIC_IRQ_ENTRY bool config GENERIC_SYSCALL bool depends on GENERIC_IRQ_ENTRY config GENERIC_ENTRY bool select GENERIC_IRQ_ENTRY select GENERIC_SYSCALL config ARCH_SUPPORTS_SYSCALL_USER_DISPATCH bool config SYSCALL_USER_DISPATCH bool "Syscall User Dispatch" depends on ARCH_SUPPORTS_SYSCALL_USER_DISPATCH depends on GENERIC_ENTRY default y help Syscall User Dispatch lets a thread have its own system calls intercepted and redirected to a userspace signal handler based on a prctl() configured instruction pointer range. If unsure, say Y. config KPROBES bool "Kprobes" depends on HAVE_KPROBES select KALLSYMS select EXECMEM select NEED_TASKS_RCU help Kprobes allows you to trap at almost any kernel address and execute a callback function. register_kprobe() establishes a probepoint and specifies the callback. Kprobes is useful for kernel debugging, non-intrusive instrumentation and testing. If in doubt, say "N". config JUMP_LABEL bool "Optimize very unlikely/likely branches" depends on HAVE_ARCH_JUMP_LABEL select OBJTOOL if HAVE_JUMP_LABEL_HACK help This option enables a transparent branch optimization that makes certain almost-always-true or almost-always-false branch conditions even cheaper to execute within the kernel. Certain performance-sensitive kernel code, such as trace points, scheduler functionality, networking code and KVM have such branches and include support for this optimization technique. If it is detected that the compiler has support for "asm goto", the kernel will compile such branches with just a nop instruction. When the condition flag is toggled to true, the nop will be converted to a jump instruction to execute the conditional block of instructions. This technique lowers overhead and stress on the branch prediction of the processor and generally makes the kernel faster. The update of the condition is slower, but those are always very rare. ( On 32-bit x86, the necessary options added to the compiler flags may increase the size of the kernel slightly. ) config STATIC_KEYS_SELFTEST bool "Static key selftest" depends on JUMP_LABEL help Boot time self-test of the branch patching code. config STATIC_CALL_SELFTEST bool "Static call selftest" depends on HAVE_STATIC_CALL help Boot time self-test of the call patching code. config OPTPROBES def_bool y depends on KPROBES && HAVE_OPTPROBES select NEED_TASKS_RCU config KPROBES_ON_FTRACE def_bool y depends on KPROBES && HAVE_KPROBES_ON_FTRACE depends on DYNAMIC_FTRACE_WITH_REGS help If function tracer is enabled and the arch supports full passing of pt_regs to function tracing, then kprobes can optimize on top of function tracing. config UPROBES def_bool n depends on ARCH_SUPPORTS_UPROBES select TASKS_TRACE_RCU help Uprobes is the user-space counterpart to kprobes: they enable instrumentation applications (such as 'perf probe') to establish unintrusive probes in user-space binaries and libraries, by executing handler functions when the probes are hit by user-space applications. ( These probes come in the form of single-byte breakpoints, managed by the kernel and kept transparent to the probed application. ) config HAVE_64BIT_ALIGNED_ACCESS def_bool 64BIT && !HAVE_EFFICIENT_UNALIGNED_ACCESS help Some architectures require 64 bit accesses to be 64 bit aligned, which also requires structs containing 64 bit values to be 64 bit aligned too. This includes some 32 bit architectures which can do 64 bit accesses, as well as 64 bit architectures without unaligned access. This symbol should be selected by an architecture if 64 bit accesses are required to be 64 bit aligned in this way even though it is not a 64 bit architecture. See Documentation/core-api/unaligned-memory-access.rst for more information on the topic of unaligned memory accesses. config HAVE_EFFICIENT_UNALIGNED_ACCESS bool help Some architectures are unable to perform unaligned accesses without the use of get_unaligned/put_unaligned. Others are unable to perform such accesses efficiently (e.g. trap on unaligned access and require fixing it up in the exception handler.) This symbol should be selected by an architecture if it can perform unaligned accesses efficiently to allow different code paths to be selected for these cases. Some network drivers, for example, could opt to not fix up alignment problems with received packets if doing so would not help much. See Documentation/core-api/unaligned-memory-access.rst for more information on the topic of unaligned memory accesses. config ARCH_USE_BUILTIN_BSWAP bool help GCC and Clang have builtin functions for handling byte-swapping. Using these allows the compiler to see what's happening and offers more opportunity for optimisation. In particular, the compiler will be able to combine the byteswap with a nearby load or store and use load-and-swap or store-and-swap instructions if the architecture has them. It should almost *never* result in code which is worse than the hand-coded assembler in <asm/swab.h>. But just in case it does, the use of the builtins is optional. Any architecture with load-and-swap or store-and-swap instructions should set this. And it shouldn't hurt to set it on architectures that don't have such instructions. config KRETPROBES def_bool y depends on KPROBES && (HAVE_KRETPROBES || HAVE_RETHOOK) config KRETPROBE_ON_RETHOOK def_bool y depends on HAVE_RETHOOK depends on KRETPROBES select RETHOOK config USER_RETURN_NOTIFIER bool depends on HAVE_USER_RETURN_NOTIFIER help Provide a kernel-internal notification when a cpu is about to switch to user mode. config HAVE_IOREMAP_PROT bool config HAVE_KPROBES bool config HAVE_KRETPROBES bool config HAVE_OPTPROBES bool config HAVE_KPROBES_ON_FTRACE bool config ARCH_CORRECT_STACKTRACE_ON_KRETPROBE bool help Since kretprobes modifies return address on the stack, the stacktrace may see the kretprobe trampoline address instead of correct one. If the architecture stacktrace code and unwinder can adjust such entries, select this configuration. config HAVE_FUNCTION_ERROR_INJECTION bool config HAVE_NMI bool config HAVE_FUNCTION_DESCRIPTORS bool config TRACE_IRQFLAGS_SUPPORT bool config TRACE_IRQFLAGS_NMI_SUPPORT bool # # An arch should select this if it provides all these things: # # task_pt_regs() in asm/processor.h or asm/ptrace.h # arch_has_single_step() if there is hardware single-step support # arch_has_block_step() if there is hardware block-step support # asm/syscall.h supplying asm-generic/syscall.h interface # linux/regset.h user_regset interfaces # CORE_DUMP_USE_REGSET #define'd in linux/elf.h # TIF_SYSCALL_TRACE calls ptrace_report_syscall_{entry,exit} # TIF_NOTIFY_RESUME calls resume_user_mode_work() # config HAVE_ARCH_TRACEHOOK bool config HAVE_DMA_CONTIGUOUS bool config GENERIC_SMP_IDLE_THREAD bool config GENERIC_IDLE_POLL_SETUP bool config ARCH_HAS_FORTIFY_SOURCE bool help An architecture should select this when it can successfully build and run with CONFIG_FORTIFY_SOURCE. # # Select if the arch provides a historic keepinit alias for the retain_initrd # command line option # config ARCH_HAS_KEEPINITRD bool # Select if arch has all set_memory_ro/rw/x/nx() functions in asm/cacheflush.h config ARCH_HAS_SET_MEMORY bool # Select if arch has all set_direct_map_invalid/default() functions config ARCH_HAS_SET_DIRECT_MAP bool # # Select if the architecture provides the arch_dma_set_uncached symbol to # either provide an uncached segment alias for a DMA allocation, or # to remap the page tables in place. # config ARCH_HAS_DMA_SET_UNCACHED bool # # Select if the architectures provides the arch_dma_clear_uncached symbol # to undo an in-place page table remap for uncached access. # config ARCH_HAS_DMA_CLEAR_UNCACHED bool config ARCH_HAS_CPU_FINALIZE_INIT bool config ARCH_HAS_DELAY_TIMER bool # The architecture has a per-task state that includes the mm's PASID config ARCH_HAS_CPU_PASID bool select IOMMU_MM_DATA config HAVE_ARCH_THREAD_STRUCT_WHITELIST bool help An architecture should select this to provide hardened usercopy knowledge about what region of the thread_struct should be whitelisted for copying to userspace. Normally this is only the FPU registers. Specifically, arch_thread_struct_whitelist() should be implemented. Without this, the entire thread_struct field in task_struct will be left whitelisted. # Select if arch wants to size task_struct dynamically via arch_task_struct_size: config ARCH_WANTS_DYNAMIC_TASK_STRUCT bool config ARCH_WANTS_NO_INSTR bool help An architecture should select this if the noinstr macro is being used on functions to denote that the toolchain should avoid instrumenting such functions and is required for correctness. config ARCH_32BIT_OFF_T bool depends on !64BIT help All new 32-bit architectures should have 64-bit off_t type on userspace side which corresponds to the loff_t kernel type. This is the requirement for modern ABIs. Some existing architectures still support 32-bit off_t. This option is enabled for all such architectures explicitly. # Selected by 64 bit architectures which have a 32 bit f_tinode in struct ustat config ARCH_32BIT_USTAT_F_TINODE bool # Selected by architectures with Total Store Order (TSO) config ARCH_MEMORY_ORDER_TSO bool config HAVE_ASM_MODVERSIONS bool help This symbol should be selected by an architecture if it provides <asm/asm-prototypes.h> to support the module versioning for symbols exported from assembly code. config HAVE_REGS_AND_STACK_ACCESS_API bool help This symbol should be selected by an architecture if it supports the API needed to access registers and stack entries from pt_regs, declared in asm/ptrace.h For example the kprobes-based event tracer needs this API. config HAVE_RSEQ bool depends on HAVE_REGS_AND_STACK_ACCESS_API help This symbol should be selected by an architecture if it supports an implementation of restartable sequences. config HAVE_RUST bool help This symbol should be selected by an architecture if it supports Rust. config HAVE_FUNCTION_ARG_ACCESS_API bool help This symbol should be selected by an architecture if it supports the API needed to access function arguments from pt_regs, declared in asm/ptrace.h config HAVE_HW_BREAKPOINT bool depends on PERF_EVENTS config HAVE_MIXED_BREAKPOINTS_REGS bool depends on HAVE_HW_BREAKPOINT help Depending on the arch implementation of hardware breakpoints, some of them have separate registers for data and instruction breakpoints addresses, others have mixed registers to store them but define the access type in a control register. Select this option if your arch implements breakpoints under the latter fashion. config HAVE_USER_RETURN_NOTIFIER bool config HAVE_PERF_EVENTS_NMI bool help System hardware can generate an NMI using the perf event subsystem. Also has support for calculating CPU cycle events to determine how many clock cycles in a given period. config HAVE_HARDLOCKUP_DETECTOR_PERF bool depends on HAVE_PERF_EVENTS_NMI help The arch chooses to use the generic perf-NMI-based hardlockup detector. Must define HAVE_PERF_EVENTS_NMI. config HAVE_HARDLOCKUP_DETECTOR_ARCH bool help The arch provides its own hardlockup detector implementation instead of the generic ones. It uses the same command line parameters, and sysctl interface,