-
Notifications
You must be signed in to change notification settings - Fork 6.2k
8373941: Epsilon: Robust counter updates in early VM phases #29061
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
8373941: Epsilon: Robust counter updates in early VM phases #29061
Conversation
|
👋 Welcome back shade! A progress list of the required criteria for merging this PR into |
|
@shipilev 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 24 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 |
Webrevs
|
|
@stefank -- is that what you had in mind as one of the solutions? |
stefank
left a comment
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 good to me.
Kim would probably prefer if you changed the volatile bool _ready to use the new Atomic<bool> class.
Right. There are other cases in Epsilon that would enjoy this conversion. Tell you what, let's do this version (so that is also easily backportable), and then I'll do a cleanup that converts all Epsilon code to |
|
Going to push as commit 47e1935.
Your commit was automatically rebased without conflicts. |
See more details in the bug. This PR makes the counters updated on allocation path more robust. New regression test captures the original failure (intermittently). This would be also backported to JDK 26.
Additional testing:
gc/epsilon, 100xruntime/cds/appcds/TestEpsilonGCWithCDS.java, 100xgc/epsilon/TestInitAllocs.java, 1000xProgress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/29061/head:pull/29061$ git checkout pull/29061Update a local copy of the PR:
$ git checkout pull/29061$ git pull https://git.openjdk.org/jdk.git pull/29061/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 29061View PR using the GUI difftool:
$ git pr show -t 29061Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/29061.diff
Using Webrev
Link to Webrev Comment