The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@infradead.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
	linux-kernel@vger.kernel.org, mingo@elte.hu, alan@redhat.com
Subject: Re: [PATCH] ftrace: add an fsync tracer
Date: Thu, 6 Nov 2008 09:45:58 -0800	[thread overview]
Message-ID: <20081106094558.50d94bcc@infradead.org> (raw)
In-Reply-To: <alpine.DEB.1.10.0811061020311.31011@gandalf.stny.rr.com>

On Thu, 6 Nov 2008 10:34:50 -0500 (EST)
Steven Rostedt <rostedt@goodmis.org> wrote:
> 
> What I would like is a single "event tracer" that does all of this.
> But add the ability to start and stop different events. We could start
> with this tracer, and then add more events to this tracer. Have a
> separate file to show which events are available.
> 
> This will keep the 'available_tracers' file small, but it would be
> fine if the 'events' file grew large.

well 2 ounces versus one liter ;)


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.

right now this is what the fsync tracer does, because it's the only way
to do such a thing.
I don't care how to otherwise do it ....


-- 
Arjan van de Ven 	Intel Open Source Technology Centre
For development, discussion and tips for power savings, 
visit http://www.lesswatts.org

  reply	other threads:[~2008-11-06 17:45 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 [this message]
2008-11-06 20:19                 ` Frank Ch. Eigler
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=20081106094558.50d94bcc@infradead.org \
    --to=arjan@infradead.org \
    --cc=alan@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