aboutsummaryrefslogtreecommitdiff
path: root/fpu
diff options
context:
space:
mode:
authorGreg Kurz <groug@kaod.org>2017-08-14 19:49:16 +0200
committerDavid Gibson <david@gibson.dropbear.id.au>2017-08-22 21:26:46 +1000
commit5dfaa532e0010c2dea50385c87683b0d756aa12f (patch)
tree9f98804fe3436f795cf157b3d218a7834e0d8a48 /fpu
parentc363a37a450f925df76b88a87dc733bad75cc452 (diff)
downloadqemu-5dfaa532e0010c2dea50385c87683b0d756aa12f.zip
qemu-5dfaa532e0010c2dea50385c87683b0d756aa12f.tar.gz
qemu-5dfaa532e0010c2dea50385c87683b0d756aa12f.tar.bz2
ppc: fix ppc_set_compat() with KVM PR
When running in KVM PR mode, kvmppc_set_compat() always fail because the current PR implementation doesn't handle KVM_REG_PPC_ARCH_COMPAT. Now that the machine code inconditionally calls ppc_set_compat_all() at reset time to restore the compat mode default value (commit 66d5c492dd3a9), it is impossible to start a guest with PR: qemu-system-ppc64: Unable to set CPU compatibility mode in KVM: Invalid argument A tentative patch [1] was recently sent by Suraj to address the issue, but it would prevent the compat mode to be turned off on reset. And we really don't want to explicitely check for KVM PR. During the patch's review, David suggested that we should only call the KVM ioctl() if the compat PVR changes. This allows at least to run with KVM PR, provided no compat mode is requested from the command line (which should be the case when running PR nested). This is what this patch does. While here, we also fix the side effect where KVM would fail but we would change the CPU state in QEMU anyway. [1] http://patchwork.ozlabs.org/patch/782039/ Signed-off-by: Greg Kurz <groug@kaod.org> Reviewed-by: Suraj Jitindar Singh <sjitindarsingh@gmail.com> Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Diffstat (limited to 'fpu')
0 files changed, 0 insertions, 0 deletions