From: "Tzvetomir Stoyanov (VMware)" <tz.stoyanov@gmail.com>
To: rostedt@goodmis.org, y.karadz@gmail.com
Cc: linux-trace-devel@vger.kernel.org
Subject: [PATCH 0/4] New tracefs APIs
Date: Tue, 30 Nov 2021 07:00:53 +0200 [thread overview]
Message-ID: <20211130050057.336228-1-tz.stoyanov@gmail.com> (raw)
Two new library APIs are proposed, to provide a missing functionality:
tracefs_dynevent_get_event()
tracefs_event_apply_filter()
Tzvetomir Stoyanov (VMware) (4):
libtracefs: Reuse logic for loading events inside the library
libtracefs: New API for getting dynamic event
libtracefs: Unit test for tracefs_dynevent_get_event()
libtracefs: New API for applying filter on event.
Documentation/libtracefs-dynevents.txt | 15 ++++++-
Documentation/libtracefs-filter.txt | 11 ++++-
include/tracefs-local.h | 3 ++
include/tracefs.h | 5 +++
src/tracefs-dynevents.c | 29 +++++++++++++
src/tracefs-events.c | 11 +++--
src/tracefs-filter.c | 19 +++++++++
utest/tracefs-utest.c | 58 +++++++++++++++++---------
8 files changed, 125 insertions(+), 26 deletions(-)
--
2.33.1
next reply other threads:[~2021-11-30 5:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-30 5:00 Tzvetomir Stoyanov (VMware) [this message]
2021-11-30 5:00 ` [PATCH 1/4] libtracefs: Reuse logic for loading events inside the library Tzvetomir Stoyanov (VMware)
2021-11-30 5:00 ` [PATCH 2/4] libtracefs: New API for getting dynamic event Tzvetomir Stoyanov (VMware)
2021-12-01 21:04 ` Steven Rostedt
2021-12-02 5:05 ` Tzvetomir Stoyanov
2021-11-30 5:00 ` [PATCH 3/4] libtracefs: Unit test for tracefs_dynevent_get_event() Tzvetomir Stoyanov (VMware)
2021-11-30 5:00 ` [PATCH 4/4] libtracefs: New API for applying filter on event Tzvetomir Stoyanov (VMware)
2021-12-01 19:55 ` Steven Rostedt
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=20211130050057.336228-1-tz.stoyanov@gmail.com \
--to=tz.stoyanov@gmail.com \
--cc=linux-trace-devel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=y.karadz@gmail.com \
/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).