All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Rutland <mark.rutland@arm.com>
To: linux-kernel@vger.kernel.org
Cc: linux-trace-kernel@vger.kernel.org, mark.rutland@arm.com,
	mhiramat@kernel.org, rostedt@goodmis.org, zanussi@kernel.org
Subject: [PATCH 1/2] tracing/hist: simplify contains_operator()
Date: Thu,  2 Mar 2023 17:17:54 +0000	[thread overview]
Message-ID: <20230302171755.1821653-2-mark.rutland@arm.com> (raw)
In-Reply-To: <20230302171755.1821653-1-mark.rutland@arm.com>

In a subsequent patch we'll add additional operators for histogram
expressions.

In preparation for adding additional operators, this patch refactors
contains_operator() to consider each operator within a precedence group
independently by using the 'sep' pointer as the current rightmost
operator, and removing the separate op pointers.

Within each precedence group, this allows operators to be checked
independently with a consistent pattern:

	op = strrchr(str, $OP_CHAR);
	if (op > *sep) {
		*sep = op;
		field_op = $FIELD_OP_TYPE;
	}

This makes it easy to add new operators of the same precedence without
needing to check multiple pointers, and without needing a final switch
statement to recover the relevant pointer.

There should be no functional change as a result of this patch.

Signed-off-by: Mark Rutland <mark.rutland@arm.com>
Cc: Masami Hiramatsu <mhiramat@kernel.org>
Cc: Steven Rostedt (Google) <rostedt@goodmis.org>
Cc: Tom Zanussi <zanussi@kernel.org>
Cc: linux-trace-kernel@vger.kernel.org
---
 kernel/trace/trace_events_hist.c | 80 ++++++++++++--------------------
 1 file changed, 30 insertions(+), 50 deletions(-)

diff --git a/kernel/trace/trace_events_hist.c b/kernel/trace/trace_events_hist.c
index 10d36f751fcd..a308da2cde2f 100644
--- a/kernel/trace/trace_events_hist.c
+++ b/kernel/trace/trace_events_hist.c
@@ -1813,13 +1813,15 @@ static char *expr_str(struct hist_field *field, unsigned int level)
 static int contains_operator(char *str, char **sep)
 {
 	enum field_op_id field_op = FIELD_OP_NONE;
-	char *minus_op, *plus_op, *div_op, *mult_op;
+	char *op;
 
+	*sep = NULL;
 
 	/*
-	 * Report the last occurrence of the operators first, so that the
-	 * expression is evaluated left to right. This is important since
-	 * subtraction and division are not associative.
+	 * For operators of the same precedence report the last occurrence of
+	 * the operators first, so that the expression is evaluated left to
+	 * right. This is important since subtraction and division are not
+	 * associative.
 	 *
 	 *	e.g
 	 *		64/8/4/2 is 1, i.e 64/8/4/2 = ((64/8)/4)/2
@@ -1830,68 +1832,46 @@ static int contains_operator(char *str, char **sep)
 	 * First, find lower precedence addition and subtraction
 	 * since the expression will be evaluated recursively.
 	 */
-	minus_op = strrchr(str, '-');
-	if (minus_op) {
+	op = strrchr(str, '-');
+	if (op > *sep) {
+		*sep = op;
+
 		/*
 		 * Unary minus is not supported in sub-expressions. If
 		 * present, it is always the next root operator.
 		 */
-		if (minus_op == str) {
-			field_op = FIELD_OP_UNARY_MINUS;
-			goto out;
-		}
+		if (op == str)
+			return FIELD_OP_UNARY_MINUS;
 
 		field_op = FIELD_OP_MINUS;
 	}
 
-	plus_op = strrchr(str, '+');
-	if (plus_op || minus_op) {
-		/*
-		 * For operators of the same precedence use to rightmost as the
-		 * root, so that the expression is evaluated left to right.
-		 */
-		if (plus_op > minus_op)
-			field_op = FIELD_OP_PLUS;
-		goto out;
+	op = strrchr(str, '+');
+	if (op > *sep) {
+		*sep = op;
+		field_op = FIELD_OP_PLUS;
 	}
 
 	/*
-	 * Multiplication and division have higher precedence than addition and
-	 * subtraction.
+	 * If we've found a low-precedence operator, we're done.
 	 */
-	div_op = strrchr(str, '/');
-	if (div_op)
-		field_op = FIELD_OP_DIV;
+	if (*sep)
+		return field_op;
 
-	mult_op = strrchr(str, '*');
 	/*
-	 * For operators of the same precedence use to rightmost as the
-	 * root, so that the expression is evaluated left to right.
+	 * Second, consider the higher precedence multiplication and division
+	 * operators.
 	 */
-	if (mult_op > div_op)
-		field_op = FIELD_OP_MULT;
+	op = strrchr(str, '/');
+	if (op > *sep) {
+		*sep = op;
+		field_op = FIELD_OP_DIV;
+	}
 
-out:
-	if (sep) {
-		switch (field_op) {
-		case FIELD_OP_UNARY_MINUS:
-		case FIELD_OP_MINUS:
-			*sep = minus_op;
-			break;
-		case FIELD_OP_PLUS:
-			*sep = plus_op;
-			break;
-		case FIELD_OP_DIV:
-			*sep = div_op;
-			break;
-		case FIELD_OP_MULT:
-			*sep = mult_op;
-			break;
-		case FIELD_OP_NONE:
-		default:
-			*sep = NULL;
-			break;
-		}
+	op = strrchr(str, '*');
+	if (op > *sep) {
+		*sep = op;
+		field_op = FIELD_OP_MULT;
 	}
 
 	return field_op;
-- 
2.30.2


  reply	other threads:[~2023-03-02 17:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-02 17:17 [PATCH 0/2] tracing/hist: add a modulus operator Mark Rutland
2023-03-02 17:17 ` Mark Rutland [this message]
2023-03-18 19:12   ` [PATCH 1/2] tracing/hist: simplify contains_operator() Steven Rostedt
2023-03-22 13:13     ` Mark Rutland
2023-03-02 17:17 ` [PATCH 2/2] tracing/hist: add modulus operator Mark Rutland
2023-03-02 21:41   ` kernel test robot
2023-03-03 12:56   ` kernel test robot
2023-03-18 19:19   ` Steven Rostedt
2023-03-22 13:40     ` Mark Rutland

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=20230302171755.1821653-2-mark.rutland@arm.com \
    --to=mark.rutland@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=mhiramat@kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=zanussi@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.