Re: [PATCH 1/3] clocksource: drivers: set clockevent device cpumask to cpu_possible_mask

From: Daniel Lezcano
Date: Wed Jul 11 2018 - 07:36:08 EST


On 11/07/2018 13:24, Sudeep Holla wrote:
> Currently, quite a few clockevent devices have cpumask set to
> cpu_all_mask which should be fine. However, cpu_possible_mask is more
> accurate and if there are any other clockevent devices in the system
> which have cpumask set to cpu_possible_mask, then having cpu_all_mask
> may result in issues (mostly boot hang with forever loops in
> clockevents_notify_released).
>
> So, lets replace all the clockevent device cpu_all_mask to
> cpu_possible_mask in order to prevent above mentioned possible issue.
>
> Cc: Daniel Lezcano <daniel.lezcano@xxxxxxxxxx>
> Cc: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
> Cc: Thierry Reding <thierry.reding@xxxxxxxxx>
> Cc: Jonathan Hunter <jonathanh@xxxxxxxxxx>
> Cc: Santosh Shilimkar <ssantosh@xxxxxxxxxx>
> Signed-off-by: Sudeep Holla <sudeep.holla@xxxxxxx>
> ---

Applied, thanks for the fix.


--
<http://www.linaro.org/> Linaro.org â Open source software for ARM SoCs

Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog