roctracer: use multiple tracks for HIP streams

[Maetveis]

Use different perfetto tracks for each stream, and set the name of these tracks to the stream pointer values. Setting the name like this matches the args in the API traces.
This fixes overlapping work on multiple streams appearing as a call stack.

Here's a screenshot of the results:

I would like to add an option to disable the new behaviour, because some applications might create a large number of streams which would obscure the traces. The environment variable and option parsing parts I don't yet fully understand so therefore Draft, and I would appreciate some hints for that.

[jrmadsen]

The environment variable and option parsing parts I don't yet fully understand so therefore Draft, and I would appreciate some hints for that.

Create a declaration for getting the option in source/lib/omnitrace/library/config.hpp, add the option right after here (or closer to other similar options in terms of categories):

https://github.com/AMDResearch/omnitrace/blob/654beef6ab730e87d837fec9b2ca33d36b81e781/source/lib/omnitrace/library/config.cpp#L607

The macro is <type>, <name>, <description>, <default-value>, <categories...>.

Then implement getting the value in config.cpp, something like:

bool
get_perfetto_roctracer_per_stream()
{
    static auto _v = get_config()->find("OMNITRACE_<name>");
    return static_cast<tim::tsettings<bool>&>(*_v->second).get();
}

[jrmadsen]

Build error: https://my.cdash.org/viewBuildError.php?buildid=2242917

[omnitrace/omnitrace/source/lib/omnitrace/library/roctracer.cpp:519](https://github.com/AMDResearch/omnitrace/blob/master/omnitrace/omnitrace/source/lib/omnitrace/library/roctracer.cpp#L519):2: error: extra ‘;’ [-Werror=pedantic]
  519 | };
      |  ^
[omnitrace/omnitrace/source/lib/omnitrace/library/roctracer.cpp:527](https://github.com/AMDResearch/omnitrace/blob/master/omnitrace/omnitrace/source/lib/omnitrace/library/roctracer.cpp#L527):2: error: extra ‘;’ [-Werror=pedantic]
  527 | };
      |  ^

Just noting this to point you to the dashboard since this is nicer (IMO) than the logs from GitHub actions

[Maetveis]

For tests I don't know how to tackle this, as I see perfetto traces can be verified by the python script, but it isn't aware of tracks currently.

[jrmadsen]

@Maetveis I am going to open a PR onto your branch with these changes. In #206, I am making perfetto annotations optional and I want to get this merged before that to avoid you having to deal with the (likely) conflicts.

[Maetveis]

I am making perfetto annotations optional and I want to get this merged before that to avoid you having to deal with the (likely) conflicts.

Thanks, altough I might only be able to continue working on this PR next week, so maybe you shouldn't hold out on it.

[jrmadsen]

Superceded by #209