Hi. > Are you meaning > > synchronous MCA is caused within an execution context, for example > a process is doing a load and hits an exception > > whereas a asynchronous MCA could happen when a line is written back > to main memory and this could happen outside of the process's context ? That's right. Thus, the platform should use data poisoning to get capacity of sending synchronous MCA instead of asynchronous MCA, even though the poisoning is not the best way. Thanks. ------ 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 Mon Nov 10 05:35:50 2003
This archive was generated by hypermail 2.1.8 : 2005-08-02 09:20:20 EST