linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Leonidas S. Barbosa" <leosilva@linux.vnet.ibm.com>
To: linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org
Cc: linuxppc-dev@lists.ozlabs.org,
	Herbert Xu <herbert@gondor.apana.org.au>,
	pfsmorigo@linux.vnet.ibm.com,
	Michael Ellerman <mpe@ellerman.id.au>
Subject: [PATCH 0/2] Uncomment VSX enable routine for instructions access
Date: Mon, 13 Jul 2015 13:50:14 -0300	[thread overview]
Message-ID: <20150713165011.GA3356@bluepex.com> (raw)

enable_kernel_vsx() was commented since anything was using
it. It changes with vmx_crypto driver that call VSX instructions
and need kernel_vsx enabled in order to do it properly. Without
a way to enable VSX instruction vmx_crypto fails into an exception.

These patches uncomment enable_kernel_vsx() rountine and put it
available for use. Also adds it in vmx_crypto in order to
enable kernel_vsx before use VSX instructions.

Leonidas S. Barbosa (2):
  Uncomment and make enable_kernel_vsx() routine available
  Adding enable_kernel_vsx() to access VSX instructions

 arch/powerpc/include/asm/switch_to.h | 1 +
 arch/powerpc/kernel/process.c        | 3 ---
 drivers/crypto/vmx/aes.c             | 3 +++
 drivers/crypto/vmx/aes_cbc.c         | 3 +++
 drivers/crypto/vmx/aes_ctr.c         | 3 +++
 drivers/crypto/vmx/ghash.c           | 4 ++++
 6 files changed, 14 insertions(+), 3 deletions(-)

-- 
2.1.0

             reply	other threads:[~2015-07-13 16:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-13 16:50 Leonidas S. Barbosa [this message]
2015-07-14  7:02 ` [PATCH 0/2] Uncomment VSX enable routine for instructions access 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=20150713165011.GA3356@bluepex.com \
    --to=leosilva@linux.vnet.ibm.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.au \
    --cc=pfsmorigo@linux.vnet.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).