[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <aWar5eUPISsiLA00@x1>
Date: Tue, 13 Jan 2026 17:32:37 -0300
From: Arnaldo Carvalho de Melo <acme@...nel.org>
To: Ian Rogers <irogers@...gle.com>
Cc: James Clark <james.clark@...aro.org>,
John Garry <john.g.garry@...cle.com>, Will Deacon <will@...nel.org>,
Mike Leach <mike.leach@...aro.org>, Leo Yan <leo.yan@...ux.dev>,
Peter Zijlstra <peterz@...radead.org>,
Ingo Molnar <mingo@...hat.com>, Namhyung Kim <namhyung@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
Jiri Olsa <jolsa@...nel.org>,
Adrian Hunter <adrian.hunter@...el.com>,
Akio Kakuno <fj3333bs@...jp.fujitsu.com>,
Yoshihiro Furudera <fj5100bi@...itsu.com>,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-perf-users@...r.kernel.org
Subject: Re: [PATCH] perf vendor events arm64: Remove uncountable events
On Sat, Jan 03, 2026 at 05:27:49PM -0800, Ian Rogers wrote:
> On Sat, Jan 3, 2026 at 8:38 AM James Clark <james.clark@...aro.org> wrote:
> > On 02/01/2026 3:29 pm, Ian Rogers wrote:
> > > On Wed, Dec 31, 2025 at 4:13 AM James Clark <james.clark@...aro.org> wrote:
> > >> These events are never countable by the PMU and are only intended to
> > >> be used as external inputs to trace. Therefore showing them in 'perf
> > >> list' is misleading so remove them.
> > > What does "trace" mean in this context?
> > CPU trace, Either ETE (Embedded Trace Extension) or ETM (Embedded Trace
> > Macrocell). You can select PMU events as inputs to the trace block to
> > make it do things like start and stop tracing.
> Ah ok, trace immediately makes me think of `perf trace` currently.
> Presumably there's no perf integration for ETE and ETM that somehow
> use these event encodings? Looks not and the changes make sense to me.
>
> Reviewed-by: Ian Rogers <irogers@...gle.com>
Thanks, applied to perf-tools-next,
- Arnaldo
Powered by blists - more mailing lists