History

memremap: fix highmem support

Currently memremap checks if the range is "System RAM" and returns the kernel linear address. This is broken for highmem platforms where a range may be "System RAM", but is not part of the kernel linear mapping. Fallback to ioremap_cache() in these cases, to let the arch code attempt to handle it. Note that ARM ioremap will WARN when attempting to remap ram, and in that case the caller needs to be fixed. For this reason, existing ioremap_cache() usages for ARM are already trained to avoid attempts to remap ram. The impact of this bug is low for now since the pmem driver is the only user of memremap(), but this is important to fix before more conversions to memremap arrive in 4.4.

Dan Williams committed 11 years ago

Commit 182475b1 parent 25cb62b1 file · +12 −2Browse files

Unified · Split

kernel/memremap.c+12−2
@@ -24,6 +24,16 @@ __weak void __iomem *ioremap_cache(resource_size_t offset, unsigned long size) · 23 unmodified lines
2424 }
2525 #endif
2626
27+static void *try_ram_remap(resource_size_t offset, size_t size)
28+{
29+ struct page *page = pfn_to_page(offset >> PAGE_SHIFT);
30+
31+ /* In the simple case just return the existing linear address */
32+ if (!PageHighMem(page))
33+ return __va(offset);
34+ return NULL; /* fallback to ioremap_cache */
35+}
36+
2737 /**
2838 * memremap() - remap an iomem_resource as cacheable memory
2939 * @offset: iomem resource start address
@@ -66,8 +76,8 @@ void *memremap(resource_size_t offset, size_t size, unsigned long flags) · 36 unmodified lines
6676 * the requested range is potentially in "System RAM"
6777 */
6878 if (is_ram == REGION_INTERSECTS)
69− addr = __va(offset);
70− else
79+ addr = try_ram_remap(offset, size);
80+ if (!addr)
7181 addr = ioremap_cache(offset, size);
7282 }
7383