Re: libdrm_amdgpu being forked and merged into Mesa

On Fri, Oct 25, 2024 at 6:57 PM Michel Dänzer wrote: > On 2024-10-25 17:57, Bas Nieuwenhuizen wrote: > > On Fri, Oct 25, 2024 at 4:36 PM Michel Dänzer < > michel.daen...@mailbox.org > wrote: > > On 2024-10-25 12:18, Bas Nieuwenhuizen wrote: > > > > > (no

Re: libdrm_amdgpu being forked and merged into Mesa

On 2024-10-25 17:57, Bas Nieuwenhuizen wrote: > On Fri, Oct 25, 2024 at 4:36 PM Michel Dänzer > wrote: > On 2024-10-25 12:18, Bas Nieuwenhuizen wrote: > > > (not to mention that it would mean that any users would need to use > libdrm_amdgpu. Given that

Re: libdrm_amdgpu being forked and merged into Mesa

On Fri, Oct 25, 2024 at 4:36 PM Michel Dänzer wrote: > On 2024-10-25 12:18, Bas Nieuwenhuizen wrote: > > On Fri, Oct 25, 2024 at 11:21 AM Michel Dänzer < > michel.daen...@mailbox.org > wrote: > > > > On 2024-10-24 17:08, Marek Olšák wrote: > > > We don't

Re: libdrm_amdgpu being forked and merged into Mesa

On 2024-10-25 12:18, Bas Nieuwenhuizen wrote: > On Fri, Oct 25, 2024 at 11:21 AM Michel Dänzer > wrote: > > 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 dr

Unable to create a project in gitlab.freedesktop.org

Hello I want to do a merge request but I am unable to create any project, The gitlab page gives me this message: "You cannot create projects in your personal namespace. Contact your GitLab administrator." Also the fork button is not enabled (it is greyed out). Can you help me? Thanks

Re: libdrm_amdgpu being forked and merged into Mesa

On Fri, Oct 25, 2024 at 11:21 AM Michel Dänzer wrote: > 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 sh

Re: libdrm_amdgpu being forked and merged into Mesa

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

Re: libdrm_amdgpu being forked and merged into Mesa

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. Alex told me in person 2 weeks ago that we can put libdrm_amdgpu into Mesa. Marek On Thu,

Re: libdrm_amdgpu being forked and merged into Mesa

On Thu, Oct 24, 2024 at 8:38 AM Christian König wrote: > > Completely agree, but that's a platform decision which Alex needs to make. + Felix Does buffer sharing with ROCm depend on the shared VA space? Alex > > Christian. > > Am 24.10.24 um 14:16 schrieb Marek Olšák: > > I don't think we need

Re: libdrm_amdgpu being forked and merged into Mesa

I'm not sure what this means. ROCm allocates all its virtual address space with mmap. That includes address space for BOs imported with the interop APIs. We are sharing the GPU virtual address space with Mesa since we're using the same render nodes. So if Mesa's GPU virtual address space manag