From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>,
Markus Armbruster <armbru@redhat.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] RFC: Universal encryption on QEMU I/O channels
Date: Wed, 04 Feb 2015 22:06:01 +0100 [thread overview]
Message-ID: <54D289B9.5050808@redhat.com> (raw)
In-Reply-To: <CAFEAcA-Pzcs6ECDafhW0MtJz4WgLBJOFhhVJx+z1UO4Uq3swxQ@mail.gmail.com>
On 04/02/2015 21:41, Peter Maydell wrote:
> That suggests to me that we could reasonably advance to
> 2.22 or 2.24 if it seemed beneficial, but not beyond that.
> Is there anything particularly worthwhile that would get us?
2.22 is the first version to have GIO.
2.28 would give us TLS support in GIO, but Daniel said it's buggy.
2.32 has new-style synchronization primitives, for which we currently
have some hideous compatibility wrappers.
It looks like there's no particular reason yet to bump our requirement.
Paolo
next prev parent reply other threads:[~2015-02-04 21:06 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-04 11:32 [Qemu-devel] RFC: Universal encryption on QEMU I/O channels Daniel P. Berrange
2015-02-04 12:43 ` Paolo Bonzini
2015-02-04 13:00 ` Daniel P. Berrange
2015-02-04 13:42 ` Paolo Bonzini
2015-02-04 14:08 ` Daniel P. Berrange
2015-02-04 14:23 ` Paolo Bonzini
2015-02-04 14:34 ` Daniel P. Berrange
2015-02-04 15:04 ` Paolo Bonzini
2015-02-04 15:11 ` Daniel P. Berrange
2015-02-04 15:22 ` Paolo Bonzini
2015-02-04 15:26 ` Daniel P. Berrange
2015-02-04 16:46 ` Paolo Bonzini
2015-02-05 14:38 ` Stefan Hajnoczi
2015-02-05 14:44 ` Cornelia Huck
2015-02-05 14:45 ` Peter Maydell
2015-02-04 13:49 ` Markus Armbruster
2015-02-04 13:55 ` Peter Maydell
2015-02-04 16:33 ` Markus Armbruster
2015-02-04 16:41 ` Daniel P. Berrange
2015-02-04 20:41 ` Peter Maydell
2015-02-04 21:06 ` Paolo Bonzini [this message]
2015-02-05 7:57 ` Markus Armbruster
2015-02-04 13:08 ` Dr. David Alan Gilbert
2015-02-04 14:02 ` Daniel P. Berrange
2015-02-04 14:28 ` Paolo Bonzini
2015-02-04 14:48 ` Marcel Apfelbaum
2015-02-04 14:50 ` Daniel P. Berrange
2015-02-04 18:34 ` Eric Blake
2015-02-05 9:11 ` Dr. David Alan Gilbert
2015-02-04 14:27 ` Paolo Bonzini
2015-02-04 14:37 ` Dr. David Alan Gilbert
2015-03-06 17:18 ` Daniel P. Berrange
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=54D289B9.5050808@redhat.com \
--to=pbonzini@redhat.com \
--cc=armbru@redhat.com \
--cc=peter.maydell@linaro.org \
--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).