> > hardware to hardware could have a higher priority than normal programs being
> > run. That way they're not preempted by simple programs, it would have to
> > be purposely preempted by the user.
>
> How do you know they are there. How do you detect the situation, or do you
> plan to audit every driver ?
Any driver which depends on timing is broken. 2.4.9 was happy to spend
two seconds in interrupt (console switch). So I doubt too much drivers
are broken like that.
And... The drivers were broken already. That is not reason against the
patch!
Pavel
-- (about SSSCA) "I don't say this lightly. However, I really think that the U.S. no longer is classifiable as a democracy, but rather as a plutocracy." --hpa - 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/