Re: [ANNOUNCE] trace-cmd v2.8

Bhaskar Chowdhury <[email protected]>
Newsgroups org.kernel.vger.linux-trace-users,org.kernel.vger.linux-kernel,org.kernel.vger.linux-rt-users,org.kernel.vger.linux-trace-devel
Message-ID <20190613230106.GA11097@UbuntuLinux>
Cool ! Steven :)
On 12:20 Thu 13 Jun , Steven Rostedt wrote:
>
>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.
signature.asc (application/pgp-signature, 488 B)
-----BEGIN PGP SIGNATURE-----

iQEzBAABCgAdFiEEnwF+nWawchZUPOuwsjqdtxFLKRUFAl0C1a4ACgkQsjqdtxFL
KRXR2wgAxiCv+t41nkzBpXWshoOvmJse582RwQcoz+WJJlG8zEXAomJnUq4qNhd9
SErkP2Ql3kPvBuoXhIFMyHf1dkl/0McAmQKI3iHhLc2411Tq3u/8Gm9Fi3qFzQ+g
LMrDOG5IkLJfeI8kgrIx7Xr0BGGAqwnrYDKpyZIG/mLddaepAfNjMOZPSzD6V3mB
9IDihfmj0YiUcB3BkFFGwL6LcAkZ5GajJ+QGOeKYPNRaZpCFueG62Xp1nOZOYja4
oIR12fja0HK1B0aJoqSfDSuFXVPE/brJEKnWlkeFtpIGeCGizIVN2kpvIY95n5dN
emN9rVoDNwthCphA+Z7hqYkETNUjBQ==
=8f84
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.