Re: [libvirt] [PATCH v2] qemu: bulk stats: add pcpu placement information

From: "Peter Krempa" <pkrempa(a)redhat.com&gt; To: "Francesco Romani" <fromani(a)redhat.com&gt;, libvir-list(a)redhat.com Sent: Thursday, December 11, 2014 10:04:24 AM Subject: Re: [libvirt] [PATCH v2] qemu: bulk stats: add pcpu placement information On 12/11/14 08:43, Francesco Romani wrote: > This patch adds the information about the physical cpu > placement of virtual cpus for bulk stats. > > This is the only difference in output with the > virDomainGetVcpus() API. > Management software, like oVirt, needs this information > to properly manage NUMA configurations. Are you sure that you are getting what you expect? When this stats group was first implemented I asked not to include this stat as it only shows the actual host cpu id where the guest cpu is running at that precise moment. The problem with that is that usual configurations don't map the cpus in a 1:1 fashion, but rather allow a specific guest CPU to be run on a subset of host cpus according to it's scheduling decisions. That means that the stat might oscillate in the given set where the guest vcpu is pinned at. Could you please share your use case for this one? I'm curious to see whether you have some real use of such data.