On 11/07/2018 15:42, Sudeep Holla wrote: > Hi Daniel, > > On 11/07/18 12:36, Daniel Lezcano wrote: >> 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 <[email protected]> >>> Cc: Thomas Gleixner <[email protected]> >>> Cc: Thierry Reding <[email protected]> >>> Cc: Jonathan Hunter <[email protected]> >>> Cc: Santosh Shilimkar <[email protected]> >>> Signed-off-by: Sudeep Holla <[email protected]> >>> --- >> >> Applied, thanks for the fix. >> > > Thomas was planning to take this, see [1]
Thomas ? Do you want to take all the series ? Or shall I take this one ? -- <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
