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.16
Date: Wed, 28 May 2025 18:27:04 -0400 [thread overview]
Message-ID: <20250528222704.623477429@goodmis.org> (raw)
git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace.git
ring-buffer/for-next
Head SHA1: 1e83735aeb8330a23dd6020cd917ef12dd7ee56e
Masami Hiramatsu (Google) (1):
tracing: Reset last-boot buffers when reading out all cpu buffers
Steven Rostedt (9):
ring-buffer: Move cpus_read_lock() outside of buffer->mutex
ring-buffer: Do not trigger WARN_ON() due to a commit_overrun
ring-buffer: Allow reserve_mem persistent ring buffers to be mmapped
ring-buffer: Removed unnecessary if() goto out where out is the next line
ring-buffer: Remove jump to out label in ring_buffer_swap_cpu()
ring-buffer: Simplify reset_disabled_cpu_buffer() with use of guard()
ring-buffer: Simplify ring_buffer_read_page() with guard()
ring-buffer: Make ring_buffer_{un}map() simpler with guard(mutex)
ring-buffer: Simplify functions with __free(kfree) to free allocations
----
kernel/trace/ring_buffer.c | 213 ++++++++++++++++++++++++---------------------
kernel/trace/trace.c | 26 +++++-
2 files changed, 134 insertions(+), 105 deletions(-)
next reply other threads:[~2025-05-28 22:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-28 22:27 Steven Rostedt [this message]
2025-05-28 22:27 ` [for-next][PATCH 01/10] ring-buffer: Move cpus_read_lock() outside of buffer->mutex Steven Rostedt
2025-05-28 22:27 ` [for-next][PATCH 02/10] ring-buffer: Do not trigger WARN_ON() due to a commit_overrun Steven Rostedt
2025-05-28 22:27 ` [for-next][PATCH 03/10] ring-buffer: Allow reserve_mem persistent ring buffers to be mmapped Steven Rostedt
2025-05-28 22:27 ` [for-next][PATCH 04/10] tracing: Reset last-boot buffers when reading out all cpu buffers Steven Rostedt
2025-05-28 22:27 ` [for-next][PATCH 05/10] ring-buffer: Removed unnecessary if() goto out where out is the next line Steven Rostedt
2025-05-28 22:27 ` [for-next][PATCH 06/10] ring-buffer: Remove jump to out label in ring_buffer_swap_cpu() Steven Rostedt
2025-05-28 22:27 ` [for-next][PATCH 07/10] ring-buffer: Simplify reset_disabled_cpu_buffer() with use of guard() Steven Rostedt
2025-05-28 22:27 ` [for-next][PATCH 08/10] ring-buffer: Simplify ring_buffer_read_page() with guard() Steven Rostedt
2025-05-28 22:27 ` [for-next][PATCH 09/10] ring-buffer: Make ring_buffer_{un}map() simpler with guard(mutex) Steven Rostedt
2025-05-28 22:27 ` [for-next][PATCH 10/10] ring-buffer: Simplify functions with __free(kfree) to free allocations 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=20250528222704.623477429@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.