On Wed, Apr 17, 2013 at 04:26:18PM -0700, Stephen Boyd wrote: > Hot-plugging with CONFIG_DEBUG_PREEMPT=y on a device with arm > architected timers causes a slew of "using smp_processor_id() in > preemptible" warnings: > > BUG: using smp_processor_id() in preemptible [00000000] code: sh/111 > caller is arch_timer_cpu_notify+0x14/0xc8 > > This happens because sometimes the cpu notifier, > arch_timer_cpu_notify(), is called in preemptible context and > other times in non-preemptible context but we use this_cpu_ptr() > to retrieve the clockevent in all cases. We're only going to > actually use the pointer in non-preemptible context though, so > push the this_cpu_ptr() access down into the cases to force the > checks to occur only in non-preemptible contexts. > > Cc: John Stultz <john.stultz@xxxxxxxxxx> > Cc: Thomas Gleixner <tglx@xxxxxxxxxxxxx> > Cc: Mark Rutland <mark.rutland@xxxxxxx> > Acked-by: Marc Zyngier <Marc.Zyngier@xxxxxxx> > Signed-off-by: Stephen Boyd <sboyd@xxxxxxxxxxxxxx> > --- > > Resending to arm-soc maintainers instead of timekeeping maintainers. Who > maintains this driver? Subsystem is maintained by John and Thomas, but given the recent moves of ARM drivers there (which mostly has been acked by them), we'll take the patch at this time. Applied on top of late/clksrc in arm-soc. Thanks. -Olof -- To unsubscribe from this list: send the line "unsubscribe linux-arm-msm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
