From: Danny Tsen <dtsen@linux.ibm.com>
To: linux-crypto@vger.kernel.org
Cc: herbert@gondor.apana.org.au, dtsen@us.ibm.com,
nayna@linux.ibm.com, linux-kernel@vger.kernel.org,
Danny Tsen <dtsen@linux.ibm.com>,
appro@cryptogams.org, ltcgcw@linux.vnet.ibm.com,
leitao@debian.org, linuxppc-dev@lists.ozlabs.org
Subject: [PATCH v2 0/3] crypto: X25519 supports for ppc64le
Date: Thu, 16 May 2024 11:19:54 -0400 [thread overview]
Message-ID: <20240516151957.2215-1-dtsen@linux.ibm.com> (raw)
This patch series provide X25519 support for ppc64le with a new module
curve25519-ppc64le.
The implementation is based on CRYPTOGAMs perl output from x25519-ppc64.pl.
(see https://github.com/dot-asm/cryptogams/)
Modified and added 4 supporting functions.
This patch has passed the selftest by running modprobe
curve25519-ppc64le.
Danny Tsen (3):
X25519 low-level primitives for ppc64le.
X25519 core functions for ppc64le
Update Kconfig and Makefile for ppc64le x25519.
arch/powerpc/crypto/Kconfig | 11 +
arch/powerpc/crypto/Makefile | 2 +
arch/powerpc/crypto/curve25519-ppc64le-core.c | 299 ++++++++
arch/powerpc/crypto/curve25519-ppc64le_asm.S | 671 ++++++++++++++++++
4 files changed, 983 insertions(+)
create mode 100644 arch/powerpc/crypto/curve25519-ppc64le-core.c
create mode 100644 arch/powerpc/crypto/curve25519-ppc64le_asm.S
--
2.31.1
next reply other threads:[~2024-05-16 15:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-16 15:19 Danny Tsen [this message]
2024-05-16 15:19 ` [PATCH v2 1/3] crypto: X25519 low-level primitives for ppc64le Danny Tsen
2024-05-16 15:19 ` [PATCH v2 2/3] crypto: X25519 core functions " Danny Tsen
2024-07-19 0:25 ` Jeff Johnson
2024-07-19 0:28 ` Jeff Johnson
2024-05-16 15:19 ` [PATCH v2 3/3] crypto: Update Kconfig and Makefile for ppc64le x25519 Danny Tsen
2024-05-31 10:20 ` [PATCH v2 0/3] crypto: X25519 supports for ppc64le Herbert Xu
2024-05-31 21:10 ` Danny Tsen
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=20240516151957.2215-1-dtsen@linux.ibm.com \
--to=dtsen@linux.ibm.com \
--cc=appro@cryptogams.org \
--cc=dtsen@us.ibm.com \
--cc=herbert@gondor.apana.org.au \
--cc=leitao@debian.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=ltcgcw@linux.vnet.ibm.com \
--cc=nayna@linux.ibm.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;
as well as URLs for NNTP newsgroup(s).