linux-trace-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Tzvetomir Stoyanov <tstoyanov@vmware.com>
Cc: "linux-trace-devel@vger.kernel.org" <linux-trace-devel@vger.kernel.org>
Subject: Re: [PATCH 0/2] convert traceevent into a thread safe library
Date: Fri, 30 Nov 2018 11:47:42 -0500	[thread overview]
Message-ID: <20181130114742.43446dd8@gandalf.local.home> (raw)
In-Reply-To: <20181130131254.32621-1-tstoyanov@vmware.com>

On Fri, 30 Nov 2018 13:13:06 +0000
Tzvetomir Stoyanov <tstoyanov@vmware.com> wrote:

> This short patch series begins tranformation of libtraceevent into a
> 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.
> 

I've been thinking about this some. And we should change our
development model. We should be pushing these changes into the
trace-cmd tree first.

The reason I wanted to send to Linux tools/lib/traceevent was because
that would open it up to more people in the review stage. But
unfortunately, it leaves us vulnerable to having bugs and unexpected
consequences of these changes.

I think the renames and man pages were fine to go to Linux first. But
now that we are starting to change the way things work, that should go
into trace-cmd first, so that we can have a bit more thorough testing.

Let's get all the patches that have been sent upstream (including my
last patchset I sent to Arnaldo) backported into trace-cmd, and start
doing updates to the trace-cmd repo first. This way we can make sure
the code is tested before we send it to Arnaldo, because I believe they
think we are testing these patches before we send them, and honestly,
we are not.

Sound good?

Note, when writing the patches to trace-cmd, lets continue with the
naming convention "tools/lib/traceevent" just as if we were to be
sending them to Linux.

-- Steve


> Tzvetomir Stoyanov (2):
>   tools/lib/traceevent: make libtraceevent thread safe
>   tools/lib/traceevent: make few libtraceevent internal variables to be
>     per thread
> 
>  tools/lib/traceevent/Build                |  1 +
>  tools/lib/traceevent/event-parse-local.h  | 15 ++++--
>  tools/lib/traceevent/event-parse-thread.c | 63 +++++++++++++++++++++++
>  tools/lib/traceevent/event-parse.c        | 45 ++++++++--------
>  4 files changed, 100 insertions(+), 24 deletions(-)
>  create mode 100644 tools/lib/traceevent/event-parse-thread.c
> 

  parent reply	other threads:[~2018-12-01  3:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-30 13:13 [PATCH 0/2] convert traceevent into a thread safe library Tzvetomir Stoyanov
2018-11-30 13:13 ` [PATCH 1/2] tools/lib/traceevent: make libtraceevent thread safe Tzvetomir Stoyanov
2018-11-30 13:13 ` [PATCH 2/2] tools/lib/traceevent: make few libtraceevent internal variables to be per thread Tzvetomir Stoyanov
2018-11-30 16:47 ` Steven Rostedt [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-12-05  9:22 [PATCH 0/2] convert traceevent into a thread safe library 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=20181130114742.43446dd8@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=linux-trace-devel@vger.kernel.org \
    --cc=tstoyanov@vmware.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).