Home
last modified time | relevance | path

Searched hist:"0177 db01adf26cf9c5dfe1feaf17087de4b9e40e" (Results 1 – 6 of 6) sorted by relevance

/openbmc/linux/arch/s390/crypto/
H A Dsha_common.cdiff 0177db01adf26cf9c5dfe1feaf17087de4b9e40e Mon Aug 15 03:41:52 CDT 2016 Martin Schwidefsky <schwidefsky@de.ibm.com> s390/crypto: simplify return code handling

The CPACF instructions can complete with three different condition codes:
CC=0 for successful completion, CC=1 if the protected key verification
failed, and CC=3 for partial completion.

The inline functions will restart the CPACF instruction for partial
completion, this removes the CC=3 case. The CC=1 case is only relevant
for the protected key functions of the KM, KMC, KMAC and KMCTR
instructions. As the protected key functions are not used by the
current code, there is no need for any kind of return code handling.

Reviewed-by: Harald Freudenberger <freude@linux.vnet.ibm.com>
Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
H A Dghash_s390.cdiff 0177db01adf26cf9c5dfe1feaf17087de4b9e40e Mon Aug 15 03:41:52 CDT 2016 Martin Schwidefsky <schwidefsky@de.ibm.com> s390/crypto: simplify return code handling

The CPACF instructions can complete with three different condition codes:
CC=0 for successful completion, CC=1 if the protected key verification
failed, and CC=3 for partial completion.

The inline functions will restart the CPACF instruction for partial
completion, this removes the CC=3 case. The CC=1 case is only relevant
for the protected key functions of the KM, KMC, KMAC and KMCTR
instructions. As the protected key functions are not used by the
current code, there is no need for any kind of return code handling.

Reviewed-by: Harald Freudenberger <freude@linux.vnet.ibm.com>
Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
H A Ddes_s390.cdiff 0177db01adf26cf9c5dfe1feaf17087de4b9e40e Mon Aug 15 03:41:52 CDT 2016 Martin Schwidefsky <schwidefsky@de.ibm.com> s390/crypto: simplify return code handling

The CPACF instructions can complete with three different condition codes:
CC=0 for successful completion, CC=1 if the protected key verification
failed, and CC=3 for partial completion.

The inline functions will restart the CPACF instruction for partial
completion, this removes the CC=3 case. The CC=1 case is only relevant
for the protected key functions of the KM, KMC, KMAC and KMCTR
instructions. As the protected key functions are not used by the
current code, there is no need for any kind of return code handling.

Reviewed-by: Harald Freudenberger <freude@linux.vnet.ibm.com>
Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
H A Dprng.cdiff 0177db01adf26cf9c5dfe1feaf17087de4b9e40e Mon Aug 15 03:41:52 CDT 2016 Martin Schwidefsky <schwidefsky@de.ibm.com> s390/crypto: simplify return code handling

The CPACF instructions can complete with three different condition codes:
CC=0 for successful completion, CC=1 if the protected key verification
failed, and CC=3 for partial completion.

The inline functions will restart the CPACF instruction for partial
completion, this removes the CC=3 case. The CC=1 case is only relevant
for the protected key functions of the KM, KMC, KMAC and KMCTR
instructions. As the protected key functions are not used by the
current code, there is no need for any kind of return code handling.

Reviewed-by: Harald Freudenberger <freude@linux.vnet.ibm.com>
Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
H A Daes_s390.cdiff 0177db01adf26cf9c5dfe1feaf17087de4b9e40e Mon Aug 15 03:41:52 CDT 2016 Martin Schwidefsky <schwidefsky@de.ibm.com> s390/crypto: simplify return code handling

The CPACF instructions can complete with three different condition codes:
CC=0 for successful completion, CC=1 if the protected key verification
failed, and CC=3 for partial completion.

The inline functions will restart the CPACF instruction for partial
completion, this removes the CC=3 case. The CC=1 case is only relevant
for the protected key functions of the KM, KMC, KMAC and KMCTR
instructions. As the protected key functions are not used by the
current code, there is no need for any kind of return code handling.

Reviewed-by: Harald Freudenberger <freude@linux.vnet.ibm.com>
Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
/openbmc/linux/arch/s390/include/asm/
H A Dcpacf.hdiff 0177db01adf26cf9c5dfe1feaf17087de4b9e40e Mon Aug 15 03:41:52 CDT 2016 Martin Schwidefsky <schwidefsky@de.ibm.com> s390/crypto: simplify return code handling

The CPACF instructions can complete with three different condition codes:
CC=0 for successful completion, CC=1 if the protected key verification
failed, and CC=3 for partial completion.

The inline functions will restart the CPACF instruction for partial
completion, this removes the CC=3 case. The CC=1 case is only relevant
for the protected key functions of the KM, KMC, KMAC and KMCTR
instructions. As the protected key functions are not used by the
current code, there is no need for any kind of return code handling.

Reviewed-by: Harald Freudenberger <freude@linux.vnet.ibm.com>
Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>