From: Tzvetomir Stoyanov <tstoyanov@vmware.com>
To: rostedt@goodmis.org
Cc: linux-trace-devel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/5] Cleanup traceevent API and make it more consistent
Date: Wed, 27 Mar 2019 16:19:41 +0200 [thread overview]
Message-ID: <20190327141946.4353-1-tstoyanov@vmware.com> (raw)
[
v2 changes:
- Excluded patches:
"tools/lib/traceevent: Remove tep filter trivial APIs"
"tools/lib/traceevent: remove call to exit() from tep_filter_add_filter_str()"
from the series, as they are already merged.
- Dropped patch "tools/lib/traceevent: Add counter to track parsing failures",
this functionality will not be part of the traceevent library. Applications
should track parsing failures themselves.
- Few minor changes, to address Steven Rostedt comments
]
This patch series does a cleanup of traceevent implementation and APIs:
- All "pevent" function parameters and local variables are renamed to "tep".
This makes the implementation consistent with the chosen naming convention,
tep (trace event parser), and avoids any confusion with the old "pevent" name.
- Renamed a bunch of tracevent APIs, to make names consistent and descriptive.
- Unified all tep_is_... APIs to return bool value, instead of int.
Changes depend on "Few patches, related to libtracevent APIs" patchset and
should be applied on top of it.
Tzvetomir Stoyanov (5):
tools/perf,tools/lib/traceevent: Make traceevent APIs more consistent
tools/lib/traceevent: Rename input arguments of libtraceevent APIs
from pevent to tep
tools/perf,tools/lib/traceevent: Rename "pevent" member of struct
tep_event to "tep"
tools/perf,tools/lib/traceevent: Rename "pevent" member of struct
tep_event_filter to "tep"
tools/lib/traceevent: Rename input arguments and local variables of
libtraceevent from pevent to tep
tools/lib/traceevent/event-parse-api.c | 152 ++--
tools/lib/traceevent/event-parse-local.h | 6 +-
tools/lib/traceevent/event-parse.c | 811 +++++++++---------
tools/lib/traceevent/event-parse.h | 130 +--
tools/lib/traceevent/event-plugin.c | 32 +-
tools/lib/traceevent/parse-filter.c | 46 +-
tools/lib/traceevent/plugin_cfg80211.c | 8 +-
tools/lib/traceevent/plugin_function.c | 14 +-
tools/lib/traceevent/plugin_hrtimer.c | 12 +-
tools/lib/traceevent/plugin_jbd2.c | 12 +-
tools/lib/traceevent/plugin_kmem.c | 32 +-
tools/lib/traceevent/plugin_kvm.c | 48 +-
tools/lib/traceevent/plugin_mac80211.c | 8 +-
tools/lib/traceevent/plugin_sched_switch.c | 18 +-
tools/lib/traceevent/plugin_scsi.c | 8 +-
tools/lib/traceevent/plugin_xen.c | 8 +-
tools/perf/builtin-kmem.c | 2 +-
tools/perf/util/data-convert-bt.c | 4 +-
tools/perf/util/python.c | 2 +-
.../util/scripting-engines/trace-event-perl.c | 2 +-
.../scripting-engines/trace-event-python.c | 2 +-
tools/perf/util/trace-event-parse.c | 2 +-
tools/perf/util/trace-event-read.c | 2 +-
tools/perf/util/trace-event.c | 4 +-
24 files changed, 682 insertions(+), 683 deletions(-)
--
2.20.1
next reply other threads:[~2019-03-27 14:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-27 14:19 Tzvetomir Stoyanov [this message]
2019-03-27 14:19 ` [PATCH v2 1/5] tools/perf,tools/lib/traceevent: Make traceevent APIs more consistent Tzvetomir Stoyanov
2019-03-27 14:41 ` Steven Rostedt
2019-03-27 14:19 ` [PATCH v2 2/5] tools/lib/traceevent: Rename input arguments of libtraceevent APIs from pevent to tep Tzvetomir Stoyanov
2019-03-27 15:06 ` Steven Rostedt
2019-03-27 14:19 ` [PATCH v2 3/5] tools/perf,tools/lib/traceevent: Rename "pevent" member of struct tep_event to "tep" Tzvetomir Stoyanov
2019-03-27 14:19 ` [PATCH v2 4/5] tools/perf,tools/lib/traceevent: Rename "pevent" member of struct tep_event_filter " Tzvetomir Stoyanov
2019-03-27 14:19 ` [PATCH v2 5/5] tools/lib/traceevent: Rename input arguments and local variables of libtraceevent from pevent to tep 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=20190327141946.4353-1-tstoyanov@vmware.com \
--to=tstoyanov@vmware.com \
--cc=linux-kernel@vger.kernel.org \
--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).