[Intel-gfx] [PATCH 5/5] dma-buf: nuke reservation_object seq number

2019-08-09 Thread Christian König
The only remaining use for this is to protect against setting a new exclusive fence while we grab both exclusive and shared. That can also be archived by looking if the exclusive fence has changed or not after completing the operation. Signed-off-by: Christian König ---

Re: [Intel-gfx] [PATCH 5/5] dma-buf: nuke reservation_object seq number

2019-08-05 Thread Daniel Vetter
On Mon, Aug 05, 2019 at 05:07:41PM +0100, Chris Wilson wrote: > Quoting Christian König (2019-08-05 16:45:54) > > @@ -214,16 +214,16 @@ static __poll_t dma_buf_poll(struct file *file, > > poll_table *poll) > > return 0; > > > > retry: > > - seq =

Re: [Intel-gfx] [PATCH 5/5] dma-buf: nuke reservation_object seq number

2019-08-05 Thread Chris Wilson
Quoting Christian König (2019-08-05 16:45:54) > @@ -214,16 +214,16 @@ static __poll_t dma_buf_poll(struct file *file, > poll_table *poll) > return 0; > > retry: > - seq = read_seqcount_begin(>seq); > rcu_read_lock(); > > + fence_excl =