xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: ian.campbell@citrix.com, ian.jackson@eu.citrix.com,
	jbeulich@suse.com, keir@xen.org, tim@xen.org
Cc: Boris Ostrovsky <boris.ostrovsky@oracle.com>,
	roger.pau@citrix.com, wei.liu2@citrix.com,
	xen-devel@lists.xen.org
Subject: [PATCH] docs: Specify VCPU hotplug procedure for HVMlite guests
Date: Wed,  3 Feb 2016 11:11:39 -0500	[thread overview]
Message-ID: <1454515899-1787-1-git-send-email-boris.ostrovsky@oracle.com> (raw)

HVMlite VCPUs can be added and removed by toggling 'availability'
value of VCPU's xenstore entry.

Signed-off-by: Boris Ostrovsky <boris.ostrovsky@oracle.com>
---

I am not sure this is really needed since it's no different from how we
do hotplug for PV or HVM/qemu-trad guests.

I may have been a bit too grandiose by describing yesterday's patch as
"add CPU hotplug support". It was really enabling existing functionality.

 docs/misc/hvmlite.markdown | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/docs/misc/hvmlite.markdown b/docs/misc/hvmlite.markdown
index c1b75c6..1a2e866 100644
--- a/docs/misc/hvmlite.markdown
+++ b/docs/misc/hvmlite.markdown
@@ -80,3 +80,8 @@ are used in order to bring up secondary vCPUs:
  * `VCPUOP_down` is used to bring down a vCPU.
 
  * `VCPUOP_is_up` is used to scan the number of available vCPUs.
+
+## VCPU hotplug ##
+
+VCPUs can be hot-plugged or hot-removed by writing "online" or "offline" to
+xenstore's /local/domain/<domain_id>/cpu/<vcpu_id>/availability entry
-- 
2.1.0

             reply	other threads:[~2016-02-03 16:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-03 16:11 Boris Ostrovsky [this message]
2016-02-03 16:20 ` [PATCH] docs: Specify VCPU hotplug procedure for HVMlite guests Wei Liu

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=1454515899-1787-1-git-send-email-boris.ostrovsky@oracle.com \
    --to=boris.ostrovsky@oracle.com \
    --cc=ian.campbell@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=jbeulich@suse.com \
    --cc=keir@xen.org \
    --cc=roger.pau@citrix.com \
    --cc=tim@xen.org \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xen.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).