From: Christian Borntraeger <borntraeger@de.ibm.com>
To: "Andreas Färber" <afaerber@suse.de>,
"Matthew Rosato" <mjrosato@linux.vnet.ibm.com>,
qemu-devel@nongnu.org
Cc: cornelia.huck@de.ibm.com, agraf@suse.de, rth@twiddle.net
Subject: Re: [Qemu-devel] [PATCH 0/4] s390: Allow hotplug of s390 CPUs
Date: Mon, 9 Nov 2015 16:37:54 +0100 [thread overview]
Message-ID: <5640BDD2.9040102@de.ibm.com> (raw)
In-Reply-To: <5640BD5B.9050204@de.ibm.com>
Am 09.11.2015 um 16:35 schrieb Christian Borntraeger:
> Am 09.11.2015 um 16:28 schrieb Andreas Färber:
>> Hi,
>>
>> Am 09.11.2015 um 16:17 schrieb Matthew Rosato:
>>> 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.
>>
>> What exactly is still missing for you to use the standard device_add?
>>
>> Last time I checked (a while ago...) some patches were stuck on the x86
>> side, and I don't recall hearing any feedback from the s390x side in my
>> KVM Forum CPU hotplug session.
>
> libvirt uses "cpu-add" unconditionally for hotplugging, so we certainly
> want to support that.
Sorry, hit send too early. I assume you want us to support device_add of
a CPU in addition to that. Correct?
next prev parent reply other threads:[~2015-11-09 15:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-09 15:17 [Qemu-devel] [PATCH 0/4] s390: Allow hotplug of s390 CPUs Matthew Rosato
2015-11-09 15:17 ` [Qemu-devel] [PATCH 1/4] s390x/cpu: Cleanup init in preparation for hotplug Matthew Rosato
2015-11-09 15:17 ` [Qemu-devel] [PATCH 2/4] s390x/cpu: Set initial CPU state in common routine Matthew Rosato
2015-11-09 15:17 ` [Qemu-devel] [PATCH 3/4] s390x/cpu: Add function to set CPU state Matthew Rosato
2015-11-09 15:17 ` [Qemu-devel] [PATCH 4/4] s390x/cpu: Allow hotplug of CPUs Matthew Rosato
2015-11-09 15:28 ` [Qemu-devel] [PATCH 0/4] s390: Allow hotplug of s390 CPUs Andreas Färber
2015-11-09 15:35 ` Christian Borntraeger
2015-11-09 15:37 ` Christian Borntraeger [this message]
2015-11-09 15:55 ` Christian Borntraeger
2015-11-09 16:07 ` Matthew Rosato
2015-11-09 15:56 ` Andreas Färber
2015-11-09 20:04 ` Christian Borntraeger
2015-11-10 12:39 ` Bharata B Rao
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=5640BDD2.9040102@de.ibm.com \
--to=borntraeger@de.ibm.com \
--cc=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=cornelia.huck@de.ibm.com \
--cc=mjrosato@linux.vnet.ibm.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 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.