Re: [PATCH v2] mm/mm_init.c: print mem_init info after defer_init is done

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Jun 11, 2024 at 05:12:13PM +0200, David Hildenbrand wrote:
>On 11.06.24 16:52, Wei Yang wrote:
>> Current call flow looks like this:
>> 
>> start_kernel
>>    mm_core_init
>>      mem_init
>>      mem_init_print_info
>>    rest_init
>>      kernel_init
>>        kernel_init_freeable
>>          page_alloc_init_late
>>            deferred_init_memmap
>> 
>> If CONFIG_DEFERRED_STRUCT_PAGE_INIT, the time mem_init_print_info()
>> calls, pages are not totally initialized and freed to buddy.
>> 
>> This has one issue
>> 
>>    * nr_free_pages() just contains partial free pages in the system,
>>      which is not we expect.
>> 
>> Let's print the mem info after defer_init is done.
>> 
>> Also this would help changing totalram_pages accounting, since we plan
>> to move the accounting into __free_pages_core().
>> 
>> Signed-off-by: Wei Yang <richard.weiyang@xxxxxxxxx>
>> CC: David Hildenbrand <david@xxxxxxxxxx>
>
>Acked-by: David Hildenbrand <david@xxxxxxxxxx>
>
>Hoping this won't reveal other surprises.
>

:-)

>-- 
>Cheers,
>
>David / dhildenb

-- 
Wei Yang
Help you, Help me




[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux