[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20210812155029.929048-1-rostedt@goodmis.org>
Date: Thu, 12 Aug 2021 11:50:27 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: linux-trace-devel@...r.kernel.org
Cc: linux-kernel@...r.kernel.org, Tom Zanussi <zanussi@...nel.org>,
Daniel Bristot de Oliveira <bristot@...hat.com>,
Masami Hiramatsu <mhiramat@...nel.org>,
"Steven Rostedt (VMware)" <rostedt@...dmis.org>
Subject: [PATCH v2 0/2] libtracefs: Make hist variable names unique
From: "Steven Rostedt (VMware)" <rostedt@...dmis.org>
In order to be able to have API that can do onmax() and onchange() as well
as include the .save() and .snapshot() actions, we need to make sure that
the variable names are unique even between different events.
The first adds a "randomness" to the name, and the second patch fixes an
issue where the "end" event fields are saved in the same name as they are
called, then the ".save" action can not be used on them.
Changes since v1:
- Use open coded "rand()" as rand() is not reentrant, and it we use our own
seed each time.
- Use gettimeofday() instead of time() as Yordan pointed out that time()
has a resolution of 1 second, and a thread could call this for different
synthetic events.
Steven Rostedt (VMware) (2):
libtracefs: Add random number to keep synthetic variables unique
libtracefs: Have end event variables not be the end event field name
src/tracefs-hist.c | 45 +++++++++++++++++++++++++++++++++++----------
1 file changed, 35 insertions(+), 10 deletions(-)
--
2.30.2
Powered by blists - more mailing lists