From: Ian Campbell <ijc@hellion.org.uk>
To: john stultz <johnstul@us.ibm.com>
Cc: linux-kernel@vger.kernel.org, Andi Kleen <ak@suse.de>
Subject: Re: PMTMR running too fast
Date: Wed, 06 Dec 2006 08:14:23 +0000 [thread overview]
Message-ID: <1165392864.5499.68.camel@localhost.localdomain> (raw)
In-Reply-To: <1165347242.8326.15.camel@localhost>
[-- Attachment #1: Type: text/plain, Size: 818 bytes --]
On Tue, 2006-12-05 at 11:34 -0800, john stultz wrote:
> On Tue, 2006-12-05 at 07:41 +0000, Ian Campbell wrote:
> > Should tsc be preferred to pit though?
>
> Depends on your system. If C2/C3 or cpufreq state changes are detected,
> we mark the tsc as unstable.
I'm not using them on purpose but I'll check it out.
> It sounds as if from your earlier email the TSC works fine, so we might
> want to look at what's making the system think its not ok. I probably
> need to add a message as to why it was disqualified. However, that's a
> separate issue from the last patch.
I'll have a play, see if I can figure it out.
> Thanks for the testing!
Thanks for the fix!
Ian.
--
Ian Campbell
* Turken thinks little kids are absolutely adorable... especialyy when
they're someone elses.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-12-06 8:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-03 13:50 PMTMR running too fast Ian Campbell
2006-12-04 19:19 ` john stultz
2006-12-04 19:40 ` Ian Campbell
2006-12-04 20:14 ` john stultz
2006-12-05 7:41 ` Ian Campbell
2006-12-05 19:34 ` john stultz
2006-12-06 8:14 ` Ian Campbell [this message]
2006-12-06 19:46 ` Ian Campbell
2006-12-06 16:44 ` Andi Kleen
2006-12-06 19:28 ` john stultz
2006-12-06 20:14 ` Andi Kleen
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=1165392864.5499.68.camel@localhost.localdomain \
--to=ijc@hellion.org.uk \
--cc=ak@suse.de \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.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