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
8303013: Always do remembered set verification during G1 Full GC #12781
8303013: Always do remembered set verification during G1 Full GC #12781
Conversation
👋 Welcome back tschatzl! A progress list of the required criteria for merging this PR into |
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.
VerifyRememberedSets
should be removed as well, in another PR.
@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 18 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 |
And potentially |
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.
Thanks for your reviews
/integrate
Going to push as commit 4c5d9cf.
Your commit was automatically rebased without conflicts. |
Hi all,
can I have reviews for this change that removes the
G1VerifyRSetsDuringFullGC
flag because it seems superfluous: if we are doing verification, we likely want to have all subsystems checked; now there is the argument that remset verification is somewhat expensive, and hence the reason for this flag. However I believe that the existing flags to control verification execution (VerifyGCType
) are much better than this particular flag.There is a
VerifyRememberedSets
flag available that is currently only used in Parallel GC that might be used here to control all remembered set verification; however I believe that if we do verification, we typically want all of it (and it can be toned down byVerifyGCType
and friends). If you think it is useful, I can enable G1 to honourVerifyRememberedSets
too (with a default oftrue
and obviously only active if other verification is enabled).Testing: tier1-3
Thanks,
Thomas
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk pull/12781/head:pull/12781
$ git checkout pull/12781
Update a local copy of the PR:
$ git checkout pull/12781
$ git pull https://git.openjdk.org/jdk pull/12781/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 12781
View PR using the GUI difftool:
$ git pr show -t 12781
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/12781.diff