New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[22.03] Add aarch64 asm accelerated versions of crypto algorihtms to kernel #10030
Closed
cotequeiroz
wants to merge
11
commits into
openwrt:openwrt-22.03
from
cotequeiroz:arm64-kernel-crypto
Closed
[22.03] Add aarch64 asm accelerated versions of crypto algorihtms to kernel #10030
cotequeiroz
wants to merge
11
commits into
openwrt:openwrt-22.03
from
cotequeiroz:arm64-kernel-crypto
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This enables arm64/neon version of AES, SHA256 and SHA512 algorithms in the kernel. bcm2710 does not support armv8 crypto extensions, so they are not included. Signed-off-by: Eneas U de Queiroz <cotequeiroz@gmail.com> (cherry picked from commit 38ebb21)
This enables arm64/neon version of AES, SHA256 and SHA512 algorithms in the kernel. bcm2711 does not support armv8 crypto extensions, so they are not included. Signed-off-by: Eneas U de Queiroz <cotequeiroz@gmail.com> (cherry picked from commit 7b6beb7)
This enables armv8 crypto extensions version of AES and GHASH algorithms in the kernel. Signed-off-by: Eneas U de Queiroz <cotequeiroz@gmail.com> (cherry picked from commit b2cb87b)
This enables armv8 crypto extensions version of AES, GHASH, SHA256 and CRC T10 algorithms in the kernel. Signed-off-by: Eneas U de Queiroz <cotequeiroz@gmail.com> (cherry picked from commit eb33232)
This is result of a plain make kernel_oldconfig CONFIG_TARGET=subtarget. Signed-off-by: Eneas U de Queiroz <cotequeiroz@gmail.com> (cherry picked from commit a4c6384)
This enables armv8 crypto extensions version of AES, GHASH, SHA1, SHA256, and SHA512 algorithms in the kernel. The choice of algorithms match the 32-bit versions that are enabled in the target config-5.10 file, but were only used by the cortexa9 subtarget. Signed-off-by: Eneas U de Queiroz <cotequeiroz@gmail.com> (cherry picked from commit f5167e1)
This is result of a plain make kernel_oldconfig CONFIG_TARGET=subtarget. Signed-off-by: Eneas U de Queiroz <cotequeiroz@gmail.com> (cherry picked from commit 39b6af1)
This enables armv8 crypto extensions version of AES, GHASH, SHA1, SHA256, and SHA512 algorithms in the kernel. The choice of algorithms match the 32-bit versions that are enabled in the target config-5.10 file, but were only used by the cortexa9 subtarget. Signed-off-by: Eneas U de Queiroz <cotequeiroz@gmail.com> (cherry picked from commit 06bb5ac)
Adds the crypto extensions version of the CRC T10 algorithm that is already built into the kernel. Signed-off-by: Eneas U de Queiroz <cotequeiroz@gmail.com> (cherry picked from commit 1b94e4a)
This enables armv8 crypto extensions version of AES, GHASH, and CRC T10 algorithms in the kernel. Signed-off-by: Eneas U de Queiroz <cotequeiroz@gmail.com> (cherry picked from commit b1346d3)
This enables armv8 crypto extensions version of AES, GHASH, SHA1, and CRC T10 algorithms in the kernel. Signed-off-by: Eneas U de Queiroz <cotequeiroz@gmail.com> (cherry picked from commit 9be3518)
@Ansuel |
@cotequeiroz yhea will merge this ASAP |
Merged to openwrt-22.03 with
|
mans0n
added
the
release/22.03
pull request/issue targeted (also) for OpenWrt 22.03 release
label
Jun 11, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
kernel
pull request/issue with Linux kernel related changes
release/22.03
pull request/issue targeted (also) for OpenWrt 22.03 release
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is the same as #9756, applied to 22.03. Just like I did in #9756, I compiled-tested the changes for all targets, but I don't have any of them to run-test.
This series adds armv8 Crypto Extensions accelerated versions of crypto algorithms to the following targets:
bcm4908
layerscape/armv8_64b
mvebu/cortexa53
mvebu/cortexa72
rockchip/armv8
sunxi/cortexa53
Also:
octeontx
was missing the CE optimized CRC T10 algorihtm, so it was added here.bcm27xx/bcm2710
andbcm27xx/bcm2711
don't have the crypto extensions, so the SIMD neon versions were added instead.mvebu/cortex{a53,a72}
configs were given a refresh, although they are not strictly required.For most targets, no algorithms were added if the regular C version was not included. I've made an exception for mvebu: I've mirrored the algorithms that the 32-bit cortex-a9 has. I found it rather odd that the asm config symbols were set at the target, not subtarget config, even though they only apply to the 32-bit a9. So, i mimicked what 86e27f1 had done to cortex-a9 and added the same algorithms to the 64-bit targets.