From: Eric Farman <farman@linux.ibm.com>
To: Harald Freudenberger <freude@linux.ibm.com>,
richard.henderson@linaro.org, iii@linux.ibm.com,
david@kernel.org, thuth@redhat.com, berrange@redhat.com
Cc: qemu-s390x@nongnu.org, qemu-devel@nongnu.org,
linux-s390@vger.kernel.org, dengler@linux.ibm.com,
borntraeger@linux.ibm.com, fcallies@linux.ibm.com,
cohuck@redhat.com
Subject: Re: [PATCH v16 06/20] target/s390x: Adjust addressing mode checks for sha512 and sha256
Date: Tue, 25 Aug 2026 06:15:40 -0400 [thread overview]
Message-ID: <09380eca-8da0-4342-9a49-f86842d1a0a0@linux.ibm.com> (raw)
In-Reply-To: <20260824083204.40877-7-freude@linux.ibm.com>
On 8/24/26 4:31 AM, Harald Freudenberger wrote:
> The handling for different addressing modes in the both sha
> implementations cpacf sha256 and sha512 was incomplete. Rework this
> addressing checking to clearly have support for s390 64 bit and 32 bit
> addressing mode but raise an exception otherwise.
>
> Also bail out early (for KIMD only) if length is 0.
>
> Signed-off-by: Harald Freudenberger <freude@linux.ibm.com>
> Suggested-by: Ilya Leoshkevich <iii@linux.ibm.com>
> ---
> target/s390x/tcg/cpacf_sha256.c | 16 +++++++++++++---
> target/s390x/tcg/cpacf_sha512.c | 16 +++++++++++++---
> 2 files changed, 26 insertions(+), 6 deletions(-)
I was going to ask why this wasn't just included in the first place, but
I see that sha512 is pre-existing. So, makes sense this way...
Reviewed-by: Eric Farman <farman@linux.ibm.com>
>
> diff --git a/target/s390x/tcg/cpacf_sha256.c b/target/s390x/tcg/cpacf_sha256.c
> index 67321b565c..de305b6838 100644
> --- a/target/s390x/tcg/cpacf_sha256.c
> +++ b/target/s390x/tcg/cpacf_sha256.c
> @@ -111,14 +111,24 @@ int cpacf_sha256(CPUS390XState *env, const int mmu_idx, uintptr_t ra,
> {
> enum { MAX_BLOCKS_PER_RUN = 128 }; /* 128 * 64 = 8K */
> uint64_t len = *len_reg, processed = 0;
> - int message_reg_len = 64;
> + int message_reg_len;
> uint32_t a[8];
>
> g_assert(type == S390_FEAT_TYPE_KIMD || type == S390_FEAT_TYPE_KLMD);
>
> - if (!(env->psw.mask & PSW_MASK_64)) {
> + /* check addressing mode, raise exception if not supported here */
> + if (env->psw.mask & PSW_MASK_64) {
> + message_reg_len = 64;
> + } else if (env->psw.mask & PSW_MASK_32) {
> + message_reg_len = 32;
> len = (uint32_t)len;
> - message_reg_len = (env->psw.mask & PSW_MASK_32) ? 32 : 24;
> + } else {
> + tcg_s390_program_interrupt(env, PGM_SPECIFICATION, ra);
> + }
> +
> + /* for KIMD only: early bail out if length is zero */
> + if (type == S390_FEAT_TYPE_KIMD && !len) {
> + return 0;
> }
>
> /* KIMD: length has to be properly aligned. */
> diff --git a/target/s390x/tcg/cpacf_sha512.c b/target/s390x/tcg/cpacf_sha512.c
> index edd8dae78f..cad8e0e1bd 100644
> --- a/target/s390x/tcg/cpacf_sha512.c
> +++ b/target/s390x/tcg/cpacf_sha512.c
> @@ -126,13 +126,23 @@ int cpacf_sha512(CPUS390XState *env, const int mmu_idx, uintptr_t ra,
> {
> enum { MAX_BLOCKS_PER_RUN = 64 }; /* Arbitrary: keep interactivity. */
> uint64_t len = *len_reg, a[8], processed = 0;
> - int message_reg_len = 64;
> + int message_reg_len;
>
> g_assert(type == S390_FEAT_TYPE_KIMD || type == S390_FEAT_TYPE_KLMD);
>
> - if (!(env->psw.mask & PSW_MASK_64)) {
> + /* check addressing mode, raise exception if not supported here */
> + if (env->psw.mask & PSW_MASK_64) {
> + message_reg_len = 64;
> + } else if (env->psw.mask & PSW_MASK_32) {
> + message_reg_len = 32;
> len = (uint32_t)len;
> - message_reg_len = (env->psw.mask & PSW_MASK_32) ? 32 : 24;
> + } else {
> + tcg_s390_program_interrupt(env, PGM_SPECIFICATION, ra);
> + }
> +
> + /* for KIMD only: early bail out if length is zero */
> + if (type == S390_FEAT_TYPE_KIMD && !len) {
> + return 0;
> }
>
> /* KIMD: length has to be properly aligned. */
next prev parent reply other threads:[~2026-08-25 10:15 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-24 8:31 [PATCH v16 00/20] Extend qemu CPACF support Harald Freudenberger
2026-08-24 8:31 ` [PATCH v16 01/20] target/s390x: Fix missing privileged flag at PCKMO instruction Harald Freudenberger
2026-08-24 8:31 ` [PATCH v16 02/20] target/s390x: Rework s390 cpacf implementations Harald Freudenberger
2026-08-24 8:31 ` [PATCH v16 03/20] target/s390x: Move cpacf sha512 code into a new file Harald Freudenberger
2026-08-24 8:31 ` [PATCH v16 04/20] target/s390x: Support cpacf sha256 Harald Freudenberger
2026-08-24 8:31 ` [PATCH v16 05/20] target/s390x: Add helper functions for copy memory to and from guest Harald Freudenberger
2026-08-24 8:31 ` [PATCH v16 06/20] target/s390x: Adjust addressing mode checks for sha512 and sha256 Harald Freudenberger
2026-08-25 10:15 ` Eric Farman [this message]
2026-08-24 8:31 ` [PATCH v16 07/20] crypto: Add aes-helpers file to support some AES modes Harald Freudenberger
2026-08-24 8:31 ` [PATCH v16 08/20] target/s390x: Support AES ECB for cpacf km instruction Harald Freudenberger
2026-08-24 8:31 ` [PATCH v16 09/20] target/s390x: Support AES CBC for cpacf kmc instruction Harald Freudenberger
2026-08-24 8:31 ` [PATCH v16 10/20] target/s390x: Support AES CTR for cpacf kmctr instruction Harald Freudenberger
2026-08-24 8:31 ` [PATCH v16 11/20] target/s390x: Minimal AES XTS support for cpacf pcc instruction Harald Freudenberger
2026-08-24 8:31 ` [PATCH v16 12/20] target/s390x: Support AES XTS for cpacf km instruction Harald Freudenberger
2026-08-24 8:31 ` [PATCH v16 13/20] target/s390x: Base support for cpacf protected keys and pckmo Harald Freudenberger
2026-08-24 8:31 ` [PATCH v16 14/20] target/s390x: Support protected key AES ECB for cpacf km instruction Harald Freudenberger
2026-08-24 8:31 ` [PATCH v16 15/20] target/s390x: Support protected key AES CBC for cpacf kmc instruction Harald Freudenberger
2026-08-24 8:32 ` [PATCH v16 16/20] target/s390x: Support protected key AES CTR for cpacf kmctr instruction Harald Freudenberger
2026-08-24 8:32 ` [PATCH v16 17/20] target/s390x: Minimal protected key AES XTS support for cpacf pcc instruction Harald Freudenberger
2026-08-24 8:32 ` [PATCH v16 18/20] target/s390x: Support protected key AES XTS for cpacf km instruction Harald Freudenberger
2026-08-24 8:32 ` [PATCH v16 19/20] docs/s390: Document CPACF instructions support Harald Freudenberger
2026-08-24 8:32 ` [PATCH v16 20/20] tests/tcg/s390x: Add tests for CPACF instructions Harald Freudenberger
2026-09-09 1:00 ` Eric Farman
2026-09-09 14:51 ` [PATCH v16 00/20] Extend qemu CPACF support Eric Farman
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=09380eca-8da0-4342-9a49-f86842d1a0a0@linux.ibm.com \
--to=farman@linux.ibm.com \
--cc=berrange@redhat.com \
--cc=borntraeger@linux.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@kernel.org \
--cc=dengler@linux.ibm.com \
--cc=fcallies@linux.ibm.com \
--cc=freude@linux.ibm.com \
--cc=iii@linux.ibm.com \
--cc=linux-s390@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=thuth@redhat.com \
/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