From: "Michael S. Tsirkin" <mst@redhat.com>
To: Maxime Coquelin <maxime.coquelin@redhat.com>
Cc: peterx@redhat.com, marcandre.lureau@gmail.com,
vkaplans@redhat.com, jasowang@redhat.com, wexu@redhat.com,
yuanhan.liu@linux.intel.com, qemu-devel@nongnu.org,
jfreiman@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2 0/6] vhost-user: Specify and implement device IOTLB support
Date: Tue, 30 May 2017 21:20:45 +0300 [thread overview]
Message-ID: <20170530211819-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20170526142858.19931-1-maxime.coquelin@redhat.com>
On Fri, May 26, 2017 at 04:28:52PM +0200, Maxime Coquelin wrote:
> This series aims at specifying ans implementing the protocol update
> required to support device IOTLB with user backends.
>
> In this second non-RFC version, main changes are:
> - spec fixes and clarification
> - rings information update has been restored back to ring enablement time
> - Work around GCC 4.4.7 limitation wrt assignment in unnamed union at
> declaration time.
>
> The series can be tested with vhost_iotlb_proto_v2 branch on my gitlab
> account[0].
>
> The slave requests channel part is re-used from Marc-André's series submitted
> last year[1], with main changes from original version being request/feature
> names renaming and addition of the REPLY_ACK feature support.
>
> Regarding IOTLB protocol, one noticeable change is the IOTLB miss request
> reply made optionnal (i.e. only if slave requests it by setting the
> VHOST_USER_NEED_REPLY flag in the message header). This change provides
> more flexibility in the backend implementation of the feature.
>
> The protocol is very close to kernel backends, except that a new
> communication channel is introduced to enable the slave to send
> requests to the master.
>
> [0]: https://gitlab.com/mcoquelin/dpdk-next-virtio/commits/vhost_iotlb_proto_v2
> [1]: https://lists.gnu.org/archive/html/qemu-devel/2016-04/msg00095.html
Overall, this looks good to me. I do think patch 3 isn't a good idea
though, if slave wants something let it request it.
Need to find out why does vhost in kernel want the used ring iotlb at
start time - especially considering we aren't even guaranteed one entry
covers the whole ring, and invalidates should affect all addresses at
least in theory.
> Marc-André Lureau (2):
> vhost-user: add vhost_user to hold the chr
> vhost-user: add slave-req-fd support
>
> Maxime Coquelin (4):
> vhost: propagate errors in vhost_device_iotlb_miss()
> vhost: rework IOTLB messaging
> vhost: extend ring information update for IOTLB to all rings
> spec/vhost-user spec: Add IOMMU support
>
> docs/specs/vhost-user.txt | 118 ++++++++++++++++++++++++-
> hw/virtio/vhost-backend.c | 130 ++++++++++++++++------------
> hw/virtio/vhost-user.c | 177 +++++++++++++++++++++++++++++++++++++-
> hw/virtio/vhost.c | 27 ++++--
> include/hw/virtio/vhost-backend.h | 23 +++--
> include/hw/virtio/vhost.h | 2 +-
> 6 files changed, 397 insertions(+), 80 deletions(-)
>
> --
> 2.9.4
next prev parent reply other threads:[~2017-05-30 18:21 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-26 14:28 [Qemu-devel] [PATCH v2 0/6] vhost-user: Specify and implement device IOTLB support Maxime Coquelin
2017-05-26 14:28 ` [Qemu-devel] [PATCH v2 1/6] vhost: propagate errors in vhost_device_iotlb_miss() Maxime Coquelin
2017-05-26 14:28 ` [Qemu-devel] [PATCH v2 2/6] vhost: rework IOTLB messaging Maxime Coquelin
2017-05-26 14:28 ` [Qemu-devel] [PATCH v2 3/6] vhost: extend ring information update for IOTLB to all rings Maxime Coquelin
2017-05-30 18:12 ` Michael S. Tsirkin
2017-05-30 21:06 ` Maxime Coquelin
2017-05-30 21:11 ` Maxime Coquelin
2017-05-31 15:20 ` Maxime Coquelin
2017-06-01 13:55 ` Michael S. Tsirkin
2017-06-01 13:54 ` Michael S. Tsirkin
2017-05-31 8:48 ` Jason Wang
2017-05-26 14:28 ` [Qemu-devel] [PATCH v2 4/6] vhost-user: add vhost_user to hold the chr Maxime Coquelin
2017-05-26 14:28 ` [Qemu-devel] [PATCH v2 5/6] vhost-user: add slave-req-fd support Maxime Coquelin
2017-05-30 18:17 ` Michael S. Tsirkin
2017-05-30 21:26 ` Maxime Coquelin
2017-05-26 14:28 ` [Qemu-devel] [PATCH v2 6/6] spec/vhost-user spec: Add IOMMU support Maxime Coquelin
2017-05-30 18:08 ` Michael S. Tsirkin
2017-05-30 16:15 ` [Qemu-devel] [PATCH v2 0/6] vhost-user: Specify and implement device IOTLB support Maxime Coquelin
2017-05-30 18:20 ` Michael S. Tsirkin [this message]
2017-05-31 8:33 ` Jason Wang
2017-05-31 15:32 ` Maxime Coquelin
2017-06-01 7:04 ` Jason Wang
2017-06-01 8:39 ` Maxime Coquelin
2017-06-01 13:59 ` Michael S. Tsirkin
2017-06-02 5:53 ` Jason Wang
2017-06-02 15:24 ` Michael S. Tsirkin
2017-06-05 8:51 ` Jason Wang
2017-06-05 15:08 ` 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=20170530211819-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=jasowang@redhat.com \
--cc=jfreiman@redhat.com \
--cc=marcandre.lureau@gmail.com \
--cc=maxime.coquelin@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=vkaplans@redhat.com \
--cc=wexu@redhat.com \
--cc=yuanhan.liu@linux.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).