Messages in this thread | | | Date | Thu, 7 Jan 2016 14:00:35 -0800 | Subject | Re: [RFC] perf record: missing buildid for callstack modules | From | Stephane Eranian <> |
| |
On Thu, Jan 7, 2016 at 1:59 PM, Arnaldo Carvalho de Melo <acme@kernel.org> wrote: > Em Thu, Jan 07, 2016 at 01:56:14PM -0800, Stephane Eranian escreveu: >> 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. > > I agree, would consider applying a patch that provides the option but > does not do this by default. > I agree, not the default.
| |