linux-kernel - Re: [PATCH] Fix i486 suspend to disk CR4 oops

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 18 Aug 2008 15:38:09 +0100 (BST)
From:	"Maciej W. Rozycki" <macro@...ux-mips.org>
To:	David Fries <david@...es.net>
cc:	Ingo Molnar <mingo@...e.hu>, linux-kernel@...r.kernel.org,
	Pavel Machek <pavel@....cz>, "H. Peter Anvin" <hpa@...or.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	"Rafael J. Wysocki" <rjw@...k.pl>
Subject: Re: [PATCH] Fix i486 suspend to disk CR4 oops

On Mon, 18 Aug 2008, David Fries wrote:

> That's what I get for reading the Intel instruction set reference,
> "The CR4 register was added to the Intel Architecture beginning with
> the Pentium processor."

 Indeed.  It started with the Pentium and some of the i486
models/steppings that were released after the Pentium got the CR4 register
implemented too.  These include at the least the write-back enhanced 
versions of the iDX2 and iDX4 processors as well later steppings of the 
i486SX, which I encountered myself.  There could be others -- iSX2?

 Unfortunately as usually with Intel you have to read all the documents
they release to hope to get a full image and even then you'll probably
come out confused and with bits of data missing -- if in doubt, check the
silicon: it has the most definite information.  However these additions
were actually documented quite well in the respective i486-class processor
datasheets -- IIRC Intel have released a combined version at one point.  
I am not sure whether it has ever been available on-line.

  Maciej
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/