From: Cornelia Huck <cohuck@redhat.com>
To: Janosch Frank <frankja@linux.ibm.com>
Cc: thuth@redhat.com, david@redhat.com, qemu-devel@nongnu.org,
pasic@linux.ibm.com, borntraeger@de.ibm.com,
qemu-s390x@nongnu.org, mhartmay@linux.ibm.com,
walling@linux.ibm.com
Subject: Re: [PATCH v2 0/2] s390x: pv: Diag318 fixes
Date: Thu, 22 Oct 2020 16:06:18 +0200 [thread overview]
Message-ID: <20201022160618.177e1d76.cohuck@redhat.com> (raw)
In-Reply-To: <20201022103135.126033-1-frankja@linux.ibm.com>
On Thu, 22 Oct 2020 06:31:33 -0400
Janosch Frank <frankja@linux.ibm.com> wrote:
> Here are two fixes for the diag318 support that fix crashes when
> booting PV guests.
>
> We're working on extending our testing to catch problems like these
> earlier.
>
>
> Branch:
> https://gitlab.com/frankja/qemu/-/commits/bb/frankja/diag318_fixes
>
> CI:
> https://gitlab.com/frankja/qemu/-/pipelines/206174979
>
>
> V2:
> * Moved fencing nto cpu model functions
> * Added rev-by and acks
>
>
> Janosch Frank (2):
> s390x: pv: Remove sclp boundary checks
> s390x: pv: Fix diag318 PV fencing
>
> hw/s390x/sclp.c | 5 -----
> target/s390x/cpu_features.c | 5 +++++
> target/s390x/cpu_features.h | 4 ++++
> target/s390x/cpu_models.c | 4 ++++
> target/s390x/kvm.c | 3 +--
> 5 files changed, 14 insertions(+), 7 deletions(-)
>
Thanks, applied.
prev parent reply other threads:[~2020-10-22 14:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-22 10:31 [PATCH v2 0/2] s390x: pv: Diag318 fixes Janosch Frank
2020-10-22 10:31 ` [PATCH v2 1/2] s390x: pv: Remove sclp boundary checks Janosch Frank
2020-10-22 10:31 ` [PATCH v2 2/2] s390x: pv: Fix diag318 PV fencing Janosch Frank
2020-10-22 10:53 ` David Hildenbrand
2020-10-22 11:07 ` Christian Borntraeger
2020-10-22 12:40 ` Marc Hartmayer
2020-10-22 12:50 ` [PATCH v2 0/2] s390x: pv: Diag318 fixes Collin Walling
2020-10-22 14:06 ` Cornelia Huck [this message]
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=20201022160618.177e1d76.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=david@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=mhartmay@linux.ibm.com \
--cc=pasic@linux.ibm.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).