On Fri, 2005-03-04 at 23:57 +0100, Pavel Machek wrote: > What prevents driver from being run on another CPU, maybe just doing > mdelay() between hardware accesses?
Almost all drivers that I know have some sort of locking. Nothing nasty about it. Besides, you can't expect everything to be as simple as putting two bit of lego together, the problem isn't simple. If an IOs gets there out of sync, it's a non-issue, it will most probably just return all 1's, and if using Seto proposed functions, the bit of code doing it will "know" there was an error and will stop. But a driver notified of errors that, typically, triggered a slot isolation like on pSeries, will have to wait for all IOs to complete anyway, stop everything, so that the slot can be reset. I think you are raising a non-issue. Ben. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
