From: "Tzvetomir Stoyanov (VMware)" <tz.stoyanov@gmail.com>
To: rostedt@goodmis.org
Cc: linux-trace-devel@vger.kernel.org
Subject: [PATCH v4 0/8] trace-cmd convert
Date: Thu, 11 Nov 2021 17:12:20 +0200 [thread overview]
Message-ID: <20211111151228.86922-1-tz.stoyanov@gmail.com> (raw)
A new trace-cmd subcommand is introduced:
trace-cmd convert -i <input file> -o <output file>
The command converts trace file between different versions. There are two
parameters for controlling the type of the output file:
--file-version < 6 / 7>
--compression < none / any / name of the desired compression algorithm >
This patch-set depends on:
"trace-cmd fixes and clean-ups" patch set.
"Refactor APIs for creating output handler" patch set.
"Refactor the logic for writing trace data in the file" patch set.
"Trace file version 7 - sections" patch set.
"Trace file version 7 - compression" patch set.
v4 changes:
- Rebased on top of the latest master.
v3 changes:
- Rebased on top of the latest master.
v2 changes:
- fixed issues of split and convert commands with some corner cases
Tzvetomir Stoyanov (VMware) (8):
trace-cmd library: Use output handler when copying data from input
file
trace-cmd library: Handle version 7 files when copying headers between
files
trace-cmd library: Copy CPU count between trace files
trace-cmd library: New API to copy buffer description between trace
files
trace-cmd library: New API to copy options between trace files
trace-cmd library: New API to copy trace data between trace files
trace-cmd library: Extend tracecmd_copy() API
trace-cmd: Add new subcommand "convert"
.../include/private/trace-cmd-private.h | 15 +-
lib/trace-cmd/include/trace-cmd-local.h | 13 +
lib/trace-cmd/trace-input.c | 698 +++++++++++++++---
lib/trace-cmd/trace-output.c | 122 ++-
lib/trace-cmd/trace-util.c | 8 +-
tracecmd/Makefile | 1 +
tracecmd/include/trace-local.h | 2 +
tracecmd/trace-cmd.c | 1 +
tracecmd/trace-convert.c | 106 +++
tracecmd/trace-restore.c | 2 +-
tracecmd/trace-split.c | 2 +-
tracecmd/trace-usage.c | 13 +
12 files changed, 879 insertions(+), 104 deletions(-)
create mode 100644 tracecmd/trace-convert.c
--
2.33.1
next reply other threads:[~2021-11-11 15:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-11 15:12 Tzvetomir Stoyanov (VMware) [this message]
2021-11-11 15:12 ` [PATCH v4 1/8] trace-cmd library: Use output handler when copying data from input file Tzvetomir Stoyanov (VMware)
2021-11-11 15:12 ` [PATCH v4 2/8] trace-cmd library: Handle version 7 files when copying headers between files Tzvetomir Stoyanov (VMware)
2021-11-11 15:12 ` [PATCH v4 3/8] trace-cmd library: Copy CPU count between trace files Tzvetomir Stoyanov (VMware)
2021-11-11 15:12 ` [PATCH v4 4/8] trace-cmd library: New API to copy buffer description " Tzvetomir Stoyanov (VMware)
2021-11-11 15:12 ` [PATCH v4 5/8] trace-cmd library: New API to copy options " Tzvetomir Stoyanov (VMware)
2021-11-11 15:12 ` [PATCH v4 6/8] trace-cmd library: New API to copy trace data " Tzvetomir Stoyanov (VMware)
2021-11-11 15:12 ` [PATCH v4 7/8] trace-cmd library: Extend tracecmd_copy() API Tzvetomir Stoyanov (VMware)
2021-11-11 15:12 ` [PATCH v4 8/8] trace-cmd: Add new subcommand "convert" 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=20211111151228.86922-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).