| commit | 4da7faaeb0c7dd3f7f233165d336c878f78fd1eb | |
| author | Igor Mammedov <imammedo@redhat.com> | |
| Mon, 18 Jul 2016 08:32:36 +0000 (18 10:32 +0200) | ||
| committer | Eduardo Habkost <ehabkost@redhat.com> | |
| Wed, 20 Jul 2016 15:02:19 +0000 (20 12:02 -0300) | ||
| tree | 3dd30cef9b17e9c068e0f94c9c475f7f7011eece | treesnapshot (tar.gz zip) |
| parent | 73360e27850b213327011f7e22e03865b8c0dd5b | commitdiff |
pc: Enforce adding CPUs contiguously and removing them in opposite order
It will still allow us to use cpu_index as migration instance_id
since when CPUs are added contiguously (from the first to the last)
and removed in opposite order, cpu_index stays stable and it's
reproducible on destination side.
While there is work in progress to support migration when there
are holes in cpu_index range resulting from out-of-order plug or
unplug, this patch is intended as an interim solution until
cpu_index usage is cleaned up.
As result of this patch it would be possible to plug/unplug CPUs,
but in limited order that doesn't break migration.
Signed-off-by: Igor Mammedov <imammedo@redhat.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
It will still allow us to use cpu_index as migration instance_id
since when CPUs are added contiguously (from the first to the last)
and removed in opposite order, cpu_index stays stable and it's
reproducible on destination side.
While there is work in progress to support migration when there
are holes in cpu_index range resulting from out-of-order plug or
unplug, this patch is intended as an interim solution until
cpu_index usage is cleaned up.
As result of this patch it would be possible to plug/unplug CPUs,
but in limited order that doesn't break migration.
Signed-off-by: Igor Mammedov <imammedo@redhat.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
| hw/i386/pc.c | diffblobblamehistory |