On Fri, 17 Mar 2023 10:31:46 GMT, Serguei Spitsyn wrote:
>> This is needed for future performance/scalability improvements in JVMTI
>> support of virtual threads.
>> The update includes the following:
>>
>> 1. Refactored the `VirtualThread` native methods:
>> `notifyJvmtiMountBegin`
On Sat, 18 Mar 2023 11:24:47 GMT, Alan Bateman 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).
>
>
On Fri, 17 Mar 2023 10:31:46 GMT, Serguei Spitsyn wrote:
>> This is needed for future performance/scalability improvements in JVMTI
>> support of virtual threads.
>> The update includes the following:
>>
>> 1. Refactored the `VirtualThread` native methods:
>> `notifyJvmtiMountBegin`
On Fri, 17 Mar 2023 10:31:46 GMT, Serguei Spitsyn wrote:
>> This is needed for future performance/scalability improvements in JVMTI
>> support of virtual threads.
>> The update includes the following:
>>
>> 1. Refactored the `VirtualThread` native methods:
>> `notifyJvmtiMountBegin`
On Fri, 17 Mar 2023 17:33:46 GMT, Vladimir Ivanov wrote:
> Overall, compiler changes look good.
> Any performance numbers to justify the intrinsification?
Thank you for review and your guidance and help with C2 intrinsification!
My goal was to move the notifyJvmtiEvents checks from Java to VM
On Fri, 17 Mar 2023 10:31:46 GMT, Serguei Spitsyn wrote:
>> This is needed for performance improvements in support of virtual threads.
>> The update includes the following:
>>
>> 1. Refactored the `VirtualThread` native methods:
>> `notifyJvmtiMountBegin` and `notifyJvmtiMountEnd`
> This is needed for performance improvements in support of virtual threads.
> The update includes the following:
>
> 1. Refactored the `VirtualThread` native methods:
> `notifyJvmtiMountBegin` and `notifyJvmtiMountEnd` =>
> `notifyJvmtiMount`
> `notifyJvmtiUnmountBegin` and
