-
Notifications
You must be signed in to change notification settings - Fork 6.2k
8352918: Shenandoah: Verifier does not deactivate barriers as intended #24264
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
8352918: Shenandoah: Verifier does not deactivate barriers as intended #24264
Conversation
|
👋 Welcome back wkemper! A progress list of the required criteria for merging this PR into |
|
@earthling-amzn 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 25 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 |
|
@earthling-amzn The following labels will be automatically applied to this pull request:
When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing lists. If you would like to change these labels, use the /label pull request command. |
Webrevs
|
shipilev
left a comment
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.
Ouch. Took me a while to understand which field is updated, since fields are named the same in ShenandoahHeap and here. I suggest renaming fields in ShenandoahGCStateResetter to _saved_gc_state and _saved_gc_state_changed.
ysramakrishna
left a comment
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.
🚢
|
/integrate |
|
Going to push as commit 1bd0ce1.
Your commit was automatically rebased without conflicts. |
|
@earthling-amzn Pushed as commit 1bd0ce1. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
When verifying reachable objects, Shenandoah's verifier clears the
_gc_statewith the intention of deactivating barriers. However, the mechanism for this is afriendof the heap and does not toggle the flag to cause threads to use the value set on the verifier's safepoint. The net effect here is that the barriers are not deactivated during verification. Leaving the barriers on while the verifier traverses the heap may have unintended consequences (cards marked, objects evacuated, etc.)Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/24264/head:pull/24264$ git checkout pull/24264Update a local copy of the PR:
$ git checkout pull/24264$ git pull https://git.openjdk.org/jdk.git pull/24264/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 24264View PR using the GUI difftool:
$ git pr show -t 24264Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/24264.diff
Using Webrev
Link to Webrev Comment