From: Ingo Molnar <mingo@elte.hu>
To: Pavel Emelyanov <xemul@openvz.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Kirill Korotaev <dev@openvz.org>
Subject: Re: [PATCH] x86: fix hpet timer reinit for x86_64
Date: Wed, 4 Feb 2009 14:49:33 +0100 [thread overview]
Message-ID: <20090204134933.GC17024@elte.hu> (raw)
In-Reply-To: <4989709F.1050207@openvz.org>
* Pavel Emelyanov <xemul@openvz.org> wrote:
> There's a small problem with hpet_rtc_reinit function - it checks
> for the
> hpet_readl(HPET_COUNTER) - hpet_t1_cmp > 0
> to continue increasing both the HPET_T1_CMP (register) and the
> hpet_t1_cmp (variable).
>
> But since the HPET_COUNTER is always 32-bit, if the hpet_t1_cmp
> is 64-bit this condition will always be FALSE once the latter hits
> the 32-bit boundary, and we can have a situation, when we don't
> increase the HPET_T1_CMP register high enough.
>
> The result - timer stops ticking, since HPET_T1_CMP becomes less,
> than the COUNTER and never increased again.
>
> The solution is to cut the upper 32-bit from the hpet_t1_cmp
> variable to make the comparison to HPET_COUNTER correct.
>
> Reported-by: Kirill Korotaev <dev@openvz.org>
> Signed-off-by: Pavel Emelyanov <xemul@openvz.org>
applied to tip/timers/urgent, thanks Pavel!
I'm wondering, what symptoms were seen due to the bug? Did system time stop,
or did it become erratic, or were there outright lockups?
Ingo
next prev parent reply other threads:[~2009-02-04 13:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-04 10:40 [PATCH] x86: fix hpet timer reinit for x86_64 Pavel Emelyanov
2009-02-04 11:39 ` Vitaly Mayatskikh
2009-02-04 11:43 ` Kirill Korotaev
2009-02-04 11:51 ` Pavel Emelyanov
2009-02-04 13:49 ` Ingo Molnar [this message]
2009-02-05 8:01 ` Kirill Korotaev
2009-02-05 14:53 ` Ingo Molnar
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=20090204134933.GC17024@elte.hu \
--to=mingo@elte.hu \
--cc=dev@openvz.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=xemul@openvz.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: 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