Re: [PATCH] printing support for MCA/INIT

From: Hidetoshi Seto <seto.hidetoshi_at_jp.fujitsu.com>
Date: 2006-06-08 20:27:18
Keith Owens wrote:
> Also consider that crash dump may be invoked from MCA/INIT.  The
> various crash dump analysis tools all expect to find the messages in
> the dmesg buffer in the dump.  Adding a special print buffer just for
> MCA/INIT means changing all the crash dump tools to look in two places.

I doubt it.
If you successfully get the crash dump, you will be able to see where
the dump was invoked, possibly with short string describing why the dump
was invoked. Then these short messages from MCA/INIT handler are not so
important thing even still you can look in special buffer.

Or export ia64_mlogbuf_break and use it to flush special buffer to
dmesg buffer before you invoke crash dump.

> It is possible to make the core of printk completely NMI safe.  We can
> make it lockless, or retain the locks but detect that there is no
> movement and ignore the lock.  The SN2 serial console does the latter,
> see drivers/serial/sn_console.c::sn_sal_console_write().  This means
> that SN2 machines can safely write to the console even from MCA/INIT.
> printk can use the same technique to lock access to its print buffer.

Latter will not be acceptable. How long we can pause the system to
recover a TLB error which can be swept in a second?

I have no idea to make printk lockless. Really can we?

Still I like patching as a workaround better than waiting incredible
feature in future.

H.Seto

-
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 Thu Jun 08 20:26:16 2006

This archive was generated by hypermail 2.1.8 : 2006-06-08 20:26:26 EST