Mesa userqueue free do no wait for the free to complete and go ahead in unmapping the vital bos while kernel is still in queue free and corresponding cleanup.
So ideally we dont need the logging for that and hence remove the warn message as this is expected behaviour and functionally we are making sure to wait for the required fences before unmap. Signed-off-by: Sunil Khatri <[email protected]> --- drivers/gpu/drm/amd/amdgpu/amdgpu_userq.c | 1 - 1 file changed, 1 deletion(-) diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_userq.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_userq.c index f0c7b686f68d..ebfef6470f90 100644 --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_userq.c +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_userq.c @@ -1352,7 +1352,6 @@ void amdgpu_userq_gem_va_unmap_validate(struct amdgpu_device *adev, if (!ip_mask) return; - dev_warn_once(adev->dev, "now unmapping a vital queue va:%llx\n", saddr); /** * The userq VA mapping reservation should include the eviction fence, * if the eviction fence can't signal successfully during unmapping, -- 2.34.1
