From: Zhen Lei <thunder.leizhen@huawei.com>
To: Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Juri Lelli <juri.lelli@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ben Segall <bsegall@google.com>, "Mel Gorman" <mgorman@suse.de>,
Daniel Bristot de Oliveira <bristot@redhat.com>,
Valentin Schneider <vschneid@redhat.com>,
<linux-kernel@vger.kernel.org>,
"Paul E . McKenney" <paulmck@kernel.org>,
Frederic Weisbecker <frederic@kernel.org>,
Neeraj Upadhyay <quic_neeraju@quicinc.com>,
"Josh Triplett" <josh@joshtriplett.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Lai Jiangshan <jiangshanlai@gmail.com>,
Joel Fernandes <joel@joelfernandes.org>, <rcu@vger.kernel.org>
Cc: Zhen Lei <thunder.leizhen@huawei.com>
Subject: [PATCH v4 0/2] rcu: Display registers of self-detected stall as far as possible
Date: Thu, 4 Aug 2022 10:34:18 +0800 [thread overview]
Message-ID: <20220804023420.1663-1-thunder.leizhen@huawei.com> (raw)
v3 --> v4:
1. To avoid undo/redo, merge patch 1-2 in v3 into one.
v2 --> v3:
1. Patch 1 Add trigger_single_cpu_backtrace(cpu) in synchronize_rcu_expedited_wait()
Subsequently, we can see that all callers of dump_cpu_task() try
trigger_single_cpu_backtrace() first. Then I do the cleanup in Patch 2.
2. Patch 3, as Paul E. McKenney's suggestion, push the code into dump_cpu_task().
For newcomers:
Currently, dump_cpu_task() is mainly used by RCU, in order to dump the
stack traces of the current task of the specified CPU when a rcu stall
is detected.
For architectures that do not support NMI interrupts, registers is not
printed when rcu stall is self-detected. This patch series improve it.
v2:
https://lkml.org/lkml/2022/7/27/1800
Zhen Lei (2):
sched/debug: Try trigger_single_cpu_backtrace(cpu) in dump_cpu_task()
sched/debug: Show the registers of 'current' in dump_cpu_task()
kernel/rcu/tree_stall.h | 8 +++-----
kernel/sched/core.c | 14 ++++++++++++++
kernel/smp.c | 3 +--
3 files changed, 18 insertions(+), 7 deletions(-)
--
2.25.1
next reply other threads:[~2022-08-04 2:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-04 2:34 Zhen Lei [this message]
2022-08-04 2:34 ` [PATCH v4 1/2] sched/debug: Try trigger_single_cpu_backtrace(cpu) in dump_cpu_task() Zhen Lei
2022-08-04 2:34 ` [PATCH v4 2/2] sched/debug: Show the registers of 'current' " Zhen Lei
2022-08-04 18:09 ` [PATCH v4 0/2] rcu: Display registers of self-detected stall as far as possible Paul E. McKenney
2022-08-05 8:09 ` Leizhen (ThunderTown)
2022-08-06 7:19 ` Leizhen (ThunderTown)
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=20220804023420.1663-1-thunder.leizhen@huawei.com \
--to=thunder.leizhen@huawei.com \
--cc=bristot@redhat.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=frederic@kernel.org \
--cc=jiangshanlai@gmail.com \
--cc=joel@joelfernandes.org \
--cc=josh@joshtriplett.org \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=quic_neeraju@quicinc.com \
--cc=rcu@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@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