From: Tzvetomir Stoyanov <tstoyanov@vmware.com>
To: "rostedt@goodmis.org" <rostedt@goodmis.org>
Cc: "linux-trace-devel@vger.kernel.org" <linux-trace-devel@vger.kernel.org>
Subject: [PATCH 0/2] convert traceevent into a thread safe library
Date: Wed, 5 Dec 2018 09:22:11 +0000 [thread overview]
Message-ID: <20181205092200.2291-1-tstoyanov@vmware.com> (raw)
thread safe library. It implements per thread local storage for
tep->last_event cache, and converts input_buf, input_buf_ptr
and input_buf_siz internal variables to be thread specific.
[backported from Linux kernel tree]
Tzvetomir Stoyanov (2):
tools/lib/traceevent: make libtraceevent thread safe
tools/lib/traceevent: make few libtraceevent internal variables to be
per thread
lib/traceevent/Makefile | 1 +
lib/traceevent/event-parse-local.h | 15 +++++--
lib/traceevent/event-parse-thread.c | 63 +++++++++++++++++++++++++++++
lib/traceevent/event-parse.c | 45 +++++++++++----------
4 files changed, 100 insertions(+), 24 deletions(-)
create mode 100644 lib/traceevent/event-parse-thread.c
--
2.19.2
next reply other threads:[~2018-12-05 9:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-05 9:22 Tzvetomir Stoyanov [this message]
2018-12-05 9:22 ` [PATCH 1/2] tools/lib/traceevent: make libtraceevent thread safe Tzvetomir Stoyanov
2018-12-11 16:56 ` Steven Rostedt
2018-12-11 17:29 ` Steven Rostedt
2018-12-05 9:22 ` [PATCH 2/2] tools/lib/traceevent: make few libtraceevent internal variables to be per thread Tzvetomir Stoyanov
-- strict thread matches above, loose matches on Subject: below --
2018-11-30 13:13 [PATCH 0/2] convert traceevent into a thread safe library Tzvetomir Stoyanov
2018-11-30 16:47 ` 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=20181205092200.2291-1-tstoyanov@vmware.com \
--to=tstoyanov@vmware.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).