Eduardo Habkost <ehabkost@xxxxxxxxxx> writes: > Hi, > > This is the first try at a simple system to make the CPU model definitions > versioned (to allow them to get bug fixes while allowing migration from older > versions and keeping command-line compatibility), and per- machine-type aliases > for compatibility. > > The lack of CPU model versioning is blocking multiple bug fixes that are > necessary on CPU model definitions, but can't be included today because they > would break migration. > > Later, after this gets in (or at least gets some feedback), I plan to send a > proposal for a machine-friendly CPU feature / CPU model probing interface that > libvirt could use. This isn't the right approach. The CPU properties should be exposed as QOM properties which then allows the machine type globals to be used to control stuff like this. Is there a specific set of properties you want to control? As long as it's a small number, we can start with that and get something in shape for 1.2. Regards, Anthony Liguori > > Eduardo Habkost (3): > vl.c: extract qemu_machine_init() function > per-machine-type CPU model alias system > x86: pc: versioned CPU model names & compatibility aliases > > hw/boards.h | 13 +++++++++ > hw/pc_piix.c | 56 ++++++++++++++++++++++++++++++++++++ > sysconfigs/target/cpus-x86_64.conf | 18 ++++++------ > vl.c | 28 +++++++++++++++++- > 4 files changed, 105 insertions(+), 10 deletions(-) > > -- > 1.7.10.4 -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list