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:44:28 +0800 [thread overview]
Message-ID: <1287650668.2237.12.camel@myhost> (raw)
In-Reply-To: <AANLkTikzSZNtTGfOcP-87u+pMZyW8WrdxwV52ZV3f=nX@mail.gmail.com>
> > i try by set_ftrace_pid, it also can't ftrace the kswapd.
>
> Are you sure kswapd got chance to run on your system?
>
> BTW, I can successfully trace bdi_writeback_thread,
> # tracer: function
> #
> # TASK-PID CPU# TIMESTAMP FUNCTION
> # | | | | |
> flush-8:0-374 [000] 600743.828496: finish_task_switch <-schedule
> flush-8:0-374 [000] 600743.828498: perf_event_task_sched_in
> <-finish_task_switch
> flush-8:0-374 [000] 600743.828498: del_timer_sync <-schedule_timeout
> flush-8:0-374 [000] 600743.828499: try_to_del_timer_sync
> <-del_timer_sync
> flush-8:0-374 [000] 600743.828499: lock_timer_base
> <-try_to_del_timer_sync
> flush-8:0-374 [000] 600743.828499: _spin_lock_irqsave <-lock_timer_base
> flush-8:0-374 [000] 600743.828500: _spin_unlock_irqrestore
> <-try_to_del_timer_sync
> flush-8:0-374 [000] 600743.828500: kthread_should_stop
> <-bdi_writeback_task
are you use my scprit to trace the bdi_writeback_thread ?
next prev parent reply other threads:[~2010-10-21 8:48 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 [this message]
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=1287650668.2237.12.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 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.