From: Alex Williamson <alex.williamson@redhat.com>
To: Tiwei Bie <tiwei.bie@intel.com>
Cc: virtio-dev@lists.oasis-open.org, qemu-devel@nongnu.org,
mst@redhat.com, pbonzini@redhat.com, stefanha@redhat.com,
cunming.liang@intel.com, dan.daly@intel.com,
jianfeng.tan@intel.com, zhihong.wang@intel.com,
xiao.w.wang@intel.com
Subject: Re: [Qemu-devel] [RFC 3/3] vhost-user: add VFIO based accelerators support
Date: Tue, 16 Jan 2018 10:23:39 -0700 [thread overview]
Message-ID: <20180116102339.7ad44e48@w520.home> (raw)
In-Reply-To: <20171222064151.29266-4-tiwei.bie@intel.com>
On Fri, 22 Dec 2017 14:41:51 +0800
Tiwei Bie <tiwei.bie@intel.com> wrote:
> Signed-off-by: Tiwei Bie <tiwei.bie@intel.com>
> ---
> docs/interop/vhost-user.txt | 57 ++++++
> hw/vfio/common.c | 2 +-
> hw/virtio/vhost-user.c | 381 ++++++++++++++++++++++++++++++++++++++++-
> hw/virtio/vhost.c | 3 +-
> hw/virtio/virtio-pci.c | 8 -
> hw/virtio/virtio-pci.h | 8 +
> include/hw/vfio/vfio.h | 2 +
> include/hw/virtio/vhost-user.h | 26 +++
> 8 files changed, 476 insertions(+), 11 deletions(-)
>
> diff --git a/hw/vfio/common.c b/hw/vfio/common.c
> index 7b2924c0ef..53d8700581 100644
> --- a/hw/vfio/common.c
> +++ b/hw/vfio/common.c
> @@ -49,7 +49,7 @@ struct vfio_as_head vfio_address_spaces =
> * initialized, this file descriptor is only released on QEMU exit and
> * we'll re-use it should another vfio device be attached before then.
> */
> -static int vfio_kvm_device_fd = -1;
> +int vfio_kvm_device_fd = -1;
> #endif
It seems troublesome for vhost to maintain it's own list of groups and
register them with the vfio-kvm device. These should likely be made
into services provided by vfio/common.c such that we can have a single
group list and interfaces for adding and deleting them. Thanks,
Alex
next prev parent reply other threads:[~2018-01-16 17:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-22 6:41 [Qemu-devel] [RFC 0/3] Extend vhost-user to support VFIO based accelerators Tiwei Bie
2017-12-22 6:41 ` [Qemu-devel] [RFC 1/3] vhost-user: support receiving file descriptors in slave_read Tiwei Bie
2017-12-22 6:41 ` [Qemu-devel] [RFC 2/3] vhost-user: introduce shared vhost-user state Tiwei Bie
2017-12-22 6:41 ` [Qemu-devel] [RFC 3/3] vhost-user: add VFIO based accelerators support Tiwei Bie
2018-01-16 17:23 ` Alex Williamson [this message]
2018-01-17 5:00 ` Tiwei Bie
2018-01-02 2:42 ` [Qemu-devel] [RFC 0/3] Extend vhost-user to support VFIO based accelerators Alexey Kardashevskiy
2018-01-02 5:49 ` Liang, Cunming
2018-01-02 6:01 ` Alexey Kardashevskiy
2018-01-02 6:48 ` Liang, Cunming
2018-01-03 14:34 ` [Qemu-devel] [virtio-dev] " Jason Wang
2018-01-04 6:18 ` Tiwei Bie
2018-01-04 7:21 ` Jason Wang
2018-01-05 6:58 ` Liang, Cunming
2018-01-05 8:38 ` Jason Wang
2018-01-05 10:25 ` Liang, Cunming
2018-01-08 3:23 ` Jason Wang
2018-01-08 8:23 ` [Qemu-devel] [virtio-dev] " Liang, Cunming
2018-01-08 10:06 ` Jason Wang
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=20180116102339.7ad44e48@w520.home \
--to=alex.williamson@redhat.com \
--cc=cunming.liang@intel.com \
--cc=dan.daly@intel.com \
--cc=jianfeng.tan@intel.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=tiwei.bie@intel.com \
--cc=virtio-dev@lists.oasis-open.org \
--cc=xiao.w.wang@intel.com \
--cc=zhihong.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;
as well as URLs for NNTP newsgroup(s).