All of lore.kernel.org
 help / color / mirror / Atom feed
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: Thu, 17 Mar 2005 16:43:30 -0800	[thread overview]
Message-ID: <b1fa291705031716436706245@mail.gmail.com> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D1E3722@liverpoolst.ad.cl.cam.ac.uk>

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

  reply	other threads:[~2005-03-18  0:43 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 [this message]
2005-03-19  8:00 ` Kip Macy
  -- 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=b1fa291705031716436706245@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.