| commit | 9dceda5fc34a5868012260ee7271c7a6f36cc1f4 | |
| author | David Gibson <david@gibson.dropbear.id.au> | |
| Mon, 16 Apr 2018 06:47:19 +0000 (16 16:47 +1000) | ||
| committer | David Gibson <david@gibson.dropbear.id.au> | |
| Fri, 22 Jun 2018 04:19:07 +0000 (22 14:19 +1000) | ||
| tree | 0bbb670ea02e4858c7dbba93c8a9b8fb2952ce0b | treesnapshot (tar.gz zip) |
| parent | 27f00f0a108484a975dc075086f8461ff279e1b3 | commitdiff |
spapr: Limit available pagesizes to provide a consistent guest environment
KVM HV has some limitations (deriving from the hardware) that mean not all
host-cpu supported pagesizes may be usable in the guest. At present this
means that KVM guests and TCG guests may see different available page sizes
even if they notionally have the same vcpu model. This is confusing and
also prevents migration between TCG and KVM.
This patch makes the environment consistent by always allowing the same set
of pagesizes. Since we can't remove the KVM limitations, we do this by
always applying the same limitations it has, even to TCG guests.
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Reviewed-by: Cédric Le Goater <clg@kaod.org>
Reviewed-by: Greg Kurz <groug@kaod.org>
KVM HV has some limitations (deriving from the hardware) that mean not all
host-cpu supported pagesizes may be usable in the guest. At present this
means that KVM guests and TCG guests may see different available page sizes
even if they notionally have the same vcpu model. This is confusing and
also prevents migration between TCG and KVM.
This patch makes the environment consistent by always allowing the same set
of pagesizes. Since we can't remove the KVM limitations, we do this by
always applying the same limitations it has, even to TCG guests.
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Reviewed-by: Cédric Le Goater <clg@kaod.org>
Reviewed-by: Greg Kurz <groug@kaod.org>
| hw/ppc/spapr_caps.c | diffblobblamehistory |