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:35:14 -0500 [thread overview]
Message-ID: <20050607223514.GH28421@us.ibm.com> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D282107@liverpoolst.ad.cl.cam.ac.uk>
* Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk> [2005-06-07 17:27]:
>
>
> > -----Original Message-----
> > From: xen-devel-bounces@lists.xensource.com
> > [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of
> > Ryan Harper
> > Sent: 07 June 2005 23:03
> > To: xen-devel@lists.xensource.com
> > Subject: [Xen-devel] [PATCH] add dom0 vcpu hotplug control
> >
> > This patch adds new control messages for vcpu hotplug events.
> > Via the xm vcpu_hotplug sub-program, VCPUS in domains can be
> > enabled/disabled when CONFIG_HOTPLUG_CPU is enabled in the
> > target domain's kernel.
> >
> > Currently there is nothing that tracks whether a VCPU is up or down.
> > My previous [1]patch added a new per-VCPU flag (VCPUF_down)
> > which could be used to keep track of which VCPUS are up and
> > down. Right now, there isn't a hypercall that returns the
> > per-VCPU flag status (something equivalent to the per-domain
> > flags in get_dominfo ). Have we thought about a
> > get_vcpu_info hypercall? I'd like to get that implemented so
> > I can report VCPU state in the xm list --vcpus output. That
> > would also make it easier to skip sending control messages
> > that don't change the VCPU's state (e.g. sending a down
> > message to a vcpu that is already down).
>
> I haven't looked at the code, but can you not use DOM0_GETVCPUCONTEXT to
> iterate over all the VCPUs for a domain? (e.g. if you ask for VCPU N and
> it doesn't exist (isn't up) you'll get the state for the next highest
> numbered one, or ESRCH if there isn't one) That's the behaviour I'd
> expect.
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.
--
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:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-07 22:26 [PATCH] add dom0 vcpu hotplug control Ian Pratt
2005-06-07 22:35 ` Ryan Harper [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-06-07 22:53 Ian Pratt
2005-06-07 22:59 ` 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=20050607223514.GH28421@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.