Currently CPU (profiler.h) and GPU (exposed in vk_combuf.h) profilers provide completely disjoint event streams.
They are kind of fundamentally different:
different even sources,
only loosely synchronized timestamps sources (might be slightly mismatching),
different rules about when a consistent set of events is available (cpu: at frame boundary, gpu: after the previous frame has been fully processed, which is a bit into current cpu frame ideally).
But it might be still useful to combine them functionally, so that consuming these event is easy from a single "source of truth".
Also, embedding all profiler logic into profiler.h makes it extractable into its own "library".
Currently CPU (
profiler.h) and GPU (exposed invk_combuf.h) profilers provide completely disjoint event streams. They are kind of fundamentally different:But it might be still useful to combine them functionally, so that consuming these event is easy from a single "source of truth".
Also, embedding all profiler logic into
profiler.hmakes it extractable into its own "library".