[libvirt] [RFC PATCH 0/2] nodeinfo: PPC64: Fix topology and siblings info on capabilities and nodeinfo

[Shivaprasad G Bhat]

The nodeinfo output was fixed earlier to reflect the actual cpus available in
KVM mode on PPC64. The earlier fixes covered the aspect of not making a host
look overcommitted when its not. The current fixes are aimed at helping the
users make better decisions on the kind of guest cpu topology that can be
supported on the given sucore_per_core setting of KVM host and also hint the
way to pin the guest vcpus efficiently.

I am planning to add some test cases once the approach is accepted.

With respect to Patch 2:
The second patch adds a new element to the cpus tag and I need your inputs on
if that is okay. Also if there is a better way. I am not sure if the existing
clients have RNG checks that might fail with the approach. Or if the checks
are not enoforced on the elements but only on the tags.

With my approach if the rng checks pass, the new element "capacity" even if
ignored by many clients would have no impact except for PPC64.

To the extent I looked at code, the siblings changes dont affect existing
libvirt functionality. Please do let me know otherwise.


---

Shivaprasad G Bhat (2):
      nodeinfo: Reflect guest usable host topology on PPC64
      Introduce capacity to virCapsHostNUMACellCPU to help vcpu pinning decisions


 src/conf/capabilities.c                        |    3 +
 src/conf/capabilities.h                        |    1 
 src/nodeinfo.c                                 |   51 ++++++++++++++++++++++--
 tests/vircaps2xmldata/vircaps-basic-4-4-2G.xml |   32 ++++++++-------
 tests/vircaps2xmltest.c                        |    1 
 5 files changed, 67 insertions(+), 21 deletions(-)

--
Signature