From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Suchit Karunakaran <suchitkarunakaran@gmail.com>
Cc: ardb@kernel.org, linus.walleij@linaro.org, ebiggers@google.com,
nathan@kernel.org, lumag@kernel.org, dave@vasilevsky.ca,
ruanjinjie@huawei.com, kees@kernel.org, liuyuntao12@huawei.com,
linux-arm-kernel@lists.infradead.org, skhan@linuxfoundation.org,
linux-kernel-mentees@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm: allow single CPU configuration by adjusting NR_CPUS range and defaults
Date: Thu, 24 Jul 2025 18:45:56 +0100 [thread overview]
Message-ID: <aIJxVDBXyFgrz8AV@shell.armlinux.org.uk> (raw)
In-Reply-To: <20250724172603.18701-1-suchitkarunakaran@gmail.com>
On Thu, Jul 24, 2025 at 10:56:03PM +0530, Suchit Karunakaran wrote:
> Previously, the NR_CPUS config for ARM required a minimum of 2 CPUs.
> This patch changes the minimum NR_CPUS to 1 when SMP is not enabled,
> sets range to exactly 1 if !SMP, allowing only a single CPU setting and
> adds conditional defaults:
> - default to 1 if SMP is disabled (uniprocessor)
> - default to 4 if SMP is enabled (multiprocessor)
>
> Signed-off-by: Suchit Karunakaran <suchitkarunakaran@gmail.com>
This hasn't been tested. NR_CPUS depends on SMP, so if SMP is not
enabled, then NR_CPUS doesn't exist in the configuration. Therefore,
providing a default for !SMP is meaningless.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!
next prev parent reply other threads:[~2025-07-24 17:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-24 17:26 [PATCH] arm: allow single CPU configuration by adjusting NR_CPUS range and defaults Suchit Karunakaran
2025-07-24 17:45 ` Russell King (Oracle) [this message]
2025-07-24 17:57 ` Suchit K
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=aIJxVDBXyFgrz8AV@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=ardb@kernel.org \
--cc=dave@vasilevsky.ca \
--cc=ebiggers@google.com \
--cc=kees@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel-mentees@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=liuyuntao12@huawei.com \
--cc=lumag@kernel.org \
--cc=nathan@kernel.org \
--cc=ruanjinjie@huawei.com \
--cc=skhan@linuxfoundation.org \
--cc=suchitkarunakaran@gmail.com \
/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