cirno/plan9front
1
0
Fork 0
mirror of git://git.9front.org/plan9front/plan9front synced 2025-01-12 11:10:06 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

kernel: never do sched() in unlock() when not in "Running" state.

Browse source 
Some callers of unlock change the process state
(such as qlock()) which means they are committed
to calling sched() anyway, so no ned to call it
internally.
This commit is contained in:
cinap_lenrek 2024-01-05 01:58:37 +00:00
parent 381da3192f
commit 39321d74d8
1 changed files with 6 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

12
sys/src/9/port/taslock.c
View file

@ -204,13 +204,13 @@ unlock(Lock *l)
coherence();
l->key = 0;
if(up && --up->nlocks == 0 && up->delaysched && islo()){
/*
* Call sched if the need arose while locks were held
* But, don't do it from interrupt routines, hence the islo() test
*/
/*
* Call sched if the need arose while locks were held
* But, don't do it from interrupt routines, hence the islo() test
*/
if(up && --up->nlocks == 0)
if(up->state == Running && up->delaysched && islo())
sched();
}
}
uintptr ilockpcs[0x100] = { [0xff] = 1 };