From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] tracing: Make the backup instance readonly
Date: Tue, 13 Jan 2026 15:04:58 +0900 [thread overview]
Message-ID: <20260113150458.8633891cf9f377565642124b@kernel.org> (raw)
In-Reply-To: <20260112194722.19164ca7@gandalf.local.home>
On Mon, 12 Jan 2026 19:47:22 -0500
Steven Rostedt <rostedt@goodmis.org> wrote:
> On Mon, 12 Jan 2026 19:45:51 -0500
> Steven Rostedt <rostedt@goodmis.org> wrote:
>
> > Let's not add any flags to the eventfs_entry. That is created for every
> > event, and events are already too big in size. I don't want to increase the
> > size of each event for this feature.
>
> Actually, there's not many of these. But they are all static variables. How
> are you going to differentiate them?
Since the format/id files are always readonly, so we can put a mode flag on
each entry.
Anyway, I will just share the readonly entries in the same array, but
put them at the beginning of it.
Let me update it to v3.
Thanks,
>
> -- Steve
>
--
Masami Hiramatsu (Google) <mhiramat@kernel.org>
next prev parent reply other threads:[~2026-01-13 6:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-08 14:22 [PATCH v2 0/2] tracing: Remove backup instance after read all Masami Hiramatsu (Google)
2026-01-08 14:23 ` [PATCH v2 1/2] tracing: Make the backup instance readonly Masami Hiramatsu (Google)
2026-01-13 0:31 ` Masami Hiramatsu
2026-01-13 0:45 ` Steven Rostedt
2026-01-13 0:47 ` Steven Rostedt
2026-01-13 6:04 ` Masami Hiramatsu [this message]
2026-01-08 14:23 ` [PATCH v2 2/2] tracing: Add autoremove feature to the backup instance Masami Hiramatsu (Google)
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=20260113150458.8633891cf9f377565642124b@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