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: Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] DOM0_GETDOMAININFO intended behavior
From: Kip Macy <kip.macy@xxxxxxxxx>
Date: Sat, 4 Jun 2005 17:17:31 -0700
Cc: Daniel Stekloff <dsteklof@xxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, Christian.Limpach@xxxxxxxxxxxx
Delivery-date: Sun, 05 Jun 2005 00:16:44 +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=GTRnrb7LGfb5WhQDf9RHpdarQKTu1kXYR99/c73Ksaai85fx84TQsvyjGrVv1lovD5XzpOfW3/GdGwJ+bYDltM03Z3FbQwc0lNcRUCto94req78W7Y1pxTgdysWkzTQAp5eS9kOk2qdkZDUUbU7WZP3hiqeVijooVWOYJOExJEU=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <A95E2296287EAD4EB592B5DEEFCE0E9D282077@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
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: <A95E2296287EAD4EB592B5DEEFCE0E9D282077@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
Reply-to: Kip Macy <kip.macy@xxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
> 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.

I agree. That way the default behaviour would be what most people expect.


> Ian
> > 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