From: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
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>
Subject: Re: [RFC/PATCH] printk: Fix preferred console selection with multiple matches
Date: Wed, 11 Dec 2019 11:01:49 +0900 [thread overview]
Message-ID: <20191211020149.GN88619@google.com> (raw)
In-Reply-To: <98df321d16adb67c5579ac4b67d845fc0c2c97df.camel@kernel.crashing.org>
On (19/12/11 09:26), Benjamin Herrenschmidt wrote:
[..]
> No not exactly. Architectures/platforms use add_preferred_console()
> (such as arm64 with ACPI but powerpc at least does it too) based on
> various factors to select a reasonable "default" for that specific
> platform. Without that the kernel will basically default to the first
> one to register which may not be what you want.
>
> The command line ones however want to override the defaults (provided
> they exist, ie, it's possible that whever is specified on the command
> line doesn't actually exist, and thus shall be ignored. That typically
> happens when there is either no match or ->setup fails).
>
> > 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?
>
> Why would the patch affect this negatively ? Today we stop on the first
> match, mark the driver enabled, and make it preferred if the match
> index matches preferred_console.
As far as I know, ->match() does not only match but also does ->setup().
If we have two console list entries that match (one via aliasing and one
via exact match) then the console driver is setup twice. Do all console
drivers handle it? [double setup]
If we could perform simple alias matching, without ->setup() call, and
exact matching (strcmp()), and then, if newcon would match two entries,
we would pick up the last matching entry and configure newcon only once.
This changes the order, tho.
[..]
> - Another match that is marked preferred_console, in which case in
> addition to being enabled, the newly registered console will also be
> made the default console (ie, first in the list with CONSDEV set). This
> is actually what we want ! IE. The console matches the last specified
> one on the command line.
Well, it still looks to me that what you want is to "ignore alias
match and prefer exact match".
-ss
next prev parent reply other threads:[~2019-12-11 2: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
2019-12-10 22:26 ` Benjamin Herrenschmidt
2019-12-11 2:01 ` Sergey Senozhatsky [this message]
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=20191211020149.GN88619@google.com \
--to=sergey.senozhatsky.work@gmail.com \
--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