From: Jianfeng Wang <jianfeng.w.wang@oracle.com>
To: linux-trace-devel@vger.kernel.org
Cc: rostedt@goodmis.org, jianfeng.w.wang@oracle.com, junxiao.bi@oracle.com
Subject: [PATCH v2 0/2] trace-cmd ftrace: support function retval feature in function_graph
Date: Tue, 21 May 2024 14:37:28 -0700 [thread overview]
Message-ID: <20240521213730.67993-1-jianfeng.w.wang@oracle.com> (raw)
The upstream Linux kernel has introduced a funcgraph retval feature
for the function_graph tracer. (Commit ID:
a1be9ccc57f07d54278be34eed6bd679bc941c97). This patchset is to utilize
this feature to support printing each function's return value in
'trace-cmd report'. Add two fgraph options so that users can skip
the printing or force the return values to be printed in hex.
Change history:
===============
v2:
- Check if a retval is an error code: if not, print it in hex.
- Make this retval feature on by default.
- Add fgraph:retval-skip and fgraph:retval-hex options.
v1: https://lore.kernel.org/linux-trace-devel/20240415154921.4998-1-jianfeng.w.wang@oracle.com
Jianfeng Wang (2):
trace-cmd ftrace: print function retval in function_graph
trace-cmd: Add ftrace options for the fgraph retval feature
lib/trace-cmd/trace-ftrace.c | 51 ++++++++++++++++++++++++++++++++++++
1 file changed, 51 insertions(+)
--
2.42.1
next reply other threads:[~2024-05-21 21:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-21 21:37 Jianfeng Wang [this message]
2024-05-21 21:37 ` [PATCH v2 1/2] trace-cmd ftrace: print function retval in function_graph Jianfeng Wang
2024-07-17 18:48 ` Steven Rostedt
2024-05-21 21:37 ` [PATCH v2 2/2] trace-cmd: Add ftrace options for the fgraph retval feature Jianfeng Wang
2024-07-17 18:50 ` Steven Rostedt
2024-07-17 20:44 ` Jianfeng Wang
2024-07-17 20:58 ` Steven Rostedt
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=20240521213730.67993-1-jianfeng.w.wang@oracle.com \
--to=jianfeng.w.wang@oracle.com \
--cc=junxiao.bi@oracle.com \
--cc=linux-trace-devel@vger.kernel.org \
--cc=rostedt@goodmis.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;
as well as URLs for NNTP newsgroup(s).