This update is for Valhalla pre-integration. It introduces new JVMTI capability
`can_support_value_objects`.
The variable `_can_support_value_objects_count` is introduced for optimization.
It follows the pattern of the `can_support_virtual_threads` capability.
Additionally, this update includes test fixes:
- test/hotspot/jtreg/serviceability/jvmti/HeapMonitor/libHeapMonitorTest.cpp:
- Removed the `if (!jni->HasIdentity(object))` check because it is not
needed anymore as the JVMTI capability `can_support_value_objects` is no
acquired by the test
- These two tests are updated to provide both positive and negative coverage
for new capability:
test/hotspot/jtreg/serviceability/jvmti/valhalla/VMObjectAllocValue
test/hotspot/jtreg/serviceability/jvmti/valhalla/SampledObjectAllocValue
Testing:
- Ran updated tests locally
- Submitted mach5 tiers 1-6
---------
- [x] I confirm that I make this contribution in accordance with the [OpenJDK
Interim AI Policy](https://openjdk.org/legal/ai).
-------------
Commit messages:
- 8387552: [lworld] Add new capability to enable value objects support for
JVMTI VMObjectAlloc and SampledObjectAlloc
Changes: https://git.openjdk.org/valhalla/pull/2607/files
Webrev: https://webrevs.openjdk.org/?repo=valhalla&pr=2607&range=00
Issue: https://bugs.openjdk.org/browse/JDK-8387552
Stats: 98 lines in 10 files changed: 72 ins; 6 del; 20 mod
Patch: https://git.openjdk.org/valhalla/pull/2607.diff
Fetch: git fetch https://git.openjdk.org/valhalla.git pull/2607/head:pull/2607
PR: https://git.openjdk.org/valhalla/pull/2607
