diff options
| author | Eric Biggers <ebiggers@kernel.org> | 2026-09-27 15:43:10 -0700 |
|---|---|---|
| committer | Eric Biggers <ebiggers@kernel.org> | 2026-09-30 09:42:10 -0700 |
| commit | f083f8de5290dc6384b2929306c0e99714c93d6f (patch) | |
| tree | be7c4b7720ea51a6c9e6825649e426f63af26a71 /tools/perf/scripts/python/bin/stackcollapse-report | |
| parent | bd888e3dc9e06731eb78e4ad142c64c82a220edf (diff) | |
| download | linux-f083f8de5290dc6384b2929306c0e99714c93d6f.tar.gz linux-f083f8de5290dc6384b2929306c0e99714c93d6f.zip | |
lib/crypto: riscv/aes-ctr: Migrate optimized code into library
Instead of exposing the riscv-optimized AES-CTR code via a
riscv-specific crypto_skcipher algorithm, just implement the AES-CTR
library functions. This is simpler, it makes the AES-CTR library
functions be riscv-optimized, and it also fixes the longstanding issue
where the riscv-optimized AES-CTR code was disabled by default. AES-CTR
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_enckey rather than struct crypto_aes_ctx, and
adjust the argument order.
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/.
Also re-enable the library-based "ccm(aes)" and "gcm(aes)".
Reviewed-by: Ard Biesheuvel <ardb@kernel.org>
Link: https://patch.msgid.link/20260927224418.109759-20-ebiggers@kernel.org
Signed-off-by: Eric Biggers <ebiggers@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/bin/stackcollapse-report')
0 files changed, 0 insertions, 0 deletions
