From: Matthew Rosato <mjrosato@linux.ibm.com>
To: jgg@nvidia.com, alex.williamson@redhat.com
Cc: cohuck@redhat.com, borntraeger@linux.ibm.com,
jjherne@linux.ibm.com, akrowiak@linux.ibm.com,
pasic@linux.ibm.com, zhenyuw@linux.intel.com,
zhi.a.wang@intel.com, hch@infradead.org,
intel-gfx@lists.freedesktop.org,
intel-gvt-dev@lists.freedesktop.org, linux-s390@vger.kernel.org,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/1] vfio: remove VFIO_GROUP_NOTIFY_SET_KVM
Date: Tue, 17 May 2022 14:08:50 -0400 [thread overview]
Message-ID: <20220517180851.166538-1-mjrosato@linux.ibm.com> (raw)
As discussed in this thread:
https://lore.kernel.org/kvm/20220516172734.GE1343366@nvidia.com/
Let's remove VFIO_GROUP_NOTIFY_SET_KVM and instead assume the association
has already been established prior to device_open. For the types today
that need a KVM (GVT, vfio-ap) these will fail if a KVM is not found.
Looking ahead, vfio-pci-zdev will optionally want the KVM association
(enable hardware assists) but it will not be a hard requirement (still
want to allow other, non-KVM userspace usage).
This is built on top of Jason's group locking series:
https://github.com/jgunthorpe/linux/commits/vfio_group_locking
And tested with s390x-pci (zdev-kvm series) and vfio-ap (no GVT to test
with)
@Jason since it's based on your initial patch if you'd rather a SoB just
let me know.
Matthew Rosato (1):
vfio: remove VFIO_GROUP_NOTIFY_SET_KVM
drivers/gpu/drm/i915/gvt/gvt.h | 2 -
drivers/gpu/drm/i915/gvt/kvmgt.c | 60 +++++------------------
drivers/s390/crypto/vfio_ap_ops.c | 35 +++-----------
drivers/s390/crypto/vfio_ap_private.h | 3 --
drivers/vfio/vfio.c | 68 +++++++++------------------
include/linux/vfio.h | 5 +-
6 files changed, 41 insertions(+), 132 deletions(-)
--
2.27.0
next reply other threads:[~2022-05-17 18:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-17 18:08 Matthew Rosato [this message]
2022-05-17 18:08 ` [PATCH 1/1] vfio: remove VFIO_GROUP_NOTIFY_SET_KVM Matthew Rosato
2022-05-17 18:56 ` Jason Gunthorpe
2022-05-18 7:39 ` Christoph Hellwig
2022-05-18 11:58 ` Jason Gunthorpe
2022-05-18 7:47 ` Christoph Hellwig
2022-05-18 14:37 ` Matthew Rosato
2022-05-18 15:12 ` Jason Gunthorpe
2022-05-18 15:33 ` Matthew Rosato
2022-05-18 15:38 ` Jason Gunthorpe
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=20220517180851.166538-1-mjrosato@linux.ibm.com \
--to=mjrosato@linux.ibm.com \
--cc=akrowiak@linux.ibm.com \
--cc=alex.williamson@redhat.com \
--cc=borntraeger@linux.ibm.com \
--cc=cohuck@redhat.com \
--cc=hch@infradead.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-gvt-dev@lists.freedesktop.org \
--cc=jgg@nvidia.com \
--cc=jjherne@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=pasic@linux.ibm.com \
--cc=zhenyuw@linux.intel.com \
--cc=zhi.a.wang@intel.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