[PATCH v2 08/25] arch: introduce memremap()

From
Dan Williams <hidden>
Date
2015-07-26 17:49:42
Also in
linux-arch, lkml, nvdimm
Reply to
Christoph Hellwig, 2015-07-26
On Sun, Jul 26, 2015 at 10:25 AM, Christoph Hellwig [off-list ref] wrote:
On Fri, Jul 24, 2015 at 10:38:42PM -0400, Dan Williams wrote:
quoted
The behavior change to return NULL on an unsupported request is reserved
for a later patch.
Why?
This is for drivers like pmem that care about the mapping type.  For
example, if pmem can't get a cache-enabled mapping it is potentially
putting the write durability of the persistent media at risk.
quoted
+enum {
+     MEMREMAP_WB = 1 << 0,
+     MEMREMAP_WT = 1 << 1,
+     MEMREMAP_CACHE = MEMREMAP_WB,
What's the point of having this MEMREMAP_CACHE alias?
For developers that are used to seeing ioremap_cache()...
Also please document the meaning of the flags for the poor users.
Will do.  I'll mostly borrow from the x86 mapping type definitions,
but these will also have architecture specific semantics /
constraints.
Thread (67 messages) 67 messages, 10 authors, last reply 2016-04-21
Keyboard shortcuts
hback out one level
jnext message in thread / next series-diff position
kprevious message in thread / previous series-diff position
ldrill in
Escclose help / fold thread tree
?toggle this help