From: Stefan Hajnoczi <stefanha@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: "Elena Ufimtseva" <elena.ufimtseva@oracle.com>,
"John G Johnson" <john.g.johnson@oracle.com>,
"Thomas Huth" <thuth@redhat.com>,
"Jagannathan Raman" <jag.raman@oracle.com>,
qemu-devel@nongnu.org, "Markus Armbruster" <armbru@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: Re: [PATCH] multiprocess: move feature to meson_options.txt
Date: Thu, 25 Feb 2021 16:35:27 +0000 [thread overview]
Message-ID: <YDfRz3zhkoTiyoKt@stefanha-x1.localdomain> (raw)
In-Reply-To: <e89873e7-d996-0161-8c4f-587aadd2208f@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1478 bytes --]
On Thu, Feb 25, 2021 at 01:15:53PM +0100, Paolo Bonzini wrote:
> On 25/02/21 11:38, Philippe Mathieu-Daudé wrote:
> > On 2/24/21 1:23 PM, Paolo Bonzini wrote:
> > > Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> > > ---
> > > configure | 12 ++++--------
> > > meson.build | 9 +++++++--
> > > meson_options.txt | 2 ++
> > > 3 files changed, 13 insertions(+), 10 deletions(-)
> > ...
> >
> > > @@ -2535,6 +2540,7 @@ endif
> > > summary_info += {'target list': ' '.join(target_dirs)}
> > > if have_system
> > > summary_info += {'default devices': get_option('default_devices')}
> > > + summary_info += {'Multiprocess QEMU': multiprocess_allowed}
> >
> > Since you are changing this, it is a good opportunity to find a
> > better description to this feature (similarly how we recently clarified
> > the TCI description).
> >
> > The current description is confusing with multiprocessing (which is
> > by default on QEMU and every developer want to exploit that).
> >
> > So the main multiprocess code resides in hw/remote/mpqemu*.
> >
> > I have the impression "monolithic application" is common in
> > software engineering. What about "polylithic QEMU"?
> >
> > Stefan once described it as "out of (main) process device emulation".
>
> Out of process emulation?
When Multiprocess QEMU switches to the vfio-user protocol the feature
could be renamed to "vfio-user device backends".
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-02-25 16:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-24 12:23 [PATCH] multiprocess: move feature to meson_options.txt Paolo Bonzini
2021-02-25 10:38 ` Philippe Mathieu-Daudé
2021-02-25 12:15 ` Paolo Bonzini
2021-02-25 16:35 ` Stefan Hajnoczi [this message]
2021-02-25 17:50 ` Jag Raman
2021-02-25 23:16 ` Philippe Mathieu-Daudé
2021-02-26 7:48 ` Paolo Bonzini
2021-02-26 8:50 ` Philippe Mathieu-Daudé
2021-03-01 11:24 ` Stefan Hajnoczi
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=YDfRz3zhkoTiyoKt@stefanha-x1.localdomain \
--to=stefanha@redhat.com \
--cc=armbru@redhat.com \
--cc=elena.ufimtseva@oracle.com \
--cc=jag.raman@oracle.com \
--cc=john.g.johnson@oracle.com \
--cc=pbonzini@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@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).