linux-trace-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Beau Belgrave <beaub@linux.microsoft.com>
To: Masami Hiramatsu <mhiramat@kernel.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
	linux-trace-devel@vger.kernel.org,
	Tzvetomir Stoyanov <tz.stoyanov@gmail.com>
Subject: Re: [PATCH v2] libtraceevent: Add __rel_loc relative location attribute support
Date: Mon, 29 Nov 2021 12:15:07 -0800	[thread overview]
Message-ID: <20211129201507.GA30603@kbox> (raw)
In-Reply-To: <163767457857.543504.6091850281066240970.stgit@devnote2>

On Tue, Nov 23, 2021 at 10:36:18PM +0900, Masami Hiramatsu wrote:
> Add '__rel_loc' new dynamic data location attribute which encodes
> the data location from the next to the field itself. This is similar
> to the '__data_loc' but the location offset is not from the event
> entry but from the next of the field.
> 
> This patch adds '__rel_loc' decoding support in the libtraceevent.
> 
> Signed-off-by: Masami Hiramatsu <mhiramat@kernel.org>
> ---
>  Changes in v2:
>    - Fix to adjust '*offset' instead of 'offset' in dynamic_offset_field()
> ---
>  src/event-parse.c  |   54 +++++++++++++++++++++++++++++++++-------------------
>  src/event-parse.h  |    5 +++--
>  src/parse-filter.c |    5 ++++-
>  3 files changed, 41 insertions(+), 23 deletions(-)
> 
> diff --git a/src/event-parse.c b/src/event-parse.c
> index 70637586bc9a..a88c73a8d0fb 100644
> --- a/src/event-parse.c
> +++ b/src/event-parse.c

[..]

> @@ -3308,19 +3318,23 @@ process_function(struct tep_event *event, struct tep_print_arg *arg,
>  		free_token(token);
>  		return process_int_array(event, arg, tok);
>  	}
> -	if (strcmp(token, "__get_str") == 0) {
> +	if (strcmp(token, "__get_str") == 0 ||
> +	    strcmp(token, "__get_rel_str") == 0) {

Should user_events use __get_rel_str vs __get_str for the print_fmt?
Both __dyn_loc and __rel_loc use __get_str currently.

Thanks,
-Beau

  parent reply	other threads:[~2021-11-29 20:19 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-22  9:36 [PATCH] libtraceevent: Add __rel_loc support Masami Hiramatsu
2021-11-22  9:36 ` [PATCH] libtraceevent: Add __rel_loc relative location attribute support Masami Hiramatsu
2021-11-23  3:39   ` Steven Rostedt
2021-11-23 12:05     ` Masami Hiramatsu
2021-11-23 14:49       ` Steven Rostedt
2021-11-23 13:36     ` [PATCH v2] " Masami Hiramatsu
2021-11-24 23:07       ` Steven Rostedt
2021-11-26 12:20         ` Masami Hiramatsu
2021-11-26 18:23           ` Steven Rostedt
2021-11-29 20:15       ` Beau Belgrave [this message]
2021-11-29 20:27         ` Steven Rostedt
2021-11-29 21:26           ` Beau Belgrave
2021-11-30  0:16             ` Masami Hiramatsu

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=20211129201507.GA30603@kbox \
    --to=beaub@linux.microsoft.com \
    --cc=linux-trace-devel@vger.kernel.org \
    --cc=mhiramat@kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=tz.stoyanov@gmail.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).