[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-devel] DOM0_GETDOMAININFO intended behavior

To: "Daniel Stekloff" <dsteklof@xxxxxxxxxx>, "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
From: "Macy, Kip" <Kip.Macy@xxxxxxxxxx>
Date: Thu, 9 Jun 2005 17:18:02 -0700
Cc: Kip Macy <kip.macy@xxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, Christian.Limpach@xxxxxxxxxxxx
Delivery-date: Sun, 12 Jun 2005 11:35:29 +0000
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
Thread-index: AcVtQ9ieFK3PGEzlSX2Hb4GVQAyQlgADe5sQ
Thread-topic: [Xen-devel] DOM0_GETDOMAININFO intended behavior

> I think the cleanest fix is just to add an 'iterate' flag to the 
> parameters in GETDOMAININFO, no?


Ok... now that I (unintentionally) went overboard on this, why not just
document how it works and leave it as is? What will the flag really buy
you? 

Behaviour consistent with the other DOM0 operations.

-Kip

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

Prev by Date: [Xen-devel] RE: Xen-devel Digest, Vol 4, Issue 62
Next by Date: Re: [Xen-devel] [PATCH] rename some xsenstore library functions
Previous by thread: RE: [Xen-devel] DOM0_GETDOMAININFO intended behavior
Next by thread: RE: [Xen-devel] [PATCH] Xenoprof patches for xen-unstable
Index(es):
- Date
- Thread

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.