linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Giovanni Gherdovich <ggherdovich@suse.cz>
To: Milian Wolff <milian.wolff@kdab.com>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: profiling Firefox, no perf-<PID>.map file
Date: Sun, 04 Sep 2016 12:50:35 +0200	[thread overview]
Message-ID: <1472986235.1802.4.camel@suse.cz> (raw)
In-Reply-To: <3432177.9qbfN6MEYg@agathebauer>

On Sat, 2016-09-03 at 22:37 +0200, Milian Wolff wrote:
> [...]
> 
> You need integration for generating such a file in the JavaScript engine. node 
> and QML are two examples for that. But if you don't want to attribute JIT code 
> addresses to JavaScript code, you can safely ignore this warning.
> 

Right, thanks for pointing it out. It's the VM who's JIT'ing that is
in charge of writing the perf-<PID>.map files.
I've now found the relevant part in Brendan Gregg's perf page describing
this: http://www.brendangregg.com/perf.html#JIT_Symbols
The first time around I read that section it didn't ring a bell,
now I see what the problem is.

Thanks,
Giovanni

      reply	other threads:[~2016-09-04 10:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-03 18:53 profiling Firefox, no perf-<PID>.map file Giovanni Gherdovich
2016-09-03 20:37 ` Milian Wolff
2016-09-04 10:50   ` Giovanni Gherdovich [this message]

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=1472986235.1802.4.camel@suse.cz \
    --to=ggherdovich@suse.cz \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=milian.wolff@kdab.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).