From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: stefanha@redhat.com, mst@redhat.com, mlureau@redhat.com,
qemu-devel@nongnu.org
Cc: Maxime Coquelin <maxime.coquelin@redhat.com>
Subject: [Qemu-devel] [RFC 0/5] vhost-user: Forward virtio device status updates
Date: Fri, 16 Feb 2018 18:29:05 +0100 [thread overview]
Message-ID: <20180216172910.8549-1-maxime.coquelin@redhat.com> (raw)
This series introduces a new vhost-user request to notify the
backend with virtio device status updates.
This is done to address the case when the guest driver only
intializes a subset of the virtqueues. For example, it happens
with Windows virtio-net driver, when the virtio-net device has
more queue pairs than vCPUs.
With Virtio 1.0 devices, the driver sets DRIVER_OK after having
intialized all queues, so the backend can use this information
to start the vhost port.
With legacy devices, this is not guaranteed as mentionned in
the spec, so the backend should not rely on DRIVER_OK.
A solution has yet to be found for legacy devices.
Maxime Coquelin (5):
vhost: send virtio device status update to the backend
vhost-user: Introduce new request to send virtio device status
vhost_net: send virtio device status update to the backend
vhost-user-blk: send virtio status to the backend
vhost-user-scsi: send virtio status to the backend
docs/interop/vhost-user.txt | 14 ++++++++++++++
hw/block/vhost-user-blk.c | 1 +
hw/net/vhost_net.c | 10 ++++++++++
hw/net/virtio-net.c | 7 ++++++-
hw/scsi/vhost-user-scsi.c | 2 ++
hw/virtio/vhost-user.c | 35 +++++++++++++++++++++++++++++++++++
hw/virtio/vhost.c | 11 +++++++++++
include/hw/virtio/vhost-backend.h | 3 +++
include/hw/virtio/vhost.h | 3 +++
include/net/vhost_net.h | 2 ++
10 files changed, 87 insertions(+), 1 deletion(-)
--
2.14.3
next reply other threads:[~2018-02-16 17:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-16 17:29 Maxime Coquelin [this message]
2018-02-16 17:29 ` [Qemu-devel] [RFC 1/5] vhost: send virtio device status update to the backend Maxime Coquelin
2018-02-16 17:29 ` [Qemu-devel] [RFC 2/5] vhost-user: Introduce new request to send virtio device status Maxime Coquelin
2018-02-27 15:01 ` Michael S. Tsirkin
2018-02-27 16:30 ` Maxime Coquelin
2018-02-16 17:29 ` [Qemu-devel] [RFC 3/5] vhost_net: send virtio device status update to the backend Maxime Coquelin
2018-02-16 17:29 ` [Qemu-devel] [RFC 4/5] vhost-user-blk: send virtio status " Maxime Coquelin
2018-02-16 17:29 ` [Qemu-devel] [RFC 5/5] vhost-user-scsi: " 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=20180216172910.8549-1-maxime.coquelin@redhat.com \
--to=maxime.coquelin@redhat.com \
--cc=mlureau@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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).