mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jinjie Ruan <ruanjinjie@huawei.com>
To: <corbet@lwn.net>, <skhan@linuxfoundation.org>,
	<rdunlap@infradead.org>, <bigeasy@linutronix.de>,
	<clrkwllms@kernel.org>, <rostedt@goodmis.org>, <rppt@kernel.org>,
	<arnd@arndb.de>, <bp@alien8.de>, <kmehltretter@gmail.com>,
	<dapeng1.mi@linux.intel.com>, <elver@google.com>,
	<enelsonmoore@gmail.com>, <jlayton@kernel.org>,
	<quchaosheng000406@163.com>, <linux-doc@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, <linux-rt-devel@lists.linux.dev>
Cc: <ruanjinjie@huawei.com>
Subject: [PATCH 1/2] docs: kernel-parameters: Drop unsupported preempt= modes
Date: Wed, 28 Oct 2026 10:43:32 +0800	[thread overview]
Message-ID: <20261028024333.795917-2-ruanjinjie@huawei.com> (raw)
In-Reply-To: <20261028024333.795917-1-ruanjinjie@huawei.com>

Since commit d3d16750693b ("sched: dynamic: Make PREEMPT_DYNAMIC depend
on ARCH_HAS_PREEMPT_LAZY") only "full" and "lazy" are accepted with
CONFIG_PREEMPT_DYNAMIC: every architecture that supports it selects
ARCH_HAS_PREEMPT_LAZY, which excludes the none and voluntary models.
Passing either is rejected with "Dynamic Preempt: unsupported mode".

Remove the two lines so the parameter reference matches the code.

Signed-off-by: Jinjie Ruan <ruanjinjie@huawei.com>
---
 Documentation/admin-guide/kernel-parameters.txt | 2 --
 1 file changed, 2 deletions(-)

diff --git a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-guide/kernel-parameters.txt
index fce0d52b9cfe..11f0b700d56a 100644
--- a/Documentation/admin-guide/kernel-parameters.txt
+++ b/Documentation/admin-guide/kernel-parameters.txt
@@ -5428,8 +5428,6 @@ Kernel parameters
 
 	preempt=	[KNL]
 			Select preemption mode if you have CONFIG_PREEMPT_DYNAMIC
-			none - Limited to cond_resched() calls
-			voluntary - Limited to cond_resched() and might_sleep() calls
 			full - Any section that isn't explicitly preempt disabled
 			       can be preempted anytime.  Tasks will also yield
 			       contended spinlocks (if the critical section isn't
-- 
2.34.1


  reply	other threads:[~2026-10-28  2:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-28  2:43 [PATCH 0/2] docs: Remove the " Jinjie Ruan
2026-10-28  2:43 ` Jinjie Ruan [this message]
2026-10-28 15:40   ` [PATCH 1/2] docs: kernel-parameters: Drop " Daniel Pereira
2026-11-02 13:34   ` Sebastian Andrzej Siewior
2026-10-28  2:43 ` [PATCH 2/2] docs: sched-preemption: Fix the list of runtime-selectable models Jinjie Ruan
2026-10-28 15:43   ` Daniel Pereira
2026-11-02 13:34   ` Sebastian Andrzej Siewior

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=20261028024333.795917-2-ruanjinjie@huawei.com \
    --to=ruanjinjie@huawei.com \
    --cc=arnd@arndb.de \
    --cc=bigeasy@linutronix.de \
    --cc=bp@alien8.de \
    --cc=clrkwllms@kernel.org \
    --cc=corbet@lwn.net \
    --cc=dapeng1.mi@linux.intel.com \
    --cc=elver@google.com \
    --cc=enelsonmoore@gmail.com \
    --cc=jlayton@kernel.org \
    --cc=kmehltretter@gmail.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-devel@lists.linux.dev \
    --cc=quchaosheng000406@163.com \
    --cc=rdunlap@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=rppt@kernel.org \
    --cc=skhan@linuxfoundation.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

all inboxes | Powered by JetHome®