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: "Kip Macy" <kip.macy@xxxxxxxxx>, "Xen Developers" <xen-devel@xxxxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] "virtual cluster" debug support
From: "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
Date: Fri, 18 Mar 2005 00:35:10 -0000
Cc: <ian.pratt@xxxxxxxxxxxx>
Delivery-date: Fri, 18 Mar 2005 00:36:51 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
Thread-index: AcUrTlVNnXcgiZLkS+6roA1aG4fLPwAAxI7A
Thread-topic: [Xen-devel] "virtual cluster" debug support
> To my local tree I'm about to commit support for the notion of a
> "virtual cluster" for debugging purposes. The idea is that when one
> node (domain) in a cluster hits a breakpoint, all the other nodes are
> paused so that the first node doesn't get voted out of the quorum. I'd
> be very surprised if there are other potential users for this
> functionality, but I'm asking just in case.
> 
> The current implementation is done in such a way as to minimally
> perturb the existing interfaces to make it easy to carry it as an
> outside patch indefinitely. However, if others might use, it could be
> implemented more cleanly.

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_ide95&alloc_id396&op=click
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel