On Tue, Jul 13, 2021 at 7:42 PM Rob Clark wrote:
> On Tue, Jul 13, 2021 at 9:58 AM Daniel Vetter wrote:
> >
> > On Tue, Jul 13, 2021 at 6:51 PM Rob Clark wrote:
> > >
> > > On Mon, Jul 12, 2021 at 1:02 PM Daniel Vetter
> > > wrote:
> > > >
> > > > There's only one exclusive slot, and we must n
On Tue, Jul 13, 2021 at 9:58 AM Daniel Vetter wrote:
>
> On Tue, Jul 13, 2021 at 6:51 PM Rob Clark wrote:
> >
> > On Mon, Jul 12, 2021 at 1:02 PM Daniel Vetter
> > wrote:
> > >
> > > There's only one exclusive slot, and we must not break the ordering.
> > >
> > > Adding a new exclusive fence dr
On Tue, Jul 13, 2021 at 6:51 PM Rob Clark wrote:
>
> On Mon, Jul 12, 2021 at 1:02 PM Daniel Vetter wrote:
> >
> > There's only one exclusive slot, and we must not break the ordering.
> >
> > Adding a new exclusive fence drops all previous fences from the
> > dma_resv. To avoid violating the signa
On Mon, Jul 12, 2021 at 1:02 PM Daniel Vetter wrote:
>
> There's only one exclusive slot, and we must not break the ordering.
>
> Adding a new exclusive fence drops all previous fences from the
> dma_resv. To avoid violating the signalling order we err on the side of
> over-synchronizing by waitin
There's only one exclusive slot, and we must not break the ordering.
Adding a new exclusive fence drops all previous fences from the
dma_resv. To avoid violating the signalling order we err on the side of
over-synchronizing by waiting for the existing fences, even if
userspace asked us to ignore t
