From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: Wander Lairson Costa <wander@redhat.com>
Cc: Petr Mladek <pmladek@suse.com>,
Sergey Senozhatsky <senozhatsky@chromium.org>,
Steven Rostedt <rostedt@goodmis.org>,
John Ogness <john.ogness@linutronix.de>,
open list <linux-kernel@vger.kernel.org>,
"Paul E . McKenney" <paulmck@kernel.org>
Subject: Re: [PATCH v2 1/1] printk: suppress rcu stall warnings caused by slow console devices
Date: Fri, 12 Nov 2021 10:41:55 +0900 [thread overview]
Message-ID: <YY3GY8ZSH5ACaZZS@google.com> (raw)
In-Reply-To: <20211111195904.618253-2-wander@redhat.com>
On (21/11/11 16:59), Wander Lairson Costa wrote:
>
> If we have a reasonable large dataset to flush in the printk ring
> buffer in the presence of a slow console device (like a serial port
> with a low baud rate configured), the RCU stall detector may report
> warnings.
>
> This patch suppresses RCU stall warnings while flushing the ring buffer
> to the console.
>
[..]
> +extern int rcu_cpu_stall_suppress;
> +
> +static void rcu_console_stall_suppress(void)
> +{
> + if (!rcu_cpu_stall_suppress)
> + rcu_cpu_stall_suppress = 4;
> +}
> +
> +static void rcu_console_stall_unsuppress(void)
> +{
> + if (rcu_cpu_stall_suppress == 4)
> + rcu_cpu_stall_suppress = 0;
> +}
> +
> /**
> * console_unlock - unlock the console system
> *
> @@ -2634,6 +2648,9 @@ void console_unlock(void)
> * and cleared after the "again" goto label.
> */
> do_cond_resched = console_may_schedule;
> +
> + rcu_console_stall_suppress();
> +
> again:
> console_may_schedule = 0;
>
> @@ -2645,6 +2662,7 @@ void console_unlock(void)
> if (!can_use_console()) {
> console_locked = 0;
> up_console_sem();
> + rcu_console_stall_unsuppress();
> return;
> }
>
> @@ -2716,8 +2734,10 @@ void console_unlock(void)
>
> handover = console_lock_spinning_disable_and_check();
> printk_safe_exit_irqrestore(flags);
> - if (handover)
> + if (handover) {
> + rcu_console_stall_unsuppress();
> return;
> + }
>
> if (do_cond_resched)
> cond_resched();
> @@ -2738,6 +2758,8 @@ void console_unlock(void)
> retry = prb_read_valid(prb, next_seq, NULL);
> if (retry && console_trylock())
> goto again;
> +
> + rcu_console_stall_unsuppress();
> }
May be we can just start touching watchdogs from printing routine?
next prev parent reply other threads:[~2021-11-12 1:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-11 19:59 [PATCH v2 0/1] printk: suppress rcu stall warnings caused by slow Wander Lairson Costa
2021-11-11 19:59 ` [PATCH v2 1/1] printk: suppress rcu stall warnings caused by slow console devices Wander Lairson Costa
2021-11-11 21:13 ` Paul E. McKenney
2021-11-11 23:28 ` kernel test robot
2021-11-11 23:33 ` kernel test robot
2021-11-12 1:41 ` Sergey Senozhatsky [this message]
2021-11-12 2:23 ` Paul E. McKenney
2021-11-12 14:42 ` Wander Costa
2021-11-12 14:57 ` Paul E. McKenney
2021-11-12 14:58 ` Wander Costa
2022-01-07 18:53 ` Paul E. McKenney
2022-01-07 20:16 ` Wander Costa
2022-01-10 11:10 ` Petr Mladek
2022-01-17 11:26 ` Wander Costa
2021-11-12 8:45 ` Petr Mladek
2021-11-12 14:08 ` Wander Costa
2021-11-15 10:10 ` Petr Mladek
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=YY3GY8ZSH5ACaZZS@google.com \
--to=senozhatsky@chromium.org \
--cc=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=wander@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