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>,
Mike Rapoport <rppt@kernel.org>,
linux-mm@kvack.org
Subject: [PATCH v4 0/2] tracing: Make persistent ring buffer freeable
Date: Wed, 19 Feb 2025 00:08:47 +0900 [thread overview]
Message-ID: <173989132750.230693.15749600013776132201.stgit@devnote2> (raw)
Hi,
Here is the 4th version of patches for making the persistent ring buffer
freeable. The previous version is here;
https://lore.kernel.org/all/173928521419.906035.17750338150436695675.stgit@devnote2/
In this version, I used free_reserved_area() instead of custom releasing
code. This seems working correctly. Thanks Mike!
Thank you,
---
Masami Hiramatsu (Google) (2):
mm/memblock: Add reserved memory release function
tracing: Freeable reserved ring buffer
include/linux/mm.h | 1 +
kernel/trace/trace.c | 13 +++++++++-
kernel/trace/trace.h | 1 +
mm/memblock.c | 66 +++++++++++++++++++++++++++++++++++++++++---------
4 files changed, 68 insertions(+), 13 deletions(-)
--
Masami Hiramatsu (Google) <mhiramat@kernel.org>
next reply other threads:[~2025-02-18 15:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-18 15:08 Masami Hiramatsu (Google) [this message]
2025-02-18 15:08 ` [PATCH v4 1/2] mm/memblock: Add reserved memory release function Masami Hiramatsu (Google)
2025-04-05 2:30 ` Wei Yang
2025-04-07 0:33 ` Masami Hiramatsu
2025-04-07 1:40 ` Masami Hiramatsu
2025-02-18 15:09 ` [PATCH v4 2/2] tracing: Freeable reserved ring buffer Masami Hiramatsu (Google)
2025-02-25 20:55 ` [PATCH v4 0/2] tracing: Make persistent ring buffer freeable 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=173989132750.230693.15749600013776132201.stgit@devnote2 \
--to=mhiramat@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=rostedt@goodmis.org \
--cc=rppt@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).