From: Herbert Xu <herbert@gondor.apana.org.au>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: gilad@benyossef.com, linux-crypto@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/2] crypto: implement SM4 for arm64 using special instructions
Date: Sat, 5 May 2018 15:17:11 +0800 [thread overview]
Message-ID: <20180505071711.r5swugmom3t44kcd@gondor.apana.org.au> (raw)
In-Reply-To: <20180425122046.12695-1-ard.biesheuvel@linaro.org>
On Wed, Apr 25, 2018 at 02:20:44PM +0200, Ard Biesheuvel wrote:
> Patch #1 makes some preparatory changes so the C routines can be used as
> a fallback by other drivers.
>
> Patch #2 implements the SM4 core cipher using the special instructions
> introduced as an optional extension by revision 8.2 of the ARM architecture.
>
> Note that this does not implement cipher+chaining mode combinations as we
> do for AES. This can be added later if desiresd.
>
> Ard Biesheuvel (2):
> crypto: sm4 - export encrypt/decrypt routines to other drivers
> crypto: arm64 - add support for SM4 encryption using special
> instructions
>
> arch/arm64/crypto/Kconfig | 6 ++
> arch/arm64/crypto/Makefile | 3 +
> arch/arm64/crypto/sm4-ce-core.S | 36 ++++++++++
> arch/arm64/crypto/sm4-ce-glue.c | 73 ++++++++++++++++++++
> crypto/sm4_generic.c | 10 +--
> include/crypto/sm4.h | 3 +
> 6 files changed, 127 insertions(+), 4 deletions(-)
> create mode 100644 arch/arm64/crypto/sm4-ce-core.S
> create mode 100644 arch/arm64/crypto/sm4-ce-glue.c
All applied. Thanks.
--
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
WARNING: multiple messages have this Message-ID (diff)
From: herbert@gondor.apana.org.au (Herbert Xu)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] crypto: implement SM4 for arm64 using special instructions
Date: Sat, 5 May 2018 15:17:11 +0800 [thread overview]
Message-ID: <20180505071711.r5swugmom3t44kcd@gondor.apana.org.au> (raw)
In-Reply-To: <20180425122046.12695-1-ard.biesheuvel@linaro.org>
On Wed, Apr 25, 2018 at 02:20:44PM +0200, Ard Biesheuvel wrote:
> Patch #1 makes some preparatory changes so the C routines can be used as
> a fallback by other drivers.
>
> Patch #2 implements the SM4 core cipher using the special instructions
> introduced as an optional extension by revision 8.2 of the ARM architecture.
>
> Note that this does not implement cipher+chaining mode combinations as we
> do for AES. This can be added later if desiresd.
>
> Ard Biesheuvel (2):
> crypto: sm4 - export encrypt/decrypt routines to other drivers
> crypto: arm64 - add support for SM4 encryption using special
> instructions
>
> arch/arm64/crypto/Kconfig | 6 ++
> arch/arm64/crypto/Makefile | 3 +
> arch/arm64/crypto/sm4-ce-core.S | 36 ++++++++++
> arch/arm64/crypto/sm4-ce-glue.c | 73 ++++++++++++++++++++
> crypto/sm4_generic.c | 10 +--
> include/crypto/sm4.h | 3 +
> 6 files changed, 127 insertions(+), 4 deletions(-)
> create mode 100644 arch/arm64/crypto/sm4-ce-core.S
> create mode 100644 arch/arm64/crypto/sm4-ce-glue.c
All applied. Thanks.
--
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
next prev parent reply other threads:[~2018-05-05 7:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-25 12:20 [PATCH 0/2] crypto: implement SM4 for arm64 using special instructions Ard Biesheuvel
2018-04-25 12:20 ` Ard Biesheuvel
2018-04-25 12:20 ` [PATCH 1/2] crypto: sm4 - export encrypt/decrypt routines to other drivers Ard Biesheuvel
2018-04-25 12:20 ` Ard Biesheuvel
2018-04-25 12:23 ` Ard Biesheuvel
2018-04-25 12:23 ` Ard Biesheuvel
2018-04-25 12:47 ` Gilad Ben-Yossef
2018-04-25 12:47 ` Gilad Ben-Yossef
2018-04-25 12:20 ` [PATCH 2/2] crypto: arm64 - add support for SM4 encryption using special instructions Ard Biesheuvel
2018-04-25 12:20 ` Ard Biesheuvel
2018-05-05 7:17 ` Herbert Xu [this message]
2018-05-05 7:17 ` [PATCH 0/2] crypto: implement SM4 for arm64 " Herbert Xu
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=20180505071711.r5swugmom3t44kcd@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=ard.biesheuvel@linaro.org \
--cc=gilad@benyossef.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.