qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Cody <jcody@redhat.com>
To: qemu-devel@nongnu.org
Cc: kwolf@redhat.com, famz@redhat.com, stefanha@redhat.com
Subject: [Qemu-devel] [PATCH v3 0/4] Initial VHDX support
Date: Mon, 29 Apr 2013 14:48:15 -0400	[thread overview]
Message-ID: <cover.1367261038.git.jcody@redhat.com> (raw)


Differences from v2:


Patch 2/4:  changed 2 uint8_t[16] to MSGUID (Kevin)
            renamed all strucs to proper style (Kevin)
            indentations / style (Kevin)
            Removed/fixed outdated comments (Stefan)
            dropped vhdx_header_padded (Kevin)            
            
Patch 3/4:  removed hunk that was meant for old patch 5/5 (Fam)
            check VHDX header version field (Fam)
            validate file type id in open and not just probe (Kevin)
            allow headers with seq # of 0 if other header is invalid (Kevin)
            fixed masking typo for parent meta present (Kevin)
            removed error check for 512-byte sectors (Kevin)
            verify region and metadata table guid are unique (Kevin)
            removed signed/unsigned comparisons (Stefan)
            sanity checking on rt.entry_count (Stefan)
            use clz_() instead of inline code (Stefan)
            bat_rt.length sanity check - compute it rather
               than trust the entry length (Stefan)

Patch 5 (v2): Dropped

This adds the initial support for VHDX image files.  

It currently only supports read operations of VHDX, for fixed and dynamic files.

Notably, the following is not yet supported:
    * Differencing files
    * Log replay (so we will refuse to open any images that are not 'clean')
    * .bdrv_create()
    * write operations other than to the header


Jeff Cody (4):
  qemu: add castagnoli crc32c checksum algorithm
  block: vhdx header for the QEMU support of VHDX images
  block: initial VHDX driver support framework - supports open and probe
  block: add read-only support to VHDX image format.

 block/Makefile.objs   |   1 +
 block/vhdx.c          | 972 ++++++++++++++++++++++++++++++++++++++++++++++++++
 block/vhdx.h          | 325 +++++++++++++++++
 include/qemu/crc32c.h |  35 ++
 util/Makefile.objs    |   1 +
 util/crc32c.c         | 115 ++++++
 6 files changed, 1449 insertions(+)
 create mode 100644 block/vhdx.c
 create mode 100644 block/vhdx.h
 create mode 100644 include/qemu/crc32c.h
 create mode 100644 util/crc32c.c

-- 
1.8.1.4

             reply	other threads:[~2013-04-29 18:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-29 18:48 Jeff Cody [this message]
2013-04-29 18:48 ` [Qemu-devel] [PATCH v3 1/4] qemu: add castagnoli crc32c checksum algorithm Jeff Cody
2013-04-29 18:48 ` [Qemu-devel] [PATCH v3 2/4] block: vhdx header for the QEMU support of VHDX images Jeff Cody
2013-04-29 18:48 ` [Qemu-devel] [PATCH v3 3/4] block: initial VHDX driver support framework - supports open and probe Jeff Cody
2013-04-29 18:48 ` [Qemu-devel] [PATCH v3 4/4] block: add read-only support to VHDX image format Jeff Cody
2013-05-01 12:43 ` [Qemu-devel] [PATCH v3 0/4] Initial VHDX support Stefan Hajnoczi
2013-05-01 15:06   ` Jeff Cody
2013-05-02 11:40     ` Stefan Hajnoczi

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=cover.1367261038.git.jcody@redhat.com \
    --to=jcody@redhat.com \
    --cc=famz@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@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).