-
Notifications
You must be signed in to change notification settings - Fork 208
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
8325587: Shenandoah: ShenandoahLock should allow blocking in VM #2797
8325587: Shenandoah: ShenandoahLock should allow blocking in VM #2797
Conversation
👋 Welcome back xpeng! A progress list of the required criteria for merging this PR into |
@pengxiaolong 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 44 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. 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 (@phohensee, @shipilev) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
This backport pull request has now been updated with issue from the original commit. |
Webrevs
|
Outline the backport series you're proposing? |
Thanks Paul, I have provided the list of bugs I'm going to backport. |
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.
Thank you. 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 fine, with minor nit.
/approval request Backport of 8325587: Shenandoah: ShenandoahLock should allow blocking in VM, not a clean backport, fixed the conflicts and code style issues, ran hotspot_gc_shenandoah test suite and all tests with -XX:+UseShenandoahGC; overall risk should be low. |
@pengxiaolong |
I agree it is a good time to bring all 4 backports into JDK 17u. |
Thanks all for the reviews! /integrate |
@pengxiaolong |
/sponsor |
Going to push as commit dc69e05.
Your commit was automatically rebased without conflicts. |
@shipilev @pengxiaolong Pushed as commit dc69e05. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Hi,
This PR is a Backport of JDK-8325587: Shenandoah: ShenandoahLock should allow blocking in VM, the original commit was authored by Aleksey Shipilev on 21 Feb 2024 and was reviewed by Robbin Ehn and Roman Kennke, and already backported to jdk21.
It is not a clean backport for JDK17 due to code style change(NULL -> nullptr) and thread header file and API changes.
This is the first backport of a series of improvements for ShenandoahLock to improve contention issue which we I have seem in our customer's production load running with JDK17, here are the series of improvements I'm going to backport to JDK17:
Best,
Xiaolong.
Additional tests:
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk17u-dev.git pull/2797/head:pull/2797
$ git checkout pull/2797
Update a local copy of the PR:
$ git checkout pull/2797
$ git pull https://git.openjdk.org/jdk17u-dev.git pull/2797/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 2797
View PR using the GUI difftool:
$ git pr show -t 2797
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk17u-dev/pull/2797.diff
Webrev
Link to Webrev Comment