From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: mst@redhat.com, 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
Cc: Maxime Coquelin <maxime.coquelin@redhat.com>
Subject: [Qemu-devel] [PATCH v3 0/5] vhost-user: Specify and implement device IOTLB support
Date: Fri, 2 Jun 2017 12:18:26 +0200 [thread overview]
Message-ID: <20170602101831.26576-1-maxime.coquelin@redhat.com> (raw)
This series aims at specifying ans implementing the protocol update
required to support device IOTLB with user backends.
In this third non-RFC version, main change is mandating the slave to be able
to send IOTLB miss requests for any addresses it needs to access. It implies
the removal of patch 3, which is no more necessary, and the related spec
update in patch 6. Also, a check is added in vhost-user init to ensure that
the slave does not advertise VIRTIO_F_IOMMU_PLATFORM if it does not support
both VHOST_USER_PROTOCOL_F_SLAVE_REQ and VHOST_USER_PROTOCOL_F_REPLY_ACK
protcol features.
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.
[1]: https://lists.gnu.org/archive/html/qemu-devel/2016-04/msg00095.html
Marc-André Lureau (2):
vhost-user: add vhost_user to hold the chr
vhost-user: add slave-req-fd support
Maxime Coquelin (3):
vhost: propagate errors in vhost_device_iotlb_miss()
vhost: rework IOTLB messaging
spec/vhost-user spec: Add IOMMU support
docs/specs/vhost-user.txt | 116 ++++++++++++++++++++++-
hw/net/vhost_net.c | 1 +
hw/virtio/vhost-backend.c | 130 ++++++++++++++-----------
hw/virtio/vhost-user.c | 194 ++++++++++++++++++++++++++++++++++++--
hw/virtio/vhost.c | 19 ++--
include/hw/virtio/vhost-backend.h | 23 +++--
include/hw/virtio/vhost.h | 2 +-
7 files changed, 404 insertions(+), 81 deletions(-)
--
2.9.4
next reply other threads:[~2017-06-02 10:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-02 10:18 Maxime Coquelin [this message]
2017-06-02 10:18 ` [Qemu-devel] [PATCH v3 1/5] vhost: propagate errors in vhost_device_iotlb_miss() Maxime Coquelin
2017-06-02 10:18 ` [Qemu-devel] [PATCH v3 2/5] vhost: rework IOTLB messaging Maxime Coquelin
2017-06-02 10:18 ` [Qemu-devel] [PATCH v3 3/5] vhost-user: add vhost_user to hold the chr Maxime Coquelin
2017-06-02 10:18 ` [Qemu-devel] [PATCH v3 4/5] vhost-user: add slave-req-fd support Maxime Coquelin
2017-06-02 10:18 ` [Qemu-devel] [PATCH v3 5/5] spec/vhost-user spec: Add IOMMU support Maxime Coquelin
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=20170602101831.26576-1-maxime.coquelin@redhat.com \
--to=maxime.coquelin@redhat.com \
--cc=jasowang@redhat.com \
--cc=jfreiman@redhat.com \
--cc=marcandre.lureau@gmail.com \
--cc=mst@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).