>> Not all machine checks are fatal - it would be bad for us to go into
>> an infinite spin instead of executing the recovery code.
>
> Then for the time being extlog shouldn't hook into the decoder chain
> but into mce_process_work, i.e. the last should call it. Or maybe add
> another notifier which is not atomic...
I spoke too quickly. The only MCE for which we have recovery code are
those that hit in application code. So the processor that is trying to do
the printk() can't possibly be holding the locks. Other processors might
have held the lock at the time of the MCE - but they have all returned
from the handler at the time we try the printk - so they will make progess
and release the lock so that we can acquire it.
-Tony
��.n��������+%������w��{.n�����{�����ܨ}���Ơz�j:+v�����w����ޙ��&�)ߡ�a����z�ޗ���ݢj��w�f
