From: Mikael Pettersson <mikpe@csd.uu.se>
To: bgerst@didntduck.org
Cc: linux-kernel@vger.kernel.org, torvalds@transmeta.com
Subject: Re: [PATCH] Cleanup f00f bug code
Date: Fri, 28 Sep 2001 01:13:50 +0200 (MET DST) [thread overview]
Message-ID: <200109272313.BAA16620@harpo.it.uu.se> (raw)
On Wed, 26 Sep 2001 21:52:09 -0400, Brian Gerst wrote:
>This patch changes the f00f bug workaround code to use a fixed mapping
>instead of touching the page tables directly. It also removes the
>assumption that only 686's don't have the bug. It has been tested for
>normal operation of the relocated IDT, but I don't have a processor with
>the bug to do a real test. Could someone with such a processor please
>verify that the workaround still works?
It doesn't. 2.4.9-ac16 + your patch booted ok on my P5MMX, and the
kernel printed that it applied the F0 0F workaround, but executing
F0 0F C7 C8 in user-space caused an instant lockup.
/Mikael
next reply other threads:[~2001-09-27 23:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-27 23:13 Mikael Pettersson [this message]
2001-09-29 13:35 ` Brian Gerst
-- strict thread matches above, loose matches on Subject: below --
2002-02-20 1:17 [PATCH] Cleanup F00F " Brian Gerst
2001-09-27 1:52 [PATCH] Cleanup f00f " Brian Gerst
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=200109272313.BAA16620@harpo.it.uu.se \
--to=mikpe@csd.uu.se \
--cc=bgerst@didntduck.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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
all inboxes | Powered by JetHome®