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 0/2] trace-cmd ftrace: support function retval feature in function_graph
Date: Mon, 15 Apr 2024 08:49:19 -0700	[thread overview]
Message-ID: <20240415154921.4998-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 feature can be
useful for debugging kernel problems, such as root cause
analysis for syscall errors.

This patch series is to utilize this feature to support
printing each function's return value in 'trace-cmd report'.
The default is off. Add a ftrace internal option so that
users can turn this feature on if they'd like to request for
the retval information in the function_graph tracer.

Jianfeng Wang (2):
  trace-cmd ftrace: print function retval in function_graph
  trace-cmd: Add ftrace options with fgraph retval option

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

-- 
2.42.1


             reply	other threads:[~2024-04-15 15:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-15 15:49 Jianfeng Wang [this message]
2024-04-15 15:49 ` [PATCH 1/2] trace-cmd ftrace: print function retval in function_graph Jianfeng Wang
2024-04-15 15:49 ` [PATCH 2/2] trace-cmd: Add ftrace options with fgraph retval option Jianfeng Wang
2024-04-30 22:45   ` Jianfeng Wang
2024-04-30 23:06     ` Steven Rostedt
2024-05-17  0:53   ` Steven Rostedt
2024-05-17 18:50     ` Jianfeng Wang
2024-05-17 19:00       ` Steven Rostedt
2024-05-17 19:23         ` [External] : " 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=20240415154921.4998-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).