Self-Referencing Page Tables for the X86-Architecture
Posted9 days agoActive8 days ago
0l.deResearchstory
informativeneutral
Debate
20/100
FreebsdCPU DesignMemory Locality
Key topics
Freebsd
CPU Design
Memory Locality
Discussion Activity
Light discussionFirst comment
2h
Peak period
5
2-4h
Avg / period
2.5
Key moments
- 01Story posted
Dec 25, 2025 at 3:58 AM EST
9 days ago
Step 01 - 02First comment
Dec 25, 2025 at 6:04 AM EST
2h after posting
Step 02 - 03Peak activity
5 comments in 2-4h
Hottest window of the conversation
Step 03 - 04Latest activity
Dec 26, 2025 at 5:04 AM EST
8 days ago
Step 04
Generating AI Summary...
Analyzing up to 500 comments to identify key contributors and discussion patterns
ID: 46383139Type: storyLast synced: 12/25/2025, 10:05:22 PM
Want the full context?
Jump to the original sources
Read the primary article or dive into the live Hacker News thread when you're ready.
- What if you want to port to an architecture that can’t do them?
- How sure are you that all the bonus bits in the entries line up right?
- What if you want to use huge pages of various sizes?
- What if you want to write-protect some page tables?
- What if you want to access a non-current page table? If you do that you need to write all the relevant logic anyway.
- What if a page table isn’t allocated? You probably don’t want to find out by trying to access it and getting a page fault in kernel mode.
- What if you don’t want user code to be able to trivially guess kernel addresses?