From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:58642) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YOqmW-0000Xg-I1 for qemu-devel@nongnu.org; Fri, 20 Feb 2015 11:50:25 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YOqmT-0007hG-B2 for qemu-devel@nongnu.org; Fri, 20 Feb 2015 11:50:24 -0500 Received: from mx1.redhat.com ([209.132.183.28]:37242) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YOqmT-0007gt-4r for qemu-devel@nongnu.org; Fri, 20 Feb 2015 11:50:21 -0500 Date: Fri, 20 Feb 2015 17:50:06 +0100 From: Kashyap Chamarthy Message-ID: <20150220165006.GC6881@tesla.redhat.com> References: <1423865338-8576-1-git-send-email-jsnow@redhat.com> <20150220110920.GD3867@stefanha-thinkpad.redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150220110920.GD3867@stefanha-thinkpad.redhat.com> Subject: Re: [Qemu-devel] [PATCH v13 00/17] block: incremental backup series List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Stefan Hajnoczi Cc: kwolf@redhat.com, famz@redhat.com, armbru@redhat.com, qemu-devel@nongnu.org, vsementsov@parallels.com, mreitz@redhat.com, John Snow On Fri, Feb 20, 2015 at 11:09:20AM +0000, Stefan Hajnoczi wrote: > On Fri, Feb 13, 2015 at 05:08:41PM -0500, John Snow wrote: > > This series requires: [PATCH v3] blkdebug: fix "once" rule > > > > Welcome to the "incremental backup" newsletter, where we discuss > > exciting developments in non-redundant backup technology. > > This issue is called the "Max Reitz Fixup" issue. > > > > This patchset enables the in-memory part of the incremental backup > > feature. There are two series on the mailing list now by Vladimir > > Sementsov-Ogievskiy that enable the migration and persistence of > > dirty bitmaps. > > > > This series and most patches were originally by Fam Zheng. > > Please add docs/incremental-backup.txt explaining how the commands are > intended to be used to perform backups. The QAPI documentation is > sparse and QMP clients would probably need to read the code to > understand how these commands work. Thanks for noting this, I have this series applied locally to test and was intending to going through the iotests for initial documentation when I actually make time to test this sometime next week :-) -- /kashyap