From: "Tzvetomir Stoyanov (VMware)" <tz.stoyanov@gmail.com>
To: rostedt@goodmis.org
Cc: linux-trace-devel@vger.kernel.org
Subject: [PATCH v2 0/5] tracefs library
Date: Mon, 6 Jan 2020 17:40:53 +0200 [thread overview]
Message-ID: <20200106154058.60660-1-tz.stoyanov@gmail.com> (raw)
Add a skeleton for new library: libtracefs, providing APIs
for accessing files from tracefs. The library files are added in
lib/tracefs
include/tracefs
It is built and installed by trace-cmd targets
make libs
make install_libs
[
v2 changes:
- Fix copyright of the newly created files
- Remove tracefs_write_file() API, add it as a local helper function
]
Tzvetomir Stoyanov (VMware) (5):
trace-cmd: Introduce libtracefs library
kernel-shark: Use new tracefs library
trace-cmd: New libtracefs APIs for ftrace instances
trace-cmd,kernel-shark: New libtracefs APIs for ftrace events and
systems
trace-cmd,kernel-shark: New libtracefs APIs for loading ftrace events
Makefile | 27 +-
include/trace-cmd/trace-cmd.h | 21 -
include/tracefs/tracefs.h | 56 +++
kernel-shark/CMakeLists.txt | 3 +-
kernel-shark/build/FindTraceCmd.cmake | 30 ++
kernel-shark/src/CMakeLists.txt | 2 +
kernel-shark/src/KsCaptureDialog.cpp | 4 +-
kernel-shark/src/libkshark.h | 1 +
lib/trace-cmd/trace-input.c | 95 ----
lib/trace-cmd/trace-output.c | 3 +-
lib/trace-cmd/trace-recorder.c | 7 +-
lib/trace-cmd/trace-util.c | 629 ------------------------
lib/tracefs/Makefile | 48 ++
lib/tracefs/include/tracefs-local.h | 13 +
lib/tracefs/tracefs-events.c | 661 ++++++++++++++++++++++++++
lib/tracefs/tracefs-instance.c | 267 +++++++++++
lib/tracefs/tracefs-utils.c | 226 +++++++++
tracecmd/Makefile | 2 +-
tracecmd/include/trace-local.h | 5 +-
tracecmd/trace-check-events.c | 5 +-
tracecmd/trace-list.c | 21 +-
tracecmd/trace-record.c | 373 ++++++---------
tracecmd/trace-show.c | 7 +-
tracecmd/trace-snapshot.c | 9 +-
tracecmd/trace-stack.c | 9 +-
tracecmd/trace-stat.c | 38 +-
26 files changed, 1531 insertions(+), 1031 deletions(-)
create mode 100644 include/tracefs/tracefs.h
create mode 100644 lib/tracefs/Makefile
create mode 100644 lib/tracefs/include/tracefs-local.h
create mode 100644 lib/tracefs/tracefs-events.c
create mode 100644 lib/tracefs/tracefs-instance.c
create mode 100644 lib/tracefs/tracefs-utils.c
--
2.24.1
next reply other threads:[~2020-01-06 15:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-06 15:40 Tzvetomir Stoyanov (VMware) [this message]
2020-01-06 15:40 ` [PATCH v2 1/5] trace-cmd: Introduce libtracefs library Tzvetomir Stoyanov (VMware)
2020-01-06 15:40 ` [PATCH v2 2/5] kernel-shark: Use new tracefs library Tzvetomir Stoyanov (VMware)
2020-01-08 19:05 ` Steven Rostedt
2020-01-08 20:09 ` Steven Rostedt
2020-01-06 15:40 ` [PATCH v2 3/5] trace-cmd: New libtracefs APIs for ftrace instances Tzvetomir Stoyanov (VMware)
2020-01-08 19:37 ` Steven Rostedt
2020-01-09 13:29 ` Tzvetomir Stoyanov
2020-01-06 15:40 ` [PATCH v2 4/5] trace-cmd,kernel-shark: New libtracefs APIs for ftrace events and systems Tzvetomir Stoyanov (VMware)
2020-01-08 20:22 ` Steven Rostedt
2020-01-09 13:37 ` Tzvetomir Stoyanov
2020-01-08 21:09 ` Steven Rostedt
2020-01-09 14:14 ` Tzvetomir Stoyanov
2020-01-09 2:32 ` Steven Rostedt
2020-01-06 15:40 ` [PATCH v2 5/5] trace-cmd,kernel-shark: New libtracefs APIs for loading ftrace events 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=20200106154058.60660-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).