From: Stevie O <stevie@qrpff.net>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Local APIC option (CONFIG_X86_UP_APIC) locks up Inspiron 8100
Date: Wed, 31 Oct 2001 18:49:58 -0500 [thread overview]
Message-ID: <5.1.0.14.2.20011031184117.00b0da30@whisper.qrpff.net> (raw)
In-Reply-To: <E15ysre-0003FD-00@the-village.bc.nu>
In-Reply-To: <5.1.0.14.2.20011030235723.022818d8@whisper.qrpff.net>
At 10:44 AM 10/31/2001 +0000, Alan Cox wrote:
> > One other thing: how would the kernel react to the "SpeedStep" feature of
> > changing the CPU speed while things are still running?
>
>Depends on the laptop. Speedstop is not documented by intel so either it
>works because the APM bios did the right thing, or it doesn't work because
>it didn't. The only kernel issue is delay loops. We calibrate them at boot
>and assume the base clock is constant. In practice this isnt showing up as
>a real problem, although we do need to switch to the ACPI timers on later
>laptops
Yeah, that's what I'm concerned with -- the delay loops. I don't know what
they're used for, so I don't know what the CPU speed change would affect.
Mine would switch between 1.0GHz (996MHz according to /proc/cpuinfo) and
733MHz (730MHz). That's a difference of 36% - a timer calibrated to wait 1s
at 733MHz would only wait for 0.733s at 1GHz, and .3s can be quite
important in the computing world.
And, of course, since the BIOS can't handle APCI, using an APCI timer
wouldn't help much, would it?
--
Stevie-O
Real programmers use dd if=/dev/mouse of=a.out and move their mice around.
next prev parent reply other threads:[~2001-10-31 23:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-31 5:06 Stevie O
2001-10-31 10:44 ` Alan Cox
2001-10-31 11:26 ` Mikael Pettersson
2001-10-31 23:49 ` Stevie O [this message]
2001-10-31 20:11 Mikael Pettersson
2001-10-31 21:42 ` andersg
2001-10-31 22:17 Mikael Pettersson
2001-10-31 22:24 ` andersg
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=5.1.0.14.2.20011031184117.00b0da30@whisper.qrpff.net \
--to=stevie@qrpff.net \
--cc=alan@lxorguk.ukuu.org.uk \
--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
all inboxes | Powered by JetHome®