WARNING - OLD ARCHIVES

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

xen-devel

Re: [Xen-devel] "virtual cluster" debug support

To: Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] "virtual cluster" debug support
From: Kip Macy <kip.macy@xxxxxxxxx>
Date: Thu, 17 Mar 2005 16:43:30 -0800
Cc: Xen Developers <xen-devel@xxxxxxxxxxxxxxxxxxxxx>, ian.pratt@xxxxxxxxxxxx
Delivery-date: Fri, 18 Mar 2005 01:00:32 +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:references; b=us/ZmTZseuji/Cxtmd5b3GelxJhqsrCVnf92Dukm7bWRdE/yaZyzsjo3w3rlV7nBqO1FgxJ8VmMDuWLBtBmPxu1AHeuzDKno6ymwS/n8tvgqAMbiHJR+G27glwFMXOeunwAvM1eCql1iQTHX7p7HMHXsxQF9oNGrKZqkgZW/iI8=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <A95E2296287EAD4EB592B5DEEFCE0E9D1E3722@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
References: <A95E2296287EAD4EB592B5DEEFCE0E9D1E3722@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
Reply-to: Kip Macy <kip.macy@xxxxxxxxx>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
That is almost exactly what I've done, except I didn't add a group id
and I used pad0 builddomain for a partner id (yes I know it is gross)
so the group would get set at buildtime.

And of course one cannot set domain 0 as a partner.
 

       -Kip


> I guess the 'nice' way of doing this would be to have a notion of
> 'domain groups', akin to process groups. This would be pretty trivial to
> hack in:
>  * add a group_id integer to the domain struct. 0 is special = not
> grouped
>  * add a domains struct * to create a circular list of domains in same
> group
>  * add a dom0_op to set the group of a domain (scan domain list, adjust
> circular list)
>  * on break point follow circular list issuing pause_domain(d)
> 
> Ian
>


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel