[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Qemu-devel] [PATCH v3 21/21] s390x: allow CPU hotplug in random core-id
|
From: |
David Hildenbrand |
|
Subject: |
[Qemu-devel] [PATCH v3 21/21] s390x: allow CPU hotplug in random core-id order |
|
Date: |
Thu, 7 Sep 2017 22:13:35 +0200 |
SCLP correctly indicates the core-id aka. CPU address for each available
CPU.
As the core-id corresponds to cpu_index, also a newly created kvm vcpu
gets assigned this core-id as vcpu id. So SIGP in the kernel works
correctly (it uses the vcpu id to lookup the correct CPU).
So there should be nothing hindering us from hotplugging CPUs in random
core-id order.
This now makes sure that the output from "query-hotpluggable-cpus"
is completely true. Until now, a specific order is implicit. Performance
vice, hotplugging CPUs in non-sequential order might not be the best thing
to do, as VCPU lookup inside KVM might be a little slower. But that
doesn't hinder us from supporting it.
next_core_id is now used by linux user only.
Signed-off-by: David Hildenbrand <address@hidden>
---
target/s390x/cpu.c | 8 +-------
1 file changed, 1 insertion(+), 7 deletions(-)
diff --git a/target/s390x/cpu.c b/target/s390x/cpu.c
index ad9dcdaaf1..5701a41112 100644
--- a/target/s390x/cpu.c
+++ b/target/s390x/cpu.c
@@ -199,6 +199,7 @@ static void s390_cpu_realizefn(DeviceState *dev, Error
**errp)
#else
/* implicitly set for linux-user only */
cpu->env.core_id = scc->next_core_id;
+ scc->next_core_id++;
#endif
if (cpu_exists(cpu->env.core_id)) {
@@ -206,12 +207,6 @@ static void s390_cpu_realizefn(DeviceState *dev, Error
**errp)
cpu->env.core_id);
goto out;
}
- if (cpu->env.core_id != scc->next_core_id) {
- error_setg(&err, "Unable to add CPU: %" PRIu32
- ", the next available id is %" PRIu32, cpu->env.core_id,
- scc->next_core_id);
- goto out;
- }
/* sync cs->cpu_index and env->core_id. The latter is needed for TCG. */
cs->cpu_index = env->core_id;
@@ -219,7 +214,6 @@ static void s390_cpu_realizefn(DeviceState *dev, Error
**errp)
if (err != NULL) {
goto out;
}
- scc->next_core_id++;
#if !defined(CONFIG_USER_ONLY)
qemu_register_reset(s390_cpu_machine_reset_cb, cpu);
--
2.13.5
- [Qemu-devel] [PATCH v3 11/21] s390x: allow only 1 CPU with TCG, (continued)
- [Qemu-devel] [PATCH v3 11/21] s390x: allow only 1 CPU with TCG, David Hildenbrand, 2017/09/07
- [Qemu-devel] [PATCH v3 12/21] target/s390x: set cpu->id for linux user when realizing, David Hildenbrand, 2017/09/07
- [Qemu-devel] [PATCH v3 13/21] target/s390x: use "core-id" for cpu number/address/id handling, David Hildenbrand, 2017/09/07
- [Qemu-devel] [PATCH v3 14/21] target/s390x: rename next_cpu_id to next_core_id, David Hildenbrand, 2017/09/07
- [Qemu-devel] [PATCH v3 15/21] s390x: print CPU definitions in sorted order, David Hildenbrand, 2017/09/07
- [Qemu-devel] [PATCH v3 16/21] s390x: allow cpu hotplug via device_add, David Hildenbrand, 2017/09/07
- [Qemu-devel] [PATCH v3 17/21] s390x: CPU hot unplug via device_del cannot work for now, David Hildenbrand, 2017/09/07
- [Qemu-devel] [PATCH v3 18/21] s390x: implement query-hotpluggable-cpus, David Hildenbrand, 2017/09/07
- [Qemu-devel] [PATCH v3 19/21] s390x: get rid of cpu_s390x_create(), David Hildenbrand, 2017/09/07
- [Qemu-devel] [PATCH v3 20/21] s390x: generate sclp cpu information from possible_cpus, David Hildenbrand, 2017/09/07
- [Qemu-devel] [PATCH v3 21/21] s390x: allow CPU hotplug in random core-id order,
David Hildenbrand <=