Obvious bug | Usage model is a thread mmaps this file during initialization. It then | writes a 1 to the mmap'd file after it grabs the lock in its critical | section where it wants immunity from pre-emption.
You need to write it first or you can be pre-empted taking the lock before asking for immunity. Presumably you could equally use something to group tasks (say a control group of some form) and implement voluntary pre-emption within the group only when in user space. Ie they only pre-empt each other by yielding but they can be pre-empted by other tasks outside the group ? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
