Em Tue, Dec 09, 2014 at 02:01:11PM -0800, Andi Kleen escreveu: > Arnaldo Carvalho de Melo <[email protected]> writes: > > > > Humm, I wonder if we could try to attach a 'perf probe' (uprobes) to > > some JVM method that is known to invalidate JITted code -> symtab > > mappings so that we would use it as a PERF_RECORD_MMAP equivalent... > > I.e. we would know that that map overlaps the previous one and that the > > symtab is a new one for that addr range, etc, just like we do for > > executable mmaps coming from the kernel (PERF_RECORD_MMAP). > > JAVA already has a API to get all these information. That is > what oprofile, Vtune and Brendan's agent uses.
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. The described solutions states that those maps can get stale, i.e. they will change and we don't get a notification for that. 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? 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? >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. > It just needs a better interface from the agent to perf, to pass all > needed information, including symbols, line numbers, executable code > (for PT decoding and for showing diassembler), and ordering it by time > so that no hacks are needed. > > BTW other JITs (LLVM, Mono, V8, ...) have similar interfaces. > > Longer term as the kernel gets more JITed (eBPF etc.) it likely needs > some kind of JIT interface too. Right, this is something we need to have, no questions about it, its just a matter of cooking up some prototype implementation... If, for instance, the java agent would put on some file those events, timestamped, then when in perf report we would just insert them into the event stream as synthesized PERF_RECORD_MMAPs, probably that would be enough. > -Andi > > -- > [email protected] -- Speaking for myself only -- To unsubscribe from this list: send the line "unsubscribe linux-perf-users" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
