From: Eric Biggers <ebiggers@kernel.org>
To: linux-crypto@vger.kernel.org
Cc: Ard Biesheuvel <ardb@kernel.org>,
"Jason A . Donenfeld" <Jason@zx2c4.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
sparclinux@vger.kernel.org, Andreas Larsson <andreas@gaisler.com>,
"David S . Miller" <davem@davemloft.net>,
Stian Halseth <stian@itx.no>, Magnus Lindholm <linmag7@gmail.com>,
John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
Eric Biggers <ebiggers@kernel.org>
Subject: [PATCH 0/4] Migrate SPARC64 accelerated AES modes into library
Date: Tue, 17 Nov 2026 20:10:29 -0800 [thread overview]
Message-ID: <20261118041033.50014-1-ebiggers@kernel.org> (raw)
This series is targeting libcrypto-next. It can also be retrieved from:
git fetch https://git.kernel.org/pub/scm/linux/kernel/git/ebiggers/linux.git aes-sparc-v1
This series migrates the SPARC64 crypto opcodes accelerated
implementations of AES-ECB, AES-CBC, and AES-CTR into lib/crypto/.
This makes the AES-ECB, AES-CBC, and AES-CTR library APIs be properly
accelerated on SPARC64, while still being available in the
crypto_skcipher API via crypto/aes.c. As usual, the longstanding issue
of acceleration being disabled by default is also fixed.
After this, the only thing left in arch/sparc/crypto/ is Camellia.
Tested in QEMU (specifically commit 97c88c61d45d, which has Stian
Halseth's recent changes that added support for the AES, CRC32C, SHA1,
SHA256, and SHA512 opcodes) with the new ECB, CBC, and CTR KUnit tests
(https://lore.kernel.org/r/20261116062849.1071038-1-ebiggers@kernel.org/)
and CONFIG_CRYPTO_SELFTESTS_FULL=y, using Stian Halseth's patch that
makes the SPARC kernel detect QEMU's support for the crypto opcodes
(https://lore.kernel.org/r/20261117112914.2300417-1-stian@itx.no/).
Eric Biggers (4):
lib/crypto: sparc/aes: Add and use round key load helper
lib/crypto: sparc/aes-ctr: Migrate optimized code into library
lib/crypto: sparc/aes-ecb: Migrate optimized code into library
lib/crypto: sparc/aes-cbc: Migrate optimized code into library
arch/sparc/crypto/Kconfig | 10 -
arch/sparc/crypto/Makefile | 2 -
arch/sparc/crypto/aes_glue.c | 344 ----------------------------------
crypto/aes.c | 13 +-
include/crypto/aes.h | 39 ----
lib/crypto/sparc/aes.h | 348 +++++++++++++++++++++++++++++++----
lib/crypto/sparc/aes_asm.S | 24 ++-
7 files changed, 334 insertions(+), 446 deletions(-)
delete mode 100644 arch/sparc/crypto/aes_glue.c
base-commit: 30e5781e2cd0aeffd80d524bbdac176579a3235f
--
2.56.1
next reply other threads:[~2026-11-18 4:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-18 4:10 Eric Biggers [this message]
2026-11-18 4:10 ` [PATCH 1/4] lib/crypto: sparc/aes: Add and use round key load helper Eric Biggers
2026-11-18 4:10 ` [PATCH 2/4] lib/crypto: sparc/aes-ctr: Migrate optimized code into library Eric Biggers
2026-11-18 4:10 ` [PATCH 3/4] lib/crypto: sparc/aes-ecb: " Eric Biggers
2026-11-18 4:10 ` [PATCH 4/4] lib/crypto: sparc/aes-cbc: " Eric Biggers
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=20261118041033.50014-1-ebiggers@kernel.org \
--to=ebiggers@kernel.org \
--cc=Jason@zx2c4.com \
--cc=andreas@gaisler.com \
--cc=ardb@kernel.org \
--cc=davem@davemloft.net \
--cc=glaubitz@physik.fu-berlin.de \
--cc=herbert@gondor.apana.org.au \
--cc=linmag7@gmail.com \
--cc=linux-crypto@vger.kernel.org \
--cc=sparclinux@vger.kernel.org \
--cc=stian@itx.no \
/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