-
Notifications
You must be signed in to change notification settings - Fork 6.1k
8317368: [JVMCI] SIGSEGV in JVMCIEnv::initialize_installed_code on libgraal #17714
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 never! A progress list of the required criteria for merging this PR into |
|
@tkrodriguez 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. |
|
@tkrodriguez this pull request can not be integrated into git checkout tkr-nmethod-keep-alive
git fetch https://git.openjdk.org/jdk.git master
git merge FETCH_HEAD
# resolve conflicts and follow the instructions given by git merge
git commit -m "Merge master"
git push |
|
I don't see an easy way to avoid the extra field in |
src/hotspot/share/jvmci/jvmciEnv.hpp
Outdated
| // Given an instance of HotSpotInstalledCode return the corresponding CodeBlob*. | ||
| CodeBlob* get_code_blob(JVMCIObject code); | ||
|
|
||
| // Given an instance of HotSpotInstalledCode return the corresponding nmethod. |
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.
Can you please improve the comment while here, adding a , after HotSpotInstalledCode.
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.
ok
|
@tkrodriguez 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 13 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 |
|
@tkrodriguez This pull request has been inactive for more than 4 weeks and will be automatically closed if another 4 weeks passes without any activity. To avoid this, simply add a new comment to the pull request. Feel free to ask for assistance if you need help with progressing this pull request towards integration! |
|
Can this be merged soon Tom? |
|
I resync'ed with master and mach5 testing was clean. I'll ping some likely reviewers. |
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.
Seems fine.
May be we should consider specialized jvmciJavaThread subclass to keep all JVMCI fields instead of having them in JavaThread even when Graal is not used.
|
@tkrodriguez did you consider an nmethod's state similar to |
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.
|
You mean to add a level of indirection for the JVMCI specific fields? Some of them would be fine with that but a few really want direct access. We'd have to rework some interpreter assembly and code generation on the Graal side for those fields that accessed directly. I could look into it at some point. |
|
Regarding the comment about the special state, the problem is that the nmethod must be visited by the GC while it's alive and the only way to ensure that for it to be explicitly visited during GC. There's no way to fixup the nmethod after the fact. |
|
Thanks for the reviews. /integrate |
|
Going to push as commit f6f038a.
Your commit was automatically rebased without conflicts. |
|
@tkrodriguez Pushed as commit f6f038a. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
This fixes some lurking issues with JVMCI and nmethod related both BarrierSetNMethod and the garbage collection of nmethods. In particular the stack walking in c2v_iterateFrames visits many frames and needs a KeepStackGCProcessedMark for safety. Additionally, JVMCI interacts with nmethods in complex ways and needs some sort of strong root during these interactions. A new JavaThread field has been added that mirrors the way JVMTI keeps nmethods alive.
Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/17714/head:pull/17714$ git checkout pull/17714Update a local copy of the PR:
$ git checkout pull/17714$ git pull https://git.openjdk.org/jdk.git pull/17714/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 17714View PR using the GUI difftool:
$ git pr show -t 17714Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/17714.diff
Webrev
Link to Webrev Comment