From: "Tzvetomir Stoyanov (VMware)" <tz.stoyanov@gmail.com>
To: rostedt@goodmis.org
Cc: linux-trace-devel@vger.kernel.org
Subject: [PATCH v2 0/3] libtracefs: Introduce new API to reset ftrace instance
Date: Wed, 26 Apr 2023 07:11:21 +0300 [thread overview]
Message-ID: <20230426041124.69544-1-tz.stoyanov@gmail.com> (raw)
A new API tracefs_instance_reset() for resetting instance to its default
state, based on the logic from "trace-cmd reset" command.
v2 changes:
- Check if the kernel is configured with triggers enabled, before calling
clear_trigger().
- Clear "stack_trace_filter" file.
- Fixed spelling and coding style errors.
Tzvetomir Stoyanov (VMware) (3):
libtracefs: New API to reset ftrace instance
libtracefs: Documentation for tracefs_instance_reset()
libtracefs: Unit test for tracefs_instance_reset()
Documentation/libtracefs-instances-manage.txt | 7 +-
Documentation/libtracefs.txt | 1 +
include/tracefs-local.h | 1 +
include/tracefs.h | 1 +
src/tracefs-instance.c | 207 ++++++++++++++++++
src/tracefs-utils.c | 20 ++
utest/tracefs-utest.c | 183 ++++++++++++++++
7 files changed, 418 insertions(+), 2 deletions(-)
--
2.39.2
next reply other threads:[~2023-04-26 4:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-26 4:11 Tzvetomir Stoyanov (VMware) [this message]
2023-04-26 4:11 ` [PATCH v2 1/3] libtracefs: New API to reset ftrace instance Tzvetomir Stoyanov (VMware)
2023-04-26 4:11 ` [PATCH v2 2/3] libtracefs: Documentation for tracefs_instance_reset() Tzvetomir Stoyanov (VMware)
2023-04-26 4:11 ` [PATCH v2 3/3] libtracefs: Unit test " Tzvetomir Stoyanov (VMware)
2023-05-29 12:05 ` Steven Rostedt
2023-05-30 8:19 ` Tzvetomir Stoyanov
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=20230426041124.69544-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).