From: sashiko-bot@kernel.org
To: "Leo Yan" <leo.yan@arm.com>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: [PATCH 3/3] coresight: perf: Suppress ITRACE start records
Date: Tue, 01 Sep 2026 16:45:53 +0000 [thread overview]
Message-ID: <20260901164554.38BB41F00A3A@smtp.kernel.org> (raw)
In-Reply-To: <20260901-perf_suppress_itrace_start_records-v1-3-c4fbc6860859@arm.com>
> PERF_RECORD_ITRACE_START establishes the initial thread context at the
> beginning of a trace. Afterwards, decoders track the thread context using
> context packets.
>
> Call perf_event_itrace_started() after successfully starting the event
> to prevent perf core from emitting redundant PERF_RECORD_ITRACE_START
> records when the event is scheduled in again.
>
> When per-thread mode traces multiple child threads, tooling should
> enable context ID tracing instead to identify each thread.
>
> Signed-off-by: Leo Yan <leo.yan@arm.com>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260901-perf_suppress_itrace_start_records-v1-0-c4fbc6860859@arm.com?part=3
prev parent reply other threads:[~2026-09-01 16:45 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
2026-09-01 16:36 ` [PATCH 3/3] coresight: perf: Suppress " Leo Yan
2026-09-01 16:45 ` sashiko-bot [this message]
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=20260901164554.38BB41F00A3A@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=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 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.