From: Steven Rostedt <rostedt@goodmis.org>
To: <linux-trace-devel@vger.kernel.org>
Cc: Sameeruddin shaik <sameeruddin.shaik8@gmail.com>
Subject: Re: [PATCH 0/3] libtracefs: Update filtering functions
Date: Wed, 7 Apr 2021 16:30:55 -0400 [thread overview]
Message-ID: <20210407163055.5fe73c25@gandalf.local.home> (raw)
In-Reply-To: <20210407202126.1870994-1-rostedt@goodmis.org>
On Wed, 7 Apr 2021 16:21:23 -0400
Steven Rostedt <rostedt@goodmis.org> wrote:
> From: "Steven Rostedt (VMware)" <rostedt@goodmis.org>
>
> Add tracefs_function_notrace() to set the functions not to trace.
> Create a per instance pthread mutex lock.
>
> [ This is actually the first time I'm sending patches via
> git send-email! Hopefully I dont' screw it up ;-) ]
Hmm, as I found that my gitconfig uses vmware's smtp server, and the
Receive-SPF does not match. It may be blocked by the mailing lists.
I may try a second time. :-/
-- Steve
>
> Steven Rostedt (VMware) (3):
> libtracefs: Move most functionality into helper function for
> tracefs_function_filter()
> libtracefs: Add tracefs_function_notrace() API
> libtracefs: Add a pthread_mutex per instance
>
> Documentation/libtracefs-function-filter.txt | 19 ++-
> include/tracefs-local.h | 12 +-
> include/tracefs.h | 3 +
> src/tracefs-instance.c | 6 +
> src/tracefs-tools.c | 152 ++++++++++++-------
> 5 files changed, 131 insertions(+), 61 deletions(-)
>
prev parent reply other threads:[~2021-04-07 20:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-07 20:21 [PATCH 0/3] libtracefs: Update filtering functions Steven Rostedt
2021-04-07 20:21 ` [PATCH 1/3] libtracefs: Move most functionality into helper function for tracefs_function_filter() Steven Rostedt
2021-04-07 20:21 ` [PATCH 2/3] libtracefs: Add tracefs_function_notrace() API Steven Rostedt
2021-04-08 4:25 ` Tzvetomir Stoyanov
2021-04-08 12:53 ` Steven Rostedt
2021-04-07 20:21 ` [PATCH 3/3] libtracefs: Add a pthread_mutex per instance Steven Rostedt
2021-04-07 20:30 ` 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=20210407163055.5fe73c25@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=sameeruddin.shaik8@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).