On Mon, 23 Oct 2017, Johannes Berg wrote: > On Mon, 2017-10-23 at 12:23 +0200, Thomas Gleixner wrote: > > On Mon, 23 Oct 2017, Johannes Berg wrote: > > > > > On Sun, 2017-10-22 at 23:40 +0200, Anna-Maria Gleixner wrote: > > > > From: Thomas Gleixner <tglx@xxxxxxxxxxxxx> > > > > > > > > Switch the timer to HRTIMER_MODE_SOFT, which executed the timer > > > > callback in softirq context and remove the hrtimer_tasklet. > > > > I can't build as its part of the whole hrtimer rework series. > > I guess you mean you *can* build it? Surely you're introducing the new > HR timer modes in some patch that I didn't see? :-) Sorry, we did not want to expose you to 30 patches fiddling with the core code. They are on LKML though. > > > > + hrtimer_init(&data->beacon_timer, CLOCK_MONOTONIC, > > > > + HRTIMER_MODE_ABS_SOFT); > > > > Sure, though it does not matter in that case. Will fix that up. > > Right. Then again, why even pass it to init() and start()? Can you > start without going through start()? There is a subtle magic with CLOCK_REALTIME timers. CLOCK_REALTIME timers differentiate between ABS and REL modes. ABS timers are exposed to clock modifications (settimeofday() ...), REL timers are not. We solve that by associating them to different clock bases, which has to be done at init time, but the start function needs the REL/ABS information as well. For CLOCK_MONOTONIC this is not really required, but the function is used for all clock bases, so we require the mode bits for all. Thanks, tglx
