RFR: 8238761: Asynchronous handshakes [v3]
David Holmes
dholmes at openjdk.java.net
Wed Sep 23 04:13:05 UTC 2020
On Mon, 21 Sep 2020 21:59:40 GMT, Coleen Phillimore <coleenp at openjdk.org> wrote:
>> The thread executing this handshake operation, what the current thread is doesn't matter.
>> You can't use current threads resources or be dependent otherwise on it.
>>
>> Exception being locking issues in JVM TI, where we are dependent that requester have locked JVM TI state lock for us,
>> but we are not dependent that the current thread is the owner. So checking that the lock is held by requester doesn't
>> matter for how is the 'driver'.
>
> The "driver" concept is odd. Should it really be caller? Like the thread that called VMHandshake?
In this context "driver" is just the current thread, that called execute.
-------------
PR: https://git.openjdk.java.net/jdk/pull/151
More information about the serviceability-dev
mailing list