From: Eduard - Gabriel Munteanu <eduard.munteanu@linux360.ro>
To: Ingo Molnar <mingo@elte.hu>
Cc: Zhaolei <zhaolei@cn.fujitsu.com>,
Pekka Enberg <penberg@cs.helsinki.fi>,
Steven Rostedt <rostedt@goodmis.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Tom Zanussi <tzanussi@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] ftrace: Separate include/trace/kmemtrace.h to kmemtrace part and tracepoint part
Date: Fri, 10 Apr 2009 18:21:22 +0300 [thread overview]
Message-ID: <20090410152121.GA5505@localhost> (raw)
In-Reply-To: <20090410110303.GB21506@elte.hu>
On Fri, Apr 10, 2009 at 01:03:03PM +0200, Ingo Molnar wrote:
>
> * Zhaolei <zhaolei@cn.fujitsu.com> wrote:
>
> > Current kmemtrace.h is used both as header file of kmemtrace and kmem's
> > tracepoints definition.
> > Tracepoints' definition file may be used by other code, and should only have
> > definition of tracepoint.
> >
> > We can separate include/trace/kmemtrace.h into 2 files:
> > include/linux/kmemtrace.h: header file for kmemtrace
> > include/trace/kmem.h: definition of kmem tracepoints
> >
> > Signed-off-by: Zhao Lei <zhaolei@cn.fujitsu.com>
> > ---
> > include/linux/kmemtrace.h | 25 +++++++++++++++++++++++++
> > include/linux/slab_def.h | 2 +-
> > include/linux/slub_def.h | 2 +-
> > include/trace/{kmemtrace.h => kmem.h} | 25 +++----------------------
> > init/main.c | 2 +-
> > kernel/trace/kmemtrace.c | 2 +-
> > kernel/trace/trace.h | 2 +-
> > mm/slab.c | 2 +-
> > mm/slob.c | 2 +-
> > mm/slub.c | 2 +-
> > 10 files changed, 36 insertions(+), 30 deletions(-)
> > create mode 100644 include/linux/kmemtrace.h
> > rename include/trace/{kmemtrace.h => kmem.h} (78%)
>
> Pekka, Eduard, do you agree with these two patches? Converting those
> tracepoints to TRACE_EVENT() is really nice. The above include file
> restructuring makes sense too - it separates tracepoint definition
> from the plugin init method.
>
> Ingo
Yes, these two patches look great. The first one makes the kmem
tracepoints usable by other things (e.g. kmemcheck) in a
kmemtrace-independent fashion, which is nice. Thanks, Zhao.
One thing I don't actually get is why have kmem_event_types.h separate
from kmem.h, but it's not really an issue, I see other tracers doing the
same thing. Other than that, it looks fine although I didn't test. Here's
the ack if you need it:
Acked-by: Eduard - Gabriel Munteanu <eduard.munteanu@linux360.ro>
Pekka?
Eduard
next prev parent reply other threads:[~2009-04-10 15:21 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
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 [this message]
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=20090410152121.GA5505@localhost \
--to=eduard.munteanu@linux360.ro \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=penberg@cs.helsinki.fi \
--cc=rostedt@goodmis.org \
--cc=tzanussi@gmail.com \
--cc=zhaolei@cn.fujitsu.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