From: Steven Rostedt <rostedt@goodmis.org>
To: Mark Brown <broonie@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
bpf@vger.kernel.org, Masami Hiramatsu <mhiramat@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Andrew Morton <akpm@linux-foundation.org>,
Sven Schnelle <svens@linux.ibm.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>, Guo Ren <guoren@kernel.org>,
Donglin Peng <dolinux.peng@gmail.com>,
Zheng Yejian <zhengyejian@huaweicloud.com>,
Aishwarya.TCV@arm.com
Subject: Re: [PATCH v4 2/4] ftrace: Add support for function argument to graph tracer
Date: Fri, 11 Apr 2025 13:02:00 -0400 [thread overview]
Message-ID: <20250411130200.76b52a61@gandalf.local.home> (raw)
In-Reply-To: <20250411124849.30d612ed@gandalf.local.home>
On Fri, 11 Apr 2025 12:48:49 -0400
Steven Rostedt <rostedt@goodmis.org> wrote:
> On Fri, 11 Apr 2025 12:45:52 -0400
> Steven Rostedt <rostedt@goodmis.org> wrote:
>
> > Also, is it possible to just enable function_graph tarcing and see if it
> > adds these blank lines between events?
>
> Never mind. When I enable the funcgraph-retval option, I get the blank
> lines too.
>
> There's likely an added '\n' that shouldn't be. Let me go look.
>
Found it, and yes it is the commit you bisected it to:
It added a '\n' when the retval option would print one too.
This should fix it:
diff --git a/kernel/trace/trace_functions_graph.c b/kernel/trace/trace_functions_graph.c
index 2f077d4158e5..718f6e84cc83 100644
--- a/kernel/trace/trace_functions_graph.c
+++ b/kernel/trace/trace_functions_graph.c
@@ -971,11 +971,10 @@ print_graph_entry_leaf(struct trace_iterator *iter,
if (args_size >= FTRACE_REGS_MAX_ARGS * sizeof(long)) {
print_function_args(s, entry->args, ret_func);
- trace_seq_putc(s, ';');
+ trace_seq_puts(s, ";\n");
} else
- trace_seq_puts(s, "();");
+ trace_seq_puts(s, "();\n");
}
- trace_seq_printf(s, "\n");
print_graph_irq(iter, graph_ret->func, TRACE_GRAPH_RET,
cpu, iter->ent->pid, flags);
-- Steve
next prev parent reply other threads:[~2025-04-11 17:00 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-27 18:58 [PATCH v4 0/4] ftrace: Add function arguments to function tracers Steven Rostedt
2025-02-27 18:58 ` [PATCH v4 1/4] ftrace: Add print_function_args() Steven Rostedt
2025-02-27 18:58 ` [PATCH v4 2/4] ftrace: Add support for function argument to graph tracer Steven Rostedt
2025-04-09 22:34 ` Mark Brown
2025-04-10 17:17 ` Steven Rostedt
2025-04-11 13:00 ` Mark Brown
2025-04-11 16:45 ` Steven Rostedt
2025-04-11 16:48 ` Steven Rostedt
2025-04-11 17:02 ` Steven Rostedt [this message]
2025-04-11 17:33 ` Steven Rostedt
2025-04-11 16:58 ` Mark Brown
2025-04-11 17:12 ` Steven Rostedt
2025-04-11 17:39 ` Mark Brown
2025-04-11 18:16 ` Mark Brown
2025-04-11 18:24 ` Steven Rostedt
2025-04-11 18:29 ` Mark Brown
2025-04-11 18:31 ` Steven Rostedt
2025-04-11 19:13 ` Steven Rostedt
2025-04-11 19:26 ` Steven Rostedt
2025-04-11 19:27 ` Steven Rostedt
2025-04-14 3:00 ` Masami Hiramatsu
2025-04-14 3:08 ` Masami Hiramatsu
2025-04-14 13:31 ` Steven Rostedt
2025-04-15 17:40 ` Steven Rostedt
2025-08-09 2:24 ` Sasha Levin
2025-08-13 23:53 ` Steven Rostedt
2025-08-14 17:05 ` Sasha Levin
2025-08-19 22:21 ` Steven Rostedt
2025-02-27 18:58 ` [PATCH v4 3/4] ftrace: Have funcgraph-args take affect during tracing Steven Rostedt
2025-02-27 18:58 ` [PATCH v4 4/4] ftrace: Add arguments to function tracer 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=20250411130200.76b52a61@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=Aishwarya.TCV@arm.com \
--cc=akpm@linux-foundation.org \
--cc=aou@eecs.berkeley.edu \
--cc=bpf@vger.kernel.org \
--cc=broonie@kernel.org \
--cc=dolinux.peng@gmail.com \
--cc=guoren@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=svens@linux.ibm.com \
--cc=zhengyejian@huaweicloud.com \
/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).