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 v2 0/3] s390x/sclp: 64 bit event masks
Date: Fri, 23 Feb 2018 11:37:55 +0100 [thread overview]
Message-ID: <20180223113755.6528b741.cohuck@redhat.com> (raw)
In-Reply-To: <1519316579-7162-1-git-send-email-imbrenda@linux.vnet.ibm.com>
On Thu, 22 Feb 2018 17:22:56 +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")
>
> v1 -> v2
> * improved comments and patch descriptions to better explain why we need
> this, including better description of the old broken behaviour
> * rename SCLPEVMSK to SCLP_EVMASK to improve readability
> * removed some unneded variable initializations
> * fixed a pre-existing typo
>
> 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 | 150 +++++++++++++++++++++++++++++++-------
> 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, 151 insertions(+), 45 deletions(-)
>
This looks sane as far as I can see without having access to the
documentation.
BTW, I saw you also extended the masks in the Linux (guest) code (at
least, I see patches queued on the s390 features branch...) You also
might want to adjust the "Linux uses 4 byte masks" comment in the code
in the future.
Before I queue this, I'd like some r-bs/a-bs by folks with access to
the documentation.
next prev parent reply other threads:[~2018-02-23 10:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-22 16:22 [Qemu-devel] [PATCH v2 0/3] s390x/sclp: 64 bit event masks Claudio Imbrenda
2018-02-22 16:22 ` [Qemu-devel] [PATCH v2 1/3] s390x/sclp: proper support of larger send and receive masks Claudio Imbrenda
2018-02-23 10:31 ` Cornelia Huck
2018-02-23 11:18 ` Claudio Imbrenda
2018-02-22 16:22 ` [Qemu-devel] [PATCH v2 2/3] s390x/sclp: clean up sclp masks Claudio Imbrenda
2018-02-22 16:22 ` [Qemu-devel] [PATCH v2 3/3] s390x/sclp: extend SCLP event masks to 64 bits Claudio Imbrenda
2018-02-23 10:37 ` Cornelia Huck [this message]
2018-02-23 11:19 ` [Qemu-devel] [PATCH v2 0/3] s390x/sclp: 64 bit event masks Claudio Imbrenda
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=20180223113755.6528b741.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).