-
Notifications
You must be signed in to change notification settings - Fork 5.7k
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
8317440: Lock rank checking fails when code root set is modified with the Servicelock held after JDK-8315503 #16062
8317440: Lock rank checking fails when code root set is modified with the Servicelock held after JDK-8315503 #16062
Conversation
👋 Welcome back tschatzl! A progress list of the required criteria for merging this PR into |
/label add hotspot-gc |
@tschatzl |
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.
Variant 1 seems ok. Uses of the CHT shouldn't take locks, so having a low lock ranking for CHT lock seems like it'll be fine (I can't find where it takes the ThreadsSMRDelete_lock). If any of this breaks, we can try approach #2 next.
@tschatzl 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 26 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 |
Thread lists synchronization in |
Thanks @coleenp @albertnetymk for your reviews |
Going to push as commit 0cf1a55.
Your commit was automatically rebased without conflicts. |
Going with variant 2. |
So a new lock rank issue has been found? sigh |
Hi all,
please review this change that fixes lock ranking after recent changes to the code root set, now using a CHT.
The issue came up because the lock rank of the CHT lock has been larger than the rank of the Servicethread_lock where it is possible that code roots can be added.
The suggested solution is to fix up the lock rankings to work; actually this PR contains two variants:
The other lock ranking changes to Metaspace_lock and ContinuationRelativize_lock are simply undos of the respective changes in JDK-8315503.
Testing: tier1-8 for variant 2), tier 1-7 for variant 1)
Thanks,
Thomas
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/16062/head:pull/16062
$ git checkout pull/16062
Update a local copy of the PR:
$ git checkout pull/16062
$ git pull https://git.openjdk.org/jdk.git pull/16062/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 16062
View PR using the GUI difftool:
$ git pr show -t 16062
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/16062.diff
Webrev
Link to Webrev Comment