-
Notifications
You must be signed in to change notification settings - Fork 6.2k
8211238: @Deprecated JFR event #16931
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 mgronlun! A progress list of the required criteria for merging this PR into |
|
/label add hotspot-jfr |
|
@mgronlun |
Webrevs
|
|
|
|
A question about "level". Is the intention that the value can be anything, e.g. some new event next month might use the values "1", "2, "3"? Just asking because ordinarily deprecated vs. terminally deprecated is very specific to the manner in which a program element is deprecated and I assume you don't want this event grabbing the general name for a very specific event setting. |
Yes, the design is generic. An event control/setting to be used also for other events. |
|
Hi @mgronlun - sorry for opening a design discussion in PR :( I wonder - will this report each single one invocation of a deprecated method conforming to the rules (JDK method called from non-JDK code)? Can this, potentially, flood the recording if the deprecated method gets called from a hot loop? |
Hi @jbachorik, it will only report one event per unique call site, during link time. Its not a function of hotness, only unique edge discovery. |
|
/label -build |
|
@magicus |
Excellent! Thanks! |
src/hotspot/share/jfr/recorder/checkpoint/jfrCheckpointManager.cpp
Outdated
Show resolved
Hide resolved
|
@mgronlun 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. ➡️ To integrate this PR with the above commit message to the |
|
Many thanks, @jbachorik and @egahlin, for your reviews - much appreciated! |
|
/integrate |
|
Going to push as commit 49fff01.
Your commit was automatically rebased without conflicts. |
Greetings,
please help review this enhancement to add a JFR event to report runtime invocations of methods that have been declared deprecated in the JDK.
Testing: jdk_jfr, CI 1-6, stress testing
Thanks
Markus
Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/16931/head:pull/16931$ git checkout pull/16931Update a local copy of the PR:
$ git checkout pull/16931$ git pull https://git.openjdk.org/jdk.git pull/16931/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 16931View PR using the GUI difftool:
$ git pr show -t 16931Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/16931.diff
Webrev
Link to Webrev Comment