On Wed, Jul 10, 2002 at 03:16:21PM +0100, Jon Burgess wrote:
> This may be caused by the cache routines running from the a cached kseg0, it
> looks like it can be fixed by making sure that the are always called via
> KSEG1ADDR(fn) which looks like it could be done with a bit of fiddling of the
> setup_cache_funcs code. I have included a patch below which starts this, but I
> haven't caught all combinations of how the routines are called.
While that could be done it's not a good idea; running code in KSEG1 is
> Alternatively it could be a CP0 pipeline interaction of the cache instruction
> and mfc0 but I can't find anything detailed about it. I thought this was the
> problem initially and have included a patch below which adds an extra nop.
Running uncached is so slow that the pipeline will slip and stall basically
every cycle which should get you around the hazard. Anyway, there's no
hazard for mfc0 documented in the MIPS32 spec so this smells like a silicon
Which particular CPU and revision are you using?