Documentation/locking/locktypes.rst

58 On non-PREEMPT_RT kernels, local_lock functions are wrappers around
71 On non-PREEMPT_RT kernels, these lock types are also spinning locks:
94 rw_semaphores have a special interface which allows non-owner release for
103 PI has limitations on non-PREEMPT_RT kernels due to preemption and
137 On non-PREEMPT_RT kernels the implementation is fair, thus preventing
141 exist special-purpose interfaces that allow non-owner release for readers.
164 On non-PREEMPT_RT kernels local_lock operations map to the preemption and
202 per-CPU data structures on a non PREEMPT_RT kernel.
229 On a non-PREEMPT_RT kernel spinlock_t is mapped to raw_spinlock_t and has
247    Non-PREEMPT_RT kernels disable preemption to get this effect.
255  - Tasks holding a spinlock_t do not migrate.  Non-PREEMPT_RT kernels
261    task-state rules apply to all kernel configurations.  Non-PREEMPT_RT
278    blocked until the lock becomes available.  Therefore, when a non-lock
290 					non lock wakeup
304 Non-PREEMPT_RT kernels implement rwlock_t as a spinning lock and the
331 implications. For example, on a non-PREEMPT_RT kernel the following code
344 PREEMPT_RT and non-PREEMPT_RT kernels::
372 On a non-PREEMPT_RT kernel this works correctly, but on a PREEMPT_RT kernel
403 have a few implications.  For example, on a non-PREEMPT_RT kernel the
430 This is correct code on a non-PREEMPT_RT kernel, but on a PREEMPT_RT kernel
442 On a non-PREEMPT_RT kernel migrate_disable() maps to preempt_disable()
459 While correct on a non-PREEMPT_RT kernel, this breaks on PREEMPT_RT because
471 On a non-PREEMPT_RT kernel this protects against reentrancy by disabling
482 allocating memory.  Thus, on a non-PREEMPT_RT kernel the following code
491 while holding normal non-raw spinlocks because they do not disable