cpus-common: ensure auto-assigned cpu_indexes don't clash
authorAlex Bennée <alex.bennee@linaro.org>
Wed, 20 May 2020 14:05:38 +0000 (15:05 +0100)
committerAlex Bennée <alex.bennee@linaro.org>
Wed, 27 May 2020 13:26:49 +0000 (14:26 +0100)
commit716386e397fabbbf9915d49f8bc79673fd2831bb
treeab86eab7413cef4854f370f28ce9e7963e327f53
parentc729a99d27018b8d619544b18926b234b010b733
cpus-common: ensure auto-assigned cpu_indexes don't clash

Basing the cpu_index on the number of currently allocated vCPUs fails
when vCPUs aren't removed in a LIFO manner. This is especially true
when we are allocating a cpu_index for each guest thread in
linux-user where there is no ordering constraint on their allocation
and de-allocation.

[I've dropped the assert which is there to guard against out-of-order
removal as this should probably be caught higher up the stack. Maybe
we could just ifdef CONFIG_SOFTTMU it?]

Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
Acked-by: Igor Mammedow <imammedo@redhat.com>
Cc: Nikolay Igotti <igotti@gmail.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>
Cc: Eduardo Habkost <ehabkost@redhat.com>
Message-Id: <20200520140541.30256-13-alex.bennee@linaro.org>
cpus-common.c