From: Peter Zijlstra <peterz@infradead.org>
To: Jann Horn <jannh@google.com>
Cc: Dmitry Vyukov <dvyukov@google.com>,
Andrey Konovalov <andreyknvl@gmail.com>,
Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <nick.desaulniers+lkml@gmail.com>,
Bill Wendling <morbo@google.com>,
Justin Stitt <justinstitt@google.com>,
linux-kernel@vger.kernel.org, kasan-dev@googlegroups.com,
llvm@lists.linux.dev, Ingo Molnar <mingo@redhat.com>,
Josh Poimboeuf <jpoimboe@kernel.org>
Subject: Re: [PATCH 0/3] KCOV function entry/exit records
Date: Wed, 11 Mar 2026 23:57:17 +0100 [thread overview]
Message-ID: <20260311225717.GY606826@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <20260311-kcov-extrecord-v1-0-68f03c4a05ad@google.com>
On Wed, Mar 11, 2026 at 10:06:13PM +0100, Jann Horn wrote:
> This series adds a KCOV feature that userspace can use to keep track of
> the current call stack. When userspace enables the new mode
> KCOV_TRACE_PC_EXT, collected instruction addresses are tagged with one
> of three types:
>
> - function entry
> - non-entry basic block
> - function exit
>
> This requires corresponding LLVM support; an LLVM patch implementing
> this feature has been uploaded for review at
> <https://github.com/llvm/llvm-project/pull/185972>, but hasn't landed yet.
And I don't suppose KCOV will finally honour noinstr ?
next prev parent reply other threads:[~2026-03-11 22:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-11 21:06 Jann Horn
2026-03-11 21:06 ` [PATCH 1/3] sched: Ensure matching stack state for kcov disable/enable on switch Jann Horn
2026-03-11 21:06 ` [PATCH 2/3] kcov: wire up compiler instrumentation for CONFIG_KCOV_EXT_RECORDS Jann Horn
2026-03-13 7:53 ` Dmitry Vyukov
2026-03-13 7:59 ` Dmitry Vyukov
2026-03-13 12:40 ` Jann Horn
2026-03-13 12:40 ` Jann Horn
2026-03-11 21:06 ` [PATCH 3/3] kcov: introduce extended PC coverage collection mode Jann Horn
2026-03-13 7:58 ` Dmitry Vyukov
2026-03-13 12:31 ` Jann Horn
2026-03-16 16:50 ` Alexander Potapenko
2026-03-11 22:57 ` Peter Zijlstra [this message]
2026-03-12 11:44 ` [PATCH 0/3] KCOV function entry/exit records Jann Horn
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=20260311225717.GY606826@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=andreyknvl@gmail.com \
--cc=dvyukov@google.com \
--cc=jannh@google.com \
--cc=jpoimboe@kernel.org \
--cc=justinstitt@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=mingo@redhat.com \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=nick.desaulniers+lkml@gmail.com \
/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®