Daniel Phillips
d3bb1ca4af
The MemoryAllocAll test in kfdtests exercises the new KFD memory availability API by trying to allocate a single buffer object that exactly fills all of vram. Desired object size is determined using the memory availility KFD ioctl via libhsakmt, then an object is allocated slightly larger than that size. If the allocation attempt fails then the test tries to allocate a slightly smaller object, and continues trying with smaller sizes until the allocation succeeds. The test succeeds if the successfully allocated object is within some specified tolerance of the available memory reported. There are a number of known issues that can cause the successfully allocated object to be significantly smaller than reported availability. Until these issues are addressed, we should not fail the test, but just log the actual divergence between the size of the object we thought we could allocate, and what was actually possible. Signed-off-by: Daniel Phillips <daniel.phillips@amd.com> Change-Id: I165a30865ffbb2353286dcc896ad8e24af124615
ROCt Library
This repository includes the user-mode API interfaces used to interact with the ROCk driver.
Starting at 1.7 release, ROCt uses drm render device. This requires the user to belong to video group. Add the user account to video group with "sudo usermod -a -G video username" command if the user if not part of video group yet. NOTE: Users of Ubuntu 20.04 will need to add the user to the new "render" group, as Ubuntu has changed the owner:group of /dev/kfd to render:render as of that release
ROCk Driver
The ROCt library is not a standalone product and requires that you have the correct ROCk driver set installed. We recommend reading the full compatibility and installation details which are available in the ROCk github:
https://github.com/RadeonOpenCompute/ROCK-Radeon-Open-Compute-Kernel-Driver
Building the Thunk
A simple cmake-based system is available for building thunk. To build the thunk from the the ROCT-Thunk-Interface directory, execute:
mkdir -p build
cd build
cmake ..
make
If the hsakmt-roct and hsakmt-roct-dev packages are desired:
mkdir -p build
cd build
cmake ..
make package
If you choose not to build and install packages, manual installation of the binaries and header files can be done via:
make install
NOTE: For older versions of the thunk where hsakmt-dev.txt is present, "make package-dev" and "make install-dev" are required to generate/install the developer packages. Currently, these are created via the "make package" and "make install" commands
Disclaimer
The information contained herein is for informational purposes only, and is subject to change without notice. While every precaution has been taken in the preparation of this document, it may contain technical inaccuracies, omissions and typographical errors, and AMD is under no obligation to update or otherwise correct this information. Advanced Micro Devices, Inc. makes no representations or warranties with respect to the accuracy or completeness of the contents of this document, and assumes no liability of any kind, including the implied warranties of noninfringement, merchantability or fitness for particular purposes, with respect to the operation or use of AMD hardware, software or other products described herein. No license, including implied or arising by estoppel, to any intellectual property rights is granted by this document. Terms and limitations applicable to the purchase or use of AMD's products are as set forth in a signed agreement between the parties or in AMD's Standard Terms and Conditions of Sale.
AMD, the AMD Arrow logo, and combinations thereof are trademarks of Advanced Micro Devices, Inc. Other product names used in this publication are for identification purposes only and may be trademarks of their respective companies.
Copyright (c) 2014-2020 Advanced Micro Devices, Inc. All rights reserved.