Manual Pages  — CRITICAL_ENTER

The CPU might also receive and handle interrupts within a critical section. When this occurs the interrupt exit will not result in a context switch, and execution will continue in the critical section. Thus, the net effect of a critical section on the current thread's execution is similar to running with interrupts disabled, except that timer interrupts and filtered interrupt handlers do not incur a latency penalty.

The critical_enter() and critical_exit() functions manage a per-thread counter to handle nested critical sections. If a thread is made runnable that would normally preempt the current thread while the current thread is in a critical section, then the preemption will be deferred until the current thread exits the outermost critical section.

Note that these functions do not provide any inter-CPU synchronization, data protection, or memory ordering guarantees, and thus should not be used to protect shared data structures.

These functions should be used with care as an unbound or infinite loop within a critical region will deadlock the CPU. Also, they should not be interlocked with operations on mutexes, sx locks, semaphores, or other synchronization primitives, as these primitives may require a context switch to operate. One exception to this is that spin mutexes include a critical section, so in certain cases critical sections may be interlocked with spin mutexes.