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>
Subject: [PATCH 0/4] tracing: Have function tracing and events handle module addresses
Date: Tue, 04 Mar 2025 18:15:45 -0500 [thread overview]
Message-ID: <20250304231545.708806702@goodmis.org> (raw)
This is based on top of Masami's patch:
https://lore.kernel.org/linux-trace-kernel/173886114516.496116.8314066678313037503.stgit@devnote2/
As it requires the function trace_adjust_address() for both kernel text
and modules.
This updates the function tracer as well as the pointers used in events
to be updated via the trace_adjust_address() function.
Steven Rostedt (4):
tracing: Update function trace addresses with module addresses
tracing: Show function names when possible when listing fields
tracing: Only return an adjusted address if it matches the kernel address
tracing: Adjust addresses for printing out fields
----
kernel/trace/trace.c | 5 ++++-
kernel/trace/trace_output.c | 46 +++++++++++++++++++++++++++++----------------
2 files changed, 34 insertions(+), 17 deletions(-)
next reply other threads:[~2025-03-04 23:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-04 23:15 Steven Rostedt [this message]
2025-03-04 23:15 ` [PATCH 1/4] tracing: Update function trace addresses with module addresses Steven Rostedt
2025-03-04 23:15 ` [PATCH 2/4] tracing: Show function names when possible when listing fields Steven Rostedt
2025-03-04 23:15 ` [PATCH 3/4] tracing: Only return an adjusted address if it matches the kernel address Steven Rostedt
2025-03-04 23:15 ` [PATCH 4/4] tracing: Adjust addresses for printing out fields 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=20250304231545.708806702@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 \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.