aboutsummaryrefslogtreecommitdiff
path: root/disas/moxie.c
diff options
context:
space:
mode:
authorLaurent Vivier <lvivier@redhat.com>2017-12-14 19:09:48 +0100
committerMichael Roth <mdroth@linux.vnet.ibm.com>2017-12-15 09:36:56 -0600
commitb7d059b91f78ac0cc4ccfbb951c70f0befc49374 (patch)
tree590ef8312eba696263f01d6f842c0dc7ed773f85 /disas/moxie.c
parent2f3e3890c49bae320431a95a72f45041c79ccc70 (diff)
spapr: don't initialize PATB entry if max-cpu-compat < power9
if KVM is enabled and KVM capabilities MMU radix is available, the partition table entry (patb_entry) for the radix mode is initialized by default in ppc_spapr_reset(). It's a problem if we want to migrate the guest to a POWER8 host while the kernel is not started to set the value to the one expected for a POWER8 CPU. The "-machine max-cpu-compat=power8" should allow to migrate a POWER9 KVM host to a POWER8 KVM host, but because patb_entry is set, the destination QEMU tries to enable radix mode on the POWER8 host. This fails and cancels the migration: Process table config unsupported by the host error while loading state for instance 0x0 of device 'spapr' load of migration failed: Invalid argument This patch doesn't set the PATB entry if the user provides a CPU compatibility mode that doesn't support radix mode. Signed-off-by: Laurent Vivier <lvivier@redhat.com> Signed-off-by: David Gibson <david@gibson.dropbear.id.au> (cherry picked from commit 1481fe5fcfeb7fcf3c1ebb9d8c0432e3e0188ccf) Signed-off-by: Michael Roth <mdroth@linux.vnet.ibm.com>
Diffstat (limited to 'disas/moxie.c')
0 files changed, 0 insertions, 0 deletions