From: Cornelia Huck <cohuck@redhat.com>
To: Claudio Imbrenda <imbrenda@linux.vnet.ibm.com>
Cc: qemu-s390x@nongnu.org, qemu-devel@nongnu.org, borntraeger@de.ibm.com
Subject: Re: [Qemu-devel] [PATCH v1 0/3] s390x/sclp: 64 bit event masks
Date: Wed, 21 Feb 2018 16:36:25 +0100 [thread overview]
Message-ID: <20180221163625.69dfe7de.cohuck@redhat.com> (raw)
In-Reply-To: <1519152302-19079-1-git-send-email-imbrenda@linux.vnet.ibm.com>
On Tue, 20 Feb 2018 19:44:59 +0100
Claudio Imbrenda <imbrenda@linux.vnet.ibm.com> wrote:
> Until 67915de9f0383ccf4a ("s390x/event-facility: variable-length event masks")
> we only supported 32bit sclp event masks, even though the archiecture
> allows the guests to set up sclp event masks up to 1021 bytes in length.
> With that patch the behaviour was almost compliant, but some issues were
> still remaining, in particular regarding the handling of selective reads
> and migration.
>
> This patchset fixes migration and the handling of selective reads, and
> puts in place the support for 64-bit sclp event masks internally.
>
> A new property of the sclp-event device switches between the 32bit masks
> and the compliant behaviour. The property is bound to the machine
> version, so older machines keep the old broken behaviour, allowing for
> migration, but the default is the compliant implementation.
>
> Fixes: 67915de9f0383ccf4a ("s390x/event-facility: variable-length event masks")
>
> Claudio Imbrenda (3):
> s390x/sclp: proper support of larger send and receive masks
> s390x/sclp: clean up sclp masks
> s390x/sclp: extend SCLP event masks to 64 bits
>
> hw/char/sclpconsole-lm.c | 4 +-
> hw/char/sclpconsole.c | 4 +-
> hw/s390x/event-facility.c | 147 +++++++++++++++++++++++++++++++-------
> hw/s390x/s390-virtio-ccw.c | 8 ++-
> hw/s390x/sclpcpu.c | 4 +-
> hw/s390x/sclpquiesce.c | 4 +-
> include/hw/s390x/event-facility.h | 22 +++---
> 7 files changed, 149 insertions(+), 44 deletions(-)
>
I can't review the architecture details without documentation
obviously, so another question: Do you have a test you can share? :)
prev parent reply other threads:[~2018-02-21 15:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-20 18:44 [Qemu-devel] [PATCH v1 0/3] s390x/sclp: 64 bit event masks Claudio Imbrenda
2018-02-20 18:45 ` [Qemu-devel] [PATCH v1 1/3] s390x/sclp: proper support of larger send and receive masks Claudio Imbrenda
2018-02-21 15:12 ` Cornelia Huck
2018-02-21 16:28 ` Claudio Imbrenda
2018-02-21 17:06 ` Cornelia Huck
2018-02-22 9:29 ` Claudio Imbrenda
2018-02-20 18:45 ` [Qemu-devel] [PATCH v1 2/3] s390x/sclp: clean up sclp masks Claudio Imbrenda
2018-02-21 15:20 ` Cornelia Huck
2018-02-21 16:42 ` Claudio Imbrenda
2018-02-21 17:30 ` Cornelia Huck
2018-02-22 9:29 ` Claudio Imbrenda
2018-02-20 18:45 ` [Qemu-devel] [PATCH v1 3/3] s390x/sclp: extend SCLP event masks to 64 bits Claudio Imbrenda
2018-02-21 15:34 ` Cornelia Huck
2018-02-21 16:51 ` Claudio Imbrenda
2018-02-21 17:33 ` Cornelia Huck
2018-02-21 15:36 ` 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=20180221163625.69dfe7de.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=imbrenda@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.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;
as well as URLs for NNTP newsgroup(s).