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>
Subject: Re: [Xen-devel] DOM0_GETDOMAININFO intended behavior
From: Christian Limpach <christian.limpach@xxxxxxxxx>
Date: Sat, 4 Jun 2005 20:42:54 +0100
Cc: Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, Kip Macy <kip.macy@xxxxxxxxx>
Delivery-date: Sat, 04 Jun 2005 19:42:10 +0000
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=tMh4MsycqB9Ovyh3yzjFLv8/8hYMMqKn+L1zXGdQVcMUNmhV+EytwhPZOqvp2Cr8KCpesARYcUEWNXSfKgGODRxCClqSrkmZtFIneEBmGEr0c/MfP8jIbgVVnoULmzFjPjiAw8TaGI5lRrLRpYF+cmQNrQQMabPefyyl3QWO/2k=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <200506040756.26647.dsteklof@xxxxxxxxxx>
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>
References: <A95E2296287EAD4EB592B5DEEFCE0E9D28206E@xxxxxxxxxxxxxxxxxxxxxxxxxxx> <200506040756.26647.dsteklof@xxxxxxxxxx>
Reply-to: Christian.Limpach@xxxxxxxxxxxx
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On 6/4/05, Daniel Stekloff <dsteklof@xxxxxxxxxx> wrote:
> On Saturday 04 June 2005 01:20, Ian Pratt wrote:
> > > :-)
> > >
> > > I asked the same question a week or two ago and yes it is
> > > intended. It provides for easy iteration. I think it is kind
> > > of a hackish interface as it isn't uniform with *all* the
> > > other DOM0 calls. However, it works and once you know to
> > > check the domid return value your code will work as expected.
> >
> > I suppose we could add a flag to indicate whether you were iterating or
> > wanted information on a specific domain. I think currently the only case
> > where we want to iterate is 'xm list'.
> If you're ok with changing the interface, wouldn't it be better for the
> hypercall to get and return just the requested domain info while you move the
> interation to libxc? The library could have two calls, one which calls the
> other: xc_domain_getinfo() and xc_domain_getinfo_list()

This doesn't scale well if your domain id space is sparse, which it
can easily become on a server which has many domains restarting
frequently.  This is the reason for the current behaviour.

I don't see what's wrong with the current behaviour anyway, how hard
is it to check if the call succeeded and then additionally check if
information for the requested domain was returned?  We could avoid the
additional check by having a different return code for when the call
succeeded but returned information for a different domain than the
requested one.


Xen-devel mailing list