From: Thomas Gleixner <tglx@linutronix.de> To: LKML <linux-kernel@vger.kernel.org> Cc: Ingo Molnar <mingo@kernel.org>, Peter Zijlstra <peterz@infradead.org>, Helge Deller <deller@gmx.de>, John Stultz <john.stultz@linaro.org>, linux-m68k@vger.kernel.org, dhowells@redhat.com Subject: [patch 3/4] posix-timers: Handle relative timers with CONFIG_TIME_LOW_RES proper Date: Thu, 14 Jan 2016 16:54:47 -0000 [thread overview] Message-ID: <20160114164159.450510905@linutronix.de> (raw) In-Reply-To: 20160114163744.582215466@linutronix.de [-- Attachment #1: posix-timers--Handle-relative-timers-with-CONFIG_TIME_LOW_RES-proper.patch --] [-- Type: text/plain, Size: 897 bytes --] As Helge reported for timerfd we have the same issue in posix timers. We return remaining time larger than the programmed relative time to user space in case of CONFIG_TIME_LOW_RES=y. Use the proper function to adjust the extra time added in hrtimer_start_range_ns(). Signed-off-by: Thomas Gleixner <tglx@linutronix.de> --- kernel/time/posix-timers.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) --- a/kernel/time/posix-timers.c +++ b/kernel/time/posix-timers.c @@ -760,7 +760,7 @@ common_timer_get(struct k_itimer *timr, (timr->it_sigev_notify & ~SIGEV_THREAD_ID) == SIGEV_NONE)) timr->it_overrun += (unsigned int) hrtimer_forward(timer, now, iv); - remaining = ktime_sub(hrtimer_get_expires(timer), now); + remaining = __hrtimer_expires_remaining_adjusted(timer, now); /* Return 0 only, when the timer is expired and not pending */ if (remaining.tv64 <= 0) { /*
WARNING: multiple messages have this Message-ID (diff)
From: Thomas Gleixner <tglx@linutronix.de> To: LKML <linux-kernel@vger.kernel.org> Cc: Ingo Molnar <mingo@kernel.org>, Peter Zijlstra <peterz@infradead.org>, Helge Deller <deller@gmx.de>, John Stultz <john.stultz@linaro.org>, linux-m68k@lists.linux-m68k.org, dhowells@redhat.com Subject: [patch 3/4] posix-timers: Handle relative timers with CONFIG_TIME_LOW_RES proper Date: Thu, 14 Jan 2016 16:54:47 -0000 [thread overview] Message-ID: <20160114164159.450510905@linutronix.de> (raw) In-Reply-To: 20160114163744.582215466@linutronix.de [-- Attachment #1: posix-timers--Handle-relative-timers-with-CONFIG_TIME_LOW_RES-proper.patch --] [-- Type: text/plain, Size: 897 bytes --] As Helge reported for timerfd we have the same issue in posix timers. We return remaining time larger than the programmed relative time to user space in case of CONFIG_TIME_LOW_RES=y. Use the proper function to adjust the extra time added in hrtimer_start_range_ns(). Signed-off-by: Thomas Gleixner <tglx@linutronix.de> --- kernel/time/posix-timers.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) --- a/kernel/time/posix-timers.c +++ b/kernel/time/posix-timers.c @@ -760,7 +760,7 @@ common_timer_get(struct k_itimer *timr, (timr->it_sigev_notify & ~SIGEV_THREAD_ID) == SIGEV_NONE)) timr->it_overrun += (unsigned int) hrtimer_forward(timer, now, iv); - remaining = ktime_sub(hrtimer_get_expires(timer), now); + remaining = __hrtimer_expires_remaining_adjusted(timer, now); /* Return 0 only, when the timer is expired and not pending */ if (remaining.tv64 <= 0) { /*
next prev parent reply other threads:[~2016-01-14 16:56 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2016-01-14 16:54 [patch 0/4] hrtimers: Handle remaining time correctly for CONFIG_TIME_LOW_RES=y Thomas Gleixner 2016-01-14 16:54 ` Thomas Gleixner 2016-01-14 16:54 ` [patch 1/4] hrtimer: Handle remaining time proper for TIME_LOW_RES Thomas Gleixner 2016-01-14 16:54 ` Thomas Gleixner 2016-01-16 18:36 ` Helge Deller 2016-01-16 18:36 ` Helge Deller 2016-01-16 18:36 ` Helge Deller 2016-01-17 10:42 ` [tip:timers/urgent] " tip-bot for Thomas Gleixner 2016-01-14 16:54 ` [patch 2/4] timerfd: Handle relative timers with CONFIG_TIME_LOW_RES proper Thomas Gleixner 2016-01-17 10:43 ` [tip:timers/urgent] " tip-bot for Thomas Gleixner 2016-01-14 16:54 ` [patch 2/4] " Thomas Gleixner 2016-01-14 16:54 ` Thomas Gleixner [this message] 2016-01-14 16:54 ` [patch 3/4] posix-timers: " Thomas Gleixner 2016-01-17 10:43 ` [tip:timers/urgent] " tip-bot for Thomas Gleixner 2016-01-14 16:54 ` [patch 4/4] itimers: " Thomas Gleixner 2016-01-14 16:54 ` Thomas Gleixner 2016-01-17 10:43 ` [tip:timers/urgent] " tip-bot for Thomas Gleixner
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=20160114164159.450510905@linutronix.de \ --to=tglx@linutronix.de \ --cc=deller@gmx.de \ --cc=dhowells@redhat.com \ --cc=john.stultz@linaro.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-m68k@vger.kernel.org \ --cc=mingo@kernel.org \ --cc=peterz@infradead.org \ /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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.