From: Dmitry Vyukov <dvyukov@google.com>
To: tglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
dave.hansen@linux.intel.com, x86@kernel.org
Cc: linux-kernel@vger.kernel.org, syzkaller@googlegroups.com,
elver@google.com, glider@google.com, nogikh@google.com,
tarasmadan@google.com, Dmitry Vyukov <dvyukov@google.com>
Subject: [PATCH 4/4] x86: Ignore stack unwinding in KCOV
Date: Tue, 4 Jun 2024 15:45:05 +0200 [thread overview]
Message-ID: <4c05efefe278bc5b140dba40eb1d195cceb2e6ce.1717507310.git.dvyukov@google.com> (raw)
In-Reply-To: <cover.1717507310.git.dvyukov@google.com>
Stack unwinding produces large amounts of uninteresting coverage.
It's called from KASAN kmalloc/kfree hooks, fault injection, etc.
It's not particularly useful and is not a function of system call args.
Ignore that code.
Signed-off-by: Dmitry Vyukov <dvyukov@google.com>
Cc: x86@kernel.org
Cc: linux-kernel@vger.kernel.org
Cc: syzkaller@googlegroups.com
---
arch/x86/kernel/Makefile | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/arch/x86/kernel/Makefile b/arch/x86/kernel/Makefile
index 20a0dd51700a..cd49ebfae984 100644
--- a/arch/x86/kernel/Makefile
+++ b/arch/x86/kernel/Makefile
@@ -39,6 +39,14 @@ KMSAN_SANITIZE_sev.o := n
# first second.
KCOV_INSTRUMENT_head$(BITS).o := n
KCOV_INSTRUMENT_sev.o := n
+# These are called from save_stack_trace() on debug paths,
+# and produce large amounts of uninteresting coverage.
+KCOV_INSTRUMENT_stacktrace.o := n
+KCOV_INSTRUMENT_dumpstack.o := n
+KCOV_INSTRUMENT_dumpstack_$(BITS).o := n
+KCOV_INSTRUMENT_unwind_orc.o := n
+KCOV_INSTRUMENT_unwind_frame.o := n
+KCOV_INSTRUMENT_unwind_guess.o := n
CFLAGS_irq.o := -I $(src)/../include/asm/trace
--
2.45.1.467.gbab1589fc0-goog
next prev parent reply other threads:[~2024-06-04 13:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1717507310.git.dvyukov@google.com>
2024-06-04 13:45 ` [PATCH 1/4] x86/entry: Remove unwanted instrumentation in common_interrupt() Dmitry Vyukov
2024-06-04 15:04 ` Alexander Potapenko
2024-06-04 16:00 ` Dave Hansen
2024-06-04 16:07 ` Dmitry Vyukov
2024-06-04 19:38 ` Peter Zijlstra
2024-06-04 13:45 ` [PATCH 2/4] kcov: add interrupt handling self test Dmitry Vyukov
2024-06-04 15:26 ` Alexander Potapenko
2024-06-05 9:09 ` Marco Elver
2024-06-05 9:18 ` Dmitry Vyukov
2024-06-05 9:33 ` Marco Elver
2024-06-11 7:52 ` Dmitry Vyukov
2024-06-04 13:45 ` [PATCH 3/4] module: Fix KCOV-ignored file name Dmitry Vyukov
2024-06-04 15:03 ` Alexander Potapenko
2024-06-04 13:45 ` Dmitry Vyukov [this message]
2024-06-04 15:06 ` [PATCH 4/4] x86: Ignore stack unwinding in KCOV Alexander Potapenko
2024-06-05 8:26 ` Marco Elver
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4c05efefe278bc5b140dba40eb1d195cceb2e6ce.1717507310.git.dvyukov@google.com \
--to=dvyukov@google.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=elver@google.com \
--cc=glider@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=nogikh@google.com \
--cc=syzkaller@googlegroups.com \
--cc=tarasmadan@google.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®