On Thu, 2009-11-12 at 11:12 +0800, Yinghai Lu wrote: > ykzhao wrote: > > On Thu, 2009-11-12 at 03:05 +0800, Yinghai Lu wrote: > >> ykzhao wrote: > >>> On Wed, 2009-11-11 at 10:27 +0800, Yinghai Lu wrote: > >>>> try to find_e820_area/reserve_early, and call acpi_reserve_memory early > >>>> > >>>> to get area is below 1M > >>>> > >>>> -v2: change function name to acpi_reserve_wakeup_memory according to Rafael > >>> It seems that the function of find_e820_area is called in several > >>> places. > >>> >Initmem_init: bootmap = find_e820_area(0, end_pfn<<PAGE_SHIFT, > >>> bootmap_size, PAGE_SIZE); > >>> > >>> If we also call it in the acpi_reserve_wakeup_memory, do we get the same > >>> base address as that obtained in initmem_init? > >> no. find_e820_area will check the reserve res array that could be updated by reserve_early. > > It will check the reserved region array when calling the function of > > find_e820_area. > > But it seems that the array is not updated when the find_e820_area is > > called in the function of initmem_init. > > right after that will use reserve_bootmem for those range in initmem_init. Yes. The reserve_bootmem is called for the range in initmem_init. But the reserved_early array is not updated. > > also we could reserve_early there and let bootmem conversion to do that for us. > > but for numa there is some chance to use other node bootmem to for that bootdata and bitmap. > so make it simple just use reserve_bootmem there. > > YH -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
