RFR: 8315061: Make LockingMode a product flag

Roman Kennke rkennke at openjdk.org
Wed Aug 30 21:27:09 UTC 2023


On Wed, 30 Aug 2023 20:43:56 GMT, Daniel D. Daugherty <dcubed at openjdk.org> wrote:

> Repeating my answer from the RFE:
> 
> 
> 
> https://bugs.openjdk.org/browse/JDK-8315061?focusedCommentId=14607768&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14607768
> 
> 
> 
> In order to change the default LockingMode value from LM_LEGACY to
> 
> LM_LIGHTWEIGHT, we have to first change LockingMode to a product
> 
> flag in JDK22 and then in the next release we can change the default
> 
> LockingMode value from LM_LEGACY to LM_LIGHTWEIGHT.
> 
> 
> 
> We can't change the default LockingMode value without making LockingMode
> 
> into a product flag because we have to give customers a supported means
> 
> of changing the LockingMode should there be any issues with the new default. 

Hmmm ok. It already has been a product flag, but it has been experimental. Requiring to unlock experimental or diagnostic options for customers to change the flag is not enough to change the default value, then? I was not aware of that...

-------------

PR Comment: https://git.openjdk.org/jdk/pull/15496#issuecomment-1699862894


More information about the hotspot-runtime-dev mailing list