From: Steven Rostedt <srostedt@redhat.com>
To: "Figo.zhang" <zhangtianfei@leadcoretech.com>
Cc: Li Zefan <lizf@cn.fujitsu.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Ftrace: can trace kthread?
Date: Thu, 21 Oct 2010 09:33:43 -0400 [thread overview]
Message-ID: <1287668023.2824.15.camel@fedora> (raw)
In-Reply-To: <1287647732.2237.7.camel@myhost>
Just a quick note. Please send email to my rostedt@goodmis.org address.
I do not check my srostedt@redhat.com address as often.
I know, I know, I have it as my Author tag (but not my signed off by)
and I had to add it to my business card. I just could not be so bold as
to put my goodmis.org address on my Red Hat business card ;-) And there
was no good way to add it as a secondary.
-- Steve
On Thu, 2010-10-21 at 15:55 +0800, Figo.zhang wrote:
> 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
>
>
>
prev parent reply other threads:[~2010-10-21 13:33 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
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 [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=1287668023.2824.15.camel@fedora \
--to=srostedt@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=zhangtianfei@leadcoretech.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.