From: Stefan Hajnoczi <stefanha@gmail.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: "Nikos Dragazis" <ndragazis@arrikto.com>,
"Jan Kiszka" <jan.kiszka@siemens.com>,
"John G. Johnson" <john.g.johnson@oracle.com>,
"Andra-Irina Paraschiv" <andraprs@amazon.com>,
kvm <kvm@vger.kernel.org>, "Michael S. Tsirkin" <mst@redhat.com>,
qemu-devel <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>,
"Jag Raman" <jag.raman@oracle.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: Re: Inter-VM device emulation (call on Mon 20th July 2020)
Date: Mon, 20 Jul 2020 18:11:53 +0100 [thread overview]
Message-ID: <CAJSP0QU78mAK-DiOYXvTOEa3=CAEy1rQtyTBe5rrKDs=yfptAg@mail.gmail.com> (raw)
In-Reply-To: <20200715112342.GD18817@stefanha-x1.localdomain>
Thank you everyone who joined!
I didn't take notes but two things stood out:
1. The ivshmem v2 and virtio-vhost-user use cases are quite different
so combining them does not seem realistic. ivshmem v2 needs to be as
simple for the hypervisor to implement as possible even if this
involves some sacrifices (e.g. not transparent to the Driver VM that
is accessing the device, performance). virtio-vhost-user is more aimed
at general-purpose device emulation although support for arbitrary
devices (e.g. PCI) would be important to serve all use cases.
2. Alexander Graf's idea for a new Linux driver that provides an
enforcing software IOMMU. This would be a character device driver that
is mmapped by the device emulation process (either vhost-user-style on
the host or another VMM for inter-VM device emulation). The Driver VMM
can program mappings into the device and the page tables in the device
emulation process will be updated. This way the Driver VMM can share
memory specific regions of guest RAM with the device emulation process
and revoke those mappings later.
Stefan
next prev parent reply other threads:[~2020-07-20 17:12 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
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 [this message]
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='CAJSP0QU78mAK-DiOYXvTOEa3=CAEy1rQtyTBe5rrKDs=yfptAg@mail.gmail.com' \
--to=stefanha@gmail.com \
--cc=alex.bennee@linaro.org \
--cc=andraprs@amazon.com \
--cc=graf@amazon.com \
--cc=jag.raman@oracle.com \
--cc=jan.kiszka@siemens.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=philmd@redhat.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).