From: Yang Jihong <yangjihong1@huawei.com>
To: <peterz@infradead.org>, <mingo@redhat.com>, <acme@kernel.org>,
<mark.rutland@arm.com>, <alexander.shishkin@linux.intel.com>,
<jolsa@kernel.org>, <namhyung@kernel.org>, <ast@kernel.org>,
<daniel@iogearbox.net>, <andrii@kernel.org>, <kafai@fb.com>,
<songliubraving@fb.com>, <yhs@fb.com>, <john.fastabend@gmail.com>,
<kpsingh@kernel.org>, <irogers@google.com>,
<davemarchevsky@fb.com>, <adrian.hunter@intel.com>,
<alexandre.truong@arm.com>, <linux-kernel@vger.kernel.org>,
<linux-perf-users@vger.kernel.org>, <netdev@vger.kernel.org>,
<bpf@vger.kernel.org>
Cc: <yangjihong1@huawei.com>
Subject: [RFC v2 02/17] perf kwork: Add irq kwork record support
Date: Fri, 24 Jun 2022 22:03:34 +0800 [thread overview]
Message-ID: <20220624140349.16964-3-yangjihong1@huawei.com> (raw)
In-Reply-To: <20220624140349.16964-1-yangjihong1@huawei.com>
Record interrupt events irq:irq_handler_entry & irq_handler_exit
Test cases:
# perf kwork record -o perf_kwork.date -- sleep 1
[ perf record: Woken up 0 times to write data ]
[ perf record: Captured and wrote 0.556 MB perf_kwork.date ]
#
# perf evlist -i perf_kwork.date
irq:irq_handler_entry
irq:irq_handler_exit
dummy:HG
# Tip: use 'perf evlist --trace-fields' to show fields for tracepoint events
#
Signed-off-by: Yang Jihong <yangjihong1@huawei.com>
---
tools/perf/Documentation/perf-kwork.txt | 2 +-
tools/perf/builtin-kwork.c | 15 ++++++++++++++-
tools/perf/util/kwork.h | 1 +
3 files changed, 16 insertions(+), 2 deletions(-)
diff --git a/tools/perf/Documentation/perf-kwork.txt b/tools/perf/Documentation/perf-kwork.txt
index dc1e36da57bb..57bd5fa7d5c9 100644
--- a/tools/perf/Documentation/perf-kwork.txt
+++ b/tools/perf/Documentation/perf-kwork.txt
@@ -32,7 +32,7 @@ OPTIONS
-k::
--kwork::
- List of kwork to profile
+ List of kwork to profile (irq, etc)
-v::
--verbose::
diff --git a/tools/perf/builtin-kwork.c b/tools/perf/builtin-kwork.c
index f3552c56ede3..a26b7fde1e38 100644
--- a/tools/perf/builtin-kwork.c
+++ b/tools/perf/builtin-kwork.c
@@ -25,7 +25,20 @@
#include <linux/time64.h>
#include <linux/zalloc.h>
+const struct evsel_str_handler irq_tp_handlers[] = {
+ { "irq:irq_handler_entry", NULL, },
+ { "irq:irq_handler_exit", NULL, },
+};
+
+static struct kwork_class kwork_irq = {
+ .name = "irq",
+ .type = KWORK_CLASS_IRQ,
+ .nr_tracepoints = 2,
+ .tp_handlers = irq_tp_handlers,
+};
+
static struct kwork_class *kwork_class_supported_list[KWORK_CLASS_MAX] = {
+ [KWORK_CLASS_IRQ] = &kwork_irq,
};
static void setup_event_list(struct perf_kwork *kwork,
@@ -132,7 +145,7 @@ int cmd_kwork(int argc, const char **argv)
OPT_BOOLEAN('D', "dump-raw-trace", &dump_trace,
"dump raw trace in ASCII"),
OPT_STRING('k', "kwork", &kwork.event_list_str, "kwork",
- "list of kwork to profile"),
+ "list of kwork to profile (irq, etc)"),
OPT_BOOLEAN('f', "force", &kwork.force, "don't complain, do it"),
OPT_END()
};
diff --git a/tools/perf/util/kwork.h b/tools/perf/util/kwork.h
index 6950636aab2a..f1d89cb058fc 100644
--- a/tools/perf/util/kwork.h
+++ b/tools/perf/util/kwork.h
@@ -13,6 +13,7 @@
#include <linux/bitmap.h>
enum kwork_class_type {
+ KWORK_CLASS_IRQ,
KWORK_CLASS_MAX,
};
--
2.30.GIT
next prev parent reply other threads:[~2022-06-24 14:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-24 14:03 [RFC v2 00/17] perf: Add perf kwork Yang Jihong
2022-06-24 14:03 ` [RFC v2 01/17] perf kwork: New tool Yang Jihong
2022-06-24 14:03 ` Yang Jihong [this message]
2022-06-24 14:03 ` [RFC v2 03/17] perf kwork: Add softirq kwork record support Yang Jihong
2022-06-24 14:03 ` [RFC v2 04/17] perf kwork: Add workqueue " Yang Jihong
2022-06-24 14:03 ` [RFC v2 05/17] tools lib: Add list_last_entry_or_null Yang Jihong
2022-06-24 14:03 ` [RFC v2 06/17] perf kwork: Implement perf kwork report Yang Jihong
2022-06-24 14:03 ` [RFC v2 07/17] perf kwork: Add irq report support Yang Jihong
2022-06-24 14:03 ` [RFC v2 08/17] perf kwork: Add softirq " Yang Jihong
2022-06-24 14:03 ` [RFC v2 09/17] perf kwork: Add workqueue " Yang Jihong
2022-06-24 14:03 ` [RFC v2 10/17] perf kwork: Implement perf kwork latency Yang Jihong
2022-06-24 14:03 ` [RFC v2 11/17] perf kwork: Add softirq latency support Yang Jihong
2022-06-24 14:03 ` [RFC v2 12/17] perf kwork: Add workqueue " Yang Jihong
2022-06-24 14:03 ` [RFC v2 13/17] perf kwork: Implement perf kwork timehist Yang Jihong
2022-06-24 14:03 ` [RFC v2 14/17] perf kwork: Implement bpf trace Yang Jihong
2022-06-24 14:03 ` [RFC v2 15/17] perf kwork: Add irq trace bpf support Yang Jihong
2022-06-24 14:03 ` [RFC v2 16/17] perf kwork: Add softirq " Yang Jihong
2022-06-24 14:03 ` [RFC v2 17/17] perf kwork: Add workqueue " Yang Jihong
2022-07-02 9:35 ` [RFC v2 00/17] perf: Add perf kwork Yang Jihong
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=20220624140349.16964-3-yangjihong1@huawei.com \
--to=yangjihong1@huawei.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=alexandre.truong@arm.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davemarchevsky@fb.com \
--cc=irogers@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=songliubraving@fb.com \
--cc=yhs@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).