Bureaucrats, ninja, Administrators
67,565
edits
PCSX2 Documentation/So maybe it's about time we explained VTLB: Difference between revisions
PCSX2 Documentation/So maybe it's about time we explained VTLB (view source)
Revision as of 19:59, 5 April 2015
, 5 April 2015no edit summary
m (Ngng moved page So maybe it's about time we explained VTLB to PCSX2 Documentation/So maybe it's about time we explained VTLB without leaving a redirect) |
No edit summary |
||
| Line 1: | Line 1: | ||
{{DocTabs|Section=3}} | |||
''Originally written by Jake Stine'' | ''Originally written by Jake Stine'' | ||
| Line 33: | Line 34: | ||
The benefits of this model are three-fold: efficiency, extensibility, and ease of debugging. If a game doesn't use the Ps2's TLB, then the VTLB will simply use direct memOps (fast!). If a game does happen to use the TLB, then VTLB can remap the memory as needed, allowing that game to emulate correctly also without having to needlessly burden other games with the overhead of virtual memory remapping logic. And to top it all off, handler mappings can be traced and dumped quickly and easily at any stage of emulation. Smile | The benefits of this model are three-fold: efficiency, extensibility, and ease of debugging. If a game doesn't use the Ps2's TLB, then the VTLB will simply use direct memOps (fast!). If a game does happen to use the TLB, then VTLB can remap the memory as needed, allowing that game to emulate correctly also without having to needlessly burden other games with the overhead of virtual memory remapping logic. And to top it all off, handler mappings can be traced and dumped quickly and easily at any stage of emulation. Smile | ||
{{PCSX2 Developers Blog Navbox}} | |||