From: Heiko Stuebner <heiko@sntech.de>
To: palmer@dabbelt.com, paul.walmsley@sifive.com
Cc: aou@eecs.berkeley.edu, heiko@sntech.de,
herbert@gondor.apana.org.au, davem@davemloft.net,
conor.dooley@microchip.com, linux-riscv@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org,
christoph.muellner@vrull.eu, ebiggers@kernel.org,
Heiko Stuebner <heiko.stuebner@vrull.eu>
Subject: [PATCH v6 0/3] Implement GCM ghash using Zbc and Zbkb extensions
Date: Sun, 9 Jul 2023 17:42:40 +0200 [thread overview]
Message-ID: <20230709154243.1582671-1-heiko@sntech.de> (raw)
From: Heiko Stuebner <heiko.stuebner@vrull.eu>
This was originally part of my vector crypto series, but was part
of a separate openssl merge request implementing GCM ghash as using
non-vector extensions.
As that pull-request
https://github.com/openssl/openssl/pull/20078
got merged recently into openssl, we could also check if this could
go into the kernel as well and provide a base for further accelerated
cryptographic support.
changes in v6:
- rebase on top of riscv/for-next
- rebase on top of Samuel Ortiz Arch-random series
https://lore.kernel.org/r/20230709115549.2666557-1-sameo@rivosinc.com
as it has the nicer Zbc + Zbkb integration for extensions and hwprobe
- update perl code with better licensing text (Eric)
This was also merged into the original openSSL sources
- add SPDX license identifier (Eric)
- drop unneeded fallback element in the private struct (Herbert)
Changes in v5:
- rebased on top of 6.4-based riscv/next
- code from openssl is now dual-licensed under Apache + BSD
see https://github.com/openssl/openssl/pull/20649
- separate init functions instead of creating them with macros (Nathan)
Changes in v4:
- rebase on top of riscv/for-next
- split out the scalar crypto implementation from the vector series
- refresh code from openSSL to match exactly
- Remove RFC label, as Zbc and Zbkb are ratified and
the cryptographic code was merged into openSSL
changes in v3:
- rebase on top of 6.3-rc2
- rebase on top of vector-v14 patchset
- add the missing Co-developed-by mentions to showcase
the people that did the actual openSSL crypto code
changes in v2:
- rebased on 6.2 + zbb series, so don't include already
applied changes anymore
- refresh code picked from openssl as that side matures
- more algorithms (SHA512, AES, SM3, SM4)
Heiko Stuebner (3):
RISC-V: expose Zbc as Kconfig option
RISC-V: hook new crypto subdir into build-system
RISC-V: crypto: add accelerated GCM GHASH implementation
arch/riscv/Kbuild | 1 +
arch/riscv/Kconfig | 23 ++
arch/riscv/crypto/Kconfig | 18 ++
arch/riscv/crypto/Makefile | 18 ++
arch/riscv/crypto/ghash-riscv64-glue.c | 291 +++++++++++++++++
arch/riscv/crypto/ghash-riscv64-zbc.pl | 430 +++++++++++++++++++++++++
arch/riscv/crypto/riscv.pm | 261 +++++++++++++++
crypto/Kconfig | 3 +
8 files changed, 1045 insertions(+)
create mode 100644 arch/riscv/crypto/Kconfig
create mode 100644 arch/riscv/crypto/Makefile
create mode 100644 arch/riscv/crypto/ghash-riscv64-glue.c
create mode 100644 arch/riscv/crypto/ghash-riscv64-zbc.pl
create mode 100644 arch/riscv/crypto/riscv.pm
--
2.39.2
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next reply other threads:[~2023-07-09 15:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-09 15:42 Heiko Stuebner [this message]
2023-07-09 15:42 ` [PATCH v6 1/3] RISC-V: expose Zbc as Kconfig option Heiko Stuebner
2023-07-09 15:42 ` [PATCH v6 2/3] RISC-V: hook new crypto subdir into build-system Heiko Stuebner
2023-07-09 15:42 ` [PATCH v6 3/3] RISC-V: crypto: add accelerated GCM GHASH implementation Heiko Stuebner
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=20230709154243.1582671-1-heiko@sntech.de \
--to=heiko@sntech.de \
--cc=aou@eecs.berkeley.edu \
--cc=christoph.muellner@vrull.eu \
--cc=conor.dooley@microchip.com \
--cc=davem@davemloft.net \
--cc=ebiggers@kernel.org \
--cc=heiko.stuebner@vrull.eu \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
/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