Robert Lowery wrote:
>
> >I question this because it is too risky to apply. There is no way any
> >distribution or production system could ever consider applying the
> >preempt kernel and ship it in its next kernel update 2.4. You never know
> >if a driver will deadlock because it is doing a test and set bit busy
> >loop by hand instead of using spin_lock and you cannot audit all the
> >device drivers out there.
>
> Quick question from a kernel newbie.
>
> Could this audit be partially automated by the Stanford Checker? or would
> there
> be too many false positives from other similar looping code?
>
> -Robert
Sounds like a REALLY good thing (tm) to me. How do we get them
interested?
-- George george@mvista.com High-res-timers: http://sourceforge.net/projects/high-res-timers/ Real time sched: http://sourceforge.net/projects/rtsched/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Tue Jan 15 2002 - 21:00:47 EST