From: Jiri Olsa <jolsa@redhat.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: acme@kernel.org, jolsa@kernel.org, linux-kernel@vger.kernel.org,
Andi Kleen <ak@linux.intel.com>
Subject: Re: [PATCH v1 07/15] perf, tools: Expression parser enhancements for metrics
Date: Mon, 7 Aug 2017 11:51:55 +0200 [thread overview]
Message-ID: <20170807095155.GB13591@krava> (raw)
In-Reply-To: <20170724234015.5165-8-andi@firstfloor.org>
On Mon, Jul 24, 2017 at 04:40:07PM -0700, Andi Kleen wrote:
> From: Andi Kleen <ak@linux.intel.com>
>
> Enhance the expression parser for more complex metric formulas.
>
> - Support python style IF ELSE operators
> - Support MIN/MAX operations
> - Support | & ^ operators
> - Minor cleanups and fixes
> - Add an #SMT_On magic variable for formulas that depend on the SMT
> status.
> - Support an \ escape for operators. This allows to specify event names
> like c2-residency
please state some examples of this
thanks,
jirka
> - Support @ as an alternative for / to be able to specify pmus without
> conflicts with operators (like msr/tsc/ as msr@tsc@)
>
> Signed-off-by: Andi Kleen <ak@linux.intel.com>
> ---
> tools/perf/tests/expr.c | 5 ++++
> tools/perf/util/expr.y | 61 ++++++++++++++++++++++++++++++++++++++++++++-----
> 2 files changed, 60 insertions(+), 6 deletions(-)
>
> diff --git a/tools/perf/tests/expr.c b/tools/perf/tests/expr.c
> index 6c6a3749aaf6..e75365098f23 100644
> --- a/tools/perf/tests/expr.c
> +++ b/tools/perf/tests/expr.c
> @@ -31,6 +31,11 @@ int test__expr(int subtest __maybe_unused)
> ret |= test(&ctx, "(BAR/2)%2", 1);
> ret |= test(&ctx, "1 - -4", 5);
> ret |= test(&ctx, "(FOO-1)*2 + (BAR/2)%2 - -4", 5);
> + ret |= test(&ctx, "1-1 | 1", 1);
> + ret |= test(&ctx, "1-1 & 1", 0);
> + ret |= test(&ctx, "min(1,2) + 1", 2);
> + ret |= test(&ctx, "max(1,2) + 1", 3);
> + ret |= test(&ctx, "1+1 if 3*4 else 0", 2);
>
> if (ret)
> return ret;
> diff --git a/tools/perf/util/expr.y b/tools/perf/util/expr.y
> index 953e65ba2cc7..5753c4f21534 100644
> --- a/tools/perf/util/expr.y
> +++ b/tools/perf/util/expr.y
> @@ -4,6 +4,7 @@
> #include "util/debug.h"
> #define IN_EXPR_Y 1
> #include "expr.h"
> +#include "smt.h"
> #include <string.h>
>
> #define MAXIDLEN 256
> @@ -22,13 +23,15 @@
>
> %token <num> NUMBER
> %token <id> ID
> +%token MIN MAX IF ELSE SMT_ON
> +%left MIN MAX IF
> %left '|'
> %left '^'
> %left '&'
> %left '-' '+'
> %left '*' '/' '%'
> %left NEG NOT
> -%type <num> expr
> +%type <num> expr if_expr
>
> %{
> static int expr__lex(YYSTYPE *res, const char **pp);
> @@ -57,7 +60,12 @@ static int lookup_id(struct parse_ctx *ctx, char *id, double *val)
> %}
> %%
>
> -all_expr: expr { *final_val = $1; }
> +all_expr: if_expr { *final_val = $1; }
> + ;
> +
> +if_expr:
> + expr IF expr ELSE expr { $$ = $3 ? $1 : $5; }
> + | expr
> ;
>
> expr: NUMBER
> @@ -66,13 +74,19 @@ expr: NUMBER
> YYABORT;
> }
> }
> + | expr '|' expr { $$ = (long)$1 | (long)$3; }
> + | expr '&' expr { $$ = (long)$1 & (long)$3; }
> + | expr '^' expr { $$ = (long)$1 ^ (long)$3; }
> | expr '+' expr { $$ = $1 + $3; }
> | expr '-' expr { $$ = $1 - $3; }
> | expr '*' expr { $$ = $1 * $3; }
> | expr '/' expr { if ($3 == 0) YYABORT; $$ = $1 / $3; }
> | expr '%' expr { if ((long)$3 == 0) YYABORT; $$ = (long)$1 % (long)$3; }
> | '-' expr %prec NEG { $$ = -$2; }
> - | '(' expr ')' { $$ = $2; }
> + | '(' if_expr ')' { $$ = $2; }
> + | MIN '(' expr ',' expr ')' { $$ = $3 < $5 ? $3 : $5; }
> + | MAX '(' expr ',' expr ')' { $$ = $3 > $5 ? $3 : $5; }
> + | SMT_ON { $$ = smt_on() > 0; }
> ;
>
> %%
> @@ -82,13 +96,47 @@ static int expr__symbol(YYSTYPE *res, const char *p, const char **pp)
> char *dst = res->id;
> const char *s = p;
>
> - while (isalnum(*p) || *p == '_' || *p == '.') {
> + if (*p == '#')
> + *dst++ = *p++;
> +
> + while (isalnum(*p) || *p == '_' || *p == '.' || *p == ':' || *p == '@' || *p == '\\') {
> if (p - s >= MAXIDLEN)
> return -1;
> - *dst++ = *p++;
> + /*
> + * Allow @ instead of / to be able to specify pmu/event/ without
> + * conflicts with normal division.
> + */
> + if (*p == '@')
> + *dst++ = '/';
> + else if (*p == '\\')
> + *dst++ = *++p;
> + else
> + *dst++ = *p;
> + p++;
> }
> *dst = 0;
> *pp = p;
> + dst = res->id;
> + switch (dst[0]) {
> + case 'm':
> + if (!strcmp(dst, "min"))
> + return MIN;
> + if (!strcmp(dst, "max"))
> + return MAX;
> + break;
> + case 'i':
> + if (!strcmp(dst, "if"))
> + return IF;
> + break;
> + case 'e':
> + if (!strcmp(dst, "else"))
> + return ELSE;
> + break;
> + case '#':
> + if (!strcasecmp(dst, "#smt_on"))
> + return SMT_ON;
> + break;
> + }
> return ID;
> }
>
> @@ -102,6 +150,7 @@ static int expr__lex(YYSTYPE *res, const char **pp)
> p++;
> s = p;
> switch (*p++) {
> + case '#':
> case 'a' ... 'z':
> case 'A' ... 'Z':
> return expr__symbol(res, p - 1, pp);
> @@ -151,7 +200,7 @@ int expr__find_other(const char *p, const char *one, const char ***other,
> err = 0;
> break;
> }
> - if (tok == ID && strcasecmp(one, val.id)) {
> + if (tok == ID && (!one || strcasecmp(one, val.id))) {
> if (num_other >= EXPR_MAX_OTHER - 1) {
> pr_debug("Too many extra events in %s\n", orig);
> break;
> --
> 2.9.4
>
next prev parent reply other threads:[~2017-08-07 9:52 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-24 23:40 Support standalone metrics and metric groups for perf Andi Kleen
2017-07-24 23:40 ` [PATCH v1 01/15] perf, tools, stat: Fix buffer overflow while freeing events Andi Kleen
2017-08-01 8:11 ` Jiri Olsa
2017-07-24 23:40 ` [PATCH v1 02/15] perf, tools: Tighten detection of BPF events Andi Kleen
2017-08-02 7:35 ` Jiri Olsa
2017-08-02 19:10 ` Arnaldo Carvalho de Melo
2017-07-24 23:40 ` [PATCH v1 03/15] perf, tools, stat: Fix saved values rbtree lookup Andi Kleen
2017-08-02 7:35 ` Jiri Olsa
2017-08-02 19:11 ` Arnaldo Carvalho de Melo
2017-08-14 17:43 ` [tip:perf/core] perf " tip-bot for Andi Kleen
2017-07-24 23:40 ` [PATCH v1 04/15] perf, tools: Support weak groups Andi Kleen
2017-08-02 7:35 ` Jiri Olsa
2017-07-24 23:40 ` [PATCH v1 05/15] perf, tools: Add missing newline to expr parser error messages Andi Kleen
2017-08-02 7:37 ` Jiri Olsa
2017-08-14 17:44 ` [tip:perf/core] perf " tip-bot for Andi Kleen
2017-07-24 23:40 ` [PATCH v1 06/15] perf, tools: Add utility function to detect SMT status Andi Kleen
2017-07-24 23:40 ` [PATCH v1 07/15] perf, tools: Expression parser enhancements for metrics Andi Kleen
2017-08-07 9:51 ` Jiri Olsa [this message]
2017-07-24 23:40 ` [PATCH v1 08/15] perf, tools: Increase maximum number of events in expressions Andi Kleen
2017-07-24 23:40 ` [PATCH v1 09/15] perf, tools: Dedup events in expression parsing Andi Kleen
2017-08-07 9:51 ` Jiri Olsa
2017-07-24 23:40 ` [PATCH v1 10/15] perf, tools: Support metric_group and no event name in json parser Andi Kleen
2017-07-24 23:40 ` [PATCH v1 11/15] perf, tools, stat: Factor out generic metric printing Andi Kleen
2017-07-24 23:40 ` [PATCH v1 12/15] perf, tools, stat: Support JSON metrics in perf stat Andi Kleen
2017-07-24 23:40 ` [PATCH v1 13/15] perf, tools, list: Add metric groups to perf list Andi Kleen
2017-07-24 23:40 ` [PATCH v1 14/15] perf, tools, stat: Don't use ctx for saved values lookup Andi Kleen
2017-07-24 23:40 ` [PATCH v1 15/15] perf, tools: Support duration_time Andi Kleen
2017-08-07 10:36 ` Jiri Olsa
2017-07-26 14:15 ` Support standalone metrics and metric groups for perf Jiri Olsa
2017-07-26 15:38 ` Andi Kleen
2017-07-28 8:48 ` Jiri Olsa
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=20170807095155.GB13591@krava \
--to=jolsa@redhat.com \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=andi@firstfloor.org \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).