-
Notifications
You must be signed in to change notification settings - Fork 5.7k
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
8300197: Freeze/thaw an interpreter frame using a single copy_to_chunk() call #13477
8300197: Freeze/thaw an interpreter frame using a single copy_to_chunk() call #13477
Conversation
👋 Welcome back fbredber! A progress list of the required criteria for merging this PR into |
Webrevs
|
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.
I've tested jdk_loom on ppc64le successfully.
Thanks, Richard.
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.
Thanks for this @fbredber ! |
src/hotspot/cpu/aarch64/continuationFreezeThaw_aarch64.inline.hpp
Outdated
Show resolved
Hide resolved
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.
I'll do another round of testing.
Thanks, Richard.
Tests are clean. |
FYI: I also performed tier1-3 tests on linux-riscv64 unmatched boards, result looks good. |
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 @fbredber!
@fbredber 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 81 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. 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 (@reinrich, @pchilano, @RealFYang) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
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.
Thanks, Richard.
Will you provide any additional feedback @theRealAph and @RealFYang? |
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. Thanks.
Thanks for the review guys. Can any of you give me a helping hand (sponsor) the integration. |
/integrate |
/sponsor Thanks, Richard. |
Going to push as commit a8d16de.
Your commit was automatically rebased without conflicts. |
On certain architectures (like AARCH64) padding may be inserted between the locals and the rest of the stack frame in order to keep the frame pointer 16-byte-aligned.
This padding is currently not freezed, instead freezing of a single interpreter stack frame is done using two separate copy_to_chunk() calls (see recurse_freeze_interpreted_frame). Likewise, thawing is done using two separate copy_from_chunk() calls.
This poses a bit of a problem when trying to relativize stack addresses in interpreter frames (JDK-8289296). Since relative offsets may need to be changed during freezing and thawing.
By both freezing and thawing the padding we remove the need to change any relative offsets in runtime.
Tested tier1-tier8 on supported platforms, found no new issues. PowerPC and RISC-V was sanity tested using Qemu.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/13477/head:pull/13477
$ git checkout pull/13477
Update a local copy of the PR:
$ git checkout pull/13477
$ git pull https://git.openjdk.org/jdk.git pull/13477/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 13477
View PR using the GUI difftool:
$ git pr show -t 13477
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/13477.diff
Webrev
Link to Webrev Comment