From: Stefan Hajnoczi <stefanha@redhat.com>
To: "Wang, Wei W" <wei.w.wang@intel.com>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"virtio-comment@lists.oasis-open.org"
<virtio-comment@lists.oasis-open.org>,
"mst@redhat.com" <mst@redhat.com>,
"pbonzini@redhat.com" <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [virtio-comment] [PATCH] *** Vhost-pci RFC v2 ***
Date: Mon, 29 Aug 2016 11:24:51 -0400 [thread overview]
Message-ID: <20160829152451.GB18909@stefanha-x1.localdomain> (raw)
In-Reply-To: <286AC319A985734F985F78AFA26841F7CB5968@shsmsx102.ccr.corp.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1466 bytes --]
On Mon, Jun 27, 2016 at 02:01:24AM +0000, Wang, Wei W wrote:
> On Sun 6/19/2016 10:14 PM, Wei Wang wrote:
> > This RFC proposes a design of vhost-pci, which is a new virtio device type.
> > The vhost-pci device is used for inter-VM communication.
> >
> > Changes in v2:
> > 1. changed the vhost-pci driver to use a controlq to send acknowledgement
> > messages to the vhost-pci server rather than writing to the device
> > configuration space;
> >
> > 2. re-organized all the data structures and the description layout;
> >
> > 3. removed the VHOST_PCI_CONTROLQ_UPDATE_DONE socket message, which
> > is redundant;
> >
> > 4. added a message sequence number to the msg info structure to identify
> > socket
> > messages, and the socket message exchange does not need to be blocking;
> >
> > 5. changed to used uuid to identify each VM rather than using the QEMU process
> > id
> >
>
> One more point should be added is that the server needs to send periodic socket messages to check if the driver VM is still alive. I will add this message support in next version. (*v2-AR1*)
Either the driver VM could go down or the device VM (server) could go
down. In both cases there must be a way to handle the situation.
If the server VM goes down it should be possible for the driver VM to
resume either via hotplug of a new device or through messages
reinitializing the dead device when the server VM restarts.
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-08-29 15:25 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-19 14:14 [Qemu-devel] [PATCH] *** Vhost-pci RFC v2 *** Wei Wang
2016-06-19 14:14 ` [Qemu-devel] [PATCH] Vhost-pci RFC v2: a new virtio device for inter-VM communication Wei Wang
2016-08-29 15:27 ` Stefan Hajnoczi
2016-06-27 2:01 ` [Qemu-devel] [virtio-comment] [PATCH] *** Vhost-pci RFC v2 *** Wang, Wei W
2016-08-29 15:24 ` Stefan Hajnoczi [this message]
2016-08-29 15:42 ` Michael S. Tsirkin
2016-08-30 10:08 ` Wang, Wei W
2016-08-30 11:10 ` Michael S. Tsirkin
2016-08-30 12:59 ` Wang, Wei W
2016-08-31 16:07 ` Stefan Hajnoczi
2016-09-01 16:27 ` Wei Wang
2016-09-02 13:26 ` Stefan Hajnoczi
2016-09-03 13:36 ` Wang, Wei W
2016-09-05 8:56 ` Marc-André Lureau
2016-09-06 17:16 ` Stefan Hajnoczi
2016-09-07 12:27 ` Wang, Wei W
2016-08-29 15:41 ` Michael S. Tsirkin
2016-08-30 10:07 ` Wang, Wei W
2016-08-31 12:30 ` [Qemu-devel] " Marc-André Lureau
2016-09-01 16:26 ` Wei Wang
2016-09-01 8:49 ` Marc-André Lureau
2016-09-01 12:13 ` [Qemu-devel] [virtio-comment] " Wei Wang
2016-09-01 13:05 ` Marc-André Lureau
2016-09-02 1:29 ` Wei Wang
2016-09-02 8:15 ` Marc-André Lureau
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=20160829152451.GB18909@stefanha-x1.localdomain \
--to=stefanha@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=virtio-comment@lists.oasis-open.org \
--cc=wei.w.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;
as well as URLs for NNTP newsgroup(s).