From: John Garry <john.garry@huawei.com>
To: Robin Murphy <robin.murphy@arm.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Nick Forrington <nick.forrington@arm.com>
Cc: <linux-kernel@vger.kernel.org>,
<linux-perf-users@vger.kernel.org>,
"Will Deacon" <will@kernel.org>,
James Clark <james.clark@arm.com>,
Mike Leach <mike.leach@linaro.org>, Leo Yan <leo.yan@linaro.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>,
"Namhyung Kim" <namhyung@kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] perf vendor events: Update events for Neoverse E1
Date: Tue, 6 Sep 2022 15:47:49 +0100 [thread overview]
Message-ID: <0f73ba23-b892-035a-10f0-384e77b71040@huawei.com> (raw)
In-Reply-To: <caaf43aa-6c36-b263-30ba-7a4d3edd4e20@arm.com>
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.
thanks,
John
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-09-06 15:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-05 15:30 [PATCH] perf vendor events: Update events for Neoverse E1 Nick Forrington
2022-09-06 13:07 ` Arnaldo Carvalho de Melo
2022-09-06 13:22 ` John Garry
2022-09-06 14:36 ` Robin Murphy
2022-09-06 14:47 ` John Garry [this message]
2022-09-07 15:39 ` Nick Forrington
2022-09-08 18:37 ` Arnaldo Carvalho de Melo
2022-09-12 17:13 ` Nick Forrington
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=0f73ba23-b892-035a-10f0-384e77b71040@huawei.com \
--to=john.garry@huawei.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=james.clark@arm.com \
--cc=jolsa@kernel.org \
--cc=leo.yan@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mike.leach@linaro.org \
--cc=namhyung@kernel.org \
--cc=nick.forrington@arm.com \
--cc=robin.murphy@arm.com \
--cc=will@kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).