Linux RCU subsystem development
 help / color / mirror / Atom feed
From: Neeraj Upadhyay <Neeraj.Upadhyay@kernel.org>
To: rcu@vger.kernel.org
Cc: paulmck@kernel.org, joel@joelfernandes.org, frederic@kernel.org,
	boqun.feng@gmail.com, urezki@gmail.com,
	linux-kernel@vger.kernel.org, kernel-team@meta.com,
	rostedt@goodmis.org, mingo@kernel.org, peterz@infradead.org,
	leobras@redhat.com, imran.f.khan@oracle.com, riel@surriel.com,
	tglx@linutronix.de
Subject: [PATCH rcu 0/4] CSD-lock diagnostics updates for v6.12
Date: Fri, 16 Aug 2024 10:06:00 +0530	[thread overview]
Message-ID: <20240816043600.GA25206@neeraj.linux> (raw)

Hello!

This series adds following changes to the CSD-lock diagnostics (rebased on v6.11-rc1):

1.      Print large CSD-lock-hold time numbers as negatives, courtesy of Paul E. McKenney.

2.      Add api to provide an indication of ongoing CSD-lock stall, courtesy of Paul E. McKenney.

3.      Add a backoff mechanism for repeated CSD-lock diagnostic reports of same incident,
        courtesy of Paul E. McKenney.

4.      Print only local CPU info when sched_clock goes backward, courtesy of Rik van Riel.


As communicated earlier at [1], I will be submitting these changes as part of RCU tree,
due to dependency of RCU commit "7c72dedb0079 rcu: Summarize RCU CPU stall warnings during
CSD-lock stalls" [2] on these changes.

Git tree is at [2]

[1] https://lore.kernel.org/lkml/20240722133559.GA667117@neeraj.linux/
[2] https://git.kernel.org/pub/scm/linux/kernel/git/neeraj.upadhyay/linux-rcu.git/commit/?h=rcustall.15.08.24a&id=7c72dedb0079e62c1c75dbab038332017f34a6b8
[3] https://git.kernel.org/pub/scm/linux/kernel/git/neeraj.upadhyay/linux-rcu.git/log/?h=csd.lock.15.08.24a


- Neeraj


Paul E. McKenney (3):
  locking/csd_lock: Print large numbers as negatives
  locking/csd_lock: Provide an indication of ongoing CSD-lock stall
  locking/csd-lock: Use backoff for repeated reports of same incident

Rik van Riel (1):
  smp: print only local CPU info when sched_clock goes backward

 include/linux/smp.h |  6 ++++++
 kernel/smp.c        | 38 +++++++++++++++++++++++++++++++++-----
 lib/Kconfig.debug   |  1 +
 3 files changed, 40 insertions(+), 5 deletions(-)

             reply	other threads:[~2024-08-16  4:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-16  4:36 Neeraj Upadhyay [this message]
2024-08-16  4:39 ` [PATCH rcu 1/4] locking/csd_lock: Print large numbers as negatives neeraj.upadhyay
2024-08-16  4:39 ` [PATCH rcu 2/4] locking/csd_lock: Provide an indication of ongoing CSD-lock stall neeraj.upadhyay
2024-08-16  4:39 ` [PATCH rcu 3/4] locking/csd-lock: Use backoff for repeated reports of same incident neeraj.upadhyay
2024-08-16  4:39 ` [PATCH rcu 4/4] smp: print only local CPU info when sched_clock goes backward neeraj.upadhyay

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=20240816043600.GA25206@neeraj.linux \
    --to=neeraj.upadhyay@kernel.org \
    --cc=boqun.feng@gmail.com \
    --cc=frederic@kernel.org \
    --cc=imran.f.khan@oracle.com \
    --cc=joel@joelfernandes.org \
    --cc=kernel-team@meta.com \
    --cc=leobras@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=paulmck@kernel.org \
    --cc=peterz@infradead.org \
    --cc=rcu@vger.kernel.org \
    --cc=riel@surriel.com \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    --cc=urezki@gmail.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