[prev in list] [next in list] [prev in thread] [next in thread] 

List:       openjdk-serviceability-dev
Subject:    Changing granularity of jvmtis DynamicCodeGenerated for interpreter
From:       Vladimir Kempik <vladimir.kempik () gmail ! com>
Date:       2023-05-31 10:33:04
Message-ID: 4D5C2E91-15D9-4010-8611-C8914B44D9D8 () gmail ! com
[Download RAW message or body]

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


[Attachment #3 (unknown)]

<html><head><meta http-equiv="content-type" content="text/html; \
charset=utf-8"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: \
space; line-break: after-white-space;"><span>Hello</span><span><br></span><span>I've \
found a need to change the granularity of JVMTI's&nbsp;DynamicCodeGenerated for \
interpreter's generated \
code.</span><div></div><div><span><br></span></div><div><span>Currently it shows just \
one big interpreter area, probably because of this \
code:</span></div><div><span><br></span></div><div><span style="color: rgb(63, 67, \
80); font-family: &quot;Open Sans&quot;, sans-serif; font-size: 13.5px; \
font-variant-ligatures: normal; orphans: 2; white-space: pre-wrap; widows: 2; \
background-color: rgba(63, 67, 80, 0.04); text-decoration-thickness: initial; \
text-decoration-style: initial; text-decoration-color: initial;"> \
                JvmtiExport::post_dynamic_code_generated("Interpreter",
                                             \
AbstractInterpreter::code()-&gt;code_start(),  \
AbstractInterpreter::code()-&gt;code_end());</span></div><div><span><br></span><span></span></div><span>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.</span><div><span><br></span></div><div><span>What would \
be the ideal place to insert \
detailed&nbsp;</span><span>JvmtiExport::post_dynamic_code_generated() calls \
&nbsp;then ?</span><div></div></div><div><span><br></span></div><div><span>Thanks in \
advance, Vladimir</span></div></body></html>



[prev in list] [next in list] [prev in thread] [next in thread]

Configure | About | News | Add a list | Sponsored by KoreLogic