michaelkuc6/blog_os
1
0
Fork 0
mirror of https://github.com/phil-opp/blog_os.git synced 2025-12-16 22:37:49 +00:00
Code Issues Projects Releases Wiki Activity

Fix alt text for image

Browse Source
This commit is contained in:
Philipp Oppermann
2018-12-13 18:32:21 +01:00
parent 7fbbaa6d60
commit aa55d2639a
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
blog/content/second-edition/posts/09-paging/index.md
View File

@@ -158,7 +158,7 @@ The physical address of the currently active level 4 page table, which is the ro
The above page table hierarchy maps two pages (in blue). The start addresses of these pages are `0x803FE7F000` and `0x803FE00000`. Let's see what happens when the program tries to read from address `0x803FE7F5CE`. First, we convert the address to binary and determine the page table indices and the page offset for the address: The above page table hierarchy maps two pages (in blue). The start addresses of these pages are `0x803FE7F000` and `0x803FE00000`. Let's see what happens when the program tries to read from address `0x803FE7F5CE`. First, we convert the address to binary and determine the page table indices and the page offset for the address:
![An example 4-level page hierarchy with each page table shown in physical memory](x86_64-page-table-translation-addresses.svg) ![The sign extension bits are all 0, the level 4 index is 1, the level 3 index is 0, the level 2 index is 511, the level 1 index is 127, and the page offset is 0x5ce](x86_64-page-table-translation-addresses.svg)
With these indices, we can now walk the page table hierarchy to determine the mapped frame for the address: With these indices, we can now walk the page table hierarchy to determine the mapped frame for the address: