From: James Clark <james.clark@arm.com>
To: Marc Jorda <marc.jorda@bsc.es>
Cc: "linux-perf-users@vger.kernel.org" <linux-perf-users@vger.kernel.org>
Subject: Re: Available Arm CPUs with SPE
Date: Fri, 25 Nov 2022 12:01:49 +0000 [thread overview]
Message-ID: <ecfae192-95fd-0814-1896-d60e9d44417a@arm.com> (raw)
In-Reply-To: <2695ecbe-816e-eab7-8da2-30e0f62ae926@bsc.es>
On 25/11/2022 11:17, 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?
Hi Marc,
Graviton 2s on AWS should have it and N1SDP has it. You will need a
metal instance at the moment so that rules out Graviton 3.
Make sure you read the kernel requirements section here [1]
>
> 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?
I'm not sure about this, as you say it's optional, but whether all
current Neoverse CPUs have it or not I don't know.
I found this here [2] if it helps:
SPE is an optional Armv8-A architecture extension available since
Armv8.2-A. Examples of infrastructure CPUs supporting SPE are
Neoverse-E1, Neoverse N1 and Neoverse V1. Graviton 2 and Ampere Altra
are examples of Neoverse-based processors
>
> Thank you very much,
> Marc
>
[1]:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/tools/perf/Documentation/perf-arm-spe.txt
[2]:
https://community.arm.com/arm-community-blogs/b/tools-software-ides-blog/posts/arm-allinea-studio-21-0
next prev parent reply other threads:[~2022-11-25 12:01 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 [this message]
2022-11-25 12:26 ` Leo Yan
2022-11-25 21:06 ` Al Grant
2022-11-28 11:02 ` Marc Jorda
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=ecfae192-95fd-0814-1896-d60e9d44417a@arm.com \
--to=james.clark@arm.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=marc.jorda@bsc.es \
/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.