From: "Masami Hiramatsu (Google)" <mhiramat@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org
Subject: [PATCH v2 0/2] tracing: Add an option to show symbols in _text+offset for function profiler
Date: Mon, 22 Sep 2025 21:46:02 +0900 [thread overview]
Message-ID: <175854516202.353182.1216978967046454932.stgit@devnote2> (raw)
Hi,
This series implements an option to show symbols in _text+OFFSET
format instead of symbol name in the function profiler.
This is the 2nd version, the 1st one is here;
https://lore.kernel.org/all/175826135058.101165.7219957344129610147.stgit@devnote2/
This version adds a patch to expand the trace_iterator_flag flag
bits to 64 bits [1/2] because there is already 32 flags and no space
to add a new flag. Also, add a dummy TRACE_ITER_PROF_TEXT_OFFSET to
fix a compliation error if CONFIG_FUNCTION_PROFILER=n.
Thank you,
---
Masami Hiramatsu (Google) (2):
tracing: Allow tracer to add more than 32 options
tracing: Add an option to show symbols in _text+offset for function profiler
kernel/trace/ftrace.c | 26 ++++++++++
kernel/trace/trace.c | 24 +++++-----
kernel/trace/trace.h | 92 +++++++++++++++++++++----------------
kernel/trace/trace_irqsoff.c | 2 -
kernel/trace/trace_sched_wakeup.c | 2 -
5 files changed, 91 insertions(+), 55 deletions(-)
--
Masami Hiramatsu (Google) <mhiramat@kernel.org>
next reply other threads:[~2025-09-22 12:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-22 12:46 Masami Hiramatsu (Google) [this message]
2025-09-22 12:46 ` [PATCH v2 1/2] tracing: Allow tracer to add more than 32 options Masami Hiramatsu (Google)
2025-09-23 1:47 ` kernel test robot
2025-09-23 2:25 ` Masami Hiramatsu
2025-09-22 12:46 ` [PATCH v2 2/2] tracing: Add an option to show symbols in _text+offset for function profiler Masami Hiramatsu (Google)
2025-09-23 2:32 ` kernel test robot
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=175854516202.353182.1216978967046454932.stgit@devnote2 \
--to=mhiramat@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=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).