public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Pavel Skripkin <paskripkin@gmail.com>
To: sjg@chromium.org, u-boot@lists.denx.de
Cc: Pavel Skripkin <paskripkin@gmail.com>
Subject: [PATCH] docs: fix wrong proftool usage
Date: Wed, 12 Apr 2023 22:05:31 +0300	[thread overview]
Message-ID: <20230412190531.160574-1-paskripkin@gmail.com> (raw)

Guide shows incorrect usage of proftool, which is confusing. If proftool
is used w/o '-o' argument it complains like following

$ ./sandbox/tools/proftool -m sandbox/System.map -t trace dump-ftrace > trace.dat
Must provide trace data, System.map file and output file
Usage: proftool [-cmtv] <cmd> <profdata>

s/>/-o/ fixes it and proftool outputs decoded data to trace.dat

Signed-off-by: Pavel Skripkin <paskripkin@gmail.com>
---
 doc/develop/trace.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/develop/trace.rst b/doc/develop/trace.rst
index 8425d843e9..9bbe1345d2 100644
--- a/doc/develop/trace.rst
+++ b/doc/develop/trace.rst
@@ -100,7 +100,7 @@ Then run proftool to convert the trace information to ftrace format
 
 .. code-block:: console
 
-    $ ./sandbox/tools/proftool -m sandbox/System.map -t trace dump-ftrace >trace.dat
+    $ ./sandbox/tools/proftool -m sandbox/System.map -t trace dump-ftrace -o trace.dat
 
 Finally run kernelshark to display it (note it only works with `.dat` files!):
 
-- 
2.39.2


             reply	other threads:[~2023-04-13 14:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-12 19:05 Pavel Skripkin [this message]
2023-04-19  1:45 ` [PATCH] docs: fix wrong proftool usage Simon Glass
2023-04-25 13:41   ` Pavel Skripkin
2023-04-25 13:58     ` Tom Rini

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=20230412190531.160574-1-paskripkin@gmail.com \
    --to=paskripkin@gmail.com \
    --cc=sjg@chromium.org \
    --cc=u-boot@lists.denx.de \
    /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