linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Andi Kleen <andi@firstfloor.org>,
	Brendan Gregg <brendan.d.gregg@gmail.com>,
	Carl Love <cel@us.ibm.com>, Pekka Enberg <penberg@kernel.org>,
	"linux-perf-use." <linux-perf-users@vger.kernel.org>
Subject: Re: Perf support for interpreted and Just-In-Time translated olanguages
Date: Wed, 10 Dec 2014 18:32:28 +0100	[thread overview]
Message-ID: <20141210173228.GA6759@two.firstfloor.org> (raw)
In-Reply-To: <20141209222203.GD8788@kernel.org>

> I understood that there is a way to ask for the current JITted code ->
> symtab, my question was specifically about how to get notifications when
> those mappings change.

JVMTI has a callback interface, so you can register call backs for
specific events:

http://docs.oracle.com/javase/7/docs/platform/jvmti/jvmti.html#EventSection

> When we use mmap(addr, len, PROT_EXEC) the kernel has a meta event
> called PERF_RECORD_MMAP that will record addr range, symtab DSO path,
> and we ask it to be timestamped, how to do that for the equivalent part
> in the JVM?

The CompiledMethodLoad callback would trigger that event.

> 
> My initial thought was to find that using perf probe and insert there a
> probe point, but I think that there may be already an existing
> tracepoint in the jvm for that, one that, from what I've read so far,
> is _not_ being used by this java perf agent, right?

It's not needed. Java already has all the needed hooks.

Maybe for some different JITs.

> 
> From what I understood, how would it insert that event into the
> perf.data event stream? Only if it necessarily involved a new mmap, via
> the kernel, etc.

That's the new interface to be defined.

Just write a perf.data?

-Andi


-- 
ak@linux.intel.com -- Speaking for myself only.

  parent reply	other threads:[~2014-12-10 17:32 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-05 20:18 Perf support for interpreted and Just-In-Time translated languages Carl Love
2014-12-05 21:27 ` Brendan Gregg
2014-12-09 20:34   ` Arnaldo Carvalho de Melo
2014-12-09 22:01     ` Andi Kleen
2014-12-09 22:22       ` Perf support for interpreted and Just-In-Time translated olanguages Arnaldo Carvalho de Melo
2014-12-10  0:38         ` Andi Kleen
2014-12-10 17:41           ` Carl Love
2014-12-10 18:09             ` Andi Kleen
2014-12-10 19:21             ` Arnaldo Carvalho de Melo
2014-12-10 19:19           ` Arnaldo Carvalho de Melo
2014-12-10 17:32         ` Andi Kleen [this message]
2014-12-10 17:39           ` David Ahern
2014-12-10 18:05             ` Andi Kleen
2014-12-10 18:27               ` David Ahern
2014-12-10 19:43                 ` Arnaldo Carvalho de Melo
2015-01-09 20:19                   ` Carl Love
2015-01-10  4:15                     ` William Cohen
2015-01-10 15:14                       ` David Ahern
2015-01-12 17:22                         ` Carl Love
2015-01-12 17:58                           ` David Ahern
2015-01-12 18:43                             ` Carl Love
2015-01-20 18:19                             ` Carl Love
2015-01-20 19:29                               ` Arnaldo Carvalho de Melo
2015-01-20 20:34                                 ` Carl Love
2015-01-20 20:52                                   ` Arnaldo Carvalho de Melo
2015-01-23  8:25                               ` Sujoy Saraswati
2014-12-10  7:55     ` Perf support for interpreted and Just-In-Time translated languages Pekka Enberg

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=20141210173228.GA6759@two.firstfloor.org \
    --to=andi@firstfloor.org \
    --cc=acme@kernel.org \
    --cc=brendan.d.gregg@gmail.com \
    --cc=cel@us.ibm.com \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=penberg@kernel.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;
as well as URLs for NNTP newsgroup(s).