eglantine-cirakg/src/core/hle/lock.cpp, branch nx2 Mirror of github.com/cira0100/Eglantine-public nx2, a fork of Djihads80/Eglantine. https://git.cirakg.xyz/eglantine-cirakg/atom?h=nx2 2021-12-18T00:05:51+00:00 core: hle: Remove global HLE lock. 2021-12-18T00:05:51+00:00 bunnei bunneidev@gmail.com 2021-12-18T00:05:51+00:00 urn:sha1:5192e8e092397b2f0af6f3a80adbd7b5272b58d8 - This was added early on as a hack to protect against some concurrency issues. - It's not clear that this serves any purpose anymore, and if it does, individual components should be fixed rather than using a global recursive mutex. Fix build on macOS and linux 2018-01-13T22:38:52+00:00 MerryMage MerryMage@users.noreply.github.com 2018-01-13T22:14:04+00:00 urn:sha1:d616b36e7b46c76fad4f29ddff09d68d0bd5958f Use recursive_mutex instead of mutex to fix #2902 2017-08-29T08:39:55+00:00 danzel danzel@localhost.geek.nz 2017-08-29T08:39:55+00:00 urn:sha1:e16c96d5874d35c6745f32f09d8b3c0a228d0802 Kernel/HLE: Use a mutex to synchronize access to the HLE kernel state between the cpu thread and any other possible threads that might touch the kernel (network thread, etc). 2017-08-22T14:30:55+00:00 Subv subv2112@gmail.com 2017-07-21T04:52:50+00:00 urn:sha1:9cf64ca2cf2148b0a223fd9c1920c73537d6477c This mutex is acquired in SVC::CallSVC, ie, as soon as the guest application enters the HLE kernel, and should be acquired by the aforementioned threads before modifying kernel structures.