Re: [PATCH v2] dma-buf: Wait on the reservation object when sync'ing before CPU access

On Mon, Dec 19, 2016 at 10:40:41AM +0900, Inki Dae wrote: > > > 2016년 08월 16일 01:02에 Daniel Vetter 이(가) 쓴 글: > > On Mon, Aug 15, 2016 at 04:42:18PM +0100, Chris Wilson wrote: > >> Rendering operations to the dma-buf are tracked implicitly via the > >> reservation_object (dmabuf->resv). This is

Re: [PATCH v2] dma-buf: Wait on the reservation object when sync'ing before CPU access

On Mon, Dec 19, 2016 at 10:40:41AM +0900, Inki Dae wrote: > > > 2016년 08월 16일 01:02에 Daniel Vetter 이(가) 쓴 글: > > On Mon, Aug 15, 2016 at 04:42:18PM +0100, Chris Wilson wrote: > >> Rendering operations to the dma-buf are tracked implicitly via the > >> reservation_object (dmabuf->resv). This is

Re: [PATCH v2] dma-buf: Wait on the reservation object when sync'ing before CPU access

2016년 08월 16일 01:02에 Daniel Vetter 이(가) 쓴 글: > On Mon, Aug 15, 2016 at 04:42:18PM +0100, Chris Wilson wrote: >> Rendering operations to the dma-buf are tracked implicitly via the >> reservation_object (dmabuf->resv). This is used to allow poll() to >> wait upon outstanding rendering (or just

Re: [PATCH v2] dma-buf: Wait on the reservation object when sync'ing before CPU access

2016년 08월 16일 01:02에 Daniel Vetter 이(가) 쓴 글: > On Mon, Aug 15, 2016 at 04:42:18PM +0100, Chris Wilson wrote: >> Rendering operations to the dma-buf are tracked implicitly via the >> reservation_object (dmabuf->resv). This is used to allow poll() to >> wait upon outstanding rendering (or just

Re: [PATCH v2] dma-buf: Wait on the reservation object when sync'ing before CPU access

On Mon, Aug 15, 2016 at 04:42:18PM +0100, Chris Wilson wrote: > Rendering operations to the dma-buf are tracked implicitly via the > reservation_object (dmabuf->resv). This is used to allow poll() to > wait upon outstanding rendering (or just query the current status of > rendering). The dma-buf

Re: [PATCH v2] dma-buf: Wait on the reservation object when sync'ing before CPU access

On Mon, Aug 15, 2016 at 04:42:18PM +0100, Chris Wilson wrote: > Rendering operations to the dma-buf are tracked implicitly via the > reservation_object (dmabuf->resv). This is used to allow poll() to > wait upon outstanding rendering (or just query the current status of > rendering). The dma-buf

[PATCH v2] dma-buf: Wait on the reservation object when sync'ing before CPU access

Rendering operations to the dma-buf are tracked implicitly via the reservation_object (dmabuf->resv). This is used to allow poll() to wait upon outstanding rendering (or just query the current status of rendering). The dma-buf sync ioctl allows userspace to prepare the dma-buf for CPU access,

[PATCH v2] dma-buf: Wait on the reservation object when sync'ing before CPU access

Rendering operations to the dma-buf are tracked implicitly via the reservation_object (dmabuf->resv). This is used to allow poll() to wait upon outstanding rendering (or just query the current status of rendering). The dma-buf sync ioctl allows userspace to prepare the dma-buf for CPU access,

[PATCH v2] dma-buf: Wait on the reservation object when sync'ing before CPU access

Rendering operations to the dma-buf are tracked implicitly via the reservation_object (dmabuf->resv). This is used to allow poll() to wait upon outstanding rendering (or just query the current status of rendering). The dma-buf sync ioctl allows userspace to prepare the dma-buf for CPU access,

[PATCH v2] dma-buf: Wait on the reservation object when sync'ing before CPU access

Rendering operations to the dma-buf are tracked implicitly via the reservation_object (dmabuf->resv). This is used to allow poll() to wait upon outstanding rendering (or just query the current status of rendering). The dma-buf sync ioctl allows userspace to prepare the dma-buf for CPU access,