From: Salman Qazi <sqazi@google.com>
To: sqazi@google.com, Peter Zijlstra <a.p.zijlstra@chello.nl>,
John Stultz <johnstul@us.ibm.com>,
LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
Paul Turner <pjt@google.com>
Subject: [PATCH] sched, x86: fix overflow in cyc2ns_offset
Date: Thu, 08 Mar 2012 15:23:03 -0800 [thread overview]
Message-ID: <20120308232303.11660.48285.stgit@dungbeetle.mtv.corp.google.com> (raw)
When a machine boots up, the TSC generally gets reset. However, when
kexec is used to boot into a kernel, the TSC value would be carried
over from the previous kernel. The computation of cycns_offset in
set_cyc2ns_scale is prone to an overflow, if the machine has been up
more than 208 days prior to the kexec. The overflow happens when
we multiply *scale, even though there is enough room to store the
final answer. We fix this issue by decomposing tsc_now into the
quotient and remainder of division by CYC2NS_SCALE_FACTOR and then
performing the multiplication separately on the two components.
Signed-off-by: Salman Qazi <sqazi@google.com>
---
arch/x86/kernel/tsc.c | 12 +++++++++++-
1 files changed, 11 insertions(+), 1 deletions(-)
diff --git a/arch/x86/kernel/tsc.c b/arch/x86/kernel/tsc.c
index a62c201..ef1dc8e 100644
--- a/arch/x86/kernel/tsc.c
+++ b/arch/x86/kernel/tsc.c
@@ -608,6 +608,8 @@ static void set_cyc2ns_scale(unsigned long cpu_khz, int cpu)
{
unsigned long long tsc_now, ns_now, *offset;
unsigned long flags, *scale;
+ unsigned long long quot;
+ unsigned long long rem;
local_irq_save(flags);
sched_clock_idle_sleep_event();
@@ -620,7 +622,15 @@ static void set_cyc2ns_scale(unsigned long cpu_khz, int cpu)
if (cpu_khz) {
*scale = (NSEC_PER_MSEC << CYC2NS_SCALE_FACTOR)/cpu_khz;
- *offset = ns_now - (tsc_now * *scale >> CYC2NS_SCALE_FACTOR);
+
+ /*
+ * Avoid premature overflow by splitting into quotient
+ * and remainder. See the comment above __cycles_2_ns
+ */
+ quot = (tsc_now >> CYC2NS_SCALE_FACTOR);
+ rem = tsc_now & ((1ULL << CYC2NS_SCALE_FACTOR) - 1);
+ *offset = ns_now - (quot * *scale +
+ ((rem * *scale) >> CYC2NS_SCALE_FACTOR));
}
sched_clock_idle_wakeup_event(0);
next reply other threads:[~2012-03-08 23:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-08 23:23 Salman Qazi [this message]
2012-03-09 19:23 ` john stultz
2012-03-09 23:58 ` Salman Qazi
2012-03-10 0:00 ` Salman Qazi
2012-03-10 0:22 ` Paul Turner
2012-03-10 0:29 ` Salman Qazi
2012-03-10 0:25 ` john stultz
2012-03-10 0:28 ` Salman Qazi
2012-03-10 0:35 ` john stultz
2012-03-10 0:41 Salman Qazi
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=20120308232303.11660.48285.stgit@dungbeetle.mtv.corp.google.com \
--to=sqazi@google.com \
--cc=a.p.zijlstra@chello.nl \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=pjt@google.com \
/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
all inboxes | Powered by JetHome®