RFR: 8315884: New Object to ObjectMonitor mapping

Axel Boldt-Christmas aboldtch at openjdk.org
Mon Jul 8 10:14:32 UTC 2024


On Mon, 8 Jul 2024 09:39:32 GMT, Thomas Wuerthinger <duke at openjdk.org> wrote:

> Is this change expected to require JVMCI and/or Graal JIT changes?

Support for `UseObjectMonitorTable` would require changes to Graal JIT. (`UseObjectMonitorTable` is off by default). 
Minimal support would be to call into the VM for inflated monitors. (Similarly to what this patch does for C2 for none x86 / aarch64 platforms).

For starting the VM normally without `UseObjectMonitorTable` no semantic change is required. All locking modes and VM invariants w.r.t. locking are the same.

As mentioned this patch contains a refactoring which renames one exported `JVMCI` symbol which I suspect should only be used by Graal JIT for `LM_LEGACY`. As such the Graal JIT needs to be updated to use this new symbol name.

-------------

PR Comment: https://git.openjdk.org/jdk/pull/20067#issuecomment-2213602121


More information about the serviceability-dev mailing list