[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAP-5=fXyVtZChi1fkochiyKw6AztdhEE_rfpJUsz_P9po5bhXA@mail.gmail.com>
Date: Mon, 13 Jan 2025 07:51:15 -0800
From: Ian Rogers <irogers@...gle.com>
To: James Clark <james.clark@...aro.org>
Cc: 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>,
Arnaldo Carvalho de Melo <acme@...nel.org>, 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>, Kan Liang <kan.liang@...ux.intel.com>,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-perf-users@...r.kernel.org, Nick Forrington <nick.forrington@....com>
Subject: Re: [PATCH v1 1/2] perf vendor events arm64: Add N3 events/metrics
On Mon, Jan 13, 2025 at 4:35 AM James Clark <james.clark@...aro.org> wrote:
>
>
>
> On 10/01/2025 5:20 pm, Ian Rogers wrote:
> > Using the scripts at:
> > https://gitlab.arm.com/telemetry-solution/telemetry-solution/
> >
> > Generate perf json for neoverse-n3 using the following command:
> > ```
> > $ telemetry-solution/tools/perf_json_generator/generate.py \
> > tools/perf/ --telemetry-files \
> > telemetry-solution/data/pmu/cpu/neoverse/neoverse-n3.json:neoverse-n3
> > ```
> >
> > Signed-off-by: Ian Rogers <irogers@...gle.com>
> > ---
> > .../arm64/arm/neoverse-n3/core-imp-def.json | 930 ++++++++++++++++++
>
> I assume you got warnings about missing groups, if one is missing that
> results in everything being dumped in core-imp-def.json. I have an
> internal ticket open about it which is why I didn't post N3 and V3 jsons
> yet, I'll check on it again.
I was testing with JEVENTS_ARCH=all. I'm not sure what the group
warning is, do you have a link?
> Up to you whether you want to continue with it like this and I can send
> a fix up later but there's also a conflict with the recent Fujitsu
> Monaka events.
I'm happy to let you push the updates. An alternative, that may work
around the group issue, is just to push the event updates. Any chance
on an ETA?
Thanks,
Ian
Powered by blists - more mailing lists