------- Comment From <email address hidden> 2019-01-11 01:58 EDT-------
I talked to Michael Roth on this. It looks like everything is there for spectre mitigation but there's two patches to allow power 8 guests to use cap_cfpc=workaround:
072f416a53: target/ppc: Don't require private l1d cache on POWER8 for cap_ppc_safe_cache
b2540203bd: ppc/spapr_caps: Don't disable cap_cfpc on POWER8 by default
Looks like the first one also pre-reqs:
8fea704 target/ppc: Factor out the parsing in kvmppc_get_cpu_characteristics()
Suraj - anything else needed or you suggest there?
Finally, this is, as Michael said, cosmetic, but if you wanted you can pull it in (it's not necessary):
8c5909c419 ppc/spapr-caps: Change migration macro to take full spapr-cap name
------- Comment From <email address hidden> 2019-01-11 01:58 EDT------- workaround:
I talked to Michael Roth on this. It looks like everything is there for spectre mitigation but there's two patches to allow power 8 guests to use cap_cfpc=
072f416a53: target/ppc: Don't require private l1d cache on POWER8 for cap_ppc_safe_cache
b2540203bd: ppc/spapr_caps: Don't disable cap_cfpc on POWER8 by default
Looks like the first one also pre-reqs: get_cpu_ characteristics ()
8fea704 target/ppc: Factor out the parsing in kvmppc_
Suraj - anything else needed or you suggest there?
Finally, this is, as Michael said, cosmetic, but if you wanted you can pull it in (it's not necessary):
8c5909c419 ppc/spapr-caps: Change migration macro to take full spapr-cap name