hmp: dont attempt to pull tasks if affinity doesn't allow it
authorChris Redpath <chris.redpath@arm.com>
Mon, 24 Mar 2014 13:47:30 +0000 (13:47 +0000)
committerRobin Murphy <robin.murphy@arm.com>
Wed, 20 Aug 2014 14:04:07 +0000 (15:04 +0100)
commit95365d0a9ec7c16fbe25682998f898e400c27177
treed54c1c1e50b4bc753d182321b9e2ae1198ccc17c
parentbefb0c2d040d2cd4f88ad8a54075c1f59bef938a
hmp: dont attempt to pull tasks if affinity doesn't allow it

When looking for a task to be idle-pulled, don't consider tasks
where the affinity does not allow that task to be placed on the
target CPU. Also ensure that tasks with restricted affinity
do not block selecting other unrestricted busy tasks.

Use the knowledge of target CPU more effectively in idle pull
by passing to hmp_get_heaviest_task when we know it, otherwise
only checking for general affinity matches with any of the CPUs
in the bigger HMP domain.

We still need to explicitly check affinity is allowed in idle pull
since if we find no match in hmp_get_heaviest_task we will return
the current one, which may not be affine to the new CPU despite
having high enough load. In this case, there is nothing to move.

Signed-off-by: Chris Redpath <chris.redpath@arm.com>
Signed-off-by: Jon Medhurst <tixy@linaro.org>
kernel/sched/fair.c