From: Stefan Hajnoczi <stefanha@gmail.com>
To: Stefano Garzarella <sgarzare@redhat.com>
Cc: Julio Montes <julio.montes@intel.com>,
Sebastien Boeuf <sebastien.boeuf@intel.com>,
qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [PATCH 0/3] virtio: add vhost-user-vsock device
Date: Thu, 21 May 2020 15:35:59 +0100 [thread overview]
Message-ID: <20200521143559.GL251811@stefanha-x1.localdomain> (raw)
In-Reply-To: <20200515152110.202917-1-sgarzare@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 472 bytes --]
On Fri, May 15, 2020 at 05:21:07PM +0200, Stefano Garzarella wrote:
> This series add vhost-user-vsock base device and its PCI version
> (vhost-user-vsock-pci).
> The vhost-user-vsock device can be used to implement the virtio-vsock
> device emulation in user-space.
> An use case might be Kata, where they prefer to emulate devices
> in user-space.
Looks good.
My main concern is live migration. If it hasn't been tested, please
remove the live migration code.
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-05-21 14:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-15 15:21 [PATCH 0/3] virtio: add vhost-user-vsock device Stefano Garzarella
2020-05-15 15:21 ` [PATCH 1/3] vhost-vsock: add vhost-vsock-common abstraction Stefano Garzarella
2020-05-15 15:21 ` [PATCH 2/3] virtio: add vhost-user-vsock base device Stefano Garzarella
2020-05-15 15:21 ` [PATCH 3/3] virtio: add vhost-user-vsock-pci device Stefano Garzarella
2020-05-21 14:35 ` Stefan Hajnoczi [this message]
2020-05-21 15:07 ` [PATCH 0/3] virtio: add vhost-user-vsock device Stefano Garzarella
2020-05-22 10:06 ` Stefano Garzarella
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=20200521143559.GL251811@stefanha-x1.localdomain \
--to=stefanha@gmail.com \
--cc=julio.montes@intel.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=sebastien.boeuf@intel.com \
--cc=sgarzare@redhat.com \
--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).