On 2017-06-16 18:58:15 [+0200], To Daniel Bristot de Oliveira wrote:
> Any objections?
Okay, taking this for v4.9 then (mostly the same, except for one
superfluous check):
Subject: [PATCH] sched/migrate disable: handle updated task-mask mg-dis section
If task's cpumask changes while in the task
On 2017-06-16 18:58:15 [+0200], To Daniel Bristot de Oliveira wrote:
> Any objections?
Okay, taking this for v4.9 then (mostly the same, except for one
superfluous check):
Subject: [PATCH] sched/migrate disable: handle updated task-mask mg-dis section
If task's cpumask changes while in the task
On 2017-06-16 12:39:48 [+0200], Daniel Bristot de Oliveira wrote:
> In the case of an affinity change during a migrate_disable section,
> __set_cpus_allowed_ptr will not try to move the task from a CPU
> in which it cannot execute anymore.
>
> So, after enabling migration, if the current task
On 2017-06-16 12:39:48 [+0200], Daniel Bristot de Oliveira wrote:
> In the case of an affinity change during a migrate_disable section,
> __set_cpus_allowed_ptr will not try to move the task from a CPU
> in which it cannot execute anymore.
>
> So, after enabling migration, if the current task
In the case of an affinity change during a migrate_disable section,
__set_cpus_allowed_ptr will not try to move the task from a CPU
in which it cannot execute anymore.
So, after enabling migration, if the current task cannot execute in
the current CPU anymore, migrate it away.
Signed-off-by:
In the case of an affinity change during a migrate_disable section,
__set_cpus_allowed_ptr will not try to move the task from a CPU
in which it cannot execute anymore.
So, after enabling migration, if the current task cannot execute in
the current CPU anymore, migrate it away.
Signed-off-by:
6 matches
Mail list logo