From: Marc Zyngier <maz@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>, Joey Gouly <joey.gouly@arm.com>,
Vincenzo Frascino <Vincenzo.Frascino@arm.com>,
Mark Brown <broonie@kernel.org>, 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:06:13 +0100 [thread overview]
Message-ID: <875ynbc1je.wl-maz@kernel.org> (raw)
In-Reply-To: <20220414115544.36204-1-tianjia.zhang@linux.alibaba.com>
On Thu, 14 Apr 2022 12:55:44 +0100,
Tianjia Zhang <tianjia.zhang@linux.alibaba.com> 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.
Err, not just that, for sure. What does this patch buys you on its
own, given that the kernel doesn't implement anything yet and that all
the SME instructions will UNDEF?
[1] is the real deal.
Thanks,
M.
[1] https://lore.kernel.org/r/20220408114328.1401034-1-broonie@kernel.org
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2022-04-14 12:06 UTC|newest]
Thread overview: 7+ 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 12:02 ` Mark Brown
2022-04-15 2:25 ` Tianjia Zhang
2022-04-19 13:58 ` Mark Brown
2022-04-24 9:27 ` Tianjia Zhang
2022-04-14 12:06 ` Marc Zyngier [this message]
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=875ynbc1je.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=Vincenzo.Frascino@arm.com \
--cc=anshuman.khandual@arm.com \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--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=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 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).