From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([208.118.235.92]:60504)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <omamluk@zerto.com>) id 1SXYb0-0002T2-CM
	for qemu-devel@nongnu.org; Thu, 24 May 2012 10:01:03 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <omamluk@zerto.com>) id 1SXYaq-0001zB-Hh
	for qemu-devel@nongnu.org; Thu, 24 May 2012 10:00:53 -0400
Received: from mail-bk0-f45.google.com ([209.85.214.45]:58580)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <omamluk@zerto.com>) id 1SXYaq-0001yq-5r
	for qemu-devel@nongnu.org; Thu, 24 May 2012 10:00:44 -0400
Received: by bkwj10 with SMTP id j10so8455235bkw.4
	for <qemu-devel@nongnu.org>; Thu, 24 May 2012 07:00:40 -0700 (PDT)
Message-ID: <4FBE3EFE.4020402@zerto.com>
Date: Thu, 24 May 2012 17:00:30 +0300
From: Ori Mamluk <omamluk@zerto.com>
MIME-Version: 1.0
References: <4FB6821A.1080902@redhat.com> <4FBE3A89.8020702@redhat.com>
In-Reply-To: <4FBE3A89.8020702@redhat.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] Block job commands in QEMU 1.2 [v2,
	including support for replication]
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: Paolo Bonzini <pbonzini@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>, Luiz Capitulino <lcapitulino@redhat.com>, Eric Blake <eblake@redhat.com>, qemu-devel <qemu-devel@nongnu.org>, Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>

On 24/05/2012 16:41, Paolo Bonzini wrote:
> The dirty bitmap is managed by these QMP commands:
>
> * blockdev-dirty-enable: takes a file name used for the dirty bitmap,
> and an optional granularity.  Setting the granularity will not be
> supported in the initial version.
>
> * query-block-dirty: returns statistics about the dirty bitmap: right
> now the granularity, the number of bits that are set, and whether QEMU
> is using the dirty bitmap or just adding to it.
>
> * blockdev-dirty-disable: disable the dirty bitmap.
>
>
When do bits get cleared from the bitmap?
"using the dirty bitmap or just adding to it" - I'm not sure I 
understand what you mean. what's the difference?

Thanks,
Ori