From: Mark Brown <broonie@kernel.org>
To: Tianjia Zhang <tianjia.zhang@linux.alibaba.com>
Cc: Will Deacon <will@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Jonathan Corbet <corbet@lwn.net>, Marc Zyngier <maz@kernel.org>,
Joey Gouly <joey.gouly@arm.com>,
Vincenzo Frascino <Vincenzo.Frascino@arm.com>,
Arnd Bergmann <arnd@arndb.de>,
Anshuman Khandual <anshuman.khandual@arm.com>,
Fuad Tabba <tabba@google.com>,
Mark Rutland <mark.rutland@arm.com>,
Vladimir Murzin <vladimir.murzin@arm.com>,
James Morse <james.morse@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
linux-arm-kernel@lists.infradead.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64/sme: Add hwcap for Scalable Matrix Extension
Date: Thu, 14 Apr 2022 13:02:35 +0100 [thread overview]
Message-ID: <YlgNW0/ji6KlkyZo@sirena.org.uk> (raw)
In-Reply-To: <20220414115544.36204-1-tianjia.zhang@linux.alibaba.com>
[-- Attachment #1: Type: text/plain, Size: 894 bytes --]
On Thu, Apr 14, 2022 at 07:55:44PM +0800, Tianjia Zhang wrote:
> Allow userspace to detect support for SME (Scalable Matrix Extension)
> by providing a hwcap for it, using the official feature name FEAT_SME,
> declared in ARM DDI 0487H.a specification.
There's already a hwcap for the core feature and all the subfeatures
added as part of the series I've been posting for SME:
https://lore.kernel.org/linux-arm-kernel/20220408114328.1401034-1-broonie@kernel.org/
Why add something independently, especially given that there is no way
for userspace to do anything constructive with the feature without the
rest of the kernel support? Any attempt to use SME instructions without
kernel support will trap and generate a SIGILL even if the feature is
present in hardware.
Do you have a system with SME that you're trying to use? Review/testing
on the current series would be appreciated.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@kernel.org>
To: Tianjia Zhang <tianjia.zhang@linux.alibaba.com>
Cc: Will Deacon <will@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Jonathan Corbet <corbet@lwn.net>, Marc Zyngier <maz@kernel.org>,
Joey Gouly <joey.gouly@arm.com>,
Vincenzo Frascino <Vincenzo.Frascino@arm.com>,
Arnd Bergmann <arnd@arndb.de>,
Anshuman Khandual <anshuman.khandual@arm.com>,
Fuad Tabba <tabba@google.com>,
Mark Rutland <mark.rutland@arm.com>,
Vladimir Murzin <vladimir.murzin@arm.com>,
James Morse <james.morse@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
linux-arm-kernel@lists.infradead.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64/sme: Add hwcap for Scalable Matrix Extension
Date: Thu, 14 Apr 2022 13:02:35 +0100 [thread overview]
Message-ID: <YlgNW0/ji6KlkyZo@sirena.org.uk> (raw)
In-Reply-To: <20220414115544.36204-1-tianjia.zhang@linux.alibaba.com>
[-- Attachment #1.1: Type: text/plain, Size: 894 bytes --]
On Thu, Apr 14, 2022 at 07:55:44PM +0800, Tianjia Zhang wrote:
> Allow userspace to detect support for SME (Scalable Matrix Extension)
> by providing a hwcap for it, using the official feature name FEAT_SME,
> declared in ARM DDI 0487H.a specification.
There's already a hwcap for the core feature and all the subfeatures
added as part of the series I've been posting for SME:
https://lore.kernel.org/linux-arm-kernel/20220408114328.1401034-1-broonie@kernel.org/
Why add something independently, especially given that there is no way
for userspace to do anything constructive with the feature without the
rest of the kernel support? Any attempt to use SME instructions without
kernel support will trap and generate a SIGILL even if the feature is
present in hardware.
Do you have a system with SME that you're trying to use? Review/testing
on the current series would be appreciated.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
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-04-14 12:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-14 11:55 [PATCH] arm64/sme: Add hwcap for Scalable Matrix Extension Tianjia Zhang
2022-04-14 11:55 ` Tianjia Zhang
2022-04-14 12:02 ` Mark Brown [this message]
2022-04-14 12:02 ` Mark Brown
2022-04-15 2:25 ` Tianjia Zhang
2022-04-15 2:25 ` Tianjia Zhang
2022-04-19 13:58 ` Mark Brown
2022-04-19 13:58 ` Mark Brown
2022-04-24 9:27 ` Tianjia Zhang
2022-04-24 9:27 ` Tianjia Zhang
2022-04-14 12:06 ` Marc Zyngier
2022-04-14 12:06 ` Marc Zyngier
2022-04-15 2:30 ` Tianjia Zhang
2022-04-15 2:30 ` Tianjia Zhang
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=YlgNW0/ji6KlkyZo@sirena.org.uk \
--to=broonie@kernel.org \
--cc=Vincenzo.Frascino@arm.com \
--cc=anshuman.khandual@arm.com \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=james.morse@arm.com \
--cc=joey.gouly@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mathieu.poirier@linaro.org \
--cc=maz@kernel.org \
--cc=suzuki.poulose@arm.com \
--cc=tabba@google.com \
--cc=tianjia.zhang@linux.alibaba.com \
--cc=vladimir.murzin@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 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.