From: Jonathan Corbet <corbet@lwn.net>
To: John Ogness <john.ogness@linutronix.de>,
h3288824963 <3288824963@qq.com>,
linux-doc@vger.kernel.org
Cc: pmladek@suse.com, senozhatsky@chromium.org, rostedt@goodmis.org,
qujingling@huawei.com, zhangjiaji1@huawei.com,
xushuangxing@huawei.com, hujinfei3@huawei.com,
h3288824963 <3288824963@qq.com>
Subject: Re: [PATCH v2] Documentation: printk: Add section about avoiding lockups
Date: Tue, 17 Mar 2026 08:41:43 -0600 [thread overview]
Message-ID: <87a4w6ecwo.fsf@trenco.lwn.net> (raw)
In-Reply-To: <87341yd79c.fsf@jogness.linutronix.de>
John Ogness <john.ogness@linutronix.de> writes:
> On 2026-03-17, h3288824963 <3288824963@qq.com> wrote:
>> Add a section 'Avoiding lockups from excessive printk() use' to
>> printk-basics.rst, explaining the risk of calling printk() in hot paths
>> with legacy consoles and suggesting alternatives.
>>
>> The section covers:
>> - Rate-limited and one-time printing variants
>> - Log level filtering
>> - printk_deferred() for legacy consoles
>> - Porting to nbcon API (preferred solution)
>> - Using tracepoints for permanent debugging
>>
>> This documentation is relevant only for legacy console drivers and
>> !PREEMPT_RT kernels.
>>
>> Suggested-by: Petr Mladek <pmladek@suse.com>
>> Suggested-by: John Ogness <john.ogness@linutronix.de>
>> Signed-off-by: h3288824963 <3288824963@qq.com>
>
> Thanks for addressing my concerns.
>
> Reviewed-by: John Ogness <john.ogness@linutronix.de>
Applied, thanks.
jon
prev parent reply other threads:[~2026-03-17 14:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-17 10:57 [PATCH v2] Documentation: printk: Add section about avoiding lockups h3288824963
2026-03-17 11:29 ` John Ogness
2026-03-17 14:41 ` Jonathan Corbet [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=87a4w6ecwo.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=3288824963@qq.com \
--cc=hujinfei3@huawei.com \
--cc=john.ogness@linutronix.de \
--cc=linux-doc@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=qujingling@huawei.com \
--cc=rostedt@goodmis.org \
--cc=senozhatsky@chromium.org \
--cc=xushuangxing@huawei.com \
--cc=zhangjiaji1@huawei.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