From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:37648) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WLFLd-0004SQ-1y for qemu-devel@nongnu.org; Wed, 05 Mar 2014 12:11:17 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WLFLY-0001MR-3p for qemu-devel@nongnu.org; Wed, 05 Mar 2014 12:11:12 -0500 Received: from mx1.redhat.com ([209.132.183.28]:46500) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WLFLX-0001M2-RW for qemu-devel@nongnu.org; Wed, 05 Mar 2014 12:11:08 -0500 Received: from int-mx12.intmail.prod.int.phx2.redhat.com (int-mx12.intmail.prod.int.phx2.redhat.com [10.5.11.25]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id s25HB2kw010338 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Wed, 5 Mar 2014 12:11:06 -0500 Message-ID: <5317502B.5010608@redhat.com> Date: Wed, 05 Mar 2014 09:26:19 -0700 From: Eric Blake MIME-Version: 1.0 References: <1393860533-2063-1-git-send-email-mreitz@redhat.com> In-Reply-To: <1393860533-2063-1-git-send-email-mreitz@redhat.com> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="Mtp0KMdX158QQj0lNfk2XaVAsvXmdJf38" Subject: Re: [Qemu-devel] [PATCH 00/10] block/json: Add JSON protocol driver List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Max Reitz , qemu-devel@nongnu.org Cc: Kevin Wolf , Stefan Hajnoczi This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --Mtp0KMdX158QQj0lNfk2XaVAsvXmdJf38 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 03/03/2014 08:28 AM, Max Reitz wrote: > This series adds a passthrough JSON protocol block driver. Its filename= s > are JSON objects prefixed by "json:". The objects are used as options > for opening another block device which will be the child of the JSON > device. Regarding this child device, the JSON driver behaves nearly the= > same as raw_bsd in that it is just a passthrough driver. The only > difference is probably that the JSON driver identifies itself as a bloc= k > filter, in contrast to raw_bsd. >=20 > The purpose of this driver is that it may sometimes be desirable to > specify options for a block device where only a filename can be given, > e.g., for backing files. Using this should obviously be the exception, > but it is nice to have if actually needed. I like the idea! It will be more work for libvirt to actually understand how a json: protocol is actually interpreted if it encounters a qcow2 file with a json: backing file, but it does open up possibilities that are hard to encode in any other sane way. --=20 Eric Blake eblake redhat com +1-919-301-3266 Libvirt virtualization library http://libvirt.org --Mtp0KMdX158QQj0lNfk2XaVAsvXmdJf38 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 Comment: Public key at http://people.redhat.com/eblake/eblake.gpg Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBCAAGBQJTF1ArAAoJEKeha0olJ0Nq5/cH/A58MEJ1QTHIsPUHMiG9VtCI LmZs7526iTWZEJInGQS4hqwqAHU4rIgLofmM/TfuZzaN/N+ErIUJBFJ5+hQJpyok mGbJBa8AkQLSXnrEMgU3F1x1kf/Q+dY/DrkCs4iJhOgDktHc+s1LMaVzvC1rWx73 Z1ijSsxE2tAeU4bN7JqT4UgbnYTZel+UqBmBfWBhpkwFTTx489qkoYHJLzAvi0zn R8Z04YVtSEz1f/bxzHD0/urQ/ozjv/c3w5NQo1eKxHpLJRJ2r7rUnwnRHnLa5g84 EbzIQY8uyS0A8WdmuZ2jD9ticAr8eRGsXIrwVCkJ58U78BoXRfIjQmRFlKdNSHk= =Id/E -----END PGP SIGNATURE----- --Mtp0KMdX158QQj0lNfk2XaVAsvXmdJf38--