From: Mike Galbraith <efault@gmx.de>
To: Frederic Weisbecker <frederic@kernel.org>,
Valentin Schneider <valentin.schneider@arm.com>
Cc: linux-kernel@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>
Subject: Re: [PATCH] sched: Split preemption model selection between DYNAMIC & !DYNAMIC
Date: Wed, 10 Nov 2021 05:37:48 +0100 [thread overview]
Message-ID: <beec14cee84de7a4bedd7a63c2acdf150a82bc09.camel@gmx.de> (raw)
In-Reply-To: <20211110011738.GD288354@lothringen>
On Wed, 2021-11-10 at 02:17 +0100, Frederic Weisbecker wrote:
> On Tue, Nov 09, 2021 at 03:10:57PM +0000, Valentin Schneider wrote:
> > +choice
> > + prompt "Default boot-time Preemption Model"
> > + depends on PREEMPT_DYNAMIC
> > + default PREEMPT_NONE_BEHAVIOUR
> > + help
> > + This option defines the default preemption model of the kernel
> > + if it hasn't been specified by the "preempt=" command line parameter.
> >
> > -config PREEMPT_VOLUNTARY
> > - bool
> > +config PREEMPT_NONE_BEHAVIOUR
> > + bool "No Forced Preemption (Server)"
> >
> > -config PREEMPT
> > - bool
> > - select PREEMPTION
> > - select UNINLINE_SPIN_UNLOCK if !ARCH_INLINE_SPIN_UNLOCK
> > +config PREEMPT_VOLUNTARY_BEHAVIOUR
> > + bool "Voluntary Kernel Preemption (Desktop)"
> > +
> > +config PREEMPT_BEHAVIOUR
> > + bool "Preemptible Kernel (Low-Latency Desktop)"
> > +endchoice
>
> The problem here is that you're duplicating the existing titles
> for the static entries and you're losing all the help that text that used to come
> along. The point of the BEHAVIOUR thing, further mapping to either
> static or dynamic preemption, was to avoid that duplication and keep the
> same titles and help for the three behaviour, whether static or dynamic.
Adding "depends on !PREEMPT_DYNAMIC" to the first (legacy?) choice made
it appear/disappear at the appropriate time as well, but I have no idea
how duplication of help text can be avoided.
-Mike
next prev parent reply other threads:[~2021-11-10 4:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-09 15:10 Valentin Schneider
2021-11-10 1:17 ` Frederic Weisbecker
2021-11-10 4:37 ` Mike Galbraith [this message]
2021-11-10 11:24 ` Valentin Schneider
2021-11-10 14:45 ` Valentin Schneider
2021-11-10 15:03 ` Marco Elver
2021-11-10 15:16 ` Marco Elver
2021-11-10 16:49 ` Frederic Weisbecker
2021-11-10 16:56 ` Frederic Weisbecker
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=beec14cee84de7a4bedd7a63c2acdf150a82bc09.camel@gmx.de \
--to=efault@gmx.de \
--cc=frederic@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=valentin.schneider@arm.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
Powered by JetHome