Re: Query regarding __hrtimer_get_next_event()

2017-10-27 Thread Thomas Gleixner
On Thu, 26 Oct 2017, Neeraj Upadhyay wrote: > Hi tglx, > > Forgot to mention, we are using kernel stable version 3.18 > https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/tree/kernel/time/timekeeping.c?h=v3.18.77 > > wall time is being set to a value close to epoch > but les

Re: Query regarding __hrtimer_get_next_event()

2017-10-26 Thread Neeraj Upadhyay
Hi tglx, Forgot to mention, we are using kernel stable version 3.18 https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/tree/kernel/time/timekeeping.c?h=v3.18.77 wall time is being set to a value close to epoch but less than epoch + current uptime. Looks like https://git.ke

Re: Query regarding __hrtimer_get_next_event()

2017-10-26 Thread Thomas Gleixner
On Thu, 26 Oct 2017, Neeraj Upadhyay wrote: > We have one query regarding the __hrtimer_get_next_event(). > The expires_next.tv64 is set to 0 if it is < 0. We observed > an hrtimer interrupt storm for one of the hrtimers with > below properties: > > * Expires for the hrtimer was set to KTIME_MAX.