diff options
| author | Vitaly Kuznetsov <vkuznets@redhat.com> | 2021-11-16 17:34:38 +0100 |
|---|---|---|
| committer | Paolo Bonzini <pbonzini@redhat.com> | 2021-11-18 08:12:14 +0100 |
| commit | f60a00d7295057cb4baea5a321501efc72794453 (patch) | |
| tree | 4bd5794b032d48125f98268464160232ea2a3e56 /lib/test_scanf.c | |
| parent | KVM: x86: Assume a 64-bit hypercall for guests with protected state (diff) | |
| download | linux-f60a00d7295057cb4baea5a321501efc72794453.tar.xz linux-f60a00d7295057cb4baea5a321501efc72794453.zip | |
KVM: arm64: Cap KVM_CAP_NR_VCPUS by kvm_arm_default_max_vcpus()
Generally, it doesn't make sense to return the recommended maximum number
of vCPUs which exceeds the maximum possible number of vCPUs.
Note: ARM64 is special as the value returned by KVM_CAP_MAX_VCPUS differs
depending on whether it is a system-wide ioctl or a per-VM one. Previously,
KVM_CAP_NR_VCPUS didn't have this difference and it seems preferable to
keep the status quo. Cap KVM_CAP_NR_VCPUS by kvm_arm_default_max_vcpus()
which is what gets returned by system-wide KVM_CAP_MAX_VCPUS.
Signed-off-by: Vitaly Kuznetsov <vkuznets@redhat.com>
Message-Id: <20211116163443.88707-2-vkuznets@redhat.com>
Acked-by: Marc Zyngier <maz@kernel.org>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'lib/test_scanf.c')
0 files changed, 0 insertions, 0 deletions