public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Gleb Natapov <gleb@redhat.com>
To: Chegu Vinod <chegu_vinod@hp.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] KVM: x86: Increase the "hard" max VCPU limit
Date: Sun, 28 Apr 2013 13:18:01 +0300	[thread overview]
Message-ID: <20130428101801.GG30504@redhat.com> (raw)
In-Reply-To: <1367112664-19862-1-git-send-email-chegu_vinod@hp.com>

On Sat, Apr 27, 2013 at 06:31:04PM -0700, Chegu Vinod wrote:
> KVM guests today use 8bit APIC ids allowing for 256 ID's. Reserving one
> ID for Broadcast interrupts should leave 255 ID's. In case of KVM there
> is no need for reserving another ID for IO-APIC so the hard max limit for
> VCPUS can be increased from 254 to 255. (This was confirmed by Gleb Natapov
> http://article.gmane.org/gmane.comp.emulators.kvm.devel/99713  )
> 
> Signed-off-by: Chegu Vinod <chegu_vinod@hp.com>
Applied, thanks.

> ---
>  arch/x86/include/asm/kvm_host.h |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> diff --git a/arch/x86/include/asm/kvm_host.h b/arch/x86/include/asm/kvm_host.h
> index 4979778..bc57bfa 100644
> --- a/arch/x86/include/asm/kvm_host.h
> +++ b/arch/x86/include/asm/kvm_host.h
> @@ -31,7 +31,7 @@
>  #include <asm/msr-index.h>
>  #include <asm/asm.h>
>  
> -#define KVM_MAX_VCPUS 254
> +#define KVM_MAX_VCPUS 255
>  #define KVM_SOFT_MAX_VCPUS 160
>  #define KVM_USER_MEM_SLOTS 125
>  /* memory slots that are not exposed to userspace */
> -- 
> 1.7.1

--
			Gleb.

      reply	other threads:[~2013-04-28 10:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-28  1:31 [PATCH] KVM: x86: Increase the "hard" max VCPU limit Chegu Vinod
2013-04-28 10:18 ` Gleb Natapov [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130428101801.GG30504@redhat.com \
    --to=gleb@redhat.com \
    --cc=chegu_vinod@hp.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox