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 10:28:57 -0600 Message-ID: <1165249737.30343.7.camel@basalt> References: <20061204105824.942096000@suse.de> <20061204105847.355561000@suse.de> Reply-To: Hollis Blanchard Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20061204105847.355561000@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 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? Even if that's the case, shouldn't we still have headers in xen/include/public/foreign, since otherwise external tools #including those headers will break? -- Hollis Blanchard IBM Linux Technology Center