diff options
| author | Eric Biggers <ebiggers@kernel.org> | 2026-09-27 15:43:11 -0700 |
|---|---|---|
| committer | Eric Biggers <ebiggers@kernel.org> | 2026-09-30 09:42:10 -0700 |
| commit | 69897f5e8552af8835a2c8a36aa7d597e1cf6689 (patch) | |
| tree | ab0bb9c731e815640efea99d59666f244d97b08b /tools/perf/scripts/python/bin/stackcollapse-record | |
| parent | f083f8de5290dc6384b2929306c0e99714c93d6f (diff) | |
| download | linux-69897f5e8552af8835a2c8a36aa7d597e1cf6689.tar.gz linux-69897f5e8552af8835a2c8a36aa7d597e1cf6689.zip | |
lib/crypto: riscv/aes-xts: Migrate optimized code into library
Instead of exposing the riscv-optimized AES-XTS code via a
riscv-specific crypto_skcipher algorithm, just implement the AES-XTS
library functions. This is simpler, it makes the AES-XTS library
functions be riscv-optimized, and it also fixes the longstanding issue
where the riscv-optimized AES-XTS code was disabled by default. AES-XTS
support still remains available through crypto_skcipher via
crypto/aes.c, but individual architectures no longer need to handle it.
To match what the library expects, update the assembly functions to
operate on struct aes_key rather than struct crypto_aes_ctx, adjust the
argument order, and remove the redundant ciphertext stealing support
which is already implemented in a generic way in the library.
Bump up the priority of the corresponding library-based algorithm on
riscv now that it no longer has to be lower than arch/riscv/crypto/.
Reviewed-by: Ard Biesheuvel <ardb@kernel.org>
Link: https://patch.msgid.link/20260927224418.109759-21-ebiggers@kernel.org
Signed-off-by: Eric Biggers <ebiggers@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/bin/stackcollapse-record')
0 files changed, 0 insertions, 0 deletions
