linux-trace-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Tzvetomir Stoyanov (VMware)" <tz.stoyanov@gmail.com>
To: rostedt@goodmis.org
Cc: linux-trace-devel@vger.kernel.org
Subject: [PATCH v3 0/3] Changes in few libtraceevent APIs
Date: Thu,  1 Aug 2019 10:49:56 +0300	[thread overview]
Message-ID: <20190801074959.22023-1-tz.stoyanov@gmail.com> (raw)

Before releasing libtraceevent as a standalone library, few
APIs must be changed:
 - Event printing interface is redesigned, to be more simple
   and user friendly. Now the tep_print_event() API can be used 
   to print various event information. All other event print APIs
   are removed.
 - Changed the user's plugin directory to 
   ~/.local/lib/traceevent/plugins/ to be XDG compliant.

[
 v3 changes:
   - The user's plugin directory is changed to ~/.local/lib/traceevent/plugins/,
     as Patrick McLean suggested.
   - New tep_print_event() item is added - TEP_PRINT_INFO_RAW, to print
     event information in raw format.
   - Removed prefix "tep_" from newly added static functions and few
     other changes, suggested by Steven Rostedt.
]
 
Tzvetomir Stoyanov (3):
  tools/lib/traceevent, tools/perf: Changes in tep_print_event_* APIs
  tools/lib/traceevent: Remove tep_register_trace_clock()
  tools/lib/traceevent: Change user's plugin directory

 tools/lib/traceevent/Makefile            |   6 +-
 tools/lib/traceevent/event-parse-api.c   |  40 ---
 tools/lib/traceevent/event-parse-local.h |   6 -
 tools/lib/traceevent/event-parse.c       | 333 +++++++++++++----------
 tools/lib/traceevent/event-parse.h       |  30 +-
 tools/lib/traceevent/event-plugin.c      |   2 +-
 tools/perf/builtin-kmem.c                |   3 +-
 tools/perf/util/sort.c                   |   3 +-
 tools/perf/util/trace-event-parse.c      |   2 +-
 9 files changed, 207 insertions(+), 218 deletions(-)

-- 
2.21.0


             reply	other threads:[~2019-08-01  7:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-01  7:49 Tzvetomir Stoyanov (VMware) [this message]
2019-08-01  7:49 ` [PATCH v3 1/3] tools/lib/traceevent, tools/perf: Changes in tep_print_event_* APIs Tzvetomir Stoyanov (VMware)
2019-09-02  8:16   ` [tip: perf/core] libtraceevent, perf tools: " tip-bot2 for Tzvetomir Stoyanov
2019-08-01  7:49 ` [PATCH v3 2/3] tools/lib/traceevent: Remove tep_register_trace_clock() Tzvetomir Stoyanov (VMware)
2019-09-02  8:16   ` [tip: perf/core] libtraceevent: " tip-bot2 for Tzvetomir Stoyanov
2019-08-01  7:49 ` [PATCH v3 3/3] tools/lib/traceevent: Change user's plugin directory Tzvetomir Stoyanov (VMware)
2019-09-02  8:16   ` [tip: perf/core] libtraceevent: Change users " tip-bot2 for 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=20190801074959.22023-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).