Re: [hatari-devel] Opinions on Hatari profiler "user interface"?

[Laurent Sallafranque <laurent.sallafranque@xxxxxxx>]

Hi again,

> > I use it a lot now with my current new dev.
> Now you got me interested. :-)
> What kind of a project you're working on, is it related
> to Beats of Rage, or something new?

You know me by the time, I won't say anything until it's over. ;)

It's something new (not related to Beats of Rage).
It's about 60% finished and I'm already quite pleased about the result.
But it's a secret ;) (I know, a secret on a mailing list ... <:oD)


> I commited support for that, for *CPU* side:
> 	http://hg.tuxfamily.org/mercurialroot/hatari/hatari/


Great job.
I'll test it tomorrow (it's a bit too late tonight).
I'm currently working on the CPU side, so, it's no problem for the DSP 
(at least for now, but I'll see later if something is needed on this part)
And in general, the DSP code is smaller than the CPU code.

> I use those "top" count & cycles lists mainly to see where in memory
> the hotspots are and how/whether they're close together or spread out.


Actually, I've got 5 parts in my code which are cycles eater and they're 
not close to each other.
(My example was pure invention)
And it took a lot of commands to have a quick clue about the cycles 
eater instructions.
With this option, I can see in one look the main eaters and that's nice.
After, if needed, I can dig into some precise disasm, but the first 
overview is faster for a first analysis.

Best regards

Laurent



Le 03/04/2013 22:43, Eero Tamminen a écrit :
> Hi,
>
> Le 03/04/2013 21:09, Laurent Sallafranque a écrit :
> > I use it a lot now with my current new dev.
> Now you got me interested. :-)
>
> What kind of a project you're working on, is it related
> to Beats of Rage, or something new?
>
>
> > Would it be possible to add the instruction disasm just after the PC,
> > count: and number of hits
> >
> > Something like :
> > > profile counts
> > addr:        count:
> > 0x05ce14    5.38%    134638        move.l    d0,(a0)
> > 0x05ce18    5.38%    134638        nop
> ...
>
> I commited support for that, for *CPU* side:
> 	http://hg.tuxfamily.org/mercurialroot/hatari/hatari/
>
> With the current *DSP* disassembler, its only possible to have
> the disassembly on its own line, but that would look pretty messy,
> especially as DSP disassembly includes also address and profiling
> information, so I left that out.
>
>
> > > With this, I could see in one look which instructions are concerned
> > > instead of doing many times
> > > d $05ce14
> > > d $05ce26
> > > d $05ce20
> > > ...
> I use those "top" count & cycles lists mainly to see where in memory
> the hotspots are and how/whether they're close together or spread out.
> Then I just start disassembling from somewhere slightly before
> the hotspot (to see how code arrives in the hotspot).
>
> I.e. in above case dissassembling forward from the first instruction would
> quickly show all the relevant instructions.  I hope doing something like
> that is enough for the DSP side...
>
>
> 	- Eero