[QUESTION] Are these issues PREEMPT_RT-specific?

[Ran Hongyun]

The commit eb0d280c2751 ("eventpoll: Replace rwlock with spinlock") aims to fix:

1.Priority inversion – On PREEMPT_RT, rwlock_t readers lack priority
inheritance (PI), so a low-priority reader holding the lock can be
preempted by a medium-priority task, blocking a high-priority writer
indefinitely.

2.Stall – A reader (p_read) holding the lock can be throttled by CFS
bandwidth control and scheduled out. A writer (p_write) blocks waiting
for the lock, and a timer thread (ktimers/n) needed to replenish p_read's
runtime is blocked due to writer-fairness (286deb7ec03d). This forms a
circular dependency and stalls the system.

Are these issues PREEMPT_RT-specific? 

Any clarification would be appreciated.

Thanks,
Ran Hongyun