linux-kernel - Re: [PATCH v2] x86: PAT: Documentation: rewrite "MTRR effects on PAT / non-PAT systems"

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] [day] [month] [year] [list]

Date:	Tue, 15 Mar 2016 23:24:22 +0100
From:	"Luis R. Rodriguez" <mcgrof@...nel.org>
To:	Ingo Molnar <mingo@...nel.org>
Cc:	"Luis R. Rodriguez" <mcgrof@...nel.org>,
	paulmck@...ux.vnet.ibm.com, bp@...en8.de, tglx@...utronix.de,
	hpa@...or.com, toshi.kani@...com, airlied@...hat.com,
	benh@...nel.crashing.org, mst@...hat.com, vinod.koul@...el.com,
	jgross@...e.com, daniel.vetter@...ll.ch, luto@...capital.net,
	davem@...emloft.net, ben@...adent.org.uk,
	benjamin.poirier@...il.com, linux-fbdev@...r.kernel.org,
	linux-arch@...r.kernel.org, linux-kernel@...r.kernel.org,
	x86@...nel.org, linux-doc@...r.kernel.org, corbet@....net
Subject: Re: [PATCH v2] x86: PAT: Documentation: rewrite "MTRR effects on PAT
 / non-PAT systems"

On Sat, Mar 05, 2016 at 12:52:55PM +0100, Ingo Molnar wrote:
> 
> * Luis R. Rodriguez <mcgrof@...nel.org> wrote:
> 
> > The current documentation refers to using set_memory_wc() as a
> > possible hole strategy when you have overlapping ioremap() regions,
> 
> The whole explanation should talk about virtual aliases over the same physical 
> address, not some 'overlapping regions'.
> 
> I see where this talk about 'overlap' comes: the memtype rbtree in 
> arch/x86/mm/pat_rbtree.c indeed has memtype ranges that may overlap on the 
> physical side. But it is highly confusing to call this 'overlapping' on the driver 
> API documentation level without making it really clear what it's about.

Alright thanks, I think I'll just stick to aliasing. I'll go over the
threads and pick out only what is relevant.

  Luis