On Mon, Mar 25, 2013 at 01:11:13PM +0900, Joonsoo Kim wrote: > nobootmem use max_low_pfn for computing boundary in free_all_bootmem() > So we need proper value to max_low_pfn. > > But, there is some difficulty related to max_low_pfn. max_low_pfn is used > for two meanings in various architectures. One is for number of pages > in lowmem and the other is for maximum lowmem pfn. Now, in ARM, it is used > as number of pages in lowmem. You can get more information in below link. > http://lwn.net/Articles/543408/ > http://lwn.net/Articles/543424/ > > As I investigated, architectures which use max_low_pfn as maximum pfn are > more than others, so to change meaning of max_low_pfn to maximum pfn > is preferable solution to me. This patch change max_low_pfn as maximum > lowmem pfn in ARM. In addition, min_low_pfn, max_pfn is assigned according > to this criteria. > > There is no real user for max_low_pfn except block/blk-setting.c and > blk-setting.c assume that max_low_pfn is maximum lowmem pfn, > so this patch may not harm anything.
This will need some very rigorous testing before it can go into mainline. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
