summaryrefslogtreecommitdiff
path: root/include/hw/ppc/pnv_xscom.h
diff options
context:
space:
mode:
authorDavid Gibson <david@gibson.dropbear.id.au>2016-11-01 10:25:29 +1100
committerDavid Gibson <david@gibson.dropbear.id.au>2016-11-15 10:05:51 +1100
commit8bd9530e1302566e9dc71abe04346ca7d16613b1 (patch)
tree98f9ae20e9a505a5b94261072f01121f6d88552e /include/hw/ppc/pnv_xscom.h
parent5c69452c1456fcefaa9d7505c06b82c48b459dff (diff)
downloadqemu-8bd9530e1302566e9dc71abe04346ca7d16613b1.tar.gz
powernv: CPU compatibility modes don't make sense for powernv
powernv has some code (derived from the spapr equivalent) used in device tree generation which depends on the CPU's compatibility mode / logical PVR. However, compatibility modes don't make sense on powernv - at least not as a property controlled by the host - because the guest in powernv has full hypervisor level access to the virtual system, and so owns the PCR (Processor Compatibility Register) which implements compatiblity modes. Note: the new logic doesn't take into account kvmppc_smt_threads() like the old version did. However, if core->nr_threads exceeds kvmppc_smt_threads() then things will already be broken and clamping the value in the device tree isn't going to save us. Signed-off-by: David Gibson <david@gibson.dropbear.id.au> Reviewed-by: Greg Kurz <groug@kaod.org> Reviewed-by: Thomas Huth <thuth@redhat.com>
Diffstat (limited to 'include/hw/ppc/pnv_xscom.h')
0 files changed, 0 insertions, 0 deletions