Kernel execution serialization about radeon_compute_profiler HOT 4 OPEN

When collecting performance counters, the profiler will introduce serialization to try to ensure that only one kernel is executing at a time. There is no option for this, as it is the default behavior.

from radeon_compute_profiler.

What about measuring performance in real-life environment under concurrent execution?

Additionally this seems to imply that traces in CodeXL can't be used to analyze kernel overlap?

from radeon_compute_profiler.

Serialization is only done when collecting performance counters (which is the mode you would use to analyze performance of individual kernels). No additional serialization is introduced when collecting a trace (which is the mode you would use to analyze an entire application (including kernel overlap)).

from radeon_compute_profiler.

I see. I'd suggest allowing serialization to be turned on/off.

Is there a way to measure wall-time only without serialization?

from radeon_compute_profiler.