When vram size <= THRESHOLD(256M) lets use GTT for dumb buffer
allocation. As SG will be enabled with vram size <= 256M
scan out will not be an issue.
Signed-off-by: Deepak Sharma
---
drivers/gpu/drm/amd/amdgpu/amdgpu_gem.c | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git
On Fri, May 18, 2018 at 10:21 AM, Michel Dänzer wrote:
> From: Michel Dänzer
>
> Fixes crash in that case.
>
> Bugzilla: https://bugs.freedesktop.org/106293
> Signed-off-by: Michel Dänzer
Series is:
Reviewed-by: Alex Deucher
> ---
> src/radeon_glamor.c | 3 +++
> 1 file changed, 3 insertions
is_dpm_running callback was assigned to the same value
twice. Drop the duplicate.
Signed-off-by: Alex Deucher
---
drivers/gpu/drm/amd/powerplay/smumgr/vegam_smumgr.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/gpu/drm/amd/powerplay/smumgr/vegam_smumgr.c
b/drivers/gpu/drm/amd/pow
To free the fence from the amdgpu_fence_slab, need twice call_rcu, to avoid
the amdgpu_fence_slab_fini call kmem_cache_destroy(amdgpu_fence_slab) before
kmem_cache_free(amdgpu_fence_slab, fence), add rcu_barrier after
drm_sched_entity_fini.
The kmem_cache_free(amdgpu_fence_slab, fence)'s call tra
Hi Christian,
Thanks for your advice, will send a modify patch later.
Best Wishes,
Emily Deng
From: Koenig, Christian
Sent: Friday, May 18, 2018 6:36 PM
To: Deng, Emily ; amd-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/amdgpu: add rcu_barrier after entity fini
Ah! So we have one RCU g