Skip to content

8356556: AArch64: No need for acquire fence in safepoint poll in FFM #25829

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

toxaart
Copy link
Contributor

@toxaart toxaart commented Jun 16, 2025

Hi, please consider the following changes:

On AArch64, the acquire bool argument of the safepoint_poll() method is removed, as the load-acquire ldar instruction in the safepoint_poll() implementation is not needed completely. It was used for observing the disarmed value when VMThread was used to disarm the Java threads, but currently JavaThreads disarm themselves.

Tested in tiers 1 - 4.


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-8356556: AArch64: No need for acquire fence in safepoint poll in FFM (Enhancement - P4)

Reviewers

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/25829/head:pull/25829
$ git checkout pull/25829

Update a local copy of the PR:
$ git checkout pull/25829
$ git pull https://git.openjdk.org/jdk.git pull/25829/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 25829

View PR using the GUI difftool:
$ git pr show -t 25829

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/25829.diff

Using Webrev

Link to Webrev Comment

@bridgekeeper
Copy link

bridgekeeper bot commented Jun 16, 2025

👋 Welcome back toxaart! 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 Jun 16, 2025

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

8356556: AArch64: No need for acquire fence in safepoint poll in FFM

Reviewed-by: dholmes, pchilanomate

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 33 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.

As you do not have Committer status in this project an existing Committer must agree to sponsor your change. Possible candidates are the reviewers of this PR (@pchilano, @dholmes-ora) but any other Committer may sponsor as well.

➡️ To flag this PR as ready for integration with the above commit message, type /integrate in a new comment. (Afterwards, your sponsor types /sponsor in a new comment to perform the integration).

@openjdk
Copy link

openjdk bot commented Jun 16, 2025

@toxaart The following label will be automatically applied to this pull request:

  • hotspot

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.

@toxaart toxaart marked this pull request as ready for review June 16, 2025 14:37
@openjdk openjdk bot added the rfr Pull request is ready for review label Jun 16, 2025
@mlbridge
Copy link

mlbridge bot commented Jun 16, 2025

Webrevs

Copy link
Contributor

@pchilano pchilano left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thanks.

@openjdk openjdk bot added the ready Pull request is ready to be integrated label Jun 17, 2025
Copy link
Member

@dholmes-ora dholmes-ora left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Overall looks good, but one nit.

Thanks

@openjdk openjdk bot removed the ready Pull request is ready to be integrated label Jun 17, 2025
Copy link
Member

@dholmes-ora dholmes-ora left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Thanks

@openjdk openjdk bot added the ready Pull request is ready to be integrated label Jun 17, 2025
@toxaart
Copy link
Contributor Author

toxaart commented Jun 17, 2025

/integrate

@openjdk openjdk bot added the sponsor Pull request is ready to be sponsored label Jun 17, 2025
@openjdk
Copy link

openjdk bot commented Jun 17, 2025

@toxaart
Your change (at version 6120a1e) is now ready to be sponsored by a Committer.

@coleenp
Copy link
Contributor

coleenp commented Jun 17, 2025

It also looks good.
/sponsor

@openjdk
Copy link

openjdk bot commented Jun 17, 2025

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

Your commit was automatically rebased without conflicts.

@theRealAph
Copy link
Contributor

/sponsor

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

openjdk bot commented Jun 17, 2025

@coleenp @toxaart Pushed as commit c1deb9e.

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

@openjdk
Copy link

openjdk bot commented Jun 17, 2025

@theRealAph The command sponsor can only be used in open pull requests.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
hotspot [email protected] integrated Pull request has been integrated
Development

Successfully merging this pull request may close these issues.

5 participants