lkml.org 
[lkml]   [2016]   [Jan]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [RFC] perf record: missing buildid for callstack modules
On Thu, Jan 07, 2016 at 01:56:14PM -0800, Stephane Eranian wrote:
> Hi,
>
> Whenever you do:
>
> $ perf record -g -a sleep 10
>
> Perf will collect the callstack for each sample. At the end of the
> run, perf record
> adds the buildid for all dso with at least one sample. But when it does this, it
> only looks at the sampled IP and ignore the modules traversed by the callstack.
> That means that, it is not possible to uniquely identify the modules executed,
> unless they had at least one IP sample captured. But this is not
> always the case.
>
> How about providing an option to perf record to force collecting
> buildid for all IPs
> captured in the callstack? I understand that would cost more at the end of the
> collection, but this would be beneficial to several monitoring scenarios.

If you do that I would rather collect buildid for everything that is synthesized
(everything in /proc)

-Andi

\
 
 \ /
  Last update: 2016-01-07 23:01    [W:1.419 / U:0.336 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site