From: Marco Elver <elver@google.com>
To: Soham Bagchi <soham.bagchi@utah.edu>
Cc: dvyukov@google.com, andreyknvl@gmail.com,
akpm@linux-foundation.org, tglx@linutronix.de,
glider@google.com, sohambagchi@outlook.com, arnd@arndb.de,
kasan-dev@googlegroups.com, linux-kernel@vger.kernel.org,
corbet@lwn.net, workflows@vger.kernel.org,
linux-doc@vger.kernel.org
Subject: Re: [PATCH 2/2] kcov: load acquire coverage count in user-space code
Date: Mon, 28 Jul 2025 22:32:48 +0200 [thread overview]
Message-ID: <CANpmjNPWzJZrAFT3-013GJhksK0jkB6n0HmF+h0hdoQUwGuxfA@mail.gmail.com> (raw)
In-Reply-To: <20250728184318.1839137-2-soham.bagchi@utah.edu>
On Mon, 28 Jul 2025 at 20:43, Soham Bagchi <soham.bagchi@utah.edu> wrote:
>
> Updating the KCOV documentation to use a load-acquire
> operation for the first element of the shared memory
> buffer between kernel-space and user-space.
>
> The load-acquire pairs with the write memory barrier
> used in kcov_move_area()
>
> Signed-off-by: Soham Bagchi <soham.bagchi@utah.edu>
> ---
> Documentation/dev-tools/kcov.rst | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/dev-tools/kcov.rst b/Documentation/dev-tools/kcov.rst
> index 6611434e2dd..46450fb46fe 100644
> --- a/Documentation/dev-tools/kcov.rst
> +++ b/Documentation/dev-tools/kcov.rst
> @@ -287,6 +287,11 @@ handle instance id.
> The following program demonstrates using KCOV to collect coverage from both
> local tasks spawned by the process and the global task that handles USB bus #1:
>
> +The user-space code for KCOV should also use an acquire to fetch the count
> +of coverage entries in the shared buffer. This acquire pairs with the
> +corresponding write memory barrier (smp_wmb()) on the kernel-side in
> +kcov_move_area().
> +
This new paragraph is misplaced.
You've added it after the "... handles USB bus #1:" part which clearly
should be right before the code (note the colon).
Why not add what you wrote here as a block-comment (similar in style
to comment above the sleep()) right above the __atomic_load_n below? I
think those details probably don't quite belong into the high level
text, but the detailed code example.
> .. code-block:: c
>
> /* Same includes and defines as above. */
> @@ -361,7 +366,7 @@ local tasks spawned by the process and the global task that handles USB bus #1:
> */
> sleep(2);
>
> - n = __atomic_load_n(&cover[0], __ATOMIC_RELAXED);
> + n = __atomic_load_n(&cover[0], __ATOMIC_ACQUIRE);
> for (i = 0; i < n; i++)
> printf("0x%lx\n", cover[i + 1]);
> if (ioctl(fd, KCOV_DISABLE, 0))
> --
> 2.34.1
>
next prev parent reply other threads:[~2025-07-28 20:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-28 18:43 [PATCH 1/2] kcov: use write memory barrier after memcpy() in kcov_move_area() Soham Bagchi
2025-07-28 18:43 ` [PATCH 2/2] kcov: load acquire coverage count in user-space code Soham Bagchi
2025-07-28 20:32 ` Marco Elver [this message]
2025-08-03 18:05 ` [PATCH v2] " Soham Bagchi
2025-08-04 6:00 ` Marco Elver
2025-08-07 0:36 ` Andrew Morton
2025-07-28 20:26 ` [PATCH 1/2] kcov: use write memory barrier after memcpy() in kcov_move_area() 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=CANpmjNPWzJZrAFT3-013GJhksK0jkB6n0HmF+h0hdoQUwGuxfA@mail.gmail.com \
--to=elver@google.com \
--cc=akpm@linux-foundation.org \
--cc=andreyknvl@gmail.com \
--cc=arnd@arndb.de \
--cc=corbet@lwn.net \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=soham.bagchi@utah.edu \
--cc=sohambagchi@outlook.com \
--cc=tglx@linutronix.de \
--cc=workflows@vger.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