From: "Tzvetomir Stoyanov (VMware)" <tz.stoyanov@gmail.com>
To: rostedt@goodmis.org
Cc: linux-trace-devel@vger.kernel.org
Subject: [PATCH 0/8] Changes to trace-cmd logs
Date: Wed, 28 Apr 2021 10:41:41 +0300 [thread overview]
Message-ID: <20210428074149.757163-1-tz.stoyanov@gmail.com> (raw)
Recently changes in traceevent and tracefs libraries were introduced: log
levels and new APIs to modify them. As trace-cmd library uses traceevent
and tracefs libraries, those changes affect trace-cmd as well.
These changes depend on "[PATCH 0/2] Add API to set severity to tracefs
library logs"
https://lore.kernel.org/linux-trace-devel/20210428073212.756329-1-tz.stoyanov@gmail.com/
Tzvetomir Stoyanov (VMware) (8):
trace-cmd library: Use tep_vprint() for logs
trace-cmd library: Add tracecmd_info() log function
trace-cmd library: Add log levels
trace-cmd library: Document the API for log levels
trace-cmd library: Renamed tracecmd_fatal() to tracecmd_critical()
trace-cmd library: Set debug log level in debug mode
trace-cmd report: Set the log level with -V and -q options
trace-cmd: Add new function to set log level
Documentation/libtracecmd/libtracecmd-log.txt | 78 +++++++++++++++++++
Documentation/libtracecmd/libtracecmd.txt | 3 +
include/trace-cmd/trace-cmd.h | 2 +
lib/trace-cmd/include/trace-cmd-local.h | 4 +-
lib/trace-cmd/trace-input.c | 14 ++--
lib/trace-cmd/trace-plugin.c | 2 +-
lib/trace-cmd/trace-util.c | 47 +++++++++--
python/ctracecmd.i | 13 +---
tracecmd/include/trace-local.h | 2 +
tracecmd/trace-cmd.c | 55 +++++++++----
tracecmd/trace-read.c | 2 +
tracecmd/trace-record.c | 14 ++++
12 files changed, 194 insertions(+), 42 deletions(-)
create mode 100644 Documentation/libtracecmd/libtracecmd-log.txt
--
2.30.2
next reply other threads:[~2021-04-28 7:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-28 7:41 Tzvetomir Stoyanov (VMware) [this message]
2021-04-28 7:41 ` [PATCH 1/8] trace-cmd library: Use tep_vprint() for logs Tzvetomir Stoyanov (VMware)
2021-04-28 7:41 ` [PATCH 2/8] trace-cmd library: Add tracecmd_info() log function Tzvetomir Stoyanov (VMware)
2021-04-28 7:41 ` [PATCH 3/8] trace-cmd library: Add log levels Tzvetomir Stoyanov (VMware)
2021-04-28 7:41 ` [PATCH 4/8] trace-cmd library: Document the API for " Tzvetomir Stoyanov (VMware)
2021-04-28 7:41 ` [PATCH 5/8] trace-cmd library: Renamed tracecmd_fatal() to tracecmd_critical() Tzvetomir Stoyanov (VMware)
2021-04-28 7:41 ` [PATCH 6/8] trace-cmd library: Set debug log level in debug mode Tzvetomir Stoyanov (VMware)
2021-04-28 7:41 ` [PATCH 7/8] trace-cmd report: Set the log level with -V and -q options Tzvetomir Stoyanov (VMware)
2021-04-28 7:41 ` [PATCH 8/8] trace-cmd: Add new function to set log level Tzvetomir Stoyanov (VMware)
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=20210428074149.757163-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).