Re: [PATCH 1/3] arm: kvm: clamp NR_VCPUS to MAX _VCPUS

From: Marc Zyngier
Date: Sat Sep 14 2013 - 08:22:27 EST


On 2013-09-14 13:14, Alexander Graf wrote:
Am 14.09.2013 um 07:10 schrieb Andrew Jones <drjones@xxxxxxxxxx>:

Signed-off-by: Andrew Jones <drjones@xxxxxxxxxx>
---
arch/arm/kvm/arm.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/arch/arm/kvm/arm.c b/arch/arm/kvm/arm.c
index 741f66a2edbd7..9ebf8ac3a12ff 100644
--- a/arch/arm/kvm/arm.c
+++ b/arch/arm/kvm/arm.c
@@ -201,7 +201,7 @@ int kvm_dev_ioctl_check_extension(long ext)
r = 1;
break;
case KVM_CAP_NR_VCPUS:
- r = num_online_cpus();
+ r = min(num_online_cpus(), KVM_MAX_VCPUS);

Is there any real reason to prohibit overcommit?

I don't think this affects overcommit. This is the "recommended" limit, and you can still go up to KVM_MAX_CPUS.

M.
--
Fast, cheap, reliable. Pick two.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/