> Hmm, I assume these are some decisions that x86 platform will have to
> make going forward in a subsequent patch as the third patch does for
> the arm64 platform. But it is clearly beyond the scope of this patch
> which never intended to change existing behavior on a given platform.
>
Yeah, I
On 07/06/2020 02:33 PM, David Hildenbrand wrote:
>> return 0;
>> @@ -1505,7 +1505,7 @@ int __meminit vmemmap_populate(unsigned long start,
>> unsigned long end, int node,
>> int err;
>>
>> if (end - start < PAGES_PER_SECTION * sizeof(struct page))
>> -err =
> return 0;
> @@ -1505,7 +1505,7 @@ int __meminit vmemmap_populate(unsigned long start,
> unsigned long end, int node,
> int err;
>
> if (end - start < PAGES_PER_SECTION * sizeof(struct page))
> - err = vmemmap_populate_basepages(start, end, node);
> +
vmemmap_populate_basepages() is used across platforms to allocate backing
memory for vmemmap mapping. This is used as a standard default choice or
as a fallback when intended huge pages allocation fails. This just creates
entire vmemmap mapping with base pages (PAGE_SIZE).
On arm64 platforms,
4 matches
Mail list logo
