From mboxrd@z Thu Jan  1 00:00:00 1970
From: Keir Fraser <keir@xensource.com>
Subject: Re: 32-on-64: pvfb issue
Date: Mon, 22 Jan 2007 15:40:46 +0000
Message-ID: <C1DA8B7E.802D%keir@xensource.com>
References: <45B4D937.5070502@suse.de>
Mime-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <45B4D937.5070502@suse.de>
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Gerd Hoffmann <kraxel@suse.de>, Markus Armbruster <armbru@redhat.com>
Cc: Xen devel list <xen-devel@lists.xensource.com>
List-Id: xen-devel@lists.xenproject.org

On 22/1/07 15:33, "Gerd Hoffmann" <kraxel@suse.de> 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