From: Steven Rostedt <rostedt@kernel.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 0/9] ring-buffer: Updates for 7.2
Date: Fri, 29 May 2026 09:22:12 -0400 [thread overview]
Message-ID: <20260529132212.153072686@kernel.org> (raw)
git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace.git
ring-buffer/for-next
Head SHA1: 8928e4a3be34bf053f9ef1cad67263604bf4f05e
Masami Hiramatsu (Google) (6):
ring-buffer: Skip invalid sub-buffers when validating persistent ring buffer
ring-buffer: Skip invalid sub-buffers when rewinding persistent ring buffer
ring-buffer: Add persistent ring buffer invalid-page inject test
ring-buffer: Show commit numbers in buffer_meta file
ring-buffer: Cleanup persistent ring buffer validation
ring-buffer: Cleanup buffer_data_page related code
Steven Rostedt (3):
ring-buffer: Have dropped subbuffers be persistent across reboots
ring-buffer: Show persistent buffer dropped events in trace file
ring-buffer: Show persistent buffer dropped events in trace_pipe file
----
include/linux/ring_buffer.h | 1 +
kernel/trace/Kconfig | 34 +++
kernel/trace/ring_buffer.c | 543 +++++++++++++++++++++++++++++---------------
kernel/trace/trace.c | 4 +
4 files changed, 402 insertions(+), 180 deletions(-)
next reply other threads:[~2026-05-29 13:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-29 13:22 Steven Rostedt [this message]
2026-05-29 13:22 ` [for-next][PATCH 1/9] ring-buffer: Skip invalid sub-buffers when validating persistent ring buffer Steven Rostedt
2026-05-29 13:22 ` [for-next][PATCH 2/9] ring-buffer: Skip invalid sub-buffers when rewinding " Steven Rostedt
2026-05-29 13:22 ` [for-next][PATCH 3/9] ring-buffer: Add persistent ring buffer invalid-page inject test Steven Rostedt
2026-05-29 13:22 ` [for-next][PATCH 4/9] ring-buffer: Show commit numbers in buffer_meta file Steven Rostedt
2026-05-29 13:22 ` [for-next][PATCH 5/9] ring-buffer: Cleanup persistent ring buffer validation Steven Rostedt
2026-05-29 13:22 ` [for-next][PATCH 6/9] ring-buffer: Cleanup buffer_data_page related code Steven Rostedt
2026-05-29 13:22 ` [for-next][PATCH 7/9] ring-buffer: Have dropped subbuffers be persistent across reboots Steven Rostedt
2026-05-29 13:22 ` [for-next][PATCH 8/9] ring-buffer: Show persistent buffer dropped events in trace file Steven Rostedt
2026-05-29 13:22 ` [for-next][PATCH 9/9] ring-buffer: Show persistent buffer dropped events in trace_pipe file 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=20260529132212.153072686@kernel.org \
--to=rostedt@kernel.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.