Keith Owens wrote: > > On Sat, 1 Nov 2003 07:39:52 +0100 ("CET), > Matthias Fouquet-Lapar <mfl@sgi.com> wrote: > >I think there should be an abstraction layer hiding the underlying > >HW implementation. I think handling for example a memory error > >by killing the affected user application, should work on any chipset > >and/or CPU architecture (if technically possible). > > 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. The problem with SEGV is that there exist applications which do strange mmap/mprot tricks and catch and retry SEGVs to implement app-level paging-like behaviour. Two examples which already run on (some ports of) Linux are: The Texas Persistent Store (open source) http://www.iam.unibe.ch/~scg/Archive/Software/FreeDB/FreeDB.23.html ObjectStore (commercial) http://www.objectstore.net/products/objectstore/index.ssp You'd have to use SIGBUS or some other signal, or add a new code to the sigcontext to allow those apps to handle the difference. Greg. -- Greg Banks, R&D Software Engineer, SGI Australian Software Group. I don't speak for SGI. - 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 Tue Nov 4 23:15:11 2003
This archive was generated by hypermail 2.1.8 : 2005-08-02 09:20:20 EST