Geert,
So we could stop blocking further interrupts in multi platform kernels. How
much of a performance hit will this be on say a stock Falcon or TT?
That's 15000 - 3 more interrupts per second.
Yep, but pretty much all NOP. Is the interrupt entry/return that much of
a hassle these days?
On Fri, Aug 2, 2013 at 7:26 PM, Michael Schmitz wrote:
>>> What is the cause of the problem exactly - the hsync handler changing the
>>> IPL to block out further interrupts, whenever it is called for the first
>>> time after interrupts are enabled? We could stop doing that on
>>> multi-platform ke
Hi Geert,
Didn't we have that sorted out earlier? I seem to recall this has surfaced
before.
You mean commit 94674cd5299e825cb31979c3b9a4c1a3e6074839
("m68k: Correct the Atari ALLOWINT definition")? That was a related but
slightly different problem.
That's proably what I recalled, yes.
What
On Fri, Aug 2, 2013 at 11:08 AM, Michael Schmitz
wrote:
>>> [0.16] WARNING: at /root/linux-3.10.1/init/main.c:698
>>> do_one_initcall+0x12e/0x13a()
>>> [0.16] initcall param_sysfs_init+0x0/0x1a4 returned with disabled
>>> interrupts
>>>
>>> This seems to happen for several initcall
Hi Geert,
[0.16] WARNING: at /root/linux-3.10.1/init/main.c:698
do_one_initcall+0x12e/0x13a()
[0.16] initcall param_sysfs_init+0x0/0x1a4 returned with
disabled interrupts
This seems to happen for several initcalls. Geert et al,
can you have a look at them, they’re scary ☺
Thorsten,
I’d like the m68k people to read the whole eMail and test
https://www.freewrt.org/~tg/dp/dists/hacks/dirty/Crossbuilt/linux/
linux-image-3.10-0+m68k.1-m68k_3.10.1-1+m68k.1_m68k.deb
on all their boxen, at least Amiga/Atari/Macintosh
Not anytime soon - the boot disk on my Falcon just
6 matches
Mail list logo
