From: Steven Rostedt <rostedt@goodmis.org>
To: Sameeruddin Shaik <sameeruddin.shaik8@gmail.com>
Cc: linux-trace-devel@vger.kernel.org,
"Tzvetomir Stoyanov (VMware)" <tz.stoyanov@gmail.com>
Subject: Re: libtracefs: New APIS to write/erase 'set_ftrace_filter' and 'set_ftrace_notrace' Inbox
Date: Thu, 28 Jan 2021 12:59:31 -0500 [thread overview]
Message-ID: <20210128125931.300d5c8d@gandalf.local.home> (raw)
In-Reply-To: <CAK7tX=akBmqBDUZ1k6dDd9aZ=xoTwppBiEa21wQomME-vQzv7g@mail.gmail.com>
On Thu, 28 Jan 2021 11:20:38 +0530
Sameeruddin Shaik <sameeruddin.shaik8@gmail.com> wrote:
> hi,
> I am working on the below API's
> ----------------------------------------------------
>
> Add an API to set filtering of functions:
>
> int tracefs_function_filter(struct tracefs_instance *instance, const
> char *filter);
>
> Which would write into the set_ftrace_filter file for the instance.
>
> Also have a:
>
> int tracefs_function_notrace(struct tracefs_instance *instance, const
> char *filter);
>
> That would write into the set_ftrace_notrace file for the instance.
>
> Have a:
>
> int tracefs_function_filter_clear(struct tracefs_instance *instance);
>
> That clears the set_ftrace_filter file.
>
> and a:
>
> int tracefs_function_notrace_clear(struct tracefs_instance *instance);
>
> That clears the set_ftrace_notrace file.
> ----------------------------------------------------------
>
> Bugzilla link: https://bugzilla.kernel.org/show_bug.cgi?id=210643
>
> if there is anyone already working on these API's please let me know.
>
>
I don't believe anyone is currently working on this APIs. We're happy to
see patches for them coming from you.
-- Steve
prev parent reply other threads:[~2021-01-28 18:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-28 5:50 libtracefs: New APIS to write/erase 'set_ftrace_filter' and 'set_ftrace_notrace' Inbox Sameeruddin Shaik
2021-01-28 17:59 ` Steven Rostedt [this message]
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=20210128125931.300d5c8d@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=sameeruddin.shaik8@gmail.com \
--cc=tz.stoyanov@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).