From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:42640) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SuNdg-0005re-Ad for qemu-devel@nongnu.org; Thu, 26 Jul 2012 08:58:01 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SuNda-0008Jb-Ju for qemu-devel@nongnu.org; Thu, 26 Jul 2012 08:58:00 -0400 Received: from mx1.redhat.com ([209.132.183.28]:2059) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SuNda-0008JW-Bm for qemu-devel@nongnu.org; Thu, 26 Jul 2012 08:57:54 -0400 Message-ID: <50113EB0.7070709@redhat.com> Date: Thu, 26 Jul 2012 14:57:20 +0200 From: Kevin Wolf MIME-Version: 1.0 References: <1343218884-14980-1-git-send-email-stefanha@linux.vnet.ibm.com> <1343218884-14980-4-git-send-email-stefanha@linux.vnet.ibm.com> In-Reply-To: <1343218884-14980-4-git-send-email-stefanha@linux.vnet.ibm.com> Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH v2 3/7] docs: add lazy refcounts bit to qcow2 specification List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Stefan Hajnoczi Cc: Khoa Huynh , Anthony Liguori , qemu-devel@nongnu.org Am 25.07.2012 14:21, schrieb Stefan Hajnoczi: > The lazy refcounts bit indicates that this image can take advantage of > the dirty bit and that refcount updates can be postponed. > > Signed-off-by: Stefan Hajnoczi > --- > docs/specs/qcow2.txt | 7 ++++++- > 1 file changed, 6 insertions(+), 1 deletion(-) > > diff --git a/docs/specs/qcow2.txt b/docs/specs/qcow2.txt > index 339cdc1..f2f4faa 100644 > --- a/docs/specs/qcow2.txt > +++ b/docs/specs/qcow2.txt > @@ -86,7 +86,12 @@ in the description of a field. > Bitmask of compatible features. An implementation can > safely ignore any unknown bits that are set. > > - Bits 0-63: Reserved (set to 0) > + Bit 0: Lazy refcounts bit. If this bit is set then > + lazy refcount updates can be used. This means > + postponing marking the image file dirty and Not sure what was intended here, but the dirty flag isn't set anywhere yet, so you can't postpone it either. Maybe s/postponing//? > + postponing refcount metadata updates. > + > + Bits 1-63: Reserved (set to 0) > > 88 - 95: autoclear_features > Bitmask of auto-clear features. An implementation may only Kevin