From: Steven Rostedt <rostedt@goodmis.org>
To: LKML <linux-kernel@vger.kernel.org>,
Linux Trace Devel <linux-trace-devel@vger.kernel.org>,
"linux-trace-users@vger.kernel.org"
<linux-trace-users@vger.kernel.org>
Subject: [ANNOUNCE] trace-cmd 2.9.2
Date: Thu, 25 Mar 2021 17:23:57 -0400 [thread overview]
Message-ID: <20210325172357.6e059c31@gandalf.local.home> (raw)
I'm happy to announce trace-cmd version 2.9.2!
*** NOTICE ***
This is the last version that is self contained for interacting
with the tracefs directory and parsing the events.
The parsing of events is now a separate repository:
https://git.kernel.org/pub/scm/libs/libtrace/libtraceevent.git/
And the access to the tracefs directory is here:
https://git.kernel.org/pub/scm/libs/libtrace/libtracefs.git/
After this release, trace-cmd will depend on those repositories and
its internal copies will be removed. Please install those libraries
for future building of trace-cmd.
*** NOTICE 2 ***
KernelShark is now in its own repository (and will depend on libtracecmd
in this repo, but has not been officially released just yet, but soon!).
This is the last version that will home KernelShark in this repository.
KernelShark now lives here:
https://git.kernel.org/pub/scm/utils/trace-cmd/kernel-shark.git/
After this release, "make gui" will no longer build KernelShark.
*** END NOTICES ***
Features and user visible updates since 2.9.1:
- Will use system libraries libtraceevent and libtracefs if they are
present and will only build the local versions if they are not.
- The saved comms are stored at the end of running a trace-cmd record
to be able to get the names of what is running after they ran.
- trace-cmd clear is now instance aware.
- New trace-cmd report --ts-check option to check if timestamps are
monotonic.
- New "make uninstall" to remove an installed instance of trace-cmd
executables and libraries.
- Added make-trace-cmd.sh script as a template on how to install the
libraries and executables.
For more information, please visit https://www.trace-cmd.org.
-- Steve
reply other threads:[~2021-03-25 21:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20210325172357.6e059c31@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=linux-trace-users@vger.kernel.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).