From: Kip Macy <kip.macy@gmail.com>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: Xen Developers <xen-devel@lists.sourceforge.net>, ian.pratt@cl.cam.ac.uk
Subject: Re: "virtual cluster" debug support
Date: Sat, 19 Mar 2005 00:00:56 -0800 [thread overview]
Message-ID: <b1fa2917050319000056e69d4f@mail.gmail.com> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D1E3722@liverpoolst.ad.cl.cam.ac.uk>
Please review the following diff. I will follow up with a signed off
patch with the required fixes.
http://www.fsmware.com/xenofreebsd/gdb/050318/clusterbkpt.diff
-Kip
On Fri, 18 Mar 2005 00:35:10 -0000, Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk> wrote:
> > 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_id=6595&alloc_id=14396&op=click
next prev parent reply other threads:[~2005-03-19 8:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-18 0:35 "virtual cluster" debug support Ian Pratt
2005-03-18 0:43 ` Kip Macy
2005-03-19 8:00 ` Kip Macy [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-03-19 23:33 Ian Pratt
2005-03-19 23:13 Ian Pratt
2005-03-19 23:23 ` Kip Macy
2005-03-19 22:19 Ian Pratt
2005-03-19 22:41 ` Kip Macy
2005-03-18 0:04 Kip Macy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b1fa2917050319000056e69d4f@mail.gmail.com \
--to=kip.macy@gmail.com \
--cc=ian.pratt@cl.cam.ac.uk \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--cc=xen-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.