[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <36c3bd1a-f025-449d-9b17-8436987f4639@helsinkinet.fi>
Date: Wed, 23 Oct 2024 11:51:54 +0300
From: Eero Tamminen <oak@...sinkinet.fi>
To: Jean-Michel Hautbois <jeanmichel.hautbois@...eli.org>
Cc: linux-m68k@...ts.linux-m68k.org, linux-kernel@...r.kernel.org,
linux-trace-kernel@...r.kernel.org, rostedt@...dmis.org
Subject: Re: [PATCH RFC 1/2] m68k: Add tracirqs
Hi,
On 23.10.2024 8.53, Jean-Michel Hautbois wrote:
...
>> There's one similar site in arch/m68k/kernel/head.S
>> (ret_from_exception) where interrupts are enabled that would need a
>> similar change, if you want to enable this for all m68k.
>
> I won't be able to test it though ;-).
> I see there are a few interrupts disabling in
> arch/m68k/include/asm/entry.h too ?
I would suggest using Hatari for testing it, as that emulates real HW
more accurately than Aranym, and provides better debugging & profiling
utilities than either Aranym or real HW [1], especially for kernel side.
(Because ColdFire is close to m68k, Hatari can help in debugging also
issues that are in Linux code they share.)
Here are detailed and IMHO easy instructions on how to do that:
https://hatari.tuxfamily.org/doc/m68k-linux.txt
I'd recommend using Git HEAD of Hatari [2] for testing though, because
there was a recent fix to handling prefetch during bus errors, when 030
MMU is enabled, and without that fix, prefetch + cache emulation would
need to to be disabled for user-space to work correctly. If you disable
those (--compatible off --cycle-exact off), you can start with Hatari
version from Linux distros though...
(You can mail me directly if you have problems with Hatari. Getting
ftrace working on m68k would be interesting.)
- Eero
[1] https://hatari.tuxfamily.org/doc/debugger.html
[2] Upstream: https://git.tuxfamily.org/hatari/hatari.git/
or mirror: https://github.com/hatari/hatari/
Powered by blists - more mailing lists