From: Zhaolei <zhaolei@cn.fujitsu.com>
To: Steven Rostedt <rostedt@goodmis.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Tom Zanussi <tzanussi@gmail.com>, Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] tracepoint: Make kmem tracepoint use TRACE_EVENT macro
Date: Fri, 10 Apr 2009 14:37:52 +0800 [thread overview]
Message-ID: <49DEE940.9070209@cn.fujitsu.com> (raw)
In-Reply-To: <49DEE6DA.80600@cn.fujitsu.com>
Zhaolei wrote:
> TRACE_EVENT is more unify and generic for define a tracepoint.
> It also add ftrace support for this tracepoint.
>
> Signed-off-by: Zhao Lei <zhaolei@cn.fujitsu.com>
> ---
> include/trace/kmem.h | 39 +-------
> include/trace/kmem_event_types.h | 193 +++++++++++++++++++++++++++++++++++++
> include/trace/trace_event_types.h | 1 +
> include/trace/trace_events.h | 1 +
> 4 files changed, 197 insertions(+), 37 deletions(-)
> create mode 100644 include/trace/kmem_event_types.h
Sorry for notice that this patch must apply on top of skb's TRACE_EVENT patch:
[PATCH] Tracepoint: Make skb tracepoint use TRACE_EVENT macro
Because both patch need to add a line into include/trace/trace_event_types.h
and include/trace/trace_events.h.
Thanks
Zhaolei
next prev parent reply other threads:[~2009-04-10 6:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-10 6:26 [PATCH 1/2] ftrace: Separate include/trace/kmemtrace.h to kmemtrace part and tracepoint part Zhaolei
2009-04-10 6:27 ` [PATCH 2/2] tracepoint: Make kmem tracepoint use TRACE_EVENT macro Zhaolei
2009-04-10 6:37 ` Zhaolei [this message]
2009-04-10 13:29 ` Frederic Weisbecker
2009-04-13 22:22 ` [tip:tracing/core] tracing, kmemtrace: Make kmem tracepoints " tip-bot for Zhaolei
2009-04-10 11:03 ` [PATCH 1/2] ftrace: Separate include/trace/kmemtrace.h to kmemtrace part and tracepoint part Ingo Molnar
2009-04-10 15:21 ` Eduard - Gabriel Munteanu
2009-04-12 10:25 ` Ingo Molnar
2009-04-13 22:21 ` [tip:tracing/core] tracing, kmemtrace: " tip-bot for Zhaolei
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=49DEE940.9070209@cn.fujitsu.com \
--to=zhaolei@cn.fujitsu.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
--cc=tzanussi@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