-
Notifications
You must be signed in to change notification settings - Fork 160
8073464: GC workers do not have thread names #184
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 simonis! A progress list of the required criteria for merging this PR into |
This backport pull request has now been updated with issue from the original commit. |
Webrevs
|
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.
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.
The parent pull request that this pull request depends on has now been integrated and the target branch of this pull request has been updated. This means that changes from the dependent pull request can start to show up as belonging to this pull request, which may be confusing for reviewers. To remedy this situation, simply merge the latest changes from the new target branch into this pull request by running commands similar to these in the local repository for your personal fork: git checkout JDK-8073464
git fetch https://git.openjdk.org/jdk8u-dev master
git merge FETCH_HEAD
# if there are conflicts, follow the instructions given by git merge
git commit -m "Merge master"
git push |
@simonis This change now passes all automated pre-integration checks. 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 6 new commits pushed to the
Please see this link for an up-to-date comparison between the source branch of this pull request and the ➡️ To integrate this PR with the above commit message to the |
/integrate |
Going to push as commit df44cbf.
Your commit was automatically rebased without conflicts. |
This is a backport of "JDK-8073464: GC workers do not have thread names" which I request for parity with Oracle JDK 8 where it was downported to 8u351 (see JDK-8285732). This downport depends on "JDK-6885993: Named Thread: introduce print() and print_on(outputStream* st) methods" for which a pull request already exists.
Both of these changes are required to fix the native names of internal threads like for example GC threads. This does not only simplify debugging, but also helps observability tools. Finally, these two changes fix the "sun.management.HotspotInternal" MxBean which returns the "InternalThreadCpuTimes". The "InternalThreadCpuTimes" attribute returns a map with a thread-name to thread-cpu-time mapping but is currently broken in JDK 8 because internal threads without native names (e.g. GC threads) are all mapped to the same entry (i.e. "Unknown").
The patch applies cleanly except for two copyright year mismatches in
concurrentGCThread.cpp
andthread.hpp
. I've attached a diff of this patch compared to the original JDK 9 patch to this PR for your convenience (see 8073464-jdk8-vs-jdk9.txt)Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk8u-dev pull/184/head:pull/184
$ git checkout pull/184
Update a local copy of the PR:
$ git checkout pull/184
$ git pull https://git.openjdk.org/jdk8u-dev pull/184/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 184
View PR using the GUI difftool:
$ git pr show -t 184
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk8u-dev/pull/184.diff