What is the strategy to update the CPU Models in src/cpu/cpu_map.xml based on?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi All,

I am not sure about the update strategy of CPU models in libvirt.

IMO, It's depend on the CPU model in qemu-kvm, if some CPU models
were updated in qemu-kvm. Then, we should modify the src/cpu/cpu_map.xml
of libvirt to synchronize?

eg:

  commit cad8054ece28("cpu: Add cpu definition for Intel Sandy Bridge
cpu type") in libvirt upstream.

   https://bugzilla.redhat.com/show_bug.cgi?id=761005

If it's right, I found this commit b3a4f0b1a072("target-i386: add VME to
all CPUs") updated the VME feature in qemu upstream. But in the src/cpu
/cpu_map.xml of libvirt, It didn't be updated.

eg:
  For the SandyBridge CPU,

    - In QEmu, it has the 'vme' feature defined by CPUID_VME

    - In libvirt, it doesn't has the 'vme' in cpu_map.xml file.

Why?

Thanks,

	dou





--
libvir-list mailing list
libvir-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvir-list



[Index of Archives]     [Virt Tools]     [Libvirt Users]     [Lib OS Info]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]     [Fedora Tools]

  Powered by Linux