From: Jan Kiszka <jan.kiszka@siemens.com>
To: Stefan Hajnoczi <stefanha@redhat.com>,
Nikos Dragazis <ndragazis@arrikto.com>
Cc: "John G. Johnson" <john.g.johnson@oracle.com>,
"Andra-Irina Paraschiv" <andraprs@amazon.com>,
kvm@vger.kernel.org, "Michael S. Tsirkin" <mst@redhat.com>,
qemu-devel@nongnu.org,
"Maxime Coquelin" <maxime.coquelin@redhat.com>,
"Alexander Graf" <graf@amazon.com>,
"Thanos Makatos" <thanos.makatos@nutanix.com>,
"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: Inter-VM device emulation (call on Mon 20th July 2020)
Date: Wed, 15 Jul 2020 13:28:07 +0200 [thread overview]
Message-ID: <deb5788e-c828-6996-025d-333cf2bca7ab@siemens.com> (raw)
In-Reply-To: <20200715112342.GD18817@stefanha-x1.localdomain>
[-- Attachment #1: Type: text/plain, Size: 2152 bytes --]
On 15.07.20 13:23, Stefan Hajnoczi wrote:
> Hi,
> Several projects are underway to create an inter-VM device emulation
> interface:
>
> * ivshmem v2
> https://www.mail-archive.com/qemu-devel@nongnu.org/msg706465.html
>
> A PCI device that provides shared-memory communication between VMs.
> This device already exists but is limited in its current form. The
> "v2" project updates IVSHMEM's capabilities and makes it suitable as
> a VIRTIO transport.
>
> Jan Kiszka is working on this and has posted specs for review.
>
> * virtio-vhost-user
> https://www.mail-archive.com/virtio-dev@lists.oasis-open.org/msg06429.html
>
> A VIRTIO device that transports the vhost-user protocol. Allows
> vhost-user device emulation to be implemented by another VM.
>
> Nikos Dragazis is working on this with QEMU, DPDK, and VIRTIO patches
> posted.
>
> * VFIO-over-socket
> https://github.com/tmakatos/qemu/blob/master/docs/devel/vfio-over-socket.rst
>
> Similar to the vhost-user protocol in spirit but for any PCI device.
> Uses the Linux VFIO ioctl API as the protocol instead of vhost.
>
> It doesn't have a virtio-vhost-user equivalent yet, but the same
> approach could be applied to VFIO-over-socket too.
>
> Thanos Makatos and John G. Johnson are working on this. The draft
> spec is available.
>
> Let's have a call to figure out:
>
> 1. What is unique about these approaches and how do they overlap?
> 2. Can we focus development and code review efforts to get something
> merged sooner?
>
> Jan and Nikos: do you have time to join on Monday, 20th of July at 15:00
> UTC?
> https://www.timeanddate.com/worldclock/fixedtime.html?iso=20200720T1500
>
Not at that slot, but one hour earlier or later would work for me (so far).
Jan
> Video call URL: https://bluejeans.com/240406010
>
> It would be nice if Thanos and/or JJ could join the call too. Others
> welcome too (feel free to forward this email)!
>
> Stefan
>
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 8492 bytes --]
next prev parent reply other threads:[~2020-07-15 11:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <86d42090-f042-06a1-efba-d46d449df280@arrikto.com>
2020-07-15 11:23 ` Inter-VM device emulation (call on Mon 20th July 2020) Stefan Hajnoczi
2020-07-15 11:28 ` Jan Kiszka [this message]
2020-07-15 15:38 ` Stefan Hajnoczi
2020-07-15 16:44 ` Alex Bennée
2020-07-17 8:58 ` Nikos Dragazis
2020-07-17 17:10 ` Stefan Hajnoczi
2020-07-15 16:20 ` Thanos Makatos
2020-07-20 17:11 ` Stefan Hajnoczi
2020-07-21 10:49 ` Alex Bennée
2020-07-21 19:08 ` Jan Kiszka
2020-07-27 10:14 ` Stefan Hajnoczi
2020-07-27 10:30 ` Alex Bennée
2020-07-27 11:37 ` Michael S. Tsirkin
2020-07-27 12:22 ` Alex Bennée
2020-07-27 11:52 ` Jean-Philippe Brucker
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=deb5788e-c828-6996-025d-333cf2bca7ab@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=alex.bennee@linaro.org \
--cc=andraprs@amazon.com \
--cc=graf@amazon.com \
--cc=john.g.johnson@oracle.com \
--cc=kvm@vger.kernel.org \
--cc=maxime.coquelin@redhat.com \
--cc=mst@redhat.com \
--cc=ndragazis@arrikto.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=thanos.makatos@nutanix.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).