On Fri, Sep 08, 2023 at 04:48:46PM +0200, Igor Mammedov wrote: > On Fri, 8 Sep 2023 14:45:24 +0200 > Tim Wiederhake <twied...@redhat.com> wrote: > > > Synchronizing the list of cpu features and models with qemu is a recurring > > task in libvirt. For x86, this is done by reading qom-list-properties for > > max-x86_64-cpu and manually filtering out everthing that does not look like > > a feature name, as well as parsing target/i386/cpu.c for cpu models. > > modulo fixing typos/name conflicts in 1st 3 patches, > > I don't think it's a great idea for libvirt (or any other user) to parse > QEMU source (whether it's C code or yaml) or other way around for users > to influence QEMU internals.
NB It isn't for libvirt to parse at runtime, rather it is for libvirt maintainers to consume during dev, so libvirt keeps in sync with QEMU features. With 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 :|
