summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorQiang Ma <maqianga@uniontech.com>2026-05-04 04:00:37 +0300
committerHuacai Chen <chenhuacai@loongson.cn>2026-05-04 04:00:37 +0300
commitb3e31a6650d4cab63f0814c37c0b360372c6ee9e (patch)
tree481f82e865fee5e6210c1303ceaa2efce01f568c
parentb323a441da602dfdfc24f30d3190cac786ffebf2 (diff)
downloadlinux-b3e31a6650d4cab63f0814c37c0b360372c6ee9e.tar.xz
LoongArch: KVM: Cap KVM_CAP_NR_VCPUS by KVM_CAP_MAX_VCPUS
It doesn't make sense to return the recommended maximum number of vCPUs which exceeds the maximum possible number of vCPUs. Other architectures have already done this, such as commit 57a2e13ebdda ("KVM: MIPS: Cap KVM_CAP_NR_VCPUS by KVM_CAP_MAX_VCPUS") Cc: stable@vger.kernel.org Reviewed-by: Bibo Mao <maobibo@loongson.cn> Signed-off-by: Qiang Ma <maqianga@uniontech.com> Signed-off-by: Huacai Chen <chenhuacai@loongson.cn>
-rw-r--r--arch/loongarch/kvm/vm.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/arch/loongarch/kvm/vm.c b/arch/loongarch/kvm/vm.c
index 8cc5ee1c53ef..1317c718f896 100644
--- a/arch/loongarch/kvm/vm.c
+++ b/arch/loongarch/kvm/vm.c
@@ -125,7 +125,7 @@ int kvm_vm_ioctl_check_extension(struct kvm *kvm, long ext)
r = 1;
break;
case KVM_CAP_NR_VCPUS:
- r = num_online_cpus();
+ r = min_t(unsigned int, num_online_cpus(), KVM_MAX_VCPUS);
break;
case KVM_CAP_MAX_VCPUS:
r = KVM_MAX_VCPUS;