Messages in this thread | | | Date | Fri, 10 Jun 2011 16:17:08 +0900 | From | Akihiro Nagai <> | Subject | Re: [PATCH -tip v4 0/7] perf: Introduce branch sub commands |
| |
(2011/05/26 22:28), Frederic Weisbecker wrote: > (Adding David Ahern in Cc) > > Ok that's all good except this needs to use the "perf script" centralized > dump. > > Currently running "perf script" without an actual script dumps > the events by default, whatever kind of event they are: hardware, > software, tracepoints, ... > So we want the branch output to be supported there, so we can reuse > some code and interface. > > For example, "perf script -f branch:comm,tid,sym" would print the > comm, tid and the sym for to and from addresses. > > That's better than creating a new set of options in a new command > that people need to relearn while everybody could simply get > familiarized with common perf script options. > > Of course we can still have a "perf branch" command, which could > be a tiny shortcut that maps to perf record and perf script. > > Like: > > perf branch record > perf branch [trace] -f tid,sym,comm > > Would map to: > > perf record branch:u > perf script -f branch:tid,sym,comm > > And may be if one day we can do something more tricky than a > linear output for branches (like source code coloring/browsing), > then it may be implemented inside perf branch and not rely on > another subcommand. Until then we are only dealing with raw linear > dump, and that's a core job for perf script where we want to > centralize that kind of facility. OK. I agreed that the core job is dumpimg BTS logs on perf script.
Next, I'd like to implement the perf-branch's functions and additional interfaces to perf script. For example, resoving symbols and dso about branch_to address and, adding interfaces to get source file path, line number using debuginfo.
I presented about perf-branch's future plan in LinuxCon Japan 2011, please refer the follwing slide. http://events.linuxfoundation.org/events/linuxcon-japan/nagai (The slide will be available soon)
Thank you.
> > Thanks. >
| |