Re: [PATCH 0/5] KVM: Cap KVM_CAP_NR_VCPUS by KVM_CAP_MAX_VCPUS and re-purpose it on x86
From: Christian Borntraeger <hidden>
Date: 2021-11-15 12:35:31
Also in:
kvm, kvm-riscv, linux-arm-kernel, lkml
Am 11.11.21 um 17:32 schrieb Paolo Bonzini:
On 11/11/21 17:27, Vitaly Kuznetsov wrote:quoted
This is a comtinuation of "KVM: x86: Drop arbitraty KVM_SOFT_MAX_VCPUS" (https://lore.kernel.org/kvm/20211111134733.86601-1-vkuznets@redhat.com/ (local)) work. 1) Enforce KVM_CAP_NR_VCPUS <= KVM_CAP_MAX_VCPUS rule on all architectures. [Sean Christopherson] 2) Make KVM_CAP_NR_VCPUS return num_online_cpus() and not an arbitrary value of '710' on x86. Everything but x86 was only 'eyeball tested', the change is trivial but sorry in advance if I screwed up)Christian, can you look at this for s390? Returning a fixed value seems wrong for KVM_CAP_NR_VCPUS.
If we talk about recommended number, then num_online_cpus() also seems to make sense on s390 so if you change that for s390 as well I can ACK this.