From: "Tzvetomir Stoyanov (VMware)" <tz.stoyanov@gmail.com>
To: rostedt@goodmis.org
Cc: linux-trace-devel@vger.kernel.org
Subject: [PATCH v2 0/7] New libtracefs APIs
Date: Tue, 12 Jan 2021 11:20:17 +0200 [thread overview]
Message-ID: <20210112092024.605705-1-tz.stoyanov@gmail.com> (raw)
Added new APIs to tracefs library and updated man pages and unit tests:
tracefs_instance_file_read_number();
tracefs_instance_file_open();
tracefs_trace_is_on();
tracefs_trace_on();
tracefs_trace_off();
tracefs_trace_on_get_fd()p;
tracefs_trace_on_fd();
tracefs_trace_off_fd();
v2 changes:
- Renamed tracefs_instance_file_read_int() to tracefs_instance_file_read_number().
- Added new tracefs_trace_on_get_fd() API.
- Better error checking of tracefs_instance_file_read_number() API.
- A few code clean-ups, suggested by Steven.
Tzvetomir Stoyanov (VMware) (7):
libtracefs: tracefs_instance_file_read() get a const file name
libtracefs: New APIs for opening and reading ftrace files
libtracefs: New APIs for enable / disable tracing
libtracefs: Documentation for the new APIs for opening and reading
ftrace files
libtracefs: Documentation for enable / disable tracing APIs
libtracefs: Unit tests for the new APIs for opening and reading ftrace
files
libtracefs: Unit tests for enable / disable tracing APIs
Documentation/libtracefs-instances-files.txt | 47 +++++-
Documentation/libtracefs-traceon.txt | 151 +++++++++++++++++++
Documentation/libtracefs.txt | 10 +-
include/tracefs.h | 24 ++-
src/Makefile | 1 +
src/tracefs-instance.c | 62 +++++++-
src/tracefs-tools.c | 109 +++++++++++++
utest/tracefs-utest.c | 137 ++++++++++++++++-
8 files changed, 532 insertions(+), 9 deletions(-)
create mode 100644 Documentation/libtracefs-traceon.txt
create mode 100644 src/tracefs-tools.c
--
2.29.2
next reply other threads:[~2021-01-12 9:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-12 9:20 Tzvetomir Stoyanov (VMware) [this message]
2021-01-12 9:20 ` [PATCH v2 1/7] libtracefs: tracefs_instance_file_read() get a const file name Tzvetomir Stoyanov (VMware)
2021-01-12 9:20 ` [PATCH v2 2/7] libtracefs: New APIs for opening and reading ftrace files Tzvetomir Stoyanov (VMware)
2021-01-12 9:20 ` [PATCH v2 3/7] libtracefs: New APIs for enable / disable tracing Tzvetomir Stoyanov (VMware)
2021-02-19 3:07 ` Steven Rostedt
2021-01-12 9:20 ` [PATCH v2 4/7] libtracefs: Documentation for the new APIs for opening and reading ftrace files Tzvetomir Stoyanov (VMware)
2021-01-12 9:20 ` [PATCH v2 5/7] libtracefs: Documentation for enable / disable tracing APIs Tzvetomir Stoyanov (VMware)
2021-01-12 9:20 ` [PATCH v2 6/7] libtracefs: Unit tests for the new APIs for opening and reading ftrace files Tzvetomir Stoyanov (VMware)
2021-01-12 9:20 ` [PATCH v2 7/7] libtracefs: Unit tests for enable / disable tracing APIs 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=20210112092024.605705-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).