[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AANLkTikzSZNtTGfOcP-87u+pMZyW8WrdxwV52ZV3f=nX@mail.gmail.com>
Date: Thu, 21 Oct 2010 16:39:12 +0800
From: Yong Zhang <yong.zhang0@...il.com>
To: "Figo.zhang" <zhangtianfei@...dcoretech.com>
Cc: Li Zefan <lizf@...fujitsu.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Steven Rostedt <srostedt@...hat.com>
Subject: Re: Ftrace: can trace kthread?
On Thu, Oct 21, 2010 at 4:21 PM, Figo.zhang
<zhangtianfei@...dcoretech.com> wrote:
> On Thu, 2010-10-21 at 16:10 +0800, Yong Zhang wrote:
>> On Thu, Oct 21, 2010 at 3:55 PM, Figo.zhang
>> <zhangtianfei@...dcoretech.com> wrote:
>> > hi,
>> >
>> > is it ftrace in 2.6.36-rc8 can trace the kthread?
>>
>> How about the set_ftrace_pid interface?
>>
>
> 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
Thanks,
Yong
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists