xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Anthony PERARD <anthony.perard@citrix.com>
To: Xen Devel <xen-devel@lists.xen.org>
Cc: Anthony PERARD <anthony.perard@citrix.com>,
	Stefano Stabellini <stefano.stabellini@citrix.com>,
	Ian Campbell <ian.campbell@citrix.com>
Subject: [PATCH v4 0/2] CPU hotplug for qemu-xen
Date: Tue, 25 Jun 2013 11:07:51 +0100	[thread overview]
Message-ID: <1372154873-25790-1-git-send-email-anthony.perard@citrix.com> (raw)

Hi all,

This series implements the 'cpu-add' QMP command to hotplug CPU with qemu-xen.

When using adding vcpus with this series, libxl will report many "error". This
is because libxl call the QMP command 'cpu-add' for every plugged vcpus, even
those that have been plugged before. There is currently no way to list cpus
that are plugged by QEMU. Also, the way errors are handled by libxl_qmp those
not help yet to suppress this error printing.

Unplug of vcpu is not supported by the series.

Change since the last set:
  - ignore the return value of libxl__qmp_cpu_add as it those not give any
    usefull information.

And before (v2-v3):
  - use more and different macro in the libxl patch.

Anthony PERARD (2):
  libxl: Add "cpu-add" QMP command.
  libxl: Use QMP cpu-add to hotplug CPU with qemu-xen.

 tools/libxl/libxl.c          | 47 ++++++++++++++++++++++++++++++++++++++------
 tools/libxl/libxl_internal.h |  2 ++
 tools/libxl/libxl_qmp.c      | 21 ++++++++++++++++++++
 3 files changed, 64 insertions(+), 6 deletions(-)

-- 
Anthony PERARD

             reply	other threads:[~2013-06-25 10:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-25 10:07 Anthony PERARD [this message]
2013-06-25 10:07 ` [PATCH v4 1/2] libxl: Add "cpu-add" QMP command Anthony PERARD
2013-06-25 10:07 ` [PATCH v4 2/2] libxl: Use QMP cpu-add to hotplug CPU with qemu-xen Anthony PERARD
2013-06-26 10:56   ` George Dunlap
2013-06-26 13:56   ` Ian Campbell

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=1372154873-25790-1-git-send-email-anthony.perard@citrix.com \
    --to=anthony.perard@citrix.com \
    --cc=ian.campbell@citrix.com \
    --cc=stefano.stabellini@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).