From: Elena Ufimtseva <elena.ufimtseva@oracle.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: "John G Johnson" <john.g.johnson@oracle.com>,
sstabellini@kernel.org, "Jag Raman" <jag.raman@oracle.com>,
konrad.wilk@oracle.com,
"Peter Maydell" <peter.maydell@linaro.org>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
qemu-devel@nongnu.org, ross.lagerwall@citrix.com,
liran.alon@oracle.com, "Stefan Hajnoczi" <stefanha@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
kanth.ghatraju@oracle.com,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>
Subject: Re: [Qemu-devel] [multiprocess RFC PATCH 36/37] multi-process: add the concept description to docs/devel/qemu-multiprocess
Date: Tue, 28 May 2019 08:18:21 -0700 [thread overview]
Message-ID: <20190528151820.GA4545@heatpipe> (raw)
In-Reply-To: <20190523111130.GF26632@stefanha-x1.localdomain>
On Thu, May 23, 2019 at 12:11:30PM +0100, Stefan Hajnoczi wrote:
> Hi Jag and Elena,
> Do you think a call would help to move discussion along more quickly?
>
Hi Stefan,
We would like to join this call.
And thank you inviting us!
Elena
> We could use the next KVM Community Call on June 4th to discuss
> remaining concerns and the next steps:
> https://calendar.google.com/calendar/embed?src=dG9iMXRqcXAzN3Y4ZXZwNzRoMHE4a3BqcXNAZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ
>
> I also hope to include other core QEMU developers. As you know, I'm
> skeptical, but it could be just me and I don't want to block you
> unnecessarily if others are more enthusiastic about this approach.
>
> Stefan
next prev parent reply other threads:[~2019-05-28 15:21 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-07 7:22 [Qemu-devel] [multiprocess RFC PATCH 36/37] multi-process: add the concept description to docs/devel/qemu-multiprocess elena.ufimtseva
2019-03-07 8:14 ` Thomas Huth
2019-03-07 14:16 ` Kevin Wolf
2019-03-07 14:21 ` Thomas Huth
2019-03-07 14:40 ` Konrad Rzeszutek Wilk
2019-03-07 14:53 ` Thomas Huth
2019-03-08 18:22 ` Elena Ufimtseva
2019-03-07 14:26 ` Stefan Hajnoczi
2019-03-07 14:51 ` Daniel P. Berrangé
2019-03-07 16:05 ` Michael S. Tsirkin
2019-03-07 16:19 ` Daniel P. Berrangé
2019-03-07 16:46 ` Michael S. Tsirkin
2019-03-07 16:49 ` Daniel P. Berrangé
2019-03-07 19:27 ` Stefan Hajnoczi
2019-03-07 23:29 ` John G Johnson
2019-03-08 9:50 ` Stefan Hajnoczi
[not found] ` <20190326080822.GC21018@stefanha-x1.localdomain>
[not found] ` <e5395abf-6b41-46c8-f5af-3210077dfdd5@oracle.com>
[not found] ` <CAAdtpL4ztcpf-CTx0fc5T_+VQ+8upHa2pEMoiZPcmBXOO6L3Og@mail.gmail.com>
2019-04-23 21:26 ` Jag Raman
2019-04-23 21:26 ` Jag Raman
2019-04-25 15:44 ` Stefan Hajnoczi
2019-04-25 15:44 ` Stefan Hajnoczi
2019-05-07 19:00 ` Jag Raman
2019-05-23 10:40 ` Stefan Hajnoczi
2019-06-11 15:53 ` Jag Raman
2019-05-23 11:11 ` Stefan Hajnoczi
2019-05-28 15:18 ` Elena Ufimtseva [this message]
2019-05-30 20:54 ` Elena Ufimtseva
2019-06-11 15:59 ` Jag Raman
2019-06-12 16:24 ` Stefan Hajnoczi
2019-06-12 17:01 ` Elena Ufimtseva
2019-03-11 10:20 ` Daniel P. Berrangé
2019-05-07 21:00 ` Elena Ufimtseva
2019-05-23 11:22 ` 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=20190528151820.GA4545@heatpipe \
--to=elena.ufimtseva@oracle.com \
--cc=dgilbert@redhat.com \
--cc=f4bug@amsat.org \
--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=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=ross.lagerwall@citrix.com \
--cc=sstabellini@kernel.org \
--cc=stefanha@gmail.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).