• KAMEZAWA Hiroyuki's avatar
    For /proc/kcore, each arch registers its memory range by kclist_add(). · 884a2e28
    KAMEZAWA Hiroyuki authored
    In usual,
    
    	- range of physical memory
    	- range of vmalloc area
    	- text, etc...
    
    are registered but "range of physical memory" has some troubles.  It
    doesn't updated at memory hotplug and it tend to include unnecessary
    memory holes.  Now, /proc/iomem (kernel/resource.c) includes required
    physical memory range information and it's properly updated at memory
    hotplug.  Then, it's good to avoid using its own code(duplicating
    information) and to rebuild kclist for physical memory based on
    /proc/iomem.
    Signed-off-by: default avatarKAMEZAWA 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: default avatarAndrew Morton <akpm@linux-foundation.org>
    884a2e28
init_64.c 23.4 KB