From: "Tzvetomir Stoyanov (VMware)" <tz.stoyanov@gmail.com>
To: rostedt@goodmis.org
Cc: linux-trace-devel@vger.kernel.org
Subject: [PATCH v2 0/5] New libtracefs APIs for trace options and trace dir
Date: Wed, 20 Jan 2021 17:12:51 +0200 [thread overview]
Message-ID: <20210120151256.43075-1-tz.stoyanov@gmail.com> (raw)
A new set of tracefs library APIs for:
- Working with trace options.
- Working with non default tracing directory.
v2 changes:
- Changed the trace options IDs from bitmask to enum.
- Abstracted trace options bitmap structure.
- Removed test_nop_refuse and test_nop_accept options from the library.
- Renamed tracefs_instance_get() to tracefs_instance_alloc().
Tzvetomir Stoyanov (VMware) (5):
libtracefs: New APIs for trace options
libtracefs: Unit tests for tracing options APIs
libtracefs: Add information about top tracing directory in instance
structure
libtracefs: New APIs for getting existing trace instance
libtracefs: Unit tests for working with non default tracing dir
include/tracefs.h | 64 ++++++
src/tracefs-instance.c | 137 ++++++++++---
src/tracefs-tools.c | 244 +++++++++++++++++++++++
utest/tracefs-utest.c | 431 +++++++++++++++++++++++++++++++++++------
4 files changed, 786 insertions(+), 90 deletions(-)
--
2.29.2
next reply other threads:[~2021-01-20 15:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-20 15:12 Tzvetomir Stoyanov (VMware) [this message]
2021-01-20 15:12 ` [PATCH v2 1/5] libtracefs: New APIs for trace options Tzvetomir Stoyanov (VMware)
2021-01-20 15:12 ` [PATCH v2 2/5] libtracefs: Unit tests for tracing options APIs Tzvetomir Stoyanov (VMware)
2021-01-20 15:12 ` [PATCH v2 3/5] libtracefs: Add information about top tracing directory in instance structure Tzvetomir Stoyanov (VMware)
2021-01-20 15:12 ` [PATCH v2 4/5] libtracefs: New APIs for getting existing trace instance Tzvetomir Stoyanov (VMware)
2021-01-20 15:12 ` [PATCH v2 5/5] libtracefs: Unit tests for working with non default tracing dir 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=20210120151256.43075-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).