Thank you for your remarks.
The MCAs/INITs are rare.One hopes. :-)
Should you have a single unrecoverable MCA, the game is over. Neither the original code, nor mine can log it before the machine is re-booted / halted. Only the recovered ones play. It is safe to continue after the recovered ones. You need these logs to be alerted and to program the maintenance. Both the original code and mine can "swallow" about 1 recovered event / minute, and tolerate a "burst" of 2 or IA64_MAX_MCA_INIT_BUFS events. The probability to have more than that _independent_ events in a small time frame is very very low. Therefore you can afford losing events of the same "burst".
There is no use wasting much permanent resources.Sometimes a necessary evil. Normal memory allocation routines cannot be called from MCA/INIT context.
This is why I pre-allocate IA64_MAX_MCA_INIT_BUFS buffers.
Even if the system is going down it is still nice to try to go down gracefully. Taking a system dump and logging as much as possible is usefull, too.
You (may want to) take a dump if the event is not recovered. In such e case, neither the original code, nor mine does any useful thing :-)
In the case where all the CPUs are INITed, what happens? Does this assume only one CPU at a time processes/logs records?
I have not added my code to the INIT handler yet.
From the SAL spec.: INIT reason code:
0 = Received INIT signal on this processor for reasons other than machine
check rendezvous and CrashDump switch assertion.
1 = Received INIT signal on this processor during machine check rendezvous.
2 = Received INIT signal on this processor due to CrashDump switch assertion.
I think there is no use to log anything in the cases of MCA rendezvous
and CrashDump (that can actually dump, call the KDB).
I intend to log the "other reasons" only, by the monarch only.
The code does not assume that the rendezvous always works.Could you explain. Do you mean MCA/INIT rendezvous?
Yes. If everything goes fine, only one CPU, the monarch logs. (See also the comment in the INIT handler saying: FIXME: Workaround for broken proms that drive all INIT events as monarchs.) However, the SAL spec. allows in "OS_MCA Hand-off State" that "Rendezvous of other processors was required but was unsuccessful on one or more processors." E.g. two non-global MCAs can happen on two CPUs, both of them can start to execute the MCA handler, thinking that each of them is monarch. My code should survive... Thanks, Zoltan -- To unsubscribe from this list: send the line "unsubscribe linux-ia64" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
|