[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87sj2f9n8o.fsf@sejong.aot.lge.com>
Date: Thu, 25 Apr 2013 14:45:59 +0900
From: Namhyung Kim <namhyung@...nel.org>
To: "zhangwei\(Jovi\)" <jovi.zhangwei@...wei.com>
Cc: Steven Rostedt <rostedt@...dmis.org>,
Arnaldo Carvalho de Melo <acme@...stprotocols.net>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Paul Mackerras <paulus@...ba.org>,
Ingo Molnar <mingo@...nel.org>,
Namhyung Kim <namhyung.kim@....com>,
LKML <linux-kernel@...r.kernel.org>,
Frederic Weisbecker <fweisbec@...il.com>,
Jiri Olsa <jolsa@...hat.com>, David Ahern <dsahern@...il.com>,
Stephane Eranian <eranian@...gle.com>
Subject: Re: [RFC 00/14] perf tools: Introduce new 'ftrace' command
Hi Jovi,
On Wed, 24 Apr 2013 19:14:49 +0800, zhangwei wrote:
> On 2013/4/24 17:27, Namhyung Kim wrote:
>>> Also, have you given thought on how to execute both ftrace and the pmu
>>> counters? That is, to get a way to interleave the data?
>>
>> I didn't think about it yet. I just thought enabling event tracing in
>> ftrace and get the data along with the function tracing. I'm not sure
>> how they interfere each other when enabled at the same time.
>>
>> If that's not a valid concern, I think it's doable.
>
> There have ftrace:function event in tracing infrastructure, that event works in perf,
> but I'm not sure if it could enhance to showing function graph as this patchset did.
> perf record -e ftrace:function ls > /dev/null
> perf report
Yes, I know that.
When I asked to Steve that how I can use ftrace:funcgraph_{entry,exit}
as tracepoint events in perf tools, he said it'd be a non-trivial job
and need some amount of scary work. :)
Thanks,
Namhyung
--
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