From: "Andreas Färber" <afaerber@suse.de>
To: Jens Freimann <jfrei@linux.vnet.ibm.com>
Cc: Eduardo Habkost <ehabkost@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>,
Alexander Graf <agraf@suse.de>,
Christian Borntraeger <borntraeger@de.ibm.com>,
Cornelia Huck <cornelia.huck@de.ibm.com>,
Igor Mammedov <imammedo@redhat.com>
Subject: Re: [Qemu-devel] [RFC/PATCH 0/1] cpu hotplug for s390
Date: Wed, 17 Apr 2013 20:06:37 +0200 [thread overview]
Message-ID: <516EE4AD.3090508@suse.de> (raw)
In-Reply-To: <1364971345-3110-1-git-send-email-jfrei@linux.vnet.ibm.com>
Hi Jens,
Am 03.04.2013 08:42, schrieb Jens Freimann:
> this is what our approach to CPU hotplug looks like.
> With respect to Igor's CPU hotplug series, how should we proceed?
> Should we change the interface to
> qemu_system_cpu_add_notifier/qemu_system_cpu_hotplug_request/cpu-add etc?
I am wondering if my recent qdev/device_add fixes would allow to
implement CPU hot-add via device_add for s390x?
Background is that for x86 we currently have a flat CPU core/thread
namespace but would need to deal with sockets, cores and threads to get
topologies right. I assume there are no such issues on s390x, so that
the vCPU to CPUState mapping could stay 1:1?
> Feedback regarding the non-API part is also highly welcome!
I did spot some QOM'ish nitpicks in the qdev_create() but I am wondering
if you and Alex see an urgent need to get this into 1.5 during the Soft
Freeze or whether we can just align it to x86 work for now and deal with
it after the release?
Regards,
Andreas
> Thang Pham (1):
> s390: implement CPU hotplug
>
> hmp-commands.hx | 14 +++++
> hw/s390x/Makefile.objs | 2 +-
> hw/s390x/event-facility.c | 9 ++++
> hw/s390x/event-facility.h | 3 ++
> hw/s390x/s390-virtio.c | 34 +++++++++---
> hw/s390x/sclp.c | 134 +++++++++++++++++++++++++++++++++++++++++++++-
> hw/s390x/sclp.h | 47 +++++++++++++++-
> include/sysemu/sysemu.h | 1 +
> monitor.c | 31 +++++++++++
> target-s390x/cpu.c | 59 ++++++++++++++++++++
> target-s390x/cpu.h | 7 +++
> target-s390x/helper.c | 43 +++++++++++++++
> vl.c | 6 +++
> 13 files changed, 379 insertions(+), 11 deletions(-)
>
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2013-04-17 18:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-03 6:42 [Qemu-devel] [RFC/PATCH 0/1] cpu hotplug for s390 Jens Freimann
2013-04-03 6:42 ` [Qemu-devel] [RFC/PATCH 1/1] s390: implement CPU hotplug Jens Freimann
2013-04-18 12:54 ` Igor Mammedov
2013-04-17 18:06 ` Andreas Färber [this message]
2013-04-17 18:14 ` [Qemu-devel] [RFC/PATCH 0/1] cpu hotplug for s390 Eduardo Habkost
2013-04-19 7:51 ` Jens Freimann
2013-04-19 13:16 ` Andreas Färber
2013-04-19 14:28 ` Igor Mammedov
2013-04-19 19:13 ` Christian Borntraeger
2013-04-19 19:58 ` Eduardo Habkost
-- strict thread matches above, loose matches on Subject: below --
2013-05-03 13:50 Jason J. Herne
2013-05-03 14:13 ` Igor Mammedov
2013-05-03 14:22 ` Andreas Färber
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=516EE4AD.3090508@suse.de \
--to=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=borntraeger@de.ibm.com \
--cc=cornelia.huck@de.ibm.com \
--cc=ehabkost@redhat.com \
--cc=imammedo@redhat.com \
--cc=jfrei@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.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).