> Now the `JvmtiVTMSTransitionDisabler` mechanism supports disabling VTMS > transitions for all virtual threads only. It should also support disabling > transitions for any specific virtual thread as well. This will improve > scalability of the JVMTI functions operating on target virtual threads as the > functions can be executed concurrently without blocking each other execution > when target virtual threads are different. > New constructor `JvmtiVTMSTransitionDisabler(jthread vthread)` is added which > has jthread parameter of the target virtual thread. > > Testing: > mach5 jobs are TBD (preliminary testing was completed): > - all JVMTI, JDWP, JDI and JDB tests have to be run > - Kitchensink > - tier5
Serguei Spitsyn has updated the pull request incrementally with one additional commit since the last revision: use owned_by_self vs is_locked in JvmtiVTMSTransition_lock asserts ------------- Changes: - all: https://git.openjdk.org/jdk/pull/11690/files - new: https://git.openjdk.org/jdk/pull/11690/files/7783992f..3c73fae3 Webrevs: - full: https://webrevs.openjdk.org/?repo=jdk&pr=11690&range=03 - incr: https://webrevs.openjdk.org/?repo=jdk&pr=11690&range=02-03 Stats: 2 lines in 1 file changed: 0 ins; 0 del; 2 mod Patch: https://git.openjdk.org/jdk/pull/11690.diff Fetch: git fetch https://git.openjdk.org/jdk pull/11690/head:pull/11690 PR: https://git.openjdk.org/jdk/pull/11690