Closed fwyzard closed 2 years ago
It does work. If you create amd and nvidia device on the same thread, you always need to call oroCtxSetCurrent
before calling functions like oroMalloc
. However, if you create a device per thread, it simply works without doing it as the api choice is stored per thread.
We have some applications executing on amd and nvidia at the same time in a single app which is working totally fine.
Thanks !
From a quick look at the code, it seems that some parts do, while others do not. For example, the initialisation and device handling seem to support enabling both CUDA and HIP at the same time, while the host memory allocation and registration functions work with only either one at a time.