From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Ian Campbell <ian.campbell@citrix.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
oleksandr.dmytryshyn@globallogic.com,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
David Vrabel <david.vrabel@citrix.com>,
xen-devel <xen-devel@lists.xenproject.org>,
roger.pau@citrix.com
Subject: Re: Guidelines for new PV protocol submission
Date: Tue, 20 Jan 2015 14:00:17 +0000 [thread overview]
Message-ID: <54BE5F71.6000303@citrix.com> (raw)
In-Reply-To: <54BE6ACA020000780005711A@mail.emea.novell.com>
On 20/01/15 13:48, Jan Beulich wrote:
>>>> On 20.01.15 at 14:39, <andrew.cooper3@citrix.com> wrote:
>> It is far nicer to work from a document than to worry how another
>> compiler might change the structure.
> Compilers have (almost, i.e. leaving aside bitfields) no freedom in laying
> out structures - any platform's ABI defines how this needs to be done.
> Or else code compiled with different compilers wouldn't inter-operate.
Widths of types are not consistent.
Attempting to use the Xen header files on windows requires sed because
unsigned longs are still 32 bits even on 64bit windows. (i.e. an
unsigned long is not valid for a pointer of natural width, which occurs
even in the HVM ABI).
Assuming a posix view of the world is not good enough for the Xen
ecosystem, which is why a document is preferable to a C structure.
~Andrew
next prev parent reply other threads:[~2015-01-20 14:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-20 12:47 Guidelines for new PV protocol submission Roger Pau Monné
2015-01-20 13:20 ` David Vrabel
2015-01-20 13:39 ` Andrew Cooper
2015-01-20 13:48 ` Jan Beulich
2015-01-20 14:00 ` Andrew Cooper [this message]
2015-01-20 16:32 ` Jan Beulich
2015-01-20 14:21 ` Ian Jackson
2015-01-20 16:28 ` Ian Campbell
2015-01-20 13:46 ` Jan Beulich
2015-02-05 10:42 ` Ian Campbell
2015-02-09 11:01 ` Roger Pau Monné
2015-02-09 11:11 ` Ian Campbell
2015-02-09 11:59 ` Vitaly Chernooky
2015-02-09 13:15 ` Ian Campbell
2015-02-09 13:45 ` Vitaly Chernooky
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=54BE5F71.6000303@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=david.vrabel@citrix.com \
--cc=ian.campbell@citrix.com \
--cc=oleksandr.dmytryshyn@globallogic.com \
--cc=roger.pau@citrix.com \
--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.