From: Ingo Molnar <mingo@kernel.org>
To: "Wangnan (F)" <wangnan0@huawei.com>
Cc: Hou Pengyang <houpengyang@huawei.com>,
acme@kernel.org, mingo@redhat.com, namhyung@kernel.org,
a.p.zijlstra@chello.nl, linux-kernel@vger.kernel.org
Subject: Re: [RFC] perf report: introduce --map-anon-mem for anon-executable-memory symbols parsing
Date: Fri, 19 Jun 2015 12:42:14 +0200 [thread overview]
Message-ID: <20150619104214.GA3298@gmail.com> (raw)
In-Reply-To: <5583E088.6080202@huawei.com>
* Wangnan (F) <wangnan0@huawei.com> wrote:
> On 2015/6/18 22:01, Hou Pengyang wrote:
> >This patch introduces a --map-anon-mem argument to perf report to deal
> >with anon-executable-memory symbol parsing.
>
> --map-anon-mem is not a good name. The user defined map area list
> introduced in this patch can be used on not only anon mapping but
> also file mapping.
Yeah, so quirky options generally suck and only 0.01% of the users will use it.
It's in a way worse than not having this code, because we'll have to maintain it,
but it won't be used.
Is there a way to auto-detect 'executable anon mappings' (perhaps by generating an
MMAP event with some extra bit set, or a new MMAP event?) so that it's all
seemless?
The user should not be required to know about such details!
Thanks,
Ingo
next prev parent reply other threads:[~2015-06-19 10:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-18 14:01 [RFC] perf report: introduce --map-anon-mem for anon-executable-memory symbols parsing Hou Pengyang
2015-06-19 9:27 ` Wangnan (F)
2015-06-19 10:42 ` Ingo Molnar [this message]
2015-06-19 20:10 ` Arnaldo Carvalho de Melo
2015-06-22 15:22 ` Hou Pengyang
2015-06-22 15:53 ` Arnaldo Carvalho de Melo
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=20150619104214.GA3298@gmail.com \
--to=mingo@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--cc=houpengyang@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=wangnan0@huawei.com \
/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).