* Re: [9front] Re: tsemaquire
@ 2017-05-18 9:29 cinap_lenrek
0 siblings, 0 replies; 2+ messages in thread
From: cinap_lenrek @ 2017-05-18 9:29 UTC (permalink / raw)
To: 9front
basically, portclock dequeued the timer and then called the timer function.
so just calling timerdel() isnt enougth to disable the timer. as the timer
could already have been dequeued and running. the fix i linked keeps track
of the completion of the timer function, making timerdel() wait until it
returned in case it got run.
--
cinap
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [9front] Re: tsemaquire
@ 2017-05-18 9:22 cinap_lenrek
0 siblings, 0 replies; 2+ messages in thread
From: cinap_lenrek @ 2017-05-18 9:22 UTC (permalink / raw)
To: 9front
its a race condition. timerdel() doesnt guarantee that the timer function would
still fire (from another cpu).
http://code.9front.org/hg/plan9front/rev/381f1cb08002
--
cinap
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2017-05-18 9:29 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-05-18 9:29 [9front] Re: tsemaquire cinap_lenrek
-- strict thread matches above, loose matches on Subject: below --
2017-05-18 9:22 cinap_lenrek
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).