Re: RFR: 8247972: incorrect implementation of JVM TI GetObjectMonitorUsage [v5]

2024-02-14 Thread David Holmes
On Wed, 14 Feb 2024 12:16:38 GMT, Serguei Spitsyn wrote: >> src/hotspot/share/runtime/threads.cpp line 1200: >> >>> 1198: if (pending == monitor || >>> 1199: (waiting == monitor && >>> JavaThreadStatus::BLOCKED_ON_MONITOR_ENTER == >>> 1200:

Re: RFR: 8247972: incorrect implementation of JVM TI GetObjectMonitorUsage [v5]

2024-02-14 Thread Serguei Spitsyn
On Wed, 14 Feb 2024 02:18:58 GMT, David Holmes 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 five additional >>

Re: RFR: 8247972: incorrect implementation of JVM TI GetObjectMonitorUsage [v5]

2024-02-13 Thread David Holmes
On Tue, 13 Feb 2024 07:11:18 GMT, Serguei Spitsyn wrote: >> The implementation of the JVM TI `GetObjectMonitorUsage` does not match the >> spec. >> The function returns the following structure: >> >> >> typedef struct { >> jthread owner; >> jint entry_count; >> jint waiter_count;

Re: RFR: 8247972: incorrect implementation of JVM TI GetObjectMonitorUsage [v5]

2024-02-12 Thread Serguei Spitsyn
> The implementation of the JVM TI `GetObjectMonitorUsage` does not match the > spec. > The function returns the following structure: > > > typedef struct { > jthread owner; > jint entry_count; > jint waiter_count; > jthread* waiters; > jint notify_waiter_count; >