linux-trace-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jianfeng Wang <jianfeng.w.wang@oracle.com>
To: linux-trace-devel@vger.kernel.org
Cc: rostedt@goodmis.org, jianfeng.w.wang@oracle.com
Subject: [PATCH v3 0/2] trace-cmd report: support function retval in function_graph
Date: Wed, 17 Jul 2024 16:17:01 -0700	[thread overview]
Message-ID: <20240717231703.46744-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 three fgraph options so that users can skip
the printing, and force the return values to be printed in decimal
or in hex format.

Change history:
===============
v3:
- Fix code format.
- Add fgraph:retval-dec option.

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 report: Print function retval in function_graph
  trace-cmd report: Add options for the fgraph retval feature

 lib/trace-cmd/trace-ftrace.c | 72 ++++++++++++++++++++++++++++++++++++
 1 file changed, 72 insertions(+)

-- 
2.42.1


             reply	other threads:[~2024-07-17 23:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-17 23:17 Jianfeng Wang [this message]
2024-07-17 23:17 ` [PATCH v3 1/2] trace-cmd report: Print function retval in function_graph Jianfeng Wang
2024-07-17 23:17 ` [PATCH v3 2/2] trace-cmd report: Add options for the fgraph retval feature Jianfeng Wang

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=20240717231703.46744-1-jianfeng.w.wang@oracle.com \
    --to=jianfeng.w.wang@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).