On 2024-10-24 17:08, Marek Olšák wrote: > We don't need to share the same VMID between ROCm and Mesa. We don't > need to share the same driver FD between ROCm and Mesa either. It will > be like having 2 different processes, and that should always work.
Per https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/31756#note_2626236, does anything prevent the application from passing the same DRM file description (doesn't need to be the same *descriptor*) to separate drivers? (Not sure it can even pass a DRM fd to ROCm, surely can e.g. to radeonsi & AMDVLK though) I guess one way to avoid this issue would be for Mesa to always use a different DRM file description internally, then it would have to share buffers with the DRM file description passed in by the application as needed though. -- Earthling Michel Dänzer \ GNOME / Xwayland / Mesa developer https://redhat.com \ Libre software enthusiast
