How MMU Enables Virtual Memory, Protection, and Process Isolation

Memory Management Unit (MMU)

The MMU is a hardware block positioned between the CPU and main memory. It translates virtual addresses to physical addresses, enforces access‑permission checks (read/write/execute), and can control cache behavior, thereby providing isolation and protection for modern operating systems.

Virtual address translation

When the CPU issues a virtual address, the MMU extracts the virtual page number, looks up the corresponding entry in the process’s page table, obtains the physical frame number, and concatenates the page offset to form the final physical address. This translation enables demand paging, memory protection, and the illusion of a large contiguous address space.

Illustrative example

Consider a program that needs a read‑only code region and a read‑write data region. On a system without an MMU both regions must be placed at fixed physical addresses; an out‑of‑range access can corrupt memory or crash the system. With an MMU the program works with virtual addresses; the MMU maps the code pages to read‑only physical frames and the data pages to writable frames. If the program accesses an unmapped or protected page, the MMU raises a page‑fault instead of allowing arbitrary memory corruption. The MMU can also map several virtual pages to the same physical frame (page sharing) to reduce RAM usage.

Isolation of identical virtual address spaces

Each process has its own virtual address space. The MMU keeps a separate page‑table context for each process (e.g., the CR3 register on x86). Identical virtual addresses in different processes are therefore translated to distinct physical frames, and page‑level permission bits prevent one process from reading or writing another’s memory.

Page tables

A page table stores the mapping virtual page → physical frame. Virtual addresses are divided into two fields:

| page number | offset |

The page number indexes the page‑table entry, which contains the frame number and permission bits. The offset selects the byte within the page (commonly 4 KB). The operating system creates, updates, and switches page tables on context switches, page faults, and memory‑allocation operations.

Why Linux requires an MMU

Linux relies on per‑process virtual address spaces, demand paging, copy‑on‑write, and fine‑grained memory protection. All of these features need hardware support for translating virtual addresses to physical memory. Without an MMU the kernel cannot isolate processes or provide virtual memory, so Linux cannot run.

Why some simple SoCs can run without an MMU

Real‑time operating systems (RTOS) and bare‑metal applications often target microcontrollers that lack an MMU. They use a flat physical address space, perform static memory allocation, and do not require page‑level protection or virtual‑memory features. This simplifies the memory model and guarantees deterministic latency, making it suitable for embedded systems without MMU hardware.