All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson@redhat.com>
To: Jike Song <jike.song@intel.com>
Cc: pbonzini@redhat.com, guangrong.xiao@linux.intel.com,
	kevin.tian@intel.com, kwankhede@nvidia.com, cjia@nvidia.com,
	kvm@vger.kernel.org
Subject: Re: [v7 0/3] plumb kvm/vfio to notify kvm:group attach/detach
Date: Wed, 30 Nov 2016 10:06:57 -0700	[thread overview]
Message-ID: <20161130100657.04ba599f@t450s.home> (raw)
In-Reply-To: <583CEFAA.3070600@intel.com>

On Tue, 29 Nov 2016 11:02:02 +0800
Jike Song <jike.song@intel.com> wrote:

> On 11/22/2016 02:09 PM, Jike Song wrote:
> > So far KVM and VFIO are mostly transparent to each other.
> > However, there are users who would rely on them both. For
> > example, KVMGT relies on VFIO to mediate device operations,
> > and it also relies on KVM for features such as guest page
> > tracking. To do that, it needs to know which KVM instance
> > a vfio_group is attached to, when it will be detached.
> > 
> > There is already a kvm_vfio device serving for similar
> > purpose, this series extends it to allow users register
> > notifiers on a vfio_group, and notify kvm:group attaching
> > and detaching events to that.
> > 
> > 
> > Changes v7:
> > 	- replace vfio->opened with container user like iommu notifier registration
> > 	- fix a typo
> > Changes v6:
> > 	- only allow registration on already opened vfio_group 
> > 	- moved WARN_ON from vfio_group_release to vfio_group_fops_release
> > 	- remove unnecessary check
> > Changes v5:
> > 	- separate vfio_group and vfio_iommu events from each other
> > 	- force user to specify which type it is interested in, and which events.
> > 	  Register it IFF all required events are supported
> > Changes v4:
> > 	- use a notifier-based implementation in vfio_group
> > 	- combine the notifier along with iommu notifier by Kirti
> > Changes v3:
> > 	- don't touch kvm_put_kvm, vfio won't need it
> > 	- fix a race condition
> > Changes v2:
> > 	- As Paolo suggested, drop the type and get/put ops from
> > 	  vfio, assuming that the data will always be kvm.
> > 
> > 
> > 
> > Jike Song (3):
> >   vfio: vfio_register_notifier: classify iommu notifier
> >   vfio: support notifier chain in vfio_group
> >   kvm: set/clear kvm to/from vfio_group when group add/delete
> > 
> >  drivers/vfio/vfio.c  | 167 ++++++++++++++++++++++++++++++++++++++++++++-------
> >  include/linux/vfio.h |  22 ++++++-
> >  virt/kvm/vfio.c      |  31 ++++++++++
> >  3 files changed, 195 insertions(+), 25 deletions(-)  
> 
> Hi Alex,
> 
> Since Paolo has ACKed a previous version of PATCH [3/3] before, if you have
> no more comments on this series, could you pick them up? Please be aware that
> 1/3 was updated, or I can send a v8 if you prefer :)

Sorry for the delay, I was on holiday.  Please send a v8, particularly
since I noted updates in patch 3/3 as well.  I would prefer to commit
this with a R-b from Kirti since the NVIDIA driver is also affected by
this, but I believe this is the right approach for us long term.  I'm
also having trouble finding an ack from Paolo that's particularly
relevant for the kvm-vfio portion, but I don't think this is a
controversial issue, I feel comfortable that he's onboard with the
idea.  Thanks,

Alex

  reply	other threads:[~2016-11-30 17:07 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-22  6:09 [v7 0/3] plumb kvm/vfio to notify kvm:group attach/detach Jike Song
2016-11-22  6:09 ` [v7 1/3] vfio: vfio_register_notifier: classify iommu notifier Jike Song
2016-11-23  8:50   ` [UPDATE v7 " Jike Song
2016-11-22  6:09 ` [v7 2/3] vfio: support notifier chain in vfio_group Jike Song
2016-11-22 13:35   ` Kirti Wankhede
2016-11-22 14:02     ` Alex Williamson
2016-11-22 14:39       ` Kirti Wankhede
2016-11-22 14:50         ` Alex Williamson
2016-11-23  3:20           ` Jike Song
2016-11-23  4:52             ` Kirti Wankhede
2016-11-23  5:56               ` Alex Williamson
2016-11-23  6:29                 ` Jike Song
2016-11-23  6:33                   ` Tian, Kevin
2016-11-23  7:53                     ` Jike Song
2016-11-23 12:45                       ` Alex Williamson
2016-11-22  6:09 ` [v7 3/3] kvm: set/clear kvm to/from vfio_group when group add/delete Jike Song
2016-11-30 17:02   ` Alex Williamson
2016-12-01  2:47     ` Jike Song
2016-11-29  3:02 ` [v7 0/3] plumb kvm/vfio to notify kvm:group attach/detach Jike Song
2016-11-30 17:06   ` Alex Williamson [this message]
2016-12-01  2:27     ` Jike Song
2016-12-01  4:42       ` Kirti Wankhede

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=20161130100657.04ba599f@t450s.home \
    --to=alex.williamson@redhat.com \
    --cc=cjia@nvidia.com \
    --cc=guangrong.xiao@linux.intel.com \
    --cc=jike.song@intel.com \
    --cc=kevin.tian@intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=kwankhede@nvidia.com \
    --cc=pbonzini@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.