JDK-8271293 : Monitor class should use ThreadBlockInVMPreprocess
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 18
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2021-07-26
  • Updated: 2021-08-05
  • Resolved: 2021-08-05
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 18
18 masterFixed
Related Reports
Relates :  
JDK-8265753 - Remove manual JavaThread transitions to blocked
Relates :  
JDK-8260376 - Cleanup Thread state transitions
Description
JDK-8265753 added ThreadBlockInVMPreprocess as a more general class of ThreadBlockInVM that can take a call-back to be executed before possibly executing SafepointMechanism::process_if_requested(). 
This class should also be used in the Monitor class instead of using ThreadBlockInVM. This will allow to remove the embedded InFlightMutexRelease object from ThreadBlockInVM and to move the InFlightMutexRelease class definition to mutex.cpp where it belongs.
Comments
Changeset: 62e72adf Author: Patricio Chilano Mateo <pchilanomate@openjdk.org> Date: 2021-08-05 19:16:14 +0000 URL: https://git.openjdk.java.net/jdk/commit/62e72adfa7bcc8e2a70c1346f3051deb2488affc
05-08-2021