On Wed, 03 Oct 2007 08:35:35 -0700 Badari Pulavarty <[EMAIL PROTECTED]> wrote:
> On Wed, 2007-10-03 at 10:19 +0900, KAMEZAWA Hiroyuki wrote: > CONFIG_ARCH_HAS_VALID_MEMORY_RANGE. Then define own > find_next_system_ram() (rename to is_valid_memory_range()) - which > checks the given range is a valid memory range for memory-remove > or not. What do you think ? > My concern is... Now, memory hot *add* makes use of resource(/proc/iomem) information for onlining memory.(See add_memory()->register_memory_resource() in mm/memoryhotplug.c) So, we'll have to consider changing it if we need. Does PPC64 memory hot add registers new memory information to arch dependent information list ? It seems ppc64 registers hot-added memory information from *probe* file and registers it by add_memory()->register_memory_resource(). If you add all add/remove/walk system ram information in sane way, I have no objection. I like find_next_system_ram() because I used some amount of time to debug it ;) Thanks, -Kame _______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
