public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Li Zefan <lizf@cn.fujitsu.com>
To: paulmck@linux.vnet.ibm.com
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
	Ingo Molnar <mingo@elte.hu>, LKML <linux-kernel@vger.kernel.org>,
	Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [PATCH] rcu: convert rcupreempt trace to seq file
Date: Mon, 12 Jan 2009 09:09:02 +0800	[thread overview]
Message-ID: <496A982E.3020103@cn.fujitsu.com> (raw)
In-Reply-To: <20090111051604.GF7061@linux.vnet.ibm.com>

>> The debugfs and seqfile handling and handled in the statistical
>> tracing engine.
>>
>> You just have to provide an iterator for your stat entries through two callbacks:
>>
>> _ stat_start() -> gives the first entry
>> _ stat_next() -> iterates over the next entry
>>
>> And an output callback
>>
>> _ stat_show() -> print one entry from your stat list
>>
>> And two optional things:
>>
>> _ stat_cmp() -> compare two entries, useful if you want your stats to be sorted
>> _ stat_headers() -> provide the first line in your stat file, typically to describe your columns
>>
>> The last thing you need is to give a name to your trace file.
>> You will retrieve it into /debugfs/tracing/trace_stat/your_file_name as a current snapshot
>> of your stats.
>>
>> It is currently used by the branch tracer, and by a pending patch for a new workqueue
>> tracer which will provide you a simple example.
>>
>> If you have any question about how to use it, don't hesitate to ask.
> 
> Li Zefan, is this something you would be willing to try?  Sounds like
> it might be a good addition.
> 

Sure, I'll try. :)


  reply	other threads:[~2009-01-12  1:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-10  7:48 [PATCH] rcu: convert rcupreempt trace to seq file Li Zefan
2009-01-10 22:31 ` Paul E. McKenney
2009-01-11  1:39   ` Ingo Molnar
2009-01-11  5:01     ` Frederic Weisbecker
2009-01-11  5:16       ` Paul E. McKenney
2009-01-12  1:09         ` Li Zefan [this message]
2009-01-12  1:59           ` Paul E. McKenney
2009-01-13  3:19       ` Li Zefan
2009-01-13  8:49         ` Frederic Weisbecker
2009-01-13  9:03           ` Li Zefan
2009-01-13  9:17             ` Frederic Weisbecker
2009-01-13 13:08             ` Steven Rostedt

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=496A982E.3020103@cn.fujitsu.com \
    --to=lizf@cn.fujitsu.com \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=paulmck@linux.vnet.ibm.com \
    --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