Messages in this thread | | | Date | Mon, 28 Mar 2011 08:31:23 -0600 | From | David Ahern <> | Subject | Re: [PATCH -tip v3 3/6] perf branch trace: print pid and command |
| |
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.
>> >>> >>> Can perf-script do it by writing scripts? >> >> If you are pulling the data from a perf sample then you can accomplish >> the same goal within perf-script. > It seems that perf-script doesn't have the interface of converting > sample->addr to symbol, pid, comm and others. Of course, we can add > the interface to perf-script, and it could be another way to implement > this function using perf-script. > However, since BTS output usually becomes huge, it would be very slow > to convert all the data by python/perl.
Custom fields are not run through python/perl; they are generated from C-code. Take a look at tools/perf/builtin-script.c
| |