Babneet Singh

Launched grinders to see if this issue is a blocker for the 0.42 release: - 250x on `win2019x64-openj9-4`: https://openj9-jenkins.osuosl.org/job/Grinder/3061 - 50x on 5 different machines (250x in total): https://openj9-jenkins.osuosl.org/job/Grinder/3062 No...

@dmitripivkine For the I-slot, DDR doesn't find a root for me as well. All the DDR cmds to find the root throw the below exception because they expect an object...

DDR finds the root for the virtual thread address, but it also detects corruption on my end. With `rootpathverbose`, I see the below exception, which reports `Operand stack underflow in...

> I guess this is manifestation of optimization can be disabled by -Xjit:enableAggressiveLiveness In our JDK21+ builds, we run the test with `-Xjit:enableAggressiveLiveness`: [Collectable.java#L27](https://github.com/ibmruntimes/openj9-openjdk-jdk21/blob/dbe6beb1fd6ca96a75fd7046be1ed1fcfb69caa5/test/jdk/java/lang/Thread/virtual/Collectable.java#L27). I have verified that `-Xjit:enableAggressiveLiveness` is...

@thallium This is becoming a large PR (1000+ lines). Please create a separate PR for each JVMTI extension function for ease of reviewing and reducing the risk of failures. When...

PR title shouldn't have a full-stop; I have removed it. The PR description and commit message needs more details: - which JVMTI extension functions are updated? - what do the...

@llxia Requesting your review for the test changes.

There are typos in the commit messages. Correction version: ``` In each of the tests, a virtual thread runs methodToCompile() for a relatively large number of iterations to JIT compile...

@llxia There are two variants of existing tests in `jvmtitests/playlist.xml`: `^arch.390` and `arch.390`. Do we need to do the same for the new test?

> The new test cmdLineTester_jvmtitests_Java21andUp only uses jvmtitests_Java21andUp.xml that you added. Do we want it to run on arch.390? It should be run everywhere. But, existing tests have two targets:...