From: Theodore Tso <tytso@mit.edu>
To: Mathieu Desnoyers <compudj@krystal.dyndns.org>
Cc: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
ltt-dev@lists.casi.polymtl.ca,
Ext4 Developers List <linux-ext4@vger.kernel.org>
Subject: Re: [ltt-dev] Fw: [PATCH] ext4: Add markers for better debuggability
Date: Fri, 9 Jan 2009 13:58:40 -0500 [thread overview]
Message-ID: <20090109185840.GD23869@mit.edu> (raw)
In-Reply-To: <20090109144901.GA7262@Krystal>
On Fri, Jan 09, 2009 at 09:49:01AM -0500, Mathieu Desnoyers wrote:
>
> Given this is meant to be in the mainline kernel, using tracepoints
> rather than markers would be more appropriate. Please see
> Documentation/tracepoints.txt and samples/tracepoints/ for details.
I saw that, but I'm still not sure how I would actually *use*
tracepoints. I can use markers today with Systemtap, and I need an
easy way to be able to selectively do things like "trap and print all
of the logged data when the ext4_request_inode tracepoint/marker is
tripped where dev=='dm-8'".
Unfortunately, Systemtap seems doomed given its current course and
direction, so I'm not opposed to moving to another solution --- I just
need a HOWTO that demonstrates how I can do this painlessly and
easily; preferably without having me have to manually hack up a kernel
module each time I want to implement the tracing
Is there an easy way to do that using ltt today? Can you point me at
a sample of how this could be done?
- Ted
next prev parent reply other threads:[~2009-01-09 18:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090109170408.75C1.KOSAKI.MOTOHIRO@jp.fujitsu.com>
2009-01-09 14:49 ` [ltt-dev] Fw: [PATCH] ext4: Add markers for better debuggability Mathieu Desnoyers
2009-01-09 18:58 ` Theodore Tso [this message]
2009-01-10 16:19 ` Mathieu Desnoyers
2009-01-10 18:42 ` Theodore Tso
2009-01-10 20:40 ` Steven Rostedt
2009-01-10 21:50 ` Theodore Tso
2009-01-12 1:34 ` Mathieu Desnoyers
2009-01-10 18:19 ` LTTng for ext4 tracing HOWTO 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=20090109185840.GD23869@mit.edu \
--to=tytso@mit.edu \
--cc=compudj@krystal.dyndns.org \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-ext4@vger.kernel.org \
--cc=ltt-dev@lists.casi.polymtl.ca \
/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;
as well as URLs for NNTP newsgroup(s).