> On 2021-02-10, at 10:30 AM, Jaromir <m at jaromir.net> wrote:
>  I did try to use #yield but the primitive
> seems to check only the active priority queue (and assumes it can't even
> happen that higher priority processes are waiting while a lower priority
> process is active - which is probably a reasonable assumption - if it
> weren't for the #priority: behavior). So I guess either #priority: or #yield
> should be modified.

That doesn't seem right; the primitiveYield carefully transfers control to the result of `wakeHighestPriority()` which is certainly *meant* to find the highest priority process that is runnable. It's what I wrote the original version to do nearly 20 years ago..


tim
--
tim Rowledge; tim at rowledge.org; http://www.rowledge.org/tim
Hackers have kernel knowledge.