e500: Use cpu_index instead of vcpu_dt_id
authorSam Bobroff <sam.bobroff@au1.ibm.com>
Thu, 3 Aug 2017 06:28:36 +0000 (16:28 +1000)
committerDavid Gibson <david@gibson.dropbear.id.au>
Thu, 7 Sep 2017 23:30:55 +0000 (09:30 +1000)
commit6d536570198460743d01a7dc08deda56deee66ab
tree98cfffaeb7354d4eb277725722c6a2f39fd3e251
parente2676b169754c3956bad421a8c80982e651b1b4c
e500: Use cpu_index instead of vcpu_dt_id

The e500 platform code uses the function ppc_get_vcpu_dt_id() to get
an id to put in its device tree.  Which seems like it makes sense, but
ppc_get_vcpu_dt_id() is actually badly named - it only differs from
cpu_index in cases where you're running on KVM HV and the host's
number of threads differs from the guests.  Since KVM HV only supports
PAPR, not e500, it doesn't make sense to use it here.

Simply use the cpu_index instead (which is 'i' in this context
because qemu_get_cpu(i) returns the cpu with cpu_index == i).

Signed-off-by: Sam Bobroff <sam.bobroff@au1.ibm.com>
Reviewed-by: Greg Kurz <groug@kaod.org>
[dwg: Rewrote commit message]
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
hw/ppc/e500.c