diff options
| author | Igor Mammedov <imammedo@redhat.com> | 2016-07-25 11:59:21 +0200 |
|---|---|---|
| committer | Eduardo Habkost <ehabkost@redhat.com> | 2016-07-26 15:32:01 -0300 |
| commit | a07f953ef4ef48058c24fb50b49e6fa28bf5f5f4 (patch) | |
| tree | 5715286d5955f261ff6e4d1c76a6fd9ee4a9fec7 /contrib | |
| parent | 8b1b835035fda831b405c1947210efcf758a7ca8 (diff) | |
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>
Diffstat (limited to 'contrib')
0 files changed, 0 insertions, 0 deletions