On 11/12/21 11:38, Andrew Jones wrote:
I'd like KVM to be consistent across architectures and have the same
(similar) meaning for KVM_CAP_NR_VCPUS.
KVM_CAP_NR_VCPUS seems pretty useless if we just want to tell userspace
the same thing it can get with _SC_NPROCESSORS_ONLN. In fact, if userspace
knows something we don't about the future onlining of some pcpus, then
maybe userspace would prefer to check _SC_NPROCESSORS_CONF.
It's the same for most architectures, but for example PPC has to take
into account the handling of threads, which can exist while the VMs run
but not in the host. So KVM_CAP_NR_VCPUS on PPC is _SC_NPROCESSORS_CONF
times the number of threads per core.
If you don't count PPC (not sure about s390), it _is_ pretty useless indeed.
Paolo
