From: Janosch Frank <frankja@linux.ibm.com>
To: Collin Walling <walling@linux.ibm.com>,
qemu-s390x@nongnu.org, qemu-devel@nongnu.org
Cc: borntraeger@de.ibm.com, thuth@redhat.com, cohuck@redhat.com,
david@redhat.com
Subject: Re: [PATCH v3] s390: kvm: adjust diag318 resets to retain data
Date: Wed, 10 Nov 2021 13:42:06 +0100 [thread overview]
Message-ID: <695c3358-54e1-e7ea-76fc-14a2ca91eee1@linux.ibm.com> (raw)
In-Reply-To: <20211109205602.99732-1-walling@linux.ibm.com>
On 11/9/21 21:56, Collin Walling wrote:
> The CPNC portion of the diag 318 data is erroneously reset during an
> initial CPU reset caused by SIGP. Let's go ahead and relocate the
> diag318_info field within the CPUS390XState struct such that it is
> only zeroed during a clear reset. This way, the CPNC will be retained
> for each VCPU in the configuration after the diag 318 instruction
> has been invoked.
I'd add something like:
The s390 machine reset code takes care of zeroing the diag318 data on VM
resets which also cover resets caused by diag308.
>
> Signed-off-by: Collin Walling <walling@linux.ibm.com>
> Fixes: fabdada9357b ("s390: guest support for diagnose 0x318")
> Reported-by: Christian Borntraeger <borntraeger@de.ibm.com>
> ---
Reviewed-by: Janosch Frank <frankja@linux.ibm.com>
>
> Changelog:
>
> v2
> - handler uses run_on_cpu again
> - reworded commit message slightly
> - added fixes and reported-by tags
>
> v3
> - nixed code reduction changes
> - added a comment to diag318 handler to briefly describe
> when relevent data is zeroed
>
> ---
> target/s390x/cpu.h | 4 ++--
> target/s390x/kvm/kvm.c | 4 ++++
> 2 files changed, 6 insertions(+), 2 deletions(-)
>
> diff --git a/target/s390x/cpu.h b/target/s390x/cpu.h
> index 3153d053e9..88aace36ff 100644
> --- a/target/s390x/cpu.h
> +++ b/target/s390x/cpu.h
> @@ -63,6 +63,8 @@ struct CPUS390XState {
> uint64_t etoken; /* etoken */
> uint64_t etoken_extension; /* etoken extension */
>
> + uint64_t diag318_info;
> +
> /* Fields up to this point are not cleared by initial CPU reset */
> struct {} start_initial_reset_fields;
>
> @@ -118,8 +120,6 @@ struct CPUS390XState {
> uint16_t external_call_addr;
> DECLARE_BITMAP(emergency_signals, S390_MAX_CPUS);
>
> - uint64_t diag318_info;
> -
> #if !defined(CONFIG_USER_ONLY)
> uint64_t tlb_fill_tec; /* translation exception code during tlb_fill */
> int tlb_fill_exc; /* exception number seen during tlb_fill */
> diff --git a/target/s390x/kvm/kvm.c b/target/s390x/kvm/kvm.c
> index 5b1fdb55c4..6acf14d5ec 100644
> --- a/target/s390x/kvm/kvm.c
> +++ b/target/s390x/kvm/kvm.c
> @@ -1585,6 +1585,10 @@ void kvm_s390_set_diag318(CPUState *cs, uint64_t diag318_info)
> env->diag318_info = diag318_info;
> cs->kvm_run->s.regs.diag318 = diag318_info;
> cs->kvm_run->kvm_dirty_regs |= KVM_SYNC_DIAG318;
> + /*
> + * diag 318 info is zeroed during a clear reset and
> + * diag 308 IPL subcodes.
> + */
> }
> }
>
>
next prev parent reply other threads:[~2021-11-10 12:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-09 20:56 [PATCH v3] s390: kvm: adjust diag318 resets to retain data Collin Walling
2021-11-10 12:42 ` Janosch Frank [this message]
2021-11-11 7:33 ` Collin Walling
2021-11-17 7:43 ` Christian Borntraeger
2021-11-17 15:23 ` Collin Walling
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=695c3358-54e1-e7ea-76fc-14a2ca91eee1@linux.ibm.com \
--to=frankja@linux.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=thuth@redhat.com \
--cc=walling@linux.ibm.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;
as well as URLs for NNTP newsgroup(s).