]> git.ipfire.org Git - thirdparty/kernel/linux.git/commit
crypto: x86/aes-gcm - rename avx10 and avx10_512 to avx512
authorEric Biggers <ebiggers@kernel.org>
Thu, 2 Oct 2025 02:31:12 +0000 (19:31 -0700)
committerEric Biggers <ebiggers@kernel.org>
Mon, 27 Oct 2025 03:37:40 +0000 (20:37 -0700)
commit12beec21c50950cc9a1907750200af4eb99a8aca
tree7a186a592d6b59a6b916c545f5031b2d8814a60c
parentf65e90860679d39e01c8bf40b8c740d7ca61476c
crypto: x86/aes-gcm - rename avx10 and avx10_512 to avx512

With the "avx10_256" code removed and the AVX10 specification having
been changed to basically just be a re-packaged AVX512, the "avx10_512"
name no longer makes sense.  Replace it with "avx512".

While doing this, also add the "vaes_" prefix in places that didn't
already have it.  The result is that the two VAES optimized
implementations are consistently called vaes_avx2 and vaes_avx512.
(Also drop the "-x86_64" part of the assembly filename, to keep it from
getting too long.  There's no 32-bit version of this code, and the fact
that it's 64-bit is unremarkable; it's the norm for new code.)

Note: although aes_gcm_aad_update_vaes_avx512() (previously called
aes_gcm_aad_update_vaes_avx10()) uses at most 256-bit vectors, it still
depends on the AVX512 CPU feature.  So its new name is still accurate.
Also, a later commit will make it sometimes use 512-bit vectors anyway.

Acked-by: Ard Biesheuvel <ardb@kernel.org>
Tested-by: Ard Biesheuvel <ardb@kernel.org>
Link: https://lore.kernel.org/r/20251002023117.37504-4-ebiggers@kernel.org
Signed-off-by: Eric Biggers <ebiggers@kernel.org>
arch/x86/crypto/Makefile
arch/x86/crypto/aes-gcm-aesni-x86_64.S
arch/x86/crypto/aes-gcm-vaes-avx2.S
arch/x86/crypto/aes-gcm-vaes-avx512.S [moved from arch/x86/crypto/aes-gcm-avx10-x86_64.S with 92% similarity]
arch/x86/crypto/aesni-intel_glue.c