From: Steven Rostedt <rostedt@goodmis.org>
To: "linux-trace-users@vger.kernel.org"
<linux-trace-users@vger.kernel.org>,
Linux Trace Devel <linux-trace-devel@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-rt-users <linux-rt-users@vger.kernel.org>,
Yordan Karadzhov <ykaradzhov@vmware.com>,
Slavomir Kaslev <kaslevs@vmware.com>,
Tzvetomir Stoyanov <tstoyanov@vmware.com>
Subject: [ANNOUNCE] trace-cmd v2.8
Date: Thu, 13 Jun 2019 12:20:35 -0400 [thread overview]
Message-ID: <20190613122035.7d19f318@gandalf.local.home> (raw)
Finally, after a long time, trace-cmd version 2.8 is released!
This will give us a path to release KernelShark 1.0 (after we fix a few
more bugs).
http://trace-cmd.org
Enjoy!
-- Steve
Features since 2.7:
o Restructure of the source directory layout
o Loading of plugins from build directory (over other locations)
o trace-cmd reset updates (restores more, and keeps tracing_on enabled)
o trace-cmd stat shows more information about the state of ftrace
o Better accuracy with trace-cmd record --date
o Version of executable now saved in trace.dat file
trace-cmd report --version, will show that version
o trace-cmd listen has a V3 protocal (V2 is no longer used)
This is a big step toward a virt-server implementation
o trace-cmd record --no-filter option added to not filter out
the trace-cmd tasks while tracing.
o Better bash completion for trace-cmd commands
o The "mono" clock is shown now in seconds
o --max-graph-depth can be used by instances
And of course a ton of fixes and clean ups.
next reply other threads:[~2019-06-13 16:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-13 16:20 Steven Rostedt [this message]
2019-06-13 23:01 ` [ANNOUNCE] trace-cmd v2.8 Bhaskar Chowdhury
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=20190613122035.7d19f318@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=kaslevs@vmware.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=linux-trace-users@vger.kernel.org \
--cc=tstoyanov@vmware.com \
--cc=ykaradzhov@vmware.com \
/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).