All of lore.kernel.org
 help / color / mirror / Atom feed
From: Janosch Frank <frankja@linux.ibm.com>
To: Gautam Gala <ggala@linux.ibm.com>,
	qemu-s390x@nongnu.org, qemu-devel@nongnu.org
Cc: Christian Borntraeger <borntraeger@linux.ibm.com>,
	Thomas Huth <thuth@redhat.com>,
	Steffen Eiden <seiden@linux.ibm.com>
Subject: Re: [PATCH v4 3/3] target/s390x: Return UVC cmd code, RC and RRC value when DIAG 308 Subcode 10 fails to enter secure mode
Date: Tue, 22 Apr 2025 15:17:41 +0200	[thread overview]
Message-ID: <7d812276-9f93-4fbd-90d4-b5d1cdd8c63b@linux.ibm.com> (raw)
In-Reply-To: <20250417123756.729132-4-ggala@linux.ibm.com>

On 4/17/25 2:37 PM, Gautam Gala wrote:
> Extend DIAG308 subcode 10 to return the UVC RC, RRC and command code
> in bit positions 32-47, 16-31, and 0-15 of register R1 + 1 if the
> function does not complete successfully (in addition to the
> previously returned diag response code in bit position 47-63).
> 
> Signed-off-by: Gautam Gala <ggala@linux.ibm.com>
> ---

[...]

> +void s390_pv_inject_reset_error(CPUState *cs,
> +                                struct S390PVResponse pv_resp)
>   {
>       int r1 = (cs->kvm_run->s390_sieic.ipa & 0x00f0) >> 4;
>       CPUS390XState *env = &S390_CPU(cs)->env;
>   
> +    union {
> +        struct {
> +            uint16_t pv_cmd;
> +            uint16_t pv_rrc;
> +            uint16_t pv_rc;
> +            uint16_t diag_rc;
> +        };
> +        uint64_t regs;
> +    } resp = {.pv_cmd = pv_resp.cmd,
> +              .pv_rrc = pv_resp.rrc,
> +              .pv_rc = pv_resp.rc,
> +              .diag_rc = DIAG_308_RC_INVAL_FOR_PV};
> +

@Thomas: Is the formatting of the assignments correct or should there be 
no assignment on lines containing "{}"?

Checkpatch is happy, though personally I find it hard to read.

Once that's clear or fixed:
Reviewed-by: Janosch Frank <frankja@linux.ibm.com>




  reply	other threads:[~2025-04-22 13:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-17 12:37 [PATCH v4 0/3] DIAG 308: extend subcode 10 to return UVC cmd id, RC and RRC values upon failure to enter secure mode Gautam Gala
2025-04-17 12:37 ` [PATCH v4 1/3] target/s390x: Introduce constant when checking if PV header couldn't be decrypted Gautam Gala
2025-04-22 13:12   ` Janosch Frank
2025-04-17 12:37 ` [PATCH v4 2/3] target/s390x: Introduce function when exiting PV Gautam Gala
2025-04-22 13:13   ` Janosch Frank
2025-04-25  9:41   ` Thomas Huth
2025-04-17 12:37 ` [PATCH v4 3/3] target/s390x: Return UVC cmd code, RC and RRC value when DIAG 308 Subcode 10 fails to enter secure mode Gautam Gala
2025-04-22 13:17   ` Janosch Frank [this message]
2025-04-22 15:09     ` Thomas Huth

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=7d812276-9f93-4fbd-90d4-b5d1cdd8c63b@linux.ibm.com \
    --to=frankja@linux.ibm.com \
    --cc=borntraeger@linux.ibm.com \
    --cc=ggala@linux.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-s390x@nongnu.org \
    --cc=seiden@linux.ibm.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.