rocm-systems

Files

T

Kent Russell 9745db3053 KFDTest: Use default packaging name for kfdtest

Previously we omitted the version and arch in the filenames. By adding this,
as well as the ROCM build variable, this will allow for easy version
version detection on systems. Instead of kfdtest = v1.0.0, now it will
feature the build number, allowing for easier identification as to which
version is installed.

Change-Id: I311ed7010486e7c70af669d282910fe29ee8db45

2022-07-12 12:41:20 -04:00

gtest-1.6.0

kfdtest: Add kfdtest source code

2018-07-31 00:00:34 -04:00

include

kfdtest: Add PM4WaitRegMemPacket

2019-11-15 15:27:21 -05:00

scripts

kfdtest: Update gpuName logic for ip discovery

2022-06-23 13:48:26 -04:00

src

kfdtest: add KFDSVMRangeTest.HMMProfilingEvent

2022-07-06 10:08:44 -04:00

.gitignore

kfdtest: Add kfdtest source code

2018-07-31 00:00:34 -04:00

CMakeLists.txt

KFDTest: Use default packaging name for kfdtest

2022-07-12 12:41:20 -04:00

LICENSE.kfdtest

kfdtest: Add kfdtest source code

2018-07-31 00:00:34 -04:00

README.txt

kfdtest: Add run utility files for kfdtest

2018-07-31 00:02:04 -04:00

README.txt

1. Note on building kfdtest

To build this kfdtest application, the following libraries should be already
installed on the building machine:
libdrm libdrm_amdgpu libhsakmt

If libhsakmt is not installed, but the headers and libraries are present
locally, you can specify its directory by
export LIBHSAKMT_PATH=/*your local libhsakmt folder*/
With that, the headers and libraries are searched under
LIBHSAKMT_PATH/include and LIBHSAKMT_PATH/lib respectively.


2. How to run kfdtest

Just run "./run_kfdtest.sh" under the building output folder. You may need
to specify library path through:
export LD_LIBRARY_PATH=/*your library path containing libhsakmt*/

Note: you can use "run_kfdtest.sh -h" to see more options.