perf inject --jit: Remove //anon mmap events
PATCH RESEND 1/1 perf inject --jit: Remove //anon mmap events
From: Steve MacLean <[email protected]>
While a JIT is jitting code it will eventually need to commit more pages and change these pages to executable permissions.
Typically the JIT will want these colocated to minimize branch displacements.
The kernel will coalesce these anonymous mapping with identical permissions before sending an MMAP event for the new pages. This means the mmap event for the new pages will include the older pages.
These anonymous mmap events will obscure the jitdump injected pseudo events. This means that the jitdump generated symbols, machine code, debugging info, and unwind info will no longer be used.
Observations:
When a process emits a jit dump marker and a jitdump file, the perf-xxx.map file represents inferior information which has been superceded by the jitdump jit-xxx.dump file.
Further the '//anon*' mmap events are only required for the legacy perf-xxx.map mapping.
Summary:
Add rbtree to track which pids have sucessfully injected a jitdump file.
During "perf inject --jit", discard "//anon*" mmap events for any pid which has sucessfully processed a jitdump file.
Committer testing:
// jitdump case
perf record <app with jitdump>
perf inject --jit --input perf.data --output perfjit.data
// verify mmap "//anon" events present initially
perf script --input perf.data --show-mmap-events | grep '//anon' // verify mmap "//anon" events removed
perf script --input perfjit.data --show-mmap-events | grep '//anon'
// no jitdump case
perf record <app without jitdump>
perf inject --jit --input perf.data --output perfjit.data
// verify mmap "//anon" events present initially
perf script --input perf.data --show-mmap-events | grep '//anon' // verify mmap "//anon" events not removed
perf script --input perfjit.data --show-mmap-events | grep '//anon'
Repro:
This issue was discovered while testing the initial CoreCLR jitdump implementation. https://github.com/dotnet/coreclr/pull/26897.
--- tools/perf/builtin-inject.c | 4 +-- tools/perf/util/jitdump.c | 63 +++++++++++++++++++++++++++++++++++++++++++++ 2 files changed, 65 insertions(+), 2 deletions(-)
tools/perf/builtin-inject.c +2 -2
@@ -263,7 +263,7 @@ static int perf_event__jit_repipe_mmap(struct perf_tool *tool,* if jit marker, then inject jit mmaps and generate ELF images */ ret =jit_process (inject->session, &inject->output, machine, - event->mmap.filename, sample->pid, &n); + event->mmap.filename, event->mmap.pid, &n);if (ret <0 )return ret;if (ret) {
@@ -301,7 +301,7 @@ static int perf_event__jit_repipe_mmap2(struct perf_tool *tool,* if jit marker, then inject jit mmaps and generate ELF images */ ret =jit_process (inject->session, &inject->output, machine, - event->mmap2.filename, sample->pid, &n); + event->mmap2.filename, event->mmap2.pid, &n);if (ret <0 )return ret;if (ret) {
tools/perf/util/jitdump.c +63 -0
87 lines not on this page · raw message
Signature · 1 line
1.8.3.1
Quoted 51 lines · Steve MacLean
From: Steve MacLean <[email protected]>
While a JIT is jitting code it will eventually need to commit more pages and change these pages to executable permissions.
Typically the JIT will want these colocated to minimize branch displacements.
The kernel will coalesce these anonymous mapping with identical permissions before sending an MMAP event for the new pages. This means the mmap event for the new pages will include the older pages.
These anonymous mmap events will obscure the jitdump injected pseudo events. This means that the jitdump generated symbols, machine code, debugging info, and unwind info will no longer be used.
Observations:
When a process emits a jit dump marker and a jitdump file, the perf-xxx.map file represents inferior information which has been superceded by the jitdump jit-xxx.dump file.
Further the '//anon*' mmap events are only required for the legacy perf-xxx.map mapping.
Summary:
Add rbtree to track which pids have sucessfully injected a jitdump file.
During "perf inject --jit", discard "//anon*" mmap events for any pid which has sucessfully processed a jitdump file.
Committer testing:
// jitdump case
perf record <app with jitdump>
perf inject --jit --input perf.data --output perfjit.data// verify mmap "//anon" events present initially
perf script --input perf.data --show-mmap-events | grep '//anon' // verify mmap "//anon" events removed
perf script --input perfjit.data --show-mmap-events | grep '//anon'// no jitdump case
perf record <app without jitdump>
perf inject --jit --input perf.data --output perfjit.data// verify mmap "//anon" events present initially
perf script --input perf.data --show-mmap-events | grep '//anon' // verify mmap "//anon" events not removed
perf script --input perfjit.data --show-mmap-events | grep '//anon'
Quoted 4 lines
Repro:
This issue was discovered while testing the initial CoreCLR jitdump implementation. https://github.com/dotnet/coreclr/pull/26897.
I posted some questions for previous version in here, but can't find answers:
https://lore.kernel.org/lkml/20191003105716.GB23291@krava/
thanks,
jirka