Igor Mammedov a07f953ef4 exec: Set cpu_index only if it's not been explictly set ... It keeps the legacy behavior for all users that doesn't care about stable cpu_index value, but would allow boards that would support device_add/device_del to set stable cpu_index that won't depend on order in which cpus are created/destroyed. While at that simplify cpu_get_free_index() as cpu_index generated by USER_ONLY and softmmu variants is the same since none of the users support cpu-remove so far, except of not yet released spapr/x86 device_add/delr, which will be altered by follow up patches to set stable cpu_index manually. Signed-off-by: Igor Mammedov <imammedo@redhat.com> Reviewed-by: David Gibson <david@gibson.dropbear.id.au> Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>		2016-07-26 15:32:01 -03:00
..
container.c
cpu.c	exec: Set cpu_index only if it's not been explictly set	2016-07-26 15:32:01 -03:00
Makefile.objs
object_interfaces.c	opts-visitor: Favor new visit_free() function	2016-07-06 10:52:04 +02:00
object.c	qapi: Add new visit_complete() function	2016-07-06 10:52:04 +02:00
qom-qobject.c	qapi: Add new visit_complete() function	2016-07-06 10:52:04 +02:00
trace-events