RFR: 8304303: implement VirtualThread class notifyJvmti methods as C2 intrinsics [v4]
Serguei Spitsyn
sspitsyn at openjdk.org
Mon Mar 20 07:18:24 UTC 2023
On Sat, 18 Mar 2023 11:24:47 GMT, Alan Bateman <alanb at openjdk.org> wrote:
> The most important case is when there is no JVMTI env. If I read the changes correctly, the overhead for park/continue changes from one volatile-read (notifyJvmtiEvents) to two plain-writes (JavaThread::_is_in_VTMS_transition).
>
> If a JVMTI env has been created then there is no benefit for the moment as there is still a call into the runtime to interact with JvmtiVTMSTransitionDisabler. So I think you are saying that is for follow-on PRs.
@AlanBateman Yes, your conclusion is correct.
-------------
PR: https://git.openjdk.org/jdk/pull/13054
More information about the serviceability-dev
mailing list