From: Linus Torvalds <torvalds@osdl.org>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: "Sérgio Monteiro Basto" <sergiomb@netcabo.pt>,
"Len Brown" <len.brown@intel.com>,
"Andrew Morton" <akpm@osdl.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"ACPI Developers" <acpi-devel@lists.sourceforge.net>
Subject: Re: [ACPI] Re: [BKPATCH] LAPIC fix for 2.6
Date: Sun, 10 Oct 2004 19:44:41 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.58.0410101941590.3897@ppc970.osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.58L.0410110132170.4217@blysk.ds.pg.gda.pl>
On Mon, 11 Oct 2004, Maciej W. Rozycki wrote:
>
> How about only disabling the APIC if power-management is in use?
No. You cannot test for SMM. Full stop. That's the whole _point_ of SMM.
It's hidden away.
Why do you care? If you have a machine with this problem, just use the
"lapic" command line. We do NOT default to unsafe values.
> I don't like the idea of "punishing" good hardware, because something
> behaves ill out there.
We don't punish good hardware.
We punish _bad_ hardware. The kind of hardware that has a BIOS that has
disabled the local APIC.
Try to get your BIOS updated if you want to consider your hardware "good".
And if the hw vendor doesn't have a fixed BIOS, then don't call it good,
and use "lapic".
Linus
next prev parent reply other threads:[~2004-10-11 2:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-10 17:35 Len Brown
2004-10-10 17:45 ` Linus Torvalds
2004-10-10 19:04 ` Maciej W. Rozycki
2004-10-10 21:19 ` [ACPI] " Sérgio Monteiro Basto
2004-10-11 1:44 ` Maciej W. Rozycki
2004-10-11 2:44 ` Linus Torvalds [this message]
2004-10-11 0:47 ` Linus Torvalds
2004-10-11 11:42 ` [ACPI] " 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=Pine.LNX.4.58.0410101941590.3897@ppc970.osdl.org \
--to=torvalds@osdl.org \
--cc=acpi-devel@lists.sourceforge.net \
--cc=akpm@osdl.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@linux-mips.org \
--cc=sergiomb@netcabo.pt \
/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®