ARM: 7646/1: mm: use static_vm for managing static mapped areas
authorJoonsoo Kim <js1304@gmail.com>
Sat, 9 Feb 2013 05:28:06 +0000 (06:28 +0100)
committerRussell King <rmk+kernel@arm.linux.org.uk>
Sat, 16 Feb 2013 17:54:22 +0000 (17:54 +0000)
commit101eeda38c0ab8a4f916176e325d9e036d981a24
tree874b1f0002c9153e6af28b1ec3dd6aa0e7737086
parented8fd2186a4e4f3b98434093b56f9b793d48443e
ARM: 7646/1: mm: use static_vm for managing static mapped areas

A static mapped area is ARM-specific, so it is better not to use
generic vmalloc data structure, that is, vmlist and vmlist_lock
for managing static mapped area. And it causes some needless overhead and
reducing this overhead is better idea.

Now, we have newly introduced static_vm infrastructure.
With it, we don't need to iterate all mapped areas. Instead, we just
iterate static mapped areas. It helps to reduce an overhead of finding
matched area. And architecture dependency on vmalloc layer is removed,
so it will help to maintainability for vmalloc layer.

Reviewed-by: Nicolas Pitre <nico@linaro.org>
Acked-by: Rob Herring <rob.herring@calxeda.com>
Tested-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
Signed-off-by: Joonsoo Kim <iamjoonsoo.kim@lge.com>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
arch/arm/mm/ioremap.c
arch/arm/mm/mmu.c