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
PML5 is an Intel extension to increase addressable space from 256TB to 128PB (see wikipedia).
I admit it is a niche use case 🙂 But I was still wondering if there is any reason to not support it?
Since it uses bits from 48 to 57 for the new level, I guess it would break the safety checks for the VirtAddr type, are there other things that would break?
NB: The limine bootloader provides a way to detect if the CPU has the PML5 extension.
The text was updated successfully, but these errors were encountered:
AFAIK there is no reason we don't support 5-level paging, it's just that no one has implemented it yet. It might require redesigning some of the abstractions to support both 4-level and 5-level paging. Feel free to come up with ideas.
Since it uses bits from 48 to 57 for the new level, I guess it would break the safety checks for the VirtAddr type, are there other things that would break?
This would also break/require redesign of the page table related abstraction including Mapper and its implementations.
For VirtAddr, we could add a new generic parameter that allows specifying 4-level or 5-level paging. If we default to 4-level paging, we might be even able to avoid a breaking change. Maybe it's also possible to something similar for OffsetPageTable, etc.
PML5 is an Intel extension to increase addressable space from 256TB to 128PB (see wikipedia).
I admit it is a niche use case 🙂 But I was still wondering if there is any reason to not support it?
Since it uses bits from 48 to 57 for the new level, I guess it would break the safety checks for the
VirtAddr
type, are there other things that would break?NB: The limine bootloader provides a way to detect if the CPU has the PML5 extension.
The text was updated successfully, but these errors were encountered: