From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:47960)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <pbonzini@redhat.com>) id 1YO7Sb-0003kl-Gq
	for qemu-devel@nongnu.org; Wed, 18 Feb 2015 11:26:50 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <pbonzini@redhat.com>) id 1YO7SV-00022l-QU
	for qemu-devel@nongnu.org; Wed, 18 Feb 2015 11:26:49 -0500
Received: from mx1.redhat.com ([209.132.183.28]:46732)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <pbonzini@redhat.com>) id 1YO7SV-00022M-IE
	for qemu-devel@nongnu.org; Wed, 18 Feb 2015 11:26:43 -0500
Message-ID: <54E4BD2D.3070607@redhat.com>
Date: Wed, 18 Feb 2015 17:26:21 +0100
From: Paolo Bonzini <pbonzini@redhat.com>
MIME-Version: 1.0
References: <1423710438-14377-1-git-send-email-wency@cn.fujitsu.com>
In-Reply-To: <1423710438-14377-1-git-send-email-wency@cn.fujitsu.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] [RFC PATCH 00/14] Block replication for continuous
	checkpoints
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: Wen Congyang <wency@cn.fujitsu.com>, qemu devel <qemu-devel@nongnu.org>, Kevin Wolf <kwolf@redhat.com>, Stefan Hajnoczi <stefanha@redhat.com>
Cc: Lai Jiangshan <laijs@cn.fujitsu.com>, Jiang Yunhong <yunhong.jiang@intel.com>, Dong Eddie <eddie.dong@intel.com>, "Dr. David Alan Gilbert" <dgilbert@redhat.com>, Max Reitz <mreitz@redhat.com>, Yang Hongyang <yanghy@cn.fujitsu.com>



On 12/02/2015 04:07, Wen Congyang wrote:
> Wen Congyang (14):
>   docs: block replication's description
>   quorom: add a new read pattern
>   quorum: ignore 0-length child
>   Add new block driver interfaces to control disk replication
>   quorom: implement block driver interfaces for block replication
>   NBD client: connect to nbd server later
>   NBD client: implement block driver interfaces for block replication
>   block: add a new API to create a hidden BlockBackend
>   block: give backing image its own BlockBackend
>   allow the backing image access the origin BlockDriverState
>   allow writing to the backing file
>   Add disk buffer for block replication
>   COW: move cow interfaces to a seperate file
>   COLO: implement a new block driver

Hi Wen, sorry for the delay.

Kevin and Max need to review this series, as they are the most
comfortable with BlockDriverState vs. BlockBackend.

I suspect you cannot unconditionally give a separate BlockBackend to
each backing image, but they can hopefully suggest how to proceed.

Paolo