2017-06-02 17:31+0200, Andrew Jones: > After posting on_cpu() support yesterday I thought of some potential > issues. > 1) cpu0 was the only cpu allowed to call on_cpus, and no cpu was > allowed to call on_cpu on cpu0 (as it'll never idle). > 2) deadlocks are easy with this idle state scheduling model, but > also easy to detect, so we should. > > v2: > - fix race in cpu_wait() by ordering set/check correctly Applied, thanks.
