From: Paul Bolle <pebolle@tiscali.nl>
To: "Leonidas S. Barbosa" <leosilva@linux.vnet.ibm.com>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 7/7] Enabling VMX module for PPC64
Date: Thu, 05 Feb 2015 22:58:23 +0100 [thread overview]
Message-ID: <1423173503.32511.16.camel@x220> (raw)
In-Reply-To: <20150205172126.GA15218@bluepex.com>
On Thu, 2015-02-05 at 15:21 -0200, Leonidas S. Barbosa wrote:
> This patch enables VMX module in PPC64.
>
> Signed-off-by: Leonidas S. Barbosa <leosilva@linux.vnet.ibm.com>
> ---
> drivers/crypto/Kconfig | 12 ++++++++++++
> drivers/crypto/Makefile | 1 +
> drivers/crypto/vmx/Kconfig | 9 +++++++++
> drivers/crypto/vmx/Makefile | 21 +++++++++++++++++++++
> 4 files changed, 43 insertions(+)
> create mode 100644 drivers/crypto/vmx/Kconfig
> create mode 100644 drivers/crypto/vmx/Makefile
>
> diff --git a/drivers/crypto/Kconfig b/drivers/crypto/Kconfig
> index 2fb0fdf..979cbff 100644
> --- a/drivers/crypto/Kconfig
> +++ b/drivers/crypto/Kconfig
> @@ -436,4 +436,16 @@ config CRYPTO_DEV_QCE
> hardware. To compile this driver as a module, choose M here. The
> module will be called qcrypto.
>
> +config CRYPTO_DEV_VMX
> + bool "Support for VMX cryptographic acceleration instructions"
> + depends on PPC64
> + default n
> + help
> + Support for VMX cryptographic acceleration instructions.
> +
> +if CRYPTO_DEV_VMX
> + source "drivers/crypto/vmx/Kconfig"
> +endif
> +
> endif # CRYPTO_HW
> +
Unneeded extra line.
> diff --git a/drivers/crypto/Makefile b/drivers/crypto/Makefile
> index 3924f93..20a7127 100644
> --- a/drivers/crypto/Makefile
> +++ b/drivers/crypto/Makefile
> @@ -25,3 +25,4 @@ obj-$(CONFIG_CRYPTO_DEV_TALITOS) += talitos.o
> obj-$(CONFIG_CRYPTO_DEV_UX500) += ux500/
> obj-$(CONFIG_CRYPTO_DEV_QAT) += qat/
> obj-$(CONFIG_CRYPTO_DEV_QCE) += qce/
> +obj-$(CONFIG_CRYPTO_DEV_VMX) += vmx/
> diff --git a/drivers/crypto/vmx/Kconfig b/drivers/crypto/vmx/Kconfig
> new file mode 100644
> index 0000000..6728864
> --- /dev/null
> +++ b/drivers/crypto/vmx/Kconfig
> @@ -0,0 +1,9 @@
> +config CRYPTO_DEV_VMX_ENCRYPT
> + tristate "Encryption acceleration support on P8 CPU"
> + depends on PPC64
The net effect of the "if CRYPTO_DEV_VMX" wrapper round the source-ing
of this file is that CRYPTO_DEV_VMX_ENCRYPT depends on CRYPTO_DEV_VMX.
That makes depending on PPC64 superfluous here. You might as well make
this symbol depend on CRYPTO_DEV_VMX and drop the "if CRYPTO_DEV_VMX"
wrapper.
> + default y
> + help
> + Support for VMX cryptographic acceleration instructions on Power8 CPU.
> + This module supports acceleration for AES and GHASH in hardware. If you
> + choose 'M' here, this module will be called vmx-crypto.
> +
Trailing line of whitespace only.
> diff --git a/drivers/crypto/vmx/Makefile b/drivers/crypto/vmx/Makefile
> new file mode 100644
> index 0000000..8898ce6
> --- /dev/null
> +++ b/drivers/crypto/vmx/Makefile
> @@ -0,0 +1,21 @@
> +obj-$(CONFIG_CRYPTO_DEV_VMX_ENCRYPT) += vmx-crypto.o
> +vmx-crypto-objs := vmx.o aesp8-ppc.o ghashp8-ppc.o aes.o aes_cbc.o aes_ctr.o ghash.o
> +
> +ifeq ($(CONFIG_PPC64),y)
Can this test ever fail?
> +ifeq ($(CONFIG_CPU_LITTLE_ENDIAN),y)
> +TARGET := linux-ppc64le
> +else
> +TARGET := linux-pcc64
> +endif
> +endif
> +
> +quiet_cmd_perl = PERL $@
> + cmd_perl = $(PERL) $(<) $(TARGET) > $(@)
> +
> +$(src)/aesp8-ppc.S: $(src)/aesp8-ppc.pl
> + $(call cmd,perl)
> +
> +$(src)/ghashp8-ppc.S: $(src)/ghashp8-ppc.pl
> + $(call cmd,perl)
> +
> +.PRECIOUS: $(obj)/aesp8-ppc.S $(obj)/ghashp8-ppc.S
Paul Bolle
next prev parent reply other threads:[~2015-02-05 21:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-05 17:21 [PATCH 7/7] Enabling VMX module for PPC64 Leonidas S. Barbosa
2015-02-05 21:58 ` Paul Bolle [this message]
2015-02-06 16:41 ` Leonidas S. Barbosa
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=1423173503.32511.16.camel@x220 \
--to=pebolle@tiscali.nl \
--cc=herbert@gondor.apana.org.au \
--cc=leosilva@linux.vnet.ibm.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@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 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).