From: john stultz <johnstul@us.ibm.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: dean gaudet <dean-list-linux-kernel@arctic.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [patch] prefer TSC over PM Timer
Date: Tue, 16 Nov 2004 01:36:32 -0800 [thread overview]
Message-ID: <1100597793.13732.7.camel@leatherman> (raw)
In-Reply-To: <1100592718.2811.8.camel@laptop.fenrus.org>
On Tue, 2004-11-16 at 09:11 +0100, Arjan van de Ven wrote:
> > While there are a great number of systems that can use the TSC, cpufreq
> > scaling laptops, and a number of SMP and NUMA systems cannot use it as a
> > time source.
>
> please don't drag cpufreq into this; cpufreq adjusts this timer on
> frequency changes just fine.
Fair enough. Dominik and others have done some great work there and I
shouldn't cast doubt on it. I just haven't played with it enough to
really get confident that there really aren't any holes with it.
That said, not all laptops properly notify the kernel when they change
frequency. The BIOS just changes it on its own. My old one had this
problem and the pmtmr helped quite a bit there. But maybe these cases
are just rare enough that its not an issue.
thanks
-john
next prev parent reply other threads:[~2004-11-16 9:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-16 0:23 [patch] prefer TSC over PM Timer dean gaudet
2004-11-16 1:38 ` john stultz
2004-11-16 3:21 ` dean gaudet
2004-11-16 9:50 ` john stultz
2004-11-16 20:29 ` Dominik Brodowski
2004-11-16 21:06 ` john stultz
2004-11-16 8:11 ` Arjan van de Ven
2004-11-16 9:36 ` john stultz [this message]
2004-11-17 15:25 ` Alan Cox
2004-11-17 15:25 ` Alan Cox
2004-11-17 17:23 ` Chris Friesen
-- strict thread matches above, loose matches on Subject: below --
2004-11-16 18:27 Pallipadi, Venkatesh
2004-11-17 1:50 ` dean gaudet
2004-11-17 10:43 ` Mikael Pettersson
2004-11-17 14:19 ` Dmitry Torokhov
2004-11-17 15:31 ` Alan Cox
2004-11-18 2:01 ` Krzysztof Halasa
2004-11-17 15:08 Pallipadi, Venkatesh
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=1100597793.13732.7.camel@leatherman \
--to=johnstul@us.ibm.com \
--cc=arjan@infradead.org \
--cc=dean-list-linux-kernel@arctic.org \
--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