linux-kernel - Re: PAT and MTRRs

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:	Sun, 26 Oct 2008 17:38:23 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Arjan van de Ven <arjan@...radead.org>
CC:	"Diego M. Vadell" <dvadell@...uxclusters.com.ar>,
	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: PAT and MTRRs

Arjan van de Ven wrote:
>>>
>> Now, if it wasn't for the braindamage called ACPI and SMM, we could
>> have cleared the MTRR settings and just used PAT...
> 
> yeah.. one thing we need  to investigate is if we can set the default
> "no mtrr coverage" value to cached
> (and also.. to check we don't set that to uncached if the bios had it
> set to cached..)
> 

Well, in the end it comes down to the same thing: SMM expects the memory 
map to reside in MTRRs.  We can "sanitize" the memory map, but we can't 
throw it out the window like what we really should be able to.

	-hpa
--
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/