Re: [PATCH] drm/radeon: Override fpfn for all VRAM placements in radeon_evict_flags

2017-03-27 Thread Michel Dänzer
On 27/03/17 06:33 PM, Julien Isorce wrote: > Hi Michel, > > Great ! Would you mind to just add a note to mention that the infinite > loop actually happens in ttm_bo_mem_force_space ? Thx! I'm afraid it might be too late, as I already pushed the fix to the amd-staging-4.9 branch. I guess Alex coul

Re: [PATCH] drm/radeon: Override fpfn for all VRAM placements in radeon_evict_flags

2017-03-27 Thread Zachary Michaels
Thanks for the help and the quick turnaround! On Sun, Mar 26, 2017 at 11:36 PM, Christian König wrote: > Am 27.03.2017 um 02:58 schrieb Michel Dänzer: > >> From: Michel Dänzer >> >> We were accidentally only overriding the first VRAM placement. For BOs >> with the RADEON_GEM_NO_CPU_ACCESS flag

RE: [PATCH] drm/radeon: Override fpfn for all VRAM placements in radeon_evict_flags

2017-03-27 Thread Deucher, Alexander
> -Original Message- > From: amd-gfx [mailto:amd-gfx-boun...@lists.freedesktop.org] On Behalf > Of Michel Dänzer > Sent: Sunday, March 26, 2017 8:59 PM > To: amd-gfx@lists.freedesktop.org > Cc: Zachary Michaels; Julien Isorce > Subject: [PATCH] drm/radeon: Overr

Re: [PATCH] drm/radeon: Override fpfn for all VRAM placements in radeon_evict_flags

2017-03-27 Thread Julien Isorce
Hi Michel, Great ! Would you mind to just add a note to mention that the infinite loop actually happens in ttm_bo_mem_force_space ? Thx! Cheers Julien On 27 March 2017 at 07:36, Christian König wrote: > Am 27.03.2017 um 02:58 schrieb Michel Dänzer: > >> From: Michel Dänzer >> >> We were accid

Re: [PATCH] drm/radeon: Override fpfn for all VRAM placements in radeon_evict_flags

2017-03-26 Thread Christian König
Am 27.03.2017 um 02:58 schrieb Michel Dänzer: From: Michel Dänzer We were accidentally only overriding the first VRAM placement. For BOs with the RADEON_GEM_NO_CPU_ACCESS flag set, radeon_ttm_placement_from_domain creates a second VRAM placment with fpfn == 0. If VRAM is almost full, the first

[PATCH] drm/radeon: Override fpfn for all VRAM placements in radeon_evict_flags

2017-03-26 Thread Michel Dänzer
From: Michel Dänzer We were accidentally only overriding the first VRAM placement. For BOs with the RADEON_GEM_NO_CPU_ACCESS flag set, radeon_ttm_placement_from_domain creates a second VRAM placment with fpfn == 0. If VRAM is almost full, the first VRAM placement with fpfn > 0 may not work, but t