-
Notifications
You must be signed in to change notification settings - Fork 721
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
Handle monitor enter/exit on value based instances in Z #11677
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.
@r30shah could you please review given your expertise in the area?
I'd also like to see a better commit comment than we have currently. We should describe roughly the change being made and why it is being made. |
The PR is currently in a draft state. I'll definitely add detailed description on this change in next commit along with other changes required. |
331d116
to
1da4c7e
Compare
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.
Minor nitpick, changes looks Good to me. Also through chat, @a7ehuo has provided a sequence of instruction generated for the node from the log file and it seems ok.
If the monitor object type is value based class, VM will either issue a warning or throw an exception based on -XX:ValueBasedClassCheck option. If the monitor object type is unkonwn, insert a runtime memory check in monitor enter/exit on the class flag J9_CLASS_DISALLOWS_LOCKING_FLAGS. If the monitor object type is not value based class, proceed as how it is handled today. Related to JEP390 Signed-off-by: Annabelle Huo <Annabelle.Huo@ibm.com>
1da4c7e
to
2bdf5db
Compare
Sure, a sample instructions generated for
|
Jenkins test sanity.functional,extended.system zlinux jdk8,jdk11 |
@fjeremic All PR tests have passed. Thanks! |
If the monitor object type is value based class, VM will either issue a warning or throw an exception based on
-XX:ValueBasedClassCheck
option.If the monitor object type is unkonwn, insert a runtime memory check in monitor enter/exit on the class flag
J9_CLASS_DISALLOWS_LOCKING_FLAGS
.If the monitor object type is not value based class, proceed as how it is handled today.
Related to JEP390
Signed-off-by: Annabelle Huo Annabelle.Huo@ibm.com