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

[Xen-devel] host CPU features/flags in xen API

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] host CPU features/flags in xen API
From: John Levon <levon@xxxxxxxxxxxxxxxxx>
Date: Tue, 24 Apr 2007 00:41:06 +0100
Delivery-date: Mon, 23 Apr 2007 16:35:35 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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
User-agent: Mutt/1.5.9i
The functions to return 'features' and 'flags' in the Xen API seem a
little under-specified, in particular there's no indication of the
format of the string returned. Presumably at some point something is
going to use them. At which point the user has an interesting problem if
it's relying on something there and it's not present.

Either this return value needs to be explicitly labelled as not reliable
or something needs to be defined as 'architectural' for Xen API.

regards
john

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

<Prev in Thread] Current Thread [Next in Thread>