RFR: 8325187: JVMTI GetThreadState says virtual thread is JVMTI_THREAD_STATE_INTERRUPTED when it no longer is [v5]

David Holmes dholmes at openjdk.org
Thu Mar 7 06:47:56 UTC 2024


On Wed, 6 Mar 2024 10:41:21 GMT, Serguei Spitsyn <sspitsyn at openjdk.org> wrote:

>> Thanks, I'm already working on it.
>
> Fixed as suggested by Alan.
> 
>> Also need to think through if Object.wait will need to be changed as part of this.
> 
> Still need to look at this.

Use of `ObjectLocker` here will introduce a new pinning point for Loom. We have been removing as many uses of `ObjectLocker` as we can. I also think this will need to be moved back to Java code when the pinning currently inherent in calling `Object.wait` is addressed.

-------------

PR Review Comment: https://git.openjdk.org/jdk/pull/18093#discussion_r1515622346


More information about the hotspot-runtime-dev mailing list