From: Paolo Bonzini <pbonzini@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] RFC: Universal encryption on QEMU I/O channels
Date: Wed, 04 Feb 2015 13:43:12 +0100 [thread overview]
Message-ID: <54D213E0.8090408@redhat.com> (raw)
In-Reply-To: <20150204113229.GN3032@redhat.com>
On 04/02/2015 12:32, Daniel P. Berrange wrote:
> So my idea would be that we define a QEMUChannel object and set of APIs to
> standardize all interaction with sockets, pipes, RDMA, whatever $channel,
> and then convert the QEMU features I've mentioned over to use that. I think
> that would be simpler than trying to untangle QEMUFile code from migration
> and then extend its features.
Could it be GIOChannel simply?
1) Chardev is already mostly a wrapper around GIOChannel
2) NBD and VNC could be converted to GIOChannel with relative ease
3) migration is more complicated because (unlike everything else) it
uses a separate thread and blocking sockets, but you could probably
write a GIOChannel-based implementation of QEMUFile.
I found a GIOChannel wrapper for gnutls at
https://github.com/aldebaran/connman/blob/master/gweb/giognutls.c. It's
not the right license for QEMU (GPLv2-only) but it's only 400 lines of
code. If necessary I can help with clean-room reverse engineering.
Paolo
next prev parent reply other threads:[~2015-02-04 12:43 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 [this message]
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
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=54D213E0.8090408@redhat.com \
--to=pbonzini@redhat.com \
--cc=berrange@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).