[EMAIL PROTECTED] said:
> Jeff, any objections against adding this change to UML at some point?
No, not at all. I just need to understand what CONFIG_PREEMPT requires of
UML.
>From a quick read of Documentation/preempt-locking.txt, this looks like it's
implementing Rule #3 (unlock by the same task that locked), which looks fine.
Jeff
-
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/
