Thanks, all. I was pleased to hear many thought in active developer's mind. I want to check some in MCA recovery. Here is some steps, roughly say: - Stop whole system on MCA even if kernel not suffered. - Keep working except the suffered application. - Keep working, and give a chance to self-rehabilitation for the suffered application. Just now, Linux is making an effort to step up the second from the first. It also seems there are some key procedures, such as: - Specify process/thread(s) must be killed - Specify damaged resources (for example, poisoned pages) To specify affected ones, OS requires: - Physical address (and if possible, Virtual address) of the offending operation. - Interruption must be synchronized. - States in registers when interrupted. Is it wrong? ------ H.Seto <seto.hidetoshi@jp.fujitsu.com> - 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.htmlReceived on Thu Nov 6 07:12:01 2003
This archive was generated by hypermail 2.1.8 : 2005-08-02 09:20:20 EST