summaryrefslogtreecommitdiffstats
path: root/target-s390x/translate.c
diff options
context:
space:
mode:
authorAlexey Kardashevskiy <aik@ozlabs.ru>2014-02-02 01:45:51 +1100
committerAlexander Graf <agraf@suse.de>2014-03-05 03:07:03 +0100
commit0ce470cd4ca88e84e547a3b95159d23ce6be419e (patch)
treefae0578c41afbe617101c39c437650c1db30dcb6 /target-s390x/translate.c
parenta0fcac9c21dcbf481eeb5573a738f55023f5a953 (diff)
downloadhqemu-0ce470cd4ca88e84e547a3b95159d23ce6be419e.zip
hqemu-0ce470cd4ca88e84e547a3b95159d23ce6be419e.tar.gz
target-ppc: add PowerPCCPU::cpu_dt_id
Normally CPUState::cpu_index is used to pick the right CPU for various operations. However default consecutive numbering does not always work for POWERPC. These indexes are reflected in /proc/device-tree/cpus/PowerPC,POWER7@XX and used to call KVM VCPU's ioctls. In order to achieve this, kvmppc_fixup_cpu() was introduced. Roughly speaking, it multiplies cpu_index by the number of threads per core. This approach has disadvantages such as: 1. NUMA configuration stays broken after the fixup; 2. CPU-targeted commands from the QEMU Monitor do not work properly as CPU indexes have been fixed and there is no clear way for the user to know what the new CPU indexes are. This introduces a @cpu_dt_id field in the CPUPPCState struct which is initialized from @cpu_index by default and can be fixed later to meet the device tree requirements. This adds an API to handle @cpu_dt_id. This removes kvmppc_fixup_cpu() as it is not more needed, @cpu_dt_id is calculated in ppc_cpu_realize(). This will be used later in machine code. Signed-off-by: Alexey Kardashevskiy <aik@ozlabs.ru> Acked-by: Mike Day <ncmike@ncultra.org> Signed-off-by: Alexander Graf <agraf@suse.de>
Diffstat (limited to 'target-s390x/translate.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud