On Tue, Jun 25, 2019 at 02:00:05AM -0300, Eduardo Habkost wrote: > Management software will be expected to resolve CPU model name > aliases using the new field. > > Signed-off-by: Eduardo Habkost <ehabk...@redhat.com> > --- > Cc: Eric Blake <ebl...@redhat.com> > Cc: Markus Armbruster <arm...@redhat.com> > --- > qapi/target.json | 9 ++++++++- > 1 file changed, 8 insertions(+), 1 deletion(-) > > diff --git a/qapi/target.json b/qapi/target.json > index 1d4d54b600..0197c7962c 100644 > --- a/qapi/target.json > +++ b/qapi/target.json > @@ -475,6 +475,12 @@ > # to introspect properties configurable using -cpu or -global. > # (since 2.9) > # > +# @alias-of: Name of CPU model this model is an alias for. The target of the > +# CPU model alias may change depending on the machine type. > +# Management software is supposed to translate CPU model aliases > +# in the VM configuration, because aliases may stop being > +# migration-safe in the future (since 4.1) > +# > # @unavailable-features is a list of QOM property names that > # represent CPU model attributes that prevent the CPU from running. > # If the QOM property is read-only, that means there's no known > @@ -498,7 +504,8 @@ > '*migration-safe': 'bool', > 'static': 'bool', > '*unavailable-features': [ 'str' ], > - 'typename': 'str' }, > + 'typename': 'str', > + '*alias-of' : 'str' }, > 'if': 'defined(TARGET_PPC) || defined(TARGET_ARM) || defined(TARGET_I386) > || defined(TARGET_S390X) || defined(TARGET_MIPS)' }
IIUC, this means that data for a "Haswell" CPU model will now report "alias-of": "Haswell-NNN" (for some arbitrary NNN which may change at will in any release). Regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
