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:
committed by
Maneesh Gupta
parent
cbcc94b9e3
commit
353f9bc86c
@@ -82,7 +82,6 @@ namespace amd {
|
||||
#endif // __APPLE__
|
||||
|
||||
bool IS_HIP = false;
|
||||
std::atomic_bool IS_PROFILER_ON(false);
|
||||
|
||||
#if !defined(_WIN32) && defined(WITH_PAL_DEVICE)
|
||||
bool IS_LEGACY = true;
|
||||
|
||||
@@ -282,7 +282,6 @@ release(bool, ROC_EVENT_NO_FLUSH, false, \
|
||||
namespace amd {
|
||||
|
||||
extern bool IS_HIP;
|
||||
extern std::atomic_bool IS_PROFILER_ON;
|
||||
|
||||
extern bool IS_LEGACY;
|
||||
|
||||
|
||||
Reference in New Issue
Block a user