From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: "Masami Hiramatsu (Google)" <mhiramat@kernel.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH v6 0/4] tracing: Remove backup instance after read all
Date: Thu, 5 Feb 2026 09:41:42 +0900 [thread overview]
Message-ID: <20260205094142.03d87e2d482649cb51355017@kernel.org> (raw)
In-Reply-To: <176991653525.4025429.12655335935351822711.stgit@mhiramat.tok.corp.google.com>
Hi Steve,
Can you review this series?
On Sun, 1 Feb 2026 12:28:55 +0900
"Masami Hiramatsu (Google)" <mhiramat@kernel.org> wrote:
> Hi,
>
> Here is the v6 of the series to improve backup instances of
> the persistent ring buffer. The previous version is here:
>
> https://lore.kernel.org/all/176955897718.2786091.11948759407196200082.stgit@mhiramat.tok.corp.google.com/
>
> This version cleanup code and fix typo, according to Steve's
> comments. Also fix to init autoremove_wq only when the readonly
> instance has been made. A major UI change is that the tracing_on
> file is also removed from readonly instance.
>
> Since backup instances are a kind of snapshot of the persistent
> ring buffer, it should be readonly. And if it is readonly
> there is no reason to keep it after reading all data via trace_pipe
> because the data has been consumed. But user should be able to remove
> the readonly instance by rmdir or truncating `trace` file.
>
> Thus, [2/4] makes backup instances readonly (not able to write any
> events, cleanup trace, change buffer size). Also, [3/4] removes the
> backup instance after consuming all data via trace_pipe.
> With this improvements, even if we makes a backup instance (using
> the same amount of memory of the persistent ring buffer), it will
> be removed after reading the data automatically.
>
> ---
>
> Masami Hiramatsu (Google) (4):
> tracing: Reset last_boot_info if ring buffer is reset
> tracing: Make the backup instance non-reusable
> tracing: Remove the backup instance automatically after read
> tracing/Documentation: Add a section about backup instance
>
>
> Documentation/trace/debugging.rst | 19 ++++
> kernel/trace/trace.c | 162 ++++++++++++++++++++++++++++++-------
> kernel/trace/trace.h | 13 +++
> kernel/trace/trace_boot.c | 5 +
> kernel/trace/trace_events.c | 76 ++++++++++-------
> 5 files changed, 209 insertions(+), 66 deletions(-)
>
> --
> Masami Hiramatsu (Google) <mhiramat@kernel.org>
--
Masami Hiramatsu (Google) <mhiramat@kernel.org>
prev parent reply other threads:[~2026-02-05 0:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-01 3:28 [PATCH v6 0/4] tracing: Remove backup instance after read all Masami Hiramatsu (Google)
2026-02-01 3:29 ` [PATCH v6 1/4] tracing: Reset last_boot_info if ring buffer is reset Masami Hiramatsu (Google)
2026-02-05 1:40 ` Steven Rostedt
2026-02-06 13:50 ` Masami Hiramatsu
2026-02-11 18:28 ` Steven Rostedt
2026-02-11 18:33 ` Steven Rostedt
2026-02-01 3:29 ` [PATCH v6 2/4] tracing: Make the backup instance non-reusable Masami Hiramatsu (Google)
2026-02-05 2:17 ` Steven Rostedt
2026-02-09 9:08 ` Masami Hiramatsu
2026-02-09 23:42 ` Steven Rostedt
2026-02-10 5:14 ` Masami Hiramatsu
2026-02-11 15:42 ` Steven Rostedt
2026-02-12 4:24 ` Masami Hiramatsu
2026-02-01 3:29 ` [PATCH v6 3/4] tracing: Remove the backup instance automatically after read Masami Hiramatsu (Google)
2026-02-01 3:29 ` [PATCH v6 4/4] tracing/Documentation: Add a section about backup instance Masami Hiramatsu (Google)
2026-02-05 0:41 ` Masami Hiramatsu [this message]
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=20260205094142.03d87e2d482649cb51355017@kernel.org \
--to=mhiramat@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--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