[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <174007597343.1790567.6925222970795406098.b4-ty@kernel.org>
Date: Thu, 20 Feb 2025 10:26:13 -0800
From: Namhyung Kim <namhyung@...nel.org>
To: linux-perf-users@...r.kernel.org, james.clark@...aro.org,
irogers@...gle.com, Yangyu Chen <cyy@...self.name>
Cc: acme@...nel.org, adrian.hunter@...el.com,
alexander.shishkin@...ux.intel.com, fj3333bs@...jp.fujitsu.com,
fj5100bi@...itsu.com, john.g.garry@...cle.com, jolsa@...nel.org,
kan.liang@...ux.intel.com, leo.yan@...ux.dev,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
mark.rutland@....com, mike.leach@...aro.org, mingo@...hat.com,
peterz@...radead.org, will@...nel.org
Subject: Re: [PATCH] perf vendor events arm64: Fix incorrect CPU_CYCLE in
metrics expr
On Thu, 13 Feb 2025 16:44:09 +0800, Yangyu Chen wrote:
> Some existing metrics for Neoverse N3 and V3 expressions use CPU_CYCLE
> to represent the number of cycles, but this is incorrect. The correct
> event to use is CPU_CYCLES.
>
> I encountered this issue while working on a patch to add pmu events for
> Cortex A720 and A520 by reusing the existing patch for Neoverse N3 and
> V3 by James Clark [1] and my check script [2] reported this issue.
>
> [...]
Applied to perf-tools-next, thanks!
Best regards,
Namhyung
Powered by blists - more mailing lists