diff options
| author | David Hildenbrand <david@redhat.com> | 2017-09-13 15:24:17 +0200 |
|---|---|---|
| committer | Cornelia Huck <cohuck@redhat.com> | 2017-09-19 18:31:32 +0200 |
| commit | a1422723f75a8b73f952fc0d7b38a702ed97e5e0 (patch) | |
| tree | 8260463c374ba574263e0c819064019d60a55868 /hw/xen/xen_backend.c | |
| parent | bb535bb67e5d2271614a08593abf6aba30e598ba (diff) | |
| download | qemu-a1422723f75a8b73f952fc0d7b38a702ed97e5e0.zip qemu-a1422723f75a8b73f952fc0d7b38a702ed97e5e0.tar.gz qemu-a1422723f75a8b73f952fc0d7b38a702ed97e5e0.tar.bz2 | |
s390x: allow CPU hotplug in random core-id order
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 <david@redhat.com>
Message-Id: <20170913132417.24384-23-david@redhat.com>
Reviewed-by: Igor Mammedov <imammedo@redhat.com>
Signed-off-by: Cornelia Huck <cohuck@redhat.com>
Diffstat (limited to 'hw/xen/xen_backend.c')
0 files changed, 0 insertions, 0 deletions