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: Tue, 19 Apr 2022 14:58:17 +0100 [thread overview] Message-ID: <Yl6/+baDhElVxwyC@sirena.org.uk> (raw) In-Reply-To: <e7a0d0d4-b6ca-6fec-df33-929961f0d43e@linux.alibaba.com> [-- Attachment #1: Type: text/plain, Size: 1891 bytes --] On Fri, Apr 15, 2022 at 10:25:33AM +0800, Tianjia Zhang wrote: > On 4/14/22 8:02 PM, Mark Brown wrote: > > On Thu, Apr 14, 2022 at 07:55:44PM +0800, Tianjia Zhang wrote: > > 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. > Great job, I encountered the issue of invalid REVD (requires FEAT_SME) > instruction when developing SVE2 programs, so I plan to gradually > support SME in the kernel, thanks for your contribution, you can ignore > my patch. I see. Unfortunately all the new registers mean that we really need to define all the ABI as soon as we enable anything and the only thing we can really skip out on when doing initial enablement is KVM (which I have in fact skipped for the time being, I'll look at that at some point after the initial support is landed). > In addition, I would like to ask a question, whether there is an > alternative SVE2 instruction for the REVD instruction that can complete > this operation, if the machine does not support SME. I'm not aware of anything, but I am mostly focused on the OS support rather than any of the actual mathematical operations that are more the point of these architecture features so I might be missing something. > > Do you have a system with SME that you're trying to use? Review/testing > > on the current series would be appreciated. > Unfortunately, the value currently read by my machine ID_AA64PFR1_EL1 > register is 0x121. It seems that the hardware does not support SME. Is > there any other help I can provide? Other than verifying that the series doesn't cause trouble for systems without SME [-- 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: Tue, 19 Apr 2022 14:58:17 +0100 [thread overview] Message-ID: <Yl6/+baDhElVxwyC@sirena.org.uk> (raw) In-Reply-To: <e7a0d0d4-b6ca-6fec-df33-929961f0d43e@linux.alibaba.com> [-- Attachment #1.1: Type: text/plain, Size: 1891 bytes --] On Fri, Apr 15, 2022 at 10:25:33AM +0800, Tianjia Zhang wrote: > On 4/14/22 8:02 PM, Mark Brown wrote: > > On Thu, Apr 14, 2022 at 07:55:44PM +0800, Tianjia Zhang wrote: > > 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. > Great job, I encountered the issue of invalid REVD (requires FEAT_SME) > instruction when developing SVE2 programs, so I plan to gradually > support SME in the kernel, thanks for your contribution, you can ignore > my patch. I see. Unfortunately all the new registers mean that we really need to define all the ABI as soon as we enable anything and the only thing we can really skip out on when doing initial enablement is KVM (which I have in fact skipped for the time being, I'll look at that at some point after the initial support is landed). > In addition, I would like to ask a question, whether there is an > alternative SVE2 instruction for the REVD instruction that can complete > this operation, if the machine does not support SME. I'm not aware of anything, but I am mostly focused on the OS support rather than any of the actual mathematical operations that are more the point of these architecture features so I might be missing something. > > Do you have a system with SME that you're trying to use? Review/testing > > on the current series would be appreciated. > Unfortunately, the value currently read by my machine ID_AA64PFR1_EL1 > register is 0x121. It seems that the hardware does not support SME. Is > there any other help I can provide? Other than verifying that the series doesn't cause trouble for systems without SME [-- 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-19 13:58 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 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 [this message] 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=Yl6/+baDhElVxwyC@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: linkBe 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.