From: Matthew Rosato <mjrosato@linux.vnet.ibm.com>
To: qemu-devel@nongnu.org
Cc: dahi@linux.vnet.ibm.com, agraf@suse.de, borntraeger@de.ibm.com,
bharata@linux.vnet.ibm.com, cornelia.huck@de.ibm.com,
pbonzini@redhat.com, afaerber@suse.de, rth@twiddle.net
Subject: [Qemu-devel] [PATCH v4 0/5] Allow hotplug of s390 CPUs
Date: Wed, 17 Feb 2016 15:12:30 -0500 [thread overview]
Message-ID: <1455739955-28139-1-git-send-email-mjrosato@linux.vnet.ibm.com> (raw)
Changes from v3-v4:
* Drop patches related to device_add / device_del
* Add patch to enable cpu_add for s390x.
**************
As discussed in the KVM call, we will go ahead with cpu_add for
s390x to get cpu hotplug functionality in s390x now, until
architectures that require a more robust hotplug interface
settle on a design.
To configure a guest with 2 CPUs online at
boot and 4 maximum:
qemu -smp 2,maxcpus=4
Or, when using libvirt:
<domain>
...
<vcpu current="2">4</vcpu>
...
</domain>
To subsequently hotplug a CPU:
Issue 'cpu-add <id>' from qemu monitor, or use virsh setvcpus --count <n>
<domain>, where <n> is the total number of desired guest CPUs.
At this point, the guest must bring the CPU online for use -- This can be
achieved via "echo 1 > /sys/devices/system/cpu/cpuX/online" or via a management
tool like cpuplugd.
This patch set is based on work previously done by Jason Herne.
Matthew Rosato (5):
s390x/cpu: Cleanup init in preparation for hotplug
s390x/cpu: Set initial CPU state in common routine
s390x/cpu: Move some CPU initialization into realize
s390x/cpu: Add functions to register CPU state
s390x/cpu: Allow hotplug of CPUs
hw/s390x/s390-virtio-ccw.c | 3 ++-
hw/s390x/s390-virtio.c | 55 +++++++++++++++++++++++++++-----------
hw/s390x/s390-virtio.h | 2 +-
target-s390x/cpu.c | 66 +++++++++++++++++++++++++++++++++++++++++++---
target-s390x/cpu.h | 2 ++
5 files changed, 107 insertions(+), 21 deletions(-)
--
1.9.1
next reply other threads:[~2016-02-17 20:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-17 20:12 Matthew Rosato [this message]
2016-02-17 20:12 ` [Qemu-devel] [PATCH v4 1/5] s390x/cpu: Cleanup init in preparation for hotplug Matthew Rosato
2016-02-17 20:12 ` [Qemu-devel] [PATCH v4 2/5] s390x/cpu: Set initial CPU state in common routine Matthew Rosato
2016-02-17 20:12 ` [Qemu-devel] [PATCH v4 3/5] s390x/cpu: Move some CPU initialization into realize Matthew Rosato
2016-02-17 20:12 ` [Qemu-devel] [PATCH v4 4/5] s390x/cpu: Add functions to register CPU state Matthew Rosato
2016-02-18 8:57 ` David Hildenbrand
2016-02-18 9:36 ` Igor Mammedov
2016-02-18 20:22 ` Matthew Rosato
2016-02-17 20:12 ` [Qemu-devel] [PATCH v4 5/5] s390x/cpu: Allow hotplug of CPUs Matthew Rosato
2016-02-18 9:03 ` David Hildenbrand
2016-02-18 9:41 ` Igor Mammedov
2016-02-18 9:46 ` David Hildenbrand
2016-02-18 17:59 ` Igor Mammedov
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=1455739955-28139-1-git-send-email-mjrosato@linux.vnet.ibm.com \
--to=mjrosato@linux.vnet.ibm.com \
--cc=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=bharata@linux.vnet.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=cornelia.huck@de.ibm.com \
--cc=dahi@linux.vnet.ibm.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.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 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).