From: Jiri Olsa <jolsa@redhat.com>
To: Wang Nan <wangnan0@huawei.com>
Cc: jeremie.galarneau@efficios.com, bigeasy@linutronix.de,
lizefan@huawei.com, linux-kernel@vger.kernel.org,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [PATCH 1/2] perf: convert: fix duplicate field names and avoid reserved keywords.
Date: Wed, 21 Jan 2015 15:19:38 +0100 [thread overview]
Message-ID: <20150121141938.GB6835@krava.brq.redhat.com> (raw)
In-Reply-To: <54BF8A97.6050402@huawei.com>
On Wed, Jan 21, 2015 at 07:16:39PM +0800, Wang Nan wrote:
> Hi Jiri,
>
> I found that only this patch is not enough. When converting such tracepoints,
> it uses add_tracepoint_fields_values(..., struct format_field *fields ...),
> and fields->name is still the original one.
>
> If 'struct format_field' has a field like 'dup_name' we can make things simpler.
> However, struct format_field is part of traceevent, not only used by perf.
>
> I have no enough time to think on it. Jiri, could you please give me some hints
> so I can implement another patch tomorrow?
yea, looks like we either need to add 'void *priv' into 'struct format_field'
or if Steven doesn't like it, we'd need to save 'our' field name in some way
so it's reachable via format_field::name string.
Steven,
we need to use changed format_field::name to interface babeltrace
library, because it has restriction that fields within tracepoint
should have unique names.
Any chance we could introduce 'void *priv' member to format_field::name ?
Maybe with 'destroy_priv' callback to be called when the field is destroyed.
I can provide patch, just wanted to know first if you're not strictly against ;-)
thanks,
jirka
next prev parent reply other threads:[~2015-01-21 14:20 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-20 11:07 [PATCH 0/2] perf: convert: two patches for converting syscall tracepoitns Wang Nan
2015-01-20 11:07 ` [PATCH 1/2] perf: convert: fix duplicate field names Wang Nan
2015-01-20 13:06 ` Jiri Olsa
2015-01-21 3:23 ` [PATCH 1/2] perf: convert: fix duplicate field names and avoid reserved keywords Wang Nan
2015-01-21 11:16 ` Wang Nan
2015-01-21 14:19 ` Jiri Olsa [this message]
2015-01-21 14:25 ` Steven Rostedt
2015-01-21 14:32 ` Jiri Olsa
2015-01-22 5:35 ` [PATCH RFC 0/2] tools lib traceevent: introduces priv field to struct format_field Wang Nan
2015-01-22 5:36 ` [PATCH RFC 1/2] tools lib traceevent: add priv field to truct format_field Wang Nan
2015-01-22 5:36 ` [PATCH RFC 2/2] perf: convert: fix duplicate field names and avoid reserved keywords Wang Nan
2015-01-22 13:27 ` Jiri Olsa
2015-01-23 1:57 ` Wang Nan
2015-01-23 2:53 ` Wang Nan
2015-01-23 8:44 ` Jiri Olsa
2015-01-23 8:45 ` Jiri Olsa
2015-01-23 22:40 ` Jérémie Galarneau
2015-01-24 16:39 ` Jiri Olsa
2015-01-26 11:11 ` Wang Nan
2015-01-21 14:11 ` [PATCH 1/2] " Jiri Olsa
2015-01-21 15:56 ` Jérémie Galarneau
2015-01-22 1:38 ` Wang Nan
2015-01-22 3:14 ` Jérémie Galarneau
2015-01-22 3:21 ` Wang Nan
2015-01-23 20:45 ` Mathieu Desnoyers
2015-01-20 11:07 ` [PATCH 2/2] perf: convert: fix signess of value Wang Nan
2015-01-20 13:06 ` [PATCH 0/2] perf: convert: two patches for converting syscall tracepoitns 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=20150121141938.GB6835@krava.brq.redhat.com \
--to=jolsa@redhat.com \
--cc=bigeasy@linutronix.de \
--cc=jeremie.galarneau@efficios.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=rostedt@goodmis.org \
--cc=wangnan0@huawei.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
all inboxes | Powered by JetHome®