Re: [PATCH v4 1/3] x86/vmemmap: Drop handling of 4K unaligned vmemmap range

On 3/8/21 10:20 AM, Oscar Salvador wrote: > On Thu, Mar 04, 2021 at 07:50:10AM -0800, Dave Hansen wrote: >> On 3/1/21 12:32 AM, Oscar Salvador wrote: >>> remove_pte_table() is prepared to handle the case where either the >>> start or the end of the range is not PAGE aligned. >>> This cannot

Re: [PATCH v4 1/3] x86/vmemmap: Drop handling of 4K unaligned vmemmap range

On Thu, Mar 04, 2021 at 07:50:10AM -0800, Dave Hansen wrote: > On 3/1/21 12:32 AM, Oscar Salvador wrote: > > remove_pte_table() is prepared to handle the case where either the > > start or the end of the range is not PAGE aligned. > > This cannot actually happen: > > > > __populate_section_memmap

Re: [PATCH v4 1/3] x86/vmemmap: Drop handling of 4K unaligned vmemmap range

On 3/1/21 12:32 AM, Oscar Salvador wrote: > remove_pte_table() is prepared to handle the case where either the > start or the end of the range is not PAGE aligned. > This cannot actually happen: > > __populate_section_memmap enforces the range to be PMD aligned, > so as long as the size of the

[PATCH v4 1/3] x86/vmemmap: Drop handling of 4K unaligned vmemmap range

remove_pte_table() is prepared to handle the case where either the start or the end of the range is not PAGE aligned. This cannot actually happen: __populate_section_memmap enforces the range to be PMD aligned, so as long as the size of the struct page remains multiple of 8, the vmemmap range