From: "Paul E. McKenney" <paulmck@kernel.org>
To: bigeasy@linutronix.de
Cc: rcu@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-team@fb.com, mingo@kernel.org, jiangshanlai@gmail.com,
akpm@linux-foundation.org, mathieu.desnoyers@efficios.com,
josh@joshtriplett.org, tglx@linutronix.de, peterz@infradead.org,
rostedt@goodmis.org, dhowells@redhat.com, edumazet@google.com,
fweisbec@gmail.com, oleg@redhat.com, joel@joelfernandes.org
Subject: Quick review of RCU-related patches in v5.10.8-rt23
Date: Thu, 28 Jan 2021 11:50:37 -0800 [thread overview]
Message-ID: <20210128195037.GA9370@paulmck-ThinkPad-P72> (raw)
Hello, Sebastian,
Just doing my periodic (but decidedly non-real-time) scan of RCU-related
patches in -rt, in this case v5.10.8-rt23:
db93e2f1b4b0 ("rcu: Prevent false positive softirq warning on RT")
Looks ready for mainline, given CONFIG_PREEMPT_RT.
f3541b467fbb ("sched: Do not account rcu_preempt_depth on RT in might_sleep()")
If the scheduler maintainers are OK with their part of this patch,
looks good to me, given CONFIG_PREEMPT_RT. Feel free to add:
Acked-by: Paul E. McKenney <paulmck@ekernel.org>
d8c5a7d75e08 ("rcutorture: Avoid problematic critical section nesting on RT")
This one I need to understand better. I do like the use of local
variables to make the "if" conditions less unruly.
The rest are in -rcu already:
a163ef8687a1 ("rcu: make RCU_BOOST default on RT")
Commit 2341bc4a0311 in -rcu. In yesterday's pull request.
5ffd75a96828 ("rcu: Use rcuc threads on PREEMPT_RT as we did")
Commit 8b9a0ecc7ef5 in -rcu. In yesterday's pull request.
e0b671bca2e7 ("rcu: enable rcu_normal_after_boot by default for RT")
Commit 36221e109eb2 in -rcu. In yesterday's pull request.
e27ef68731a1 ("rcu: Don't invoke try_invoke_on_locked_down_task() with irqs disabled")
This one is in v5.10 mainline.
Any reason I shouldn't pull in db93e2f1b4b0 ("rcu: Prevent false positive
softirq warning on RT") for v5.13?
Thanx, Paul
next reply other threads:[~2021-01-28 20:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-28 19:50 Paul E. McKenney [this message]
[not found] ` <20210129161137.5e45ps7yzfuela2d@linutronix.de>
2021-01-29 16:38 ` Paul E. McKenney
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=20210128195037.GA9370@paulmck-ThinkPad-P72 \
--to=paulmck@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=bigeasy@linutronix.de \
--cc=dhowells@redhat.com \
--cc=edumazet@google.com \
--cc=fweisbec@gmail.com \
--cc=jiangshanlai@gmail.com \
--cc=joel@joelfernandes.org \
--cc=josh@joshtriplett.org \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@kernel.org \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=rcu@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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®