public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Figo.zhang" <zhangtianfei@leadcoretech.com>
To: Yong Zhang <yong.zhang0@gmail.com>
Cc: Li Zefan <lizf@cn.fujitsu.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Steven Rostedt <srostedt@redhat.com>
Subject: Re: Ftrace: can trace kthread?
Date: Thu, 21 Oct 2010 16:59:02 +0800	[thread overview]
Message-ID: <1287651542.2237.17.camel@myhost> (raw)
In-Reply-To: <AANLkTi=D_a_BH-HW9mqwLim+DjxARWzT8mxP_dah5iLY@mail.gmail.com>


> I just
> echo  0 > tracing_enabled
> echo function > current_tracer
> echo 374(pid of flush) > set_ftrace_pid
> echo 1 > tracing_enabled
> wait some time
> echo 0 > tracing_enabled
> cat trace
> 
> So I think this answer your question "could kthread be traced?"

i do it the same of you.

[root@myhost tracing]# ps -ax | grep flush
Warning: bad ps syntax, perhaps a bogus '-'? See http://procps.sf.net/faq.html
 1205 ?        S      0:01 [flush-8:0]
11852 pts/1    S+     0:00 grep flush
[root@myhost tracing]# 

so my flusher pid is 1205, i do it as below:

[root@myhost tracing]# echo 0 > tracing_enabled 
[root@myhost tracing]# echo function > current_tracer
[root@myhost tracing]# echo 1205 > set_ftrace_pid 
[root@myhost tracing]# echo 1 > tracing_enabled 

wait ... and open some pdf files, let system eat huge memory...

[root@myhost tracing]# echo 0 > tracing_enabled 
[root@myhost tracing]# cat trace
# tracer: function
#
#           TASK-PID    CPU#    TIMESTAMP  FUNCTION
#              | |       |          |         |


but i canot trace nothing. 



  reply	other threads:[~2010-10-21  9:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-21  7:55 Ftrace: can trace kthread? Figo.zhang
2010-10-21  8:10 ` Yong Zhang
2010-10-21  8:21   ` Figo.zhang
2010-10-21  8:39     ` Yong Zhang
2010-10-21  8:44       ` Figo.zhang
2010-10-21  8:54         ` Yong Zhang
2010-10-21  8:59           ` Figo.zhang [this message]
2010-10-21  9:08             ` Yong Zhang
2010-10-21  9:52               ` Figo.zhang
2010-10-21 10:08                 ` KOSAKI Motohiro
2010-10-21 10:12             ` Peter Zijlstra
2010-10-21 13:31               ` Steven Rostedt
2010-10-21 13:33 ` 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=1287651542.2237.17.camel@myhost \
    --to=zhangtianfei@leadcoretech.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizf@cn.fujitsu.com \
    --cc=srostedt@redhat.com \
    --cc=yong.zhang0@gmail.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