All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jike Song <jike.song@intel.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: "Tian, Kevin" <kevin.tian@intel.com>, Neo Jia <cjia@nvidia.com>,
	kvm@vger.kernel.org, guangrong.xiao@intel.com,
	Alex Williamson <alex.williamson@redhat.com>,
	Xiaoguang Chen <xiaoguang.chen@intel.com>,
	qemu-devel <qemu-devel@nongnu.org>,
	Kirti Wankhede <kwankhede@nvidia.com>,
	Xiao Guangrong <guangrong.xiao@linux.intel.com>
Subject: Re: [PATCH 1/2] KVM: page track: add a new notifier type: track_flush_slot
Date: Fri, 14 Oct 2016 20:26:25 +0800	[thread overview]
Message-ID: <5800CEF1.9050004@intel.com> (raw)
In-Reply-To: <b6adbaa2-acf4-7485-5786-8e2355a4b5e9@redhat.com>


On 10/14/2016 06:43 PM, Paolo Bonzini wrote:
> 
> 
> On 14/10/2016 12:37, Jike Song wrote:
>> Hi Paolo & Alex,
>>
>> IIUC, passing file descriptors means touching QEMU and the UAPI between
>> QEMU and VFIO. Would you guys have a look at below draft patch? If it's
>> on the correct direction, I'll send the split ones. Thanks!
>>
>> --
>> Thanks,
>> Jike
>>
>>
>> diff --git a/hw/vfio/pci-quirks.c b/hw/vfio/pci-quirks.c
>> index bec694c..f715d37 100644
>> --- a/hw/vfio/pci-quirks.c
>> +++ b/hw/vfio/pci-quirks.c
>> @@ -10,12 +10,14 @@
>>   * the COPYING file in the top-level directory.
>>   */
>>  
>> +#include <sys/ioctl.h>
>>  #include "qemu/osdep.h"
>>  #include "qemu/error-report.h"
>>  #include "qemu/range.h"
>>  #include "qapi/error.h"
>>  #include "hw/nvram/fw_cfg.h"
>>  #include "pci.h"
>> +#include "sysemu/kvm.h"
>>  #include "trace.h"
>>  
>>  /* Use uin32_t for vendor & device so PCI_ANY_ID expands and cannot match hw */
>> @@ -1844,3 +1846,15 @@ void vfio_setup_resetfn_quirk(VFIOPCIDevice *vdev)
>>          break;
>>      }
>>  }
>> +
>> +void vfio_quirk_kvmgt(VFIOPCIDevice *vdev)
>> +{
>> +    int vmfd;
>> +
>> +    if (!kvm_enabled() || !vdev->kvmgt)
>> +        return;
>> +
>> +    /* Tell the device what KVM it attached */
>> +    vmfd = kvm_get_vmfd(kvm_state);
>> +    ioctl(vdev->vbasedev.fd, VFIO_SET_KVMFD, vmfd);
>> +}
> 
> vfio_kvm_device_add_group is already telling the group id file
> descriptor to KVM.  You can use that existing hook (whose kernel side is
> virt/kvm/vfio.c).

Thanks for quick reply. I'll do some homework and report back :)

--
Thanks,
Jike

  reply	other threads:[~2016-10-14 12:26 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-09  7:41 [PATCH 0/2] page track add notifier type track_flush_slot Xiaoguang Chen
2016-10-09  7:41 ` [PATCH 1/2] KVM: page track: add a new notifier type: track_flush_slot Xiaoguang Chen
2016-10-09  8:31   ` Neo Jia
2016-10-09  8:56     ` Chen, Xiaoguang
2016-10-10 17:06     ` Paolo Bonzini
2016-10-10 18:01       ` Neo Jia
2016-10-10 18:32         ` Paolo Bonzini
2016-10-11  2:39           ` Xiao Guangrong
2016-10-11  8:54             ` Paolo Bonzini
2016-10-11  9:21               ` Xiao Guangrong
2016-10-11  9:47                 ` Paolo Bonzini
2016-10-14 10:37                   ` Jike Song
2016-10-14 10:43                     ` Paolo Bonzini
2016-10-14 12:26                       ` Jike Song [this message]
2016-10-14 14:41                     ` [Qemu-devel] " Alex Williamson
2016-10-14 14:46                       ` Alex Williamson
2016-10-14 16:35                         ` [Qemu-devel] " Neo Jia
2016-10-14 16:51                           ` Alex Williamson
2016-10-14 22:19                             ` Neo Jia
2016-10-17 16:02                               ` Alex Williamson
2016-10-18 12:38                                 ` Jike Song
2016-10-18 14:59                                   ` Alex Williamson
2016-10-19  2:32                                     ` Jike Song
2016-10-19  5:45                                       ` Xiao Guangrong
2016-10-19 11:56                                         ` Paolo Bonzini
2016-10-19 13:39                                           ` Xiao Guangrong
2016-10-19 14:14                                             ` Paolo Bonzini
2016-10-20  1:48                                               ` [Qemu-devel] " Xiao Guangrong
2016-10-20 17:06                                                 ` Paolo Bonzini
2016-10-20 17:19                                                   ` Xiao, Guangrong
2016-10-21  2:47                                                     ` [Qemu-devel] " Jike Song
2016-10-26 13:44                                                   ` Jike Song
2016-10-26 14:45                                                     ` Paolo Bonzini
2016-10-29  4:07                                                       ` Jike Song
2016-10-19 13:56                                       ` Eric Blake
2016-10-24  6:32                                         ` [Qemu-devel] " Jike Song
2016-10-12 20:48   ` Radim Krčmář
2016-10-09  7:41 ` [PATCH 2/2] KVM: MMU: apply page track notifier type track_flush_slot Xiaoguang Chen
2016-10-10 17:06 ` [PATCH 0/2] page track add " Paolo Bonzini
2016-10-11  2:43   ` Xiao Guangrong
2016-10-11  8:55     ` Paolo Bonzini
2016-10-12 20:52       ` Radim Krčmář

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=5800CEF1.9050004@intel.com \
    --to=jike.song@intel.com \
    --cc=alex.williamson@redhat.com \
    --cc=cjia@nvidia.com \
    --cc=guangrong.xiao@intel.com \
    --cc=guangrong.xiao@linux.intel.com \
    --cc=kevin.tian@intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=kwankhede@nvidia.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=xiaoguang.chen@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 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.