Skip to content
Snippets Groups Projects
  • Weiyi Wang's avatar
    Memory: don't lock hle mutex in memory read/write · 5159f4ee
    Weiyi Wang authored
    The comment already invalidates itself: neither MMIO nor rasterizer cache belongsHLE kernel state. This mutex has a too large scope if MMIO or cache is included, which is prone to dead lock when multiple thread acquires these resource at the same time. If necessary, each MMIO component or rasterizer should have their own lock.
    5159f4ee