From: Jeff Cody <jcody@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: kwolf@redhat.com, famz@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2 4/9] block: vhdx - log support struct and defines
Date: Thu, 1 Aug 2013 11:51:08 -0400 [thread overview]
Message-ID: <20130801155108.GK19714@localhost.localdomain> (raw)
In-Reply-To: <20130801150005.GE2387@stefanha-thinkpad.redhat.com>
On Thu, Aug 01, 2013 at 05:00:05PM +0200, Stefan Hajnoczi wrote:
> On Wed, Jul 31, 2013 at 11:23:49PM -0400, Jeff Cody wrote:
> > @@ -318,6 +323,18 @@ typedef struct VHDXMetadataEntries {
> > uint16_t present;
> > } VHDXMetadataEntries;
> >
> > +typedef struct VHDXLogEntries {
> > + uint64_t offset;
> > + uint64_t length;
> > + uint32_t head;
> > + uint32_t tail;
> > +} VHDXLogEntries;
> > +
> > +typedef struct VHDXLogEntryInfo {
> > + uint64_t sector_start;
> > + uint32_t desc_count;
> > +} VHDXLogEntryInfo;
>
> An array of VHDXLogEntryInfo structs would be affected by alignment on
> x86_64. &a[1] != (void*)a + sizeof(VHDXLogEntryInfo).
>
> IMO all on-disk structs should be QEMU_PACKED for safety.
Neither of the two structs above reflect on-disk structs (actually
VHDXLogEntryInfo is currently unused, so I should drop it from this
patch).
I should mention this in the commit message, since the patch context
isn't enough to show it, but the structs introduced in this patch are
below a comment demarcation line that calls out an end to the on-disk
structs:
/* ----- END VHDX SPECIFICATION STRUCTURES ---- */
next prev parent reply other threads:[~2013-08-01 15:51 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-01 3:23 [Qemu-devel] [PATCH v2 0/9] VHDX log replay and write support Jeff Cody
2013-08-01 3:23 ` [Qemu-devel] [PATCH v2 1/9] block: vhdx - minor comments and typo correction Jeff Cody
2013-08-01 3:23 ` [Qemu-devel] [PATCH v2 2/9] block: vhdx - add header update capability Jeff Cody
2013-08-01 13:44 ` Stefan Hajnoczi
2013-08-01 14:09 ` Jeff Cody
2013-08-07 14:42 ` Jeff Cody
2013-08-05 11:42 ` Kevin Wolf
2013-08-05 14:43 ` Jeff Cody
2013-08-05 14:45 ` Kevin Wolf
2013-08-05 14:57 ` Jeff Cody
2013-08-05 15:05 ` Kevin Wolf
2013-08-05 15:09 ` Jeff Cody
2013-08-06 8:34 ` Kevin Wolf
2013-08-01 3:23 ` [Qemu-devel] [PATCH v2 3/9] block: vhdx code movement - VHDXMetadataEntries and BDRVVHDXState to header Jeff Cody
2013-08-01 3:23 ` [Qemu-devel] [PATCH v2 4/9] block: vhdx - log support struct and defines Jeff Cody
2013-08-01 15:00 ` Stefan Hajnoczi
2013-08-01 15:51 ` Jeff Cody [this message]
2013-08-07 15:22 ` Kevin Wolf
2013-08-07 17:18 ` Jeff Cody
2013-08-01 3:23 ` [Qemu-devel] [PATCH v2 5/9] block: vhdx - break endian translation functions out Jeff Cody
2013-08-01 15:03 ` Stefan Hajnoczi
2013-08-01 15:14 ` Jeff Cody
2013-08-07 15:29 ` Kevin Wolf
2013-08-07 17:21 ` Jeff Cody
2013-08-01 3:23 ` [Qemu-devel] [PATCH v2 6/9] block: vhdx - update log guid in header, and first write tracker Jeff Cody
2013-08-01 15:09 ` Stefan Hajnoczi
2013-08-01 3:23 ` [Qemu-devel] [PATCH v2 7/9] block: vhdx - log parsing, replay, and flush support Jeff Cody
2013-08-01 3:23 ` [Qemu-devel] [PATCH v2 8/9] block: vhdx - add log write support Jeff Cody
2013-08-01 3:23 ` [Qemu-devel] [PATCH v2 9/9] block: vhdx " Jeff Cody
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=20130801155108.GK19714@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).