SWDEV-351980 - Enable profiling for commands reporting activities

Profiling should be enabled for any command reporting activities as the
activity record captures the profilingInfo's start and end timestamps.

Since IS_PROFILER_ON is only used to determine whether API tracing is
enabled, there is no need to expose it globally, it should be a property
of the activity_prof::CallbacksTable.

Change-Id: I44a0d19ed2862606cfbc9a98c1a07a336ab7e26c


[ROCm/clr commit: e713b5c7d0]
This commit is contained in:
Laurent Morichetti
2022-08-26 22:38:17 -07:00
committato da Maneesh Gupta
parent cbcc94b9e3
commit 353f9bc86c
4 ha cambiato i file con 7 aggiunte e 7 eliminazioni
+1 -1
Vedi File
@@ -143,7 +143,7 @@ class Event : public RuntimeObject {
Event();
//! Construct a new event associated to the given command \a queue.
Event(HostQueue& queue);
Event(HostQueue& queue, bool profilingEnabled = false);
//! Destroy the event.
virtual ~Event();