JDK-8184746 : The HeapRegionRemSet::_m lock should use the "access" rank
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: gc
  • Priority: P4
  • Status: Open
  • Resolution: Unresolved
  • Submitted: 2017-07-17
  • Updated: 2021-09-01
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.
Other
tbdUnresolved
Description
In the quest to make G1 heap oop stores not dictate what lock ranks may be used in the VM, or where heap oop stores may be performed, a new "access" rank was created for locks that need to be acquired in order to perform memory accesses. These are 'special' locks that must not check for safepoints and may be acquired in leaf calls and almost any context.

However, the HeapRegionRemSet::_m lock is till "leaf" ranked, and might be called from a heap oop access. Therefore, the heap oop store is not quite free, until this situation is remedied.