Re: [RFC PATCH v4 12/21] watchdog/hardlockup/hpet: Adjust timer expiration on the number of monitored CPUs

2019-06-18 Thread Ricardo Neri
On Tue, Jun 11, 2019 at 10:11:04PM +0200, Thomas Gleixner wrote: > On Thu, 23 May 2019, Ricardo Neri wrote: > > @@ -52,10 +59,10 @@ static void kick_timer(struct hpet_hld_data *hdata, > > bool force) > > return; > > > > if (hdata->has_periodic) > > - period =

Re: [RFC PATCH v4 12/21] watchdog/hardlockup/hpet: Adjust timer expiration on the number of monitored CPUs

2019-06-11 Thread Thomas Gleixner
On Thu, 23 May 2019, Ricardo Neri wrote: > @@ -52,10 +59,10 @@ static void kick_timer(struct hpet_hld_data *hdata, bool > force) > return; > > if (hdata->has_periodic) > - period = watchdog_thresh * hdata->ticks_per_second; > + period =

[RFC PATCH v4 12/21] watchdog/hardlockup/hpet: Adjust timer expiration on the number of monitored CPUs

2019-05-23 Thread Ricardo Neri
Each CPU should be monitored for hardlockups every watchdog_thresh seconds. Since all the CPUs in the system are monitored by the same timer and the timer interrupt is rotated among the monitored CPUs, the timer must expire every watchdog_thresh/N seconds; where N is the number of monitored CPUs.