From: Clark Williams <clark.williams@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: Thomas Gleixner <tglx@linutronix.org>,
linux-rt-users@vger.kernel.org, williams@redhat.com,
linux-kernel@vger.kernel.org
Subject: [PATCH PREEMPT_RT 4.19 STABLE] rt: PREEMPT_RT safety net for backported patches
Date: Sun, 30 Jan 2022 15:46:27 -0600 [thread overview]
Message-ID: <20220130221944.7992CC340E4@smtp.kernel.org> (raw)
While doing some 4.19-rt cleanup work, I stumbled across the fact that parts of
two backported patches were dependent on CONFIG_PREEMPT_RT, rather than
the CONFIG_PREEMPT_RT_FULL used in 4.19 and earlier RT series. The commits
in the linux-stable-rt v4.19-rt branch are:
dad4c6a33bf4e mm: slub: Don't resize the location tracking cache on PREEMPT_RT
e626b6f873f2c net: Treat __napi_schedule_irqoff() as __napi_schedule() on PREEMPT_RT
Discussing this at the Stable RT maintainers meeting, Steven Rostedt suggested that
we automagically select CONFIG_PREEMPT_RT if CONFIG_PREEMPT_RT_FULL is on, giving
us a safety net for any subsequently backported patches. Here's my first cut at
that patch.
I suspect we'll need a similar patch for stable RT kernels < 4.19.
Suggested-by: Steven Rostedt <rostedt@goodmis.org>
Signed-off-by: Clark Williams <williams@redhat.com>
---
kernel/Kconfig.preempt | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/kernel/Kconfig.preempt b/kernel/Kconfig.preempt
index 306567f72a3e..951f58cbd652 100644
--- a/kernel/Kconfig.preempt
+++ b/kernel/Kconfig.preempt
@@ -6,6 +6,10 @@ config PREEMPT_RT_BASE
bool
select PREEMPT
+config PREEMPT_RT
+ bool
+ default false
+
config HAVE_PREEMPT_LAZY
bool
@@ -80,6 +84,7 @@ config PREEMPT_RT_FULL
depends on IRQ_FORCED_THREADING
select PREEMPT_RT_BASE
select PREEMPT_RCU
+ select PREEMPT_RT
help
All and everything
--
2.34.1
next reply other threads:[~2022-01-30 22:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-30 21:46 Clark Williams [this message]
2022-01-31 10:23 ` [PATCH PREEMPT_RT 4.19 STABLE] rt: PREEMPT_RT safety net for backported patches 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=20220130221944.7992CC340E4@smtp.kernel.org \
--to=clark.williams@gmail.com \
--cc=bigeasy@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.org \
--cc=williams@redhat.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