| Subject | Re: [PATCH v1 11/11] KVM: x86: bump MAX_VCPUS to 288 | From | Paolo Bonzini <> | Date | Fri, 1 Jul 2016 10:43:26 +0200 |
| |
On 30/06/2016 22:54, Radim Krčmář wrote: > 288 is in high demand because of Knights Landing CPU. > We cannot set the limit to 640k, because that would be wasting space. > > Signed-off-by: Radim Krčmář <rkrcmar@redhat.com> > --- > arch/x86/include/asm/kvm_host.h | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/arch/x86/include/asm/kvm_host.h b/arch/x86/include/asm/kvm_host.h > index 48b0ca18066c..411da14a675e 100644 > --- a/arch/x86/include/asm/kvm_host.h > +++ b/arch/x86/include/asm/kvm_host.h > @@ -34,7 +34,7 @@ > #include <asm/asm.h> > #include <asm/kvm_page_track.h> > > -#define KVM_MAX_VCPUS 255 > +#define KVM_MAX_VCPUS 288 > #define KVM_SOFT_MAX_VCPUS 240 > #define KVM_USER_MEM_SLOTS 509 > /* memory slots that are not exposed to userspace */ >
Reviewed-by: Paolo Bonzini <pbonzini@redhat.com>
Paolo
|