mirror of
https://github.com/torvalds/linux.git
synced 2024-12-28 05:41:55 +00:00
arch/Kconfig: fix indentation
The convention for indentation seems to be a single tab. Help text is further indented by an additional two whitespaces. Fix the lines that violate these rules. Link: https://lkml.kernel.org/r/20230201162435.218368-1-juerg.haefliger@canonical.com Signed-off-by: Juerg Haefliger <juerg.haefliger@canonical.com> Reviewed-by: Kees Cook <keescook@chromium.org> Cc: Dan Li <ashimida@linux.alibaba.com> Cc: "Eric W. Biederman" <ebiederm@xmission.com> Cc: Frederic Weisbecker <frederic@kernel.org> Cc: Josh Poimboeuf <jpoimboe@kernel.org> Cc: Juerg Haefliger <juerg.haefliger@canonical.com> Cc: Marco Elver <elver@google.com> Cc: Mark Rutland <mark.rutland@arm.com> Cc: Nathan Chancellor <nathan@kernel.org> Cc: Nick Desaulniers <ndesaulniers@google.com> Cc: Paul E. McKenney <paulmck@kernel.org> Cc: Peter Zijlstra <peterz@infradead.org> Cc: Sami Tolvanen <samitolvanen@google.com> Cc: Tom Rix <trix@redhat.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
This commit is contained in:
parent
21773790a7
commit
9f79ffc193
128
arch/Kconfig
128
arch/Kconfig
@ -35,7 +35,7 @@ config HOTPLUG_SMT
|
|||||||
bool
|
bool
|
||||||
|
|
||||||
config GENERIC_ENTRY
|
config GENERIC_ENTRY
|
||||||
bool
|
bool
|
||||||
|
|
||||||
config KPROBES
|
config KPROBES
|
||||||
bool "Kprobes"
|
bool "Kprobes"
|
||||||
@ -55,26 +55,26 @@ config JUMP_LABEL
|
|||||||
depends on HAVE_ARCH_JUMP_LABEL
|
depends on HAVE_ARCH_JUMP_LABEL
|
||||||
select OBJTOOL if HAVE_JUMP_LABEL_HACK
|
select OBJTOOL if HAVE_JUMP_LABEL_HACK
|
||||||
help
|
help
|
||||||
This option enables a transparent branch optimization that
|
This option enables a transparent branch optimization that
|
||||||
makes certain almost-always-true or almost-always-false branch
|
makes certain almost-always-true or almost-always-false branch
|
||||||
conditions even cheaper to execute within the kernel.
|
conditions even cheaper to execute within the kernel.
|
||||||
|
|
||||||
Certain performance-sensitive kernel code, such as trace points,
|
Certain performance-sensitive kernel code, such as trace points,
|
||||||
scheduler functionality, networking code and KVM have such
|
scheduler functionality, networking code and KVM have such
|
||||||
branches and include support for this optimization technique.
|
branches and include support for this optimization technique.
|
||||||
|
|
||||||
If it is detected that the compiler has support for "asm goto",
|
If it is detected that the compiler has support for "asm goto",
|
||||||
the kernel will compile such branches with just a nop
|
the kernel will compile such branches with just a nop
|
||||||
instruction. When the condition flag is toggled to true, the
|
instruction. When the condition flag is toggled to true, the
|
||||||
nop will be converted to a jump instruction to execute the
|
nop will be converted to a jump instruction to execute the
|
||||||
conditional block of instructions.
|
conditional block of instructions.
|
||||||
|
|
||||||
This technique lowers overhead and stress on the branch prediction
|
This technique lowers overhead and stress on the branch prediction
|
||||||
of the processor and generally makes the kernel faster. The update
|
of the processor and generally makes the kernel faster. The update
|
||||||
of the condition is slower, but those are always very rare.
|
of the condition is slower, but those are always very rare.
|
||||||
|
|
||||||
( On 32-bit x86, the necessary options added to the compiler
|
( On 32-bit x86, the necessary options added to the compiler
|
||||||
flags may increase the size of the kernel slightly. )
|
flags may increase the size of the kernel slightly. )
|
||||||
|
|
||||||
config STATIC_KEYS_SELFTEST
|
config STATIC_KEYS_SELFTEST
|
||||||
bool "Static key selftest"
|
bool "Static key selftest"
|
||||||
@ -98,9 +98,9 @@ config KPROBES_ON_FTRACE
|
|||||||
depends on KPROBES && HAVE_KPROBES_ON_FTRACE
|
depends on KPROBES && HAVE_KPROBES_ON_FTRACE
|
||||||
depends on DYNAMIC_FTRACE_WITH_REGS
|
depends on DYNAMIC_FTRACE_WITH_REGS
|
||||||
help
|
help
|
||||||
If function tracer is enabled and the arch supports full
|
If function tracer is enabled and the arch supports full
|
||||||
passing of pt_regs to function tracing, then kprobes can
|
passing of pt_regs to function tracing, then kprobes can
|
||||||
optimize on top of function tracing.
|
optimize on top of function tracing.
|
||||||
|
|
||||||
config UPROBES
|
config UPROBES
|
||||||
def_bool n
|
def_bool n
|
||||||
@ -154,21 +154,21 @@ config HAVE_EFFICIENT_UNALIGNED_ACCESS
|
|||||||
config ARCH_USE_BUILTIN_BSWAP
|
config ARCH_USE_BUILTIN_BSWAP
|
||||||
bool
|
bool
|
||||||
help
|
help
|
||||||
Modern versions of GCC (since 4.4) have builtin functions
|
Modern versions of GCC (since 4.4) have builtin functions
|
||||||
for handling byte-swapping. Using these, instead of the old
|
for handling byte-swapping. Using these, instead of the old
|
||||||
inline assembler that the architecture code provides in the
|
inline assembler that the architecture code provides in the
|
||||||
__arch_bswapXX() macros, allows the compiler to see what's
|
__arch_bswapXX() macros, allows the compiler to see what's
|
||||||
happening and offers more opportunity for optimisation. In
|
happening and offers more opportunity for optimisation. In
|
||||||
particular, the compiler will be able to combine the byteswap
|
particular, the compiler will be able to combine the byteswap
|
||||||
with a nearby load or store and use load-and-swap or
|
with a nearby load or store and use load-and-swap or
|
||||||
store-and-swap instructions if the architecture has them. It
|
store-and-swap instructions if the architecture has them. It
|
||||||
should almost *never* result in code which is worse than the
|
should almost *never* result in code which is worse than the
|
||||||
hand-coded assembler in <asm/swab.h>. But just in case it
|
hand-coded assembler in <asm/swab.h>. But just in case it
|
||||||
does, the use of the builtins is optional.
|
does, the use of the builtins is optional.
|
||||||
|
|
||||||
Any architecture with load-and-swap or store-and-swap
|
Any architecture with load-and-swap or store-and-swap
|
||||||
instructions should set this. And it shouldn't hurt to set it
|
instructions should set this. And it shouldn't hurt to set it
|
||||||
on architectures that don't have such instructions.
|
on architectures that don't have such instructions.
|
||||||
|
|
||||||
config KRETPROBES
|
config KRETPROBES
|
||||||
def_bool y
|
def_bool y
|
||||||
@ -720,13 +720,13 @@ config LTO_CLANG_FULL
|
|||||||
depends on !COMPILE_TEST
|
depends on !COMPILE_TEST
|
||||||
select LTO_CLANG
|
select LTO_CLANG
|
||||||
help
|
help
|
||||||
This option enables Clang's full Link Time Optimization (LTO), which
|
This option enables Clang's full Link Time Optimization (LTO), which
|
||||||
allows the compiler to optimize the kernel globally. If you enable
|
allows the compiler to optimize the kernel globally. If you enable
|
||||||
this option, the compiler generates LLVM bitcode instead of ELF
|
this option, the compiler generates LLVM bitcode instead of ELF
|
||||||
object files, and the actual compilation from bitcode happens at
|
object files, and the actual compilation from bitcode happens at
|
||||||
the LTO link step, which may take several minutes depending on the
|
the LTO link step, which may take several minutes depending on the
|
||||||
kernel configuration. More information can be found from LLVM's
|
kernel configuration. More information can be found from LLVM's
|
||||||
documentation:
|
documentation:
|
||||||
|
|
||||||
https://llvm.org/docs/LinkTimeOptimization.html
|
https://llvm.org/docs/LinkTimeOptimization.html
|
||||||
|
|
||||||
@ -1330,9 +1330,9 @@ config ARCH_HAS_CC_PLATFORM
|
|||||||
bool
|
bool
|
||||||
|
|
||||||
config HAVE_SPARSE_SYSCALL_NR
|
config HAVE_SPARSE_SYSCALL_NR
|
||||||
bool
|
bool
|
||||||
help
|
help
|
||||||
An architecture should select this if its syscall numbering is sparse
|
An architecture should select this if its syscall numbering is sparse
|
||||||
to save space. For example, MIPS architecture has a syscall array with
|
to save space. For example, MIPS architecture has a syscall array with
|
||||||
entries at 4000, 5000 and 6000 locations. This option turns on syscall
|
entries at 4000, 5000 and 6000 locations. This option turns on syscall
|
||||||
related optimizations for a given architecture.
|
related optimizations for a given architecture.
|
||||||
@ -1356,35 +1356,35 @@ config HAVE_PREEMPT_DYNAMIC_CALL
|
|||||||
depends on HAVE_STATIC_CALL
|
depends on HAVE_STATIC_CALL
|
||||||
select HAVE_PREEMPT_DYNAMIC
|
select HAVE_PREEMPT_DYNAMIC
|
||||||
help
|
help
|
||||||
An architecture should select this if it can handle the preemption
|
An architecture should select this if it can handle the preemption
|
||||||
model being selected at boot time using static calls.
|
model being selected at boot time using static calls.
|
||||||
|
|
||||||
Where an architecture selects HAVE_STATIC_CALL_INLINE, any call to a
|
Where an architecture selects HAVE_STATIC_CALL_INLINE, any call to a
|
||||||
preemption function will be patched directly.
|
preemption function will be patched directly.
|
||||||
|
|
||||||
Where an architecture does not select HAVE_STATIC_CALL_INLINE, any
|
Where an architecture does not select HAVE_STATIC_CALL_INLINE, any
|
||||||
call to a preemption function will go through a trampoline, and the
|
call to a preemption function will go through a trampoline, and the
|
||||||
trampoline will be patched.
|
trampoline will be patched.
|
||||||
|
|
||||||
It is strongly advised to support inline static call to avoid any
|
It is strongly advised to support inline static call to avoid any
|
||||||
overhead.
|
overhead.
|
||||||
|
|
||||||
config HAVE_PREEMPT_DYNAMIC_KEY
|
config HAVE_PREEMPT_DYNAMIC_KEY
|
||||||
bool
|
bool
|
||||||
depends on HAVE_ARCH_JUMP_LABEL
|
depends on HAVE_ARCH_JUMP_LABEL
|
||||||
select HAVE_PREEMPT_DYNAMIC
|
select HAVE_PREEMPT_DYNAMIC
|
||||||
help
|
help
|
||||||
An architecture should select this if it can handle the preemption
|
An architecture should select this if it can handle the preemption
|
||||||
model being selected at boot time using static keys.
|
model being selected at boot time using static keys.
|
||||||
|
|
||||||
Each preemption function will be given an early return based on a
|
Each preemption function will be given an early return based on a
|
||||||
static key. This should have slightly lower overhead than non-inline
|
static key. This should have slightly lower overhead than non-inline
|
||||||
static calls, as this effectively inlines each trampoline into the
|
static calls, as this effectively inlines each trampoline into the
|
||||||
start of its callee. This may avoid redundant work, and may
|
start of its callee. This may avoid redundant work, and may
|
||||||
integrate better with CFI schemes.
|
integrate better with CFI schemes.
|
||||||
|
|
||||||
This will have greater overhead than using inline static calls as
|
This will have greater overhead than using inline static calls as
|
||||||
the call to the preemption function cannot be entirely elided.
|
the call to the preemption function cannot be entirely elided.
|
||||||
|
|
||||||
config ARCH_WANT_LD_ORPHAN_WARN
|
config ARCH_WANT_LD_ORPHAN_WARN
|
||||||
bool
|
bool
|
||||||
@ -1407,8 +1407,8 @@ config ARCH_SUPPORTS_PAGE_TABLE_CHECK
|
|||||||
config ARCH_SPLIT_ARG64
|
config ARCH_SPLIT_ARG64
|
||||||
bool
|
bool
|
||||||
help
|
help
|
||||||
If a 32-bit architecture requires 64-bit arguments to be split into
|
If a 32-bit architecture requires 64-bit arguments to be split into
|
||||||
pairs of 32-bit arguments, select this option.
|
pairs of 32-bit arguments, select this option.
|
||||||
|
|
||||||
config ARCH_HAS_ELFCORE_COMPAT
|
config ARCH_HAS_ELFCORE_COMPAT
|
||||||
bool
|
bool
|
||||||
|
Loading…
Reference in New Issue
Block a user