-
Notifications
You must be signed in to change notification settings - Fork 767
Update non-FLC flatlock exit to use CAS #21877
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
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.
do the timeouts in #21826 no longer happen with this PR?
d9c2917
to
f001376
Compare
5ccf3dc
to
f6ef0b1
Compare
changes ltgm, @fengxue-IS can you squash the commits? |
jenkins test sanity plinux jdk21 |
jenkins test sanity alinux jdk24 |
- Use CompareAndSwap to ensure updates to lockword is not overwritten during exit. - Also ensure vthread blocked on monitor is notified properly. - Create separate jdk24+ monitorexit code path Signed-off-by: Jack Lu <[email protected]>
@babsingh can you please restart the PR builds, I think the squash accidentally removed an extra line of code. |
jenkins test sanity alinux jdk24 |
jenkins test sanity plinux jdk21 |
jenkins compile win jdk24 |
} | ||
} else { | ||
j9objectmonitor_t newLock = 0; | ||
I_32 casSuccess = FALSE; |
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.
The type of casSuccess
should be BOOLEAN
.
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.
Opened #21935 to address it.
Related: eclipse-openj9#21877 Signed-off-by: Babneet Singh <[email protected]>
@fengxue-IS Can you address the following concerns, which were missed?
|
Use CompareAndSwap to ensure updates to lockword is not overwritten during exit.
Also ensure vthread blocked on monitor is notified properly.
Related: #21826