From: Ryan Harper <ryanh@us.ibm.com>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: Ryan Harper <ryanh@us.ibm.com>, xen-devel@lists.xensource.com
Subject: Re: [PATCH] add dom0 vcpu hotplug control
Date: Tue, 7 Jun 2005 17:59:41 -0500 [thread overview]
Message-ID: <20050607225941.GI28421@us.ibm.com> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D282108@liverpoolst.ad.cl.cam.ac.uk>
* Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk> [2005-06-07 17:54]:
>
> > That would work. Moving forward, there may be more per-VCPU
> > info that we want to collect and that it would make sense to
> > factor out per-VCPU info from DOM0_GETDOMINFO and create a
> > DOM0_GETVCPUINFO call. If that is not desirable at this
> > point, I can work with DOM0_GETVCPUCONTEXT.
>
> I think we can live with the summary provided by DOM0_GETDOMINFO for the
> moment.
OK.
> I presume the n_cpu and vcpu_to_cpu[] fields are updated to show down'ed
> VCPUs?
Not at the moment, but they should. I think if those are updated, I can
extract state info from those variables without having to issue
DOM0_VCPUCONTEXT ops. DOM0_VCPUCONTEXT should still skip vcpu's
that are not up. Thanks for the review. I'll resubmit with those
changes.
--
Ryan Harper
Software Engineer; Linux Technology Center
IBM Corp., Austin, Tx
(512) 838-9253 T/L: 678-9253
ryanh@us.ibm.com
next prev parent reply other threads:[~2005-06-07 22:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-07 22:53 [PATCH] add dom0 vcpu hotplug control Ian Pratt
2005-06-07 22:59 ` Ryan Harper [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-06-07 22:26 Ian Pratt
2005-06-07 22:35 ` Ryan Harper
2005-06-07 22:02 Ryan Harper
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=20050607225941.GI28421@us.ibm.com \
--to=ryanh@us.ibm.com \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--cc=xen-devel@lists.xensource.com \
/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.