summaryrefslogtreecommitdiffstats
path: root/arch/powerpc/mm/pgtable_64.c
diff options
context:
space:
mode:
authorMichael Ellerman <michael@ellerman.id.au>2010-11-28 19:26:36 +0100
committerBenjamin Herrenschmidt <benh@kernel.crashing.org>2010-12-09 05:35:32 +0100
commit7a9d12568e34e37a72d9e00ce01b62dec527e663 (patch)
tree117f1d41ae3fe773bca81d9a4c6286c2f9ff2134 /arch/powerpc/mm/pgtable_64.c
parentpowerpc: Update compat_arch_ptrace (diff)
downloadlinux-7a9d12568e34e37a72d9e00ce01b62dec527e663.tar.xz
linux-7a9d12568e34e37a72d9e00ce01b62dec527e663.zip
powerpc: Record vma->phys_addr in ioremap()
The vmalloc code can track the physical address of a vma, when the vma is used for ioremap, if set it is displayed in /proc/vmallocinfo. Because get_vm_area_caller() doesn't know it's being called for ioremap() it's up to the arch code to set the phys_addr. A bunch of other arch's do this, I'm not sure why powerpc doesn't? Signed-off-by: Michael Ellerman <michael@ellerman.id.au> Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Diffstat (limited to 'arch/powerpc/mm/pgtable_64.c')
-rw-r--r--arch/powerpc/mm/pgtable_64.c2
1 files changed, 2 insertions, 0 deletions
diff --git a/arch/powerpc/mm/pgtable_64.c b/arch/powerpc/mm/pgtable_64.c
index 21d6dfab7942..88927a05cdc2 100644
--- a/arch/powerpc/mm/pgtable_64.c
+++ b/arch/powerpc/mm/pgtable_64.c
@@ -223,6 +223,8 @@ void __iomem * __ioremap_caller(phys_addr_t addr, unsigned long size,
caller);
if (area == NULL)
return NULL;
+
+ area->phys_addr = paligned;
ret = __ioremap_at(paligned, area->addr, size, flags);
if (!ret)
vunmap(area->addr);