From: Ondrej Zary <linux@rainbow-software.org>
To: "linux-os (Dick Johnson)" <linux-os@analogic.com>
Cc: Zachary Amsden <zach@vmware.com>,
"Maciej W. Rozycki" <macro@linux-mips.org>,
Andi Kleen <ak@suse.de>,
linux-kernel@vger.kernel.org
Subject: Re: 2.6.14: CR4 not needed to be inspected on the 486 anymore?
Date: Mon, 07 Nov 2005 20:02:35 +0100 [thread overview]
Message-ID: <436FA4CB.6020406@rainbow-software.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0511071313330.27911@chaos.analogic.com>
linux-os (Dick Johnson) wrote:
>>No, you won't. #UD and #GP will not (I hesitate to say never, but other
>>than a processor bug, I believe that is correct) reset the processor.
>>And CR4 is not "undocumented", even on 486.
>>
>
>
> Yes it is. The i486 Programmer's reference manual documents only
> to CR3.
The manual might be older than the newer 486 CPUs.
And don't forget that not every 486 is Intel. There are at least Cyrix,
AMD and UMC with interesting Am5x86-P75 and Cx5x86 too.
--
Ondrej Zary
next prev parent reply other threads:[~2005-11-07 19:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-03 16:12 2.6.14: CR4 not needed to be inspected on the 486 anymore? Maciej W. Rozycki
2005-11-03 16:34 ` Zachary Amsden
2005-11-03 17:20 ` Maciej W. Rozycki
2005-11-03 23:49 ` Zachary Amsden
2005-11-05 17:40 ` Andi Kleen
2005-11-07 9:38 ` Maciej W. Rozycki
2005-11-07 15:44 ` Zachary Amsden
2005-11-07 16:37 ` Maciej W. Rozycki
2005-11-07 16:51 ` Zachary Amsden
2005-11-07 17:00 ` linux-os (Dick Johnson)
2005-11-07 17:32 ` Zachary Amsden
2005-11-07 18:17 ` linux-os (Dick Johnson)
2005-11-07 19:02 ` Ondrej Zary [this message]
2005-11-07 17:11 ` Maciej W. Rozycki
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=436FA4CB.6020406@rainbow-software.org \
--to=linux@rainbow-software.org \
--cc=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-os@analogic.com \
--cc=macro@linux-mips.org \
--cc=zach@vmware.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