Thread (11 messages) 11 messages, 4 authors, 2016-03-15

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

flat view

From: "Luis R. Rodriguez" <mcgrof@kernel.org>
Date: 2016-03-15 22:24:28
Also in: linux-arch, lkml

On Sat, Mar 05, 2016 at 12:52:55PM +0100, Ingo Molnar wrote:
* Luis R. Rodriguez [off-list ref] wrote:
quoted
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
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help