-
Notifications
You must be signed in to change notification settings - Fork 6.2k
8273482: Remove "foreground work" concept from WorkGang #5410
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 pliden! A progress list of the required criteria for merging this PR into |
|
/label add hotspot-gc,serviceability |
|
@pliden The |
|
@pliden |
Webrevs
|
tschatzl
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.
Lgtm. Thanks a lot for looking into this.
|
@pliden 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 38 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 |
kimbarrett
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.
|
Patch updated include the removal of a few asserts, as discussed here: http://mail.openjdk.java.net/pipermail/hotspot-gc-dev/2021-September/036807.html |
|
The reason I've added this was, that for the shenandoah GC the heap iteration would run into assertions if not called from the VM thread. Maybe this has changed in the meantime. |
As mentioned in my previous comment. This PR removes those asserts since they were overly strict. |
|
Thanks all for reviewing! /integrate |
|
Going to push as commit c1e39fa.
Your commit was automatically rebased without conflicts. |
JDK-8237354 introduced the concept of "foreground work" in WorkGang, as a special case for use by the HeapDumper. I propose that we remove this code, since this special use case can be solved without the need for the concept of "foreground work" in WorkGang.
As far as I can tell, there's no reason why it must be the VM thread that takes on the task of writing the header, iterating over roots, etc. So, in VM_HeapDumper::work(), instead of checking if the current thread is the VM thread we can just check if the worker_id is non-zero. That way, a single worker thread will take on the task of writing the header, iterating over roots, etc, and all other worker threads will continue to call worker_loop().
Testing:
Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/5410/head:pull/5410$ git checkout pull/5410Update a local copy of the PR:
$ git checkout pull/5410$ git pull https://git.openjdk.java.net/jdk pull/5410/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 5410View PR using the GUI difftool:
$ git pr show -t 5410Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/5410.diff