Background:
I'm currently working on profiling the WOA (Windows on ARM) emulation layer.
My goal is to measure the time spent on each DLL and XTAJIT cache file.
However, at present, all JIT-compiled DLLs are grouped under a single "Unknown" item in the profiler.
Limitation:
Profile Explorer uses frameIp to check DLL and calc time.
However, XTAJIT cache files are not standard PE images—they are injected at runtime by xtajit.dll and xtacache.exe.
As a result, there is no image address information available in the ETL file for these cache files.
Question:
Is it possible to enhance the kernel to include this information, or is there a feasible workaround to accurately attribute time spent to each XTAJIT cache file?
Looking forward to your feedback
Background:
I'm currently working on profiling the WOA (Windows on ARM) emulation layer.
My goal is to measure the time spent on each DLL and XTAJIT cache file.
However, at present, all JIT-compiled DLLs are grouped under a single "Unknown" item in the profiler.
Limitation:
Profile Explorer uses frameIp to check DLL and calc time.
However, XTAJIT cache files are not standard PE images—they are injected at runtime by xtajit.dll and xtacache.exe.
As a result, there is no image address information available in the ETL file for these cache files.
Question:
Is it possible to enhance the kernel to include this information, or is there a feasible workaround to accurately attribute time spent to each XTAJIT cache file?
Looking forward to your feedback