Messages in this thread | | | Date | Wed, 6 Apr 2011 14:52:28 +0200 | From | Frederic Weisbecker <> | Subject | Re: [PATCH -tip v3 3/6] perf branch trace: print pid and command |
| |
On Mon, Apr 04, 2011 at 07:00:40PM +0900, Akihiro Nagai wrote: > (2011/04/02 0:13), Frederic Weisbecker wrote: > >On Mon, Mar 28, 2011 at 08:31:23AM -0600, David Ahern wrote: > >>On 03/28/11 04:34, Akihiro Nagai wrote: > >>>>from is sample->ip? to is sample->addr? In the above example > >>>>0x39d3015260 is the value from sample->addr, 1526f is sample->ip which > >>>>resolves to _dl_next_ld_env_entry from /lib64/ld-2.13.so. > >>>Yes. > >>>In this example, resolved address is only sample->ip (branch from). > >>>We need the resolved address of sample->addr (branch to) too, because > >>>both of them are addresses of execution code. > >> > >>Ok, now I understand. In that case add conversion of sample->addr to > >>symbols to perf-script. > > > >I agree that we should rather use perf script for branch dumps. > >Sorry Akihiro, I think we suggested you to create this dedicated > >perf branch by the past. But then perf script became the vanilla dump > >tool in the middle and it seems more suitable today. > > > >We can still create a perf branch later in order to produce some more > >advanced post-processing tools. But for sample dumps perf script (which starts > >to show itself as a misnomer BTW) seems to be the right place. > Finally, I would like to create coverage test tools using BTS on perf. > I'm working on the project "Btrax" that is a coverage test tool using BTS. > The URL is: http://sourceforge.net/projects/btrax/
Cool, what is this tool doing? How is it different from perf branch?
> > And, I would like to implement other functions on perf-branch too. > For example, call graph, source code browser like perf-annotate which > can show executed codes. > So, I wolud like to continue to develop perf-branch.
And you're very welcome to do so. Such features have a nice potential I think.
Thanks.
| |