diff options
| author |   Martin Schwidefsky <schwidefsky@de.ibm.com> | 2016-08-18 12:59:46 +0200 |
|---|---|---|
| committer | Martin Schwidefsky <schwidefsky@de.ibm.com> | 2016-08-29 11:05:09 +0200 |
| commit | 69c0e360f990c2dc737681f40a361195066cef02 (patch) | |
| tree | e5e5ff1ff6f09e21b28752b948283589803d81eb /arch/s390/crypto/sha512_s390.c | |
| parent | s390/crypto: simplify init / exit functions (diff) | |
| download | linux-dev-69c0e360f990c2dc737681f40a361195066cef02.tar.xz linux-dev-69c0e360f990c2dc737681f40a361195066cef02.zip | |
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/sha512_s390.c')
| -rw-r--r-- | arch/s390/crypto/sha512_s390.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/arch/s390/crypto/sha512_s390.c b/arch/s390/crypto/sha512_s390.c index ea85757be407..2f4caa1ef123 100644 --- a/arch/s390/crypto/sha512_s390.c +++ b/arch/s390/crypto/sha512_s390.c @@ -133,7 +133,7 @@ static int __init init(void) { int ret; - if (!cpacf_query(CPACF_KIMD, CPACF_KIMD_SHA_512)) + if (!cpacf_query_func(CPACF_KIMD, CPACF_KIMD_SHA_512)) return -EOPNOTSUPP; if ((ret = crypto_register_shash(&sha512_alg)) < 0) goto out; |