From: Valentin Schneider <vschneid@redhat.com>
To: Yury Norov <yury.norov@gmail.com>,
linux-kernel@vger.kernel.org,
Geert Uytterhoeven <geert@linux-m68k.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Andrew Morton <akpm@linux-foundation.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
"Paul E . McKenney" <paulmck@kernel.org>,
Vlastimil Babka <vbabka@suse.cz>,
Dmitry Vyukov <dvyukov@google.com>,
Sander Vanheule <sander@svanheule.net>,
Alexey Klimov <klimov.linux@gmail.com>,
Eric Biggers <ebiggers@google.com>
Cc: Yury Norov <yury.norov@gmail.com>
Subject: Re: [PATCH v2] cpumask: limit visibility of FORCE_NR_CPUS
Date: Fri, 04 Nov 2022 17:43:53 +0000 [thread overview]
Message-ID: <xhsmhtu3evcme.mognet@vschneid.remote.csb> (raw)
In-Reply-To: <20221019225939.1646349-1-yury.norov@gmail.com>
On 19/10/22 15:59, Yury Norov wrote:
> In current form, FORCE_NR_CPUS is visible to all users building their
> kernels, even not experts. It is also set in allmodconfig or allyesconfig,
> which is not a correct behavior.
>
> The 'choice' and unused config UNFORCE_NR_CPUS are used to ensure that
> auto-generated configs that try to enable as much options as possible,
> like allmodconfig, don't enable FORCE_NR_CPUS.
>
> Suggested-by: Geert Uytterhoeven <geert@linux-m68k.org>
> Suggested-by: Linus Torvalds <torvalds@linux-foundation.org>
> Signed-off-by: Yury Norov <yury.norov@gmail.com>
> ---
> v2: extend commit message with an explanation for what we need 'choice'.
>
> lib/Kconfig | 31 ++++++++++++++++++++++++-------
> 1 file changed, 24 insertions(+), 7 deletions(-)
>
> diff --git a/lib/Kconfig b/lib/Kconfig
> index 9bbf8a4b2108..1ada12f5dda6 100644
> --- a/lib/Kconfig
> +++ b/lib/Kconfig
> @@ -528,14 +528,31 @@ config CPUMASK_OFFSTACK
> them on the stack. This is a bit more expensive, but avoids
> stack overflow.
>
> +choice
> + prompt "Number of CPUs detection method"
> + default UNFORCE_NR_CPUS
> + depends on SMP && EXPERT
What about moving the 'depends on EXPERT' onto FORCE_NR_CPUS? I find it
makes it easier to figure out the requirements for that option, and is
similar to how e.g. CONFIG_PREEMPT_RT is handled.
> + help
> + Select between boot-time and compile-time detection of number
> + of CPUs. If it's possible to provide exact number of CPUs at
> + compile-time, kernel code may be optimized better.
> + For general-purpose kernel, choose "boot time" option.
> +
> +config UNFORCE_NR_CPUS
> + bool "Set number of CPUs at boot time"
> + help
> + Choose it if you build general-purpose kernel and want to rely
> + on kernel to detect actual number of CPUs.
> +
> config FORCE_NR_CPUS
> - bool "NR_CPUS is set to an actual number of CPUs"
> - depends on SMP
> - help
> - Say Yes if you have NR_CPUS set to an actual number of possible
> - CPUs in your system, not to a default value. This forces the core
> - code to rely on compile-time value and optimize kernel routines
> - better.
> + bool "Set number of CPUs at compile time"
> + help
> + Choose it if NR_CPUS corresponds to an actual number of
> + possible CPUs in your system. This forces the core code
> + to rely on compile-time value and optimize kernel routines
> + better.
> +
> +endchoice
>
> config CPU_RMAP
> bool
> --
> 2.34.1
next prev parent reply other threads:[~2022-11-04 17:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-19 22:59 Yury Norov
2022-11-04 17:43 ` Valentin Schneider [this message]
2022-11-04 22:36 ` Yury Norov
2022-11-07 12:45 ` Valentin Schneider
2022-11-07 17:55 ` Linus Torvalds
2022-11-07 18:20 ` Yury Norov
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=xhsmhtu3evcme.mognet@vschneid.remote.csb \
--to=vschneid@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=dvyukov@google.com \
--cc=ebiggers@google.com \
--cc=geert@linux-m68k.org \
--cc=klimov.linux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=sander@svanheule.net \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=vbabka@suse.cz \
--cc=yury.norov@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
all inboxes | Powered by JetHome®