From: tip-bot for Thomas Gleixner <tipbot@zytor.com> To: linux-tip-commits@vger.kernel.org Cc: peterz@infradead.org, hpa@zytor.com, tglx@linutronix.de, deller@gmx.de, mingo@kernel.org, john.stultz@linaro.org, linux-kernel@vger.kernel.org Subject: [tip:timers/urgent] itimers: Handle relative timers with CONFIG_TIME_LOW_RES proper Date: Sun, 17 Jan 2016 02:43:47 -0800 [thread overview] Message-ID: <tip-51cbb5242a41700a3f250ecfb48dcfb7e4375ea4@git.kernel.org> (raw) In-Reply-To: <20160114164159.528222587@linutronix.de> Commit-ID: 51cbb5242a41700a3f250ecfb48dcfb7e4375ea4 Gitweb: http://git.kernel.org/tip/51cbb5242a41700a3f250ecfb48dcfb7e4375ea4 Author: Thomas Gleixner <tglx@linutronix.de> AuthorDate: Thu, 14 Jan 2016 16:54:48 +0000 Committer: Thomas Gleixner <tglx@linutronix.de> CommitDate: Sun, 17 Jan 2016 11:13:55 +0100 itimers: Handle relative timers with CONFIG_TIME_LOW_RES proper As Helge reported for timerfd we have the same issue in itimers. 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> Cc: Peter Zijlstra <peterz@infradead.org> Cc: Helge Deller <deller@gmx.de> Cc: John Stultz <john.stultz@linaro.org> Cc: linux-m68k@lists.linux-m68k.org Cc: dhowells@redhat.com Cc: stable@vger.kernel.org Link: http://lkml.kernel.org/r/20160114164159.528222587@linutronix.de Signed-off-by: Thomas Gleixner <tglx@linutronix.de> --- kernel/time/itimer.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/kernel/time/itimer.c b/kernel/time/itimer.c index 8d262b4..1d5c720 100644 --- a/kernel/time/itimer.c +++ b/kernel/time/itimer.c @@ -26,7 +26,7 @@ */ static struct timeval itimer_get_remtime(struct hrtimer *timer) { - ktime_t rem = hrtimer_get_remaining(timer); + ktime_t rem = __hrtimer_get_remaining(timer, true); /* * Racy but safe: if the itimer expires after the above
prev parent reply other threads:[~2016-01-17 10:44 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 ` [patch 3/4] posix-timers: " Thomas Gleixner 2016-01-14 16:54 ` 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-bot for Thomas Gleixner [this message]
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=tip-51cbb5242a41700a3f250ecfb48dcfb7e4375ea4@git.kernel.org \ --to=tipbot@zytor.com \ --cc=deller@gmx.de \ --cc=hpa@zytor.com \ --cc=john.stultz@linaro.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-tip-commits@vger.kernel.org \ --cc=mingo@kernel.org \ --cc=peterz@infradead.org \ --cc=tglx@linutronix.de \ --subject='Re: [tip:timers/urgent] itimers: Handle relative timers with CONFIG_TIME_LOW_RES proper' \ /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
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.