mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: kosaki.motohiro@jp.fujitsu.com,
	LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Peter Zijlstra <peterz@infradead.org>,
	Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
	"Luis Claudio R. Goncalves" <lclaudio@uudg.org>,
	Clark Williams <clark.williams@gmail.com>,
	Jon Masters <jonathan@jonmasters.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>,
	Christoph Hellwig <hch@infradead.org>,
	Xiao Guangrong <xiaoguangrong@cn.fujitsu.com>,
	Zhaolei <zhaolei@cn.fujitsu.com>, Li Zefan <lizf@cn.fujitsu.com>,
	Masami Hiramatsu <mhiramat@redhat.com>,
	"Frank Ch. Eigler" <fche@redhat.com>,
	Tom Zanussi <tzanussi@gmail.com>, Jason Baron <jbaron@redhat.com>,
	srostedt@redhat.com
Subject: Re: [ANNOUNCE][RFC] trace-cmd - command line reader for ftrace
Date: Mon, 20 Jul 2009 22:57:32 +0900 (JST)	[thread overview]
Message-ID: <20090720225637.AF63.A69D9226@jp.fujitsu.com> (raw)
In-Reply-To: <alpine.DEB.2.00.0907171009050.9337@gandalf.stny.rr.com>

> Again, this is very much in alpha form. It may still be very buggy, and 
> the format of the trace.dat file may soon change. Thus it is still in 
> [RFC] release status, and nothing is considered stable.
> 
> Here's some todo's I have planned.
> 
>  1) get it in a form to be used by perf (if possible)
>  2) add many more filters
>    a) More ways to filter on the report side
>    b) Add ways to filter on the recording side
>     This includes:
>       Using the /debug/tracing/event/*/filter files
>       Using the set_ftrace_filter/notrace files
>       Using the set_ftrace_pid
>       set_graph_function
>       enabling the backtrace functions
>       enabling the tracing/options
> 
> And I'm sure there are many more.
> 
> So, please feel free to download this code and play with it. If you find 
> bugs, please report. If you have other ideas that are not listed above, 
> share them.
> 
> Have fun!

Great! 
I'm very interesting this and I plan to start to evaluate this very 
good tool since next week.

Thanks for good effort.




      parent reply	other threads:[~2009-07-20 13:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-17 14:50 Steven Rostedt
2009-07-17 17:45 ` Noah Watkins
2009-07-17 23:33   ` Steven Rostedt
2009-07-17 19:43 ` Thomas Gleixner
2009-07-20 13:57 ` KOSAKI Motohiro [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=20090720225637.AF63.A69D9226@jp.fujitsu.com \
    --to=kosaki.motohiro@jp.fujitsu.com \
    --cc=acme@ghostprotocols.net \
    --cc=akpm@linux-foundation.org \
    --cc=clark.williams@gmail.com \
    --cc=fche@redhat.com \
    --cc=fweisbec@gmail.com \
    --cc=hch@infradead.org \
    --cc=jbaron@redhat.com \
    --cc=jonathan@jonmasters.org \
    --cc=lclaudio@uudg.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizf@cn.fujitsu.com \
    --cc=mathieu.desnoyers@polymtl.ca \
    --cc=mhiramat@redhat.com \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=srostedt@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=tzanussi@gmail.com \
    --cc=xiaoguangrong@cn.fujitsu.com \
    --cc=zhaolei@cn.fujitsu.com \
    /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

all inboxes | Powered by JetHome®