From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: "Masami Hiramatsu (Google)" <mhiramat@kernel.org>
Cc: Steven Rostedt <rostedt@goodmis.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: Re: [PATCH v5 0/2] tracing: Add an option to show symbols in _text+offset for function profiler
Date: Thu, 30 Oct 2025 12:29:01 +0900 [thread overview]
Message-ID: <20251030122901.46a51bfe643daa9910ad4110@kernel.org> (raw)
In-Reply-To: <176179330871.957820.2367690308433599462.stgit@devnote2>
Oops, I missed to update the version in the subject. Let me update it.
On Thu, 30 Oct 2025 12:01:48 +0900
"Masami Hiramatsu (Google)" <mhiramat@kernel.org> wrote:
> Hi,
>
> This series implements an option to show symbols in _text+OFFSET
> format instead of symbol name in the function profiler.
> This is the 6th version, the previous one is here;
>
> https://lore.kernel.org/all/176114747153.315239.6863821259073466010.stgit@devnote2/
>
> This version is rebased on top of linux-trace/for-next branch
> and modify offset format to hex.
>
> 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/blktrace.c | 6 +
> kernel/trace/ftrace.c | 26 ++++++
> kernel/trace/trace.c | 154 +++++++++++++++++-----------------
> kernel/trace/trace.h | 40 +++++----
> kernel/trace/trace_events.c | 4 -
> kernel/trace/trace_events_synth.c | 2
> kernel/trace/trace_fprobe.c | 6 +
> kernel/trace/trace_functions_graph.c | 18 ++--
> kernel/trace/trace_irqsoff.c | 30 +++----
> kernel/trace/trace_kdb.c | 2
> kernel/trace/trace_kprobe.c | 6 +
> kernel/trace/trace_output.c | 18 ++--
> kernel/trace/trace_sched_wakeup.c | 24 +++--
> kernel/trace/trace_syscalls.c | 4 -
> kernel/trace/trace_wprobe.c | 2
> 15 files changed, 187 insertions(+), 155 deletions(-)
>
> --
> Masami Hiramatsu (Google) <mhiramat@kernel.org>
--
Masami Hiramatsu (Google) <mhiramat@kernel.org>
next prev parent reply other threads:[~2025-10-30 3:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-30 3:01 [PATCH v5 0/2] tracing: Add an option to show symbols in _text+offset for function profiler Masami Hiramatsu (Google)
2025-10-30 3:01 ` [PATCH v5 1/2] tracing: Allow tracer to add more than 32 options Masami Hiramatsu (Google)
2025-10-30 3:02 ` [PATCH v5 2/2] tracing: Add an option to show symbols in _text+offset for function profiler Masami Hiramatsu (Google)
2025-10-30 3:29 ` Masami Hiramatsu [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-10-22 15:37 [PATCH v5 0/2] " Masami Hiramatsu (Google)
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=20251030122901.46a51bfe643daa9910ad4110@kernel.org \
--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).