On Wed, Nov 04, 2009 at 11:16:21PM +0100, Philippe Gerum wrote:
Core 0 waits for core 1 to acknowledge the critical IPI, but that
lazybones prefers to sleep. Likely because it did not receive the IPI in
question, actually (it should raise a bit in __ipipe_cpu_sync_map, see
On Fri, 2009-11-06 at 09:10 +0100, Richard Cochran wrote:
On Wed, Nov 04, 2009 at 11:16:21PM +0100, Philippe Gerum wrote:
Core 0 waits for core 1 to acknowledge the critical IPI, but that
lazybones prefers to sleep. Likely because it did not receive the IPI in
question, actually (it should
On Fri, Nov 06, 2009 at 09:26:58AM +0100, Philippe Gerum wrote:
Ouch. I just can't believe this went unnoticed for that long... Well, no
wonder why then, the critical IPI never gets registered, so never
detected by the pipeline core in __ipipe_grab_irq. Thanks for the heads
up.
This may
On Fri, 2009-11-06 at 10:20 +0100, Richard Cochran wrote:
On Fri, Nov 06, 2009 at 09:26:58AM +0100, Philippe Gerum wrote:
Ouch. I just can't believe this went unnoticed for that long... Well, no
wonder why then, the critical IPI never gets registered, so never
detected by the pipeline core
