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 2/2] perf docs: Add documentation for --force-btf option
Date: Fri, 22 Nov 2024 16:55:11 -0800 [thread overview]
Message-ID: <20241123005512.342079-3-howardchu95@gmail.com> (raw)
In-Reply-To: <20241123005512.342079-1-howardchu95@gmail.com>
The --force-btf option is intended for debugging purposes and is
currently undocumented. Add documentation for it.
Signed-off-by: Howard Chu <howardchu95@gmail.com>
---
tools/perf/Documentation/perf-trace.txt | 3 +++
1 file changed, 3 insertions(+)
diff --git a/tools/perf/Documentation/perf-trace.txt b/tools/perf/Documentation/perf-trace.txt
index 6e0cc50bbc13..529081599cc7 100644
--- a/tools/perf/Documentation/perf-trace.txt
+++ b/tools/perf/Documentation/perf-trace.txt
@@ -241,6 +241,9 @@ the thread executes on the designated CPUs. Default is to monitor all CPUs.
printing using the existing 'perf trace' syscall arg beautifiers to map integer
arguments to strings (pid to comm, syscall id to syscall name, etc).
+--force-btf::
+ Use btf_dump to pretty print syscall argument data, instead of using hand-crafted pretty printers.
+
PAGEFAULTS
----------
--
2.43.0
next prev parent 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 [PATCH v1 0/2] perf trace: Add tests for BTF general augmentation Howard Chu
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 ` Howard Chu [this message]
2024-11-26 17:14 ` [PATCH v1 2/2] perf docs: Add documentation for --force-btf option 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-3-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®