On Wed, Jan 11, 2017 at 04:19:19PM +0200, Joonas Lahtinen wrote:
> On ke, 2017-01-11 at 14:08 +, Chris Wilson wrote:
> > It is an error to start a new request on the same timeline (ringbuffer)
> > as the current one before the current is submitted. If there are two
> > requests emitting to the
On ke, 2017-01-11 at 14:08 +, Chris Wilson wrote:
> It is an error to start a new request on the same timeline (ringbuffer)
> as the current one before the current is submitted. If there are two
> requests emitting to the ringbuffer at the same time, the operation is
> undefined. We can catch t
Chris Wilson writes:
> It is an error to start a new request on the same timeline (ringbuffer)
> as the current one before the current is submitted. If there are two
> requests emitting to the ringbuffer at the same time, the operation is
> undefined. We can catch this by checking for the timelin
It is an error to start a new request on the same timeline (ringbuffer)
as the current one before the current is submitted. If there are two
requests emitting to the ringbuffer at the same time, the operation is
undefined. We can catch this by checking for the timeline having a later
seqno than our