From: Namhyung Kim <namhyung@kernel.org>
To: Stephane Eranian <eranian@google.com>,
Adrian Hunter <adrian.hunter@intel.com>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
LKML <linux-kernel@vger.kernel.org>, Jiri Olsa <jolsa@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>,
"ak@linux.intel.com" <ak@linux.intel.com>
Subject: Re: [RFC] perf record: missing buildid for callstack modules
Date: Sat, 9 Jan 2016 19:31:43 +0900 [thread overview]
Message-ID: <20160109103143.GE7818@danjae.kornet> (raw)
In-Reply-To: <CABPqkBRQ+4UAkumX8BLkWQmrqVTKOnOjQWpDij2jiDZTmrnOrQ@mail.gmail.com>
Hi Stephane,
On Fri, Jan 08, 2016 at 10:01:24AM -0800, Stephane Eranian wrote:
> On Thu, Jan 7, 2016 at 3:47 PM, Arnaldo Carvalho de Melo
> <acme@kernel.org> wrote:
> > Em Fri, Jan 08, 2016 at 07:47:03AM +0900, Namhyung Kim escreveu:
> >> On January 8, 2016 7:00:35 AM GMT+09:00, Stephane Eranian <eranian@google.com> wrote:
> >> >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.
> >>
> >> Hi Stephane,
> >>
> >> Please see
> >>
> >> https://lkml.org/lkml/2015/3/22/249
> >
> >
> > Oops, Stephane, please try this, so that we can finally merge it :-\
> >
> I will try it today. However, I am a bit worried about the performance
> impact. Unless I am missing something in this approach we may end up
> looking up N times the same module if it appears in N callstacks. In
> Andi's suggested approach, there would be only one pass at the beginning
> (or the end of the run). But you could miss some modules if they are gone
> by the time you run the pass.
How about this then?
Adrian, is it ok to skip process_buildids() for the auxtrace?
Thanks,
Namhyung
diff --git a/tools/perf/Documentation/perf-record.txt b/tools/perf/Documentation/perf-record.txt
index 3a1a32f5479f..fbceb631387c 100644
--- a/tools/perf/Documentation/perf-record.txt
+++ b/tools/perf/Documentation/perf-record.txt
@@ -338,6 +338,9 @@ Options passed to clang when compiling BPF scriptlets.
Specify vmlinux path which has debuginfo.
(enabled when BPF prologue is on)
+--buildid-all::
+Record build-id of all DSOs regardless whether it's actually hit or not.
+
SEE ALSO
--------
linkperf:perf-stat[1], linkperf:perf-list[1]
diff --git a/tools/perf/builtin-record.c b/tools/perf/builtin-record.c
index dc4e0adf5c5b..ab18db3153a6 100644
--- a/tools/perf/builtin-record.c
+++ b/tools/perf/builtin-record.c
@@ -50,6 +50,7 @@ struct record {
int realtime_prio;
bool no_buildid;
bool no_buildid_cache;
+ bool buildid_all;
unsigned long long samples;
};
@@ -755,14 +756,10 @@ out_child:
file->size = lseek(perf_data_file__fd(file), 0, SEEK_CUR);
if (!rec->no_buildid) {
- process_buildids(rec);
- /*
- * We take all buildids when the file contains
- * AUX area tracing data because we do not decode the
- * trace because it would take too long.
- */
- if (rec->opts.full_auxtrace)
+ if (rec->buildid_all)
dsos__hit_all(rec->session);
+ else
+ process_buildids(rec);
}
perf_session__write_header(rec->session, rec->evlist, fd, true);
}
@@ -1138,6 +1135,8 @@ struct option __record_options[] = {
"options passed to clang when compiling BPF scriptlets"),
OPT_STRING(0, "vmlinux", &symbol_conf.vmlinux_name,
"file", "vmlinux pathname"),
+ OPT_BOOLEAN(0, "buildid-all", &record.buildid_all,
+ "Record build-id of all DSOs regardless of hits"),
OPT_END()
};
@@ -1255,6 +1254,14 @@ int cmd_record(int argc, const char **argv, const char *prefix __maybe_unused)
if (err)
goto out_symbol_exit;
+ /*
+ * We take all buildids when the file contains
+ * AUX area tracing data because we do not decode the
+ * trace because it would take too long.
+ */
+ if (rec->opts.full_auxtrace)
+ rec->buildid_all = true;
+
if (record_opts__config(&rec->opts)) {
err = -EINVAL;
goto out_symbol_exit;
next prev parent reply other threads:[~2016-01-09 10:32 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-07 21:56 [RFC] perf record: missing buildid for callstack modules Stephane Eranian
2016-01-07 21:57 ` Andi Kleen
2016-01-07 22:00 ` Stephane Eranian
2016-01-07 21:59 ` Arnaldo Carvalho de Melo
2016-01-07 22:00 ` Stephane Eranian
2016-01-07 22:47 ` Namhyung Kim
2016-01-07 23:47 ` Arnaldo Carvalho de Melo
2016-01-08 18:01 ` Stephane Eranian
2016-01-08 18:19 ` Arnaldo Carvalho de Melo
2016-01-11 17:30 ` Peter Zijlstra
2016-01-11 18:22 ` Arnaldo Carvalho de Melo
2016-01-11 20:06 ` Stephane Eranian
2016-01-12 10:39 ` Ingo Molnar
2016-01-12 11:35 ` Peter Zijlstra
2016-01-12 12:18 ` Ingo Molnar
2016-01-12 13:40 ` Peter Zijlstra
2016-01-12 14:38 ` Arnaldo Carvalho de Melo
2016-01-12 15:34 ` Peter Zijlstra
2016-01-12 15:48 ` Arnaldo Carvalho de Melo
2016-01-12 16:10 ` Peter Zijlstra
2016-01-12 16:27 ` Peter Zijlstra
2016-01-12 17:15 ` Arnaldo Carvalho de Melo
2016-01-13 10:21 ` Ingo Molnar
2016-01-13 12:40 ` Peter Zijlstra
2016-01-14 11:27 ` Ingo Molnar
2016-01-14 11:36 ` Peter Zijlstra
2016-01-15 1:59 ` Stephane Eranian
2016-01-15 9:34 ` Peter Zijlstra
2016-01-15 18:58 ` Stephane Eranian
2016-01-15 19:49 ` Arnaldo Carvalho de Melo
2016-01-15 21:49 ` Stephane Eranian
2016-01-15 21:36 ` Peter Zijlstra
2016-01-12 21:02 ` Stephane Eranian
2016-01-12 13:08 ` One Thousand Gnomes
2016-01-12 14:34 ` Arnaldo Carvalho de Melo
2016-01-12 15:37 ` Peter Zijlstra
2016-01-13 10:25 ` Ingo Molnar
2016-01-12 14:23 ` Arnaldo Carvalho de Melo
2016-01-13 9:57 ` Ingo Molnar
2016-01-13 15:27 ` Arnaldo Carvalho de Melo
2016-01-19 14:56 ` Namhyung Kim
2016-01-19 15:27 ` Peter Zijlstra
2016-01-19 15:48 ` Arnaldo Carvalho de Melo
2016-01-09 10:31 ` Namhyung Kim [this message]
2016-01-11 9:27 ` Adrian Hunter
2016-01-11 11:02 ` Namhyung Kim
2016-01-11 11:54 ` Adrian Hunter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160109103143.GE7818@danjae.kornet \
--to=namhyung@kernel.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=ak@linux.intel.com \
--cc=eranian@google.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox