[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.21.1807140045060.2644@nanos.tec.linutronix.de>
Date: Sat, 14 Jul 2018 00:45:32 +0200 (CEST)
From: Thomas Gleixner <tglx@...utronix.de>
To: Daniel Lezcano <daniel.lezcano@...aro.org>
cc: Sudeep Holla <sudeep.holla@....com>, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
Thierry Reding <thierry.reding@...il.com>,
Jonathan Hunter <jonathanh@...dia.com>,
Santosh Shilimkar <ssantosh@...nel.org>
Subject: Re: [PATCH 1/3] clocksource: drivers: set clockevent device cpumask
to cpu_possible_mask
On Wed, 11 Jul 2018, Daniel Lezcano wrote:
> 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 <daniel.lezcano@...aro.org>
> >>> Cc: Thomas Gleixner <tglx@...utronix.de>
> >>> Cc: Thierry Reding <thierry.reding@...il.com>
> >>> Cc: Jonathan Hunter <jonathanh@...dia.com>
> >>> Cc: Santosh Shilimkar <ssantosh@...nel.org>
> >>> Signed-off-by: Sudeep Holla <sudeep.holla@....com>
> >>> ---
> >>
> >> 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 ?
Take it, it's ok for this to go into 4.19
Thanks,
tglx
Powered by blists - more mailing lists