<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Oct 25, 2024 at 4:36 PM Michel Dänzer <<a href="mailto:michel.daenzer@mailbox.org">michel.daenzer@mailbox.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On 2024-10-25 12:18, Bas Nieuwenhuizen wrote:<br>
> On Fri, Oct 25, 2024 at 11:21 AM Michel Dänzer <<a href="mailto:michel.daenzer@mailbox.org" target="_blank">michel.daenzer@mailbox.org</a> <mailto:<a href="mailto:michel.daenzer@mailbox.org" target="_blank">michel.daenzer@mailbox.org</a>>> wrote:<br>
> <br>
> On 2024-10-24 17:08, Marek Olšák wrote:<br>
> > We don't need to share the same VMID between ROCm and Mesa. We don't<br>
> > need to share the same driver FD between ROCm and Mesa either. It will<br>
> > be like having 2 different processes, and that should always work.<br>
> <br>
> Per <a href="https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/31756#note_2626236" rel="noreferrer" target="_blank">https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/31756#note_2626236</a> <<a href="https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/31756#note_2626236" rel="noreferrer" target="_blank">https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/31756#note_2626236</a>>, 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)<br>
> <br>
> <br>
> In RADV the app has no way to pass in a drm fd, there is only a way to query the major/minor from the fd (<a href="https://registry.khronos.org/vulkan/specs/1.3-extensions/html/chap55.html#VK_EXT_physical_device_drm" rel="noreferrer" target="_blank">https://registry.khronos.org/vulkan/specs/1.3-extensions/html/chap55.html#VK_EXT_physical_device_drm</a> <<a href="https://registry.khronos.org/vulkan/specs/1.3-extensions/html/chap55.html#VK_EXT_physical_device_drm" rel="noreferrer" target="_blank">https://registry.khronos.org/vulkan/specs/1.3-extensions/html/chap55.html#VK_EXT_physical_device_drm</a>>).<br>
<br>
Hmm. So Wayland compositors which use Vulkan have to share BOs from Vulkan into their DRM file description for KMS via dma-buf?<br>
<br>
<br>
How about ROCm, no way to pass in / retrieve a DRM file descriptor there either?<br>
<br>
<br>
> (not to mention that it would mean that any users would need to use libdrm_amdgpu. Given that the most likely combination of GBM with shared fd/handle stuff is kernel modesetting and nobody uses libdrm_amdgpu with that, having a shared libdrm_amdgpu would not help there)<br>
<br>
Not sure what you mean here, Wayland compositors use radeonsi with KMS.<br>
<br></blockquote><div>That is what I mean, since they use KMS directly, anything that radeonsi does wrt using or not using libdrm_amdgpu doesn't impact them. <br></div><div><br></div><div>(note that some compositors, like gamescope do the actual dmabuf dance)<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
-- <br>
Earthling Michel Dänzer \ GNOME / Xwayland / Mesa developer<br>
<a href="https://redhat.com" rel="noreferrer" target="_blank">https://redhat.com</a> \ Libre software enthusiast<br>
</blockquote></div></div>