| Re: [hatari-devel] Issues with cache hits/misses? |
[ Thread Index |
Date Index
| More lists.tuxfamily.org/hatari-devel Archives
]
Hi,
On sunnuntai 24 toukokuu 2015, Nicolas Pomarède wrote:
> Le 24/05/2015 21:35, Eero Tamminen a écrit :
> > Both TOS4 and EmuTOS have:
> > CACR 00003111
> >
> > Looking at Mikro's post here:
> > http://dhs.nu/bbs-coding/index.php?request=3608
> >
> > It seems that in addition to both caches being enabled,
> > burst mode is also enabled for both.
> >
> > But still there are no d-cache hits/misses reported...
>
> when Hatari starts in this mode, it should print sthg like :
>
> CPU cycleunit: 256 (0.500)
> run_1
> CPU reset
>
> what run_xx value do you have ? Did you try using cycle exact mode ?
It prints "run_2ce".
That's with following system settings:
- Falcon emulation
- 68030
- prefetch mode
- cycle exact
Same thing with "run_2p" i.e. "--cpu-exact no".
> Movem should be the instruction with the maximum possible cache access,
> with up to 16 long words being read, this means a possible max of 32
> d-cache accesses, so printing a warning for value above 5 or 6 will
> certainly print too much useless warnings.
The warning is there just temporarily, to help in verifying
that things work OK. After it's been verified that things
work OK, it can be disabled/removed.
- Eero