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
I'm trying to mimic Linux kernel behavior to shift the physical offset to start from 0xffff888000000000. However I'm trying to do this without the OS knowing this proactively (I have a custom UEFI bootloader that sets up an independent page table away from UEFI's influence), so that I can implement KASLR easily later.
I also have a ELF loader to relocate my kernel into the right virtual address, or at least it should somehow work.
The problem is, since all the physical memory will start at 0xffff888000000000, that won't pass PhysAddr::new right? And so it won't be a valid PhysFrame either.
The text was updated successfully, but these errors were encountered:
I think there's a misunderstanding here: PhysAddr is a type used for physical addresses, not the virtual addresses of mappings of physical memory, these should use VirtAddr.
I'm trying to mimic Linux kernel behavior to shift the physical offset to start from 0xffff888000000000. However I'm trying to do this without the OS knowing this proactively (I have a custom UEFI bootloader that sets up an independent page table away from UEFI's influence), so that I can implement KASLR easily later.
I also have a ELF loader to relocate my kernel into the right virtual address, or at least it should somehow work.
The problem is, since all the physical memory will start at 0xffff888000000000, that won't pass PhysAddr::new right? And so it won't be a valid PhysFrame either.
The text was updated successfully, but these errors were encountered: