On Wed, 26 May 2021 15:18:43 GMT, Patricio Chilano Mateo <pchilanom...@openjdk.org> wrote:
>> I need to run the InFlightMutexRelease constructor before I can run the >> ThreadBlockInVMPreprocess constructor. > > Just for consistency, shouldn't we just use ThreadBlockInVMPreprocess in > mutex.cpp as we are using it in objectMonitor.cpp? You mean revert your change of having the monitor as a parameter to ThreadBlockInVM? And instead just place InFlightMutexRelease in mutex and directly use ThreadBlockInVMPreprocess as OM? I don't mind mind either way, but I feel changing two of three locking implementation is enough in one change-set :) So I can open an RFE if you want? ------------- PR: https://git.openjdk.java.net/jdk/pull/3875