From: Akihiro Nagai <akihiro.nagai.hw@hitachi.com>
To: David Ahern <dsahern@gmail.com>
Cc: Arnaldo Carvalho de Melo <acme@infradead.org>,
Ingo Molnar <mingo@elte.hu>,
Peter Zijlstra <peterz@infradead.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
linux-kernel@vger.kernel.org,
Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
yrl.pp-manager.tt@hitachi.com
Subject: Re: [PATCH -tip 0/4] perf script: add BTS analysis features
Date: Thu, 30 Jun 2011 14:18:55 +0900 [thread overview]
Message-ID: <4E0C073F.5020901@hitachi.com> (raw)
In-Reply-To: <4E09F173.2060508@gmail.com>
(2011/06/29 0:21), David Ahern wrote:
> On 06/28/2011 01:40 AM, Akihiro Nagai wrote:
>> BTW, I couldn't run a script generated by 'perf script -g {pyton|perl}'
>> with branch events. How do I make scripts analyzing branch events?
>>
>> # perf record -e branches:u -c 1 -d ls
>> # perf script -g python
>> # perf script -s perf-script.py
>> in trace_begin
>> Fatal: no event_list!
>> # perf script -g perl
>> # perf script -s perf-script.pl
>> Fatal: no event_list!
>
> Generated scripts currently only work on trace events. At this point it
> is arguable that perf-script should be focused on the python and perl
> scripts and the code for dumping the events should be moved to a new
> command (perf-dump?).
I see. Thank you for your information.
I'd like to try adding the function to deal with HW-events with perf-script.
I like perf-dump idea. It makes easier to specialize output format
based on each event type.
Thank you.
>
> David
prev parent reply other threads:[~2011-06-30 5:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-28 7:40 [PATCH -tip 0/4] perf script: add BTS analysis features Akihiro Nagai
2011-06-28 7:40 ` [PATCH -tip 1/4] perf script: resolve DSOs and symbols for user-space Akihiro Nagai
2011-06-28 7:40 ` [PATCH -tip 2/4] perf script: print DSOs and symbols for BTS branch_from addr Akihiro Nagai
2011-06-28 7:40 ` [PATCH -tip 3/4] perf script: add the option to show the offset of symbols Akihiro Nagai
2011-06-28 14:52 ` David Ahern
2011-06-28 14:55 ` David Ahern
2011-06-30 4:44 ` Akihiro Nagai
2011-06-30 15:42 ` David Ahern
2011-06-28 7:40 ` [PATCH -tip 4/4] perf script: add option resolving vmlinux path Akihiro Nagai
2011-06-28 15:21 ` [PATCH -tip 0/4] perf script: add BTS analysis features David Ahern
2011-06-30 5:18 ` Akihiro Nagai [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=4E0C073F.5020901@hitachi.com \
--to=akihiro.nagai.hw@hitachi.com \
--cc=acme@infradead.org \
--cc=dsahern@gmail.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=yrl.pp-manager.tt@hitachi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox