From: Mikael Pettersson <mikpe@csd.uu.se>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Mikael Pettersson <mikpe@csd.uu.se>, Andi Kleen <ak@suse.de>,
"David S. Miller" <davem@redhat.com>,
johnstul@us.ibm.com, James Cleverdon <jamesclv@us.ibm.com>,
linux-kernel@vger.kernel.org, anton.wilson@camotion.com
Subject: Re: do_gettimeofday vs. rdtsc in the scheduler
Date: Thu, 19 Sep 2002 15:39:35 +0200 [thread overview]
Message-ID: <15753.54167.111587.38417@kim.it.uu.se> (raw)
In-Reply-To: <1032442039.26712.32.camel@irongate.swansea.linux.org.uk>
Alan Cox writes:
> On Thu, 2002-09-19 at 12:20, Mikael Pettersson wrote:
> > > The local APIC timer is specified in the Intel Manual volume 3 for example.
> > > It's an optional feature (CPUID), but pretty much everyone has it.
> >
> > Except that like everything else related to the local APIC, you're at
> > the mercy of the competence (or lack thereof) of the BIOS implementors.
> > - There are plenty of laptops whose CPUs have local APICs but whose
> > BIOSen go berserk if you enable it. There are also plenty of laptops
>
> Frequently because we don't disable it again before any APM calls I
> suspect. When a CPU goes into sleep mode you must disable PMC and local
> apic timer interrupts.
We do on sane boxes where the APM BIOS informs us before suspending.
E.g., on my ASUS P3B-F & P4T-E suspend works with local APIC enabled
because I hooked both the NMI watchdog and local APIC to the
PM system, so we disable before suspending and restore afterwards.
The problem is that some BIOSen don't post the suspend event to
our APM driver, so we fail to disable before suspend, and some BIOSen
(like the utter crap Dell put in the Inspiron) die on all entries to
the BIOS: pull the power cord -> #SMM event -> box crashes.
/Mikael
next prev parent reply other threads:[~2002-09-19 13:34 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200209172020.g8HKKPF13227@eng2.beaverton.ibm.com.suse.lists.linux.kernel>
[not found] ` <1032294559.22815.180.camel@cog.suse.lists.linux.kernel>
[not found] ` <20020917.133933.69057655.davem@redhat.com.suse.lists.linux.kernel>
2002-09-17 21:00 ` Andi Kleen
2002-09-17 20:54 ` David S. Miller
2002-09-17 21:28 ` Alan Cox
2002-09-17 21:18 ` David S. Miller
2002-09-17 22:02 ` James Cleverdon
2002-09-17 22:44 ` Andi Kleen
2002-09-17 22:38 ` David S. Miller
2002-09-17 22:55 ` James Cleverdon
2002-09-17 23:12 ` David S. Miller
2002-09-17 23:32 ` john stultz
2002-09-17 23:32 ` David S. Miller
2002-09-17 23:52 ` Andi Kleen
2002-09-17 23:46 ` David S. Miller
2002-09-17 23:58 ` Andi Kleen
2002-09-17 23:51 ` David S. Miller
2002-09-18 0:05 ` Andi Kleen
2002-09-18 1:04 ` James Cleverdon
2002-09-19 18:02 ` Andrea Arcangeli
2002-09-20 11:04 ` Maciej W. Rozycki
2002-09-19 11:20 ` Mikael Pettersson
2002-09-19 13:27 ` Alan Cox
2002-09-19 13:39 ` Mikael Pettersson [this message]
2002-09-20 15:26 ` John Levon
2002-09-18 6:40 ` Vojtech Pavlik
2002-09-19 18:04 ` Andrea Arcangeli
[not found] <200209172020.g8HKKPF13227@eng2.beaverton.ibm.com>
2002-09-17 20:29 ` Fwd: " john stultz
2002-09-17 20:39 ` David S. Miller
2002-09-17 20:57 ` john stultz
2002-09-17 20:56 ` David S. Miller
2002-09-09 22:21 anton wilson
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=15753.54167.111587.38417@kim.it.uu.se \
--to=mikpe@csd.uu.se \
--cc=ak@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=anton.wilson@camotion.com \
--cc=davem@redhat.com \
--cc=jamesclv@us.ibm.com \
--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
all inboxes | Powered by JetHome®