From: Bharata B Rao <bharata@linux.vnet.ibm.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: "Matthew Rosato" <mjrosato@linux.vnet.ibm.com>,
"Eduardo Habkost" <ehabkost@redhat.com>,
agraf@suse.de, qemu-devel@nongnu.org, cornelia.huck@de.ibm.com,
"Andreas Färber" <afaerber@suse.de>,
rth@twiddle.net
Subject: Re: [Qemu-devel] [PATCH 0/4] s390: Allow hotplug of s390 CPUs
Date: Tue, 10 Nov 2015 18:09:33 +0530 [thread overview]
Message-ID: <20151110123933.GA8664@in.ibm.com> (raw)
In-Reply-To: <5640FC4B.600@de.ibm.com>
On Mon, Nov 09, 2015 at 09:04:27PM +0100, Christian Borntraeger wrote:
>
> > Bharata did implement device_add for pseries, I thought.
Yes. For pseries, my patchset did CPU hotplug via device_add and
device_del commands. And that's what I am planning to stick to
going forward.
>
> Seems that the patches did not make it into upstream yet.
> Bharata, is cpu hotplug on pseries still missing?
Yes, the last version I posted is at
https://lists.gnu.org/archive/html/qemu-devel/2015-08/msg00650.html
Andreas mentioned that he would like to see some generic changes for
supporting device_add for CPU, socket vs core level hotplug, defining the
semantics etc. There was some discussion towards that and this is last I
heard about it:
https://lists.nongnu.org/archive/html/qemu-devel/2015-10/msg05347.html
Regards,
Bharata.
prev parent reply other threads:[~2015-11-10 12:40 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
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 [this message]
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=20151110123933.GA8664@in.ibm.com \
--to=bharata@linux.vnet.ibm.com \
--cc=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=borntraeger@de.ibm.com \
--cc=cornelia.huck@de.ibm.com \
--cc=ehabkost@redhat.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.