From: "Paul E. McKenney" <paulmck@kernel.org>
To: linux-kernel@vger.kernel.org
Cc: peterz@infradead.org, mingo@kernel.org, tglx@linutronix.de,
bigeasy@linutronix.de, frederic@kernel.org
Subject: [PATCH smp 0/2] Provide CSD lock timeout diagnostics
Date: Thu, 9 Jul 2020 16:54:36 -0700 [thread overview]
Message-ID: <20200709235436.GA20922@paulmck-ThinkPad-P72> (raw)
Hello!
This is a sneak preview of a series providing diagnostics to help track
down problems that would result in excessive csd_unlock() latencies:
1. Add source and destination CPUs to __call_single_data.
I freely admit that I found the union declaration a
bit confusing!
2. Provide CSD lock timeout diagnostics.
Thanx, Paul
------------------------------------------------------------------------
include/linux/smp.h | 3 +
include/linux/smp_types.h | 3 +
kernel/smp.c | 135 +++++++++++++++++++++++++++++++++++++++++++++-
lib/Kconfig.debug | 10 +++
4 files changed, 150 insertions(+), 1 deletion(-)
next reply other threads:[~2020-07-09 23:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-09 23:54 Paul E. McKenney [this message]
2020-07-09 23:55 ` [PATCH smp 1/2] smp: Add source and destination CPUs to __call_single_data paulmck
2020-07-09 23:55 ` [PATCH smp 2/2] kernel/smp: Provide CSD lock timeout diagnostics paulmck
2020-07-10 10:32 ` Peter Zijlstra
2020-07-10 21:28 ` Paul E. McKenney
2020-07-10 22:58 ` Paul E. McKenney
2020-07-23 13:55 ` Peter Zijlstra
2020-07-23 22:50 ` Paul E. McKenney
2020-07-24 18:19 ` Paul E. McKenney
2020-07-27 23:53 ` [PATCH smp 0/2] " Paul E. McKenney
2020-07-27 23:55 ` [PATCH smp v2 1/3] smp: Add source and destination CPUs to __call_single_data paulmck
2020-07-27 23:55 ` [PATCH smp v2 2/3] kernel/smp: Provide CSD lock timeout diagnostics paulmck
2020-07-27 23:55 ` [PATCH smp v2 3/3] smp: Make symbol 'csd_bug_count' static paulmck
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=20200709235436.GA20922@paulmck-ThinkPad-P72 \
--to=paulmck@kernel.org \
--cc=bigeasy@linutronix.de \
--cc=frederic@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.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