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 18:13, 19 July 2015
, 19 July 2015no edit summary
No edit summary |
No edit summary |
||
| Line 33: | Line 33: | ||
Ps2_Virtual_Address -> VTLB_Lookup -> Handler -> Ps2_Physical_Address | Ps2_Virtual_Address -> VTLB_Lookup -> Handler -> Ps2_Physical_Address | ||
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. | 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. :) | ||
{{PCSX2 Documentation Navbox}} | {{PCSX2 Documentation Navbox}} | ||