On Fri, Sep 29, 2000 at 11:41:57PM +1100, Anton Blanchard wrote:
> On sparc blocking interrupts does not block the reception of cpu cross
> calls, so you cannot do anything like grab locks within a called function.
So if you can't handle the IPI when you get it, set a flag and trap on the
next sti. It certainly sounds like broken hardware to me and it can be
worked around, can't it ?
Maybe we should have a version of smp_call_function that uses softirqs
(unless those are broken on sparc as well ;) ) and use the old version for
the very performance-sensitive parts only ?
Putting all tests for smp_call_function in the timer interrupt code doesn't
make any sense at all to me.
Philipp Rumpf
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sat Sep 30 2000 - 21:00:27 EST