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
8274903: Zero: Support AsyncGetCallTrace #5848
8274903: Zero: Support AsyncGetCallTrace #5848
Conversation
|
Webrevs
|
@shipilev 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! |
Anyone has opinions about this patch? :) |
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.
Hi Aleksey,
Thank you for the update. It looks pretty good to me.
I've inlined a couple of minor comments.
Also, I hope, you will update the copyright years.
Thanks,
Serguei
@shipilev This change now passes all automated pre-integration checks. 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 181 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.
|
Thank you, @sspitsyn! Any more reviews, anyone? |
No other reviews? I'd like to integrate this soon. |
Thank you! /integrate |
Going to push as commit 92aa75b.
Your commit was automatically rebased without conflicts. |
This is a Zero infrastructure improvement that makes Zero VM work with AsyncGetCallTrace, and by extension, async-profiler.
Zero is quite odd in stack management. The "real" stack actually contains the C++ Interpreter and the rest of VM code. The Java stack is reported through the usual "frame" mechanism the rest of VM uses to get the mapping from Template Interpreter, stub, and compiled code. So, to support Java-centric AsyncGetCallTrace, we t "only" need Zero to report the proper Java frames from its ZeroStack from the profiling/signal handlers.
Additional testing:
serviceability/AsyncGetCallTrace
now passasync-profiler
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/5848/head:pull/5848
$ git checkout pull/5848
Update a local copy of the PR:
$ git checkout pull/5848
$ git pull https://git.openjdk.java.net/jdk pull/5848/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 5848
View PR using the GUI difftool:
$ git pr show -t 5848
Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/5848.diff