From: Steven Rostedt <rostedt@goodmis.org>
To: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
Ingo Molnar <mingo@elte.hu>,
linux-perf-users@vger.kernel.org
Subject: Re: [PATCH] perf tools: Allow expressions in __print_symbolic() fields
Date: Wed, 08 Feb 2012 20:44:24 -0500 [thread overview]
Message-ID: <1328751864.2200.125.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <1315148939-14313-1-git-send-email-stefanha@linux.vnet.ibm.com>
Arnaldo,
Can you pull this patch into perf? You can add my:
Acked-by: Steven Rostedt <rostedt@goodmis.org>
Thanks!
-- Steve
On Sun, 2011-09-04 at 16:08 +0100, Stefan Hajnoczi wrote:
> The __print_symbolic() function takes a sequence of key-value pairs for
> pretty-printing a constant. The new kvm:kvm_exit print fmt uses the
> expression:
>
> __print_symbolic(..., { 0x040 + 1, "DB excp" }, ...)
>
> Currently only atoms are supported and this print fmt fails to parse.
> This patch adds support for expressions instead of just atoms so that
> 0x040 + 1 is parsed successfully. Also add arg_num_eval() support for
> the '+' operator.
>
> Signed-off-by: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
> ---
> The kvm:kvm_exit event was not recording enough information to format it. I
> recently fixed this by introducing a __print_symbolic(), this commit has not
> yet hit linux.git but I think it will soon. In order to correctly format the
> new kvm:kvm_exit, this patch to extend event parsing is required.
>
> tools/perf/util/trace-event-parse.c | 12 ++++++++++++
> 1 files changed, 12 insertions(+), 0 deletions(-)
>
> diff --git a/tools/perf/util/trace-event-parse.c b/tools/perf/util/trace-event-parse.c
> index 0a7ed5b..d0a4548 100644
> --- a/tools/perf/util/trace-event-parse.c
> +++ b/tools/perf/util/trace-event-parse.c
> @@ -1425,6 +1425,11 @@ static long long arg_num_eval(struct print_arg *arg)
> die("unknown op '%s'", arg->op.op);
> }
> break;
> + case '+':
> + left = arg_num_eval(arg->op.left);
> + right = arg_num_eval(arg->op.right);
> + val = left + right;
> + break;
> default:
> die("unknown op '%s'", arg->op.op);
> }
> @@ -1485,6 +1490,13 @@ process_fields(struct event *event, struct print_flag_sym **list, char **tok)
>
> free_token(token);
> type = process_arg(event, arg, &token);
> +
> + if (type == EVENT_OP)
> + type = process_op(event, arg, &token);
> +
> + if (type == EVENT_ERROR)
> + goto out_free;
> +
> if (test_type_token(type, token, EVENT_DELIM, ","))
> goto out_free;
>
prev parent reply other threads:[~2012-02-09 1:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-04 15:08 [PATCH] perf tools: Allow expressions in __print_symbolic() fields Stefan Hajnoczi
2012-02-09 1:44 ` Steven Rostedt [this message]
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=1328751864.2200.125.camel@gandalf.stny.rr.com \
--to=rostedt@goodmis.org \
--cc=acme@ghostprotocols.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=stefanha@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).