From: Marc Jorda <marc.jorda@bsc.es>
To: Al Grant <Al.Grant@arm.com>,
"leo.yan@linaro.org" <leo.yan@linaro.org>,
James Clark <James.Clark@arm.com>
Cc: "linux-perf-users@vger.kernel.org" <linux-perf-users@vger.kernel.org>
Subject: Re: Available Arm CPUs with SPE
Date: Mon, 28 Nov 2022 12:02:54 +0100 [thread overview]
Message-ID: <01b0d585-9de3-d1f1-727b-b2a69daa20f4@bsc.es> (raw)
In-Reply-To: <DB9PR08MB75125CC4EBA5F21EE3B5D33D860E9@DB9PR08MB7512.eurprd08.prod.outlook.com>
On 25/11/22 22:06, Al Grant wrote:
> Leo Yan wrote:
>> On Fri, Nov 25, 2022 at 12:17:18PM +0100, Marc Jorda wrote:
>>> Hello,
>>>
>>> I am trying to know which currently available Arm CPUs implement the
>>> Statistical Profiling Extension (SPE), does anyone know where can I
>>> find such information?
>> I don't know we have such kind of info, usually the most safe way is to check
>> SoC vendor's spec and confirm if Arm SPE is supported or not.
>>
>>> As far as I know, it is an optional extension in Armv8.2, but I don't
>>> know if it is mandatory for newer versions. Is it correct to assume
>>> that all Arm Neoverse CPUs have this extension?
>> Yes, since SPE is an optional extension, my understanding is we cannot 100% say
>> SPE is implemented in Armv8.2 and upwards CPUs (though it's unlikely not to
>> implement SPE in Arm standard CPUs).
>>
>> To avoid to mislead you, I would like loop in James and Al for more reliable
>> answer.
> Generally SPE has gone into the server cores but not the mobile cores,
> partly for power/area reasons. Neoverse N1 has SPE, but Cortex-A76,
> which is the same v8.2 architecture and a similar microarchitecture but
> optimized for mobile, does not have SPE. It's not entirely a Neoverse
> vs. Cortex thing though. You can use the PMU event repo to get a list,
> since all CPUs with SPE, and only those, will implement SAMPLE_POP:
>
> $ git clone https://ARM-software/data
> $ grep SAMPLE_POP data/pmu/*
> data/pmu/common_armv8.json: "name": "SAMPLE_POP",
> data/pmu/common_armv9.json: "name": "SAMPLE_POP",
> data/pmu/cortex-a715.json: "name": "SAMPLE_POP",
> data/pmu/cortex-x3.json: "name": "SAMPLE_POP",
> data/pmu/neoverse-n1.json: "name": "SAMPLE_POP",
> data/pmu/neoverse-n2.json: "name": "SAMPLE_POP",
> data/pmu/neoverse-v1.json: "name": "SAMPLE_POP",
> data/pmu/neoverse-v2.json: "name": "SAMPLE_POP",
>
> That is believed to be up to date and correct, but to be absolutely sure
> you would need to check the documentation for each core. Third-party
> implementations may also feature SPE, again you would need to check
> documentation. (We'd be happy to include additional PMU event JSON in
> the repo.)
>
> Also, keep in mind that even if SPE is on the CPU, some action is needed
> from firmware, hypervisor OS etc. to make it available to the end user.
> It might or might not be available to a guest OS for example.
>
> Al
Ok, thank you all for the tips, I will check these references.
Regards,
Marc
>
>> Thanks,
>> Leo
> IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
--
Accelerators and Communications for HPC
Computer Sciences Department
Barcelona Supercomputing Center (BSC)
prev parent reply other threads:[~2022-11-28 11:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-25 11:17 Available Arm CPUs with SPE Marc Jorda
2022-11-25 12:01 ` James Clark
2022-11-25 12:26 ` Leo Yan
2022-11-25 21:06 ` Al Grant
2022-11-28 11:02 ` Marc Jorda [this message]
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=01b0d585-9de3-d1f1-727b-b2a69daa20f4@bsc.es \
--to=marc.jorda@bsc.es \
--cc=Al.Grant@arm.com \
--cc=James.Clark@arm.com \
--cc=leo.yan@linaro.org \
--cc=linux-perf-users@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.