Linux RCU subsystem development
 help / color / mirror / Atom feed
From: John Ogness <john.ogness@linutronix.de>
To: paulmck@kernel.org, Petr Mladek <pmladek@suse.com>
Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
	rcu@vger.kernel.org, linux-kernel@vger.kernel.org,
	kernel-team@meta.com, rostedt@goodmis.org,
	Frederic Weisbecker <frederic@kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Alexei Starovoitov <ast@kernel.org>,
	Andrii Nakryiko <andrii@kernel.org>,
	Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
	Masami Hiramatsu <mhiramat@kernel.org>,
	linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH rcu v2] 4/5] rcu-tasks: Move RCU Tasks self-tests to core_initcall()
Date: Wed, 05 Feb 2025 22:28:06 +0106	[thread overview]
Message-ID: <84ed0c1401.fsf@jogness.linutronix.de> (raw)
In-Reply-To: <af84eb57-2da2-461c-82bb-36312bbb49b0@paulmck-laptop>

On 2025-02-05, "Paul E. McKenney" <paulmck@kernel.org> wrote:
>> Would it make sense to put a call to pr_flush() at the beginning of the
>> kernel_power_off() function?  I suspect that would take care of much
>> more than just rcutorture.
>> 
>> Or maybe after the pr_emerg("Power down\n"), since that is normally
>> the last thing that shows up on rcutorture's console logs.

Yes, after the pr_emerg("Power down\n"), as in your patch below.

> And that does the trick!  I specified 500ms, but maybe -1 would be
> better?  You tell me!  ;-)

I probably would have chosen 1000ms, but if the kthread has made no
forward progress after a few max timeslices, it probably is dead or will
not be scheduled anyway.

If there is no backlog, pr_flush() returns immediately.

I recommend _not_ using timeout_ms=-1 here, in case the kthread cannot
be scheduled (for whatever reason).

> ------------------------------------------------------------------------
>
> commit 172b692a79ec5801eab57cb55d2f9c398f244c62
> Author: Paul E. McKenney <paulmck@kernel.org>
> Date:   Wed Feb 5 12:27:23 2025 -0800
>
>     printk: Flush console log from kernel_power_off()
>     
>     Kernels built with CONFIG_PREEMPT_RT=y can lose significant console output
>     and shutdown time, which hides shutdown-time RCU issues from rcutorture.
>     Therefore, make pr_flush() public and invoke it after then last print
>     in kernel_power_off().
>     
>     Signed-off-by: Paul E. McKenney <paulmck@kernel.org>
>     Cc: Petr Mladek <pmladek@suse.com>
>     Cc: Steven Rostedt <rostedt@goodmis.org>
>     Cc: John Ogness <john.ogness@linutronix.de>
>     Cc: Sergey Senozhatsky <senozhatsky@chromium.org>
>
> diff --git a/include/linux/printk.h b/include/linux/printk.h
> index 4217a9f412b2..b3e88ff1ecc3 100644
> --- a/include/linux/printk.h
> +++ b/include/linux/printk.h
> @@ -806,4 +806,6 @@ static inline void print_hex_dump_debug(const char *prefix_str, int prefix_type,
>  #define print_hex_dump_bytes(prefix_str, prefix_type, buf, len)	\
>  	print_hex_dump_debug(prefix_str, prefix_type, 16, 1, buf, len, true)
>  
> +
> +bool pr_flush(int timeout_ms, bool reset_on_progress);

This will fail to link for !CONFIG_PRINTK.

In kernel/printk/printk.c currently there is:

#ifdef CONFIG_PRINTK
static bool pr_flush(int timeout_ms, bool reset_on_progress);
#else
static bool pr_flush(int timeout_ms, bool reset_on_progress) { return true; }
#endif

This would need to move to include/linux/printk.h

There you will find an existing CONFIG_PRINTK if/else block to move
those to.

>  #endif
> diff --git a/kernel/printk/printk.c b/kernel/printk/printk.c
> index 80910bc3470c..e0c6e5a99897 100644
> --- a/kernel/printk/printk.c
> +++ b/kernel/printk/printk.c
> @@ -2461,7 +2461,7 @@ asmlinkage __visible int _printk(const char *fmt, ...)
>  }
>  EXPORT_SYMBOL(_printk);
>  
> -static bool pr_flush(int timeout_ms, bool reset_on_progress);
> +bool pr_flush(int timeout_ms, bool reset_on_progress);
>  static bool __pr_flush(struct console *con, int timeout_ms, bool reset_on_progress);
>  
>  #else /* CONFIG_PRINTK */
> @@ -4466,7 +4466,7 @@ static bool __pr_flush(struct console *con, int timeout_ms, bool reset_on_progre
>   * Context: Process context. May sleep while acquiring console lock.
>   * Return: true if all usable printers are caught up.
>   */
> -static bool pr_flush(int timeout_ms, bool reset_on_progress)
> +bool pr_flush(int timeout_ms, bool reset_on_progress)
>  {
>  	return __pr_flush(NULL, timeout_ms, reset_on_progress);
>  }
> diff --git a/kernel/reboot.c b/kernel/reboot.c
> index a701000bab34..3448e6ae3556 100644
> --- a/kernel/reboot.c
> +++ b/kernel/reboot.c
> @@ -704,6 +704,7 @@ void kernel_power_off(void)
>  	migrate_to_reboot_cpu();
>  	syscore_shutdown();
>  	pr_emerg("Power down\n");
> +	pr_flush(500, 1);

I would have chosen:

	pr_flush(1000, true);

but I really don't have an argument either way.

>  	kmsg_dump(KMSG_DUMP_SHUTDOWN);
>  	machine_power_off();
>  }

