From mboxrd@z Thu Jan  1 00:00:00 1970
From: Kip Macy <kip.macy@gmail.com>
Subject: semantics of GETDOMAININFO
Date: Sun, 8 May 2005 14:39:39 -0700
Message-ID: <b1fa291705050814397139e089@mail.gmail.com>
Reply-To: Kip Macy <kip.macy@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Return-path: <xen-devel-bounces@lists.xensource.com>
Content-Disposition: inline
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: xen-devel <xen-devel@lists.xensource.com>
List-Id: xen-devel@lists.xenproject.org

One of the things that I've always thought was weird, but didn't pay
too close attention to is the fact that GETDOMAININFO will return a
valid result even if we give it a domid that is no longer valid.
Looking at the code we get back the first valid domain after the domid
we pass in.

What is the reason for this design choice? When I request the
attributes of a process I don't get the attributes for the next pid up
with a pid field set to the process id of the process I actually got
the attributes for.

       -Kip