From: Jeff Cody <jcody@redhat.com>
To: qemu-devel@nongnu.org
Cc: kwolf@redhat.com, famz@redhat.com, stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH v3 0/9] VHDX log replay and write support
Date: Wed, 7 Aug 2013 21:39:21 -0400 [thread overview]
Message-ID: <20130808013921.GB11689@localhost.localdomain> (raw)
In-Reply-To: <cover.1375924083.git.jcody@redhat.com>
On Wed, Aug 07, 2013 at 09:32:28PM -0400, Jeff Cody wrote:
> This patch series contains the initial VHDX log parsing, replay,
> and write support.
>
> === v3 changes ===
>
> Thank you Kevin & Stefan for the feedback; incoporated in v3:
>
> Patch 1: --- nil ---
>
> Patch 2: * use sizeof(crc) instead of 4
> * remove outdated comment
> * use sizeof(MSGUID) instead of 16
> * direct assignment of guid structs rather than memcpy
> * rename 'rw' to 'generate_data_write_guid'
> * use offsetof() instead of 4
> * comment typos
> * add missing error checking
> * MSGUID is now QEMU_PACKED
> * configure enable for vhdx is now correct and not braindead
>
> Patch 3: --- nil ---
>
> Patch 4: * code style fixes
> * removed unused struct (VHDXLogEntryInfo)
>
> Patch 5: * more direct assignment of guid rather than memcpy
> * order of operation in export/import the same now
> * became less generous with newlines (bah-humbug!)
>
> Patch 6: * more direct assignment of guid rather than memcpy
> * add error check in vhdx_user_visible_write(), now returns int
>
> Patch 7: * check error return now of vhdx_user_visible_write()
>
> Patch 8: * check error return now of vhdx_user_visible_write()
> * vhdx_log_write_sectors() uses bdrv_pwrite() vs bdrv_pwrite_sync()
> * more direct assignment of guid rather than memcpy
> * use offsetof() instead of 4
>
> Patch 9: --- nil ---
>
> === end v3 changelog ===
>
> v2 changes: Incorporated Fam's review feedback - Thank you Fam for the feedback
>
> === end v2 changelog ===
>
> This will allow an existing log in a VHDX image to be replayed (e.g., a VHDX
> image from a Hyper-V host that crashed). In addition, metadata writes are
> enabled through the log. This allows write support to be enabled for VHDX,
> as the BAT can be updated safely via the log journal.
>
> These exact patches are available from github, for testing:
> https://github.com/codyprime/qemu-kvm-jtc/tree/vhdx-write-v2-upstream
I meant to mention, that the v3 patches are available from github, for
testing:
https://github.com/codyprime/qemu-kvm-jtc/tree/vhdx-write-v3-upstream
>
> The latest vhdx work (including anything beyond these patches, such as
> backing/parent file support) can be found at:
> https://github.com/codyprime/qemu-kvm-jtc/tree/jtc-vhdx-latest
>
> Jeff Cody (9):
> block: vhdx - minor comments and typo correction.
> block: vhdx - add header update capability.
> block: vhdx code movement - VHDXMetadataEntries and BDRVVHDXState to
> header.
> block: vhdx - log support struct and defines
> block: vhdx - break endian translation functions out
> block: vhdx - update log guid in header, and first write tracker
> block: vhdx - log parsing, replay, and flush support
> block: vhdx - add log write support
> block: vhdx write support
>
> block/Makefile.objs | 2 +-
> block/vhdx-endian.c | 141 +++++++
> block/vhdx-log.c | 1011 +++++++++++++++++++++++++++++++++++++++++++++++++++
> block/vhdx.c | 399 ++++++++++++++------
> block/vhdx.h | 135 +++++--
> configure | 24 ++
> 6 files changed, 1585 insertions(+), 127 deletions(-)
> create mode 100644 block/vhdx-endian.c
> create mode 100644 block/vhdx-log.c
>
> --
> 1.8.1.4
>
prev parent reply other threads:[~2013-08-08 1:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-08 1:32 [Qemu-devel] [PATCH v3 0/9] VHDX log replay and write support Jeff Cody
2013-08-08 1:32 ` [Qemu-devel] [PATCH v3 1/9] block: vhdx - minor comments and typo correction Jeff Cody
2013-08-08 1:32 ` [Qemu-devel] [PATCH v3 2/9] block: vhdx - add header update capability Jeff Cody
2013-08-08 1:32 ` [Qemu-devel] [PATCH v3 3/9] block: vhdx code movement - VHDXMetadataEntries and BDRVVHDXState to header Jeff Cody
2013-08-08 1:32 ` [Qemu-devel] [PATCH v3 4/9] block: vhdx - log support struct and defines Jeff Cody
2013-08-08 1:32 ` [Qemu-devel] [PATCH v3 5/9] block: vhdx - break endian translation functions out Jeff Cody
2013-08-08 1:32 ` [Qemu-devel] [PATCH v3 6/9] block: vhdx - update log guid in header, and first write tracker Jeff Cody
2013-08-08 1:32 ` [Qemu-devel] [PATCH v3 7/9] block: vhdx - log parsing, replay, and flush support Jeff Cody
2013-08-08 1:32 ` [Qemu-devel] [PATCH v3 8/9] block: vhdx - add log write support Jeff Cody
2013-08-08 1:32 ` [Qemu-devel] [PATCH v3 9/9] block: vhdx " Jeff Cody
2013-08-08 1:39 ` Jeff Cody [this message]
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=20130808013921.GB11689@localhost.localdomain \
--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).