-
Notifications
You must be signed in to change notification settings - Fork 6.1k
8273916: Remove 'special' ranking #5563
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
…ing locks are always lower ranked than the safepoint checking locks because they cannot block.
…ing locks are always lower ranked than the safepoint checking locks because they cannot block.
|
👋 Welcome back coleenp! A progress list of the required criteria for merging this PR into |
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.
Sorry Coleen but I'm not understanding the mapping process here. I expected to see all special changed to the same thing, eg. nosafepoint, , and all special-N changed to nosafepoint-N, but you have not done that. ???
David
|
Thanks for looking at this, David. I started to map special(-n) to nosafepoint(-n) but since special is nosafepoint - 9 (?) there were interactions with other nosafepoint locks so they needed rankings relative to other locks. CompiledMethod_lock(nosafepoint-4) -> CodeCache_lock(nosafepoint-3) -> VtableStubs_lock(nosafepoint-2) -> CompiledIC_lock(nosafepoint) CodeSweeper_lock(nosafepoint-5) -> CompiledMethod_lock(nosafepoint-4) ThreadsSMRDelete_lock(nosafepoint-3) -> ConcurrentHashTableResize_lock(nosafepoint-2) The compiler locks have the deepest nestings. |
|
Sorry I don't follow. Lets examine that first example. We currently have: CompiledMethod_lock (special-1) -> If we change special to nosafepoint then we would have: CompiledMethod_lock (nosafepoint-1) -> so I don't see why we would have CodeCache_lock instead be nosafepoint-3 ? If all you have done is change special to nosafepoint then all the existing relative rankings remain for things like leaf and leaf-2. The only adjustment you have to make is for a leaf+2 to instead be expressed as safepoint-8. David |
|
All the lock rankings are negative values from locks they hold. The nosafepoint ranking and ranking below that are safepoint_check_never locks. So nosafepoint is the top of the lock hierarchy for safepoint_check_never locks. That's how we start with CompiledIC_lock at 'nosafepoint' rank. The lock values will not be exactly the same value as they were when they were 'special'. They'll be ordered relative to their ranking in the nosafepoint to nosafepoint-n range. I did skip a value though (nosafepoint-1). |
|
So there is more to this than just removing the "special" ranking - you've also changed some locks that are safepoint_never, that used to have ranks above what is now nosafepoint, so that they instead have ranks below nosafepoint - is that right? As long a all relative rankings of locks that can be taken together is maintained, then that is okay - but it is very hard to see that just by looking at the changes. |
|
I just merged with my previous commit and hopefully this change makes a lot more sense now. |
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 Coleen,
Changes look good to me. Not straightforward to verify by code inspection but seems you also already figured out dependent locks with all the testing.
Thanks,
Patricio
|
Thanks Patricio for the code review! |
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 Coleen,
Thanks again for the offlist discussion. Sorry it took me so long to "get it".
Cheers,
David
|
@coleenp 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 30 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 |
|
Thank you @dholmes-ora for the discussions and review! |
|
Going to push as commit d098751.
Your commit was automatically rebased without conflicts. |
This change removes the special ranking and folds it into nosafepoint. You have to look at commit #3 to see this actual part of the change that doesn't include JDK-8273915.
This passes tier1-6 also.
Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/5563/head:pull/5563$ git checkout pull/5563Update a local copy of the PR:
$ git checkout pull/5563$ git pull https://git.openjdk.java.net/jdk pull/5563/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 5563View PR using the GUI difftool:
$ git pr show -t 5563Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/5563.diff