From: Xiao Guangrong <guangrong.xiao@linux.intel.com>
To: Jike Song <jike.song@intel.com>,
pbonzini@redhat.com, alex.williamson@redhat.com
Cc: kwankhede@nvidia.com, cjia@nvidia.com, kevin.tian@intel.com,
kvm@vger.kernel.org
Subject: Re: [v3 0/5] plumb kvm/vfio to allow getting kvm from vfio_group
Date: Mon, 31 Oct 2016 15:06:32 +0800 [thread overview]
Message-ID: <eb699ed9-41c8-e34a-18b7-d3a1ee6d1c62@linux.intel.com> (raw)
In-Reply-To: <1477895706-22824-1-git-send-email-jike.song@intel.com>
On 10/31/2016 02:35 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.
>
> There is already a kvm_vfio device serving for similar purpose,
> this patchset extend it to allow external usrs like KVMGT to
> get KVM instance from the vfio_group.
>
>
> I picked one of Kirti's patchset from:
>
> https://lkml.org/lkml/2016/10/26/1119
>
> for the function to get the vfio_group from a given device.
>
>
> Changes v3:
> - don't touch kvm_put_kvm, vfio won't need it
Do not understand. vfio does not use it indeed, however, the
user of udata, i.e, KVMGT, should put kvm after vfio_group_get_kvm().
next prev parent reply other threads:[~2016-10-31 7:13 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-31 6:35 [v3 0/5] plumb kvm/vfio to allow getting kvm from vfio_group Jike Song
2016-10-31 6:35 ` [v3 1/5] vfio: Rearrange functions to get vfio_group from dev Jike Song
2016-10-31 6:35 ` [v3 2/5] vfio: export functions to get vfio_group from device and put it Jike Song
2016-10-31 6:35 ` [v3 3/5] KVM: move kvm_get_kvm to kvm_host.h Jike Song
2016-10-31 8:33 ` Paolo Bonzini
2016-10-31 6:35 ` [v3 4/5] vfio: implement APIs to set/put kvm to/from vfio group Jike Song
2016-11-07 18:04 ` Alex Williamson
2016-11-07 18:10 ` Paolo Bonzini
2016-11-07 18:28 ` Alex Williamson
2016-11-07 20:45 ` Paolo Bonzini
2016-11-09 12:49 ` Jike Song
2016-11-09 13:06 ` Xiao Guangrong
2016-11-09 13:31 ` Paolo Bonzini
2016-11-09 14:00 ` Xiao Guangrong
2016-11-09 14:28 ` Paolo Bonzini
2016-11-10 4:13 ` Jike Song
2016-11-09 17:53 ` Alex Williamson
2016-11-10 4:10 ` Jike Song
2016-11-10 6:04 ` Jike Song
2016-11-10 15:37 ` Alex Williamson
2016-11-11 7:29 ` Jike Song
2016-11-14 10:19 ` Jike Song
2016-11-14 15:52 ` Alex Williamson
2016-11-09 2:28 ` Jike Song
2016-11-09 2:52 ` Xiao Guangrong
2016-11-09 3:07 ` Jike Song
2016-10-31 6:35 ` [v3 5/5] KVM: set/clear kvm to/from vfio group during add/delete Jike Song
2016-10-31 8:33 ` Paolo Bonzini
2016-10-31 7:06 ` Xiao Guangrong [this message]
2016-10-31 7:24 ` [v3 0/5] plumb kvm/vfio to allow getting kvm from vfio_group Jike Song
2016-10-31 7:24 ` Xiao Guangrong
2016-10-31 7:30 ` Jike Song
2016-10-31 7:35 ` Xiao Guangrong
2016-11-02 1:06 ` Jike Song
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=eb699ed9-41c8-e34a-18b7-d3a1ee6d1c62@linux.intel.com \
--to=guangrong.xiao@linux.intel.com \
--cc=alex.williamson@redhat.com \
--cc=cjia@nvidia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).