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 15:23:27 -0800 [thread overview]
Message-ID: <b1fa29170503191523761b2438@mail.gmail.com> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D1E3763@liverpoolst.ad.cl.cam.ac.uk>
> GET/SETDOMAININFO is used for get/setting the CPU execution state. The
> IN parameteres are used for selecting an execution context, and adding a
> groupid parameter to them is certainly very odd.
Good point. That would lead me to believe that they are slightly
misnamed. Wouldn't GET/SETDOMAINCONTEXT be more apt?
> I don't think the patch should touch xc_linux_build either -- setting
> the groupid is a generic thing that the tools can do after creating the
> domain.
Fair enough. I can easily get carried away with what is most expedient
for me. Which is why I sent a diff and not a patch. I knew it would
come under the knife.
When I check in a file, how do I make sure it stays executable?
-Kip
-------------------------------------------------------
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 23:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-19 23:13 "virtual cluster" debug support Ian Pratt
2005-03-19 23:23 ` Kip Macy [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-03-19 23:33 Ian Pratt
2005-03-19 22:19 Ian Pratt
2005-03-19 22:41 ` Kip Macy
2005-03-18 0:35 Ian Pratt
2005-03-18 0:43 ` Kip Macy
2005-03-19 8:00 ` 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=b1fa29170503191523761b2438@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.