From: Leo Yan <leo.yan@arm.com>
To: sashiko-reviews@lists.linux.dev
Cc: linux-perf-users@vger.kernel.org
Subject: Re: [PATCH 2/3] perf: arm_spe: Suppress redundant ITRACE start records
Date: Wed, 2 Sep 2026 17:39:55 +0100 [thread overview]
Message-ID: <20260902163955.GW8904@e132581.arm.com> (raw)
In-Reply-To: <20260901164705.042781F000E9@smtp.kernel.org>
On Tue, Sep 01, 2026 at 04:47:04PM +0000, sashiko-bot@kernel.org wrote:
[...]
> > @@ -890,6 +890,8 @@ static void arm_spe_pmu_start(struct perf_event *event, int flags)
> > return;
> > }
> >
> > + perf_event_itrace_started(event);
> > +
>
> [Severity: Medium]
> Does this correctly suppress redundant records for inherited events?
>
> The core event scheduling path in perf_log_itrace_start() internally resolves
> to event->parent before checking for the PERF_ATTACH_ITRACE flag.
>
> Since perf_event_itrace_started() only mutates the local child event's
> attach_state, the parent event's flag remains permanently unset.
>
> Won't this cause the perf core to continue emitting redundant ITRACE_START
> records on every subsequent schedule-in for inherited events, negating the
> intended fix?
This would be an issue in the event core layer and should be addressed
separately. I will send a separate patch to fix it.
next prev parent reply other threads:[~2026-09-02 16:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-01 16:36 [PATCH 0/3] perf: Suppress redundant ITRACE start records for Arm SPE and CoreSight Leo Yan
2026-09-01 16:36 ` [PATCH 1/3] perf/core: Export perf_event_itrace_started() Leo Yan
2026-09-01 16:48 ` sashiko-bot
2026-09-01 16:36 ` [PATCH 2/3] perf: arm_spe: Suppress redundant ITRACE start records Leo Yan
2026-09-01 16:47 ` sashiko-bot
2026-09-02 16:39 ` Leo Yan [this message]
2026-09-01 16:36 ` [PATCH 3/3] coresight: perf: Suppress " Leo Yan
2026-09-01 16:45 ` 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=20260902163955.GW8904@e132581.arm.com \
--to=leo.yan@arm.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox