JDK-8273915 : Create 'nosafepoint' rank
  • Type: Sub-task
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 18
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2021-09-16
  • Updated: 2021-09-24
  • Resolved: 2021-09-21
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 b16Fixed
Related Reports
Relates :  
JDK-8274245 - sun/tools/jmap/BasicJMapTest.java Mutex rank failures
Description
Separate out the locks that check for safepoint and those that do not, giving the locks that do not check for safepoint a lower ranking.

If a thread has a no-safepoint checking lock held, it cannot go to a safepoint.  There's a NoSafepointVerifier installed when we take out these locks.  Because of this all non-safepoint checking locks are ranked below safepoint checking locks.

This change divides the 'leaf' ranked mutex into nosafepoint and below and leaf and below, adding the 'nosafepoint' rank.  I'm not crazy about this name.
Comments
Changeset: 111d5e1a Author: Coleen Phillimore <coleenp@openjdk.org> Date: 2021-09-21 11:37:49 +0000 URL: https://git.openjdk.java.net/jdk/commit/111d5e1a9324cb5e8d98627f6329d17fcbc9c13d
21-09-2021