You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the current implementation, BootMem::PhysicalMemoryAllocateIDMappedBlock routine identity maps more memory if we run out of them for creating page tables. However, we never check if the next Identity Mapped Address exceeds 1024M and keep mapping more memory. This would become fatal as when were > 1024M we move to the next PDT which might not exist.
Troubleshooting
This is a known issue and was left out for a future implementation. See Line 174/175 in kernel/mem/bootmem.cpp.
Recommendations
Use the BootMem::PhysicalMemoryMapToOffset(...) routine to map the memory instead as it automatically creates page tables if they do not exist.
The text was updated successfully, but these errors were encountered:
Issue Description
In the current implementation,
BootMem::PhysicalMemoryAllocateIDMappedBlock
routine identity maps more memory if we run out of them for creating page tables. However, we never check if the next Identity Mapped Address exceeds 1024M and keep mapping more memory. This would become fatal as when were > 1024M we move to the next PDT which might not exist.Troubleshooting
This is a known issue and was left out for a future implementation. See Line 174/175 in
kernel/mem/bootmem.cpp
.Recommendations
BootMem::PhysicalMemoryMapToOffset(...)
routine to map the memory instead as it automatically creates page tables if they do not exist.The text was updated successfully, but these errors were encountered: