From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Lee Revell <rlrevell@joe-job.com>
Cc: Pavel Machek <pavel@ucw.cz>, M <mru@mru.ath.cx>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: High pitched noise from laptop: processor.c in linux 2.6
Date: Sun, 17 Oct 2004 03:21:46 +0100 [thread overview]
Message-ID: <1097979705.13269.9.camel@localhost.localdomain> (raw)
In-Reply-To: <1097976283.2148.34.camel@krustophenia.net>
On Sul, 2004-10-17 at 02:24, Lee Revell wrote:
> > And heavily reduced accuracy on a lot of laptops where 1000Hz
> > is enough to make the clock slide every time the battery state is
> > queried or an SMM event triggers.
> Wouldn't such a laptop be horribly broken? 1ms is a LONG time to
> disable interrupts. That's millions of CPU cycles...
Yes, and most laptops have this problem. They use SMM traps to talk to
the battery including huge delay loops and during those SMM traps no
interrupt code runs.
> > Getting the best of both worlds depends on the stuff discussed at OLS
> > being finished, then you can have 1Khz accurancy and battery life
> I was not there but I imagine this involves a way to get 1khz accuracy
> with a 100Hz timer interrupt rate?
Think about
add_timeout(timer, when, precision_desired)
next prev parent reply other threads:[~2004-10-17 3:24 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-07 9:30 High pitched noise from laptop: processor.c in linux 2.6 Fraz
2004-10-07 10:32 ` Pavel Machek
2004-10-07 10:53 ` Måns Rullgård
2004-10-07 14:32 ` Pavel Machek
2004-10-16 19:52 ` Lee Revell
2004-10-16 21:46 ` Alan Cox
2004-10-17 1:24 ` Lee Revell
2004-10-17 1:50 ` Kyle Moffett
2004-10-17 2:21 ` Alan Cox [this message]
2004-10-17 3:33 ` Lee Revell
2004-10-22 11:40 ` Alexandre Oliva
2004-10-16 19:59 ` Måns Rullgård
2004-10-16 20:42 ` Pavel Machek
2004-10-07 14:34 ` Pavel Machek
2004-10-17 0:45 ` Alex Riesen
2004-10-07 10:37 ` Christian Hesse
-- strict thread matches above, loose matches on Subject: below --
2004-10-17 5:21 Albert Cahalan
2004-10-18 3:51 Yu, Luming
2004-10-18 11:41 ` Pavel Machek
2004-10-20 14:47 ` Måns Rullgård
2004-10-20 15:47 ` Pavel Machek
2004-10-20 16:37 ` Måns Rullgård
2004-10-20 16:49 ` Jan-Benedict Glaw
2004-10-20 16:53 ` Pavel Machek
2004-10-20 16:53 ` Lee Revell
2004-10-20 17:13 ` Måns Rullgård
2004-10-21 20:32 ` Lee Revell
2004-10-21 21:39 ` Jon Masters
2004-10-20 23:31 ` Giuseppe Bilotta
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=1097979705.13269.9.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mru@mru.ath.cx \
--cc=pavel@ucw.cz \
--cc=rlrevell@joe-job.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