From: Howard Chu <howardchu95@gmail.com>
To: peterz@infradead.org
Cc: mingo@redhat.com, acme@kernel.org, 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 v1 0/2] perf trace: Add tests for BTF general augmentation
Date: Fri, 22 Nov 2024 16:55:09 -0800 [thread overview]
Message-ID: <20241123005512.342079-1-howardchu95@gmail.com> (raw)
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 | 3 +
tools/perf/tests/shell/trace_btf_general.sh | 68 +++++++++++++++++++++
2 files changed, 71 insertions(+)
create mode 100755 tools/perf/tests/shell/trace_btf_general.sh
--
2.43.0
next reply other threads:[~2024-11-23 0:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-23 0:55 Howard Chu [this message]
2024-11-23 0:55 ` [PATCH v1 1/2] " Howard Chu
2024-11-23 0:58 ` Howard Chu
2024-11-26 16:41 ` Arnaldo Carvalho de Melo
2024-11-26 16:49 ` Arnaldo Carvalho de Melo
2024-11-26 17:12 ` Arnaldo Carvalho de Melo
2024-11-26 17:45 ` Howard Chu
2024-11-23 0:55 ` [PATCH v1 2/2] perf docs: Add documentation for --force-btf option Howard Chu
2024-11-26 17:14 ` Arnaldo Carvalho de Melo
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=20241123005512.342079-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=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.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®