From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752529AbcGAIoQ (ORCPT ); Fri, 1 Jul 2016 04:44:16 -0400 Received: from mail-wm0-f66.google.com ([74.125.82.66]:34270 "EHLO mail-wm0-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751994AbcGAIoE (ORCPT ); Fri, 1 Jul 2016 04:44:04 -0400 Subject: Re: [PATCH v1 11/11] KVM: x86: bump MAX_VCPUS to 288 To: =?UTF-8?B?UmFkaW0gS3LEjW3DocWZ?= , linux-kernel@vger.kernel.org, kvm@vger.kernel.org References: <20160630205429.16480-1-rkrcmar@redhat.com> <20160630205429.16480-12-rkrcmar@redhat.com> Cc: "Lan, Tianyu" , Igor Mammedov , Jan Kiszka , Peter Xu From: Paolo Bonzini Message-ID: Date: Fri, 1 Jul 2016 10:43:26 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.1.1 MIME-Version: 1.0 In-Reply-To: <20160630205429.16480-12-rkrcmar@redhat.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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ář > --- > 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 > #include > > -#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 Paolo