Re: [RESEND PATCH v1 2/2] cpuidle: menu: Dismiss tick impaction on correction factors

2018-08-09 Thread Rafael J. Wysocki
On Thu, Aug 9, 2018 at 7:20 PM, Leo Yan wrote: > If the idle duration predictor detects the tick is triggered, and with > meeting the condition 'data->next_timer_us > TICK_USEC', it will give a > big compensation for the 'measured' interval; this is purposed to avoid > artificially small

Re: [RESEND PATCH v1 2/2] cpuidle: menu: Dismiss tick impaction on correction factors

2018-08-09 Thread Rafael J. Wysocki
On Thu, Aug 9, 2018 at 7:20 PM, Leo Yan wrote: > If the idle duration predictor detects the tick is triggered, and with > meeting the condition 'data->next_timer_us > TICK_USEC', it will give a > big compensation for the 'measured' interval; this is purposed to avoid > artificially small

[RESEND PATCH v1 2/2] cpuidle: menu: Dismiss tick impaction on correction factors

2018-08-09 Thread Leo Yan
If the idle duration predictor detects the tick is triggered, and with meeting the condition 'data->next_timer_us > TICK_USEC', it will give a big compensation for the 'measured' interval; this is purposed to avoid artificially small correction factor values. Unfortunately, this still cannot

[RESEND PATCH v1 2/2] cpuidle: menu: Dismiss tick impaction on correction factors

2018-08-09 Thread Leo Yan
If the idle duration predictor detects the tick is triggered, and with meeting the condition 'data->next_timer_us > TICK_USEC', it will give a big compensation for the 'measured' interval; this is purposed to avoid artificially small correction factor values. Unfortunately, this still cannot