lkml.org 
[lkml]   [2016]   [Mar]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [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@kernel.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

\
 
 \ /
  Last update: 2016-03-16 00:01    [W:0.120 / U:0.020 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site