From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Adrian Hunter <adrian.hunter@intel.com>
Cc: Namhyung Kim <namhyung@kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Jiri Olsa <jolsa@kernel.org>, LKML <linux-kernel@vger.kernel.org>,
David Ahern <dsahern@gmail.com>, Andi Kleen <andi@firstfloor.org>,
Stephane Eranian <eranian@google.com>
Subject: Re: [PATCH RESEND] perf record: Add --buildid-all option
Date: Tue, 12 Jan 2016 11:35:36 -0300 [thread overview]
Message-ID: <20160112143536.GW18367@kernel.org> (raw)
In-Reply-To: <5694F166.3000401@intel.com>
Em Tue, Jan 12, 2016 at 02:28:22PM +0200, Adrian Hunter escreveu:
> On 11/01/16 15:38, Namhyung Kim wrote:
> > The --buildid-all option is to record build-id of all DSOs in the file.
> > It might be very costly to postprocess samples to find which DSO hits.
> >
> > Cc: Adrian Hunter <adrian.hunter@intel.com>
> > Cc: Andi Kleen <andi@firstfloor.org>
> > Cc: Stephane Eranian <eranian@google.com>
> > Signed-off-by: Namhyung Kim <namhyung@kernel.org>
> > ---
> > tools/perf/Documentation/perf-record.txt | 3 +++
> > tools/perf/builtin-record.c | 32 ++++++++++++++++++++++++++------
> > 2 files changed, 29 insertions(+), 6 deletions(-)
> >
> > 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..a42cb2955697 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;
> > };
> >
> > @@ -362,6 +363,13 @@ static int process_buildids(struct record *rec)
> > */
> > symbol_conf.ignore_vmlinux_buildid = true;
> >
> > + /*
> > + * If --buildid-all is given, it marks all DSO regardless of hits,
> > + * so no need to process samples.
> > + */
> > + if (rec->buildid_all)
> > + rec->tool.sample = NULL;
>
> I wonder, if we are not processing samples, could the processing could be
> much simpler?
> All we need to do is read all the MMAP events, in any order, and create DSOs
> - no need to
> create threads or map-groups etc etc.
Right, if that was the overhead, have you ever measured this?
- Arnaldo
next prev parent reply other threads:[~2016-01-12 14:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-11 13:37 [PATCH] perf record: Add --buildid-all option Namhyung Kim
2016-01-11 13:38 ` [PATCH RESEND] " Namhyung Kim
2016-01-12 12:28 ` Adrian Hunter
2016-01-12 14:35 ` Arnaldo Carvalho de Melo [this message]
2016-01-13 8:47 ` Adrian Hunter
2016-01-12 15:00 ` Arnaldo Carvalho de Melo
2016-01-13 9:41 ` [tip:perf/urgent] " tip-bot for Namhyung Kim
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=20160112143536.GW18367@kernel.org \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=andi@firstfloor.org \
--cc=dsahern@gmail.com \
--cc=eranian@google.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.