From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Andrew Morton <akpm@linux-foundation.org>,
Jiri Olsa <olsajiri@gmail.com>
Subject: [PATCH 0/3] fgraph: Do not save calltime in shadow stack
Date: Sat, 14 Sep 2024 17:48:05 -0400 [thread overview]
Message-ID: <20240914214805.779822616@goodmis.org> (raw)
Now that there's more users of the function graph infrastructure, the
calltime field on the shadow stack wastes space and also getting the
timestamp is a waste of time for those that do not use it.
Instead, have the only two users of it (function graph tracer and the
profiler) store it in its own shadow stack variable.
Steven Rostedt (3):
fgraph: Use fgraph data to store subtime for profiler
ftrace: Use a running sleeptime instead of saving in shadow stack
ftrace: Have calltime be saved in the fgraph storage
----
include/linux/ftrace.h | 5 +--
include/linux/sched.h | 1 +
kernel/trace/fgraph.c | 85 +++++++++++++++++++++---------------
kernel/trace/ftrace.c | 45 +++++++++++++------
kernel/trace/trace.h | 1 +
kernel/trace/trace_functions_graph.c | 52 +++++++++++++++++++++-
6 files changed, 137 insertions(+), 52 deletions(-)
next reply other threads:[~2024-09-14 21:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-14 21:48 Steven Rostedt [this message]
2024-09-14 21:48 ` [PATCH 1/3] fgraph: Use fgraph data to store subtime for profiler Steven Rostedt
2024-09-14 21:48 ` [PATCH 2/3] ftrace: Use a running sleeptime instead of saving on shadow stack Steven Rostedt
2024-09-14 21:48 ` [PATCH 3/3] ftrace: Have calltime be saved in the fgraph storage Steven Rostedt
2024-09-15 5:22 ` [PATCH 0/3] fgraph: Do not save calltime in shadow stack Masami Hiramatsu
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=20240914214805.779822616@goodmis.org \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.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=olsajiri@gmail.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).