Messages in this thread | | | Date | Sat, 16 Apr 2016 11:20:18 +0200 | From | Ingo Molnar <> | Subject | Re: Overlapping ioremap() calls, set_memory_*() semantics |
| |
* Toshi Kani <toshi.kani@hpe.com> wrote:
> On x86, ioremap() and remap_pfn_range() already fail on a conflicting cache > type if it is not allowed by the rule defined in is_new_memtype_allowed(). > This exception handling is necessary for remap_pfn_range() called by > /dev/mem, but I do not think it's necessary for ioremap(). I think we can > start from adding a warning message to ioremap().
Agreed, we should warn and map the situation before doing any behavioral change that isn't a fix.
Thanks,
Ingo
| |