[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20260206225051.f22b670b54e8906a4bc1bec9@kernel.org>
Date: Fri, 6 Feb 2026 22:50:51 +0900
From: Masami Hiramatsu (Google) <mhiramat@...nel.org>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: Mathieu Desnoyers <mathieu.desnoyers@...icios.com>,
linux-kernel@...r.kernel.org, linux-trace-kernel@...r.kernel.org
Subject: Re: [PATCH v6 1/4] tracing: Reset last_boot_info if ring buffer is
reset
On Wed, 4 Feb 2026 20:40:49 -0500
Steven Rostedt <rostedt@...dmis.org> wrote:
> On Sun, 1 Feb 2026 12:29:07 +0900
> "Masami Hiramatsu (Google)" <mhiramat@...nel.org> wrote:
>
> > @@ -8036,6 +8042,7 @@ tracing_snapshot_write(struct file *filp, const char __user *ubuf, size_t cnt,
> > tracing_reset_online_cpus(&tr->max_buffer);
> > else
> > tracing_reset_cpu(&tr->max_buffer, iter->cpu_file);
> > + update_last_data_if_empty(tr);
>
> Is this needed? Memory mapped buffers (which the persistent ring buffer
> is) do not have snapshot buffers.
Yeah, I did this just for consistency. But it is better to just leave
the comment here.
Thank you,
>
> -- Steve
>
>
> > }
> > break;
> > }
>
--
Masami Hiramatsu (Google) <mhiramat@...nel.org>
Powered by blists - more mailing lists