diff options
| author | Sudeep Holla <[email protected]> | 2018-07-09 16:45:35 +0100 |
|---|---|---|
| committer | Thomas Gleixner <[email protected]> | 2018-07-10 22:12:47 +0200 |
| commit | 5b5ccbc2b041f98f26b984e013d303b7f9e6fb8e (patch) | |
| tree | a29a2c70b8d1dd62580459e980f966fd4d2c8c40 | |
| parent | 1e4b044d22517cae7047c99038abb444423243ca (diff) | |
Revert "tick: Prefer a lower rating device only if it's CPU local device"
This reverts commit 1332a90558013ae4242e3dd7934bdcdeafb06c0d.
The original issue was not because of incorrect checking of cpumask for
both new and old tick device. It was incorrectly analysed was due to the
misunderstanding of the comment and misinterpretation of the return value
from tick_check_preferred. The main issue is with the clockevent driver
that sets the cpumask to cpu_all_mask instead of cpu_possible_mask.
Signed-off-by: Sudeep Holla <[email protected]>
Signed-off-by: Thomas Gleixner <[email protected]>
Tested-by: Kevin Hilman <[email protected]>
Tested-by: Martin Blumenstingl <[email protected]>
Cc: [email protected]
Cc: Marc Zyngier <[email protected]>
Link: https://lkml.kernel.org/r/[email protected]
| -rw-r--r-- | kernel/time/tick-common.c | 3 |
1 files changed, 1 insertions, 2 deletions
diff --git a/kernel/time/tick-common.c b/kernel/time/tick-common.c index b7005dd21ec1..14de3727b18e 100644 --- a/kernel/time/tick-common.c +++ b/kernel/time/tick-common.c @@ -277,8 +277,7 @@ static bool tick_check_preferred(struct clock_event_device *curdev, */ return !curdev || newdev->rating > curdev->rating || - (!cpumask_equal(curdev->cpumask, newdev->cpumask) && - !tick_check_percpu(curdev, newdev, smp_processor_id())); + !cpumask_equal(curdev->cpumask, newdev->cpumask); } /* |