[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CEFDA8E4.2D359%gjain@fb.com>
Date: Thu, 16 Jan 2014 20:23:27 +0000
From: Gaurav Jain <gjain@...com>
To: Arnaldo Carvalho de Melo <acme@...stprotocols.net>,
Namhyung Kim <namhyung@...nel.org>
CC: Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Paul Mackerras <paulus@...ba.org>,
Ingo Molnar <mingo@...nel.org>,
Namhyung Kim <namhyung.kim@....com>,
LKML <linux-kernel@...r.kernel.org>,
Jiri Olsa <jolsa@...hat.com>, David Ahern <dsahern@...il.com>,
Andi Kleen <andi@...stfloor.org>
Subject: Re: [PATCH] perf tools: Fix JIT profiling on heap
On 1/16/14, 9:37 AM, "Arnaldo Carvalho de Melo" <acme@...stprotocols.net>
wrote:
>Em Thu, Jan 16, 2014 at 10:49:31AM +0900, Namhyung Kim escreveu:
>> Gaurav reported that perf cannot profile JIT program if it executes
>> the code on heap. This was because current map__new() only handle JIT
>> on anon mappings - extends it to handle no_dso (heap, stack) case too.
>>
>> This patch assumes JIT profiling only provides dynamic function
>> symbols so check the mapping type to distinguish the case. It'd
>> provide no symbols for data mapping - if we need to support symbols on
>> data mappings later it should be changed.
>
>But we do support symbols in data mappings, that is why we have
>MAP__VARIABLE, etc, can you elaborate?
Does perf support data mappings from perf map files? Could you please
share an example of how I may be able to use this.
>Gaurav, do this fixes the problem you reported? Can I have your
>Tested-by: tag?
Yep, I¹ve tested this version of the patch and it works great for me.
Thanks,
Gaurav
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists