From: Hollis Blanchard <hollisb@us.ibm.com>
To: Gerd Hoffmann <kraxel@suse.de>
Cc: xen-devel@lists.xensource.com,
xen-ppc-devel <xen-ppc-devel@lists.xensource.com>
Subject: Re: [patch 01/10] Generate headers with arch-specific structs.
Date: Mon, 04 Dec 2006 14:12:03 -0600 [thread overview]
Message-ID: <1165263124.30343.34.camel@basalt> (raw)
In-Reply-To: <4574552C.6090801@suse.de>
On Mon, 2006-12-04 at 18:04 +0100, Gerd Hoffmann wrote:
>
> Hollis Blanchard wrote:
> > On Mon, 2006-12-04 at 11:58 +0100, Gerd Hoffmann wrote:
> >> plain text document attachment (xen-generate-foreign-headers.diff)
> >> This patch adds a script to generate headers with arch-specific
> >> structs which can be included on any architecture. Can be used
> >> to deal with structs of "foreign" architectures, needed for
> >> 32-on-64 support for example.
> >
> > This omits PowerPC; is that because we've made sure not to use
> > variable-sized types?
>
> No. It's because (a) I don't have a working cross compiler and (b)
> because it's the only bigendian architecture, so just generating those
> headers isn't enough to have any other (xen-supported) architectures
> access powerpc structs correctly. So I decided to just leave it as-is
> for now. It certaily can be added, feel free to send patches ;)
Hmm, that's ambitious. What exactly is your use case? If it's 32-on-64,
no endianness code is required, right?
--
Hollis Blanchard
IBM Linux Technology Center
next prev parent reply other threads:[~2006-12-04 20:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-04 10:58 [patch 00/10] libelf and the new domain builder Gerd Hoffmann
2006-12-04 10:58 ` [patch 01/10] Generate headers with arch-specific structs Gerd Hoffmann
2006-12-04 16:28 ` Hollis Blanchard
2006-12-04 17:04 ` Gerd Hoffmann
2006-12-04 20:12 ` Hollis Blanchard [this message]
2006-12-05 8:45 ` Gerd Hoffmann
2006-12-05 13:52 ` Hollis Blanchard
2006-12-04 10:58 ` [patch 02/10] add libelf: an ELF binary parser library Gerd Hoffmann
2006-12-04 10:58 ` [patch 03/10] libelf: use for x86 dom0 builder Gerd Hoffmann
2006-12-04 10:58 ` [patch 04/10] libelf: add to libxc Gerd Hoffmann
2006-12-04 10:58 ` [patch 05/10] libelf: use for hvm builder Gerd Hoffmann
2006-12-04 10:58 ` [patch 06/10] libelf: use for readnotes utility Gerd Hoffmann
2006-12-04 10:58 ` [patch 07/10] libxc header fixups Gerd Hoffmann
2006-12-04 10:58 ` [patch 08/10] libxc domain builder rewrite, core bits Gerd Hoffmann
2006-12-04 10:58 ` [patch 09/10] libxc domain builder rewrite, linux builder Gerd Hoffmann
2006-12-04 10:58 ` [patch 10/10] Support transparant gunzipping in the readnotes utility Gerd Hoffmann
-- strict thread matches above, loose matches on Subject: below --
2006-12-01 15:02 [patch 00/10] libelf and the new domain builder Gerd Hoffmann
2006-12-01 15:02 ` [patch 01/10] Generate headers with arch-specific structs Gerd Hoffmann
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=1165263124.30343.34.camel@basalt \
--to=hollisb@us.ibm.com \
--cc=kraxel@suse.de \
--cc=xen-devel@lists.xensource.com \
--cc=xen-ppc-devel@lists.xensource.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 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.