s390/crypto: cpacf function detection
authorMartin Schwidefsky <schwidefsky@de.ibm.com>
Thu, 18 Aug 2016 10:59:46 +0000 (12:59 +0200)
committerMartin Schwidefsky <schwidefsky@de.ibm.com>
Mon, 29 Aug 2016 09:05:09 +0000 (11:05 +0200)
commit69c0e360f990c2dc737681f40a361195066cef02
treee5e5ff1ff6f09e21b28752b948283589803d81eb
parentd863d5945f2be0abfcd9d36b1a7c605f3eaef517
s390/crypto: cpacf function detection

The CPACF code makes some assumptions about the availablity of hardware
support. E.g. if the machine supports KM(AES-256) without chaining it is
assumed that KMC(AES-256) with chaining is available as well. For the
existing CPUs this is true but the architecturally correct way is to
check each CPACF functions on its own. This is what the query function
of each instructions is all about.

Reviewed-by: Harald Freudenberger <freude@linux.vnet.ibm.com>
Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
arch/s390/crypto/aes_s390.c
arch/s390/crypto/des_s390.c
arch/s390/crypto/ghash_s390.c
arch/s390/crypto/prng.c
arch/s390/crypto/sha1_s390.c
arch/s390/crypto/sha256_s390.c
arch/s390/crypto/sha512_s390.c
arch/s390/include/asm/cpacf.h
arch/s390/kvm/kvm-s390.c