From: Frederic Weisbecker <fweisbec@gmail.com>
To: Li Zefan <lizf@cn.fujitsu.com>
Cc: Ingo Molnar <mingo@elte.hu>, Steven Rostedt <rostedt@goodmis.org>,
Johannes Berg <johannes@sipsolutions.net>,
LKML <linux-kernel@vger.kernel.org>,
Lai Jiangshan <laijs@cn.fujitsu.com>
Subject: Re: [PATCH 1/2] tracing/events: add missing type info of dynamic arrays
Date: Fri, 17 Jul 2009 00:44:19 -0400 [thread overview]
Message-ID: <20090717044418.GD4977@nowhere> (raw)
In-Reply-To: <4A5E962E.9020900@cn.fujitsu.com>
On Thu, Jul 16, 2009 at 10:53:34AM +0800, Li Zefan wrote:
> From: Lai Jiangshan <laijs@cn.fujitsu.com>
>
> The format file doesn't contain enough information for
> __dynamic_array/__string. The type name is missing.
>
> Before:
> # cat format:
> name: irq_handler_entry
> ...
> field:__data_loc name; offset:16; size:2;
>
> After:
> # cat format:
> name: irq_handler_entry
> ...
> field:__data_loc char[] name; offset:16; size:2;
>
> Signed-off-by: Lai Jiangshan <laijs@cn.fujitsu.com>
> Signed-off-by: Li Zefan <lizf@cn.fujitsu.com>
Looks good to me, but I'd prefer to wait for Steve Ack, since he wasn't
sure...
Thanks.
> ---
> include/trace/ftrace.h | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/include/trace/ftrace.h b/include/trace/ftrace.h
> index 1867553..cc78943 100644
> --- a/include/trace/ftrace.h
> +++ b/include/trace/ftrace.h
> @@ -120,7 +120,7 @@
>
> #undef __dynamic_array
> #define __dynamic_array(type, item, len) \
> - ret = trace_seq_printf(s, "\tfield:__data_loc " #item ";\t" \
> + ret = trace_seq_printf(s, "\tfield:__data_loc " #type "[] " #item ";\t"\
> "offset:%u;\tsize:%u;\n", \
> (unsigned int)offsetof(typeof(field), \
> __data_loc_##item), \
> @@ -279,7 +279,7 @@ ftrace_raw_output_##call(struct trace_iterator *iter, int flags) \
>
> #undef __dynamic_array
> #define __dynamic_array(type, item, len) \
> - ret = trace_define_field(event_call, "__data_loc" "[" #type "]", #item,\
> + ret = trace_define_field(event_call, "__data_loc " #type "[]", #item, \
> offsetof(typeof(field), __data_loc_##item), \
> sizeof(field.__data_loc_##item), 0);
>
> -- 1.6.3
next prev parent reply other threads:[~2009-07-17 4:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-16 2:52 [PATCH 0/2] tracing/events: 2 fixes for dynamic arrays Li Zefan
2009-07-16 2:53 ` [PATCH 1/2] tracing/events: add missing type info of " Li Zefan
2009-07-17 4:44 ` Frederic Weisbecker [this message]
2009-08-05 8:19 ` [tip:tracing/core] " tip-bot for Lai Jiangshan
2009-07-16 2:54 ` [PATCH 2/2] tracing/events: record the size " Li Zefan
2009-07-17 5:14 ` Frederic Weisbecker
2009-08-05 8:19 ` [tip:tracing/core] " tip-bot for Li Zefan
2009-07-20 1:18 ` [PATCH 0/2] tracing/events: 2 fixes for " Li Zefan
2009-07-20 15:38 ` Steven Rostedt
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=20090717044418.GD4977@nowhere \
--to=fweisbec@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.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