Changing granularity of jvmtis DynamicCodeGenerated for interpreter
Vladimir Kempik
vladimir.kempik at gmail.com
Wed May 31 10:33:04 UTC 2023
Hello
I’ve found a need to change the granularity of JVMTI’s DynamicCodeGenerated for interpreter’s generated code.
Currently it shows just one big interpreter area, probably because of this code:
JvmtiExport::post_dynamic_code_generated("Interpreter",
AbstractInterpreter::code()->code_start(),
AbstractInterpreter::code()->code_end());
However for template interpreter it’s possible to generate such entry for every bytecode instruction code generated ( e.g. one for sipush, etc). Just like -XX:+PrintInterpreter does.
What would be the ideal place to insert detailed JvmtiExport::post_dynamic_code_generated() calls then ?
Thanks in advance, Vladimir
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/serviceability-dev/attachments/20230531/80fe5bf3/attachment.htm>
More information about the serviceability-dev
mailing list