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-devel

Re: [Xen-devel] 32/64-bit hypercall interface

To: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] 32/64-bit hypercall interface
From: Hollis Blanchard <hollisb@xxxxxxxxxx>
Date: Fri, 30 Sep 2005 12:03:35 -0500
Cc: Jimi Xenidis <jimix@xxxxxxxxxxxxxx>, Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx>, Andrei Petrov <andrei@xxxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 30 Sep 2005 17:01:16 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1d841fb2a6ceca0ca88d15d0047ff24f@xxxxxxxxxxxx>
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>
References: <A95E2296287EAD4EB592B5DEEFCE0E9D32E068@xxxxxxxxxxxxxxxxxxxxxxxxxxx> <200509291317.25090.hollisb@xxxxxxxxxx> <200509291512.29891.hollisb@xxxxxxxxxx> <31c4b41b23a195dd2d69cdea28754843@xxxxxxxxxxxx> <20050930005405.GG5242@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <bac2506160e28cc7fecb9afa4fddfb10@xxxxxxxxxxxx> <24aa8891a52e3d3a34fc3b59179a8d0f@xxxxxxxxxx> <99da46303de5c070b985b66e5c1c96dd@xxxxxxxxxxxx> <4f11a9f98b8a256a1a9011af12e9788e@xxxxxxxxxx> <1d841fb2a6ceca0ca88d15d0047ff24f@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Sep 30, 2005, at 11:42 AM, Keir Fraser wrote:

There's the rub: we don't expect to ever want to provide 32-bit x86 ABI compatibility on 64-bit x86 Xen. We will not be supporting 32-bit paravirtualised guests on 64-bit x86 Xen, and we've taken the approach of requiring separate 32- and 64-bit toolsets (which isn't too painful on x86 since full-fledged 64-bit filesystems are quite easy to come by).

That's great, if all you care about is x86. That is how Linux started of course, and look where we are now... I think portability and well-designed interfaces are nice things to think about earlier rather than later. :)

Really this sounds to me like this is only going to be a problem for ppc. That given, knocking up a translation script to import the interfaces into your 32-bit toolchain does seem worthy of consideration. It wouldn't allow you to use the same tool binaries on both 32- and 64-bit ppc Xen, but I don't know how much you actually care about that...

A translation script seems exceedingly difficult. A separate set of headers would be less so, but extremely fragile.

--
Hollis Blanchard
IBM Linux Technology Center


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