Re: [PATCH v2] clocksource: Warn if too many missing ticks are detected

2018-09-24 Thread Waiman Long
On 09/19/2018 03:53 AM, Thomas Gleixner wrote: > On Tue, 18 Sep 2018, Waiman Long wrote: > >> The clocksource watchdog, when running, is scheduled on all the CPUs in >> the system sequentially on a round-robin fashion with a period of 0.5s. >> A bug in the 4.18 kernel is causing missing ticks when

Re: [PATCH v2] clocksource: Warn if too many missing ticks are detected

2018-09-19 Thread Waiman Long
On 09/19/2018 05:17 AM, Peter Zijlstra wrote: > On Wed, Sep 19, 2018 at 09:53:47AM +0200, Thomas Gleixner wrote: >> On Tue, 18 Sep 2018, Waiman Long wrote: >> >>> The clocksource watchdog, when running, is scheduled on all the CPUs in >>> the system sequentially on a round-robin fashion with a peri

Re: [PATCH v2] clocksource: Warn if too many missing ticks are detected

2018-09-19 Thread Peter Zijlstra
On Wed, Sep 19, 2018 at 09:53:47AM +0200, Thomas Gleixner wrote: > On Tue, 18 Sep 2018, Waiman Long wrote: > > > The clocksource watchdog, when running, is scheduled on all the CPUs in > > the system sequentially on a round-robin fashion with a period of 0.5s. > > A bug in the 4.18 kernel is causi

Re: [PATCH v2] clocksource: Warn if too many missing ticks are detected

2018-09-19 Thread Thomas Gleixner
On Tue, 18 Sep 2018, Waiman Long wrote: > The clocksource watchdog, when running, is scheduled on all the CPUs in > the system sequentially on a round-robin fashion with a period of 0.5s. > A bug in the 4.18 kernel is causing missing ticks when nohz_full > is specified. Under some circumstances, t

[PATCH v2] clocksource: Warn if too many missing ticks are detected

2018-09-18 Thread Waiman Long
The clocksource watchdog, when running, is scheduled on all the CPUs in the system sequentially on a round-robin fashion with a period of 0.5s. A bug in the 4.18 kernel is causing missing ticks when nohz_full is specified. Under some circumstances, this causes the watchdog to incorrectly state that