From: Stefano Stabellini <sstabellini@kernel.org>
To: julien.grall@arm.com
Cc: andrew.cooper3@citrix.com, sstabellini@kernel.org,
andrii_anisov@epam.com, JBeulich@suse.com,
xen-devel@lists.xen.org
Subject: [PATCH v8 09/11] xen: add per-platform defaults for NR_CPUS
Date: Mon, 30 Jul 2018 10:48:30 -0700 [thread overview]
Message-ID: <1532972912-12439-9-git-send-email-sstabellini@kernel.org> (raw)
In-Reply-To: <alpine.DEB.2.10.1807301042060.20701@sstabellini-ThinkPad-X260>
Add specific per-platform defaults for NR_CPUS. Note that the order of
the defaults matter: they need to go first, otherwise the generic
defaults will be applied.
This is done so that Xen builds customized for a specific hardware
platform can have the right NR_CPUS number.
Signed-off-by: Stefano Stabellini <sstabellini@kernel.org>
Acked-by: Jan Beulich <jbeulich@suse.com>
Acked-by: Julien Grall <julien.grall@arm.com>
CC: JBeulich@suse.com
CC: andrew.cooper3@citrix.com
---
Changes in v6:
- remove useless additional default for ALL
---
xen/arch/Kconfig | 3 +++
1 file changed, 3 insertions(+)
diff --git a/xen/arch/Kconfig b/xen/arch/Kconfig
index cf0acb7..1954d1c 100644
--- a/xen/arch/Kconfig
+++ b/xen/arch/Kconfig
@@ -3,6 +3,9 @@ config NR_CPUS
int "Maximum number of physical CPUs"
range 1 4095
default "256" if X86
+ default "8" if ARM && RCAR3
+ default "4" if ARM && QEMU
+ default "4" if ARM && MPSOC
default "128" if ARM
---help---
Specifies the maximum number of physical CPUs which Xen will support.
--
1.9.1
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2018-07-30 17:48 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-30 17:48 [PATCH v8 00/11] arm: more kconfig configurability and small default configs Stefano Stabellini
2018-07-30 17:48 ` [PATCH v8 01/11] arm: remove the ARM HDLCD driver Stefano Stabellini
2018-07-30 17:48 ` [PATCH v8 02/11] arm: make it possible to disable HAS_GICV3 Stefano Stabellini
2018-07-31 8:04 ` Jan Beulich
2018-07-31 11:07 ` Julien Grall
2018-07-30 17:48 ` [PATCH v8 03/11] arm: rename HAS_GICV3 to GICV3 Stefano Stabellini
2018-07-30 17:48 ` [PATCH v8 04/11] Make MEM_ACCESS configurable Stefano Stabellini
2018-07-30 17:48 ` [PATCH v8 05/11] make it possible to enable/disable UART drivers Stefano Stabellini
2018-07-30 17:48 ` [PATCH v8 06/11] arm: make it possible to disable the SMMU driver Stefano Stabellini
2018-07-30 17:48 ` [PATCH v8 07/11] arm: add a tiny kconfig configuration Stefano Stabellini
2018-07-30 17:48 ` [PATCH v8 08/11] arm: add ALL_PLAT, QEMU, Rcar3 and MPSoC configs Stefano Stabellini
2018-07-31 11:17 ` Julien Grall
2018-08-01 7:25 ` Andrii Anisov
2018-08-01 22:43 ` Stefano Stabellini
2018-07-30 17:48 ` Stefano Stabellini [this message]
2018-07-30 17:48 ` [PATCH v8 10/11] xen: add cloc target Stefano Stabellini
2018-07-30 17:48 ` [PATCH v8 11/11] xen: specify support for EXPERT and DEBUG Kconfig options Stefano Stabellini
2018-07-31 11:28 ` [PATCH v8 00/11] arm: more kconfig configurability and small default configs Julien Grall
2018-07-31 16:10 ` Stefano Stabellini
2018-08-02 12:07 ` Julien Grall
2018-08-02 20:25 ` Stefano Stabellini
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=1532972912-12439-9-git-send-email-sstabellini@kernel.org \
--to=sstabellini@kernel.org \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=andrii_anisov@epam.com \
--cc=julien.grall@arm.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).