linux-trace-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Ajay Kaher <ajay.kaher@broadcom.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	"Linux Trace Kernel" <linux-trace-kernel@vger.kernel.org>,
	"Masami Hiramatsu" <mhiramat@kernel.org>,
	"Mathieu Desnoyers" <mathieu.desnoyers@efficios.com>,
	"Mathias Krause" <minipli@grsecurity.net>,
	"Ilkka Naulapää" <digirigawa@gmail.com>,
	"Linus Torvalds" <torvalds@linux-foundation.org>,
	"Al Viro" <viro@zeniv.linux.org.uk>,
	regressions@leemhuis.info,
	"Dan Carpenter" <dan.carpenter@linaro.org>,
	"Beau Belgrave" <beaub@linux.microsoft.com>,
	"Florian Fainelli" <florian.fainelli@broadcom.com>,
	"Alexey Makhalov" <alexey.makhalov@broadcom.com>,
	"Vasavi Sirnapalli" <vasavi.sirnapalli@broadcom.com>
Subject: Re: [PATCH] tracing: Have format file honor EVENT_FILE_FL_FREED
Date: Mon, 29 Jul 2024 12:10:34 -0400	[thread overview]
Message-ID: <20240729121034.455fe04d@rorschach.local.home> (raw)
In-Reply-To: <CAD2QZ9aFHOTLSryw88PKdvXBQaug9di=CDQ9KjPBhuOTNhjxTQ@mail.gmail.com>

On Mon, 29 Jul 2024 18:29:49 +0530
Ajay Kaher <ajay.kaher@broadcom.com> wrote:

> Following is not related to this bug:
> event_release callback executed once 'dir' closed (no more ref), any
> specific reason to register with 'dir'/'enable' file. If not, could we
> register with the 'dir' instead of 'enable'.

I tried that at first but it got messy. The files are saved in an array
for all files in the directory. There is just one array for all
directories that gets passed to the creation functions. That is, it
doesn't grow the memory footprint with the number of directories and
files created. By adding a callback for each file seemed a bit more
robust (and easier to implement as it only modified what the array
pointed to).

Although, I could change this array to a director structure that has a
callback for when it is destroyed and an array of all the files. That
may be the better approach but it caused a bigger change to the code as
it changed a lot of the prototypes.

So I ended up with the per file callback. But it could be updated if it
is appropriate.

-- Steve

  reply	other threads:[~2024-07-29 16:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-26  0:15 [PATCH] tracing: Have format file honor EVENT_FILE_FL_FREED Steven Rostedt
2024-07-26 10:16 ` Mathias Krause
2024-07-26 14:52   ` Steven Rostedt
2024-07-26 19:58     ` Mathias Krause
2024-07-26 20:20       ` Steven Rostedt
2024-07-26 12:30 ` Ajay Kaher
2024-07-26 16:03   ` Steven Rostedt
2024-07-29 12:59     ` Ajay Kaher
2024-07-29 16:10       ` Steven Rostedt [this message]
2024-07-29 14:38 ` Masami Hiramatsu

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=20240729121034.455fe04d@rorschach.local.home \
    --to=rostedt@goodmis.org \
    --cc=ajay.kaher@broadcom.com \
    --cc=alexey.makhalov@broadcom.com \
    --cc=beaub@linux.microsoft.com \
    --cc=dan.carpenter@linaro.org \
    --cc=digirigawa@gmail.com \
    --cc=florian.fainelli@broadcom.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mhiramat@kernel.org \
    --cc=minipli@grsecurity.net \
    --cc=regressions@leemhuis.info \
    --cc=torvalds@linux-foundation.org \
    --cc=vasavi.sirnapalli@broadcom.com \
    --cc=viro@zeniv.linux.org.uk \
    /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).