kcov: improve CONFIG_ARCH_HAS_KCOV help text
The help text for CONFIG_ARCH_HAS_KCOV is stale, and describes the feature as being enabled only for x86_64, when it is now enabled for several architectures, including arm, arm64, powerpc, and s390. Let's remove that stale help text, and update it along the lines of hat for ARCH_HAS_FORTIFY_SOURCE, better describing when an architecture should select CONFIG_ARCH_HAS_KCOV. Link: http://lkml.kernel.org/r/20190412102733.5154-1-mark.rutland@arm.com Signed-off-by: Mark Rutland <mark.rutland@arm.com> Acked-by: Dmitry Vyukov <dvyukov@google.com> Cc: Kees Cook <keescook@chromium.org> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
This commit is contained in:
parent
3b991208b8
commit
40453c4f9b
1 changed files with 3 additions and 3 deletions
|
@ -753,9 +753,9 @@ endmenu # "Memory Debugging"
|
||||||
config ARCH_HAS_KCOV
|
config ARCH_HAS_KCOV
|
||||||
bool
|
bool
|
||||||
help
|
help
|
||||||
KCOV does not have any arch-specific code, but currently it is enabled
|
An architecture should select this when it can successfully
|
||||||
only for x86_64. KCOV requires testing on other archs, and most likely
|
build and run with CONFIG_KCOV. This typically requires
|
||||||
disabling of instrumentation for some early boot code.
|
disabling instrumentation for some early boot code.
|
||||||
|
|
||||||
config CC_HAS_SANCOV_TRACE_PC
|
config CC_HAS_SANCOV_TRACE_PC
|
||||||
def_bool $(cc-option,-fsanitize-coverage=trace-pc)
|
def_bool $(cc-option,-fsanitize-coverage=trace-pc)
|
||||||
|
|
Loading…
Reference in a new issue