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 0/3] drm/amdgpu: Tweaks for high pressure on CPU visible VRAM

2017-05-25 Thread Michel Dänzer
On 25/05/17 08:24 PM, Marek Olšák wrote: > On Thu, May 25, 2017 at 5:31 AM, Michel Dänzer wrote: >> On 24/05/17 08:27 PM, Christian König wrote: >>> Am 24.05.2017 um 13:03 schrieb Marek Olšák: > I think the final solution (done in fault_reserve_notify) should be: if (bo->num_cpu_page

[pull] radeon and amdgpu drm-fixes-4.12

2017-05-25 Thread Alex Deucher
Hi Dave, A bunch of bug fixes: - Fix display flickering on some chips at high refresh rates - suspend/resume fix - hotplug fix - a couple of segfault fixes for certain cases The following changes since commit d51aff16e821a755c242e14168f5d4601199eafd: Merge branch 'for-upstream/hdlcd' of git://

Re: [PATCH 2/5] drm/syncobj: add sync obj wait interface. (v3)

2017-05-25 Thread Christian König
Am 25.05.2017 um 10:47 schrieb Chris Wilson: On Wed, May 24, 2017 at 05:06:12PM +1000, Dave Airlie wrote: From: Dave Airlie This interface will allow sync object to be used to back Vulkan fences. This API is pretty much the vulkan fence waiting API, and I've ported the code from amdgpu. v2: a

Re: [PATCH 0/3] drm/amdgpu: Tweaks for high pressure on CPU visible VRAM

2017-05-25 Thread Marek Olšák
On Thu, May 25, 2017 at 5:31 AM, Michel Dänzer wrote: > On 24/05/17 08:27 PM, Christian König wrote: >> Am 24.05.2017 um 13:03 schrieb Marek Olšák: >>> I think the final solution (done in fault_reserve_notify) should be: >>> if (bo->num_cpu_page_faults++ > 20) >>> bo->preferred_domain = G

Re: [PATCH 3/5] drm/syncobj: add sync_file interaction.

2017-05-25 Thread Chris Wilson
On Wed, May 24, 2017 at 05:06:13PM +1000, Dave Airlie wrote: > From: Dave Airlie > > This interface allows importing the fence from a sync_file into > an existing drm sync object, or exporting the fence attached to > an existing drm sync object into a new sync file object. > > This should only b

Re: [PATCH 2/5] drm/syncobj: add sync obj wait interface. (v3)

2017-05-25 Thread Chris Wilson
On Wed, May 24, 2017 at 05:06:12PM +1000, Dave Airlie wrote: > From: Dave Airlie > > This interface will allow sync object to be used to back > Vulkan fences. This API is pretty much the vulkan fence waiting > API, and I've ported the code from amdgpu. > > v2: accept relative timeout, pass remai

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