From: "Steven Rostedt (VMware)" <rostedt@xxxxxxxxxxx>
The current man page and usage of trace-cmd report is confusing when it
comes to the -f option. This option will list all the functions in the
trace.dat file that have a address to name mapping. As it currently is
stated, it may confuse users in thinking that it will list the functions
that have been traced. But this is not the case.
Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=207069
Signed-off-by: Steven Rostedt (VMware) <rostedt@xxxxxxxxxxx>
---
Documentation/trace-cmd-report.1.txt | 4 +++-
tracecmd/trace-usage.c | 2 +-
2 files changed, 4 insertions(+), 2 deletions(-)
diff --git a/Documentation/trace-cmd-report.1.txt b/Documentation/trace-cmd-report.1.txt
index 87f4d7a1b046..66e96da7c3fa 100644
--- a/Documentation/trace-cmd-report.1.txt
+++ b/Documentation/trace-cmd-report.1.txt
@@ -27,7 +27,9 @@ OPTIONS
versa.
*-f*::
- This outputs the list of functions that have been recorded in the file.
+ This outputs the list of all functions that have been mapped in the trace.dat file.
+ Note, this list may contain functions that may not appear in the trace, as
+ it is the list of mappings to translate function addresses into function names.
*-P*::
This outputs the list of "trace_printk()" data. The raw trace data points
diff --git a/tracecmd/trace-usage.c b/tracecmd/trace-usage.c
index ada44c68eb00..85c635125617 100644
--- a/tracecmd/trace-usage.c
+++ b/tracecmd/trace-usage.c
@@ -191,7 +191,7 @@ static struct usage_help usage_help[] = {
" [-G]\n"
" -i input file [default trace.dat]\n"
" -e show file endianess\n"
- " -f show function list\n"
+ " -f show function mapping list\n"
" -P show printk list\n"
" -E show event files stored\n"
" -F filter to filter output on\n"
--
2.26.2
|