On Wed, 1 Jul 2026 06:18:11 GMT, Serguei Spitsyn <[email protected]> wrote:
>> This JVMTI `GetObjectMonitorUsage` spec update is for Valhalla >> pre-integration. It is just a minor clarification on the value objects >> impact when preview features are enabled. >> >> The fix also includes a minor fix for the Valhalla `GetObjectMonitorUsage` >> test by adding a couple of more checks: >> >> `test/hotspot/jtreg/serviceability/jvmti/valhalla/GetObjectMonitorUsage/libValueGetObjectMonitorUsage.cpp` >> >> Testing: >> - Ran the test >> `test/hotspot/jtreg/serviceability/jvmti/valhalla/GetObjectMonitorUsage` >> locally >> - TBD: Submit mach5 tiers 1-3 to be completely safe. >> >> --------- >> - [x] I confirm that I make this contribution in accordance with the >> [OpenJDK Interim AI Policy](https://openjdk.org/legal/ai). > > Serguei Spitsyn has updated the pull request incrementally with one > additional commit since the last revision: > > review: remove bold and reorder new spec fragment src/hotspot/share/prims/jvmti.xml line 8317: > 8315: information for objects that have no identity. The fields of > the returned > 8316: <functionlink id="jvmtiMonitorUsage"></functionlink> structure > will always > 8317: be filled in with null values and zeros. Another way to present this could be to say that it is not possible to synchronize on a value object so there is no information to return. The fields of the returned ... ------------- PR Review Comment: https://git.openjdk.org/valhalla/pull/2609#discussion_r3504971776
