New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
8315880: change LockingMode default from LM_LEGACY to LM_LIGHTWEIGHT #15797
Conversation
/label add hotspot-runtime |
👋 Welcome back dcubed! A progress list of the required criteria for merging this PR into |
@dcubed-ojdk |
@dcubed-ojdk |
@dcubed-ojdk |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. Thanks.
@dcubed-ojdk This change now passes all automated pre-integration checks. ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details. After integration, the commit message for the final commit will be:
You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed. At the time when this comment was updated there had been 73 new commits pushed to the
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details. ➡️ To integrate this PR with the above commit message to the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me, thank you!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. Thank you!
@dholmes-ora, @rkennke, and @stefank - Thanks for the reviews! |
/integrate |
Going to push as commit 455cfae.
Your commit was automatically rebased without conflicts. |
@dcubed-ojdk Pushed as commit 455cfae. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
BTW: would that mess with JVMCI/Graal? AFAIK, Graal does not implement support for lightweight locking, yet. Should we disable LW-locking when running with JVMCI? |
Good question. |
I think this may have broken JDK-8288293 😅 Is there any compiler specific implementation involved with the new lightweight locking? Just a quick question, I can figure out the rest on my own |
Not that I am aware of. AFAIK, it works fine with various versions of GCC on Linux, Xcode on MacOS and VS on Windows. |
That would be unexpected breakage indeed... |
Haha, indeed. Since this was just a default flag change, it's likely the entire thing was broken on my end to begin with, just that it never manifested since I never used the lightweight mode
Not with gcc on Windows, unfortunately. Looks like I have some work cut out for me. Thanks for the replies |
Change the default of LockingMode to LM_LIGHTWEIGHT from LM_LEGACY.
This fix has been tested with 3 Mach5 Tier[1-8] runs and a 4th is in process.
Progress
Issues
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/15797/head:pull/15797
$ git checkout pull/15797
Update a local copy of the PR:
$ git checkout pull/15797
$ git pull https://git.openjdk.org/jdk.git pull/15797/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 15797
View PR using the GUI difftool:
$ git pr show -t 15797
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/15797.diff
Webrev
Link to Webrev Comment