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
8271293: Monitor class should use ThreadBlockInVMPreprocess #4978
Conversation
|
/label add hotspot-runtime |
@pchilano |
/label remove hotspot |
@pchilano The label
|
@pchilano |
/label remove serviceability |
@pchilano |
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.
Hi Patricio,
The code cleanup/reorg looks good to me.
Thanks,
David
@pchilano 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 65 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.
|
Thanks for the review David! Patricio |
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.
Thumbs up.
I like the cleanup and moving InFlightMutexRelease to be
more encapsulated (in mutex.cpp). Also, thanks for flipping
the default state for allow_suspend to false.
Thanks for the review Dan! Patricio |
/integrate |
Going to push as commit 62e72ad.
Your commit was automatically rebased without conflicts. |
Hi,
Please review the following small patch which changes the Monitor class to use the more appropriate ThreadBlockInVMPreprocess transition wrapper instead of ThreadBlockInVM. This allows to remove the embedded InFlightMutexRelease object from ThreadBlockInVM and to move it, along with the definition of the InFlightMutexRelease class, to mutex.cpp where they belong.
I also changed the default value of allow_suspend to false, even though more users set it to true, to make it consistent with the fact that ThreadBlockInVM doesn't process suspend requests. This avoids having to think twice when looking at a ThreadBlockInVM* object as to whether it processes suspend requests or not. Suspend requests are never processed unless explicitly allowed.
I also changed ThreadBlockInVM to be a typedef to avoid declaring a wrapper class of ThreadBlockInVMPreprocess.
Testing in mach5 tiers 1-3.
Thanks,
Patricio
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/4978/head:pull/4978
$ git checkout pull/4978
Update a local copy of the PR:
$ git checkout pull/4978
$ git pull https://git.openjdk.java.net/jdk pull/4978/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 4978
View PR using the GUI difftool:
$ git pr show -t 4978
Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/4978.diff