From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:40004) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bukTf-0001p6-FJ for qemu-devel@nongnu.org; Thu, 13 Oct 2016 14:11:36 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bukTd-0008PE-BB for qemu-devel@nongnu.org; Thu, 13 Oct 2016 14:11:34 -0400 References: <1475232808-4852-1-git-send-email-vsementsov@virtuozzo.com> <135c0e49-33d9-3b76-9a69-9cfeb0bd8742@redhat.com> From: John Snow Message-ID: <9b3d7b9d-ba53-6371-cbbb-c0e701082e69@redhat.com> Date: Thu, 13 Oct 2016 14:11:20 -0400 MIME-Version: 1.0 In-Reply-To: <135c0e49-33d9-3b76-9a69-9cfeb0bd8742@redhat.com> Content-Type: text/plain; charset=iso-8859-15; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH v7 00/22] qcow2: persistent dirty bitmaps List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Max Reitz , Vladimir Sementsov-Ogievskiy , qemu-block@nongnu.org, qemu-devel@nongnu.org Cc: kwolf@redhat.com, famz@redhat.com, armbru@redhat.com, stefanha@redhat.com, pbonzini@redhat.com, den@openvz.org On 10/01/2016 09:37 AM, Max Reitz wrote: > On 30.09.2016 12:53, Vladimir Sementsov-Ogievskiy wrote: >> v7: >> https://src.openvz.org/users/vsementsov/repos/qemu/browse?at=refs%2Ftags%2Fqcow2-bitmap-v7 >> based on block-next (https://github.com/XanClic/qemu/commits/block-next) > > It should be noted that (at least my) block-next is only valid during > freeze, after that it becomes stale. I assume the patches you require > from my block-next branch are the ones from the "Dirty bitmap changes > for migration/persistence work" series, which I had to drop from my pull > requests, however, due to some issues on Big Endian machines. > > The only reason they are still in my block-next branch is, as I said, > that that branch is just stale. I won't overwrite it for the time being, > though, so this series can still be applied on top. > > Max > Lemme fix up the 32bit problems and resend that out right now. (At least it's not lock correctness.) --js