Re: profiling 68k code with an emulator (was: meeting planning)
On Fri, 16 Jan 2015, Eero Tamminen wrote:
> Hi,
>
> And the reason why this could be relevant for debian-68k
> is the Hatari profiler used to find out & optimize all
> the bottlenecks in that game:
> http://hg.tuxfamily.org/mercurialroot/hatari/hatari/raw-
> file/tip/doc/manual.html#Profiling
>
> That profiler might also be useful in profiling some
> 68k Linux performance issues (or hangs).
That sounds very promising. Profiling may confirm suspicions about the
need for a VDSO.
>
> Earlier Linux didn't work with Hatari emulator because its
> (030) MMU emulation wasn't complete. Now it should be.
Nice!
>
> ... I'd like to try it with Hatari to see whether there are any further
> issues that need to be fixed on Hatari side before 68k Linux runs in it.
I suspect there may be issues on the Linux side relating to 68030; for a
some time now I've been observing short lock-ups on 68030 (actually
PowerBook 180). I get a lot of BUG splats in the kernel logs when I
enable,
CONFIG_LOCKUP_DETECTOR=y
CONFIG_DETECT_HUNG_TASK=y
CONFIG_DEBUG_SPINLOCK=y
CONFIG_DEBUG_ATOMIC_SLEEP=y
CONFIG_DEBUG_BUGVERBOSE=y
Unfortunately I have too many other bugs to chase right now, but I'd be
interested to know if you see any issues like this on Hatari or other
platforms.
--
>
>
> - Eero
Reply to: