Re: [RFC 1/1] x86/vmemmap: Add missing update of PML4 table / PML5 table entry
From: Dave Hansen
Date: Fri Feb 14 2025 - 14:57:56 EST
On 2/14/25 11:51, Gwan-gyeong Mun wrote:
> when performing vmemmap populate, if the entry of the PML4 table/PML5 table
> pointing to the target virtual address has never been updated, a page fault
> occurs when the memset(start) called from the vmemmap_use_new_sub_pmd()
> execution flow.
"Page fault" meaning oops? Or something that we manage to handle and
return from without oopsing?
> This fixes the problem of using the virtual address without updating the
> entry in the PML4 table or PML5 table. But this is a temporary solution to
> prevent page fault problems, and it requires improvement of the routine
> that updates the missing entry in the PML4 table or PML5 table.
Can we please skip past the band-aid and go to the real fix?