8297173: usageTicks and totalTicks should be volatile to ensure that different threads get the latest ticks

[tianshuang]

As the title says, add the volatile modifier.

---

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-8297173: usageTicks and totalTicks should be volatile to ensure that different threads get the latest ticks

Reviewers

• Severin Gehwolf (@jerboaa - Reviewer) ⚠️ Review applies to dd459966
• Alan Bateman (@AlanBateman - Reviewer)

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 11199

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

Using diff file

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

[bridgekeeper]

👋 Welcome back tianshuang! 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]

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

• jmx
• 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.

[mlbridge]

Webrevs

• 01: Full - Incremental (f6b19bb0)
• 00: Full (dd459966)

[jerboaa]

Seems OK to me.

[openjdk]

⚠️ @tianshuang the full name on your profile does not match the author name in this pull requests' HEAD commit. If this pull request gets integrated then the author name from this pull requests' HEAD commit will be used for the resulting commit. If you wish to push a new commit with a different author name, then please run the following commands in a local repository of your personal fork:

$ git checkout JDK-8297173
$ git commit --author='Preferred Full Name <you@example.com>' --allow-empty -m 'Update full name'
$ git push

[openjdk]

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

8297173: usageTicks and totalTicks should be volatile to ensure that different threads get the latest ticks

Reviewed-by: sgehwolf, alanb

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

• 2b6dbc7: 8293856: AArch64: Remove clear_inst_mark from aarch64_enc_java_dynamic_call
• 2f063b8: 8296846: Minor cleanup of some dead code in Flow.java
• ab6b7ef: 8296901: Do not create unsigned certificate and CRL
• 7b3984c: 8296463: Memory leak in JVM_StartThread with the integration of Virtual threads
• 373e52c: 8296785: Use realloc for CHeap-allocated BitMaps
• a53be20: 8282404: DrawStringWithInfiniteXform.java failed with "RuntimeException: drawString with InfiniteXform transform takes long time"
• 66228f7: 8297074: Use enhanced-for cycle instead of Enumeration in javax.crypto
• 819af69: 8249693: java/nio/channels/FileChannel/FileExtensionAndMap.java uses @ignore w/o bug id
• 9c432a0: 8297165: Update Pandoc to version 2.19.2 for Oracle builds
• 8b140e2: 8297152: Add a @sealedGraph tag to ZoneId
• ... and 20 more: https://git.openjdk.org/jdk/compare/cd9c688bfce36e4b2d37dd68dd8031f197b9eddc...master

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 (@jerboaa, @AlanBateman) but any other Committer may sponsor as well.

➡️ To flag this PR as ready for integration with the above commit message, type /integrate in a new comment. (Afterwards, your sponsor types /sponsor in a new comment to perform the integration).

[jerboaa]

Please enable testing for your fork.

[tianshuang]

/integrate

[openjdk]

@tianshuang
Your change (at version dd45996) is now ready to be sponsored by a Committer.

[jerboaa]

@tianshuang If you /integrate again, I can sponsor for you if you like.

[tianshuang]

/integrate

[openjdk]

@tianshuang
Your change (at version f6b19bb) is now ready to be sponsored by a Committer.

[jerboaa]

/sponsor

[openjdk]

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

• 2b6dbc7: 8293856: AArch64: Remove clear_inst_mark from aarch64_enc_java_dynamic_call
• 2f063b8: 8296846: Minor cleanup of some dead code in Flow.java
• ab6b7ef: 8296901: Do not create unsigned certificate and CRL
• 7b3984c: 8296463: Memory leak in JVM_StartThread with the integration of Virtual threads
• 373e52c: 8296785: Use realloc for CHeap-allocated BitMaps
• a53be20: 8282404: DrawStringWithInfiniteXform.java failed with "RuntimeException: drawString with InfiniteXform transform takes long time"
• 66228f7: 8297074: Use enhanced-for cycle instead of Enumeration in javax.crypto
• 819af69: 8249693: java/nio/channels/FileChannel/FileExtensionAndMap.java uses @ignore w/o bug id
• 9c432a0: 8297165: Update Pandoc to version 2.19.2 for Oracle builds
• 8b140e2: 8297152: Add a @sealedGraph tag to ZoneId
• ... and 20 more: https://git.openjdk.org/jdk/compare/cd9c688bfce36e4b2d37dd68dd8031f197b9eddc...master

Your commit was automatically rebased without conflicts.

[openjdk]

@jerboaa @tianshuang Pushed as commit dd18d76.

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