RE: testing mca/init patch

From: Luck, Tony <tony.luck_at_intel.com>
Date: 2005-09-02 02:43:08
Keith wrote:
>That delay is coming from your SAL, nothing I can do about it.
>
 ...
>This is wrong.  The slave INIT handler was not invoked when the monarch
>was delivered, instead the slave events were delivered _after_ the
>monarch returned to the interrupted context.  It works for me on SGI's
>SAL, all the cpus enter INIT at the same time, without any noticeable
>delay.  There is no delay nor lockout in the INIT handler code before
>it gets to the first printk, so all the delay and out of order
>execution has to be coming from your SAL.
 ...
>Because all 4 cpus are driven as slaves.  All the slaves are waiting
>for the monarch to arrive.  All of the above tells me that the OS code
>is working fine, SAL is not.

That sounds all too plausible :-(

I'll track down some SAL people ask ask them what is going on.

-Tony

-
To unsubscribe from this list: send the line "unsubscribe linux-ia64" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Received on Fri Sep 02 02:44:51 2005

This archive was generated by hypermail 2.1.8 : 2005-09-02 02:45:00 EST