[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.21.1807102220320.1588@nanos.tec.linutronix.de>
Date: Tue, 10 Jul 2018 22:21:53 +0200 (CEST)
From: Thomas Gleixner <tglx@...utronix.de>
To: Sudeep Holla <sudeep.holla@....com>
cc: linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
Marc Zyngier <marc.zyngier@....com>,
Kevin Hilman <khilman@...libre.com>,
Martin Blumenstingl <martin.blumenstingl@...glemail.com>,
Mark Rutland <mark.rutland@....com>
Subject: Re: [PATCH 2/2] clocksource: arm_arch_timer: set arch_mem_timer
cpumask to cpu_possible_mask
On Tue, 10 Jul 2018, Sudeep Holla wrote:
> On 10/07/18 13:21, Thomas Gleixner wrote:
> >> Also only few ARM clocksource drivers use cpu_all_mask which could be
> >> result of copy-paste, we can even fix them too.
> >>
> >> arm_arch_timer.c: clk->cpumask = cpu_all_mask;
> >> tegra20_timer.c: tegra_clockevent.cpumask = cpu_all_mask;
> >> timer-atcpit100.c: .cpumask = cpu_all_mask,
> >> timer-keystone.c: event_dev->cpumask = cpu_all_mask;
> >> zevio-timer.c: timer->clkevt.cpumask = cpu_all_mask;
> >
> > Yes, that makes sense. What we could do is warn, when cpu_all_mask is set
> > at registration time and replace the pointer with cpu_possible_mask.
> >
> I like this approach than having to bitwise and with cpu_possible_mask
> at all the necessary place. I will cook up a patch.
Appreciated. I'm inclined to take it for 4.18 even. Please send it along
with the fixes for the above obvious failure spots.
Thanks,
tglx
Powered by blists - more mailing lists