On Thu, 8 Jun 2017 14:17:39 +1000 David Gibson <da...@gibson.dropbear.id.au> wrote:
> On Fri, Jun 02, 2017 at 01:15:03PM +1000, David Gibson wrote: > > This is a rebased and revised version of my patches revising CPU > > compatiblity mode handling on ppc, last posted in November. Since > > then, many of the patches have already been merged (some for 2.9, some > > since). This is what's left. > > > > * There was conceptual confusion about what a compatibility mode > > means, and how it interacts with the machine type. This cleans > > that up, clarifying that a compatibility mode (as an externally set > > option) only makes sense on machine types that don't permit the > > guest hypervisor privilege (i.e. 'pseries') > > > > * It was previously the user's (or management layer's) responsibility > > to determine compatibility of CPUs on either end for migration. > > This uses the compatibility modes to check that properly during an > > incoming migration. > > Anyone willing to give some review and/or testing, particularly for > patch 2/4. > I'm planning to re-run all the tests when migration of pre-2.10 machine types is fixed.
pgpp6f2iI392b.pgp
Description: OpenPGP digital signature
