[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZlWtjOGNwFIgGYdt@pathway.suse.cz>
Date: Tue, 28 May 2024 12:10:20 +0200
From: Petr Mladek <pmladek@...e.com>
To: John Ogness <john.ogness@...utronix.de>
Cc: Sergey Senozhatsky <senozhatsky@...omium.org>,
Steven Rostedt <rostedt@...dmis.org>,
Thomas Gleixner <tglx@...utronix.de>, linux-kernel@...r.kernel.org,
"Paul E. McKenney" <paulmck@...nel.org>,
Miguel Ojeda <ojeda@...nel.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Jiri Slaby <jirislaby@...nel.org>, linux-serial@...r.kernel.org,
Russell King <linux@...linux.org.uk>,
Tony Lindgren <tony@...mide.com>,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
Florian Fainelli <florian.fainelli@...adcom.com>,
Uwe Kleine-König <u.kleine-koenig@...gutronix.de>,
Théo Lebrun <theo.lebrun@...tlin.com>,
Linus Walleij <linus.walleij@...aro.org>,
Ilpo Järvinen <ilpo.jarvinen@...ux.intel.com>,
Fabio Estevam <festevam@...x.de>,
Lino Sanfilippo <l.sanfilippo@...bus.com>,
Christophe JAILLET <christophe.jaillet@...adoo.fr>,
Arnd Bergmann <arnd@...db.de>,
Andrew Morton <akpm@...ux-foundation.org>,
Uros Bizjak <ubizjak@...il.com>, Lukas Wunner <lukas@...ner.de>,
Kefeng Wang <wangkefeng.wang@...wei.com>,
Ingo Molnar <mingo@...nel.org>,
Frederic Weisbecker <frederic@...nel.org>,
Neeraj Upadhyay <quic_neeraju@...cinc.com>,
Joel Fernandes <joel@...lfernandes.org>,
Josh Triplett <josh@...htriplett.org>,
Boqun Feng <boqun.feng@...il.com>,
Mathieu Desnoyers <mathieu.desnoyers@...icios.com>,
Lai Jiangshan <jiangshanlai@...il.com>,
Zqiang <qiang.zhang1211@...il.com>, rcu@...r.kernel.org,
Peter Zijlstra <peterz@...radead.org>,
Ingo Molnar <mingo@...hat.com>, Will Deacon <will@...nel.org>,
Waiman Long <longman@...hat.com>
Subject: Re: [PATCH printk v6 00/30] wire up write_atomic() printing
On Mon 2024-05-27 08:43:19, John Ogness wrote:
> Hi,
>
> This is v6 of a series to wire up the nbcon consoles so that
> they actually perform printing using their write_atomic()
> callback. v5 is here [0]. For information about the motivation
> of the atomic consoles, please read the cover letter of v1 [1].
>
> The main focus of this series:
>
> - For nbcon consoles, always call write_atomic() directly from
> printk() caller context for the panic CPU.
>
> - For nbcon consoles, call write_atomic() when unlocking the
> console lock.
>
> - Only perform the console lock/unlock dance if legacy or boot
> consoles are registered.
>
> - For legacy consoles, if nbcon consoles are registered, do not
> attempt to print from printk() caller context for the panic
> CPU until nbcon consoles have had a chance to print the most
> significant messages.
>
> - Mark emergency sections. In these sections printk() calls
> will only store the messages. Upon exiting the emergency
> section, nbcon consoles are flushed directly. If legacy
> consoles cannot be flushed safely, an irq_work is triggered
> to do the legacy console flushing.
>
> This series does _not_ include threaded printing or nbcon
> drivers. Those features will be added in separate follow-up
> series.
>
> Note: With this series, a system with _only_ nbcon consoles
> registered will not perform console printing unless the
> console lock or nbcon port lock are used or on panic.
> This is on purpose. When nbcon kthreads are introduced,
> they will fill the gaps.
The series seems to be ready for linux-next from my POV.
I am going to push it there so that we get as much testing
as possible before the next merge window.
Best Regards,
Petr
Powered by blists - more mailing lists