On Wed, 24 Apr 2024 16:04:30 GMT, Serguei Spitsyn wrote:
> This is a fix of the following JVMTI scalability issue. A closed benchmark
> with millions of virtual threads shows 3X-4X overhead when a JVMTI agent has
> been loaded. For instance, this is observable when an app is executed under
>
This is a fix of the following JVMTI scalability issue. A closed benchmark with
millions of virtual threads shows 4X overhead when a JVMTI agent has been
loaded. For instance, this is observable when an app is executed under control
of the Oracle Studio `collect` utility.
The benchmark takes a
On Wed, 17 Apr 2024 00:29:52 GMT, Serguei Spitsyn wrote:
> This is a simple fix of three similar asserts.
> The `_target_jt->jvmti_vthread()` has to be used instead of
> `_target_jt->vthread()`.
> The `_target_jt->vthread()` can be outdated in some specific contexts as
> shown in the `hs_err`
On Tue, 23 Apr 2024 17:22:41 GMT, Guoxiong Li wrote:
>> Hi all,
>>
>> This patch removes the class `TenuredSpace` and adjusts its usages. After
>> removing `TenuredSpace`, the file `space.inline.hpp` is empty, so I remove
>> this file and change the included header file to `space.hpp`.
>>
>>
On Mon, 22 Apr 2024 16:24:06 GMT, Guoxiong Li wrote:
> Hi all,
>
> This patch removes the class `TenuredSpace` and adjusts its usages. After
> removing `TenuredSpace`, the file `space.inline.hpp` is empty, so I remove
> this file and change the included header file to `space.hpp`.
>
> The
I would find this tool particularly useful. I came across various
`hs_err_pid` files, while one can read them this can speed analyzing up
significantly.
Even for simple cases, like a bug in the FFM API usage (it's still possible
to dereference a bad address).
Looking forward to this plugin !
On Wed, 24 Apr 2024 05:44:42 GMT, Chris Plummer wrote:
>> Serguei Spitsyn has updated the pull request with a new target base due to a
>> merge or a rebase. The incremental webrev excludes the unrelated changes
>> brought in by the merge/rebase. The pull request contains four additional
>>
> This is a simple fix of three similar asserts.
> The `_target_jt->jvmti_vthread()` has to be used instead of
> `_target_jt->vthread()`.
> The `_target_jt->vthread()` can be outdated in some specific contexts as
> shown in the `hs_err` stack trace.
>
> I've seen similar issue and already
On Tue, 23 Apr 2024 13:56:32 GMT, Julian Waters wrote:
> WIP
>
> This changeset contains hsdis for Windows/gcc Port. It supports both the
> binutils and capstone backends, though the LLVM backend is left out due to
> compatibility issues encountered during the build. Currently, which gcc
>
On Mon, 15 Apr 2024 06:47:24 GMT, Serguei Spitsyn wrote:
> This is the test issue. The `WaitingPT3` thread posted the `MonitorWait`
> event but has not released the `lockCheck` monitor yet. It has been fixed to
> wait for each `WaitingTask` thread to really reach the `WAITING` state. The
>
On Wed, 24 Apr 2024 00:01:45 GMT, Serguei Spitsyn wrote:
>> This is the test issue. The `WaitingPT3` thread posted the `MonitorWait`
>> event but has not released the `lockCheck` monitor yet. It has been fixed to
>> wait for each `WaitingTask` thread to really reach the `WAITING` state. The
On Tue, 23 Apr 2024 17:22:41 GMT, Guoxiong Li wrote:
>> Hi all,
>>
>> This patch removes the class `TenuredSpace` and adjusts its usages. After
>> removing `TenuredSpace`, the file `space.inline.hpp` is empty, so I remove
>> this file and change the included header file to `space.hpp`.
>>
>>
On Tue, 23 Apr 2024 15:11:10 GMT, Andrew Haley wrote:
>> What about granting `WXWrite` only if the current thread is in
>> `_thread_in_vm`?
>> That would be more restrictive and roughly equivalent how it currently
>> works. Likely there are some places then that should be granted `WXWrite`
>>
13 matches
Mail list logo
