From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Alexander Lochmann <info@alexander-lochmann.de>
Cc: Dmitry Vyukov <dvyukov@google.com>,
Andrey Konovalov <andreyknvl@google.com>,
Jonathan Corbet <corbet@lwn.net>,
Randy Dunlap <rdunlap@infradead.org>,
Andrew Klychkov <andrew.a.klychkov@gmail.com>,
Miguel Ojeda <ojeda@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Jakub Kicinski <kuba@kernel.org>,
Aleksandr Nogikh <nogikh@google.com>,
Wei Yongjun <weiyongjun1@huawei.com>,
Maciej Grochowski <maciej.grochowski@pm.me>,
kasan-dev@googlegroups.com, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCHv3] Introduced new tracing mode KCOV_MODE_UNIQUE.
Date: Sat, 27 Mar 2021 11:37:06 +0100 [thread overview]
Message-ID: <YF8K0k1bc3e381qS@kroah.com> (raw)
In-Reply-To: <20210326205135.6098-1-info@alexander-lochmann.de>
On Fri, Mar 26, 2021 at 09:51:28PM +0100, Alexander Lochmann wrote:
> It simply stores the executed PCs.
> The execution order is discarded.
> Each bit in the shared buffer represents every fourth
> byte of the text segment.
> Since a call instruction on every supported
> architecture is at least four bytes, it is safe
> to just store every fourth byte of the text segment.
> In contrast to KCOV_MODE_TRACE_PC, the shared buffer
> cannot overflow. Thus, all executed PCs are recorded.
Odd line-wrapping :(
Anyway, this describes _what_ this does, but I have no idea _why_ we
want this at all. What does this do that you can not do today? Why is
this needed? Who will use this? What tools have been modified to work
with it to prove it works properly?
thanks,
greg k-h
next prev parent reply other threads:[~2021-03-27 10:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-26 20:51 [PATCHv3] Introduced new tracing mode KCOV_MODE_UNIQUE Alexander Lochmann
2021-03-27 10:37 ` Greg Kroah-Hartman [this message]
2021-03-27 14:56 ` Andrey Konovalov
2021-04-16 8:42 ` Dmitry Vyukov
2021-04-17 19:46 ` Andrey Konovalov
2021-09-18 20:22 ` Alexander Lochmann
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=YF8K0k1bc3e381qS@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=andrew.a.klychkov@gmail.com \
--cc=andreyknvl@google.com \
--cc=corbet@lwn.net \
--cc=dvyukov@google.com \
--cc=info@alexander-lochmann.de \
--cc=kasan-dev@googlegroups.com \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maciej.grochowski@pm.me \
--cc=nogikh@google.com \
--cc=ojeda@kernel.org \
--cc=rdunlap@infradead.org \
--cc=weiyongjun1@huawei.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