From: Mark Brown <broonie@kernel.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Will Deacon <will@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] arm64: ARM Scalable Matrix Extension is ARMv9-A
Date: Tue, 10 May 2022 13:43:32 +0100 [thread overview]
Message-ID: <Ynpd9DJ2SyC1Fi+a@sirena.org.uk> (raw)
In-Reply-To: <CAMuHMdVyjZzuNTrinRddt=nRDU-=tb+vgweemaOpG6QWsKC=JQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1502 bytes --]
On Tue, May 10, 2022 at 11:20:40AM +0200, Geert Uytterhoeven wrote:
> On Tue, May 10, 2022 at 11:15 AM Will Deacon <will@kernel.org> wrote:
> > On Mon, May 09, 2022 at 03:40:30PM +0200, Geert Uytterhoeven wrote:
> > > + The Scalable Matrix Extension (SME) is an ARMv9-A extension to the
> > > + AArch64 execution state which utilises a substantial subset of the
> > > + SVE instruction set, together with the addition of new architectural
> > Why is this useful information? The v9 vs v8 distinction is purely a
> Because I tend to disable support for extensions that are not present
> in Renesas SoCs in the (local) renesas_defconfig.
> If it's ARMv9, I know it's not present in e.g. Cortex-A57 or A-76.
Like Will says the versioning information is a shaky way of figuring
that out, especially with a feature like SME which is intended to be
totally optional. Even once you have v9 systems you're still going to
need to look at the specific systems to figure out what's implemented in
your specific silicon.
> > marketing thing, so I'd be _very_ wary of drawing any technical conclusions
> > based on that, especially as Arm have a track record for "backporting"
> > features into older CPUs if there is demand for it. Do you know what the
> > toolchains have done here? (i.e. is there march=armv9-a or can you do
> > march=armv8-a+sme or something else?).
> I have no idea. This option doesn't seem to control any compiler
> flags?
GCC does have armv9-a, not cheked clang.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2022-05-10 12:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-09 13:40 Geert Uytterhoeven
2022-05-09 15:35 ` Mark Brown
2022-05-10 8:08 ` Geert Uytterhoeven
2022-05-10 9:15 ` Will Deacon
2022-05-10 9:20 ` Geert Uytterhoeven
2022-05-10 12:43 ` Mark Brown [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=Ynpd9DJ2SyC1Fi+a@sirena.org.uk \
--to=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=geert@linux-m68k.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®