From: Stefan Hajnoczi <stefanha@gmail.com>
To: "Elena Ufimtseva" <elena.ufimtseva@oracle.com>,
"John G Johnson" <john.g.johnson@oracle.com>,
"Felipe Franciosi" <felipe@nutanix.com>,
"Jag Raman" <jag.raman@oracle.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
"Gerd Hoffmann" <kraxel@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Konrad Rzeszutek Wilk" <konrad.wilk@oracle.com>,
"Daniel P. Berrange" <berrange@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: Requirements for out-of-process device emulation
Date: Tue, 14 Jan 2020 14:06:07 +0000 [thread overview]
Message-ID: <CAJSP0QU=VP3geaJX-0=fAADB263KZOwAgSBZOvxrx2x-QiGUbA@mail.gmail.com> (raw)
In-Reply-To: <CAJSP0QUUR72Rr_deeckz+RHpZMEBv692V4XupWy9ai3i2QD8bw@mail.gmail.com>
The call is starting now! Sorry, I forgot to send this to qemu-devel.
Stefan
On Tue, Jan 14, 2020 at 11:50 AM Stefan Hajnoczi <stefanha@gmail.com> wrote:
>
> Hi,
> In today's KVM Community Call we will discuss multi-process QEMU and
> related topics (muser and VFIO).
>
> I wanted to share requirements that I've gathered from our previous discussions:
> * Multiple bus types - new bus types can be added in the future.
> * Security - VMM does not trust the device emulation process and vice versa.
> * Unprivileged operation - QEMU and the device emulation process can
> be launched without root privileges.
> * Live migration - saving device state and restoring it.
> * Recovery - the device emulation process can be restarted after a
> crash without the guest's knowledge.
> * vIOMMU - address translation and the ability to expose only a
> subset of guest RAM to the device emulation process.
> * Portability - works across host OSes
>
> Following the VFIO API closely seems attractive to avoid reinventing the wheel.
>
> Stefan
next parent reply other threads:[~2020-01-14 14:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAJSP0QUUR72Rr_deeckz+RHpZMEBv692V4XupWy9ai3i2QD8bw@mail.gmail.com>
2020-01-14 14:06 ` Stefan Hajnoczi [this message]
2020-10-09 16:18 Requirements for out-of-process device emulation Stefan Hajnoczi
2020-10-09 19:44 ` Alex Williamson
2020-10-12 15:39 ` Stefan Hajnoczi
2020-10-12 17:16 ` Alex Bennée
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='CAJSP0QU=VP3geaJX-0=fAADB263KZOwAgSBZOvxrx2x-QiGUbA@mail.gmail.com' \
--to=stefanha@gmail.com \
--cc=berrange@redhat.com \
--cc=elena.ufimtseva@oracle.com \
--cc=felipe@nutanix.com \
--cc=jag.raman@oracle.com \
--cc=john.g.johnson@oracle.com \
--cc=konrad.wilk@oracle.com \
--cc=kraxel@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).