From: Eric Farman <farman@linux.ibm.com>
To: Cornelia Huck <cohuck@redhat.com>,
qemu-devel@nongnu.org, qemu-s390x@nongnu.org
Cc: Thomas Huth <thuth@redhat.com>,
Matthew Rosato <mjrosato@linux.ibm.com>,
David Hildenbrand <david@redhat.com>,
Richard Henderson <richard.henderson@linaro.org>,
Halil Pasic <pasic@linux.ibm.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
Alex Williamson <alex.williamson@redhat.com>
Subject: Re: [PATCH v4 1/4] s390x/css: Introduce an ESW struct
Date: Fri, 18 Jun 2021 08:57:04 -0400 [thread overview]
Message-ID: <2f4b46440d693a1e52d12ef7d95c30261c2dcdbc.camel@linux.ibm.com> (raw)
In-Reply-To: <87czsjpl5i.fsf@redhat.com>
On Fri, 2021-06-18 at 11:38 +0200, Cornelia Huck wrote:
> On Fri, Jun 18 2021, Eric Farman <farman@linux.ibm.com> wrote:
>
> > The Interrupt Response Block is comprised of several other
> > structures concatenated together, but only the 12-byte
> > Subchannel-Status Word (SCSW) is defined as a proper struct.
> > Everything else is a simple array of 32-bit words.
> >
> > Let's define a proper struct for the 20-byte Extended-Status
> > Word (ESW) so that we can make good decisions about the sense
> > data that would go into the ECW area for virtual vs
> > passthrough devices.
> >
> > Signed-off-by: Eric Farman <farman@linux.ibm.com>
> > ---
> > hw/s390x/css.c | 19 +++++++++++++------
> > include/hw/s390x/ioinst.h | 12 +++++++++++-
> > 2 files changed, 24 insertions(+), 7 deletions(-)
>
> (...)
>
> > diff --git a/include/hw/s390x/ioinst.h b/include/hw/s390x/ioinst.h
> > index c6737a30d4..e7ab401781 100644
> > --- a/include/hw/s390x/ioinst.h
> > +++ b/include/hw/s390x/ioinst.h
> > @@ -123,10 +123,20 @@ typedef struct SCHIB {
> > uint8_t mda[4];
> > } QEMU_PACKED SCHIB;
> >
> > +/* format-0 extended-status word */
> > +typedef struct ESW {
> > + uint32_t word0;
>
> Maybe append /* subchannel logout for format 0 */? Can do when
> applying.
>
That's a good idea.
Eric
> > + uint32_t erw;
> > + uint64_t f_addr; /* Zeros for other ESW formats */
> > + uint32_t s_addr; /* Zeros for other ESW formats */
> > +} QEMU_PACKED ESW;
> > +
> > +#define ESW_ERW_SENSE 0x01000000
> > +
> > /* interruption response block */
> > typedef struct IRB {
> > SCSW scsw;
> > - uint32_t esw[5];
> > + ESW esw;
> > uint32_t ecw[8];
> > uint32_t emw[8];
> > } IRB;
next prev parent reply other threads:[~2021-06-18 12:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-17 23:25 [PATCH v4 0/4] s390x: Fix IRB sense data Eric Farman
2021-06-17 23:25 ` [PATCH v4 1/4] s390x/css: Introduce an ESW struct Eric Farman
2021-06-18 9:38 ` Cornelia Huck
2021-06-18 12:57 ` Eric Farman [this message]
2021-06-18 11:04 ` Cornelia Huck
2021-06-18 12:46 ` Cornelia Huck
2021-06-18 12:55 ` Eric Farman
2021-06-18 13:11 ` Cornelia Huck
2021-07-06 9:39 ` Philippe Mathieu-Daudé
2021-06-17 23:25 ` [PATCH v4 2/4] s390x/css: Split out the IRB sense data Eric Farman
2021-06-17 23:25 ` [PATCH v4 3/4] s390x/css: Refactor IRB construction Eric Farman
2021-06-17 23:25 ` [PATCH v4 4/4] s390x/css: Add passthrough IRB Eric Farman
2021-06-18 9:42 ` [PATCH v4 0/4] s390x: Fix IRB sense data Cornelia Huck
2021-06-18 15:27 ` Cornelia Huck
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=2f4b46440d693a1e52d12ef7d95c30261c2dcdbc.camel@linux.ibm.com \
--to=farman@linux.ibm.com \
--cc=alex.williamson@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=mjrosato@linux.ibm.com \
--cc=pasic@linux.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=richard.henderson@linaro.org \
--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 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).