poking at cr3 is morally wrong
osresearch opened this issue · comments
We should feel bad for how hackish the module is. Directly poking at cr3 to map the UEFI space is definitely not the right way to do this; we should figure out how to do it right.
We should feel bad for how hackish the module is. Directly poking at cr3 to map the UEFI space is definitely not the right way to do this; we should figure out how to do it right.
You can.