From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Ingo Molnar <mingo@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Jiri Olsa <jolsa@kernel.org>, Ian Rogers <irogers@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
Kan Liang <kan.liang@linux.intel.com>,
Clark Williams <williams@redhat.com>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Gabriele Monaco <gmonaco@redhat.com>
Subject: [PATCH 0/4 perf-tools-next] perf ftrace latency linear buckets
Date: Tue, 12 Nov 2024 15:12:10 -0300 [thread overview]
Message-ID: <20241112181214.1171244-1-acme@kernel.org> (raw)
From: Arnaldo Carvalho de Melo <acme@redhat.com>
Hi,
Gabriele has been using 'perf ftrace latency' in some
investigations at work and wanted to have an alternative way of
populating the buckets, so we came up with this series, please take a
look at the examples provided in the changesets.
Thanks,
- Arnaldo
Arnaldo Carvalho de Melo (3):
perf ftrace latency: Pass ftrace pointer to histogram routines to pass more args
perf ftrace latency: Introduce --bucket-range to ask for linear bucketing
perf ftrace latency: Introduce --min-latency to narrow down into a latency range
Gabriele Monaco (1):
perf ftrace latency: Add --max-latency option
tools/perf/Documentation/perf-ftrace.txt | 11 ++
tools/perf/builtin-ftrace.c | 131 ++++++++++++++++----
tools/perf/util/bpf_ftrace.c | 3 +
tools/perf/util/bpf_skel/func_latency.bpf.c | 26 +++-
tools/perf/util/ftrace.h | 3 +
5 files changed, 150 insertions(+), 24 deletions(-)
--
2.47.0
next reply other threads:[~2024-11-12 18:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-12 18:12 Arnaldo Carvalho de Melo [this message]
2024-11-12 18:12 ` [PATCH 1/4] perf ftrace latency: Pass ftrace pointer to histogram routines to pass more args Arnaldo Carvalho de Melo
2024-11-12 18:12 ` [PATCH 2/4] perf ftrace latency: Introduce --bucket-range to ask for linear bucketing Arnaldo Carvalho de Melo
2024-11-12 18:12 ` [PATCH 3/4] perf ftrace latency: Introduce --min-latency to narrow down into a latency range Arnaldo Carvalho de Melo
2024-11-12 18:12 ` [PATCH 4/4] perf ftrace latency: Add --max-latency option Arnaldo Carvalho de Melo
2024-12-10 18:17 ` [PATCH 0/4 perf-tools-next] perf ftrace latency linear buckets Arnaldo Carvalho de Melo
2024-12-11 19:58 ` 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=20241112181214.1171244-1-acme@kernel.org \
--to=acme@kernel.org \
--cc=acme@redhat.com \
--cc=adrian.hunter@intel.com \
--cc=gmonaco@redhat.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=tglx@linutronix.de \
--cc=williams@redhat.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).