On Wed, 30 Apr 2014 17:29:28 -0300 Eduardo Habkost <ehabk...@redhat.com> wrote:
> This series allows management code to use object-add on X86CPU subclasses, so > it Is there any reason why "device-add" couldn't be used? > can use it to probe for CPU model information without re-running QEMU. The > main > use case for this is to allow management code to create CPU objects and query > the "feature-words" and "filtered-features" properties on the new objects, to > find out which features each CPU model needs, and to do the same using the > "host" CPU model to check which features can be enabled in a given host. > > There's experimental libvirt code to use the new command at: > https://github.com/ehabkost/libvirt/tree/work/cpu-feature-word-query > The experimental code just create the CPU objects to query for feature > information, but doesn't do anything with that data. > > Eduardo Habkost (5): > cpu: Initialize cpu->stopped=true earlier > cpu: Don't try to pause CPUs if they are already stopped > pc: Don't crash on apic_accept_pic_intr() if CPU has no apic_state > target-i386: Make CPU objects user-creatable > target-i386: Report QOM class name for CPU definitions > > cpus.c | 13 ++++++++++--- > exec.c | 1 + > hw/i386/pc.c | 2 +- > qapi-schema.json | 6 +++++- > target-i386/cpu.c | 7 +++++++ > 5 files changed, 24 insertions(+), 5 deletions(-) > -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
