Jonathan R. Madsen

Set the `OMNITRACE_USE_SAMPLING = true` and optionally increase/decrease the `OMNITRACE_SAMPLING_FREQ`

Is it showing up in `omnitrace-avail -H`?

Ah, yeah you may just have to specify all the CPUs if you have multiple CPUs, e.g. `OMNITRACE_PAPI_EVENTS = amd64_rapl::RAPL_ENERGY_PKG:cpu=0 amd64_rapl::RAPL_ENERGY_PKG:cpu=1 (etc.)` but I highly doubt the qualifier would be...

@TomMelt have you gotten a chance to verify that adding the `:cpu=X` qualifier provided the information you were seeking?

Hmmm... It's hard to tell if it is per core or not. Three of those bars look similar in magnitude when their samples are taken at overlapping timestamps -- those...

Sorry for the delay, I started a long vacation right around when you posted the last comment. I haven’t gotten a chance yet but I’ll look into it shortly.

You can use the environment variable `ROCR_VISIBLE_DEVICES` to hide that device in the HSA runtime — which will cause rocprof and Omnitrace to not see that device when they iterate...

Based on [the error message here](https://gist.github.com/anupambhatnagar/a113c9d30f6f937420b26b433323d4ab#file-omnitrace-out-L29), it looks like rocm-smi doesn’t support getting the temperature on MI300 so omnitrace [disables rocm-smi sampling](https://gist.github.com/anupambhatnagar/a113c9d30f6f937420b26b433323d4ab#file-omnitrace-out-L1704), which is why you don’t see any activity....

Try: `omnitrace-run -c config-file.cfg -- python -m omnitrace `

There may be some issues regardless which require some detailed explanation. I’ve got a full docket today so I’ll try to provide that once I’ve got some time.