From: Andres Freund <andres@anarazel.de>
To: Stephane Eranian <eranian@google.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
"eranian@gmail.com" <eranian@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Jiri Olsa <jolsa@redhat.com>, Ingo Molnar <mingo@elte.hu>,
Anton Blanchard <anton@ozlabs.org>,
Namhyung Kim <namhyung@kernel.org>
Subject: Re: perf/jit doesn't cope well with mprotect() to jit containing pages
Date: Thu, 26 Jan 2017 14:38:20 -0800 [thread overview]
Message-ID: <20170126223820.t2564ltcu3cjmt3p@alap3.anarazel.de> (raw)
In-Reply-To: <CABPqkBR3kduhc3L41_fXjRhS-QAiL9Gt37JaQFQ-D=4XZetdZA@mail.gmail.com>
On 2017-01-26 14:26:12 -0800, Stephane Eranian wrote:
> On Thu, Jan 26, 2017 at 2:19 PM, Peter Zijlstra <peterz@infradead.org> wrote:
> > On Thu, Jan 26, 2017 at 01:00:52PM -0800, Andres Freund wrote:
> >> The problem is that (quoted below) without that hack the subsequent
> >> mmaps just expand the previous VMAs which leads to perf loosing its
> >> (address,range) -> symbol mappings for previously (in the same expanded
> >> range) known symbols.
> >
> > I'm assuming this is the userspace tool doing that, right?
> >
> > Acme, is that something we can cure? Instead of throwing away eveything
> > known of the previous map, merge them when they grow?
> >
> > So I think the problem was that we don't track munmap(), so if you see
> > two overlapping mappings, we have no clue and assume an munmap() has
> > happened or something. I can't really remember, its been many many years
> > since I wrote all that :-(
>
> But perf report takes care of overlapping mmaps normally,
> see util/map.c:map_groups__fixup_overlappings
>
> VMA merging does not change anything at the user level.
> The kernel will see two mmaps and so will perf record and perf report.
But the kernel *didn't* report two independent mmaps.
Looking at strace shows that the mmaps were done independently in page
sized chunks:
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7efd3866e000
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7efd3866d000
mprotect(0x7efd3866e000, 4096, PROT_READ|PROT_EXEC) = 0
mprotect(0x7efd3866d000, 4096, PROT_READ|PROT_EXEC) = 0
write(2, "Function loaded: evalexpr0 at 139626038091776 0x7efd3866e000 len 69", 68) = 68
(first function)
mmap(0x7efd3866f000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7efd3866c000
mmap(0x7efd3866e000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7efd3866b000
mprotect(0x7efd3866c000, 4096, PROT_READ|PROT_EXEC) = 0
mprotect(0x7efd3866b000, 4096, PROT_READ|PROT_EXEC) = 0
write(2, "Function loaded: evalexpr1 at 139626038083584 0x7efd3866c000 len 69", 68) = 68
(second function)
But then looking at the unannotated perf script --show-mmap-events:
postgres 4107 595444.867737: PERF_RECORD_MMAP2 4107/4107: [0x7efd3866e000(0x1000) @ 0x7efd3866e000 00:00 0 0]: ---p //anon
postgres 4107 595444.867825: PERF_RECORD_MMAP2 4107/4107: [0x7efd3866d000(0x2000) @ 0x7efd3866d000 00:00 0 0]: ---p //anon
postgres 4107 595444.884090: PERF_RECORD_MMAP2 4107/4107: [0x7efd3866c000(0x3000) @ 0x7efd3866c000 00:00 0 0]: ---p //anon
postgres 4107 595444.884113: PERF_RECORD_MMAP2 4107/4107: [0x7efd3866b000(0x4000) @ 0x7efd3866b000 00:00 0 0]: ---p //anon
these four mmaps regions are:
0x7efd3866e000(0x1000): 0x7efd3866e000 - 0x7efd3866f000
0x7efd3866d000(0x2000): 0x7efd3866d000 - 0x7efd3866f000
0x7efd3866c000(0x3000): 0x7efd3866c000 - 0x7efd3866f000
0x7efd3866b000(0x4000): 0x7efd3866b000 - 0x7efd3866f000
So there's just a single mapping being reported.
> This is what you have.
I'm a bit confused - isn't the trace showing exactly that the mmaps
*are* reported with a merged VMA?
> In the case of Java, if I recall, there is a single large mmap for the
> code cache and it works fine.
That explains why it's working there...
Greetings,
Andres Freund
next prev parent reply other threads:[~2017-01-26 22:39 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-10 5:02 Andres Freund
2016-12-12 8:49 ` Peter Zijlstra
2016-12-12 9:01 ` Andres Freund
2016-12-12 9:28 ` Peter Zijlstra
2017-01-26 1:25 ` Andres Freund
2017-01-26 22:15 ` Peter Zijlstra
2017-01-26 23:04 ` Andres Freund
2017-01-30 11:52 ` [tip:perf/core] perf/core: Fix PERF_RECORD_MMAP2 prot/flags for anonymous memory tip-bot for Peter Zijlstra
2017-01-26 20:32 ` perf/jit doesn't cope well with mprotect() to jit containing pages Stephane Eranian
2017-01-26 21:00 ` Andres Freund
2017-01-26 21:17 ` Stephane Eranian
2017-01-26 21:22 ` Andres Freund
2017-01-26 21:34 ` Stephane Eranian
2017-01-26 21:51 ` Andres Freund
2017-01-26 22:19 ` Peter Zijlstra
2017-01-26 22:26 ` Stephane Eranian
2017-01-26 22:38 ` Andres Freund [this message]
2017-01-26 22:51 ` Stephane Eranian
2017-01-26 23:09 ` Andres Freund
2017-01-26 23:16 ` Stephane Eranian
2017-01-27 13:07 ` Peter Zijlstra
2017-01-27 15:43 ` Arnaldo Carvalho de Melo
2017-01-27 17:35 ` Stephane Eranian
2017-01-27 17:38 ` [PATCH] handle munmap records in tools/perf was: " Arnaldo Carvalho de Melo
2017-01-27 17:46 ` Stephane Eranian
2017-01-27 18:05 ` Arnaldo Carvalho de Melo
2017-01-27 18:10 ` Stephane Eranian
2017-01-27 19:18 ` Arnaldo Carvalho de Melo
2017-01-27 19:26 ` Stephane Eranian
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=20170126223820.t2564ltcu3cjmt3p@alap3.anarazel.de \
--to=andres@anarazel.de \
--cc=acme@kernel.org \
--cc=anton@ozlabs.org \
--cc=eranian@gmail.com \
--cc=eranian@google.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.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
all inboxes | Powered by JetHome®