linux-kernel - Re: MTRR initialization

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, 20 Sep 2007 08:03:31 -0700
From:	Jesse Barnes <jbarnes@...tuousgeek.org>
To:	Andi Kleen <andi@...stfloor.org>
Cc:	Jesse Barnes <jesse.barnes@...el.com>, Howard Chu <hyc@...as.com>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: MTRR initialization

On Wednesday, September 19, 2007 11:50:23 pm Andi Kleen wrote:
> Jesse Barnes <jesse.barnes@...el.com> writes:
> > To do this in a nicer way (and be less vulnerable to similar BIOS
> > funkiness) the kernel really needs full PAT support.  That should allow
> > WC over WB and WC over UC mappings to occur, at least if I'm
> > remembering the docs right...
>
> PAT only really helps for device driver performance optimizations.
> But if the basic WB MTRRs are wrong PAT cannot really salvage it.

Look at the original bug report.  There's a bug WB region so any subsequent WC 
mappings via the MTRRs won't work, so you need PAT to do WC (unless you want 
to rewrite all your MTRR settings as Howard has to do now).

Seems like more and more machines are being setup this way, and until we have 
PAT users will have to jump through hoops to get good performance.

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