From: Matthew Rosato <mjrosato@linux.vnet.ibm.com>
To: Igor Mammedov <imammedo@redhat.com>
Cc: dahi@linux.vnet.ibm.com, qemu-devel@nongnu.org, 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: Re: [Qemu-devel] [PATCH v5 6/6] s390x/cpu: Allow hotplug of CPUs
Date: Fri, 19 Feb 2016 09:40:13 -0500 [thread overview]
Message-ID: <56C7294D.6090506@linux.vnet.ibm.com> (raw)
In-Reply-To: <20160219152835.69d75f7a@nial.brq.redhat.com>
On 02/19/2016 09:28 AM, Igor Mammedov wrote:
> On Thu, 18 Feb 2016 23:03:37 -0500
> Matthew Rosato <mjrosato@linux.vnet.ibm.com> wrote:
>
>> Implement cpu hotplug routine and add the machine hook.
>>
>> Signed-off-by: Matthew Rosato <mjrosato@linux.vnet.ibm.com>
>> ---
>> hw/s390x/s390-virtio-ccw.c | 1 +
>> target-s390x/cpu.c | 45 +++++++++++++++++++++++++++++++++++++++++++++
>> target-s390x/cpu.h | 1 +
>> 3 files changed, 47 insertions(+)
>>
>> diff --git a/hw/s390x/s390-virtio-ccw.c b/hw/s390x/s390-virtio-ccw.c
>> index 31c1082..3be41ee 100644
>> --- a/hw/s390x/s390-virtio-ccw.c
>> +++ b/hw/s390x/s390-virtio-ccw.c
>> @@ -199,6 +199,7 @@ static void ccw_machine_class_init(ObjectClass *oc, void *data)
>>
>> mc->init = ccw_init;
>> mc->reset = s390_machine_reset;
>> + mc->hot_add_cpu = s390_hot_add_cpu;
>> mc->block_default_type = IF_VIRTIO;
>> mc->no_cdrom = 1;
>> mc->no_floppy = 1;
>> diff --git a/target-s390x/cpu.c b/target-s390x/cpu.c
>> index 8dfd063..99394ec 100644
>> --- a/target-s390x/cpu.c
>> +++ b/target-s390x/cpu.c
>> @@ -32,6 +32,12 @@
>> #include "trace.h"
>> #ifndef CONFIG_USER_ONLY
>> #include "sysemu/arch_init.h"
>> +#include "sysemu/sysemu.h"
>> +#include "hw/boards.h"
>> +#include "hw/s390x/sclp.h"
>> +#include "qom/cpu.h"
>> +
>> +#define last_cpu QTAILQ_LAST(&cpus, CPUTailQ)
> this should be in qom/cpu.h, maybe a separate patch
>
I did that originally, but trips up due to usage of the phrase
'last_cpu' elsewhere in the code. Looking now, hw/intc/openpic.c is the
culprit.
I could split this out into a patch that adds last_cpu to qom/cpu.h +
changes the variable name in openpic.c.
Or use a different name for the macro. (cpu_last for example).
Preference?
>> #endif
>>
>> #define CR0_RESET 0xE0UL
>> @@ -211,6 +217,12 @@ static void s390_cpu_realizefn(DeviceState *dev, Error **errp)
>> #endif
>>
>> scc->parent_realize(dev, errp);
>> +
>> +#if !defined(CONFIG_USER_ONLY)
>> + if (dev->hotplugged) {
>> + raise_irq_cpu_hotplug();
>> + }
>> +#endif
>> }
>>
>> static void s390_cpu_initfn(Object *obj)
>> @@ -254,6 +266,39 @@ static void s390_cpu_finalize(Object *obj)
>> }
>>
>> #if !defined(CONFIG_USER_ONLY)
>> +void s390_hot_add_cpu(const int64_t id, Error **errp)
>> +{
> this one looks like a func that belongs to board and should
> be a static in hw/s390x/s390-virtio-ccw.c
>
OK, sure.
Matt
next prev parent reply other threads:[~2016-02-19 14:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-19 4:03 [Qemu-devel] [PATCH v5 0/6] Allow hotplug of s390 CPUs Matthew Rosato
2016-02-19 4:03 ` [Qemu-devel] [PATCH v5 1/6] s390x/cpu: Cleanup init in preparation for hotplug Matthew Rosato
2016-02-19 4:03 ` [Qemu-devel] [PATCH v5 2/6] s390x/cpu: Set initial CPU state in common routine Matthew Rosato
2016-02-19 4:03 ` [Qemu-devel] [PATCH v5 3/6] s390x/cpu: Move some CPU initialization into realize Matthew Rosato
2016-02-19 4:03 ` [Qemu-devel] [PATCH v5 4/6] s390x/cpu: Add CPU property links Matthew Rosato
2016-02-19 4:03 ` [Qemu-devel] [PATCH v5 5/6] s390/virtio-ccw: Add hotplug handler Matthew Rosato
2016-02-19 14:33 ` Igor Mammedov
2016-02-19 4:03 ` [Qemu-devel] [PATCH v5 6/6] s390x/cpu: Allow hotplug of CPUs Matthew Rosato
2016-02-19 14:28 ` Igor Mammedov
2016-02-19 14:40 ` Matthew Rosato [this message]
2016-02-19 16:18 ` 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=56C7294D.6090506@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=imammedo@redhat.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).