From: Andi Kleen <ak@muc.de>
To: Alexandre Oliva <aoliva@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: K8 Errata #93: adjusting address to a fixup block
Date: Sun, 17 Oct 2004 22:23:29 +0200 [thread overview]
Message-ID: <m3is99xfem.fsf@averell.firstfloor.org> (raw)
In-Reply-To: <2Qpmj-1uX-13@gated-at.bofh.it> (Alexandre Oliva's message of "Sun, 17 Oct 2004 22:00:11 +0200")
Alexandre Oliva <aoliva@redhat.com> writes:
> While I investigated the problem of probing the touchpad on a Compaq
> Presario r3004, I'd sometimes get the K8 Errata #93 warning. One of
> my theories was that we might be missing some fix up because of the
> Errata, or adjusting an address that wasn't the current-instruction
It's more likely the BIOS is executing SMM code to handle
the touch pad and that SMM code doesn't have the correct
workaround for the erratum.
> address, so I came up with this patch. It turned out to make no
> difference, but it still feels like an improvement to me, since some
> day we might be resuming from halt into a fix-up block. Thoughts?
The code is already ugly enough and handles most of the cases,
I don't think it is worth it complicating it even more just
to handle more corner cases of buggy BIOS.
The real fix is to fix your BIOS.
static int warned;
+ if ((error_code & 16) == 0)
+ return 0;
This is dubious because the I/D bit is undefined when NX is disabled
in EFER (e.g. with noexec=off or when the CPU doesn't support NX)
-Andi
next parent reply other threads:[~2004-10-17 20:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2Qpmj-1uX-13@gated-at.bofh.it>
2004-10-17 20:23 ` Andi Kleen [this message]
2004-10-21 16:49 ` K8 Errata #93: adjusting address to a fixup block Alexandre Oliva
2004-10-17 19:46 Alexandre Oliva
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=m3is99xfem.fsf@averell.firstfloor.org \
--to=ak@muc.de \
--cc=aoliva@redhat.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