Re: [PATCH 1/2] drm/amdgpu: increase fragmentation size for Vega10 v2

Am 03.08.2017 um 23:01 schrieb Felix Kuehling: On 17-07-19 11:26 AM, Christian König wrote: From: Christian König The fragment bits work differently for Vega10 compared to previous generations. Increase the fragment size to 2MB for now to better handle that. v2:

[PATCH] drm/amdgpu: set gfx_v9_0_ip_funcs as static

We won't use this member in other files, so set it static. Signed-off-by: Huang Rui --- drivers/gpu/drm/amd/amdgpu/gfx_v9_0.c | 2 +- drivers/gpu/drm/amd/amdgpu/gfx_v9_0.h | 1 - 2 files changed, 1 insertion(+), 2 deletions(-) diff --git

Re: [PATCH] drm/amdgpu: set gfx_v9_0_ip_funcs as static

Am 04.08.2017 um 11:20 schrieb Huang Rui: We won't use this member in other files, so set it static. Signed-off-by: Huang Rui Reviewed-by: Christian König --- drivers/gpu/drm/amd/amdgpu/gfx_v9_0.c | 2 +-

Re: [PATCH] drm/amdgpu: Fix recursive evict/restore worker on a multiple mapped bo

Hi Shaoyun, The change looks good to me. But I'd make the removal of the duplicate warning a separate commit and explain the scenario where this occurs in the commit description (same graphics BO imported multiple times for interop). The code you're changing is not upstream yet. It's in

[PATCH] drm/amdgpu: Fix recursive evict/restore worker on a multiple mapped bo

When one buffer object is mapped muliple times, KFD will treat them as different memory object but share the same ttm_bo with a single eviction fence. Seperate the ttm_bo_wait and attach eviction fence code to avoid ttm_bo_wait trigger the eviction worker on the bo that just be assigned with the