3 ms·

I'm curious what software is telling the kernel no. What enforces this?

• ape4 4y ago
  Why the kernel of course (joke attempt, I am wondering too)
  • salawat 4y ago
    Probably firmware/hardware.
    • monocasa 4y ago
      It's the type 1 hypervisor it wants to run on top of.
      • salawat 4y ago
        Then would not the type 1 Hypervisor then become the "kernel" seing as we've defined kernels as "that chunk of code capable of unrestricted access to machine state"?
        • monocasa 4y ago
          The line blurs for sure. I would say it's 'a' kernel. The idea of there only being one kernel is probably a concept that makes for nice layered diagrams, but doesn't come close to describing reality because of the combinatorial complexity of options for different morphs of layering. Sort of like the OSI network layers model in that way.
• jandrese 4y ago
  The memory mapper. One of the side benefits of relocatable code is the ability to enforce policy at point of access.