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-on-64: pvfb issue

To: Gerd Hoffmann <kraxel@xxxxxxx>, Markus Armbruster <armbru@xxxxxxxxxx>
Subject: Re: [Xen-devel] 32-on-64: pvfb issue
From: Keir Fraser <keir@xxxxxxxxxxxxx>
Date: Mon, 22 Jan 2007 15:40:46 +0000
Cc: Xen devel list <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 22 Jan 2007 07:40:24 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <45B4D937.5070502@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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acc+O67M7T9Mf6ouEduK3wAX8io7RQ==
Thread-topic: [Xen-devel] 32-on-64: pvfb issue
User-agent: Microsoft-Entourage/11.2.5.060620
On 22/1/07 15:33, "Gerd Hoffmann" <kraxel@xxxxxxx> wrote:

>> 
>> This identifies the ABI, but how does it provide versioning?
> 
> #define XEN_IO_PROTO_FB_GRANT_TABLES "fb-grant-tables" ?
> 
> Just create a descriptive name you like.  Assuming we don't create
> abi-dependent structs *again* when we change the protocol.
> 
> We can of course also just use XEN_IO_PROTO_ABI_NATIVE "-v2".  With the
> protocol identifier being a string there lots of ways ...

I'd suggest we add a suffix after the ABI part of the protocol name unless
we're really after full portability across any arbitrary architectures (and
so deal with e.g. endianness issues too). Whatever, clearly this approach
has the flexibility to be extended in future without adding all that much
code.

 -- Keir


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