|Re: [hatari-devel] WinUAE and 030 cache hits/misses?|
[ Thread Index |
| More lists.tuxfamily.org/hatari-devel Archives
Am Sun, 27 Jan 2013 19:41:09 +0200
schrieb Eero Tamminen <oak@xxxxxxxxxxxxxx>:
> On sunnuntai 27 tammikuu 2013, Thomas Huth wrote:
> > In cycle exact mode, the CPU core counts each cycle seperately, so
> > the global "CurrentInstrCycles" variable is not needed and not set.
> Where the CPU core keeps/counts that information in cycle exact mode?
> That information is needed by the profiler.
Since every CPU mode is doing it slightly differently, you could maybe
add a counter to cycles.c and use Cycles_GetCounter() after each
instruction to get the up-to-date cycles count.
> > And nWaitStateCycles is always cleared right before do_specialties
> > is called, so you never should see a non-zero variable here, no
> > matter which mode you are using.
> I was just checking the sum of these variables, I didn't know which
> one actually had something. I had understood that the sum of them
> is the amount of cycles spent by the instruction, isn't this correct
> when do_specialties() is called?
Just have a look at the corresponding m68k_run_xx functions. At least
nWaitStateCycles gets cleared before do_specialties is called (because
its value has already been passed to M68000_AddCycles()).