SWDEV-351540 - ROCm path was derived from hsakmt library path.
For ASAN build, the library will be installed in <Install_prefix>/lib/asan rather than <Install_Prefix>/lib
Since the header file installation path remains the same for ASAN and normal build, using the same for getting the ROCm path
Change-Id: I735dbd3c0f67a69e833059a05851da3971098ec5
Before, the GPU IDs were counted starting from zero, now CPU IDs are counted from zero and then GPU IDs from the last CPU_ID+1
Change-Id: I3f815195ad97933e02f249841e53b64b674370d9
SWDEV-356024 - Development package name will have suffix dev or devel based on OS
Devel pacakge contents - Header files and non verioned lib file librocprofiler64.so
Runtime package contents - Binaries, xml files, python files , script files, license file, librocprof-tool.so and versioned library files
Change-Id: Id416b11f49a7d0acb917bc4936cc0cba0d101bee
The initialization should be controlled from build scripts. Removing the same from source code
Build scripts is initializing the variable to "lib"
Change-Id: I55b6cf4752e692735c2a0be13b79f5988137e3a6
File reorganization feature was implemented with backward compatibility
The backward compatibility support will be deprecated in future release.
Changed the #pragma message to #warning for a smooth transition
Change-Id: Ieb7726ef219af20b9260c1e35444813a36cd8508
hipGraphs acts as a separate activity group as they have their own memory copies and their kernel dispatches and more activities, currently hip api that roctracer depend on doesn't have a way to represent this type, so we are temporarily suppressing the issue up till we have a complete support for the hipGraphs
Change-Id: I5d889be05c9414530672c781e5a712d572ea4104
merge_traces.sh was depending on tblextr.py, and the location of tblextr.py changed from bin to libexec/rocprofiler
Change-Id: I76f1a0f41ffcff26e6a1119dacfb8b2ebd56d17d
This is an attempt to support basic and derived counters for navi21. This code will not work correctly unless we add navi counters to metrics.xml and gfx_metrics.xml
Change-Id: Ied06a81345a6fbb02fa0fde1889d94bbe64e9a03
Use hsa header files from /opt/rocm-ver/include rather than using wrapper files from /opt/rocm-ver/hsa/include/hsa
Change-Id: Id7a9bde19447cd2a0fd6e03b11c08471f09c2a46
Enabling the new methodology of ROCP_STATS_OPT of getting HIP activities while the application is running
Change-Id: I19d09e2f2abe16e6528240bf55d6048645aaa09f
This issue happens when we have slices that have overlapping
timestamp values (i.e. start_ts + dur = start_ts of next slice)
and the flow event references that shared timestamp value.
The google chrome parser sorts all the events
and just taking the most recent one.
Rocprof is outputting flow attachment points as start+dur;
the end ts of the slice that can overlap with the next slice
if no gap between them.
Solution proposal by Michael Steffen (Michael.Steffen@amd.com)
Change-Id: Ifcde142144033c9012b01a78c95f047384f972dd