From: Jiri Olsa <olsajiri@gmail.com>
To: Adrian Hunter <adrian.hunter@intel.com>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
Ian Rogers <irogers@google.com>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>
Subject: Re: [PATCH V2] libperf evlist: Fix per-thread mmaps for multi-threaded targets
Date: Wed, 7 Sep 2022 16:20:59 +0200 [thread overview]
Message-ID: <Yxioy/TXc/KDLoDL@krava> (raw)
In-Reply-To: <20220905114209.8389-1-adrian.hunter@intel.com>
On Mon, Sep 05, 2022 at 02:42:09PM +0300, Adrian Hunter wrote:
> The offending commit removed mmap_per_thread(), which did not consider
> the different set-output rules for per-thread mmaps i.e. in the per-thread
> case set-output is used for file descriptors of the same thread not the
> same cpu.
>
> This was not immediately noticed because it only happens with
> multi-threaded targets and we do not have a test for that yet.
>
> Reinstate mmap_per_thread() expanding it to cover also system-wide per-cpu
> events i.e. to continue to allow the mixing of per-thread and per-cpu
> mmaps.
>
> Debug messages (with -vv) show the file descriptors that are opened with
> sys_perf_event_open. New debug messages are added (needs -vvv) that show
> also which file descriptors are mmapped and which are redirected with
> set-output.
>
> In the per-cpu case (cpu != -1) file descriptors for the same CPU are
> set-output to the first file descriptor for that CPU.
>
> In the per-thread case (cpu == -1) file descriptors for the same thread are
> set-output to the first file descriptor for that thread.
>
> Example (process 17489 has 2 threads):
>
> Before (but with new debug prints):
>
> $ perf record --no-bpf-event -vvv --per-thread -p 17489
> <SNIP>
> sys_perf_event_open: pid 17489 cpu -1 group_fd -1 flags 0x8 = 5
> sys_perf_event_open: pid 17490 cpu -1 group_fd -1 flags 0x8 = 6
> <SNIP>
> libperf: idx 0: mmapping fd 5
> libperf: idx 0: set output fd 6 -> 5
> failed to mmap with 22 (Invalid argument)
>
> After:
>
> $ perf record --no-bpf-event -vvv --per-thread -p 17489
> <SNIP>
> sys_perf_event_open: pid 17489 cpu -1 group_fd -1 flags 0x8 = 5
> sys_perf_event_open: pid 17490 cpu -1 group_fd -1 flags 0x8 = 6
> <SNIP>
> libperf: mmap_per_thread: nr cpu values (may include -1) 1 nr threads 2
> libperf: idx 0: mmapping fd 5
> libperf: idx 1: mmapping fd 6
> <SNIP>
> [ perf record: Woken up 2 times to write data ]
> [ perf record: Captured and wrote 0.018 MB perf.data (15 samples) ]
>
> Per-cpu example (process 20341 has 2 threads, same as above):
>
> $ perf record --no-bpf-event -vvv -p 20341
> <SNIP>
> sys_perf_event_open: pid 20341 cpu 0 group_fd -1 flags 0x8 = 5
> sys_perf_event_open: pid 20342 cpu 0 group_fd -1 flags 0x8 = 6
> sys_perf_event_open: pid 20341 cpu 1 group_fd -1 flags 0x8 = 7
> sys_perf_event_open: pid 20342 cpu 1 group_fd -1 flags 0x8 = 8
> sys_perf_event_open: pid 20341 cpu 2 group_fd -1 flags 0x8 = 9
> sys_perf_event_open: pid 20342 cpu 2 group_fd -1 flags 0x8 = 10
> sys_perf_event_open: pid 20341 cpu 3 group_fd -1 flags 0x8 = 11
> sys_perf_event_open: pid 20342 cpu 3 group_fd -1 flags 0x8 = 12
> sys_perf_event_open: pid 20341 cpu 4 group_fd -1 flags 0x8 = 13
> sys_perf_event_open: pid 20342 cpu 4 group_fd -1 flags 0x8 = 14
> sys_perf_event_open: pid 20341 cpu 5 group_fd -1 flags 0x8 = 15
> sys_perf_event_open: pid 20342 cpu 5 group_fd -1 flags 0x8 = 16
> sys_perf_event_open: pid 20341 cpu 6 group_fd -1 flags 0x8 = 17
> sys_perf_event_open: pid 20342 cpu 6 group_fd -1 flags 0x8 = 18
> sys_perf_event_open: pid 20341 cpu 7 group_fd -1 flags 0x8 = 19
> sys_perf_event_open: pid 20342 cpu 7 group_fd -1 flags 0x8 = 20
> <SNIP>
> libperf: mmap_per_cpu: nr cpu values 8 nr threads 2
> libperf: idx 0: mmapping fd 5
> libperf: idx 0: set output fd 6 -> 5
> libperf: idx 1: mmapping fd 7
> libperf: idx 1: set output fd 8 -> 7
> libperf: idx 2: mmapping fd 9
> libperf: idx 2: set output fd 10 -> 9
> libperf: idx 3: mmapping fd 11
> libperf: idx 3: set output fd 12 -> 11
> libperf: idx 4: mmapping fd 13
> libperf: idx 4: set output fd 14 -> 13
> libperf: idx 5: mmapping fd 15
> libperf: idx 5: set output fd 16 -> 15
> libperf: idx 6: mmapping fd 17
> libperf: idx 6: set output fd 18 -> 17
> libperf: idx 7: mmapping fd 19
> libperf: idx 7: set output fd 20 -> 19
> <SNIP>
> [ perf record: Woken up 7 times to write data ]
> [ perf record: Captured and wrote 0.020 MB perf.data (17 samples) ]
>
> Fixes: ae4f8ae16a07 ("libperf evlist: Allow mixing per-thread and per-cpu mmaps")
> Signed-off-by: Adrian Hunter <adrian.hunter@intel.com>
Acked-by: Jiri Olsa <jolsa@kernel.org>
thanks,
jirka
next prev parent reply other threads:[~2022-09-07 14:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-05 11:42 [PATCH V2] libperf evlist: Fix per-thread mmaps for multi-threaded targets Adrian Hunter
2022-09-06 12:53 ` Arnaldo Carvalho de Melo
2022-09-06 12:59 ` Jiri Olsa
2022-09-06 14:04 ` Adrian Hunter
2022-09-06 17:43 ` Ian Rogers
2022-09-06 21:17 ` Vince Weaver
2022-09-06 19:45 ` Jiri Olsa
2022-09-07 5:05 ` Adrian Hunter
2022-09-06 17:50 ` Namhyung Kim
2022-09-07 4:52 ` Adrian Hunter
2022-09-07 14:20 ` Jiri Olsa [this message]
2022-09-08 15:18 ` Arnaldo Carvalho de Melo
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=Yxioy/TXc/KDLoDL@krava \
--to=olsajiri@gmail.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=irogers@google.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).