-
Notifications
You must be signed in to change notification settings - Fork 6.1k
8335946: DTrace code snippets should be generated when DTrace flags are enabled #20090
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 kuaiwei! A progress list of the required criteria for merging this PR into |
@kuaiwei 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 28 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 (@coleenp, @dholmes-ora) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
/label remove hotspot-compiler I think this should go to hotspot-runtime. |
@TobiHartmann |
@TobiHartmann |
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.
This looks good. Does anyone use DTRACE?
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 reasonable. The dynamic DTrace ability was only on Solaris.
Thanks
Thanks for review. |
/integrate |
/sponsor |
Going to push as commit b363de8.
Your commit was automatically rebased without conflicts. |
@dholmes-ora @kuaiwei Pushed as commit b363de8. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
@dholmes-ora Thanks for your help. |
Some DTrace code snippets are generated no matter dtrace is enabled or not. It looks dtrace flags could be dynamic changed in previous jdk releases. Since they are not changeable, the code snippets can be generated based on flags. The code snippets are:
For example, run this command and check output with x86_64 build:
./java -XX:+UnlockDiagnosticVMOptions -XX:+PrintNativeNMethods -version
Apply this patch, dtrace_method invocation will be emitted only when DTraceMethodProbes is enabled.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/20090/head:pull/20090
$ git checkout pull/20090
Update a local copy of the PR:
$ git checkout pull/20090
$ git pull https://git.openjdk.org/jdk.git pull/20090/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 20090
View PR using the GUI difftool:
$ git pr show -t 20090
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/20090.diff
Webrev
Link to Webrev Comment