From: Jason Wang <jasowang@redhat.com>
To: Tiwei Bie <tiwei.bie@intel.com>
Cc: Alex Williamson <alex.williamson@redhat.com>,
mst@redhat.com, maxime.coquelin@redhat.com,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
virtualization@lists.linux-foundation.org,
netdev@vger.kernel.org, dan.daly@intel.com,
cunming.liang@intel.com, zhihong.wang@intel.com,
idos@mellanox.com, Rob Miller <rob.miller@broadcom.com>,
Ariel Adam <aadam@redhat.com>
Subject: Re: [RFC v2] vhost: introduce mdev based hardware vhost backend
Date: Thu, 18 Jul 2019 18:31:36 +0800 [thread overview]
Message-ID: <90e6a722-ce7b-2ab3-0d2d-19b2ca09f2d1@redhat.com> (raw)
In-Reply-To: <1b49aa84-2c1f-eec2-2809-711e1f2dd7de@redhat.com>
On 2019/7/10 下午3:22, Jason Wang wrote:
>> Yeah, that's a major concern. If it's true, is it something
>> that's not acceptable?
>
>
> I think not, but I don't know if any other one that care this.
>
>
>>
>>> And I do see some new RFC for VFIO to add more DMA API.
>> Is there any pointers?
>
>
> I don't remember the details, but it should be something related to
> SVA support in recent intel IOMMU.
E.g this series:
https://www.spinics.net/lists/iommu/msg37146.html
Thanks
next prev parent reply other threads:[~2019-07-18 10:31 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-03 9:13 Tiwei Bie
2019-07-03 10:09 ` Jason Wang
2019-07-03 11:52 ` Tiwei Bie
2019-07-03 12:16 ` Jason Wang
2019-07-03 13:08 ` Tiwei Bie
2019-07-04 4:31 ` Jason Wang
2019-07-04 6:21 ` Tiwei Bie
2019-07-04 6:35 ` Jason Wang
2019-07-04 7:02 ` Tiwei Bie
2019-07-05 0:30 ` Jason Wang
2019-07-05 2:23 ` Tiwei Bie
2019-07-05 14:49 ` Alex Williamson
2019-07-08 6:16 ` Tiwei Bie
2019-07-09 2:50 ` Jason Wang
2019-07-09 6:33 ` Tiwei Bie
2019-07-10 2:26 ` Jason Wang
2019-07-10 6:22 ` Tiwei Bie
2019-07-10 7:22 ` Jason Wang
2019-07-18 10:31 ` Jason Wang [this message]
2019-07-03 18:31 ` Alex Williamson
2019-07-04 1:36 ` Tiwei Bie
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=90e6a722-ce7b-2ab3-0d2d-19b2ca09f2d1@redhat.com \
--to=jasowang@redhat.com \
--cc=aadam@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=cunming.liang@intel.com \
--cc=dan.daly@intel.com \
--cc=idos@mellanox.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime.coquelin@redhat.com \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=rob.miller@broadcom.com \
--cc=tiwei.bie@intel.com \
--cc=virtualization@lists.linux-foundation.org \
--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
Powered by JetHome