-
Notifications
You must be signed in to change notification settings - Fork 5.8k
8303749: Serial: Use more strict card table API #12902
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
Conversation
👋 Welcome back ayang! A progress list of the required criteria for merging this PR into |
@albertnetymk The following label 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 list. If you would like to change these labels, use the /label pull request command. |
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.
Lgtm.
} | ||
invalidate(used_mr); | ||
dirty_MemRegion(used_mr); |
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.
Now that invalidate()
isn't called any more, it might be useful to rename the method to dirty_or_clear()
or something. In general I think that "dirty" is more specific and clear than "invalidate", but the "invalidate" term probably stems from wanting to be generic (not only here).
So feel free to ignore this suggestions.
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.
clear_into_younger
and invalidate_or_clear/dirty_or_clear
are not very descriptive. I will refactor them in another PR.
@albertnetymk 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 138 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 |
Thanks for the review. /integrate |
Going to push as commit b5108b4.
Your commit was automatically rebased without conflicts. |
@albertnetymk Pushed as commit b5108b4. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Simple refactoring to skip an unnecessary guard check.
Test: tier1-3
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk pull/12902/head:pull/12902
$ git checkout pull/12902
Update a local copy of the PR:
$ git checkout pull/12902
$ git pull https://git.openjdk.org/jdk pull/12902/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 12902
View PR using the GUI difftool:
$ git pr show -t 12902
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/12902.diff