public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Figo.zhang" <zhangtianfei@leadcoretech.com>
To: Li Zefan <lizf@cn.fujitsu.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Steven Rostedt <srostedt@redhat.com>
Subject: Ftrace: can trace kthread?
Date: Thu, 21 Oct 2010 15:55:32 +0800	[thread overview]
Message-ID: <1287647732.2237.7.camel@myhost> (raw)

hi,

is it ftrace in 2.6.36-rc8 can trace the kthread? i want to trace the
kswapd/bdi_writeback_thread, but not success. i am sure that kswapd is
running, because i let the system eat huge memory. i can trace some
function such as __do_fault. what is issue on it? 

Best,
Figo.zhang


here is my ftrace script.
i = 1
while true;
do
	echo 1 > /proc/sys/kernel/ftrace_enabled
	echo function_graph > /sys/kernel/debug/tracing/current_tracer
	echo kswapd > /sys/kernel/debug/tracing/set_graph_function
	echo 1 > /sys/kernel/debug/tracing/tracing_on
	echo 1 > /sys/kernel/debug/tracing/tracing_enabled
	sleep 1
	echo 0 > /sys/kernel/debug/tracing/tracing_enabled
	cat /sys/kernel/debug/tracing/trace > ftrace.kswap.log.$i

	let i=i+1;

done




             reply	other threads:[~2010-10-21  7:59 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-21  7:55 Figo.zhang [this message]
2010-10-21  8:10 ` Ftrace: can trace kthread? 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
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=1287647732.2237.7.camel@myhost \
    --to=zhangtianfei@leadcoretech.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizf@cn.fujitsu.com \
    --cc=srostedt@redhat.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