From: fche@redhat.com (Frank Ch. Eigler)
To: Arjan van de Ven <arjan@infradead.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org, mingo@elte.hu, alan@redhat.com,
jbaron@redhat.com
Subject: Re: [PATCH] ftrace: add an fsync tracer
Date: Thu, 06 Nov 2008 15:19:48 -0500 [thread overview]
Message-ID: <y0mej1ofvyz.fsf@ton.toronto.redhat.com> (raw)
In-Reply-To: <20081106094558.50d94bcc@infradead.org> (Arjan van de Ven's message of "Thu, 6 Nov 2008 09:45:58 -0800")
Arjan van de Ven <arjan@infradead.org> writes:
> [...]
> what is the real need is
> 1) Have a trace point in the source
> 2) Associate a "formatting function" with that point
> (which basically transforms the trace parameters to, say, a string)
> 3) A way to turn the trace point on/off.
For 1 and 2, it may be worth considering a plain trace_mark() in
do_sync(). The complication that makes this uglier than a one-liner
is d_path()'s buffer and error handling.
{
char *buffer = kzalloc (4096, GFP_KERNEL);
trace_mark(fsync, "Process %s is calling fsync on %s\n",
current->comm,
({char *err = d_path (...);
IS_ERR(err) ? "?" : err;}));
kfree (buffer);
}
With a bit of extension on the marker front, the allocation could be
made conditional on the marker being enabled.
For 3, the kernel could merge a backend that connects arbitrary
markers to an ftrace (or whatever) buffer. Several compact prototypes
for the latter exist.
- FChE
next prev parent reply other threads:[~2008-11-06 20:20 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-05 17:49 [PATCH] ftrace: add an fsync tracer Arjan van de Ven
2008-11-05 19:43 ` Marcin Slusarz
2008-11-05 20:36 ` Arjan van de Ven
2008-11-06 7:20 ` Ingo Molnar
2008-11-06 12:55 ` Peter Zijlstra
2008-11-06 13:28 ` Frédéric Weisbecker
2008-11-06 14:06 ` Arjan van de Ven
2008-11-06 14:19 ` Peter Zijlstra
2008-11-06 14:31 ` Arjan van de Ven
2008-11-06 14:50 ` Peter Zijlstra
2008-11-06 15:01 ` Arjan van de Ven
2008-11-06 15:34 ` Steven Rostedt
2008-11-06 17:45 ` Arjan van de Ven
2008-11-06 20:19 ` Frank Ch. Eigler [this message]
2008-11-06 20:29 ` Peter Zijlstra
2008-11-06 20:57 ` Frank Ch. Eigler
2008-11-06 21:18 ` Jason Baron
2008-11-06 21:53 ` Mathieu Desnoyers
2008-11-06 22:14 ` Frank Ch. Eigler
2008-11-06 22:25 ` Mathieu Desnoyers
2008-11-06 23:25 ` Frank Ch. Eigler
2008-11-07 4:25 ` Arjan van de Ven
2008-11-07 5:12 ` Mathieu Desnoyers
2008-11-06 21:13 ` Arjan van de Ven
2008-11-06 21:20 ` Frank Ch. Eigler
2008-11-06 14:14 ` Arjan van de Ven
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=y0mej1ofvyz.fsf@ton.toronto.redhat.com \
--to=fche@redhat.com \
--cc=alan@redhat.com \
--cc=arjan@infradead.org \
--cc=jbaron@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--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