From: Gerd Hoffmann <kraxel@suse.de>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com, Jan Beulich <jbeulich@novell.com>
Subject: Re: SPAM: Re: Re: [patch rfc 1/3] xen arch header rework.
Date: Wed, 11 Oct 2006 14:21:28 +0200 [thread overview]
Message-ID: <452CE1C8.8000808@suse.de> (raw)
In-Reply-To: <C152978C.2583%Keir.Fraser@cl.cam.ac.uk>
Hi,
>> I can fit it into the xen/include/public subtree so the generated header
>> files are available to everyone and not just private to libxc if that is
>> the way we'll plan to go.
>
> That would make sense. Xen itself will probably need these headers, right?
> At least for the hypercalls where we reimplement/recompile rather than hide
> the conversion in a copying shim?
Right now Jan automatically translates the complete header set, a copy
of the patch is here:
http://www.suse.de/~kraxel/patches/kraxel-unstable-master-xen-hg11731-quilt/32-on-64-compatibility-header-generation.diff
That is the only one from Jan's 32-on-64 patches I've inspected in
detail. I've played around with that one too. One of the problems I've
ran into quickly is that including headers for multiple architectures
into one source file doesn't work. Thats why I've decided to
cherry-pick the stuff which needs translation. Not sure whenever that
can work for Jan's xen kernel bits too.
cheers,
Gerd
--
Gerd Hoffmann <kraxel@suse.de>
http://www.suse.de/~kraxel/julika-dora.jpeg
next prev parent reply other threads:[~2006-10-11 12:21 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-05 9:05 [patch rfc 0/3] xen arch header patches kraxel
2006-10-05 9:05 ` [patch rfc 1/3] xen arch header rework kraxel
2006-10-05 12:27 ` Jan Beulich
2006-10-05 13:08 ` Gerd Hoffmann
2006-10-11 9:16 ` Gerd Hoffmann
2006-10-11 9:44 ` Keir Fraser
2006-10-11 10:40 ` Jacob Gorm Hansen
2006-10-11 10:50 ` Keir Fraser
2006-10-11 11:54 ` Gerd Hoffmann
2006-10-11 13:47 ` Jacob Gorm Hansen
2006-10-11 14:49 ` Gerd Hoffmann
2006-10-11 20:38 ` Julian Davison
2006-10-14 1:30 ` Steven Rostedt
2006-10-15 20:21 ` Julian Davison
2006-10-16 14:56 ` Steven Rostedt
2006-10-17 13:28 ` Jacob Gorm Hansen
2006-10-17 20:10 ` Julian Davison
2006-10-11 11:39 ` Gerd Hoffmann
2006-10-11 11:43 ` Keir Fraser
2006-10-11 12:21 ` Gerd Hoffmann [this message]
2006-10-11 12:04 ` John Levon
2006-10-05 9:05 ` [patch rfc 2/3] xen arch header rework, fixups kraxel
2006-10-05 9:05 ` [patch rfc 3/3] xen arch header rework, check utility kraxel
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=452CE1C8.8000808@suse.de \
--to=kraxel@suse.de \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=jbeulich@novell.com \
--cc=xen-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.