From: Cornelia Huck <cohuck@redhat.com>
To: Pierre Morel <pmorel@linux.ibm.com>
Cc: Halil Pasic <pasic@linux.ibm.com>,
Eric Farman <farman@linux.ibm.com>,
Farhan Ali <alifm@linux.ibm.com>,
linux-s390@vger.kernel.org, kvm@vger.kernel.org,
qemu-s390x@nongnu.org, qemu-devel@nongnu.org,
Alex Williamson <alex.williamson@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 2/2] vfio-ccw: support async command subregion
Date: Mon, 26 Nov 2018 10:58:43 +0100 [thread overview]
Message-ID: <20181126105843.2efa2d06.cohuck@redhat.com> (raw)
In-Reply-To: <8fbbe0b6-6924-ad61-1d94-26517765f346@linux.ibm.com>
On Fri, 23 Nov 2018 15:13:12 +0100
Pierre Morel <pmorel@linux.ibm.com> wrote:
> On 22/11/2018 17:54, Cornelia Huck wrote:
> > A vfio-ccw device may provide an async command subregion for
> > issuing halt/clear subchannel requests. If it is present, use
> > it for sending halt/clear request to the device; if not, fall
> > back to emulation (as done today).
> >
> > Signed-off-by: Cornelia Huck <cohuck@redhat.com>
> > ---
> > hw/s390x/css.c | 27 +++++++--
> > hw/vfio/ccw.c | 109 +++++++++++++++++++++++++++++++++++-
> > include/hw/s390x/s390-ccw.h | 3 +
> > 3 files changed, 133 insertions(+), 6 deletions(-)
> >
> > @@ -114,6 +120,87 @@ again:
> > }
> > }
> >
> > +int vfio_ccw_handle_clear(SubchDev *sch)
> > +{
> > + S390CCWDevice *cdev = sch->driver_data;
> > + VFIOCCWDevice *vcdev = DO_UPCAST(VFIOCCWDevice, cdev, cdev);
> > + struct ccw_cmd_region *region = vcdev->async_cmd_region;
> > + int ret;
> > +
> > + if (!vcdev->async_cmd_region) {
> > + /* Async command region not available, fall back to emulation */
> > + return -ENOSYS;
> > + }
> > +
> > + memset(region, 0, sizeof(*region));
> > + region->command = VFIO_CCW_ASYNC_CMD_CSCH;
> > +
> > +again:
> > + ret = pwrite(vcdev->vdev.fd, region,
> > + vcdev->async_cmd_region_size, vcdev->async_cmd_region_offset);
> > + if (ret != vcdev->async_cmd_region_size) {
> > + if (errno == EAGAIN) {
>
>
> Where do the EAGAIN come from?
It might be set by pwrite.
>
>
> > + goto again;
> > + }
> > + error_report("vfio-ccw: wirte I/O region failed with errno=%d", errno);
I should also fix up this message here and for hsch as well :)
> > + ret = -errno;
> > + } else {
> > + ret = region->ret_code;
> > + }
> > + switch (ret) {
> > + case 0:
> > + case -ENODEV:
> > + case -EACCES:
>
> should never happen?
It should not happen; but it can nevertheless be returned, so...
>
> > + return 0;
> > + case -EFAULT:
> > + default:
> > + sch_gen_unit_exception(sch);
> > + css_inject_io_interrupt(sch);
> > + return 0;
> > + }
> > +}
> > +
>
> otherwise LGTM
Thanks!
next prev parent reply other threads:[~2018-11-26 9:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-22 16:54 [Qemu-devel] [PATCH 0/2] vfio-ccw: support hsch/csch (QEMU part) Cornelia Huck
2018-11-22 16:54 ` [Qemu-devel] [PATCH 1/2] vfio-ccw: new capability chain support Cornelia Huck
2018-11-23 14:12 ` Pierre Morel
2018-11-22 16:54 ` [Qemu-devel] [PATCH 2/2] vfio-ccw: support async command subregion Cornelia Huck
2018-11-23 14:13 ` Pierre Morel
2018-11-26 9:58 ` Cornelia Huck [this message]
2018-11-26 18:01 ` Pierre Morel
2018-11-26 18:07 ` 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=20181126105843.2efa2d06.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=alifm@linux.ibm.com \
--cc=farman@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=pasic@linux.ibm.com \
--cc=pmorel@linux.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).