[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250206203249.GC1237@sol.localdomain>
Date: Thu, 6 Feb 2025 12:32:49 -0800
From: Eric Biggers <ebiggers@...nel.org>
To: Conor Dooley <conor@...nel.org>
Cc: linux-riscv@...ts.infradead.org,
Conor Dooley <conor.dooley@...rochip.com>,
Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Paul Walmsley <paul.walmsley@...ive.com>,
Palmer Dabbelt <palmer@...belt.com>,
Clément Léger <cleger@...osinc.com>,
Andy Chiu <andybnac@...il.com>, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 2/6] RISC-V: add vector crypto extension validation
checks
On Wed, Feb 05, 2025 at 04:05:08PM +0000, Conor Dooley wrote:
> The 1.0.0 Vector crypto spec states:
> The Zvknhb and Zvbc Vector Crypto Extensions --and accordingly
> the composite extensions Zvkn and Zvks-- require a Zve64x base,
> or application ("V") base Vector Extension. All of the other
> Vector Crypto Extensions can be built on any embedded (Zve*) or
> application ("V") base Vector Extension.
As previously discussed, the above paragraph incorrectly lists the set of crypto
extensions that require support for 64-bit elements. I have fixed this in the
latest RISC-V ISA manual. It looks like this patch would still do the same
thing either way, since it actually just checks that vector is available in some
form. But this is not the best version of the manual to quote from.
- Eric
Powered by blists - more mailing lists