From: Ingo Molnar <mingo@elte.hu>
To: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: linux-kernel@vger.kernel.org,
Steven Rostedt <rostedt@goodmis.org>,
Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
Subject: Re: [patch] ftrace, v15
Date: Sun, 27 Apr 2008 15:15:16 +0200 [thread overview]
Message-ID: <20080427131516.GA8850@elte.hu> (raw)
In-Reply-To: <2f11576a0804270414t3ef16998me2ff2afd21eedbe7@mail.gmail.com>
* KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com> wrote:
> Hi Ingo,
>
> > the current/latest ftrace tree can be pulled from:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/mingo/linux-2.6-sched-devel.git
> >
> > the full diffs are too large to be included here, but the shortlog and
> > the diffstat is below. Not much changed in the fundamentals since the
> > last lkml posting - but many small details were refined.
>
> I hope ftrace people discussio LTTng people more. AFAIK nobody explain
> pros. and cons. ftrace against marker approach. (of cource, LTTng
> people doen't explain it too)
check the tree :-) It has these commits too:
Markers use imv jump
Linux Kernel Markers - Use Immediate Values
Markers - define non optimized marker
Markers - remove extra format argument
LTTng instrumentation net
LTTng instrumentation mm
LTTng instrumentation kernel
LTTng instrumentation ipc
LTTng instrumentation fs
[ the latter ones are only there for testing - Mathieu is working on a
different approach for syscall instrumentation. ]
Enjoy,
Ingo
prev parent reply other threads:[~2008-04-27 13:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-27 6:30 [patch] ftrace, v15 Ingo Molnar
2008-04-27 6:32 ` David Miller
2008-04-27 7:16 ` Ingo Molnar
2008-04-27 7:22 ` David Miller
2008-04-27 11:14 ` KOSAKI Motohiro
2008-04-27 13:15 ` Ingo Molnar [this message]
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=20080427131516.GA8850@elte.hu \
--to=mingo@elte.hu \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@polymtl.ca \
--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