From: Chris Down <chris@chrisdown.name>
To: Petr Mladek <pmladek@suse.com>
Cc: linux-kernel@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Sergey Senozhatsky <senozhatsky@chromium.org>,
Steven Rostedt <rostedt@goodmis.org>,
John Ogness <john.ogness@linutronix.de>,
Geert Uytterhoeven <geert@linux-m68k.org>,
kernel-team@fb.com
Subject: Re: [PATCH v3 1/2] printk: console: Create console= parser that supports named options
Date: Mon, 17 Apr 2023 16:04:27 +0100 [thread overview]
Message-ID: <ZD1f-1JjpihR1djd@chrisdown.name> (raw)
In-Reply-To: <Yw80MmyBl4js09If@alley>
(To others on this thread wondering about this patchset, Petr and I have had
some discussions offlist about v4 and it should be up soon.)
Petr Mladek writes:
>I thought a lot how to do it a clean way. IMHO, it would be great to
>parse everything at a single place but it might require updating
>all drivers. I am not sure if it is worth it.
>
>So, I suggest to do it another way. We could implement a generic
>function to find in the new key[:value] format. It would check
>if the given option (key) exists and read the optional value.
>
>The optional value would allow to define another new options
>that would not need any value, e.g. "kthread" or "atomic" that
>might be used in the upcoming code that allows to offload
>console handling to kthreads.
Any thoughts on something simple like this that takes advantage of memmove()?
This should overcome the mmio/io concerns, and it's fairly simple.
---
static bool find_and_remove_console_option(char *buf, size_t size,
const char *wanted, char *options)
{
bool found = false, first = true;
char *item, *opt = options;
while ((item = strsep(&opt, ","))) {
char *key = item, *value;
value = strchr(item, ':');
if (value)
*(value++) = '\0';
if (strcmp(key, wanted) == 0) {
found = true;
if (value) {
if (strlen(value) > size - 1) {
pr_warn("Can't copy console option value for %s:%s: not enough space (%zu)\n",
key, value, size);
found = false;
} else {
strscpy(buf, value, size);
}
} else
*buf = '\0';
}
if (!found && opt)
*(opt - 1) = ',';
if (!found && value)
*(value - 1) = ':';
if (!first)
*(item - 1) = ',';
if (found)
break;
first = false;
}
if (found) {
if (opt)
memmove(item, opt, strlen(opt) + 1);
else if (first)
*item = '\0';
else
*--item = '\0';
}
return found;
}
next prev parent reply other threads:[~2023-04-17 15:04 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-20 17:48 [PATCH v3 0/2] printk: console: Per-console loglevels Chris Down
2022-07-20 17:48 ` [PATCH v3 1/2] printk: console: Create console= parser that supports named options Chris Down
2022-08-31 10:13 ` Petr Mladek
2022-09-05 14:43 ` Chris Down
2022-09-05 14:45 ` Chris Down
2022-09-22 15:17 ` Petr Mladek
2023-04-17 15:04 ` Chris Down [this message]
2023-04-17 15:08 ` Chris Down
2023-04-18 13:43 ` Petr Mladek
2023-04-18 13:41 ` Petr Mladek
2023-04-19 0:31 ` Chris Down
2022-07-20 17:48 ` [PATCH v3 2/2] printk: console: Support console-specific loglevels Chris Down
2022-07-21 9:50 ` kernel test robot
2022-07-21 16:20 ` Chris Down
2022-07-21 16:16 ` kernel test robot
2022-07-21 16:29 ` Chris Down
2022-09-01 9:35 ` Petr Mladek
2022-09-05 14:07 ` Chris Down
2022-09-05 15:12 ` Petr Mladek
2022-07-20 18:22 ` [PATCH v3 0/2] printk: console: Per-console loglevels John Ogness
2022-07-20 18:29 ` Chris Down
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=ZD1f-1JjpihR1djd@chrisdown.name \
--to=chris@chrisdown.name \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=john.ogness@linutronix.de \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=senozhatsky@chromium.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