John Ogness

  reply	other threads:[~2025-02-05 21:22 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-16 20:05 [PATCH rcu 0/5] Miscellaneous fixes Paul E. McKenney
2025-01-16 20:05 ` [PATCH rcu 1/5] rcu: Split rcu_report_exp_cpu_mult() mask parameter and use for tracing Paul E. McKenney
2025-01-16 20:05 ` [PATCH rcu 2/5] rcu: Remove READ_ONCE() for rdp->gpwrap access in __note_gp_changes() Paul E. McKenney
2025-01-16 20:05 ` [PATCH rcu 3/5] rcu: Fix get_state_synchronize_rcu_full() GP-start detection Paul E. McKenney
2025-01-16 20:05 ` [PATCH rcu 4/5] rcu-tasks: Move RCU Tasks self-tests to core_initcall() Paul E. McKenney
2025-01-16 20:05 ` [PATCH rcu 5/5] rcu/nocb: Print segment lengths in show_rcu_nocb_gp_state() Paul E. McKenney
2025-01-30 18:53 ` [PATCH rcu 0/5] Miscellaneous fixes Paul E. McKenney
2025-01-30 18:53   ` [PATCH rcu v2] 1/5] rcu: Split rcu_report_exp_cpu_mult() mask parameter and use for tracing Paul E. McKenney
2025-01-30 18:53   ` [PATCH rcu v2] 2/5] rcu: Remove READ_ONCE() for rdp->gpwrap access in __note_gp_changes() Paul E. McKenney
2025-01-30 18:53   ` [PATCH rcu v2] 3/5] rcu: Fix get_state_synchronize_rcu_full() GP-start detection Paul E. McKenney
2025-01-30 18:53   ` [PATCH rcu v2] 4/5] rcu-tasks: Move RCU Tasks self-tests to core_initcall() Paul E. McKenney
2025-02-04 10:26     ` Sebastian Andrzej Siewior
2025-02-04 11:51       ` Paul E. McKenney
2025-02-04 16:34         ` Sebastian Andrzej Siewior
2025-02-04 20:20           ` Paul E. McKenney
2025-02-05 14:50             ` Paul E. McKenney
2025-02-05 19:54               ` John Ogness
2025-02-05 20:10                 ` Paul E. McKenney
2025-02-05 20:31                   ` Paul E. McKenney
2025-02-05 21:22                     ` John Ogness [this message]
2025-02-05 21:55                       ` Paul E. McKenney
2025-02-05 22:20                         ` John Ogness
2025-02-05 22:31                           ` John Ogness
2025-02-05 23:50                             ` Paul E. McKenney
2025-02-06  8:28                               ` John Ogness
2025-02-06  9:58                                 ` Paul E. McKenney
2025-02-06  9:02                               ` Sebastian Andrzej Siewior
2025-02-06  9:59                                 ` Paul E. McKenney
2025-02-06 10:18                                   ` Paul E. McKenney
2025-02-06 11:06                               ` Petr Mladek
2025-02-06 16:32                                 ` Paul E. McKenney
2025-01-30 18:53   ` [PATCH rcu v2] 5/5] rcu/nocb: Print segment lengths in show_rcu_nocb_gp_state() Paul E. McKenney
2025-02-06 10:15   ` [PATCH rcu 6/5] Make RCU watch ct_kernel_exit_state() warning Paul E. McKenney
2025-02-06 17:38     ` Boqun Feng

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=84ed0c1401.fsf@jogness.linutronix.de \
    --to=john.ogness@linutronix.de \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bigeasy@linutronix.de \
    --cc=frederic@kernel.org \
    --cc=kernel-team@meta.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mhiramat@kernel.org \
    --cc=paulmck@kernel.org \
    --cc=pmladek@suse.com \
    --cc=rcu@vger.kernel.org \
    --cc=rostedt@goodmis.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