public inbox for linux-s390@vger.kernel.org
 help / color / mirror / Atom feed
From: Cornelia Huck <cohuck@redhat.com>
To: Eric Farman <farman@linux.ibm.com>
Cc: Kirti Wankhede <kwankhede@nvidia.com>,
	Alex Williamson <alex.williamson@redhat.com>,
	Halil Pasic <pasic@linux.ibm.com>,
	linux-s390@vger.kernel.org, kvm@vger.kernel.org
Subject: Re: [RFC PATCH 2/2] vfio-ccw: Wire in the request callback
Date: Thu, 19 Nov 2020 12:43:26 +0100	[thread overview]
Message-ID: <20201119124326.0345a353.cohuck@redhat.com> (raw)
In-Reply-To: <20201117032139.50988-3-farman@linux.ibm.com>

On Tue, 17 Nov 2020 04:21:39 +0100
Eric Farman <farman@linux.ibm.com> wrote:

> The device is being unplugged, so pass the request to userspace to
> ask for a graceful cleanup. This should free up the thread that
> would otherwise loop waiting for the device to be fully released.
> 
> Signed-off-by: Eric Farman <farman@linux.ibm.com>
> ---
>  drivers/s390/cio/vfio_ccw_ops.c     | 26 ++++++++++++++++++++++++++
>  drivers/s390/cio/vfio_ccw_private.h |  4 ++++
>  include/uapi/linux/vfio.h           |  1 +
>  3 files changed, 31 insertions(+)
> 

(...)

> @@ -607,6 +611,27 @@ static ssize_t vfio_ccw_mdev_ioctl(struct mdev_device *mdev,
>  	}
>  }
>  
> +/* Request removal of the device*/
> +static void vfio_ccw_mdev_request(struct mdev_device *mdev, unsigned int count)
> +{
> +	struct vfio_ccw_private *private = dev_get_drvdata(mdev_parent_dev(mdev));
> +
> +	if (!private)
> +		return;
> +
> +	if (private->req_trigger) {
> +		if (!(count % 10))
> +			dev_notice_ratelimited(mdev_dev(private->mdev),
> +					       "Relaying device request to user (#%u)\n",
> +					       count);
> +
> +		eventfd_signal(private->req_trigger, 1);
> +	} else if (count == 0) {
> +		dev_notice(mdev_dev(private->mdev),
> +			   "No device request channel registered, blocked until released by user\n");
> +	}
> +}

This looks like the vfio-pci request handler, so probably good :)

Still have to read up on the QEMU side, but a LGTM for now.

  reply	other threads:[~2020-11-19 11:43 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-17  3:21 [RFC PATCH 0/2] Connect request callback to mdev and vfio-ccw Eric Farman
2020-11-17  3:21 ` [RFC PATCH 1/2] vfio-mdev: Wire in a request handler for mdev parent Eric Farman
2020-11-19 11:30   ` Cornelia Huck
2020-11-19 14:36     ` Eric Farman
2020-11-19 15:56     ` Halil Pasic
2020-11-20 11:17       ` Cornelia Huck
2020-11-23 19:12       ` Tony Krowiak
2020-11-19 16:27     ` Alex Williamson
2020-11-19 20:04       ` Eric Farman
2020-11-20 11:22         ` Cornelia Huck
2020-11-19 15:29   ` Halil Pasic
2020-11-17  3:21 ` [RFC PATCH 2/2] vfio-ccw: Wire in the request callback Eric Farman
2020-11-19 11:43   ` Cornelia Huck [this message]
2020-11-19 12:00     ` 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=20201119124326.0345a353.cohuck@redhat.com \
    --to=cohuck@redhat.com \
    --cc=alex.williamson@redhat.com \
    --cc=farman@linux.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=kwankhede@nvidia.com \
    --cc=linux-s390@vger.kernel.org \
    --cc=pasic@linux.ibm.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