-
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
[JDK19] JVMTI GetVirtualThread #16203
Comments
@JasonFengJ9 @fengxue-IS I have updated the list of tests impacted by JVMTI GetVirtualThread. They will need to be excluded. |
Created adoptium/aqa-tests#4122 to exclude following tests:
|
The following JVMTI extension functions are implemented: - GetVirtualThread: Gets the virtual thread corresponding to a carrier thread. - GetCarrierThread: Gets the carrier thread corresponding to a virtual thread. Fixes: eclipse-openj9#16168 Fixes: eclipse-openj9#16203 Signed-off-by: Babneet Singh <sbabneet@ca.ibm.com>
The following JVMTI extension functions are implemented: - GetVirtualThread: Gets the virtual thread corresponding to a carrier thread. - GetCarrierThread: Gets the carrier thread corresponding to a virtual thread. Related: eclipse-openj9#16168 Related: eclipse-openj9#16203 Signed-off-by: Babneet Singh <sbabneet@ca.ibm.com>
The JVMTI GetVirtualThread extension function is implemented in #16518. For JDK20, no test is disabled due to this issue in https://github.com/adoptium/aqa-tests/blob/master/openjdk/excludes/ProblemList_openjdk20-openj9.txt. Thus, closing this issue. |
JVMTI GetVirtualThread is part of the JVMTI Extension API, which is not covered by the JVMTI documentation. So, it doesn't need to be supported for the current Java 19 milestone.
GetVirtualThread just returns the virtual thread object corresponding to a carrier thread via one of the input parameters. It's the inverse of GetCarrierThread (see #16168).
The following JVMTI serviceability tests will need to be disabled until support for GetVirtualThread is introduced:
Related: #16187
Excluded via adoptium/aqa-tests#4087.
The text was updated successfully, but these errors were encountered: