0Pricing
Assembly Language & x86 Low-Level Systems Programming · 课时

分页与内存管理单元(MMU)

理解 x86 MMU 如何通过页表和页目录将虚拟地址转换为物理地址。

分页与内存管理单元(MMU) 是 CoddyKit 上的免费 Assembly Language & x86 Low-Level Systems Programming 课时。 这是第 1 节课,共 4 节。 你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 AI 导师进行实践。 这是 Assembly Language & x86 Low-Level Systems Programming 学习路径的一部分,你的进度在网页和 CoddyKit 应用中同步。 Assembly Language & x86 Low-Level Systems Programming 课程共包含 4 节课。

本课时的部分内容尚未翻译,以英文显示。

What is Paging?

Welcome! Today we'll explore Paging, a crucial memory management technique in x86 systems. It's how your computer handles memory safely and efficiently.

Paging allows programs to think they have a huge, continuous block of memory, even if the physical RAM is fragmented or smaller than what the program needs.

Virtual vs. Physical Address

When a program runs, it uses virtual addresses. These are logical addresses that the program 'sees' and uses to refer to data and instructions.

However, the CPU and actual RAM hardware use physical addresses. Paging is the system that translates virtual addresses into physical addresses.

The MMU's Role

The translation from virtual to physical addresses is handled by a special hardware component inside the CPU called the Memory Management Unit (MMU).

The MMU acts like a super-fast translator, ensuring that every memory access from a program goes to the correct physical location in RAM, or signals an error if it's an invalid access.

Pages and Page Frames

For paging to work, memory is divided into fixed-size blocks:

  • Pages: These are the blocks of virtual memory that a program sees.
  • Page Frames: These are the blocks of physical memory (RAM).

On x86 systems, a common page size is 4 Kilobytes (4KB). The MMU translates virtual pages to physical page frames.

Introducing Page Tables

How does the MMU know which virtual page maps to which physical page frame? It uses data structures called page tables.

A page table is essentially an array where each entry maps a virtual page number to its corresponding physical page frame address. Each running process has its own set of page tables.

Multi-Level Paging: Page Directories

For very large virtual address spaces (like 32-bit or 64-bit systems), a single page table would be enormous. To manage this, x86 uses a multi-level paging hierarchy.

The first level is the Page Directory. It doesn't point directly to page frames, but to other Page Tables. These secondary tables then point to the actual physical page frames.

The Address Translation Process

Let's simplify the 32-bit address translation process:

  1. The CPU generates a virtual address.
  2. The MMU uses the upper bits of this address to find an entry in the Page Directory.
  3. That entry points to a specific Page Table.
  4. The MMU uses middle bits of the virtual address to find an entry in that Page Table.
  5. This entry contains the physical address of the Page Frame.
  6. The lower bits of the original virtual address (the offset) are added to the page frame address to get the final physical address.

CR3: The Paging Root

How does the MMU know where the Page Directory is for the current process?

The CPU has a special control register called CR3. This register holds the physical address of the current Page Directory Base Register (PDBR). It tells the MMU exactly where to start looking for the page directory.

PTE Flags and Permissions

Each entry in a Page Table (a PTE - Page Table Entry) contains more than just the physical address. It also has various flags:

  • Present: Is the page currently in physical memory?
  • Read/Write: Can the page be written to?
  • User/Supervisor: Can user-mode programs access this page?
  • Accessed: Has the page been accessed recently?
  • Dirty: Has the page been written to since it was loaded?

These flags are vital for memory protection and virtualization.

Benefits of Paging

Paging is fundamental to modern operating systems due to its many benefits:

  • Memory Protection: Isolates processes, preventing them from corrupting each other's memory.
  • Virtual Memory: Allows programs to use more memory than physically available by swapping pages to disk.
  • Memory Sharing: Multiple processes can share the same physical pages (e.g., for shared libraries or inter-process communication).
  • Relocation: Programs can be loaded anywhere in physical memory; the MMU handles the mapping.

Paging Knowledge Check

Which of the following best describes the primary function of the Memory Management Unit (MMU) in an x86 system?

Paging & MMU Recap

Great job! You've learned about the critical role of Paging and the MMU.

  • Programs use virtual addresses, while hardware uses physical addresses.
  • The MMU translates these addresses using Page Directories and Page Tables.
  • Memory is divided into pages (virtual) and page frames (physical).
  • The CR3 register points to the current Page Directory.
  • PTE flags control permissions and page status.

This system provides essential memory protection, virtual memory, and flexible memory management for all modern operating systems.

常见问题解答

「分页与内存管理单元(MMU)」课时是免费的吗?

是的 — 「分页与内存管理单元(MMU)」的完整文本可在网页上免费阅读。要进行交互式练习(内置代码编辑器和全天候 AI 导师)并解锁 Assembly Language & x86 Low-Level Systems Programming 课程的其余内容,请升级到 CoddyKit PRO。 Assembly Language & x86 Low-Level Systems Programming 课程共包含 4 节课。

「分页与内存管理单元(MMU)」这节课中我会学到什么?

理解 x86 MMU 如何通过页表和页目录将虚拟地址转换为物理地址。 你通过在浏览器中直接运行的动手代码来练习 Assembly Language & x86 Low-Level Systems Programming,全天候 AI 导师会在你学习这节课的过程中回答你的问题。

学习 Assembly Language & x86 Low-Level Systems Programming 需要有经验吗?

无需任何先前经验。CoddyKit 上的 Assembly Language & x86 Low-Level Systems Programming 课程适合初学者到高级学习者,你可以从这里开始或从头开始,按照自己的节奏学习。 这是第 1 节课,共 4 节。

「分页与内存管理单元(MMU)」课时需要多长时间?

大多数 CoddyKit 课程大约需要 5–10 分钟。每节课都很精短且互动,所以你能稳步进步,并在网页和应用中从离开的地方继续。

我能在这节 Assembly Language & x86 Low-Level Systems Programming 课中编写并运行代码吗?

能。每节 Assembly Language & x86 Low-Level Systems Programming 课都包含内置代码编辑器,你可以在浏览器中直接编写并运行真实代码,并获得即时 AI 反馈 — 无需本地设置。

此课程中的所有课时

  1. 分页与内存管理单元(MMU)
  2. 保护环与权限
  3. 虚拟机监控程序与虚拟化基础
  4. 分段与全局描述符表(GDT)
← 返回 Assembly Language & x86 Low-Level Systems Programming