From: "Masami Hiramatsu (Google)" <mhiramat@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
Mark Rutland <mark.rutland@arm.com>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [RFC PATCH v2 0/3] tracing: Improve persistent ring buffer
Date: Tue, 11 Feb 2025 00:43:47 +0900 [thread overview]
Message-ID: <173920222697.826592.3726270716809214055.stgit@devnote2> (raw)
Hi,
Here is the 2nd version of the patch and additional improvement for ring
buffer on reseved memory. This depends on the series of "ring-buffer/tracing:
Save module information in persistent memory" here;
https://lore.kernel.org/all/20250205225031.799739376@goodmis.org/
In v2, I removed my first 2 patches, and fixes the 3rd patch. It also add
module LRU override feature which replaces the oldest removed module if
the module table is full.
I also added 2 patches to release the memory of persistent ring buffer
if user does not need it anymore. Currently persistent ring buffer has
to be enabled by kernel cmdline, user can not remove it without
changing the cmdline and rebooting. This feature allows user to remove
persistent ring buffer and release the memory without rebooting. Thus
user can set it up by default and remove it if it is not used anymore.
Thank you,
---
Masami Hiramatsu (Google) (3):
tracing: Show last module text symbols in the stacktrace
mm/memblock: Add reserved memory release function
tracing: Freeable reserved ring buffer
include/linux/mm.h | 1
kernel/trace/trace.c | 190 ++++++++++++++++++++++++++++++++++++++++---
kernel/trace/trace.h | 5 +
kernel/trace/trace_output.c | 3 -
mm/memblock.c | 72 ++++++++++++++--
5 files changed, 244 insertions(+), 27 deletions(-)
--
Masami Hiramatsu (Google) <mhiramat@kernel.org>
next reply other threads:[~2025-02-10 15:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-10 15:43 Masami Hiramatsu (Google) [this message]
2025-02-10 15:43 ` [RFC PATCH v2 1/3] tracing: Show last module text symbols in the stacktrace Masami Hiramatsu (Google)
2025-03-07 0:46 ` Steven Rostedt
2025-03-10 8:59 ` Masami Hiramatsu
2025-02-10 15:44 ` [RFC PATCH v2 2/3] mm/memblock: Add reserved memory release function Masami Hiramatsu (Google)
2025-02-11 0:03 ` Steven Rostedt
2025-02-11 1:43 ` Masami Hiramatsu
2025-02-10 15:44 ` [RFC PATCH v2 3/3] tracing: Freeable reserved ring buffer Masami Hiramatsu (Google)
2025-02-11 0:13 ` Steven Rostedt
2025-02-11 1:41 ` Masami Hiramatsu
2025-02-11 14:57 ` 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=173920222697.826592.3726270716809214055.stgit@devnote2 \
--to=mhiramat@kernel.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=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