Skip to content

Conversation

@egahlin
Copy link
Member

@egahlin egahlin commented Mar 14, 2025

Could I have a review of a PR that fixes an incorrect scaling of samples for the ThrottleSetting.

Testing: jdk/jdk/jfr

Thanks
Erik


Progress

  • Change must be properly reviewed (1 review required, with at least 1 Reviewer)
  • Change must not contain extraneous whitespace
  • Commit message must refer to an issue

Issue

  • JDK-8351999: JFR: Incorrect scaling of throttled values (Bug - P3)

Reviewers

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 24045

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

Using diff file

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

Using Webrev

Link to Webrev Comment

@bridgekeeper
Copy link

bridgekeeper bot commented Mar 14, 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.

@openjdk
Copy link

openjdk bot commented Mar 14, 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:

8351999: JFR: Incorrect scaling of throttled values

Reviewed-by: shade

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

  • 65c5282: 8351938: C2: Print compilation bailouts with PrintCompilation compile command
  • e3c29c9: 8351556: Optimize Location.locationFor/isModuleOrientedLocation
  • a7a09f6: 8349632: RISC-V: Add Zfa fminm/fmaxm

Please see this link for an up-to-date comparison between the source branch of this pull request and 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
Copy link

openjdk bot commented Mar 14, 2025

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

  • hotspot-jfr

When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command.

@openjdk openjdk bot added the hotspot-jfr hotspot-jfr-dev@openjdk.org label Mar 14, 2025
@egahlin egahlin marked this pull request as ready for review March 14, 2025 10:47
@openjdk openjdk bot added the rfr Pull request is ready for review label Mar 14, 2025
@mlbridge
Copy link

mlbridge bot commented Mar 14, 2025

Webrevs

if (unit.nanos < SECONDS.nanos) {
long perSecond = SECONDS.nanos / unit.nanos;
samples *= Utils.multiplyOverflow(samples, perSecond, Long.MAX_VALUE);
samples = Utils.multiplyOverflow(samples, perSecond, Long.MAX_VALUE);
Copy link
Member

Choose a reason for hiding this comment

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

Reasoning from the math alone, it looks obvious that samples *= samples is not correct. So that part looks fine.

Thinking about unit.nanos == SECONDS.nanos case. This means the unit is exactly "seconds", so no adjustment is needed?

Copy link
Member Author

Choose a reason for hiding this comment

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

Native expects the value in milliseconds, and the default value is 1000 ms, so it seems fine to me.

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

egahlin commented Mar 17, 2025

/integrate

@openjdk
Copy link

openjdk bot commented Mar 17, 2025

Going to push as commit 0450ba9.
Since your change was applied there have been 16 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 Mar 17, 2025
@openjdk openjdk bot closed this Mar 17, 2025
@openjdk openjdk bot removed ready Pull request is ready to be integrated rfr Pull request is ready for review labels Mar 17, 2025
@openjdk
Copy link

openjdk bot commented Mar 17, 2025

@egahlin Pushed as commit 0450ba9.

💡 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

Labels

hotspot-jfr hotspot-jfr-dev@openjdk.org integrated Pull request has been integrated

Development

Successfully merging this pull request may close these issues.

2 participants