From: Steven Rostedt <rostedt@goodmis.org>
To: LKML <linux-kernel@vger.kernel.org>,
linux-rt-users <linux-rt-users@vger.kernel.org>,
"linux-trace-users@vger.kernel.org"
<linux-trace-users@vger.kernel.org>,
Linux Trace Devel <linux-trace-devel@vger.kernel.org>,
troyengel@gmail.com, amikhak@wirelessfabric.com,
valentin.schneider@arm.com, Patrick McLean <chutzpah@gentoo.org>,
John Kacur <jkacur@redhat.com>,
Yordan Karadzhov <y.karadz@gmail.com>,
Tzvetomir Stoyanov <tstoyanov@vmware.com>,
Slavomir Kaslev <kaslevs@vmware.com>,
howaboutsynergy@pm.me, Bas van Dijk <v.dijk.bas@gmail.com>
Subject: [ANNOUNCE] KernelShark 1.0
Date: Fri, 26 Jul 2019 09:57:30 -0400 [thread overview]
Message-ID: <20190726095730.0674d81d@gandalf.local.home> (raw)
Hi Folks,
It is finally official. We have finished and released KernelShark 1.0.
http://www.kernelshark.org
It's a completely new rewrite in Qt from the older KernelShark that was
written in GTK. It's faster, it's more extensible, and easier to use.
For how to use KernelShark please read:
http://www.kernelshark.org/Documentation.html
I would like to thank my team that worked tirelessly on this, and
especially Yordan Karadzhov who did the majority of the work, and even
came up with several algorithms to speed up the handling. I will be
transitioning maintainership off to Yordan. We will currently be
co-maintainers, but eventually we will be splitting KernelShark out of
the trace-cmd.git repo and into its own. At that time, Yordan will be
the main maintainer of the project.
Download it and try it out.
Now we can finally start working on KernelShark 2.0 that's going to be
another huge improvement!
Enjoy!
-- Steve
next reply other threads:[~2019-07-26 13:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-26 13:57 Steven Rostedt [this message]
2019-07-26 14:49 ` [ANNOUNCE] KernelShark 1.0 Bhaskar Chowdhury
2019-07-26 14:52 ` Steven Rostedt
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=20190726095730.0674d81d@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=amikhak@wirelessfabric.com \
--cc=chutzpah@gentoo.org \
--cc=howaboutsynergy@pm.me \
--cc=jkacur@redhat.com \
--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=troyengel@gmail.com \
--cc=tstoyanov@vmware.com \
--cc=v.dijk.bas@gmail.com \
--cc=valentin.schneider@arm.com \
--cc=y.karadz@gmail.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).