From: Pierre Morel <pmorel@linux.ibm.com>
To: Cornelia Huck <cohuck@redhat.com>,
Halil Pasic <pasic@linux.ibm.com>,
Eric Farman <farman@linux.ibm.com>,
Farhan Ali <alifm@linux.ibm.com>
Cc: linux-s390@vger.kernel.org, qemu-s390x@nongnu.org,
Alex Williamson <alex.williamson@redhat.com>,
qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [PATCH 2/2] vfio-ccw: support async command subregion
Date: Fri, 23 Nov 2018 15:13:12 +0100 [thread overview]
Message-ID: <8fbbe0b6-6924-ad61-1d94-26517765f346@linux.ibm.com> (raw)
In-Reply-To: <20181122165457.4517-3-cohuck@redhat.com>
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(-)
>
> diff --git a/hw/s390x/css.c b/hw/s390x/css.c
> index 04ec5cc970..0897c041c5 100644
> --- a/hw/s390x/css.c
> +++ b/hw/s390x/css.c
> @@ -22,6 +22,7 @@
> #include "trace.h"
> #include "hw/s390x/s390_flic.h"
> #include "hw/s390x/s390-virtio-ccw.h"
> +#include "hw/s390x/s390-ccw.h"
>
> typedef struct CrwContainer {
> CRW crw;
> @@ -1194,6 +1195,26 @@ static void sch_handle_start_func_virtual(SubchDev *sch)
>
> }
>
> +static void sch_handle_halt_func_passthrough(SubchDev *sch)
> +{
> + int ret;
> +
> + ret = vfio_ccw_handle_halt(sch);
> + if (ret == -ENOSYS) {
> + sch_handle_halt_func(sch);
> + }
> +}
> +
> +static void sch_handle_clear_func_passthrough(SubchDev *sch)
> +{
> + int ret;
> +
> + ret = vfio_ccw_handle_clear(sch);
> + if (ret == -ENOSYS) {
> + sch_handle_clear_func(sch);
> + }
> +}
> +
> static IOInstEnding sch_handle_start_func_passthrough(SubchDev *sch)
> {
>
> @@ -1237,11 +1258,9 @@ IOInstEnding do_subchannel_work_passthrough(SubchDev *sch)
> SCSW *s = &sch->curr_status.scsw;
>
> if (s->ctrl & SCSW_FCTL_CLEAR_FUNC) {
> - /* TODO: Clear handling */
> - sch_handle_clear_func(sch);
> + sch_handle_clear_func_passthrough(sch);
> } else if (s->ctrl & SCSW_FCTL_HALT_FUNC) {
> - /* TODO: Halt handling */
> - sch_handle_halt_func(sch);
> + sch_handle_halt_func_passthrough(sch);
> } else if (s->ctrl & SCSW_FCTL_START_FUNC) {
> return sch_handle_start_func_passthrough(sch);
> }
> diff --git a/hw/vfio/ccw.c b/hw/vfio/ccw.c
> index 9246729a75..dd0fecf168 100644
> --- a/hw/vfio/ccw.c
> +++ b/hw/vfio/ccw.c
> @@ -2,9 +2,12 @@
> * vfio based subchannel assignment support
> *
> * Copyright 2017 IBM Corp.
> + * Copyright 2018 Red Hat, Inc.
> + *
> * Author(s): Dong Jia Shi <bjsdjshi@linux.vnet.ibm.com>
> * Xiao Feng Ren <renxiaof@linux.vnet.ibm.com>
> * Pierre Morel <pmorel@linux.vnet.ibm.com>
> + * Cornelia Huck <cohuck@redhat.com>
> *
> * This work is licensed under the terms of the GNU GPL, version 2 or (at
> * your option) any later version. See the COPYING file in the top-level
> @@ -32,6 +35,9 @@ typedef struct VFIOCCWDevice {
> uint64_t io_region_size;
> uint64_t io_region_offset;
> struct ccw_io_region *io_region;
> + uint64_t async_cmd_region_size;
> + uint64_t async_cmd_region_offset;
> + struct ccw_cmd_region *async_cmd_region;
> EventNotifier io_notifier;
> bool force_orb_pfch;
> bool warned_orb_pfch;
> @@ -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?
> + goto again;
> + }
> + error_report("vfio-ccw: wirte I/O region failed with errno=%d", errno);
> + ret = -errno;
> + } else {
> + ret = region->ret_code;
> + }
> + switch (ret) {
> + case 0:
> + case -ENODEV:
> + case -EACCES:
should never happen?
> + return 0;
> + case -EFAULT:
> + default:
> + sch_gen_unit_exception(sch);
> + css_inject_io_interrupt(sch);
> + return 0;
> + }
> +}
> +
otherwise LGTM
--
Pierre Morel
Linux/KVM/QEMU in Böblingen - Germany
next prev parent reply other threads:[~2018-11-23 14:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-22 16:54 [PATCH 0/2] vfio-ccw: support hsch/csch (QEMU part) Cornelia Huck
2018-11-22 16:54 ` [PATCH 1/2] vfio-ccw: new capability chain support Cornelia Huck
2018-11-23 14:12 ` Pierre Morel
2018-11-22 16:54 ` [PATCH 2/2] vfio-ccw: support async command subregion Cornelia Huck
2018-11-23 14:13 ` Pierre Morel [this message]
2018-11-26 9:58 ` Cornelia Huck
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=8fbbe0b6-6924-ad61-1d94-26517765f346@linux.ibm.com \
--to=pmorel@linux.ibm.com \
--cc=alex.williamson@redhat.com \
--cc=alifm@linux.ibm.com \
--cc=cohuck@redhat.com \
--cc=farman@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=pasic@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