I suspect it's less "acceptable" and more "resigned to accepting it, because the alternatives are harder"
If you allow EFI code from system or peripheral firmware to run on the metal, it can happen any time they decide they want to. That's the problem. It should _only_ be possible when OS does it.
-
-
No. It can only happen when the OS calls into said EFI code. Functions don't just call themselves
-
Like when some hardware driver calls into firmware on the metal in ring0 with unrestricted memory access rather than actually implementing the functionality itself.
-
The only times the kernel calls into UEFI are To exit boot services mode To ger/set firmware variables As a last ditch way of rebooting As a last ditch way of getting/setting the time (no RTC driver) To set wake from power off timers
-
That's a smaller set than I expected, but still much more than it should be, and would benefit from virtualization if the user wants any of that functionality.
-
Fortunately there's always: # CONFIG_EFI is not set
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.