From: fche@redhat.com (Frank Ch. Eigler)
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: Arnaldo Carvalho de Melo <acme@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: Perf can't deal with many tracepoints
Date: Thu, 28 Oct 2010 13:42:36 -0400 [thread overview]
Message-ID: <y0mtyk6i583.fsf@fche.csb> (raw)
In-Reply-To: <E1PBFIJ-0004eC-Tj@tytso-glaptop> (Theodore Ts'o's message of "Wed, 27 Oct 2010 19:20:35 -0400")
"Theodore Ts'o" <tytso@mit.edu> writes:
> Perf will drop dead if it comes across tracepoints that have anything
> but primitive structure accessors in the TP_printk() section of the
> tracepoint definition. For example, the ext4 and jbd2 tracepoints uses
> jbd2_dev_to_name() to translate a dev_t to a string.
In the mean time, you may enjoy:
# stap -L 'kernel.trace("*")'
# stap -g -e '
%{
#include<linux/jbd2.h>
%}
function jbd2name(dev) %{
strlcpy(THIS->__retvalue, jbd2_dev_to_name(THIS->dev), MAXSTRINGLEN);
%}
probe kernel.trace("ext4_free_inode") {
log(jbd2name($inode->i_sb->s_dev))
}'
> The block I/O tracepoints uses MAJOR() and MINOR() to translate a
> dev_t to a major/minor number pair. [...]
(Similarly for this case.)
- FChE
prev parent reply other threads:[~2010-10-28 17:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-27 23:20 Perf can't deal with many tracepoints Theodore Ts'o
2010-10-28 0:16 ` David Daney
2010-10-28 0:40 ` Ted Ts'o
2010-10-28 0:45 ` David Daney
2010-10-28 17:42 ` Frank Ch. Eigler [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=y0mtyk6i583.fsf@fche.csb \
--to=fche@redhat.com \
--cc=acme@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.