From: Peter Zijlstra <peterz@infradead.org>
To: Petr Mladek <pmladek@suse.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
John Ogness <john.ogness@linutronix.de>,
Sergey Senozhatsky <senozhatsky@chromium.org>,
Steven Rostedt <rostedt@goodmis.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Thomas Gleixner <tglx@linutronix.de>, Jan Kara <jack@suse.cz>,
linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] printk for 6.11
Date: Thu, 25 Jul 2024 15:47:42 +0200 [thread overview]
Message-ID: <20240725134742.GG13387@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <ZqJKbcLgTeYRkDd6@pathway.suse.cz>
On Thu, Jul 25, 2024 at 02:51:57PM +0200, Petr Mladek wrote:
> I am afraid that we have to live with some buffering. Otherwhise,
> the speed of the system might be limited by the speed of the consoles.
> This might be especially noticeable during boot when a lot of HW
> gets initialized and tons of messages are flushed to a slow serial console.
Only if you create a slow atomic console. But other than that, I've been
booting like that for at least the last decade or so.
Most all my test boxes have forced synchronous earlyprintk at 115200
baud. It has saved me untold times.
I suppose I'll just keep my own printk hackery around for longer.
next prev parent reply other threads:[~2024-07-25 13:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-23 14:38 [GIT PULL] printk for 6.11 Petr Mladek
2024-07-23 18:04 ` Linus Torvalds
2024-07-23 20:41 ` John Ogness
2024-07-23 21:07 ` Linus Torvalds
2024-07-24 8:42 ` Petr Mladek
2024-07-24 12:47 ` Peter Zijlstra
2024-07-24 20:33 ` Linus Torvalds
2024-07-25 12:51 ` Petr Mladek
2024-07-25 13:47 ` Peter Zijlstra [this message]
2024-07-25 16:48 ` Linus Torvalds
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=20240725134742.GG13387@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bigeasy@linutronix.de \
--cc=jack@suse.cz \
--cc=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=senozhatsky@chromium.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
/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