From: Petr Mladek <pmladek@suse.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: "John Ogness" <john.ogness@linutronix.de>,
"Marek Behún" <kabel@kernel.org>,
"Linus Torvalds" <torvalds@linux-foundation.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Sergey Senozhatsky" <senozhatsky@chromium.org>,
"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
"Rasmus Villemoes" <linux@rasmusvillemoes.dk>,
"Jan Kara" <jack@suse.cz>,
"Peter Zijlstra" <peterz@infradead.org>
Subject: Re: [PATCH] printk/console: Enable console kthreads only when there is no boot console left
Date: Wed, 29 Jun 2022 10:29:56 +0200 [thread overview]
Message-ID: <20220629082956.GB3111@pathway.suse.cz> (raw)
In-Reply-To: <20220624184136.4aab12fb@rorschach.local.home>
On Fri 2022-06-24 18:41:36, Steven Rostedt wrote:
> On Tue, 21 Jun 2022 00:57:09 +0206
> John Ogness <john.ogness@linutronix.de> wrote:
>
> > Since early printing does not use the kernel driver model, I do not see
> > a clear solution at this point. But since using early printing is not a
> > typical use, I am OK with this patch.
>
> Does this patch still work if you add the "keep" flag to the
> earlyprintk kernel parameter?
It works. If the boot console stays then the console kthreads will
never get enabled.
Well, I hope that we will be able to add the synchronization and remove
this constraint. I think that the port->lock should be usable in
most cases.
Best Regards,
Petr
next prev parent reply other threads:[~2022-06-29 8:30 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-19 18:49 Boot stall regression from "printk for 5.19" merge Marek Behún
2022-06-19 22:23 ` John Ogness
2022-06-19 22:31 ` John Ogness
2022-06-20 10:02 ` Marek Behún
2022-06-20 9:29 ` Marek Behún
2022-06-20 11:44 ` Petr Mladek
2022-06-20 11:47 ` Petr Mladek
2022-06-20 12:04 ` Ilpo Järvinen
2022-06-20 13:48 ` Linus Torvalds
2022-06-20 14:24 ` Petr Mladek
2022-06-20 15:14 ` [PATCH] printk/console: Enable console kthreads only when there is no boot console left Petr Mladek
2022-06-20 15:16 ` Petr Mladek
2022-06-20 18:38 ` Marek Behún
2022-06-20 19:10 ` Linus Torvalds
2022-06-20 22:25 ` Petr Mladek
2022-06-20 22:51 ` John Ogness
2022-06-24 22:41 ` Steven Rostedt
2022-06-29 8:29 ` Petr Mladek [this message]
2022-06-20 5:23 ` Boot stall regression from "printk for 5.19" merge Sergey Senozhatsky
2022-06-20 10:02 ` Marek Behún
2022-06-20 10:13 ` Sergey Senozhatsky
2022-06-20 10:29 ` Marek Behún
2022-06-20 11:01 ` Andy Shevchenko
2022-06-20 10:38 ` Daniel Palmer
2022-06-21 9:39 ` Thorsten Leemhuis
2022-07-04 9:32 ` Boot stall regression from "printk for 5.19" merge #forregzbot Thorsten Leemhuis
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=20220629082956.GB3111@pathway.suse.cz \
--to=pmladek@suse.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=jack@suse.cz \
--cc=john.ogness@linutronix.de \
--cc=kabel@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=senozhatsky@chromium.org \
--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;
as well as URLs for NNTP newsgroup(s).