From: John Ogness <john.ogness@linutronix.de>
To: Donghyeok Choe <d7271.choe@samsung.com>, pmladek@suse.com
Cc: linux-kernel@vger.kernel.org, takakura@valinux.co.jp,
youngmin.nam@samsung.com, hajun.sung@samsung.com,
seungh.jung@samsung.com, jh1012.choi@samsung.com
Subject: Re: printk: selective deactivation of feature ignoring non panic cpu's messages
Date: Wed, 26 Feb 2025 05:31:53 +0106 [thread overview]
Message-ID: <84ikoxxrfy.fsf@jogness.linutronix.de> (raw)
In-Reply-To: <20250226031628.GB592457@tiffany>
Hi Donghyeok,
On 2025-02-26, Donghyeok Choe <d7271.choe@samsung.com> wrote:
> I would like to print out the message of non panic cpu as it is.
> Can I use early_param to selectively disable that feature?
I have no issues about allowing this type of feature for debugging
purposes. I do not know if early_param is the best approach. I expect
Petr will offer good insight here.
> diff --git a/kernel/printk/printk.c b/kernel/printk/printk.c
> index fb242739aec8..3f420e8bdb2c 100644
> --- a/kernel/printk/printk.c
> +++ b/kernel/printk/printk.c
> @@ -2368,6 +2368,17 @@ void printk_legacy_allow_panic_sync(void)
> }
> }
>
> +static bool __read_mostly keep_printk_all_cpu_in_panic;
> +
> +static int __init keep_printk_all_cpu_in_panic_setup(char *str)
> +{
> + keep_printk_all_cpu_in_panic = true;
> + pr_info("printk: keep printk all cpu in panic.\n");
> +
> + return 0;
> +}
> +early_param("keep_printk_all_cpu_in_panic", keep_printk_all_cpu_in_panic_setup);
Quite a long argument. I am horrible at naming. I expect Petr would have
a good suggestion (if early_param is the way to go).
> +
> asmlinkage int vprintk_emit(int facility, int level,
> const struct dev_printk_info *dev_info,
> const char *fmt, va_list args)
> @@ -2379,13 +2390,15 @@ asmlinkage int vprintk_emit(int facility, int level,
> if (unlikely(suppress_printk))
> return 0;
>
> - /*
> - * The messages on the panic CPU are the most important. If
> - * non-panic CPUs are generating any messages, they will be
> - * silently dropped.
> - */
> - if (other_cpu_in_panic() && !panic_triggering_all_cpu_backtrace)
> - return 0;
> + if (!keep_printk_all_cpu_in_panic) {
> + /*
> + * The messages on the panic CPU are the most important. If
> + * non-panic CPUs are generating any messages, they will be
> + * silently dropped.
> + */
> + if (other_cpu_in_panic() && !panic_triggering_all_cpu_backtrace)
> + return 0;
> + }
I would not nest it. Just something like:
/*
* The messages on the panic CPU are the most important. If
* non-panic CPUs are generating any messages, they may be
* silently dropped.
*/
if (!keep_printk_all_cpu_in_panic &&
!panic_triggering_all_cpu_backtrace &&
other_cpu_in_panic()) {
return 0;
}
John
next prev parent reply other threads:[~2025-02-26 4:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20250226031756epcas2p3674cccc82687effb40575aa5fa2956e0@epcas2p3.samsung.com>
2025-02-26 3:16 ` printk: selective deactivation of feature ignoring non panic cpu's messages Donghyeok Choe
2025-02-26 4:25 ` John Ogness [this message]
2025-02-26 13:58 ` Petr Mladek
2025-02-28 14:20 ` John Ogness
2025-03-04 2:01 ` Donghyeok Choe
2025-03-04 13:22 ` Petr Mladek
2025-03-04 13:59 ` John Ogness
2025-03-04 14:15 ` Petr Mladek
2025-03-17 5:06 ` Donghyeok Choe
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=84ikoxxrfy.fsf@jogness.linutronix.de \
--to=john.ogness@linutronix.de \
--cc=d7271.choe@samsung.com \
--cc=hajun.sung@samsung.com \
--cc=jh1012.choi@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=seungh.jung@samsung.com \
--cc=takakura@valinux.co.jp \
--cc=youngmin.nam@samsung.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