From 5159f4eee882027928098962cdcd71a0b56bfd38 Mon Sep 17 00:00:00 2001 From: Weiyi Wang Date: Fri, 8 Feb 2019 10:43:06 -0500 Subject: Memory: don't lock hle mutex in memory read/write 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. --- src/core/memory.cpp | 6 ------ 1 file changed, 6 deletions(-) (limited to 'src/core') diff --git a/src/core/memory.cpp b/src/core/memory.cpp index f809567b6..ec279cef8 100644 --- a/src/core/memory.cpp +++ b/src/core/memory.cpp @@ -171,9 +171,6 @@ T Read(const VAddr vaddr) { return value; } - // The memory access might do an MMIO or cached access, so we have to lock the HLE kernel state - std::lock_guard lock(HLE::g_hle_lock); - PageType type = current_page_table->attributes[vaddr >> PAGE_BITS]; switch (type) { case PageType::Unmapped: @@ -204,9 +201,6 @@ void Write(const VAddr vaddr, const T data) { return; } - // The memory access might do an MMIO or cached access, so we have to lock the HLE kernel state - std::lock_guard lock(HLE::g_hle_lock); - PageType type = current_page_table->attributes[vaddr >> PAGE_BITS]; switch (type) { case PageType::Unmapped: -- cgit v1.2.3