From: john stultz <johnstul@us.ibm.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: linux-kernel@vger.kernel.org, Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH] x86/hpet: Use the FSEC_PER_SEC constant for femto-second periods
Date: Mon, 09 Aug 2010 12:04:24 -0700 [thread overview]
Message-ID: <1281380664.2444.3.camel@localhost.localdomain> (raw)
In-Reply-To: <1281272311-13820-1-git-send-email-chris@chris-wilson.co.uk>
On Sun, 2010-08-08 at 13:58 +0100, Chris Wilson wrote:
> The current computation, introduced with f12a15be63, of FSEC_PER_SEC using
> the multiplication of (FSEC_PER_NSEC * NSEC_PER_SEC) is performed only
> with 32bit integers on small machines, resulting in an overflow and a
> *very* short intervals being programmed. An interrupt storm follows.
>
> Note that we also have to specify FSEC_PER_SEC as being long long to
> overcome the same limitations.
Thanks so much for catching and debugging this!
Acked-by: John Stultz <johnstul@us.ibm.com>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: John Stultz <johnstul@us.ibm.com>
> Cc: Thomas Gleixner <tglx@linutronix.de>
> ---
> arch/x86/kernel/hpet.c | 4 ++--
> include/linux/time.h | 2 +-
> 2 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/arch/x86/kernel/hpet.c b/arch/x86/kernel/hpet.c
> index 33dbcc4..351f9c0 100644
> --- a/arch/x86/kernel/hpet.c
> +++ b/arch/x86/kernel/hpet.c
> @@ -582,7 +582,7 @@ static void init_one_hpet_msi_clockevent(struct hpet_dev *hdev, int cpu)
> * scaled math multiplication factor for nanosecond to hpet tick
> * conversion.
> */
> - hpet_freq = 1000000000000000ULL;
> + hpet_freq = FSEC_PER_SEC;
> do_div(hpet_freq, hpet_period);
> evt->mult = div_sc((unsigned long) hpet_freq,
> NSEC_PER_SEC, evt->shift);
> @@ -837,7 +837,7 @@ static int hpet_clocksource_register(void)
> * cyc/sec = FSEC_PER_SEC/hpet_period(fsec/cyc)
> * cyc/sec = (FSEC_PER_NSEC * NSEC_PER_SEC)/hpet_period
> */
> - hpet_freq = FSEC_PER_NSEC * NSEC_PER_SEC;
> + hpet_freq = FSEC_PER_SEC;
> do_div(hpet_freq, hpet_period);
> clocksource_register_hz(&clocksource_hpet, (u32)hpet_freq);
>
> diff --git a/include/linux/time.h b/include/linux/time.h
> index cb34e35..1261270 100644
> --- a/include/linux/time.h
> +++ b/include/linux/time.h
> @@ -38,7 +38,7 @@ extern struct timezone sys_tz;
> #define NSEC_PER_MSEC 1000000L
> #define USEC_PER_SEC 1000000L
> #define NSEC_PER_SEC 1000000000L
> -#define FSEC_PER_SEC 1000000000000000L
> +#define FSEC_PER_SEC 1000000000000000LL
>
> #define TIME_T_MAX (time_t)((1UL << ((sizeof(time_t) << 3) - 1)) - 1)
>
prev parent reply other threads:[~2010-08-09 19:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-08 12:58 Chris Wilson
2010-08-09 19:04 ` john stultz [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=1281380664.2444.3.camel@localhost.localdomain \
--to=johnstul@us.ibm.com \
--cc=chris@chris-wilson.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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
Powered by JetHome