mtx: stop testing SCHEDULER_STOPPED in kabi funcs for spin mutexes
There is nothing panic-breaking to do in the unlock case and the lock case will fallback to the slow path doing the check already. MFC after: 1 week
This commit is contained in:
parent
96ff69bdc9
commit
cb00d2eba3
@ -291,9 +291,6 @@ __mtx_lock_spin_flags(volatile uintptr_t *c, int opts, const char *file,
|
||||
struct mtx *m;
|
||||
uintptr_t tid, v;
|
||||
|
||||
if (SCHEDULER_STOPPED())
|
||||
return;
|
||||
|
||||
m = mtxlock2mtx(c);
|
||||
|
||||
KASSERT(m->mtx_lock != MTX_DESTROYED,
|
||||
@ -356,9 +353,6 @@ __mtx_unlock_spin_flags(volatile uintptr_t *c, int opts, const char *file,
|
||||
{
|
||||
struct mtx *m;
|
||||
|
||||
if (SCHEDULER_STOPPED())
|
||||
return;
|
||||
|
||||
m = mtxlock2mtx(c);
|
||||
|
||||
KASSERT(m->mtx_lock != MTX_DESTROYED,
|
||||
|
Loading…
x
Reference in New Issue
Block a user