From mboxrd@z Thu Jan 1 00:00:00 1970 From: Hollis Blanchard Subject: Re: [patch 01/10] Generate headers with arch-specific structs. Date: Mon, 04 Dec 2006 14:12:03 -0600 Message-ID: <1165263124.30343.34.camel@basalt> References: <20061204105824.942096000@suse.de> <20061204105847.355561000@suse.de> <1165249737.30343.7.camel@basalt> <4574552C.6090801@suse.de> Reply-To: Hollis Blanchard Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4574552C.6090801@suse.de> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Gerd Hoffmann Cc: xen-devel@lists.xensource.com, xen-ppc-devel List-Id: xen-devel@lists.xenproject.org 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