From: Holger Dengler <dengler@linux.ibm.com>
To: Harald Freudenberger <freude@linux.ibm.com>,
herbert@gondor.apana.org.au, ifranzki@linux.ibm.com,
fcallies@linux.ibm.com
Cc: linux-crypto@vger.kernel.org, linux-s390@vger.kernel.org
Subject: Re: [PATCH v3 1/3] s390/cpacf: Rework cpacf_pcc() to return condition code
Date: Mon, 14 Apr 2025 12:14:55 +0200 [thread overview]
Message-ID: <a6207daa-ad95-4cc0-9d9a-204453dc04cf@linux.ibm.com> (raw)
In-Reply-To: <20250401145048.52564-2-freude@linux.ibm.com>
On 01/04/2025 16:50, Harald Freudenberger wrote:
> Some of the pcc sub-functions have a protected key as
> input and thus may run into the situation that this
> key may be invalid for example due to live guest migration
> to another physical hardware.
>
> Rework the inline assembler function cpacf_pcc() to
> return the condition code (cc) as return value:
> 0 - cc code 0 (normal completion)
> 1 - cc code 1 (prot key wkvp mismatch or src op out of range)
> 2 - cc code 2 (something invalid, scalar multiply infinity, ...)
> Note that cc 3 (partial completion) is handled within the asm code
> and never returned.
>
> Signed-off-by: Harald Freudenberger <freude@linux.ibm.com>
Reviewed-by: Holger Dengler <dengler@linux.ibm.com>
--
Mit freundlichen Grüßen / Kind regards
Holger Dengler
--
IBM Systems, Linux on IBM Z Development
dengler@linux.ibm.com
next prev parent reply other threads:[~2025-04-14 10:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-01 14:50 [PATCH v3 0/3] Rework protected key AES for true asynch support Harald Freudenberger
2025-04-01 14:50 ` [PATCH v3 1/3] s390/cpacf: Rework cpacf_pcc() to return condition code Harald Freudenberger
2025-04-14 10:14 ` Holger Dengler [this message]
2025-04-01 14:50 ` [PATCH v3 2/3] s390/crypto: Rework protected key AES for true asynch support Harald Freudenberger
2025-04-02 4:04 ` Herbert Xu
2025-05-06 14:02 ` Harald Freudenberger
2025-05-07 3:35 ` Herbert Xu
2025-04-25 14:56 ` Holger Dengler
2025-05-06 14:13 ` Harald Freudenberger
2025-04-01 14:50 ` [PATCH v3 3/3] Documentation: crypto_engine: Update and extend crypto engine doc Harald Freudenberger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a6207daa-ad95-4cc0-9d9a-204453dc04cf@linux.ibm.com \
--to=dengler@linux.ibm.com \
--cc=fcallies@linux.ibm.com \
--cc=freude@linux.ibm.com \
--cc=herbert@gondor.apana.org.au \
--cc=ifranzki@linux.ibm.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox