-
Type:
Enhancement
-
Resolution: Fixed
-
Priority:
P4
-
Affects Version/s: None
-
Component/s: hotspot
-
b09
-
generic
-
generic
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8242944 | 11.0.8-oracle | Harold Seigel | P4 | Resolved | Fixed | b04 |
| JDK-8236433 | 11.0.7 | Kim Barrett | P4 | Resolved | Fixed | b01 |
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.
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.
- backported by
-
JDK-8236433 Allow NamedThreads to use GlobalCounter critical sections
-
- Resolved
-
-
JDK-8242944 Allow NamedThreads to use GlobalCounter critical sections
-
- Resolved
-
- causes
-
JDK-8369250 Assess and remedy any unsafe usage of the Semaphore used by NonJavaThread::List
-
- Resolved
-
- relates to
-
JDK-8210511 TestSingleWriterSynchronizer can deadlock
-
- Resolved
-
-
JDK-8209976 Improve iteration over non-JavaThreads
-
- Resolved
-