Skip to content

8352738: Implement JEP 520: JFR Method Timing and Tracing #25306

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

Closed
wants to merge 11 commits into from

Conversation

egahlin
Copy link
Member

@egahlin egahlin commented May 19, 2025

Could I have a review of this enhancement that will add tracing capabilities to JFR? There are opportunities for performance improvements in the implementation, but I would rather add them later and separately.

Testing: tier 1-3, test/jdk/jdk/jfr

Thanks
Erik


Progress

  • Change must be properly reviewed (1 review required, with at least 1 Reviewer)
  • Change requires CSR request JDK-8356994 to be approved
  • Change must not contain extraneous whitespace
  • Commit message must refer to an issue
  • Change requires a JEP request to be targeted

Issues

  • JDK-8352738: Implement JEP 520: JFR Method Timing and Tracing (Enhancement - P2)
  • JDK-8328610: JEP 520: JFR Method Timing & Tracing (JEP)
  • JDK-8356994: Implement JEP 520: JFR Method Timing and Tracing (CSR)

Reviewers

Contributors

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/25306/head:pull/25306
$ git checkout pull/25306

Update a local copy of the PR:
$ git checkout pull/25306
$ git pull https://git.openjdk.org/jdk.git pull/25306/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 25306

View PR using the GUI difftool:
$ git pr show -t 25306

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/25306.diff

Using Webrev

Link to Webrev Comment

@bridgekeeper
Copy link

bridgekeeper bot commented May 19, 2025

👋 Welcome back egahlin! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

@egahlin
Copy link
Member Author

egahlin commented May 19, 2025

/contributor add @mgronlun

@openjdk
Copy link

openjdk bot commented May 19, 2025

@egahlin 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:

8352738: Implement JEP 520: JFR Method Timing and Tracing

Co-authored-by: Markus Grönlund <[email protected]>
Reviewed-by: shade, mgronlun

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 15 new commits pushed to the master branch:

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 master branch, type /integrate in a new comment.

@openjdk openjdk bot added the csr Pull request needs approved CSR before integration label May 19, 2025
@openjdk
Copy link

openjdk bot commented May 19, 2025

@egahlin
Contributor Markus Grönlund <[email protected]> successfully added.

@openjdk
Copy link

openjdk bot commented May 19, 2025

@egahlin The following labels will be automatically applied to this pull request:

  • hotspot
  • serviceability

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.

@egahlin
Copy link
Member Author

egahlin commented May 19, 2025

/label remove serviceability

@egahlin
Copy link
Member Author

egahlin commented May 19, 2025

/label add hotspot-jfr

@openjdk
Copy link

openjdk bot commented May 19, 2025

@egahlin
The serviceability label was successfully removed.

@openjdk
Copy link

openjdk bot commented May 19, 2025

@egahlin
The hotspot-jfr label was successfully added.

Copy link

@mgronlun mgronlun left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great work, Erik!

@egahlin egahlin marked this pull request as ready for review May 19, 2025 15:36
@openjdk openjdk bot added the rfr Pull request is ready for review label May 19, 2025
@mlbridge
Copy link

mlbridge bot commented May 19, 2025

@shipilev
Copy link
Member

May want to say /jep JEP-520 as well :)

Copy link
Member

@shipilev shipilev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Impressive work! I read it a bit superficially, here are comments/questions:

@egahlin
Copy link
Member Author

egahlin commented May 22, 2025

/jep JEP-520

@openjdk
Copy link

openjdk bot commented May 22, 2025

@egahlin
This pull request will not be integrated until the JEP-520 has been targeted.

@openjdk openjdk bot added the jep label May 22, 2025
Copy link
Member

@liach liach left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Mainly looked at bytecode transformation; those look good.

@openjdk
Copy link

openjdk bot commented May 26, 2025

@egahlin this pull request can not be integrated into master due to one or more merge conflicts. To resolve these merge conflicts and update this pull request you can run the following commands in the local repository for your personal fork:

git checkout jep-method-timing-and-tracing
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

@openjdk openjdk bot added merge-conflict Pull request has merge conflict with target branch and removed jep labels May 26, 2025
@openjdk openjdk bot removed the merge-conflict Pull request has merge conflict with target branch label May 26, 2025
@openjdk openjdk bot removed the csr Pull request needs approved CSR before integration label May 28, 2025
Copy link

@mgronlun mgronlun left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good.

@openjdk openjdk bot added the ready Pull request is ready to be integrated label May 28, 2025
@openjdk openjdk bot removed the ready Pull request is ready to be integrated label May 28, 2025
Copy link
Member

@shipilev shipilev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like some of my comments were not fully addressed, these ones that I caught on second read:

@egahlin
Copy link
Member Author

egahlin commented May 28, 2025

Looks like some of my comments were not fully addressed, these ones that I caught on second read:

Sorry about that. I remember fixing synchronized, but maybe it was in the wrong branch.

Copy link
Member

@shipilev shipilev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks OK to me, thanks.

@openjdk openjdk bot added the ready Pull request is ready to be integrated label May 29, 2025
@egahlin
Copy link
Member Author

egahlin commented May 29, 2025

Thanks for the reviews, @liach, @mgronlun, and @shipilev

@egahlin
Copy link
Member Author

egahlin commented May 29, 2025

/integrate

@openjdk
Copy link

openjdk bot commented May 29, 2025

Going to push as commit 07f5b762a09e4fe9f7ba71368593f6dfa0ff8f6e.
Since your change was applied there have been 15 commits pushed to the master branch:

Your commit was automatically rebased without conflicts.

@openjdk openjdk bot added the integrated Pull request has been integrated label May 29, 2025
@openjdk openjdk bot closed this May 29, 2025
@openjdk openjdk bot removed ready Pull request is ready to be integrated rfr Pull request is ready for review labels May 29, 2025
@openjdk
Copy link

openjdk bot commented May 29, 2025

@egahlin Pushed as commit 07f5b76.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

4 participants