From: Steven Rostedt <rostedt@goodmis.org>
To: Masami Hiramatsu <mhiramat@kernel.org>
Cc: Beau Belgrave <beaub@linux.microsoft.com>,
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: Wed, 24 Nov 2021 18:07:08 -0500 [thread overview]
Message-ID: <20211124180708.599aa110@gandalf.local.home> (raw)
In-Reply-To: <163767457857.543504.6091850281066240970.stgit@devnote2>
On Tue, 23 Nov 2021 22:36:18 +0900
Masami Hiramatsu <mhiramat@kernel.org> wrote:
> +++ b/src/event-parse.h
> @@ -125,6 +125,7 @@ enum tep_format_flags {
> TEP_FIELD_IS_LONG = 32,
> TEP_FIELD_IS_FLAG = 64,
> TEP_FIELD_IS_SYMBOLIC = 128,
> + TEP_FIELD_IS_RELATIVE = 256,
> };
>
> struct tep_format_field {
> @@ -153,12 +154,12 @@ struct tep_print_arg_atom {
>
> struct tep_print_arg_string {
> char *string;
> - int offset;
> + struct tep_format_field *field;
> };
>
> struct tep_print_arg_bitmask {
> char *bitmask;
> - int offset;
> + struct tep_format_field *field;
> };
>
We need to be careful about modifying content in event-parse.h. Because
this is exposed outside he library.
Although, I don't think this should be an issue.
We probably need to move some content out of that file if it isn't used in
any of the exposed APIs :-/
And since both libtracefs and trace-cmd do not reference any of the
tep_print_arg* fields, we probably should remove them before somebody does.
-- Steve
next prev parent reply other threads:[~2021-11-24 23:07 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 [this message]
2021-11-26 12:20 ` Masami Hiramatsu
2021-11-26 18:23 ` Steven Rostedt
2021-11-29 20:15 ` Beau Belgrave
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=20211124180708.599aa110@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=beaub@linux.microsoft.com \
--cc=linux-trace-devel@vger.kernel.org \
--cc=mhiramat@kernel.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).