-
Notifications
You must be signed in to change notification settings - Fork 6.2k
8356289: Shenandoah: Clean up SATB barrier runtime entry points #26850
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 cslucas! A progress list of the required criteria for merging this PR into |
@JohnTortugo 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 131 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 |
@JohnTortugo 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. |
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. Have we run this change through our internal CI regression pipelines?
Looks reasonable to me. I have the same question as @kdnilsen . |
Same; performance impact would be good to know (i.e. that it's performance neutral or may be even a bit better). |
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.
Internal testing looks good.
I reviewed the tests internally with @earthling-amzn ; He said everything looks good. |
/integrate |
Going to push as commit f28f618.
Your commit was automatically rebased without conflicts. |
@JohnTortugo Pushed as commit f28f618. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
The runtime entry points for the SATB slow-paths currently take a JavaThread* argument. When @rkennke did the entry points for Graal (JDK-8356075), he figured that we do not really need them. The slow-path is only called rarely (whenever the local SATB buffer is full), and getting the current Thread* in the runtime would not be the expensive part.
This PR is a patch to do that clean up. The changes were tested on Linux x64/aarch64 with JTREG tier1-3 using Shenandoah for all tests.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/26850/head:pull/26850
$ git checkout pull/26850
Update a local copy of the PR:
$ git checkout pull/26850
$ git pull https://git.openjdk.org/jdk.git pull/26850/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 26850
View PR using the GUI difftool:
$ git pr show -t 26850
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/26850.diff
Using Webrev
Link to Webrev Comment