Hi, On Tue, May 18, 2010 at 4:36 AM, Stephane Eranian <eran...@google.com>wrote:
> Hi, > > I am trying to understand how perf record deals with buildids. > I am interested in offline and not live processing. According > to http://lkml.org/lkml/2010/5/1/5, the inject patch does not > change perf record. It should still save the buildids at the > end of the perf.data file. I suspect it does not anymore. > > If I do: > > $ perf record -o - noploop 2 | perf inject -b | perf report -v -i - > [ perf record: Woken up 1 times to write data ] > [ perf record: Captured and wrote 0.063 MB - (~2756 samples) ] > build id event received for > /lib/modules/2.6.34-tip-default+/build/vmlinux: > 0ad6b5dd1295e0177be9d12acafa72daac664ee7 > Looking at the vmlinux_path (5 entries long) > Using /lib/modules/2.6.34-tip-default+/build/vmlinux for symbols > build id event received for /usr/local/bin/noploop: > e8a36c0c1e36e18522233ff2a4b1fff0f9689b1c > > There is indeed a buildid generated for my noploop test program. > > But I do the simpler: > > $ perf record -o perf.out noploop 2 > noploop for 2 seconds > [ perf record: Woken up 1 times to write data ] > [ perf record: Captured and wrote 0.063 MB perf.out (~2739 samples) ] > > $ perf buildid-list -i perf.out > $ > > I get nothing. > > If I try with perf report -D: > > $ perf report -D -i perf.out > ..... > TOTAL events: 2011 > MMAP events: 21 > LOST events: 0 > COMM events: 1 > EXIT events: 1 > THROTTLE events: 0 > UNTHROTTLE events: 0 > FORK events: 0 > READ events: 0 > SAMPLE events: 1988 > ATTR events: 0 > EVENT_TYPE events: 0 > TRACING_DATA events: 0 > BUILD_ID events: 0 > > It shows no buildid events found. > > Right, in the 'perf record -o perf.out' case, the build ids should be be saved in the normal header-writing path, and not via BUILD_ID events, so the 0 here would be expected. It looks like the HEADER_BUILD_ID feature isn't being set properly any more maybe due to some changes under dsos__read_build_ids() - I'll have to take a further look later tonight... Tom So either something is broken or I don't understand the logic here. >
------------------------------------------------------------------------------
_______________________________________________ perfmon2-devel mailing list perfmon2-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/perfmon2-devel
