Some issues I found with KernelShark 1.0 prototype

Some issues I found with KernelShark 1.0 prototype

[Steven Rostedt]

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

Re: Some issues I found with KernelShark 1.0 prototype

[Yordan Karadzhov (VMware)]

Hi Steven,

On 25.09.2018 19:33, Steven Rostedt wrote:
> 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 

OK, I will tray implementing this.

> 
>   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.

Yes, this is trivial. We just have to find a way to make it intuitive.
Maybe adding another button?


>   3. We need a "File exists, do you want to overwrite" type dialog box
>      when saving a session over a file that already exists.

Hmm, I thought that it asks before overwriting. I will check this again.

> 
>   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.

The full path of the loaded file is shown as part of the name of the 
window. It will be "KernelShark(/some/path/somefile.dat)"

> 
>   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.
> 

There is some regression in the import/export session code. I also 
noticed some problems there. Will do a careful look.

Thanks a lot for reporting all this issues!
Looking forward to see your talk.

cheers,
Yordan


> 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
>