Re: [hatari-devel] DSP performance

[ Thread Index | Date Index | More lists.tuxfamily.org/hatari-devel Archives ]


> That probably explains extra 2 cycle time. (Assuming memory cycles are 
without wait-states = 2 cycles/access)

That's the real point.
On Atari, the memory access is 4 cycles, not 2 as given by the Motorola docs.

So that's why all the cycles have to be reworked for Falcon emulation, that's what I did in the static table.

Laurent


----- Mail original -----
De: "Toni Wilen" <twilen@xxxxxxxxxx>
À: hatari-devel@xxxxxxxxxxxxxxxxxxx
Envoyé: Mercredi 1 Juillet 2015 08:48:22
Objet: Re: [hatari-devel] DSP performance

> So, in instruction cache mode, NOP is 0 head, 0 tail and 2 cycles)
>
> But in non cached mode, there's one access to the bus, so the cycles
> taken by the instruction is 4 cycles, not 2 (I'll try to find again the
> rule behing this).
> That's why I recomputed the whole table by hand to have the Falcon 16
> bit bus values and not the 68030 default 32 bit bus ones

NOP is not a good generic cycle usage test case because it waits until 
all pending memory cycles are complete. Emulation ignores this (Because 
I forgot about it)

That probably explains extra 2 cycle time. (Assuming memory cycles are 
without wait-states = 2 cycles/access)






Mail converted by MHonArc 2.6.19+ http://listengine.tuxfamily.org/