From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: barebox@lists.infradead.org
Subject: [PATCH v2 0/7] ARM64: crypto: add Crypto Extensions accelerated SHA implementation
Date: Fri, 26 May 2023 08:37:39 +0200 [thread overview]
Message-ID: <20230526063746.1155297-1-a.fatoum@pengutronix.de> (raw)
This shaves 400ms of a FIT image boot that uses sha256 as digest for
the images referenced by the selected configuration:
barebox@imx8mn-old:/ time bootm -d kernel-a
Dryrun. Aborted.
time: 998ms
barebox@imx8mn-new:/ time bootm -d kernel-a
Dryrun. Aborted.
time: 601ms
We also use SHA256 to verify barebox proper when in high assurance boot,
but that still uses the software implementation.
v1 -> v2:
- use dedicated CONFIG_ symbols for SHA224/SHA256 selftest (Sascha)
- check against CONFIG_ symbols for generic algorithm
- remove #define DEBUG in selftest
- fix oversight in new <linux/linkage.h> __ALIGN definition,
which broke build on x86 and PowerPC
-
Ahmad Fatoum (7):
crypto: digest: match driver name if no algo name matches
test: self: add digest test
include: sync <linux/linkage.h> with Linux
ARM: asm: implement CPU_BE/CPU_LE
ARM: asm: import Linux adr_l/ldr_l assembler.h definitions
crypto: sha: reorder struct sha*_state into Linux order
ARM64: crypto: add Crypto Extensions accelerated SHA implementation
arch/arm/Makefile | 3 +-
arch/arm/crypto/Makefile | 6 +
arch/arm/crypto/sha1-ce-core.S | 149 ++++++++++++++
arch/arm/crypto/sha1-ce-glue.c | 93 +++++++++
arch/arm/crypto/sha2-ce-core.S | 156 +++++++++++++++
arch/arm/crypto/sha2-ce-glue.c | 121 ++++++++++++
arch/arm/include/asm/assembler.h | 230 ++++++++++++++++++++++
arch/arm/include/asm/neon.h | 8 +
commands/digest.c | 2 +-
common/Kconfig | 6 +
crypto/Kconfig | 21 ++
crypto/digest.c | 11 +-
include/crypto/sha.h | 10 +-
include/crypto/sha1_base.h | 104 ++++++++++
include/crypto/sha256_base.h | 129 +++++++++++++
include/linux/barebox-wrapper.h | 1 +
include/linux/linkage.h | 321 ++++++++++++++++++++++++++++---
include/linux/string.h | 20 ++
test/self/Kconfig | 6 +
test/self/Makefile | 1 +
test/self/digest.c | 213 ++++++++++++++++++++
21 files changed, 1572 insertions(+), 39 deletions(-)
create mode 100644 arch/arm/crypto/sha1-ce-core.S
create mode 100644 arch/arm/crypto/sha1-ce-glue.c
create mode 100644 arch/arm/crypto/sha2-ce-core.S
create mode 100644 arch/arm/crypto/sha2-ce-glue.c
create mode 100644 arch/arm/include/asm/neon.h
create mode 100644 include/crypto/sha1_base.h
create mode 100644 include/crypto/sha256_base.h
create mode 100644 test/self/digest.c
--
2.39.2
next reply other threads:[~2023-05-26 6:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-26 6:37 Ahmad Fatoum [this message]
2023-05-26 6:37 ` [PATCH v2 1/7] crypto: digest: match driver name if no algo name matches Ahmad Fatoum
2023-05-26 6:37 ` [PATCH v2 2/7] test: self: add digest test Ahmad Fatoum
2023-05-26 6:37 ` [PATCH v2 3/7] include: sync <linux/linkage.h> with Linux Ahmad Fatoum
2023-05-26 6:54 ` Sascha Hauer
2023-05-26 7:45 ` Ahmad Fatoum
2023-05-26 6:37 ` [PATCH v2 4/7] ARM: asm: implement CPU_BE/CPU_LE Ahmad Fatoum
2023-05-26 6:37 ` [PATCH v2 5/7] ARM: asm: import Linux adr_l/ldr_l assembler.h definitions Ahmad Fatoum
2023-05-26 6:37 ` [PATCH v2 6/7] crypto: sha: reorder struct sha*_state into Linux order Ahmad Fatoum
2023-05-26 6:37 ` [PATCH v2 7/7] ARM64: crypto: add Crypto Extensions accelerated SHA implementation Ahmad Fatoum
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=20230526063746.1155297-1-a.fatoum@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
/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