> We already have that interface, it is called a signal. The kernel code > for handling these events has to be architecture dependent but, once > the data has been gathered and the decision made about which user > process to kill, we just send SEGV. :-) I think there is more to it, for example we should avoid re-allocating a page which has a hard error to make sure that the next user stumbles over this again. Maybe this information should also be kept accross a reboot for the same reason. Then you need some API to maintain this information, if for example a DIMM is replaced and it is not longer require to map out a page with an error. Thanks Matthias Fouquet-Lapar Core Platform Software mfl@sgi.com VNET 521-8213 Principal Engineer Silicon Graphics Home Office (+33) 1 3047 4127 - 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 Sun Nov 2 08:40:46 2003
This archive was generated by hypermail 2.1.8 : 2005-08-02 09:20:20 EST