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

Serguei Spitsyn sspitsyn at openjdk.org
Sat Mar 16 22:33:59 UTC 2024


On Fri, 15 Mar 2024 10:05:06 GMT, David Holmes <dholmes at openjdk.org> wrote:

>> I've restored the `InterruptedException` catch in the `Object.wait`.
>> However, the fix in `JavaThread::is_interrupted()` also impacts the variations of `sleep_nanos()`.
>
> So the current changes do not limit this to just `RawMonitorWait`. I was expecting to only see additional code in `RawMonitorWait` that emulates what the Java code does to get the virtual and carrier thread interrupt states in sync, using the interruptLock.

Okay, I can do this separation.
One minor concern is the `JavaThread::sleep_nanos(jlong nanos)` ?
It is used by the `JavaThread::sleep(jlong millis)` which in tern is not used much.

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

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


More information about the serviceability-dev mailing list