## Build docker image ```bash DOCKER_BUILDKIT=1 docker build -t ck:latest -f Dockerfile . ``` ## Launch docker ```bash docker run \ -it \ --privileged \ --group-add sudo \ -w /root/workspace \ -v ${PATH_TO_LOCAL_WORKSPACE}:/root/workspace \ ck:latest \ /bin/bash ``` ## Build CK ```bash mkdir build && cd build # Need to specify target ID, example below is for gfx908 and gfx90a cmake \ -D CMAKE_PREFIX_PATH=/opt/rocm \ -D CMAKE_CXX_COMPILER=/opt/rocm/bin/hipcc \ -D CMAKE_CXX_FLAGS="-O3" \ -D CMAKE_BUILD_TYPE=Release \ -D GPU_TARGETS=gfx908;gfx90a \ .. ``` ### Build examples and tests ```bash make -j examples tests make test ``` Instructions for running each individual examples are under ```example/``` ## Build ckProfiler ```bash make -j ckProfiler ``` Instructions for running ckProfiler are under ```profiler/``` ## Install CK ```bash make install ``` ## Using CK as pre-built kernel library Instructions for using CK as a pre-built kernel library are under ```client_example/``` ## Caveat ### Kernel Timing and Verification CK's own kernel timer will warn up kernel once, and then run it multiple times to get average kernel time. For some kernels that use atomic add, this will cause output buffer to be accumulated multiple times, causing verfication failure. To work around it, do not use CK's own timer and do verification at the same time. CK's own timer and verification in each example and ckProfiler can be enabled or disabled from command line.