JFR V2 cmdline option parsing - #23776
Conversation
tajila
left a comment
There was a problem hiding this comment.
The main required change is still missing. Basically, #define VMOPT_XXSTARTOPENJ9EXPERIMENTALFLIGHTRECORDING "-XX:StartOpenJ9ExperimentalFlightRecording" can go away and instead we can replace with -XX:+|-EnableOpenJ9ExperimentalFlightRecording which will set the J9_EXTENDED_RUNTIME3_JFR_V2_SUPPORT flag if enabled.
What is currently done under -XX:StartOpenJ9ExperimentalFlightRecording ie https://github.com/eclipse-openj9/openj9/blob/master/runtime/vm/jvminit.c#L4657-L4675 should now be done in -XX:StartFlightRecording= only if J9_EXTENDED_RUNTIME3_JFR_V2_SUPPORT. If the flag is not set, then the existing behaviour should remain.
|
Added @tajila could you have another look? |
|
@tajila this is ready for review. |
JFR V2 implementation can be enabled only when JFR support is enabled; Added com.ibm.oti.vm.VM.isJFRV2SupportEnabled() and native; Removed VMOPT_XXSTARTOPENJ9EXPERIMENTALFLIGHTRECORDING; Updated JFR V2 cmdline option parsing; Added a test. Signed-off-by: Jason Feng <fengj@ca.ibm.com>
|
Removed This seems due to uncompleted V2 implementation openj9/runtime/jcl/common/jdk_jfr_internal_JVM_common.cpp Lines 402 to 405 in dadf38d |
|
jenkins test sanity.functional,extended.functional xlinux jdk17,jdk21 |
JFR V2 cmdline option parsing
JFR V2 implementation can be enabled only when JFR support is enabled;
Added
com.ibm.oti.vm.VM.isJFRV2SupportEnabled()and native;Removed
VMOPT_XXSTARTOPENJ9EXPERIMENTALFLIGHTRECORDING;Updated JFR V2 cmdline option parsing;
Added a test.
Related to
Signed-off-by: Jason Feng fengj@ca.ibm.com