JDK-8331714 : Make OopMapCache installation lock-free
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 11,17,21,22,23
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2024-05-06
  • Updated: 2024-05-09
  • Resolved: 2024-05-07
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 23
23 b22Fixed
Related Reports
Blocks :  
JDK-8331572 - Allow using OopMapCache during concurrent GC phases
Blocks :  
JDK-8331771 - ZGC: Remove OopMapCacheAlloc_lock ordering workaround
Description
Trying to solve JDK-8331572 runs into all sorts of lock ranking issues with `OopMapCacheAlloc_lock`. I think it would be a bit saner to rewrite the double-checked locking installation to atomic lock-free.
Comments
Changeset: a2584a83 Author: Aleksey Shipilev <shade@openjdk.org> Date: 2024-05-07 08:30:26 +0000 URL: https://git.openjdk.org/jdk/commit/a2584a8341b2dc9c102abd373a890b2108d3f57e
07-05-2024
A pull request was submitted for review. URL: https://git.openjdk.org/jdk/pull/19100 Date: 2024-05-06 10:02:40 +0000
06-05-2024