From: Peter Zijlstra <peterz@infradead.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Ingo Molnar <mingo@kernel.org>,
Stephane Eranian <eranian@google.com>,
Namhyung Kim <namhyung@gmail.com>,
LKML <linux-kernel@vger.kernel.org>, Jiri Olsa <jolsa@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
"ak@linux.intel.com" <ak@linux.intel.com>
Subject: Re: [RFC] perf record: missing buildid for callstack modules
Date: Tue, 12 Jan 2016 16:34:40 +0100 [thread overview]
Message-ID: <20160112153440.GJ6357@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <20160112143805.GX18367@kernel.org>
On Tue, Jan 12, 2016 at 11:38:05AM -0300, Arnaldo Carvalho de Melo wrote:
> > Also, just parsing the gigabytes of data that comes out of perf-record
> > takes significant time, let alone poking around the filesystem and
>
> Right, that is what we would elliminate with stashing the content-based
> cookie into a PERF_RECORD_MMAP3 record.
Again, how would you go about getting that cookie for a DSO? The whole
kernel isn't involved with dlopen(), all it sees is a mmap(PROT_EXEC).
> BTW, mtime would incur in postprocessing it all.
mtime can still warn you if things are non-matching at report time
without this post-processing, and thereby solves the problem of staring
at broken/wrong data.
It doesn't get you right data, but knowing your data is broken allows
you to manually do things 'right'.
next prev parent reply other threads:[~2016-01-12 15:34 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 [this message]
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
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=20160112153440.GJ6357@twins.programming.kicks-ass.net \
--to=peterz@infradead.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=namhyung@gmail.com \
--cc=namhyung@kernel.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;
as well as URLs for NNTP newsgroup(s).