From: Eric Farman <farman@linux.ibm.com>
To: Alex Williamson <alex.williamson@redhat.com>,
Cornelia Huck <cohuck@redhat.com>
Cc: Kirti Wankhede <kwankhede@nvidia.com>,
Halil Pasic <pasic@linux.ibm.com>,
Matthew Rosato <mjrosato@linux.ibm.com>,
linux-s390@vger.kernel.org, kvm@vger.kernel.org,
Eric Farman <farman@linux.ibm.com>
Subject: [PATCH v3 0/2] Connect request callback to mdev and vfio-ccw
Date: Thu, 3 Dec 2020 22:35:10 +0100 [thread overview]
Message-ID: <20201203213512.49357-1-farman@linux.ibm.com> (raw)
Alex,
As promised, here is a v3 with a message indicating a request is blocked
until a user releases the device in question and a corresponding tweak to
the commit message describing this change (and Conny's r-b). The remainder
of the patches are otherwise identical.
v2 : https://lore.kernel.org/kvm/20201120180740.87837-1-farman@linux.ibm.com/
v1(RFC) : https://lore.kernel.org/kvm/20201117032139.50988-1-farman@linux.ibm.com/
Eric Farman (2):
vfio-mdev: Wire in a request handler for mdev parent
vfio-ccw: Wire in the request callback
drivers/s390/cio/vfio_ccw_ops.c | 26 ++++++++++++++++++++++++++
drivers/s390/cio/vfio_ccw_private.h | 4 ++++
drivers/vfio/mdev/mdev_core.c | 4 ++++
drivers/vfio/mdev/vfio_mdev.c | 13 +++++++++++++
include/linux/mdev.h | 4 ++++
include/uapi/linux/vfio.h | 1 +
6 files changed, 52 insertions(+)
--
2.17.1
next reply other threads:[~2020-12-03 21:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-03 21:35 Eric Farman [this message]
2020-12-03 21:35 ` [PATCH v3 1/2] vfio-mdev: Wire in a request handler for mdev parent Eric Farman
2020-12-03 21:35 ` [PATCH v3 2/2] vfio-ccw: Wire in the request callback Eric Farman
2020-12-03 23:48 ` [PATCH v3 0/2] Connect request callback to mdev and vfio-ccw Alex Williamson
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=20201203213512.49357-1-farman@linux.ibm.com \
--to=farman@linux.ibm.com \
--cc=alex.williamson@redhat.com \
--cc=cohuck@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=kwankhede@nvidia.com \
--cc=linux-s390@vger.kernel.org \
--cc=mjrosato@linux.ibm.com \
--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