Core Access vs Protected Space, Explained
The distinction between privileged execution and the more constrained world of applications and services.
Two execution contexts
A privileged kernel context coordinates memory, scheduling, and devices, while user mode gives applications useful interfaces without granting unrestricted access to those resources.
The boundary is practical
Crossing from an application into a driver involves a defined system call, API, or device interface. Parameters are validated and represented according to a contract so that user data is not treated as trusted kernel state.
Drivers can bridge contexts
A driver may receive requests from user mode and perform privileged hardware work. Its interface must therefore define buffers, access rights, lifetime, cancellation, and completion rather than relying on the caller to understand hardware.
Protected does not mean invisible
User-mode components can observe results and use supported operations. Protection limits direct authority; it does not prevent communication through documented boundaries.
Reference facts
- Kernel mode
- Privileged context for core resource and hardware coordination.
- User mode
- Constrained context for applications and services using defined interfaces.
Questions and answers
Can an application talk to hardware?
It can request supported operations through host and driver interfaces. Direct unrestricted access is a different privilege model.
Why validate user-mode parameters?
The kernel boundary must distinguish caller-controlled data from trusted system state and enforce the interface’s access and lifetime rules.