From: "Daniel P. Berrangé" <berrange@redhat.com>
To: elena.ufimtseva@oracle.com
Cc: john.g.johnson@oracle.com, jag.raman@oracle.com,
konrad.wilk@oracle.com, qemu-devel@nongnu.org,
ross.lagerwall@citrix.com, liran.alon@oracle.com,
stefanha@redhat.com, kanth.ghatraju@oracle.com
Subject: Re: [Qemu-devel] [RFC PATCH v2 00/35] Initial support of multi-process qemu
Date: Tue, 18 Jun 2019 09:54:56 +0100 [thread overview]
Message-ID: <20190618085456.GD28525@redhat.com> (raw)
In-Reply-To: <20190617181450.29092-1-elena.ufimtseva@oracle.com>
On Mon, Jun 17, 2019 at 11:14:50AM -0700, elena.ufimtseva@oracle.com wrote:
> From: Elena Ufimtseva <elena.ufimtseva@oracle.com>
>
> Initial support of multi-process qemu
>
> Started with the presentation in October 2017 made by
> Marc-Andre (Red Hat) and Konrad Wilk (Oracle)
> (http://events17.linuxfoundation.org/sites/events/files/slides/KVM%20FORUM%20multi-process.pdf,
> https://www.youtube.com/watch?v=Kq1-coHh7lg) and
> continued in the BoF session at the KVM forum in 2018 with Jag leading
> the discussion, the multi-process project is now in the prototype version
> and presented by this patchset.
>
> The proof of the concept patches were posted on the qemu-devel mailing
> list before the BoF session at the KVM forum and can be found here:
> https://www.mail-archive.com/qemu-devel@nongnu.org/msg566538.html
>
> This series presents the initial support for QEMU that can
> launch some of the devices in the remote processes.
>
> Thanks to a v1 review and some of the question Stefan and Daniel asked, we
> were able to incorporate your ideas into our goals.
>
> We would like to present version 2 of the patchset.
> This version has addressed comments made during the review of v1 and includes:
>
> - support for libvirt fork/exec of remote processes;
> QEMU is still capable of fork/execing the remote processes unless its disabled
> by seccomp.
> When using libvirt, the daemon will spawn remote processes and pass the communication
> file descriptors to main QEMU process and the remote processes.
> The libvirt patches are in the making and will be sent out shortly;
> - using existing -device/-drive command line options to specify remote devices with
> additional suboptons;
> - refractor message sending code;
> - remove specific HMP/QMP commands and use the one that exist now;
> - extend existing QMP commands;
> - added timeout to communication channel;
>
> Following people contributed to this patchset:
>
> John G Johnson <john.g.johnson@oracle.com>
> Jagannathan Raman <jag.raman@oracle.com>
> Elena Ufimtseva <elena.ufimtseva@oracle.com>
> Kanth Ghatraju <kanth.ghatraju@oracle.com>
>
> For full concept writeup about QEMU disaggregation refer to
> docs/devel/qemu-multiprocess.txt.
>
> This series has a limited scope and allows QEMU to launch
> LSI SCSI controller emulation in the separate process and
> execute HMP commands to manipulate the devices.
> This series with appropriate libvirt patches allows to
> launch a guest with remote processes using libvirt.
> (libvirt patches will be posted and will be reflected in the reply to
> this patch).
>
> Please refer to the docs/qemu-multiprocess.txt for usage
> information.
>
> his series is based on qemu upstream commit
> 3284aa128153750f14a61e8a96fd085e6f2999b6.
>
> TODO items:
> - bus support for remote process (non-default);
> - live migration;
> - performance improvements;
> - support for more devices;
> - support for seccomp for remote processes;
> - support for CPU disaggregated emulation;
>
> We would like to welcome all your ideas, concerns and questions
> for this patchset.
For future versions please make sure the mails sent a fully
threaded, so that all the patches are in-reply-to the cover
letter mail, rather than each scattered as a standalone mail.
The best way todo this is to use the excellent "git-publish"
tool. The added benefit of git-publish is that it will CC
all the subsystem maintainers whose code is touched
https://github.com/stefanha/git-publish
It is packaged in Debian, Ubuntu, Fedora & EPEL
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
prev parent reply other threads:[~2019-06-18 8:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-17 18:14 [Qemu-devel] [RFC PATCH v2 00/35] Initial support of multi-process qemu elena.ufimtseva
2019-06-18 8:54 ` Daniel P. Berrangé [this message]
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=20190618085456.GD28525@redhat.com \
--to=berrange@redhat.com \
--cc=elena.ufimtseva@oracle.com \
--cc=jag.raman@oracle.com \
--cc=john.g.johnson@oracle.com \
--cc=kanth.ghatraju@oracle.com \
--cc=konrad.wilk@oracle.com \
--cc=liran.alon@oracle.com \
--cc=qemu-devel@nongnu.org \
--cc=ross.lagerwall@citrix.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).