From: "Tzvetomir Stoyanov (VMware)" <tz.stoyanov@gmail.com>
To: rostedt@goodmis.org
Cc: linux-trace-devel@vger.kernel.org
Subject: [PATCH v4 0/8] libtracefs fixes and improvements
Date: Tue, 17 Nov 2020 09:45:49 +0200 [thread overview]
Message-ID: <20201117074557.180602-1-tz.stoyanov@gmail.com> (raw)
A few final tracefs library fixes and improvements, before releasing it as
an official library.
v4 changes:
- Added new patch: "Use tracefs_list_free() API".
- Hid the library non API functions.
- When creating a new trace instance, inherit the permissions of the parent
"instance" directory.
v3 changes:
- Addressed Steven's comments.
v2 changes:
- Change tracefs_instance_create() to return pointer to allocated trace
instance structure.
- Add new API: tracefs_instance_is_new() to check if the trace instance is
newly created by the library.
Tzvetomir Stoyanov (VMware) (8):
trace-cmd: Change tracefs.h include path
libtracefs: Change get name API to return constant string
libtracefs: Use tracefs_list_free() API
libtracefs: Add new API to check if instance exists
libtracefs: Combine allocate and create APIs into one
libtracefs: Add new tracefs API tracefs_instances_walk()
trace-cmd: Add new libtrasefs API to get the current trace clock
libtracefs: Hide non API functions
include/trace-cmd/trace-cmd.h | 1 +
include/tracefs/tracefs.h | 10 +-
lib/trace-cmd/trace-timesync.c | 3 +-
lib/tracefs/include/tracefs-local.h | 3 +
lib/tracefs/tracefs-events.c | 26 ++--
lib/tracefs/tracefs-instance.c | 194 +++++++++++++++++++++++++---
lib/tracefs/tracefs-utils.c | 3 +-
tracecmd/include/trace-local.h | 4 +-
tracecmd/trace-record.c | 72 +++++------
tracecmd/trace-show.c | 2 +-
tracecmd/trace-stat.c | 81 +++---------
utest/tracefs-utest.c | 107 +++++++++++++--
12 files changed, 350 insertions(+), 156 deletions(-)
--
2.28.0
next reply other threads:[~2020-11-17 7:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-17 7:45 Tzvetomir Stoyanov (VMware) [this message]
2020-11-17 7:45 ` [PATCH v4 1/8] trace-cmd: Change tracefs.h include path Tzvetomir Stoyanov (VMware)
2020-11-17 7:45 ` [PATCH v4 2/8] libtracefs: Change get name API to return constant string Tzvetomir Stoyanov (VMware)
2020-11-17 7:45 ` [PATCH v4 3/8] libtracefs: Use tracefs_list_free() API Tzvetomir Stoyanov (VMware)
2020-11-17 7:45 ` [PATCH v4 4/8] libtracefs: Add new API to check if instance exists Tzvetomir Stoyanov (VMware)
2020-11-17 7:45 ` [PATCH v4 5/8] libtracefs: Combine allocate and create APIs into one Tzvetomir Stoyanov (VMware)
2020-11-18 21:44 ` Steven Rostedt
2020-11-18 21:46 ` [PATCH v4.1 - 5.1/8] libtracefs: Use the permissions of the instances directory for instances Steven Rostedt
2020-11-19 15:07 ` Tzvetomir Stoyanov
2020-11-18 21:46 ` [PATCH v4.1 5.2/8] libtracefs: Combine allocate and create APIs into one Steven Rostedt
2020-11-17 7:45 ` [PATCH v4 6/8] libtracefs: Add new tracefs API tracefs_instances_walk() Tzvetomir Stoyanov (VMware)
2020-11-17 7:45 ` [PATCH v4 7/8] trace-cmd: Add new libtrasefs API to get the current trace clock Tzvetomir Stoyanov (VMware)
2020-11-17 7:45 ` [PATCH v4 8/8] libtracefs: Hide non API functions Tzvetomir Stoyanov (VMware)
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=20201117074557.180602-1-tz.stoyanov@gmail.com \
--to=tz.stoyanov@gmail.com \
--cc=linux-trace-devel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).