From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: David Vrabel <david.vrabel@citrix.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
Julien Grall <julien.grall@linaro.org>,
<xen-devel@lists.xenproject.org>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: [Xen-devel] [PATCH RFC] xen-block: correctly define structures in public headers
Date: Tue, 3 Dec 2013 12:18:03 +0100 [thread overview]
Message-ID: <529DBDEB.7030306@citrix.com> (raw)
In-Reply-To: <529DCB3C0200007800109502@nat28.tlf.novell.com>
On 03/12/13 12:14, Jan Beulich wrote:
>>>> On 03.12.13 at 11:57, Roger Pau Monne <roger.pau@citrix.com> wrote:
>> struct blkif_request_rw {
>> uint8_t nr_segments; /* number of segments */
>> blkif_vdev_t handle; /* only for read/write requests */
>> -#ifdef CONFIG_X86_64
>> - uint32_t _pad1; /* offsetof(blkif_request,u.rw.id) == 8 */
>> -#endif
>> uint64_t id; /* private guest value, echoed in resp */
>> blkif_sector_t sector_number;/* start sector idx on disk (r/w only) */
>> struct blkif_request_segment {
>> @@ -157,47 +154,36 @@ struct blkif_request_rw {
>> /* @last_sect: last sector in frame to transfer (inclusive). */
>> uint8_t first_sect, last_sect;
>> } seg[BLKIF_MAX_SEGMENTS_PER_REQUEST];
>> -} __attribute__((__packed__));
>> +};
>
> Removing the packed attribute here and below is not possible
> as long as the defined structures get used in struct blkif_request
> as the second field after a uint8_t one, and as long as the
> individual fields here aren't natively aligned.
Sorry, the patch is incorrect, let me resend that.
next prev parent reply other threads:[~2013-12-03 11:18 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-03 10:57 [PATCH RFC] xen-block: correctly define structures in public headers Roger Pau Monne
2013-12-03 11:01 ` David Vrabel
2013-12-03 11:07 ` Paul Durrant
2013-12-03 11:07 ` [Xen-devel] " Paul Durrant
2013-12-03 11:08 ` Ian Campbell
2013-12-03 11:59 ` David Vrabel
2013-12-03 11:59 ` [Xen-devel] " David Vrabel
2013-12-03 13:41 ` Ian Campbell
2013-12-03 13:41 ` [Xen-devel] " Ian Campbell
2013-12-03 15:11 ` David Vrabel
2013-12-03 15:17 ` Ian Campbell
2013-12-03 15:17 ` [Xen-devel] " Ian Campbell
2013-12-03 15:51 ` One Thousand Gnomes
2013-12-03 15:51 ` [Xen-devel] " One Thousand Gnomes
2013-12-03 16:06 ` Ian Campbell
2013-12-03 16:06 ` [Xen-devel] " Ian Campbell
2013-12-03 20:11 ` Konrad Rzeszutek Wilk
2013-12-03 20:11 ` [Xen-devel] " Konrad Rzeszutek Wilk
2013-12-04 9:28 ` Ian Campbell
2013-12-04 9:28 ` [Xen-devel] " Ian Campbell
2013-12-04 9:43 ` Roger Pau Monné
2013-12-04 9:43 ` Roger Pau Monné
2013-12-04 12:10 ` [Xen-devel] " Ian Campbell
2013-12-04 12:10 ` Ian Campbell
2013-12-04 11:03 ` Stefano Stabellini
2013-12-04 11:03 ` [Xen-devel] " Stefano Stabellini
2013-12-04 11:33 ` Stefano Stabellini
2013-12-04 11:33 ` Stefano Stabellini
2013-12-11 16:18 ` Stefano Stabellini
2013-12-11 16:18 ` [Xen-devel] " Stefano Stabellini
2013-12-11 16:23 ` Roger Pau Monné
2013-12-11 16:29 ` Stefano Stabellini
2013-12-11 16:29 ` Stefano Stabellini
2013-12-11 16:23 ` Roger Pau Monné
2013-12-03 15:11 ` David Vrabel
2013-12-03 11:08 ` Ian Campbell
2013-12-03 11:09 ` Roger Pau Monné
2013-12-03 11:09 ` Roger Pau Monné
2013-12-03 11:01 ` David Vrabel
2013-12-03 11:05 ` Ian Campbell
2013-12-03 11:05 ` [Xen-devel] " Ian Campbell
2013-12-03 11:11 ` Jan Beulich
2013-12-03 11:15 ` Ian Campbell
2013-12-03 11:15 ` [Xen-devel] " Ian Campbell
2013-12-03 11:11 ` Jan Beulich
2013-12-03 11:14 ` Roger Pau Monné
2013-12-03 11:14 ` [Xen-devel] " Roger Pau Monné
2013-12-03 11:14 ` Jan Beulich
2013-12-03 11:14 ` [Xen-devel] " Jan Beulich
2013-12-03 11:18 ` Roger Pau Monné [this message]
2013-12-03 11:18 ` Roger Pau Monné
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=529DBDEB.7030306@citrix.com \
--to=roger.pau@citrix.com \
--cc=JBeulich@suse.com \
--cc=boris.ostrovsky@oracle.com \
--cc=david.vrabel@citrix.com \
--cc=julien.grall@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xenproject.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.