From: Andi Kleen <andi@firstfloor.org>
To: Stephane Eranian <eranian@google.com>
Cc: Arnaldo Carvalho de Melo <acme@infradead.org>,
Ingo Molnar <mingo@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Namhyung Kim <namhyung@kernel.org>, Jiri Olsa <jolsa@redhat.com>
Subject: Re: [PATCH] tools, perf: Allow the user to disable time stamps
Date: Tue, 25 Mar 2014 15:34:52 -0700 [thread overview]
Message-ID: <87wqfhoqk3.fsf@tassilo.jf.intel.com> (raw)
In-Reply-To: <CABPqkBT48Nx0qkPgnS=JsX0Etb7Xr1rLgoOAk1bt7L+DHvugGA@mail.gmail.com> (Stephane Eranian's message of "Tue, 25 Mar 2014 23:15:05 +0100")
Stephane Eranian <eranian@google.com> writes:
>>
> But getting the mmaps at the right moment is crucial for some apps
> especially if address space is recycled otherwise symbolization
> may be incorrect.
Yes that is why it is only an option and not default.
You need to know what you're doing.
BTW I think the recycle case is not very likely on non JIT.
>> You're right for some special analysis it matters, that is why
>> it is only an option.
>>
>> But for the standard "only care about perf report and
>> don't care about about program startup" case it's a nice saving.
>>
> How do you know in advance you won't need mmap ordering?
When I measure a long running process and I know it doesn't
fork/dlopen/jit. Using --initial-delay also helps to skip
the startup phase or attaching later.
I believe it's actually a good choice for most non
forky workloads. But yes it cannot be made default.
-Andi
--
ak@linux.intel.com -- Speaking for myself only
next prev parent reply other threads:[~2014-03-25 22:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-25 20:44 [PATCH] tools, perf: Allow the user to disable time stamps Andi Kleen
2014-03-25 20:54 ` Stephane Eranian
2014-03-25 21:01 ` Andi Kleen
2014-03-25 22:15 ` Stephane Eranian
2014-03-25 22:34 ` Andi Kleen [this message]
2014-03-25 21:06 ` Andi Kleen
-- strict thread matches above, loose matches on Subject: below --
2014-03-25 20:34 Andi Kleen
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=87wqfhoqk3.fsf@tassilo.jf.intel.com \
--to=andi@firstfloor.org \
--cc=acme@infradead.org \
--cc=eranian@google.com \
--cc=jolsa@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox