[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <fd9097a8-589c-90cb-4848-10386f5f664f@arm.com>
Date: Wed, 7 Sep 2022 16:39:01 +0100
From: Nick Forrington <nick.forrington@....com>
To: John Garry <john.garry@...wei.com>,
Robin Murphy <robin.murphy@....com>,
Arnaldo Carvalho de Melo <acme@...nel.org>
Cc: linux-kernel@...r.kernel.org, linux-perf-users@...r.kernel.org,
Will Deacon <will@...nel.org>,
James Clark <james.clark@....com>,
Mike Leach <mike.leach@...aro.org>,
Leo Yan <leo.yan@...aro.org>,
Mark Rutland <mark.rutland@....com>,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
Jiri Olsa <jolsa@...nel.org>,
Namhyung Kim <namhyung@...nel.org>,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH] perf vendor events: Update events for Neoverse E1
On 06/09/2022 15:47, John Garry wrote:
> On 06/09/2022 15:36, Robin Murphy wrote:
>>>
>>> This looks the same as an a65 event. And more similar cases below,
>>> at a glance.
>>
>> According to Anandtech, E1 is to A65 what N1 is to A76, and if they
>> say so then it must be true :)
>
> That would make life easier :)
>
> And even if only the events are the same, then they are the same core
> from pmu-events PoV.
I'll submit a v2 that de-dups A65 and E1 event files. (A65 data is
already correct, so need for the E1 fixes)
Thanks, Nick
Powered by blists - more mailing lists