[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240725134742.GG13387@noisy.programming.kicks-ass.net>
Date: Thu, 25 Jul 2024 15:47:42 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: Petr Mladek <pmladek@...e.com>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
John Ogness <john.ogness@...utronix.de>,
Sergey Senozhatsky <senozhatsky@...omium.org>,
Steven Rostedt <rostedt@...dmis.org>,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
Rasmus Villemoes <linux@...musvillemoes.dk>,
Sebastian Andrzej Siewior <bigeasy@...utronix.de>,
Thomas Gleixner <tglx@...utronix.de>, Jan Kara <jack@...e.cz>,
linux-kernel@...r.kernel.org
Subject: Re: [GIT PULL] printk for 6.11
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.
Powered by blists - more mailing lists