From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:34654) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YJ35f-0004nO-9H for qemu-devel@nongnu.org; Wed, 04 Feb 2015 11:46:12 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YJ35b-0002j3-Uk for qemu-devel@nongnu.org; Wed, 04 Feb 2015 11:46:11 -0500 Received: from mx1.redhat.com ([209.132.183.28]:60710) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YJ35b-0002iu-Mp for qemu-devel@nongnu.org; Wed, 04 Feb 2015 11:46:07 -0500 Received: from int-mx10.intmail.prod.int.phx2.redhat.com (int-mx10.intmail.prod.int.phx2.redhat.com [10.5.11.23]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id t14Gk5Ei020614 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL) for ; Wed, 4 Feb 2015 11:46:06 -0500 Message-ID: <54D24CC9.2090100@redhat.com> Date: Wed, 04 Feb 2015 17:46:01 +0100 From: Paolo Bonzini MIME-Version: 1.0 References: <20150204113229.GN3032@redhat.com> <54D213E0.8090408@redhat.com> <20150204130041.GQ3032@redhat.com> <54D221BC.50008@redhat.com> <20150204140820.GS3032@redhat.com> <54D22B5A.5020904@redhat.com> <20150204143452.GV3032@redhat.com> <54D23501.5020200@redhat.com> <20150204151105.GY3032@redhat.com> <54D23932.8060101@redhat.com> <20150204152623.GA3032@redhat.com> In-Reply-To: <20150204152623.GA3032@redhat.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Subject: Re: [Qemu-devel] RFC: Universal encryption on QEMU I/O channels List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Daniel P. Berrange" Cc: qemu-devel@nongnu.org On 04/02/2015 16:26, Daniel P. Berrange wrote: > > GIOChannel's advantage is that---even though it may not be used for > > regular migration---integration with chardev would be really easy. > > If we did a QEMUIOChannel that was basically the same as IOChannel, but > with support for iovec writev/readv it'd mostly be drop-in replacement > for the chardev code I guess. Alternatively, QEMUIOChannel could be a very thin wrapper around GIOChannel. If the QEMUIOChannel is created with qemu_io_channel_unix_get_fd, the QEMUIOChannel could use g_io_channel_unix_get_fd to do writev/readv; otherwise it would just use compatibility code. This relieves you from having to rewrite all the Win32 code that glib already has. > So that version of GIO, with the glib-networking addon > to provide TLS, would mean only running on RHEL-7, which feels like it > is so new it would likely be a showstopper. As long as the non-TLS stuff works on older distros, that would be okay for me. Personally I don't care if VNC-TLS regresses on older distros, either. Paolo