From: "Michael S. Tsirkin" <mst@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: "Elena Ufimtseva" <elena.ufimtseva@oracle.com>,
john.g.johnson@oracle.com, jag.raman@oracle.com, slp@redhat.com,
qemu-devel@nongnu.org,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
kraxel@redhat.com, "Felipe Franciosi" <felipe@nutanix.com>,
thanos.makatos@nutanix.com,
"Alex Bennée" <alex.bennee@linaro.org>,
"David Gibson" <david@gibson.dropbear.id.au>
Subject: Re: Out-of-Process Device Emulation session at KVM Forum 2020
Date: Wed, 28 Oct 2020 07:09:20 -0400 [thread overview]
Message-ID: <20201028070758-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20201027151400.GA138065@stefanha-x1.localdomain>
On Tue, Oct 27, 2020 at 03:14:00PM +0000, Stefan Hajnoczi wrote:
> There will be a birds-of-a-feather session at KVM Forum, a chance for
> us to get together and discuss Out-of-Process Device Emulation.
>
> Please send suggestions for the agenda!
>
> These sessions are a good opportunity to reach agreement on topics that
> are hard to discuss via mailing lists.
>
> Ideas:
> * How will we decide that the protocol is stable? Can third-party
> applications like DPDK/SPDK use the protocol in the meantime?
and if not how do we prevent that?
> * QEMU build system requirements: how to configure and build device
> emulator binaries?
> * Common sandboxing solution shared between C and Rust-based binaries?
> minijail (https://github.com/google/minijail)? bubblewrap
> (https://github.com/containers/bubblewrap)? systemd-run?
disconnect
migration
> Stefan
next prev parent reply other threads:[~2020-10-28 11:10 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-27 15:14 Out-of-Process Device Emulation session at KVM Forum 2020 Stefan Hajnoczi
2020-10-28 9:32 ` Thanos Makatos
2020-10-28 10:07 ` Thanos Makatos
2020-10-28 11:09 ` Michael S. Tsirkin [this message]
2020-10-29 8:21 ` Stefan Hajnoczi
2020-10-29 12:08 ` Stefan Hajnoczi
2020-10-29 13:02 ` Jason Wang
2020-10-29 13:06 ` Paolo Bonzini
2020-10-29 14:08 ` Stefan Hajnoczi
2020-10-29 14:31 ` Alex Williamson
2020-10-29 15:09 ` Jason Wang
2020-10-29 15:46 ` Alex Williamson
2020-10-29 16:10 ` Paolo Bonzini
2020-10-30 1:11 ` Jason Wang
2020-10-30 3:04 ` Alex Williamson
2020-10-30 6:21 ` Stefan Hajnoczi
2020-10-30 9:45 ` Jason Wang
2020-10-30 11:13 ` Stefan Hajnoczi
2020-10-30 12:07 ` Jason Wang
2020-10-30 13:15 ` Stefan Hajnoczi
2020-11-02 2:51 ` Jason Wang
2020-11-02 10:13 ` Stefan Hajnoczi
2020-11-03 7:52 ` Jason Wang
2020-11-03 14:26 ` Stefan Hajnoczi
2020-11-04 6:50 ` Gerd Hoffmann
2020-11-04 7:42 ` Michael S. Tsirkin
2020-10-31 21:49 ` Michael S. Tsirkin
2020-11-01 8:26 ` Paolo Bonzini
2020-11-02 2:54 ` Jason Wang
2020-11-02 3:00 ` Jason Wang
2020-11-02 10:27 ` Stefan Hajnoczi
2020-11-02 10:34 ` Michael S. Tsirkin
2020-11-02 14:59 ` Stefan Hajnoczi
2020-10-30 7:51 ` Michael S. Tsirkin
2020-10-30 9:31 ` Jason Wang
2020-10-29 16:15 ` David Edmondson
2020-10-29 16:42 ` Daniel P. Berrangé
2020-10-29 17:47 ` Kirti Wankhede
2020-10-29 18:07 ` Paolo Bonzini
2020-10-30 1:15 ` Jason Wang
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=20201028070758-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=david@gibson.dropbear.id.au \
--cc=elena.ufimtseva@oracle.com \
--cc=felipe@nutanix.com \
--cc=jag.raman@oracle.com \
--cc=john.g.johnson@oracle.com \
--cc=kraxel@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=slp@redhat.com \
--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).