From: "Michael S. Tsirkin" <mst@redhat.com>
To: Tiwei Bie <tiwei.bie@intel.com>
Cc: qemu-devel@nongnu.org, virtio-dev@lists.oasis-open.org,
alex.williamson@redhat.com, jasowang@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: [virtio-dev] Re: [PATCH v2 0/6] Extend vhost-user to support VFIO based accelerators
Date: Wed, 28 Mar 2018 18:33:01 +0300 [thread overview]
Message-ID: <20180328183159-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20180328122407.gc6yba26gijlm5g6@debian>
On Wed, Mar 28, 2018 at 08:24:07PM +0800, Tiwei Bie wrote:
> > > Update notes
> > > ============
> > >
> > > IOMMU feature bit check is removed in this version, because:
> > >
> > > The IOMMU feature is negotiable, when an accelerator is used and
> > > it doesn't support virtual IOMMU, its driver just won't provide
> > > this feature bit when vhost library querying its features. And if
> > > it supports the virtual IOMMU, its driver can provide this feature
> > > bit. It's not reasonable to add this limitation in this patch set.
> >
> > Fair enough. Still:
> > Can hardware on intel platforms actually support IOTLB requests?
> > Don't you need to add support for vIOMMU shadowing instead?
> >
>
> For the hardware I have, I guess they can't for now.
So VFIO in QEMU has support for vIOMMU shadowing.
Can you use that somehow?
Ability to run dpdk within guest seems important.
--
MST
---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
WARNING: multiple messages have this Message-ID (diff)
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Tiwei Bie <tiwei.bie@intel.com>
Cc: qemu-devel@nongnu.org, virtio-dev@lists.oasis-open.org,
alex.williamson@redhat.com, jasowang@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] [PATCH v2 0/6] Extend vhost-user to support VFIO based accelerators
Date: Wed, 28 Mar 2018 18:33:01 +0300 [thread overview]
Message-ID: <20180328183159-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20180328122407.gc6yba26gijlm5g6@debian>
On Wed, Mar 28, 2018 at 08:24:07PM +0800, Tiwei Bie wrote:
> > > Update notes
> > > ============
> > >
> > > IOMMU feature bit check is removed in this version, because:
> > >
> > > The IOMMU feature is negotiable, when an accelerator is used and
> > > it doesn't support virtual IOMMU, its driver just won't provide
> > > this feature bit when vhost library querying its features. And if
> > > it supports the virtual IOMMU, its driver can provide this feature
> > > bit. It's not reasonable to add this limitation in this patch set.
> >
> > Fair enough. Still:
> > Can hardware on intel platforms actually support IOTLB requests?
> > Don't you need to add support for vIOMMU shadowing instead?
> >
>
> For the hardware I have, I guess they can't for now.
So VFIO in QEMU has support for vIOMMU shadowing.
Can you use that somehow?
Ability to run dpdk within guest seems important.
--
MST
next prev parent reply other threads:[~2018-03-28 15:33 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-19 7:15 [virtio-dev] [PATCH v2 0/6] Extend vhost-user to support VFIO based accelerators Tiwei Bie
2018-03-19 7:15 ` [Qemu-devel] " Tiwei Bie
2018-03-19 7:15 ` [virtio-dev] [PATCH v2 1/6] vhost-user: support receiving file descriptors in slave_read Tiwei Bie
2018-03-19 7:15 ` [Qemu-devel] " Tiwei Bie
2018-03-19 7:15 ` [virtio-dev] [PATCH v2 2/6] vhost-user: introduce shared vhost-user state Tiwei Bie
2018-03-19 7:15 ` [Qemu-devel] " Tiwei Bie
2018-03-22 15:13 ` [virtio-dev] " Michael S. Tsirkin
2018-03-22 15:13 ` [Qemu-devel] " Michael S. Tsirkin
2018-03-27 13:32 ` [virtio-dev] " Tiwei Bie
2018-03-27 13:32 ` [Qemu-devel] " Tiwei Bie
2018-03-19 7:15 ` [virtio-dev] [PATCH v2 3/6] virtio: support adding sub-regions for notify region Tiwei Bie
2018-03-19 7:15 ` [Qemu-devel] " Tiwei Bie
2018-03-22 14:57 ` [virtio-dev] " Michael S. Tsirkin
2018-03-22 14:57 ` [Qemu-devel] " Michael S. Tsirkin
2018-03-27 13:47 ` [virtio-dev] " Tiwei Bie
2018-03-27 13:47 ` [Qemu-devel] " Tiwei Bie
2018-03-19 7:15 ` [virtio-dev] [PATCH v2 4/6] vfio: support getting VFIOGroup from groupfd Tiwei Bie
2018-03-19 7:15 ` [Qemu-devel] " Tiwei Bie
2018-03-19 7:15 ` [virtio-dev] [PATCH v2 5/6] vfio: remove DPRINTF() definition from vfio-common.h Tiwei Bie
2018-03-19 7:15 ` [Qemu-devel] " Tiwei Bie
2018-03-22 15:15 ` [virtio-dev] " Michael S. Tsirkin
2018-03-22 15:15 ` [Qemu-devel] " Michael S. Tsirkin
2018-03-27 13:33 ` [virtio-dev] " Tiwei Bie
2018-03-27 13:33 ` [Qemu-devel] " Tiwei Bie
2018-03-19 7:15 ` [virtio-dev] [PATCH v2 6/6] vhost-user: add VFIO based accelerators support Tiwei Bie
2018-03-19 7:15 ` [Qemu-devel] " Tiwei Bie
2018-03-22 16:19 ` [virtio-dev] " Michael S. Tsirkin
2018-03-22 16:19 ` [Qemu-devel] " Michael S. Tsirkin
2018-03-27 11:06 ` [virtio-dev] " Tiwei Bie
2018-03-27 11:06 ` [Qemu-devel] " Tiwei Bie
2018-03-27 13:59 ` [virtio-dev] " Tiwei Bie
2018-03-27 13:59 ` [Qemu-devel] " Tiwei Bie
2018-03-22 14:55 ` [virtio-dev] Re: [PATCH v2 0/6] Extend vhost-user to support VFIO based accelerators Michael S. Tsirkin
2018-03-22 14:55 ` [Qemu-devel] " Michael S. Tsirkin
2018-03-23 8:54 ` [virtio-dev] " Tiwei Bie
2018-03-23 8:54 ` [Qemu-devel] " Tiwei Bie
2018-03-22 16:40 ` [virtio-dev] " Michael S. Tsirkin
2018-03-22 16:40 ` [Qemu-devel] " Michael S. Tsirkin
2018-03-28 12:24 ` [virtio-dev] " Tiwei Bie
2018-03-28 12:24 ` [Qemu-devel] " Tiwei Bie
2018-03-28 15:33 ` Michael S. Tsirkin [this message]
2018-03-28 15:33 ` Michael S. Tsirkin
2018-03-29 3:33 ` [virtio-dev] " Tiwei Bie
2018-03-29 3:33 ` [Qemu-devel] " Tiwei Bie
2018-03-29 4:16 ` Michael S. Tsirkin
2018-03-29 4:16 ` [Qemu-devel] " Michael S. Tsirkin
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=20180328183159-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=cunming.liang@intel.com \
--cc=dan.daly@intel.com \
--cc=jasowang@redhat.com \
--cc=jianfeng.tan@intel.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 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.