From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:48510)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <mreitz@redhat.com>) id 1WhLbs-0004Hy-H8
	for qemu-devel@nongnu.org; Mon, 05 May 2014 12:19:26 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <mreitz@redhat.com>) id 1WhLbl-0007Jk-Br
	for qemu-devel@nongnu.org; Mon, 05 May 2014 12:19:20 -0400
Received: from mx1.redhat.com ([209.132.183.28]:29960)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <mreitz@redhat.com>) id 1WhLbl-0007JT-4U
	for qemu-devel@nongnu.org; Mon, 05 May 2014 12:19:13 -0400
Message-ID: <5367B9FB.6060606@redhat.com>
Date: Mon, 05 May 2014 18:19:07 +0200
From: Max Reitz <mreitz@redhat.com>
MIME-Version: 1.0
References: <1397155423-29713-1-git-send-email-mreitz@redhat.com>
In-Reply-To: <1397155423-29713-1-git-send-email-mreitz@redhat.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: quoted-printable
Subject: Re: [Qemu-devel] [PATCH v3 00/12] block/json: Add JSON protocol
	driver
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>, =?UTF-8?B?QmVub8OudCBDYW5ldA==?= <benoit@irqsave.net>, Stefan Hajnoczi <stefanha@redhat.com>

On 10.04.2014 20:43, 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.
>
> 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.

Ping =E2=80=93 I do understand that Kevin has reservations against this s=
eries,=20
but as long as he doesn't explicitly ask me to reimplement this in=20
bdrv_open() without an own block driver (which I'd more or less gladly=20
do), I do not see issues why this series should not be merged.

Max