From: Steven Rostedt <rostedt@goodmis.org>
To: linux-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: [for-next][PATCH 00/10] ring-buffer: Updates for v6.15
Date: Thu, 06 Mar 2025 10:25:48 -0500 [thread overview]
Message-ID: <20250306152548.763044302@goodmis.org> (raw)
git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace.git
ring-buffer/for-next
Head SHA1: c6a1b7c2e58d048ed8b7b2f331fef42b52376336
Feng Yang (1):
ring-buffer: Fix bytes_dropped calculation issue
Steven Rostedt (9):
ring-buffer: Allow persistent ring buffers to be mmapped
ring-buffer: Use kaslr address instead of text delta
ring-buffer: Add buffer meta data for persistent ring buffer
ring-buffer: Add ring_buffer_meta_scratch()
tracing: Have persistent trace instances save KASLR offset
module: Add module_for_each_mod() function
tracing: Have persistent trace instances save module addresses
tracing: Show module names and addresses of last boot
tracing: Update modules to persistent instances when loaded
----
include/linux/module.h | 6 +
include/linux/ring_buffer.h | 8 +-
kernel/module/main.c | 13 ++
kernel/trace/ring_buffer.c | 299 ++++++++++++++++++++++++++++----------------
kernel/trace/trace.c | 268 +++++++++++++++++++++++++++++++++++----
kernel/trace/trace.h | 15 ++-
kernel/trace/trace_events.c | 40 ++++--
7 files changed, 493 insertions(+), 156 deletions(-)
next reply other threads:[~2025-03-06 15:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-06 15:25 Steven Rostedt [this message]
2025-03-06 15:25 ` [for-next][PATCH 01/10] ring-buffer: Allow persistent ring buffers to be mmapped Steven Rostedt
2025-03-06 15:25 ` [for-next][PATCH 02/10] ring-buffer: Fix bytes_dropped calculation issue Steven Rostedt
2025-03-06 15:25 ` [for-next][PATCH 03/10] ring-buffer: Use kaslr address instead of text delta Steven Rostedt
2025-03-06 15:25 ` [for-next][PATCH 04/10] ring-buffer: Add buffer meta data for persistent ring buffer Steven Rostedt
2025-03-06 15:25 ` [for-next][PATCH 05/10] ring-buffer: Add ring_buffer_meta_scratch() Steven Rostedt
2025-03-06 15:25 ` [for-next][PATCH 06/10] tracing: Have persistent trace instances save KASLR offset Steven Rostedt
2025-03-06 15:25 ` [for-next][PATCH 07/10] module: Add module_for_each_mod() function Steven Rostedt
2025-03-06 15:25 ` [for-next][PATCH 08/10] tracing: Have persistent trace instances save module addresses Steven Rostedt
2025-03-06 15:25 ` [for-next][PATCH 09/10] tracing: Show module names and addresses of last boot Steven Rostedt
2025-03-06 15:25 ` [for-next][PATCH 10/10] tracing: Update modules to persistent instances when loaded 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=20250306152548.763044302@goodmis.org \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=linux-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.