From: Mathieu Desnoyers <compudj@krystal.dyndns.org>
To: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Jason Baron <jbaron@redhat.com>,
linux-kernel@vger.kernel.org, fche@redhat.com,
fweisbec@gmail.com, edwintorok@gmail.com, mingo@elte.hu,
Steven Rostedt <rostedt@goodmis.org>,
mbligh@google.com, ltt-dev@lists.casi.polymtl.ca
Subject: Re: tracepoints for kernel/mutex.c
Date: Fri, 17 Oct 2008 12:36:30 -0400 [thread overview]
Message-ID: <20081017163630.GE5696@Krystal> (raw)
In-Reply-To: <20081017140841.FAA3.KOSAKI.MOTOHIRO@jp.fujitsu.com>
* KOSAKI Motohiro (kosaki.motohiro@jp.fujitsu.com) wrote:
> Hi
>
> > Folks, lets please start by getting the tracing infrastructure in and
> > those few high-level trace-points google proposed.
> >
> > Until we get the basics in, I think I'm going to NAK any and all
> > tracepoint/marker patches.
>
> Could you please tell me how to get these patches?
> I'd like to review it.
>
Hi Kosaki,
I am focusing on the timestamping/data relay/tracing control
infrastructure for now, so I think it is too soon to post the
instrumentation patches selelected from LTTng which correspond to the
Google instrumentation before we get something that makes that data
useful within the kernel, but if you still want to have a look, comments
are welcome.
See
git://git.kernel.org/pub/scm/linux/kernel/git/compudj/linux-2.6-lttng.git
or
http://www.kernel.org/pub/linux/kernel/people/compudj/patches/2.6/2.6.27/patch-2.6.27-lttng-0.43.tar.bz2
Commits :
irq-handle-prepare-for-instrumentation.patch
lttng-instrumentation-irq.patch
lttng-instrumentation-scheduler.patch
lttng-instrumentation-timer.patch
lttng-instrumentation-kernel.patch
lttng-instrumentation-filemap.patch
lttng-instrumentation-swap.patch
lttng-instrumentation-socket.patch
Mathieu
--
Mathieu Desnoyers
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F BA06 3F25 A8FE 3BAE 9A68
next prev parent reply other threads:[~2008-10-17 16:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-16 21:04 tracepoints for kernel/mutex.c Jason Baron
2008-10-16 21:34 ` Peter Zijlstra
2008-10-16 22:14 ` Thomas Gleixner
2008-10-17 5:09 ` KOSAKI Motohiro
2008-10-17 8:15 ` Peter Zijlstra
2008-10-17 8:22 ` KOSAKI Motohiro
2008-10-17 16:36 ` Mathieu Desnoyers [this message]
2008-10-17 14:48 ` Jason Baron
2008-10-17 16:43 ` Mathieu Desnoyers
2008-10-17 16:58 ` Frank Ch. Eigler
2008-10-17 16:48 ` Peter Zijlstra
2008-10-17 16:54 ` Mathieu Desnoyers
2008-10-16 22:10 ` Mathieu Desnoyers
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=20081017163630.GE5696@Krystal \
--to=compudj@krystal.dyndns.org \
--cc=edwintorok@gmail.com \
--cc=fche@redhat.com \
--cc=fweisbec@gmail.com \
--cc=jbaron@redhat.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ltt-dev@lists.casi.polymtl.ca \
--cc=mbligh@google.com \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--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