On Thu, 13 Feb 2014, Alan Stern wrote:
> On Thu, 13 Feb 2014, Thomas Gleixner wrote:
> I can think of two other solutions. The first is to move the
> non-hardirq-safe hrtimers into threaded softirq context, as mentioned
> above.
Right, but that's major surgery.
> The second is for ehci_hrtimer_func to schedule a tasklet instead of
> doing its work directly. But this seems like an awkward workaround for
> something which shouldn't be a problem in the first place.
Eeew.
> Of the three, using spin_lock_irqsave in ehci_irq is the simplest. If
> the hrtimers can't be moved to threaded context, that's what I'll end
> up doing.
I think, that's the simplest option for now. We'll look into the
hrtimer issue anyway, but as I said it's not a two lines patch.
Thanks,
tglx
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
