qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: qemu-devel@nongnu.org
Cc: uri Lublin <ulublin@redhat.com>
Subject: Re: [Qemu-devel] [6907] Introducing qcow2 extensions (Uri Lublin)
Date: Sat, 28 Mar 2009 21:58:26 +0300	[thread overview]
Message-ID: <49CE7352.1050800@redhat.com> (raw)
In-Reply-To: <E1LnckN-00018v-0M@cvs.savannah.gnu.org>

Anthony Liguori wrote:
> Revision: 6907
>           http://svn.sv.gnu.org/viewvc/?view=rev&root=qemu&revision=6907
> Author:   aliguori
> Date:     2009-03-28 17:55:06 +0000 (Sat, 28 Mar 2009)
> Log Message:
> -----------
> Introducing qcow2 extensions (Uri Lublin)
>
> Qcow2 extensions are build of magic (id) len (in bytes) and data.
> They reside right after the qcow2 header.
> If a backing filename exists it follows the qcow2 extension (if exist)
>
> Qcow2 extensions are read upon image open.
> Qcow2 extensions are identified by their magic.
> Unknown qcow2 extensions (unknown magic) are skipped.
> A Special magic of 0 means end-of-qcow2-extensions.
>
>   

We should introduce a notion of compatible vs. incompatible extensions.

A compatible extension my be ignored by the qcow2 code if it does not 
understand the magic number.  An incompatible extension causes an 
abort.  This allows both more flexibility in how we can change the file 
format.  I believe ext* does the same thing.


-- 
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.

  reply	other threads:[~2009-03-28 18:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-28 17:55 [Qemu-devel] [6907] Introducing qcow2 extensions (Uri Lublin) Anthony Liguori
2009-03-28 18:58 ` Avi Kivity [this message]
2009-03-29  1:13   ` Anthony Liguori
2009-03-29  5:45     ` Avi Kivity
2009-03-29 19:44       ` Anthony Liguori

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=49CE7352.1050800@redhat.com \
    --to=avi@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=ulublin@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).