From: Frederic Weisbecker <frederic@kernel.org>
To: "Zhou Ti (x2019cwm)" <x2019cwm@stfx.ca>
Cc: "fweisbec@gmail.com" <fweisbec@gmail.com>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"mingo@kernel.org" <mingo@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] fix the issue that the tick_nohz_get_sleep_length() function could return a negative value
Date: Fri, 19 Feb 2021 13:09:11 +0100 [thread overview]
Message-ID: <20210219120911.GA51281@lothringen> (raw)
In-Reply-To: <YTBPR01MB3262A1EAA009500DF6DD2132C4A20@YTBPR01MB3262.CANPRD01.PROD.OUTLOOK.COM>
On Wed, Jan 20, 2021 at 11:49:38PM +0000, Zhou Ti (x2019cwm) wrote:
> Fix the issue that the tick_nohz_get_sleep_length() function could return a
> negative value.
>
> The variable "dev->next_event" has a small possibility to be smaller than
> the variable "now" during running, which would result in a negative value
> of "*delta_next". The variable "next_event" also has a small posibility to
> be smaller than the variable "now". Both case could lead to a negative
> return of function tick_nohz_get_sleep_length().
>
> Signed-off-by: Ti Zhou <x2019cwm@stfx.ca>
> ---
> --- tip/kernel/time/tick-sched.c.orig 2021-01-20 05:34:25.151325912 -0400
> +++ tip/kernel/time/tick-sched.c 2021-01-20 19:44:28.238538380 -0400
> @@ -1142,6 +1142,9 @@ ktime_t tick_nohz_get_sleep_length(ktime
>
> *delta_next = ktime_sub(dev->next_event, now);
>
> + if (unlikely(*delta_next < 0))
> + *delta_next = 0;
> +
> if (!can_stop_idle_tick(cpu, ts))
> return *delta_next;
>
> @@ -1156,6 +1159,9 @@ ktime_t tick_nohz_get_sleep_length(ktime
> next_event = min_t(u64, next_event,
> hrtimer_next_event_without(&ts->sched_timer));
>
> + if (unlikely(next_event < now))
> + next_event = now;
> +
> return ktime_sub(next_event, now);
> }
>
I have reworked the changelog that way and queued. I'll post a
series including it after the merge window.
Thanks!
---
From: "Zhou Ti (x2019cwm)" <x2019cwm@stfx.ca>
Date: Wed, 20 Jan 2021 23:49:38 +0000
Subject: [PATCH] tick/nohz: Prevent tick_nohz_get_sleep_length() from
returning negative value
If the hardware clock happens to fire its interrupts late, two possible
issues can happen while calling tick_nohz_get_sleep_length(). Either:
1) The next clockevent device event is due past the last idle entry time.
or:
2) The last timekeeping update happened before the last idle entry time
and the next timer callback expires past the last idle entry time.
Make sure that both cases are handled to avoid returning a negative
duration to the cpuidle governors.
Signed-off-by: Ti Zhou <x2019cwm@stfx.ca>
Signed-off-by: Frederic Weisbecker <frederic@kernel.org>
---
kernel/time/tick-sched.c | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/kernel/time/tick-sched.c b/kernel/time/tick-sched.c
index e10a4af88737..22b6a46818cf 100644
--- a/kernel/time/tick-sched.c
+++ b/kernel/time/tick-sched.c
@@ -1142,6 +1142,9 @@ ktime_t tick_nohz_get_sleep_length(ktime_t *delta_next)
*delta_next = ktime_sub(dev->next_event, now);
+ if (unlikely(*delta_next < 0))
+ *delta_next = 0;
+
if (!can_stop_idle_tick(cpu, ts))
return *delta_next;
@@ -1156,6 +1159,9 @@ ktime_t tick_nohz_get_sleep_length(ktime_t *delta_next)
next_event = min_t(u64, next_event,
hrtimer_next_event_without(&ts->sched_timer));
+ if (unlikely(next_event < now))
+ next_event = now;
+
return ktime_sub(next_event, now);
}
--
2.25.1
next prev parent reply other threads:[~2021-02-19 12:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-20 23:49 [PATCH] fix the issue that the tick_nohz_get_sleep_length() function could return a negative value Zhou Ti (x2019cwm)
2021-02-01 13:47 ` Frederic Weisbecker
2021-02-19 12:09 ` Frederic Weisbecker [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-01-20 18:58 Zhou Ti (x2019cwm)
2021-01-20 22:11 ` Randy Dunlap
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210219120911.GA51281@lothringen \
--to=frederic@kernel.org \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
--cc=x2019cwm@stfx.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox