From: Steven Rostedt <rostedt@goodmis.org>
To: Yordan Karadzhov <y.karadz@gmail.com>
Cc: linux-trace-devel@vger.kernel.org
Subject: Some issues I found with KernelShark 1.0 prototype
Date: Tue, 25 Sep 2018 12:33:49 -0400 [thread overview]
Message-ID: <20180925123320.71d0d580@vmware.local.home> (raw)
Hi Yordan,
While writing my presentation I found a few slight issues that we need
to address.
1. Need to show the task in the info window when hovering over the CPU
plot between events, but not idle
2. Is there a way to do a quick zoom out. When I zoom in with a lot of
data, I find that it's quite slow to zoom back out to the original
screen.
3. We need a "File exists, do you want to overwrite" type dialog box
when saving a session over a file that already exists.
4. When restoring a session, the full path of the file being loaded
should be shown. I noticed this because I was loading a trace.dat
file from a different directory, and I wasn't sure which file it
found, as I have several trace.dat files.
5. I noticed a glitch when loading a session with both the A and B
markers are set here only one marker was shown in the list view.
I can put the session and trace.dat file someplace that you can
test this if you want.
But so far it looks great! Tomorrow I'll be presenting my talk at 11am
your time. It will hopefully be live streamed if they don't have the
issues that they had at Embedded Recipes. I'll email the list the link
when I have it.
-- Steve
next reply other threads:[~2018-09-25 22:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-25 16:33 Steven Rostedt [this message]
2018-09-26 7:22 ` Some issues I found with KernelShark 1.0 prototype Yordan Karadzhov (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=20180925123320.71d0d580@vmware.local.home \
--to=rostedt@goodmis.org \
--cc=linux-trace-devel@vger.kernel.org \
--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).