From: Howard Chu <howardchu95@gmail.com>
To: acme@kernel.org
Cc: namhyung@kernel.org, mark.rutland@arm.com,
alexander.shishkin@linux.intel.com, jolsa@kernel.org,
irogers@google.com, adrian.hunter@intel.com,
kan.liang@linux.intel.com, linux-perf-users@vger.kernel.org,
linux-kernel@vger.kernel.org, Howard Chu <howardchu95@gmail.com>
Subject: [PATCH v3 0/2] perf trace: Add more tests for BTF-augmented perf trace
Date: Wed, 11 Dec 2024 14:49:25 -0800 [thread overview]
Message-ID: <20241211224927.968483-1-howardchu95@gmail.com> (raw)
Changes in v3:
- Add vmlinux BTF check, and skip the tests if it doesn't exist
v1, v2:
The previous version of the perf trace BTF general augmentation tests
didn't pass Shellcheck (thanks to Arnaldo Carvalho de Melo
<acme@kernel.org> for pointing this out), this version uses bash instead
of POSIX shell to pass Shellcheck.
This patch series also adds documentation for the new option
--force-btf, which is used in the tests.
Link: https://lore.kernel.org/linux-perf-users/Zt9yiQq-n-W6I274@x1/
Howard Chu (2):
perf trace: Add tests for BTF general augmentation
perf docs: Add documentation for --force-btf option
tools/perf/Documentation/perf-trace.txt | 5 ++
tools/perf/tests/shell/trace_btf_general.sh | 93 +++++++++++++++++++++
2 files changed, 98 insertions(+)
create mode 100755 tools/perf/tests/shell/trace_btf_general.sh
--
2.43.0
next reply other threads:[~2024-12-11 22:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-11 22:49 Howard Chu [this message]
2024-12-11 22:49 ` [PATCH v3 1/2] perf trace: Add tests for BTF general augmentation Howard Chu
2024-12-14 0:42 ` Namhyung Kim
2024-12-15 6:57 ` Howard Chu
2024-12-11 22:49 ` [PATCH v3 2/2] perf docs: Add documentation for --force-btf option 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=20241211224927.968483-1-howardchu95@gmail.com \
--to=howardchu95@gmail.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.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=mark.rutland@arm.com \
--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