From: "Tzvetomir Stoyanov (VMware)" <tz.stoyanov@gmail.com>
To: rostedt@goodmis.org
Cc: linux-trace-devel@vger.kernel.org
Subject: [PATCH v4 0/6] trace-cmd fixes and clean-ups
Date: Fri, 8 Oct 2021 07:11:18 +0300 [thread overview]
Message-ID: <20211008041124.972956-1-tz.stoyanov@gmail.com> (raw)
Various trace-cmd application and library fixes, clean-ups and internal
refactoring, needed for trace file version 7 and compression changes.
v4 changes:
- Removed from the set the patches that were already merged upstream.
- Rebased on top of the latest master.
- Removed these 2 patches from the set, as they will be a separate patch
sets:
"trace-cmd library: Refactor APIs for creating output handler"
"trace-cmd library: Refactor the logic for writing trace data in the file"
- Addressed Steven's comments.
v3 changes:
- Fixed issues of split and convert commands with some corner cases.
v2 changes:
- More cleanups, forgotten in the first version.
Tzvetomir Stoyanov (VMware) (6):
trace-cmd library: Do not use local variables when reading CPU stat
option
trace-cmd library: Track maximum CPUs count in input handler
trace-cmd library: Fix possible memory leak in read_event_files()
trace-cmd library: Fix possible memory leak in read_ftrace_files()
trace-cmd library: Set the correct file state when reading file with
no kallsyms
trace-cmd library: Set the correct file state when reading file with
no ftrace printk data
lib/trace-cmd/trace-input.c | 92 ++++++++++++++++++++-----------------
1 file changed, 51 insertions(+), 41 deletions(-)
--
2.31.1
next reply other threads:[~2021-10-08 4:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-08 4:11 Tzvetomir Stoyanov (VMware) [this message]
2021-10-08 4:11 ` [PATCH v4 1/6] trace-cmd library: Do not use local variables when reading CPU stat option Tzvetomir Stoyanov (VMware)
2021-10-08 4:11 ` [PATCH v4 2/6] trace-cmd library: Track maximum CPUs count in input handler Tzvetomir Stoyanov (VMware)
2021-10-08 4:11 ` [PATCH v4 3/6] trace-cmd library: Fix possible memory leak in read_event_files() Tzvetomir Stoyanov (VMware)
2021-10-08 4:11 ` [PATCH v4 4/6] trace-cmd library: Fix possible memory leak in read_ftrace_files() Tzvetomir Stoyanov (VMware)
2021-10-08 4:11 ` [PATCH v4 5/6] trace-cmd library: Set the correct file state when reading file with no kallsyms Tzvetomir Stoyanov (VMware)
2021-10-08 4:11 ` [PATCH v4 6/6] trace-cmd library: Set the correct file state when reading file with no ftrace printk data 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=20211008041124.972956-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.