JDK-8209850 : Allow NamedThreads to use GlobalCounter critical sections
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: runtime
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2018-08-22
  • Updated: 2020-04-16
  • Resolved: 2018-08-23
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 11 JDK 12
11.0.7Fixed 12 b09Fixed
Related Reports
Relates :  
JDK-8210511 - TestSingleWriterSynchronizer can deadlock
Relates :  
JDK-8209976 - Improve iteration over non-JavaThreads
Description
GlobalCounter critical sections are restricted to JavaThreads and the VMThread, because those are the kinds of threads for which we have a visitation protocol. There are a number of use-cases for critical sections in various GC threads, all of which are blocked by this limitation of GlobalCounter.

To solve this, we need a way for GlobalCounter to visit (iterate over) all NamedThreads. And there are other use-cases for visiting all NamedThreads.
Comments
Isolated RFR for JDK11u backport https://mail.openjdk.java.net/pipermail/jdk-updates-dev/2019-December/002233.html
12-12-2019
Fix request This fix is required by https://bugs.openjdk.java.net/browse/JDK-8225797 backport to JDK 11u. The fix applies with minimal changes - the change is being reviewed in https://mail.openjdk.java.net/pipermail/jdk-updates-dev/2019-November/002115.html Tests from jdk_tier1, jdk_tier2 and jdk_core are all passing.
16-11-2019