From: Howard Chu <howardchu95@gmail.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
Ian Rogers <irogers@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
Kan Liang <kan.liang@linux.intel.com>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org
Subject: [PATCH v2 0/5] perf trace: Augment enum arguments with BTF
Date: Wed, 19 Jun 2024 16:20:37 +0800 [thread overview]
Message-ID: <20240619082042.4173621-1-howardchu95@gmail.com> (raw)
changes in v2:
- Move inline landlock_add_rule c code to tests/workloads
- Rename 'enum_aug_prereq' to 'check_vmlinux'
Augment enum arguments in perf trace, including syscall arguments and
non-syscall tracepoint arguments. The augmentation is implemented using
BTF.
This patch series also includes a bug fix by Arnaldo Carvalho de Melo
<acme@redhat.com>, which makes more syscalls to be traceable by perf trace.
Test is included.
Howard Chu (5):
perf trace: Fix iteration of syscall ids in syscalltbl->entries
perf trace: Augment enum syscall arguments with BTF
perf trace: Augment enum tracepoint arguments with BTF
perf trace: Filter enum arguments with enum names
perf trace: Add test for enum augmentation
tools/perf/builtin-trace.c | 214 ++++++++++++++++--
tools/perf/tests/builtin-test.c | 1 +
tools/perf/tests/shell/trace_btf_enum.sh | 57 +++++
tools/perf/tests/tests.h | 1 +
tools/perf/tests/workloads/Build | 1 +
.../perf/tests/workloads/landlock_add_rule.c | 32 +++
tools/perf/util/syscalltbl.c | 7 +
tools/perf/util/syscalltbl.h | 1 +
8 files changed, 289 insertions(+), 25 deletions(-)
create mode 100755 tools/perf/tests/shell/trace_btf_enum.sh
create mode 100644 tools/perf/tests/workloads/landlock_add_rule.c
--
2.45.2
next reply other threads:[~2024-06-19 8:19 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-19 8:20 Howard Chu [this message]
2024-06-19 8:20 ` [PATCH v2 1/5] perf trace: Fix iteration of syscall ids in syscalltbl->entries Howard Chu
2024-06-19 8:20 ` [PATCH v2 2/5] perf trace: Augment enum syscall arguments with BTF Howard Chu
2024-06-19 13:44 ` Arnaldo Carvalho de Melo
2024-06-19 17:59 ` Howard Chu
2024-06-20 16:34 ` Howard Chu
2024-06-20 19:16 ` Howard Chu
2024-06-21 13:40 ` Arnaldo Carvalho de Melo
2024-06-21 16:18 ` Howard Chu
2024-06-22 18:28 ` Arnaldo Carvalho de Melo
2024-06-23 11:34 ` Howard Chu
2024-06-21 18:03 ` Arnaldo Carvalho de Melo
2024-06-19 8:20 ` [PATCH v2 3/5] perf trace: Augment enum tracepoint " Howard Chu
2024-06-19 13:46 ` Arnaldo Carvalho de Melo
2024-06-19 18:00 ` Howard Chu
2024-06-19 8:20 ` [PATCH v2 4/5] perf trace: Filter enum arguments with enum names Howard Chu
2024-06-19 13:48 ` Arnaldo Carvalho de Melo
2024-06-19 18:18 ` Howard Chu
2024-06-19 8:20 ` [PATCH v2 5/5] perf trace: Add test for enum augmentation Howard Chu
2024-06-19 13:51 ` Arnaldo Carvalho de Melo
2024-06-19 14:36 ` Namhyung Kim
2024-06-19 18:26 ` Howard Chu
2024-06-21 16:07 ` Namhyung Kim
2024-06-21 16:43 ` Howard Chu
2024-06-21 17:15 ` Namhyung Kim
2024-06-28 6:37 ` kernel test robot
2024-06-19 13:55 ` [PATCH v2 0/5] perf trace: Augment enum arguments with BTF Arnaldo Carvalho de Melo
2024-06-19 18:19 ` Namhyung Kim
2024-06-19 18:25 ` Howard Chu
2024-06-20 19:12 ` Howard Chu
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=20240619082042.4173621-1-howardchu95@gmail.com \
--to=howardchu95@gmail.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.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=namhyung@kernel.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
all inboxes | Powered by JetHome®