WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-ppc-devel

Re: [Xen-devel] [patch 01/10] Generate headers with arch-specific struct

To: Gerd Hoffmann <kraxel@xxxxxxx>
Subject: Re: [Xen-devel] [patch 01/10] Generate headers with arch-specific structs.
From: Hollis Blanchard <hollisb@xxxxxxxxxx>
Date: Mon, 04 Dec 2006 14:12:03 -0600
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, xen-ppc-devel <xen-ppc-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 04 Dec 2006 12:12:36 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <4574552C.6090801@xxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Organization: IBM Linux Technology Center
References: <20061204105824.942096000@xxxxxxx> <20061204105847.355561000@xxxxxxx> <1165249737.30343.7.camel@basalt> <4574552C.6090801@xxxxxxx>
Reply-to: Hollis Blanchard <hollisb@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
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


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel