From: Ingo Molnar <mingo@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Liu Song <liusong@linux.alibaba.com>,
mingo@redhat.com, peterz@infradead.org, juri.lelli@redhat.com,
vincent.guittot@linaro.org, dietmar.eggemann@arm.com,
bsegall@google.com, mgorman@suse.de, bristot@redhat.com,
vschneid@redhat.com, linux-kernel@vger.kernel.org,
"Paul E. McKenney" <paulmck@kernel.org>
Subject: Re: [PATCH] sched/debug: avoid executing show_state and causing rcu stall warning
Date: Wed, 3 Aug 2022 19:13:01 +0200 [thread overview]
Message-ID: <YuqsnX6LYxe34YN3@gmail.com> (raw)
In-Reply-To: <20220803084235.5d56d1e4@gandalf.local.home>
* Steven Rostedt <rostedt@goodmis.org> wrote:
>
> [ Adding Paul ]
>
> On Wed, 3 Aug 2022 09:18:45 +0800
> Liu Song <liusong@linux.alibaba.com> wrote:
>
> > From: Liu Song <liusong@linux.alibaba.com>
> >
> > If the number of CPUs is large, "sysrq_sched_debug_show" will execute for
> > a long time. Every time I execute "echo t > /proc/sysrq-trigger" on my
> > 128-core machine, the rcu stall warning will be triggered. Moreover,
> > sysrq_sched_debug_show does not need to be protected by rcu_read_lock,
> > and no rcu stall warning will appear after adjustment.
> >
> > Signed-off-by: Liu Song <liusong@linux.alibaba.com>
> > ---
> > kernel/sched/core.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/kernel/sched/core.c b/kernel/sched/core.c
> > index 5555e49..82c117e 100644
> > --- a/kernel/sched/core.c
> > +++ b/kernel/sched/core.c
> > @@ -8879,11 +8879,11 @@ void show_state_filter(unsigned int state_filter)
> > sched_show_task(p);
> > }
> >
> > + rcu_read_unlock();
> > #ifdef CONFIG_SCHED_DEBUG
> > if (!state_filter)
> > sysrq_sched_debug_show();
>
> If this is just because sysrq_sched_debug_show() is very slow, does RCU
> have a way to "touch" it? Like the watchdogs have? That is, to tell RCU
> "Yes I know I'm taking a long time, but I'm still making forward progress,
> don't complain about me". Then the sysrq_sched_debug_show() could have:
>
> for_each_online_cpu(cpu) {
> /*
> * Need to reset softlockup watchdogs on all CPUs, because
> * another CPU might be blocked waiting for us to process
> * an IPI or stop_machine.
> */
> touch_nmi_watchdog();
> touch_all_softlockup_watchdogs();
> + touch_rcu();
> print_cpu(NULL, cpu);
> }
I'd much rather we use the specific exclusion primitive suitable for that
sequence - in that case it should be cpus_read_lock()/unlock() I suspect.
But the entire code sequence should be reviewed - do we anywhere walk task
lists that need RCU protection?
My main complaint was that we cannot just randomly drop the RCU lock with
no inspection of the underlying code.
Ingo
prev parent reply other threads:[~2022-08-03 17:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-03 1:18 [PATCH] sched/debug: avoid executing show_state and causing rcu stall warning Liu Song
2022-08-03 8:39 ` Ingo Molnar
2022-08-03 8:58 ` Liu Song
2022-08-03 9:10 ` Ingo Molnar
2022-08-03 9:25 ` Liu Song
2022-08-03 12:42 ` Steven Rostedt
2022-08-03 14:06 ` Paul E. McKenney
2022-08-03 17:14 ` Ingo Molnar
2022-08-03 17:42 ` Paul E. McKenney
2022-08-03 17:13 ` Ingo Molnar [this message]
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=YuqsnX6LYxe34YN3@gmail.com \
--to=mingo@kernel.org \
--cc=bristot@redhat.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=liusong@linux.alibaba.com \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.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