xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Doug Goldstein <cardoe@cardoe.com>, xen-devel@lists.xen.org
Cc: Keir Fraser <keir@xen.org>,
	Stefano Stabellini <stefano.stabellini@citrix.com>,
	Ian Campbell <ian.campbell@citrix.com>,
	Jan Beulich <jbeulich@suse.com>
Subject: Re: [PATCH 1/2] build: introduce CONFIG_NR_CPUS in Kconfig
Date: Sat, 9 Jan 2016 13:43:58 +0000	[thread overview]
Message-ID: <56910E9E.3060806@citrix.com> (raw)
In-Reply-To: <1452295045-30903-1-git-send-email-cardoe@cardoe.com>

On 08/01/2016 23:17, Doug Goldstein wrote:
> Introduce an option where the user can modifiy the maximum number of
> supported physical CPUs.
>
> CC: Ian Campbell <ian.campbell@citrix.com>
> CC: Stefano Stabellini <stefano.stabellini@citrix.com>
> CC: Keir Fraser <keir@xen.org>
> CC: Jan Beulich <jbeulich@suse.com>
> CC: Andrew Cooper <andrew.cooper3@citrix.com>
> Signed-off-by: Doug Goldstein <cardoe@cardoe.com>
> ---
> This patch can probably be squashed together with the next one but I
> broke it out with the hope that someone can check the wording on the
> option and also double check the range.
> ---
>  xen/arch/Kconfig     | 8 ++++++++
>  xen/arch/arm/Kconfig | 2 ++
>  xen/arch/x86/Kconfig | 2 ++
>  3 files changed, 12 insertions(+)
>  create mode 100644 xen/arch/Kconfig
>
> diff --git a/xen/arch/Kconfig b/xen/arch/Kconfig
> new file mode 100644
> index 0000000..791d577
> --- /dev/null
> +++ b/xen/arch/Kconfig
> @@ -0,0 +1,8 @@
> +
> +config NR_CPUS
> +	int "Maximum number of CPUs"
> +	range 1 4095

4094

Recursive spinlocks have 12 bit bitfield for cpu, using -1 as a sentinel.

There might be other restrictions, but none currently come to mind.

> +	default "256" if X86
> +	default "128" if ARM
> +	---help---
> +	  Specifies the maximum number of CPUs which Xen will support.

"of physical CPUs"

This will help avoid confusion with virtual cpu limits.

~Andrew

  parent reply	other threads:[~2016-01-09 13:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-08 23:17 [PATCH 1/2] build: introduce CONFIG_NR_CPUS in Kconfig Doug Goldstein
2016-01-08 23:17 ` [PATCH 2/2] build: convert NR_CPUS to Kconfig Doug Goldstein
2016-01-09 14:36   ` Andrew Cooper
2016-01-11 14:24   ` Jan Beulich
2016-01-11 15:06     ` Doug Goldstein
2016-01-11 15:30       ` Jan Beulich
2016-01-11 15:49         ` Dario Faggioli
2016-01-09 13:43 ` Andrew Cooper [this message]
2016-01-11 14:15   ` [PATCH 1/2] build: introduce CONFIG_NR_CPUS in Kconfig Jan Beulich

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=56910E9E.3060806@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=cardoe@cardoe.com \
    --cc=ian.campbell@citrix.com \
    --cc=jbeulich@suse.com \
    --cc=keir@xen.org \
    --cc=stefano.stabellini@citrix.com \
    --cc=xen-devel@lists.xen.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;
as well as URLs for NNTP newsgroup(s).