[PATCH 1/5] drm: introduce sync objects (v3)

2017-05-29 Thread Dave Airlie
From: Dave Airlie Sync objects are new toplevel drm object, that contain a pointer to a fence. This fence can be updated via command submission ioctls via drivers. There is also a generic wait obj API modelled on the vulkan wait API (with code modelled on some amdgpu code). These objects can be

Re: [PATCH 1/5] drm: introduce sync objects (v3)

2017-05-25 Thread Dave Airlie
On 25 May 2017 at 18:30, Chris Wilson wrote: > On Wed, May 24, 2017 at 05:06:11PM +1000, Dave Airlie wrote: >> From: Dave Airlie >> >> Sync objects are new toplevel drm object, that contain a >> pointer to a fence. This fence can be updated via command >> submission ioctls via drivers. >> >> Ther

Re: [PATCH 1/5] drm: introduce sync objects (v3)

2017-05-25 Thread Chris Wilson
On Wed, May 24, 2017 at 05:06:11PM +1000, Dave Airlie wrote: > From: Dave Airlie > > Sync objects are new toplevel drm object, that contain a > pointer to a fence. This fence can be updated via command > submission ioctls via drivers. > > There is also a generic wait obj API modelled on the vulk

Re: [PATCH 1/5] drm: introduce sync objects (v3)

2017-05-24 Thread Jason Ekstrand
I can't really review for all of the kernel details (though the seem ok to me) so this mostly applies to the API: Reviewed-by: Jason Ekstrand On Wed, May 24, 2017 at 12:06 AM, Dave Airlie wrote: > From: Dave Airlie > > Sync objects are new toplevel drm object, that contain a > pointer to a fe

[PATCH 1/5] drm: introduce sync objects (v3)

2017-05-24 Thread Dave Airlie
From: Dave Airlie Sync objects are new toplevel drm object, that contain a pointer to a fence. This fence can be updated via command submission ioctls via drivers. There is also a generic wait obj API modelled on the vulkan wait API (with code modelled on some amdgpu code). These objects can be