From: sashiko-bot@kernel.org
To: "Jaidev Shastri" <jaidevshastri@vt.edu>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: [PATCH 1/3] perf/core: publish the aux_event link with release semantics
Date: Tue, 22 Sep 2026 01:24:14 +0000 [thread overview]
Message-ID: <20260922012415.04C371F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260921-mb-perf-core-v1-1-ac56a719c02b@vt.edu>
> From: Jaidev Shastri <jaidevshastri@vt.edu>
>
> perf_get_aux_event() links an aux_output event to its group leader with
> a plain store to event->aux_event once the leader has been validated.
> perf_aux_output_begin() and the AUX sample path read the link with plain
> loads, from the PMU interrupt on the CPU the event is scheduled on.
>
> Store the link with smp_store_release() and read it with
> smp_load_acquire(), so that a reader that sees the link also sees the
> state of the leader it points at.
>
> Found with MBCheck, a static herd7-based memory consistency checker.
>
> Signed-off-by: Jaidev Shastri <jaidevshastri@vt.edu>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260921-mb-perf-core-v1-0-ac56a719c02b@vt.edu?part=1
next prev parent reply other threads:[~2026-09-22 1:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 1:13 [PATCH 0/3] perf/core: order three publications against their readers Jaidev Shastri via B4 Relay
2026-09-22 1:13 ` Jaidev Shastri
2026-09-22 1:13 ` [PATCH 1/3] perf/core: publish the aux_event link with release semantics Jaidev Shastri via B4 Relay
2026-09-22 1:13 ` Jaidev Shastri
2026-09-22 1:24 ` sashiko-bot [this message]
2026-09-22 1:13 ` [PATCH 2/3] perf/core: install the guest callbacks before the guest_state gate Jaidev Shastri via B4 Relay
2026-09-22 1:13 ` Jaidev Shastri
2026-09-22 1:25 ` sashiko-bot
2026-09-22 1:13 ` [PATCH 3/3] perf/core: publish perf_event_cache with release semantics Jaidev Shastri via B4 Relay
2026-09-22 1:13 ` Jaidev Shastri
2026-09-22 1:24 ` sashiko-bot
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=20260922012415.04C371F000FF@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=jaidevshastri@vt.edu \
--cc=linux-perf-users@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.