Understanding limited direct execution and kernel transitions
This is an easy operating-systems question that tests your grasp of how the OS maintains security and control through limited direct execution. It probes whether you understand the fundamental mechanism by which user-mode programs request kernel services and how the hardware enforces the boundary between privileged and unprivileged execution.
The question focuses on the special instructions and hardware structures that enable safe mode transitions. When a program needs a kernel service—such as I/O, memory management, or system calls—it cannot simply jump into kernel code. Instead, the hardware provides dedicated instructions to enter the kernel and return safely, along with a way for the OS to register the entry point where the kernel handles these transitions. Understanding these primitives is essential for reasoning about process isolation, security, and how modern operating systems actually work.
- Mode bits and privilege levels in the CPU
- System calls and trap instructions
- Trap handlers and exception tables
- User-mode vs. kernel-mode execution