Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1380533 > unrolled thread
| Started by | Ingo Molnar <mingo@kernel.org> |
|---|---|
| First post | 2016-04-16 11:30 +0200 |
| Last post | 2016-04-16 11:30 +0200 |
| Articles | 1 — 1 participant |
Back to article view | Back to linux.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: Overlapping ioremap() calls, set_memory_*() semantics Ingo Molnar <mingo@kernel.org> - 2016-04-16 11:30 +0200
| From | Ingo Molnar <mingo@kernel.org> |
|---|---|
| Date | 2016-04-16 11:30 +0200 |
| Subject | Re: Overlapping ioremap() calls, set_memory_*() semantics |
| Message-ID | <rouIa-1dw-15@gated-at.bofh.it> |
* 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
Back to top | Article view | linux.kernel
csiph-web