From: Anthony Liguori <anthony@codemonkey.ws>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: kvm-devel <kvm-devel@lists.sourceforge.net>,
Christian Ehrhardt <ehrhardt@linux.vnet.ibm.com>,
virtualization@lists.linux-foundation.org
Subject: Re: [PATCH] virtio_ring: make structure defines packed
Date: Sat, 09 Feb 2008 18:51:14 -0600 [thread overview]
Message-ID: <47AE4A82.3030504@codemonkey.ws> (raw)
In-Reply-To: <200802081401.21194.borntraeger@de.ibm.com>
Hi Christian,
Christian Borntraeger wrote:
> struct vring_used
> {
> __u16 flags;
> __u16 idx;
> + __u32 padding;
> struct vring_used_elem ring[];
> -};
> +} __attribute__ ((packed));
>
This padding that you've put in is not something that would normally
occur on x86. I've checked with GCC on 32-bit and 64-bit and neither
would include that padding. Is that padding included on s390?
I don't think we can do this on x86 at this point as it changes the
ABI. FWIW, I agree with Arnd also that we should not explicitly pad
structures that are naturally aligned anyway.
Regards,
Anthony Liguori
> struct vring {
> unsigned int num;
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> kvm-devel mailing list
> kvm-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/kvm-devel
>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
next prev parent reply other threads:[~2008-02-10 0:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-08 13:01 [PATCH] virtio_ring: make structure defines packed Christian Borntraeger
2008-02-09 8:56 ` Arnd Bergmann
2008-02-10 0:51 ` Anthony Liguori [this message]
2008-02-10 2:18 ` Arnd Bergmann
2008-02-10 6:32 ` ron minnich
2008-02-11 12:55 ` Christian Borntraeger
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=47AE4A82.3030504@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=borntraeger@de.ibm.com \
--cc=ehrhardt@linux.vnet.ibm.com \
--cc=kvm-devel@lists.sourceforge.net \
--cc=virtualization@lists.linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox