[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <4C983551.5060700@hitachi.com>
Date: Tue, 21 Sep 2010 13:32:17 +0900
From: Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>
To: Luming Yu <luming.yu@...il.com>
Cc: LKML <linux-kernel@...r.kernel.org>,
2nddept-manager@....hitachi.co.jp
Subject: Re: Is it supported to perf probe data?
(2010/09/21 10:19), Luming Yu wrote:
> On Tue, Sep 21, 2010 at 7:54 AM, Masami Hiramatsu
> <masami.hiramatsu.pt@...achi.com> wrote:
>> Hi Luming,
>>
>> (2010/09/20 17:03), Luming Yu wrote:
>>> Hi there,
>>>
>>> I need to analyze accessing pattern to a data in kernel. Wanna to
>>> check with you if perf probe can help to get that trace.
>>
>> Yes, perf probe can add new trace events which can be used
>> from perf record/report/trace or ftrace as same as other pre-defined
>> trace events. Those new events can record variables as arguments too.
>> So you can define new events with accessed data, record it by perf record,
>> and see it by perf trace.
>
> e.g. I need to trace accessing to thread_info.flags of a specific task,
> would you please show me an example how to do it.
OK, if your tracing function 'func' has a local pointer 'thread_info' which points
to the thread_info structure, you can do;
# perf probe --add 'func thread_info->flags'
to trace flags.
But if you are willing to trace (struct *thread_info)(current->stack)->flags,
sorry, currently perf probe doesn't support (1)"current" special macro, and
(2)force type casting.
If you need that kind of complicated tracing ASAP, I'd like to recommend
you to use systemtap. (which I'm trying to catch up...)
Thank you,
>
> Thanks,
> Luming
> --
> 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/
--
Masami HIRAMATSU
2nd Dept. Linux Technology Center
Hitachi, Ltd., Systems Development Laboratory
E-mail: masami.hiramatsu.pt@...achi.com
--
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