mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jim Cromie <jim.cromie@gmail.com>
To: jbaron@akamai.com, linux-kernel@vger.kernel.org,
	akpm@linuxfoundation.org, gregkh@linuxfoundation.org
Cc: linux@rasmusvillemoes.dk, Jim Cromie <jim.cromie@gmail.com>
Subject: [PATCH v3 17/21] dyndbg: refactor ddebug_read_flags out of ddebug_parse_flags
Date: Wed, 17 Jun 2020 10:25:32 -0600	[thread overview]
Message-ID: <20200617162536.611386-20-jim.cromie@gmail.com> (raw)
In-Reply-To: <20200617162536.611386-1-jim.cromie@gmail.com>

Move flag-char reading and validating code to a separate function.

This will allow later reuse to read 2 sets of flags:

  1- flags to set or clear (after the [=-+] Operator)
  2- flags to require or prohibit before changing a callsite's flagstate

Signed-off-by: Jim Cromie <jim.cromie@gmail.com>
---
 lib/dynamic_debug.c | 37 +++++++++++++++++++++++--------------
 1 file changed, 23 insertions(+), 14 deletions(-)

diff --git a/lib/dynamic_debug.c b/lib/dynamic_debug.c
index 22335f7dbac1..8400e4f90b67 100644
--- a/lib/dynamic_debug.c
+++ b/lib/dynamic_debug.c
@@ -430,6 +430,26 @@ static int ddebug_parse_query(char *words[], int nwords,
 	return 0;
 }
 
