Skip to content

CAUTION: This site hosts draft documentation for the next release. For published content of the latest release, visit www.eclipse.org/openj9/docs

-XX:[+|-]CRIURestoreNonPortableMode

(Linux® x86, Linux on POWER® (Little Endian), Linux on AArch64, and Linux on IBM Z® only)

This option specifies whether the JIT and AOT compilers generate nonportable compiled code on restore.

Restrictions:

  • This option takes effect only when -XX:+EnableCRIUSupport is enabled.
  • When you disable this option,
    • By default, CRIUSECProvider is the only security provider in both checkpoint and restore. Start of content that applies to Java 11 (LTS) and later But, if CRIUSECProvider is disabled with the -XX:-CRIUSecProvider option, then the existing security providers are used during the checkpoint phase and restore phase. You can use any algorithm in the existing providers. End of content that applies to Java 11 (LTS) and later
    • JITServer technology is disabled both before you take a checkpoint and after you restore the VM.
    • the VM generates only portable code, both before you take a checkpoint and after you restore the VM.

Syntax

    -XX:[+|-]CRIURestoreNonPortableMode
Setting Effect Default
-XX:+CRIURestoreNonPortableMode Enable yes
-XX:-CRIURestoreNonPortableMode Disable

Explanation

The JIT compiler can use hardware features of the system on which it is running to generate compiled code. That code might therefore fail if it is included in a checkpoint image that you later restore on a different system. For example, the compiled code might try to use a hardware feature that doesn't exist on the new machine, then fail. To avoid this problem, the JIT compiler by default generates code that uses only basic hardware features, therefore portable to different systems.

The -XX:+CRIURestoreNonPortableMode option is set by default so that on restore the JIT compiler can start generating nonportable compiled code. Likewise, the VM can also load nonportable AOT code post-restore. Generating nonportable compiled code also means that no further checkpoints are permitted. Only a single checkpoint can be taken in the VM's lifetime.

If you require multiple checkpoints, you can use the -XX:-CRIURestoreNonPortableMode option to generate portable JIT compiled code after restore.

See also