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
This commit is contained in:
1 parent
4fbae91468
commit
e713b5c7d0
4 files changed
+7
-7
No files matched your search
@@ -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();
|
||||
|
||||
Reference in new issue
Block a user