diff options
| author | Martin Schwidefsky <schwidefsky@de.ibm.com> | 2016-08-18 13:59:46 +0300 |
|---|---|---|
| committer | Martin Schwidefsky <schwidefsky@de.ibm.com> | 2016-08-29 12:05:09 +0300 |
| commit | 69c0e360f990c2dc737681f40a361195066cef02 (patch) | |
| tree | e5e5ff1ff6f09e21b28752b948283589803d81eb /arch/s390/crypto/ghash_s390.c | |
| parent | d863d5945f2be0abfcd9d36b1a7c605f3eaef517 (diff) | |
| download | linux-69c0e360f990c2dc737681f40a361195066cef02.tar.xz | |
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>
Diffstat (limited to 'arch/s390/crypto/ghash_s390.c')
| -rw-r--r-- | arch/s390/crypto/ghash_s390.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/arch/s390/crypto/ghash_s390.c b/arch/s390/crypto/ghash_s390.c index 8e87f5176799..564616d48d8b 100644 --- a/arch/s390/crypto/ghash_s390.c +++ b/arch/s390/crypto/ghash_s390.c @@ -136,7 +136,7 @@ static struct shash_alg ghash_alg = { static int __init ghash_mod_init(void) { - if (!cpacf_query(CPACF_KIMD, CPACF_KIMD_GHASH)) + if (!cpacf_query_func(CPACF_KIMD, CPACF_KIMD_GHASH)) return -EOPNOTSUPP; return crypto_register_shash(&ghash_alg); |