On 08/29/2018 08:33 AM, Dietmar Eggemann wrote:
Yes, this solves the issue for the case I described. Using 'p->sched_remote_wakeup' (WF_MIGRATED) looks more elegant than using 'p->sched_class == &fair_sched_class'.
It's confirmed that this patch solves the original issue we saw (and my test case passes for me as well). I will send this version out shortly.
