From: Steven Rostedt <rostedt@goodmis.org>
To: Jianfeng Wang <jianfeng.w.wang@oracle.com>
Cc: linux-trace-devel@vger.kernel.org
Subject: Re: [PATCH 2/2] trace-cmd: Add ftrace options with fgraph retval option
Date: Fri, 17 May 2024 15:00:37 -0400 [thread overview]
Message-ID: <20240517150037.5db93c4d@gandalf.local.home> (raw)
In-Reply-To: <a40c7f16-d3fd-4a30-987c-7a7d418ea5f3@oracle.com>
On Fri, 17 May 2024 11:50:29 -0700
Jianfeng Wang <jianfeng.w.wang@oracle.com> wrote:
> > Honestly, I don't think this should be an option. Or if it is, it
> > should be default on. If the retval exists in the trace, it should just
> > be printed. Why ask the user to show it when they spent the time to
> > enable it in the recording?
> >
>
> I make it a default-off option because the feature changes the output format of
> the 'trace-cmd report'. So to be on the safe side, keep the original format by
> default. Also, the kernel has options (i.e., options/funcgraph-retval and
> options/funcgraph-retval-hex) to enable printing functions' retval in trace.log
>
> >From my point of view, I'd like to see the retval on by default. If you are
> okay, I'd like to make it default on and add an option to display retval in hex.
Yeah, we can keep both as an option, but make the retval default on.
It will not change default behavior, as it should only be shown if retval
was recorded in the first place. If it wasn't recorded, the behavior should
be the same regardless of if the retval option is enabled or not in the
trace-cmd output.
-- Steve
next prev parent reply other threads:[~2024-05-17 19:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-15 15:49 [PATCH 0/2] trace-cmd ftrace: support function retval feature in function_graph Jianfeng Wang
2024-04-15 15:49 ` [PATCH 1/2] trace-cmd ftrace: print function retval " 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 [this message]
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=20240517150037.5db93c4d@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=jianfeng.w.wang@oracle.com \
--cc=linux-trace-devel@vger.kernel.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).