Re: libdrm_amdgpu being forked and merged into Mesa
Alex Deucher <[email protected]> Thu, 24 Oct 2024 09:24:22 -0400
| Newsgroups | gmane.comp.video.mesa3d.devel |
|---|---|
| Message-ID | <CADnq5_NhjK+xmi-6qR5JFMGNxCGpruS7CkmU5rC9PAur3WooDg@mail.gmail.com> |
On Thu, Oct 24, 2024 at 8:38 AM Christian König <[email protected]> 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 to share VA space. APIs usually share one or two buffers. That's almost nothing compared to the size of the occupied VA space. They also likely map them again for themselves - APIs don't share any virtual addresses as far as I know. > > Marek > > On Thu, Oct 24, 2024, 08:12 Christian König <[email protected]> wrote: >> >> Am 22.10.24 um 06:06 schrieb Marek Olšák: >> > Hi, >> > >> > The MR is up: >> > https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/31756 >> > >> > It's good to go as long as there is no functional issue. >> >> Finally getting rid of all the mid-layering? What about shared VA-space? >> >> Regards, >> Christian. >> >> > >> > libdrm_amdgpu will still be relevant for PAL, ROCm, and xf86-video-amdgpu. >> > >> > Marek >> >