From: "tip-bot2 for Dmitry Vyukov" <tip-bot2@linutronix.de>
To: linux-tip-commits@vger.kernel.org
Cc: Dmitry Vyukov <dvyukov@google.com>,
Thomas Gleixner <tglx@linutronix.de>,
Alexander Potapenko <glider@google.com>,
Marco Elver <elver@google.com>,
Andrey Konovalov <andreyknvl@gmail.com>,
"Peter Zijlstra (Intel)" <peterz@infradead.org>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: [tip: x86/build] x86: Ignore stack unwinding in KCOV
Date: Thu, 08 Aug 2024 15:49:13 -0000 [thread overview]
Message-ID: <172313215346.2215.17061867082349895480.tip-bot2@tip-bot2> (raw)
In-Reply-To: <eaf54b8634970b73552dcd38bf9be6ef55238c10.1718092070.git.dvyukov@google.com>
The following commit has been merged into the x86/build branch of tip:
Commit-ID: ae94b263f5f69c180347e795fbefa051b65aacc3
Gitweb: https://git.kernel.org/tip/ae94b263f5f69c180347e795fbefa051b65aacc3
Author: Dmitry Vyukov <dvyukov@google.com>
AuthorDate: Tue, 11 Jun 2024 09:50:33 +02:00
Committer: Thomas Gleixner <tglx@linutronix.de>
CommitterDate: Thu, 08 Aug 2024 17:36:35 +02:00
x86: Ignore stack unwinding in KCOV
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>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Reviewed-by: Alexander Potapenko <glider@google.com>
Reviewed-by: Marco Elver <elver@google.com>
Reviewed-by: Andrey Konovalov <andreyknvl@gmail.com>
Acked-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Link: https://lore.kernel.org/all/eaf54b8634970b73552dcd38bf9be6ef55238c10.1718092070.git.dvyukov@google.com
---
arch/x86/kernel/Makefile | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/arch/x86/kernel/Makefile b/arch/x86/kernel/Makefile
index a847180..f791898 100644
--- a/arch/x86/kernel/Makefile
+++ b/arch/x86/kernel/Makefile
@@ -35,6 +35,14 @@ KMSAN_SANITIZE_nmi.o := n
# If instrumentation of the following files is enabled, boot hangs during
# first second.
KCOV_INSTRUMENT_head$(BITS).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
next prev parent reply other threads:[~2024-08-08 15:49 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-11 7:50 [PATCH v2 0/4] KCOV fixes Dmitry Vyukov
2024-06-11 7:50 ` [PATCH v2 1/4] x86/entry: Remove unwanted instrumentation in common_interrupt() Dmitry Vyukov
2024-06-19 11:19 ` Peter Zijlstra
2024-06-19 13:05 ` Dmitry Vyukov
2024-08-08 15:49 ` [tip: x86/build] " tip-bot2 for Dmitry Vyukov
2024-06-11 7:50 ` [PATCH v2 2/4] kcov: add interrupt handling self test Dmitry Vyukov
2024-06-11 9:29 ` Marco Elver
2024-06-13 23:01 ` Andrey Konovalov
2024-06-19 11:13 ` Peter Zijlstra
2024-06-19 11:18 ` Dmitry Vyukov
2024-06-19 11:26 ` Peter Zijlstra
2024-08-08 15:49 ` [tip: x86/build] kcov: Add " tip-bot2 for Dmitry Vyukov
2024-06-11 7:50 ` [PATCH v2 3/4] module: Fix KCOV-ignored file name Dmitry Vyukov
2024-06-11 9:29 ` Marco Elver
2024-06-13 22:55 ` Andrey Konovalov
2024-08-08 15:49 ` [tip: x86/build] " tip-bot2 for Dmitry Vyukov
2024-06-11 7:50 ` [PATCH v2 4/4] x86: Ignore stack unwinding in KCOV Dmitry Vyukov
2024-06-13 22:51 ` Andrey Konovalov
2024-06-19 11:23 ` Peter Zijlstra
2024-06-19 13:10 ` Dmitry Vyukov
2024-08-08 15:49 ` tip-bot2 for Dmitry Vyukov [this message]
2024-06-11 9:31 ` [PATCH v2 0/4] KCOV fixes Dmitry Vyukov
2024-06-19 5:20 ` Dmitry Vyukov
2024-06-19 8:30 ` Borislav Petkov
2024-08-05 12:52 ` Andrey Konovalov
2024-08-08 15:18 ` Thomas Gleixner
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=172313215346.2215.17061867082349895480.tip-bot2@tip-bot2 \
--to=tip-bot2@linutronix.de \
--cc=andreyknvl@gmail.com \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=glider@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=peterz@infradead.org \
--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®