+static int ddebug_read_flags(const char *str, struct flag_settings *modifiers)
+{
+	int i;
+
+	for (; *str ; ++str) {
+		for (i = ARRAY_SIZE(opt_array) - 1; i >= 0; i--) {
+			if (*str == opt_array[i].opt_char) {
+				modifiers->flags |= opt_array[i].flag;
+				break;
+			}
+		}
+		if (i < 0) {
+			pr_err("unknown flag '%c'\n", *str);
+			return -EINVAL;
+		}
+	}
+	vpr_info("flags=0x%x\n", modifiers->flags);
+	return 0;
+}
+
 /*
  * Parse `str' as a flags specification, format [-+=][p]+.
  * Sets up *maskp and *flagsp to be used when changing the
@@ -438,7 +458,7 @@ static int ddebug_parse_query(char *words[], int nwords,
  */
 static int ddebug_parse_flags(const char *str, struct flag_settings *modifiers)
 {
-	int op, i;
+	int op;
 
 	switch (*str) {
 	case '+':
@@ -452,19 +472,8 @@ static int ddebug_parse_flags(const char *str, struct flag_settings *modifiers)
 	}
 	vpr_info("op='%c'\n", op);
 
-	for (; *str ; ++str) {
-		for (i = ARRAY_SIZE(opt_array) - 1; i >= 0; i--) {
-			if (*str == opt_array[i].opt_char) {
-				modifiers->flags |= opt_array[i].flag;
-				break;
-			}
-		}
-		if (i < 0) {
-			pr_err("unknown flag '%c'\n", *str);
-			return -EINVAL;
-		}
-	}
-	vpr_info("flags=0x%x\n", modifiers->flags);
+	if (ddebug_read_flags(str, modifiers))
+		return -EINVAL;
 
 	/* calculate final flags, mask based upon op */
 	switch (op) {
-- 
2.26.2


  parent reply	other threads:[~2020-06-17 16:26 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-17 16:25 [PATCH v3 00/21] dynamic_debug cleanups, query features, export Jim Cromie
2020-06-17 16:25 ` [PATCH v3 01/21] dyndbg-docs: eschew file /full/path query in docs Jim Cromie
2020-06-17 16:25 ` [PATCH v3 02/21] dyndbg-docs: initialization is done early, not arch Jim Cromie
2020-06-17 16:25 ` [PATCH v3 03/21] dyndbg: drop obsolete comment on ddebug_proc_open Jim Cromie
2020-06-17 16:25 ` [PATCH v3 04/21] dyndbg: refine debug verbosity; 1 is basic, 2 more chatty Jim Cromie
2020-06-17 16:25 ` [PATCH v3 05/21] dyndbg: rename __verbose section to __dyndbg Jim Cromie
2020-06-17 16:25 ` [PATCH v3 06/21] dyndbg: fix overcounting of ram used by dyndbg Jim Cromie
2020-06-17 16:25 ` [PATCH v3 07/21] dyndbg: fix a BUG_ON in ddebug_describe_flags Jim Cromie
2020-06-17 16:25 ` [PATCH v3 08/21] dyndbg: fix pr_err with empty string Jim Cromie
2020-06-17 16:25 ` [PATCH v3 09/21] dyndbg: prefer declarative init in caller, to memset in callee Jim Cromie
2020-06-17 16:25 ` [PATCH v3 10/21] dyndbg: make ddebug_tables list LIFO for add/remove_module Jim Cromie
2020-06-17 16:25 ` [PATCH v3 11/21] dyndbg: use gcc ?: to reduce word count Jim Cromie
2020-06-17 16:25 ` [PATCH v3 12/21] dyndbg: refactor parse_linerange out of ddebug_parse_query Jim Cromie
2020-06-17 16:25 ` [PATCH v3 13/21] dyndbg: accept 'file foo.c:func1' and 'file foo.c:10-100' Jim Cromie
2020-06-17 16:25 ` [PATCH v3 14/21] dyndbg: accept query terms like file=bar and module=foo Jim Cromie
2020-06-18 22:25   ` jim.cromie
2020-06-17 16:25 ` [PATCH v3 14/21] dyndbg: accept query terms like file=bar module=foo Jim Cromie
2020-06-17 16:25 ` [PATCH v3 14/21] dyndbg: accept query terms like module:foo and file=bar Jim Cromie
2020-06-17 16:25 ` [PATCH v3 15/21] dyndbg: export ddebug_exec_queries Jim Cromie
2020-06-17 16:25 ` [PATCH v3 16/21] dyndbg: combine flags & mask into a struct, simplify with it Jim Cromie
2020-06-17 16:25 ` Jim Cromie [this message]
2020-06-17 16:25 ` [PATCH v3 18/21] dyndbg: add filter channel to the internals Jim Cromie
2020-06-17 16:25 ` [PATCH v3 19/21] dyndbg: extend ddebug_parse_flags to accept optional leading filter-flags Jim Cromie
2020-06-18 12:44   ` Petr Mladek
2020-06-18 14:54     ` jim.cromie
2020-06-18 16:01       ` Petr Mladek
2020-06-17 16:25 ` [PATCH v3 20/21] dyndbg: add user-flag, negating-flags, and filtering on flags Jim Cromie
2020-06-17 22:13   ` Joe Perches
2020-06-17 22:57     ` jim.cromie
2020-06-18 16:19   ` Petr Mladek
2020-06-18 17:40     ` Petr Mladek
2020-06-18 18:17       ` Jason Baron
2020-06-18 19:11         ` jim.cromie
2020-06-18 19:40           ` Jason Baron
2020-06-18 21:31             ` jim.cromie
2020-06-18 22:34             ` Stanimir Varbanov
2020-06-18 22:48               ` jim.cromie
2020-06-19 16:07                 ` Jason Baron
2020-06-19  7:45           ` Petr Mladek
2020-06-19  8:10             ` Petr Mladek
2020-06-19  8:34               ` Greg KH
2020-06-18 18:15     ` jim.cromie
2020-06-17 16:25 ` [PATCH v3 21/21] dyndbg: allow negating flag-chars in modifier flags Jim Cromie
2020-06-17 20:05 ` [PATCH v3 00/21] dynamic_debug cleanups, query features, export Rasmus Villemoes

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=20200617162536.611386-20-jim.cromie@gmail.com \
    --to=jim.cromie@gmail.com \
    --cc=akpm@linuxfoundation.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jbaron@akamai.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@rasmusvillemoes.dk \
    /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®