Linux real-time development
 help / color / mirror / Atom feed
From: Clark Williams <clrkwllms@kernel.org>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
	Steven Rostedt <rostedt@goodmis.org>,
	linux-rt-devel@lists.linux.dev
Subject: Re: Possible enhancement to RCU CPU stall warning messages
Date: Thu, 15 Oct 2026 10:27:24 -0500	[thread overview]
Message-ID: <atDw3O5RILsTE1mn@demetrius> (raw)
In-Reply-To: <a7a21bf3-a7d5-45bb-be4f-0119fe53fa20@paulmck-laptop>

On Tue, Oct 13, 2026 at 05:41:41PM -0700, Paul E. McKenney wrote:
> Hello!
> 
> While chasing an "interesting" bug [1], I modified the RCU CPU
> stall-warning code so that when a task (as opposed to a CPU) is
> blocking the grace period due to being preempted, the stall-warning
> message includes the task that is currently running on the CPU that the
> preempted task wants to run on.  (In the case of the "interesting" bug,
> I kid you not, that CPU was idle.)
> 
> Would this stall-warning addition be useful for PREEMPT_RT users?
> 
> If it is not useful, I am going to keep it out of tree.  Something about
> it needing a way to dig into scheduler internals.  ;-)
> 
> But if you want it, please let me know.
> 
> 							Thanx, Paul
> 
> [1] https://lore.kernel.org/all/8fa7f795-518c-4507-b684-60b0c1cac2c5@paulmck-laptop/
> 

Paul,

While RCU isn't one of the common reasons for a latency spike, if it
*is*, then it's not one that's easily tracked down.  For that reason I'm
in favor of using your patch. 

That said, if it's going to be a pain to maintain, I can live without it. 

Clark

  reply	other threads:[~2026-10-15 15:27 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-14  0:41 Possible enhancement to RCU CPU stall warning messages Paul E. McKenney
2026-10-15 15:27 ` Clark Williams [this message]
2026-10-15 15:45   ` Paul E. McKenney
2026-10-16  7:13   ` Crystal Wood
2026-10-16 15:09     ` Paul E. McKenney
2026-10-16 15:23 ` Steven Rostedt
2026-10-16 16:00   ` Paul E. McKenney
2026-10-16 16:17     ` Steven Rostedt
2026-10-16 16:48       ` Paul E. McKenney
2026-10-16 16:54         ` Steven Rostedt
2026-10-16 17:05           ` Paul E. McKenney
2026-10-16 17:40             ` Steven Rostedt
2026-10-16 23:45               ` Paul E. McKenney
2026-10-17 19:02                 ` Paul E. McKenney
2026-10-18 14:21                   ` Steven Rostedt
2026-10-19 17:30                     ` Paul E. McKenney
2026-10-19 18:30                       ` Steven Rostedt
2026-10-19 19:24                         ` Paul E. McKenney
2026-10-19 19:28                           ` Steven Rostedt
2026-10-19 19:39                             ` Paul E. McKenney
2026-10-19 19:50                               ` Steven Rostedt
2026-10-19 20:29                                 ` 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=atDw3O5RILsTE1mn@demetrius \
    --to=clrkwllms@kernel.org \
    --cc=bigeasy@linutronix.de \
    --cc=linux-rt-devel@lists.linux.dev \
    --cc=paulmck@kernel.org \
    --cc=rostedt@goodmis.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