From: Randy Dunlap <randy.dunlap@oracle.com>
To: Remy Bohmer <linux@bohmer.net>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
Ingo Molnar <mingo@elte.hu>, Juergen Beisert <jbe@pengutronix.de>,
Darren Hart <dvhltc@us.ibm.com>,
linux-rt-users@vger.kernel.org,
Sven-Thorsten Dietrich <sdietrich@novell.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [patch 1/3] Add generic routine for parsing map-like options on kernel cmd-line (repost:CC to LKML)
Date: Wed, 19 Dec 2007 13:00:59 -0800 [thread overview]
Message-ID: <20071219130059.d99489d1.randy.dunlap@oracle.com> (raw)
In-Reply-To: <4769787e.01b4420a.2b28.ffff88cf@mx.google.com>
On Wed, 19 Dec 2007 20:45:52 +0100 Remy Bohmer wrote:
> This patch adds a generic routine to the kernel, so that a map of
> settings can be entered on the kernel commandline.
>
> Signed-off-by: Remy Bohmer <linux@bohmer.net>
>
> ---
> ---
> include/linux/kernel.h | 1
> lib/cmdline.c | 58 +++++++++++++++++++++++++++++++++++++++++++++++++
> 2 files changed, 59 insertions(+)
>
> Index: linux-2.6.24-rc5-rt1/lib/cmdline.c
> ===================================================================
> --- linux-2.6.24-rc5-rt1.orig/lib/cmdline.c 2007-10-09 22:31:38.000000000 +0200
> +++ linux-2.6.24-rc5-rt1/lib/cmdline.c 2007-12-18 21:33:58.000000000 +0100
> @@ -114,6 +115,63 @@ char *get_options(const char *str, int n
> }
>
> /**
> + * get_map_option - Parse integer from an option map
The @param lines (below) need to go here, immediately following the
function short description (the line above). No intervening blank
lines.
> + *
> + * This function parses an integer from an option map like
> + * some_map=key1:99,key2:98,...,keyN:NN,NN
> + * Only the value of the first match is returned, or if no
> + * key option is given (key = NULL) the value of the first
> + * field without a ':' is returned.
> + *
> + * @str: option string
> + * @key: The key inside the map, can be NULL
> + * @pint: (output) integer value parsed from the map @str
> + *
> + * Return values:
> + * 0 - no int in string
> + * 1 - int found
> + */
> +int get_map_option(const char *str, const char *key, int *pint)
> +{
> + char buf[COMMAND_LINE_SIZE];
COMMAND_LINE_SIZE varies from 256 to 2048, depending on $ARCH.
That's a bit too much to declare on a function's local stack --
unless you are very certain of the call tree to this point and
that the total stack size is safe. Can you just kmalloc() this
buf?
> + char *p, *substr;
> + int found = 0;
> +
> + /* We must copy the string to the stack, because strsep()
> + changes it.*/
> + strncpy(buf, str, COMMAND_LINE_SIZE);
> + buf[COMMAND_LINE_SIZE-1] = '\0';
> +
> + p = buf;
> + substr = strsep(&p, ",");
> + while ((!found) && (substr != NULL)) {
> + if (strlen(substr) != 0) {
> + if (key == NULL) {
> + /* Check for the absence of any ':' */
> + if (strchr(substr, ':') == NULL) {
> + sscanf(substr, "%d", pint);
> + found = 1;
> + }
> + } else {
> + /* check if the first part of the key matches */
> + if (!strncmp(substr, key, strlen(key))) {
> + substr += strlen(key);
> + /* Now the next char must be a ':',
> + if not, search for the next match */
> + if (*substr == ':') {
> + substr++;
> + sscanf(substr, "%d", pint);
> + found = 1;
> + }
> + }
> + }
> + }
> + substr = strsep(&p, ",");
> + }
> + return found;
> +}
---
~Randy
next prev parent reply other threads:[~2007-12-19 21:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20071219194551.315868746@bohmer.net>
2007-12-19 19:45 ` Remy Bohmer
2007-12-19 21:00 ` Randy Dunlap [this message]
2007-12-19 21:44 ` Remy Bohmer
2007-12-19 19:45 ` [patch 2/3] Enable setting of IRQ-thread priorities from kernel cmdline " Remy Bohmer
2007-12-19 20:51 ` Randy Dunlap
2007-12-20 12:02 ` Jaswinder Singh
2007-12-19 19:45 ` [patch 3/3] Enable setting of IRQ-thread priorities from kernel cmdline. " Remy Bohmer
2007-12-19 20:55 ` Randy Dunlap
2007-12-20 11:59 ` Jaswinder Singh
2007-12-20 12:25 ` Remy Bohmer
2007-12-20 12:45 ` Jaswinder Singh
2007-12-20 12:50 ` Remy Bohmer
2007-12-20 13:18 ` Juergen Beisert
2007-12-20 13:40 ` Jaswinder Singh
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=20071219130059.d99489d1.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=acme@ghostprotocols.net \
--cc=dvhltc@us.ibm.com \
--cc=jbe@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=linux@bohmer.net \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
--cc=sdietrich@novell.com \
/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
all inboxes | Powered by JetHome®