Date: Fri, 19 Jun 2015 12:42:14 +0200
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
Message-ID: <20150619104214.GA3298@gmail.com>
References: <1434636076-13502-1-git-send-email-houpengyang@huawei.com>
 <5583E088.6080202@huawei.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5583E088.6080202@huawei.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1048
Lines: 29


* 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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/