linux-kernel - Re: [PATCH] EFI: Only set regions uncacheable if they support it

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:	Thu, 15 Mar 2012 07:47:57 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Matthew Garrett <mjg@...hat.com>
CC:	linux-kernel@...r.kernel.org, x86@...nel.org,
	matt.fleming@...el.com
Subject: Re: [PATCH] EFI: Only set regions uncacheable if they support it

On 03/15/2012 07:42 AM, Matthew Garrett wrote:
> On Thu, Mar 15, 2012 at 07:36:46AM -0700, H. Peter Anvin wrote:
> 
>> I would still really like to understand why we're seeing #MCs... that's
>> bothersome all by itself.
> 
> The region is the legacy video RAM, so I can imagine there being 
> something magic about it.
> 

WTF?!  That should be UC at all times... it isn't even WC-capable.
Furthermore, we may need this region (assuming there is actually a video
card there.)

What do the fixed MTRRs look like?

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