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/
Home Products Support Community News


RE: [Xen-devel] DOM0_GETDOMAININFO intended behavior

To: "Daniel Stekloff" <dsteklof@xxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>, <Christian.Limpach@xxxxxxxxxxxx>
Subject: RE: [Xen-devel] DOM0_GETDOMAININFO intended behavior
From: "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
Date: Sat, 4 Jun 2005 22:51:27 +0100
Cc: Kip Macy <kip.macy@xxxxxxxxx>
Delivery-date: Sat, 04 Jun 2005 21:50:45 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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: AcVpRtxqwkiKe6FWTd6lknYBrzBFCQACAgww
Thread-topic: [Xen-devel] DOM0_GETDOMAININFO intended behavior
> You're right, it isn't difficult to check what is returned - 
> provided you know what to expect. If you're new, however, to 
> the API and unfamiliar with the fact that it returns the next 
> domain in the line, you could hit what we just hit. We built 
> an application to use the interface and our tests returned 
> some odd behavior. We had to delve deeper to find out if this 
> was correct or not. 

You're not the first person to be caught out by this -- I seem to recall
that xenctx forgets to do the domid check too.

Passing a flag in to explicitly request that you want to iterate would
probably be an improvement to the interface.


> The current behavior is just not obvious. Perhaps just 
> documenting it in the code and the manual is enough so others 
> don't hit this. 
> Thanks,
> Dan

Xen-devel mailing list