linux-kernel - [PATCH 0/2] Uncomment VSX enable routine for instructions access

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 13 Jul 2015 13:50:14 -0300
From:	"Leonidas S. Barbosa" <leosilva@...ux.vnet.ibm.com>
To:	linux-kernel@...r.kernel.org, linux-crypto@...r.kernel.org
Cc:	linuxppc-dev@...ts.ozlabs.org,
	Herbert Xu <herbert@...dor.apana.org.au>,
	pfsmorigo@...ux.vnet.ibm.com, Michael Ellerman <mpe@...erman.id.au>
Subject: [PATCH 0/2] Uncomment VSX enable routine for instructions access

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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/