From 7dd85b207f536c2a597c14f41bbe138917d7531a Mon Sep 17 00:00:00 2001 From: Nekotekina Date: Fri, 30 Oct 2020 22:20:20 +0300 Subject: [PATCH] vm: optimize range lock slot allocations Doesn't seem to need a barrier. --- rpcs3/Emu/Memory/vm.cpp | 4 ---- 1 file changed, 4 deletions(-) diff --git a/rpcs3/Emu/Memory/vm.cpp b/rpcs3/Emu/Memory/vm.cpp index 6c281a41e4..023b6d1c57 100644 --- a/rpcs3/Emu/Memory/vm.cpp +++ b/rpcs3/Emu/Memory/vm.cpp @@ -149,8 +149,6 @@ namespace vm fmt::throw_exception("Out of range lock bits"); } - g_mutex.lock_unlock(); - return &g_range_lock_set[std::countr_one(bits)]; } @@ -197,8 +195,6 @@ namespace vm range_lock->release(0); - std::shared_lock lock(g_mutex); - // Use ptr difference to determine location const auto diff = range_lock - g_range_lock_set; g_range_lock_bits &= ~(1ull << diff);