kcore: register vmalloc area in generic way
For /proc/kcore, vmalloc areas are registered per arch. But, all of them registers same range of [VMALLOC_START...VMALLOC_END) This patch unifies them. By this. archs which have no kclist_add() hooks can see vmalloc area correctly. Signed-off-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> Cc: Ralf Baechle <ralf@linux-mips.org> Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org> Cc: WANG Cong <xiyou.wangcong@gmail.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
This commit is contained in:

committed by
Linus Torvalds

parent
c30bb2a25f
commit
a0614da88b
@@ -110,7 +110,6 @@ void free_initrd_mem(unsigned long start, unsigned long end)
|
||||
#endif
|
||||
|
||||
#ifdef CONFIG_PROC_KCORE
|
||||
static struct kcore_list kcore_vmem;
|
||||
|
||||
static int __init setup_kcore(void)
|
||||
{
|
||||
@@ -131,9 +130,6 @@ static int __init setup_kcore(void)
|
||||
kclist_add(kcore_mem, __va(base), size, KCORE_RAM);
|
||||
}
|
||||
|
||||
kclist_add(&kcore_vmem, (void *)VMALLOC_START,
|
||||
VMALLOC_END-VMALLOC_START, KCORE_VMALLOC);
|
||||
|
||||
return 0;
|
||||
}
|
||||
module_init(setup_kcore);
|
||||
|
Reference in New Issue
Block a user