From: Namhyung Kim <namhyung@kernel.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>, Jiri Olsa <jolsa@kernel.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Ian Rogers <irogers@google.com>,
linux-perf-users@vger.kernel.org,
Song Liu <songliubraving@fb.com>, Hao Luo <haoluo@google.com>,
Blake Jones <blakejones@google.com>,
Milian Wolff <milian.wolff@kdab.com>,
bpf@vger.kernel.org
Subject: [PATCH 0/4] Track processes properly for perf record --off-cpu (v2)
Date: Thu, 11 Aug 2022 11:54:52 -0700 [thread overview]
Message-ID: <20220811185456.194721-1-namhyung@kernel.org> (raw)
Hello,
This patch series implements inheritance of offcpu events for the
child processes. Unlike perf events, BPF cannot know which task it
should track except for ones set in a BPF map at the beginning. Add
another BPF program to the fork path and add the process id to the map
if the parent is tracked.
Changes in v2)
* drop already merged fixes
* fix the shell test to omit noises
With this change, it can get the correct off-cpu events for child
processes. I've tested it with perf bench sched messaging which
creates a lot of processes.
$ sudo perf record -e dummy --off-cpu -- perf bench sched messaging
# Running 'sched/messaging' benchmark:
# 20 sender and receiver processes per group
# 10 groups == 400 processes run
Total time: 0.196 [sec]
[ perf record: Woken up 1 times to write data ]
[ perf record: Captured and wrote 0.178 MB perf.data (851 samples) ]
$ sudo perf report --stat | grep -A1 offcpu
offcpu-time stats:
SAMPLE events: 851
The benchmark passes messages by read/write and it creates off-cpu
events. With 400 processes, we can see more than 800 events.
The child process tracking is also enabled when -p option is given.
But -t option does NOT as it only cares about the specific threads.
It may be different what perf_event does now, but I think it makes
more sense.
You can get it from 'perf/offcpu-child-v2' branch in my tree
https://git.kernel.org/pub/scm/linux/kernel/git/namhyung/linux-perf.git
Thanks,
Namhyung
Namhyung Kim (4):
perf offcpu: Check process id for the given workload
perf offcpu: Parse process id separately
perf offcpu: Track child processes
perf offcpu: Update offcpu test for child process
tools/perf/tests/shell/record_offcpu.sh | 57 ++++++++++++++++++++++---
tools/perf/util/bpf_off_cpu.c | 53 ++++++++++++++++++++++-
tools/perf/util/bpf_skel/off_cpu.bpf.c | 38 ++++++++++++++++-
3 files changed, 138 insertions(+), 10 deletions(-)
base-commit: b39c9e1b101d2992de9981673919ae55a088792c
--
2.37.1.595.g718a3a8f04-goog
next reply other threads:[~2022-08-11 18:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-11 18:54 Namhyung Kim [this message]
2022-08-11 18:54 ` [PATCH 1/4] perf offcpu: Check process id for the given workload Namhyung Kim
2022-08-11 18:54 ` [PATCH 2/4] perf offcpu: Parse process id separately Namhyung Kim
2022-08-11 18:54 ` [PATCH 3/4] perf offcpu: Track child processes Namhyung Kim
2022-08-11 18:54 ` [PATCH 4/4] perf offcpu: Update offcpu test for child process Namhyung Kim
2022-08-11 20:58 ` [PATCH 0/4] Track processes properly for perf record --off-cpu (v2) 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=20220811185456.194721-1-namhyung@kernel.org \
--to=namhyung@kernel.org \
--cc=acme@kernel.org \
--cc=blakejones@google.com \
--cc=bpf@vger.kernel.org \
--cc=haoluo@google.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=milian.wolff@kdab.com \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=songliubraving@fb.com \
/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).