Skip to content

Conversation

JohnTortugo
Copy link
Contributor

@JohnTortugo JohnTortugo commented Aug 19, 2025

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

  • Change must be properly reviewed (1 review required, with at least 1 Reviewer)
  • Change must not contain extraneous whitespace
  • Commit message must refer to an issue

Issue

  • JDK-8356289: Shenandoah: Clean up SATB barrier runtime entry points (Enhancement - P4)

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

@bridgekeeper
Copy link

bridgekeeper bot commented Aug 19, 2025

👋 Welcome back cslucas! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

@openjdk
Copy link

openjdk bot commented Aug 19, 2025

@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:

8356289: Shenandoah: Clean up SATB barrier runtime entry points

Reviewed-by: kdnilsen, ysr, wkemper

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 master branch:

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 master branch, type /integrate in a new comment.

@openjdk openjdk bot changed the title JDK-8356289: Shenandoah: Clean up SATB barrier runtime entry points 8356289: Shenandoah: Clean up SATB barrier runtime entry points Aug 19, 2025
@openjdk
Copy link

openjdk bot commented Aug 19, 2025

@JohnTortugo The following labels will be automatically applied to this pull request:

  • hotspot
  • shenandoah

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.

@mlbridge
Copy link

mlbridge bot commented Aug 19, 2025

Webrevs

Copy link
Contributor

@kdnilsen kdnilsen left a 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?

@earthling-amzn
Copy link
Contributor

Looks reasonable to me. I have the same question as @kdnilsen .

@ysramakrishna
Copy link
Member

Same; performance impact would be good to know (i.e. that it's performance neutral or may be even a bit better).

@openjdk openjdk bot added the ready Pull request is ready to be integrated label Aug 21, 2025
Copy link
Contributor

@earthling-amzn earthling-amzn left a 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.

@JohnTortugo
Copy link
Contributor Author

I reviewed the tests internally with @earthling-amzn ; He said everything looks good.

@JohnTortugo
Copy link
Contributor Author

/integrate

@openjdk
Copy link

openjdk bot commented Aug 22, 2025

Going to push as commit f28f618.
Since your change was applied there have been 131 commits pushed to the master branch:

Your commit was automatically rebased without conflicts.

@openjdk openjdk bot added the integrated Pull request has been integrated label Aug 22, 2025
@openjdk openjdk bot closed this Aug 22, 2025
@openjdk openjdk bot removed ready Pull request is ready to be integrated rfr Pull request is ready for review labels Aug 22, 2025
@openjdk
Copy link

openjdk bot commented Aug 22, 2025

@JohnTortugo Pushed as commit f28f618.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

4 participants