From: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linux-kernel@vger.kernel.org, Petr Mladek <pmladek@suse.com>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
AlekseyMakarov <aleksey.makarov@linaro.org>
Subject: Re: [RFC/PATCH] printk: Fix preferred console selection with multiple matches
Date: Tue, 10 Dec 2019 17:01:54 +0900 [thread overview]
Message-ID: <20191210080154.GJ88619@google.com> (raw)
In-Reply-To: <b8131bf32a5572352561ec7f2457eb61cc811390.camel@kernel.crashing.org>
On (19/12/10 11:57), Benjamin Herrenschmidt wrote:
[..]
> - add_preferred_console is called early to register "uart0". In
> our case that happens from acpi_parse_spcr() on arm64 since the
> "enable_console" argument is true on that architecture. This causes
> "uart0" to become entry 0 of the console_cmdline array.
Hmm, two independent console list configuration sources.
[..]
> +++ b/kernel/printk/printk.c
> @@ -2646,8 +2646,8 @@ void register_console(struct console *newcon)
> if (i == preferred_console) {
> newcon->flags |= CON_CONSDEV;
> has_preferred = true;
> + break;
> }
> - break;
> }
>
> if (!(newcon->flags & CON_ENABLED))
Wouldn't this, basically, mean that we want to match only consoles,
which were in the kernel's console= cmdline? IOW, ignore consoles
that were placed into consoles list via alternative path - ACPI.
Hmm.
The patch may affect setups where alias matching is expected to
happen. E.g.:
console=uartFOO,BAR
Is 8250 the only console that does alias matching?
-ss
next prev parent reply other threads:[~2019-12-10 8:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-10 0:57 [RFC/PATCH] printk: Fix preferred console selection with multiple matches Benjamin Herrenschmidt
2019-12-10 8:01 ` Sergey Senozhatsky [this message]
2019-12-10 22:26 ` Benjamin Herrenschmidt
2019-12-11 2:01 ` Sergey Senozhatsky
2019-12-11 4:02 ` Benjamin Herrenschmidt
2019-12-11 5:35 ` Sergey Senozhatsky
2019-12-11 12:53 ` Petr Mladek
2019-12-10 9:15 ` Petr Mladek
2019-12-10 22:39 ` Benjamin Herrenschmidt
2019-12-11 9:17 ` Petr Mladek
2019-12-12 1:23 ` Sergey Senozhatsky
2019-12-16 0:09 ` Benjamin Herrenschmidt
2019-12-19 9:50 ` Petr Mladek
2019-12-12 0:35 ` Benjamin Herrenschmidt
2019-12-12 9:09 ` Petr Mladek
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=20191210080154.GJ88619@google.com \
--to=sergey.senozhatsky.work@gmail.com \
--cc=aleksey.makarov@linaro.org \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky@gmail.com \
--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