summaryrefslogtreecommitdiffstats
path: root/arch/powerpc/mm/pgtable_32.c
diff options
context:
space:
mode:
authorMichael Ellerman2010-11-28 19:26:36 +0100
committerBenjamin Herrenschmidt2010-12-09 05:35:32 +0100
commit7a9d12568e34e37a72d9e00ce01b62dec527e663 (patch)
tree117f1d41ae3fe773bca81d9a4c6286c2f9ff2134 /arch/powerpc/mm/pgtable_32.c
parentpowerpc: Update compat_arch_ptrace (diff)
downloadkernel-qcow2-linux-7a9d12568e34e37a72d9e00ce01b62dec527e663.tar.gz
kernel-qcow2-linux-7a9d12568e34e37a72d9e00ce01b62dec527e663.tar.xz
kernel-qcow2-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_32.c')
-rw-r--r--arch/powerpc/mm/pgtable_32.c1
1 files changed, 1 insertions, 0 deletions
diff --git a/arch/powerpc/mm/pgtable_32.c b/arch/powerpc/mm/pgtable_32.c
index a87ead0138b4..71932d000a72 100644
--- a/arch/powerpc/mm/pgtable_32.c
+++ b/arch/powerpc/mm/pgtable_32.c
@@ -230,6 +230,7 @@ __ioremap_caller(phys_addr_t addr, unsigned long size, unsigned long flags,
area = get_vm_area_caller(size, VM_IOREMAP, caller);
if (area == 0)
return NULL;
+ area->phys_addr = p;
v = (unsigned long) area->addr;
} else {
v = (ioremap_bot -= size);