On Wed, Jul 7, 2021 at 2:31 PM Lucas Stach wrote:
>
> Am Mittwoch, dem 07.07.2021 um 13:37 +0200 schrieb Daniel Vetter:
> > On Wed, Jul 7, 2021 at 10:54 AM Lucas Stach wrote:
> > >
> > > Hi Daniel,
> > >
> > > I'm feeling like I miss a ton of context here, so some maybe dumb
> > > questions/remar
Am Mittwoch, dem 07.07.2021 um 13:37 +0200 schrieb Daniel Vetter:
> On Wed, Jul 7, 2021 at 10:54 AM Lucas Stach wrote:
> >
> > Hi Daniel,
> >
> > I'm feeling like I miss a ton of context here, so some maybe dumb
> > questions/remarks below.
> >
> > Am Dienstag, dem 06.07.2021 um 12:12 +0200 sch
On Wed, Jul 7, 2021 at 10:54 AM Lucas Stach wrote:
>
> Hi Daniel,
>
> I'm feeling like I miss a ton of context here, so some maybe dumb
> questions/remarks below.
>
> Am Dienstag, dem 06.07.2021 um 12:12 +0200 schrieb Daniel Vetter:
> > There's only one exclusive slot, and we must not break the or
Hi Daniel,
I'm feeling like I miss a ton of context here, so some maybe dumb
questions/remarks below.
Am Dienstag, dem 06.07.2021 um 12:12 +0200 schrieb Daniel Vetter:
> There's only one exclusive slot, and we must not break the ordering.
>
> A better fix would be to us a dma_fence_chain or _arr
There's only one exclusive slot, and we must not break the ordering.
A better fix would be to us a dma_fence_chain or _array like e.g.
amdgpu now uses, but it probably makes sense to lift this into
dma-resv.c code as a proper concept, so that drivers don't have to
hack up their own solution each o
