From: Namhyung Kim <namhyung@kernel.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>, Jiri Olsa <jolsa@redhat.com>
Cc: Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
Andi Kleen <ak@linux.intel.com>, Ian Rogers <irogers@google.com>,
Changbin Du <changbin.du@gmail.com>,
Song Liu <songliubraving@fb.com>,
Athira Rajeev <atrajeev@linux.vnet.ibm.com>,
Stephane Eranian <eranian@google.com>
Subject: [PATCHSET 0/5] perf ftrace: Implement function latency histogram (v2)
Date: Wed, 15 Dec 2021 10:51:49 -0800 [thread overview]
Message-ID: <20211215185154.360314-1-namhyung@kernel.org> (raw)
Hello,
I've implemented 'latency' subcommand in the perf ftrace command to
show a histogram of function latency.
v2 changes)
* fix build errors (Arnaldo)
* add Arnaldo's test results in the commit message
* show warning when -b is used and BPF support is not enabled (Athira)
* use skel->links to save bpf links (Song)
To handle new subcommands, the existing functionality is moved to
'trace' subcommand while preserving backward compatibility of not
having a subcommand at all (defaults to 'trace').
The latency subcommand accepts a target (kernel, for now) function
with -T option and shows a histogram like below:
$ sudo ./perf ftrace latency -a -T mutex_lock sleep 1
# DURATION | COUNT | GRAPH |
0 - 1 us | 2686 | ###################### |
1 - 2 us | 976 | ######## |
2 - 4 us | 879 | ####### |
4 - 8 us | 481 | #### |
8 - 16 us | 445 | ### |
16 - 32 us | 1 | |
32 - 64 us | 0 | |
64 - 128 us | 0 | |
128 - 256 us | 0 | |
256 - 512 us | 0 | |
512 - 1024 us | 0 | |
1 - 2 ms | 0 | |
2 - 4 ms | 0 | |
4 - 8 ms | 0 | |
8 - 16 ms | 0 | |
16 - 32 ms | 0 | |
32 - 64 ms | 0 | |
64 - 128 ms | 0 | |
128 - 256 ms | 0 | |
256 - 512 ms | 0 | |
512 - 1024 ms | 0 | |
1 - ... s | 0 | |
It basically use the function graph tracer to extract the duration of
the function. But with -b/--use-bpf option, it can use BPF to save
the histogram in the kernel. For the same function, it gets:
$ sudo ./perf ftrace latency -a -b -T mutex_lock sleep 1
# DURATION | COUNT | GRAPH |
0 - 1 us | 4682 | ############################################# |
1 - 2 us | 11 | |
2 - 4 us | 0 | |
4 - 8 us | 0 | |
8 - 16 us | 7 | |
16 - 32 us | 6 | |
32 - 64 us | 0 | |
64 - 128 us | 0 | |
128 - 256 us | 0 | |
256 - 512 us | 0 | |
512 - 1024 us | 0 | |
1 - 2 ms | 0 | |
2 - 4 ms | 0 | |
4 - 8 ms | 0 | |
8 - 16 ms | 0 | |
16 - 32 ms | 0 | |
32 - 64 ms | 0 | |
64 - 128 ms | 0 | |
128 - 256 ms | 0 | |
256 - 512 ms | 0 | |
512 - 1024 ms | 0 | |
1 - ... s | 0 | |
You can get the patches at 'perf/ftrace-latency-v2' branch on
https://git.kernel.org/pub/scm/linux/kernel/git/namhyung/linux-perf.git
Thanks,
Namhyung
Namhyung Kim (5):
perf ftrace: Add 'trace' subcommand
perf ftrace: Move out common code from __cmd_ftrace
perf ftrace: Add 'latency' subcommand
perf ftrace: Add -b/--use-bpf option for latency subcommand
perf ftrace: Implement cpu and task filters in BPF
tools/perf/Makefile.perf | 2 +-
tools/perf/builtin-ftrace.c | 445 +++++++++++++++++---
tools/perf/util/Build | 1 +
tools/perf/util/bpf_ftrace.c | 152 +++++++
tools/perf/util/bpf_skel/func_latency.bpf.c | 114 +++++
tools/perf/util/ftrace.h | 81 ++++
6 files changed, 725 insertions(+), 70 deletions(-)
create mode 100644 tools/perf/util/bpf_ftrace.c
create mode 100644 tools/perf/util/bpf_skel/func_latency.bpf.c
create mode 100644 tools/perf/util/ftrace.h
base-commit: 8ff4f20f3eb55dea0dbbe5e32043ab6b7427882f
--
2.34.1.173.g76aa8bc2d0-goog
next reply other threads:[~2021-12-15 18:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-15 18:51 Namhyung Kim [this message]
2021-12-15 18:51 ` [PATCH 1/5] perf ftrace: Add 'trace' subcommand Namhyung Kim
2021-12-15 18:51 ` [PATCH 2/5] perf ftrace: Move out common code from __cmd_ftrace Namhyung Kim
2021-12-15 18:51 ` [PATCH 3/5] perf ftrace: Add 'latency' subcommand Namhyung Kim
2021-12-15 18:51 ` [PATCH 4/5] perf ftrace: Add -b/--use-bpf option for latency subcommand Namhyung Kim
2021-12-15 18:51 ` [PATCH 5/5] perf ftrace: Implement cpu and task filters in BPF Namhyung Kim
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=20211215185154.360314-1-namhyung@kernel.org \
--to=namhyung@kernel.org \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=atrajeev@linux.vnet.ibm.com \
--cc=changbin.du@gmail.com \
--cc=eranian@google.com \
--cc=irogers@google.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.